Hey all, first time poster. I wrote a real nice explanation of my problem, but i lost it so anyways, i'll keep it short(ish).
The EVO is less than 3 weeks old, running the latest OTA, recently rooted using UnrEVOked 3, nothing fancy. I ran the battery down completely last night (first time since i got the phone) and once i got to a power source, it wouldn't boot correctly. It hangs at the white splash screen, and then finally boots up but won't respond to any touch input.
Also the phone seems to be running exceedingly slow, the boot process takes substantially long than normal once it gets past the splash screen and my live background is freezing and seems to be stuttering.
I launched into the bootloader and i get a "Touch Panel - Fail". LAME!
I'm not sure what to do at this point, whether i should wipe it or go back to stock or what. Any advice would be much appreciated.
UPDATE:
I managed to get the phone into the recovery console, make a back up (i was planning on going back to the stock image) and wipe the dalvik cache and fix permissions. I rebooted and voila! fixed. Hopes this helps any one else who has this problem.
Moral of this story: Travel with a charger.
Another update. It froze up again in the middle of sending a text. I rebooted by battery removal, and it did the same thing again. Super long splash screen and sluggish boot up, no touch response when it finally came up. I booted into recovery and cleared the dalvik cache again. Seems to be working again now. We'll see if it does it again.....
Well, the screen locked up again. I tried going through the whole process again. I wiped the caches and battery stats, nothing. I wiped all the storage and data, booted into a clean stock interface, nothing. Restored the backup image, and then at some point, through all the rebooting and whatnot, it just shut down completely. I can't even get it to the bootloader. I'm really feeling like it's a hardware problem, and i've made peace with sending it back for TEP, but i have no way to unroot it.
Any suggestions? Please......
Theres unroot processes out there. I cant remember where but ive seen them. Mine gets sluggish too, but after a reboot its ok. You cant even get into the bootloader tho. I'm not even close to an expert but.......uh I'd 'lose' it and call the insurance co....
Hi everyone,
I've got a problem. My rooted desire running ReflexTSenseHD v1.8. Last night the battery went dead or so I thought then. Anyway when I got home and I tried to charge it nothing happened. Tried a few things (battery out, battery in) and finally got it charging.
The next morning I tried to boot it and but it hangs on the white HTC screen. Took the battery out, tried it again still the same screen. Took the battery out again and tried it one last time. I booted it in the bootloader and cleared storage. This time it booted, but when it finaly got to the lock screen it said: connect charger but couldn't get it off the lockscreen. Took the battery again and this time it booted normally and worked like nothing happend.
After a few hours I got curious if it would boot normally right away. But unfortunately, the whole thing started over again.
I searched the web, but couldn't find anything like this. The white htc screen freeze is known, but that is usually due to a broken/ faulty bootchip which in my case is not likely because I can boot (sometimes).
I haven't got a clue what to do next but hope any of you do.
Thanks for reading this, and hope that somebody has a solution.
Robit
ps sometimes I can boot in recovery but most of the times it will hang on the white htc screen.
Try boot into recovery and wipe the boot, cache, system, data, dalvik cache and do a factory reset too. What on a fresh rom. If you can't be bothered with that, use an ruu which will do a fresh everything, even the bootloader. If things still are messing up, talk to HTC it your carrier.
Sent from CM7
Thanks somehow I got into recovery and wiped it all, and so far so good
Sent from my HTC Desire using XDA App
unfortunately the issue has returned. So far I figured out that if I wait long enough, it will boot but then hangs onto the lockscreen, show the empty battery and says connect charger. I can't unlock it so the only way of rebooting is to take out the battery and start it again.
I just don't get it. It can't be a faulty bootchip, I suppose it wouldn't boot at all then.
I already tried the steps above from meaple but this time I hadn't so much luck. In booting it again.
I'm getting a little desperate by now so any help would again be appreciated.
Robit
ps: I'm on a new rom the RCMixHD v3.6 which at first worked like a charm.
Hi, I left my Desire with low battery on night, in the morning I woke up and I realized that it is turned off - it probably discharged. I turned it on, and it turned off while booting, it didn't have enough energy to boot... So I charged it a little bit, and again booted - phone is booting, there is green HTC logo, then "HTC Quietly Brilliant" with booting sound, and then black screen and it is booting again and again... Phone have RUU 2.3 (Gingerbread), I used GoLauncherEx, and it is rooted. I can enter recovery, I tried "reboot" and "reboot bootloader" but still the same. I wasn't doing anything with Phone, everything was working, so it happened without reason? Or maybe it's because of Launcher which is loading after turning on phone? Help me, please
I don't think that it is caused by launcher, because from what you wrote, your phone doesn't even get to UI.
Firt of all, I'd try doing a nandroid backup (just for sure), then full wipe (everything...., do it 3 times, I think I have read somewhere that cwm sometimes doesn't do i properly first time). Try to reboot. If it is still the same, try to flash another rom (cm7 for example). If that doesn't help, try official not rooted RUU and it should fix the problem. (Then, ofcourse, you will have to root your phone again.)
Good luck
Well, I found something like "Clear Storage" and it helped, thanks for answer anyway
OK, I am glad it has been solved
Hi Folks,
I was setting up my "old", rooted and S-Off Incredible for our son to play games when travelling, etc. - it's no longer registered on Verizon's network, but is fine for wireless and downloaded apps.
After charging the battery and installing about 47 app updates today (i.e., it hasn't been booted in awhile), I was tinkering around with adding some apps from Play and it suddenly rebooted. Then, it kept booting at the white HTC logo screen.
So, I pulled the battery and decided to go back to Verizon stock, using the image from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
Essentially, I booted into HBOOT, went into CWM Recovery, wiped appropriate storage, then rebooted back into HBOOT after putting the above image onto the root of my SD card. Maybe I don't need to wipe storage for a RUU, but it's habit by now.
HBOOT installed the RUU image after it prompted for a Yes/No and the Incredible booted with that old, "DROID!!" startup (gosh, didn't miss that) and showed the initial lock screen.
I pulled down the lock and started only a few seconds into phone initialization when it rebooted.
Now, it reboots as early as the HTC logo screen or gets to the lockscreen and reboots on its own after a second or two.
Seems like a boot loop, but I just installed a new RUU - so . . . I'm wondering if this is a deeper issue.
Ideas on how to go about fixing this rebooting problem are welcome, please. Is it possible that my half-completed Play install - i.e., just before it began this symptom - crunched a file system that needs to be fixed up?
Thanks,
- ooofest
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
ooofest said:
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
Click to expand...
Click to collapse
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Click to expand...
Click to collapse
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
ooofest said:
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
Click to expand...
Click to collapse
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Click to expand...
Click to collapse
Yeah, it tends to get beyond the HTC logo screen after a new ROM install, but usually reboots as soon as I see the notification for "preparing internal storage".
Afterwards, it tends to reboot at varying times - sometimes at the HTC logo, other times it gets past OS startup and reboots after a few seconds.
. . .
EDIT: I just rebooted and . . . now it suddenly booted into CM and is working normally. What the heck?!
I'm not a CM person and would like to install another ROM to see what happens after that - do you think the phone EMMC is starting to go, perhaps?
- ooofest
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Click to expand...
Click to collapse
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
ooofest said:
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
Click to expand...
Click to collapse
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
cmlusco said:
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
Click to expand...
Click to collapse
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
ooofest said:
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
Click to expand...
Click to collapse
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
cmlusco said:
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
Click to expand...
Click to collapse
Interestingly, I let it "cool down" for a bit and charge from the wall instead of USB, then was able to wipe all storage, install CM7 and it booted up fine.
So, I let it sit for a bit longer, wiped again and installed the latest stock RUU. This time, it took longer to boot and came up fine - I now have a relatively stock (except for S-Off) Incredible, again.
From your suggestion, I'll shop for another battery and see if a new one helps to keep the sudden reboots at bay.
Thanks.
- ooofest
Hi Folks,
After working this for some days, my Droid Incredible with AMOLED display still gets into a reboot or boot-loop condition after a random amount of time of continuous use. Almost as if it heats up or something in its memory mgmt is flaky.
It can take new ROMs, recoveries, HBOOTs, radios, etc. - but, regular use just brings up the boot condition too easily, so I can't give it to my kid as a simple gaming device. I tried a new battery in case that might be the issue, but the condition still persists. Pulling the battery and waiting 10+ minutes usually allows it to work again, until the next reboot cycle starts up.
This phone is running the latest RUU and is also S-Off.
So, I'd like to give it away to the first person who requests it.
I'm not offering a trade or purchase, but if someone wants this phone to use/test/etc. with, just PM me and we can plan on a quick dropoff in NY/NJ/CT area or I'll send it to your continental USA address with both batteries and no explicit or implied warranties, guaranties, liabilities or claims of operating performance, etc.
- ooofest
So I have a rooted HTC desire HD with Jellytime on it. All was working great till recently when it would shut down by itself. Today after I wanted to test a new boot screen from Rom toolkit I restarted it and while the boot screen worked great after it finished I see a black screen (backlit so I know its on). I tried going to the bootloader but after I try to go to wipe cache for example it restarts by itself and it gets stuck after the boot screen... Any ideas?
ok an update seems that if I go to the recovery via down button and power it lets me do actions. All this time I went to recovery mode when phone was shut down and plugged into a power source. I did a wipe cache and now it says android is upgrading and now it finished saying starting apps. Hope it didnt get stuck there because it keeps doin the cycle animation but doesn't do anything else.. I ll leave it be for a bit like this... :/ Had to restart it by removing the battery after 20 minutes... same problem as before still...
another update... just before it goes to a black screen when the boot screen finishes an orange light appears just briefly (where the green light appears when it charges)
Wipe everything (system data cache) and install a stock-ish ROM. What happens?
bananagranola said:
Wipe everything (system data cache) and install a stock-ish ROM. What happens?
Click to expand...
Click to collapse
I flashed the rom again and wiped data and all seem to be ok now. I ll update this because I saw many people have similar problems... thanks in advance for any help!
Have the same problem.
I bought this with the problem that it keeps rebooting all the time.
I unlock the bootloader with htcdev,root with Easy Ace Tool,flashed the new cyanogenmod 11,
but did the same .
At least 3-4 rebooting before open normally.
I said that it must be ROM issue and flashed the KK-LegacyCarbon-4.4.
Did the things should be...flash the ROM and then the boo.img separately.
Now i have black screen and the only screen i am able to get is bootloader and the recovery 4EXT.
I reflased cyanogenmod back but nothing happened,any thoughts???