[SOLVED] Stuck on white HTC screen after flashing the latest Unity v9 kernel
Guys, i flashed the GoApk ROM 2.3.5 with Sense 3.0 and everything was fine. Today, i flashed the new Unity v9 kernel after wiping Dalvik cache and rebooted, but now my phone has been stuck at the wite HTC screen for the past 1 hour. The three button reset is not working, neither is the adbreboot recovery command as adb does not detect my device. Please help... I do not want to pull the battery and fry my eMMC.
EDIT: Got into the recovery and restored nandroid backup. Back up and running now. Thanks everybody for their contribution.
Guys, i flashed the GoApk ROM 2.3.5 with Sense 3.0 and everything was fine. Today, i flashed the new Unity v9 kernel after wiping Dalvik cache and rebooted, but now my phone has been stuck at the wite HTC screen for the past 1 hour. The three button reset is not working, neither is the adbreboot recovery command as adb does not detect my device. Please help... I do not want to pull the battery and fry my eMMC.
Look in my signature for various links...
Download and extract the adb & fastboot into a directory on your PC. Ensure that you have HTC drivers installed on you PC if not also download and install the link in my signature.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
adb reboot recovery
which should take you into recovery, where you'll be able to reflash or restore a nandroid backup from.
I think it got updated to the most recent one when i flashed the ROM. I tried everything you have suggested. Nothing works...
---------- Post added at 08:18 PM ---------- Previous post was at 08:16 PM ----------
I'm just waiting for the battery to run out so it powers off and then i'll try to boot into recovery again. I thought Unity kernels were compatible with sense roms. Please can anybody help me out here?
@ proxuser: But i do not have EXT4, i have CWM recovery. Can you guide me as to how to do what you sais in your last post please?
Have you attempted the suggestions in my earlier post #2?
After following what I suggested, although I'm not the only person to suggest that you attempt to use adb ....you seem to be missing the point or perhaps not understanding?
Follow step in post #2
Then fire up a PC CMD window, go to the directory where adb is extracted to and type the command
Code:
adb devices
tell us what the response is?
---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------
Quote:
Originally Posted by enigmaamit
wont pulling the battery fry my eMMC? i'm scared of that...
It doesn't matter whether you have CWM or 4EXT they both are similar and perform the same functions.
There are still quite a few of folks who run Gingerbread on their … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?