2013-05-08, 01:32
(This post was last modified: 2013-05-08, 01:37 by RickyGoldsmith.)
I have a GiONEE Dream D1 device which is based of the MediaTek 6589 family.
The Rooting and CWM is done. I tried 2 ROMs (MIUI and LeWA), both of which get stuck at boot.
I traced the boot and trapped the log for both the stock ROM and the ROMs I'm trying to port.
The major difference that I could conclude is this:
The faulty ROM has a problem with the atci-ril service. Here's the error msg:
fail to open atci-ril socket. errno:2
This, in trun, is one of the important service that establishes the communication channel in between the GSM Stack and the RIL Daemon. This error message keep repeating throughout the boot stuck process.
Anyone has any clue for the cause of this problem? Did I miss (which I think I definitely did - just don't know which one) any system library/firmware from the OEM dude!!!!
Or is this a known issues with MTK Device? If anyone wants the full logs, I can share them. I have both the logs.
I forgot to add that I am using the kernel from the stock rom (The OEM did not release the ROM / Kernel).
Also, I have ensured that I use the ROM based on the same android version that the stock rom is.
The Rooting and CWM is done. I tried 2 ROMs (MIUI and LeWA), both of which get stuck at boot.
I traced the boot and trapped the log for both the stock ROM and the ROMs I'm trying to port.
The major difference that I could conclude is this:
The faulty ROM has a problem with the atci-ril service. Here's the error msg:
fail to open atci-ril socket. errno:2
This, in trun, is one of the important service that establishes the communication channel in between the GSM Stack and the RIL Daemon. This error message keep repeating throughout the boot stuck process.
Anyone has any clue for the cause of this problem? Did I miss (which I think I definitely did - just don't know which one) any system library/firmware from the OEM dude!!!!
Or is this a known issues with MTK Device? If anyone wants the full logs, I can share them. I have both the logs.
I forgot to add that I am using the kernel from the stock rom (The OEM did not release the ROM / Kernel).
Also, I have ensured that I use the ROM based on the same android version that the stock rom is.