[Q] Bizarre reboot, boot loop issue - Desire Q&A, Help & Troubleshooting

Hi all,
So the history is I had CyanogenMod6 on my Desire and was using OsmAnd in the car with the car charger plugged in. The phone reset so I started it again, reopened OsmAnd, then it crashed again. It stopped on the HTC white logo so I removed the charger and weirdly it then booted. When it crashed a third time then it stopped on the white HTC logo and wouldn't go further, regardless of whether the charger was in or out.
I've tried removing the battery etc, but that made no difference.
I've now flashed back to the 2.29 RUU using PB99IMG.zip on the goldcard. This loads fine and all is well, but then every now and again it resets and sticks on the HTC screen again. Also I turned it off once to put my normal SD card back in, and restarting it gave me the white HTC screen. Huh??
Can anyone help please? I need this phone for work and having it die on me and needing an RUU reset (so ALL my data is wiped) is a proper pita.
Thanks.

If its only doing it using osmand then don't use it. Use something else. If its doing it without using it do a full factory wipe, then format the system and boot mounts then reflash. You should be alright. If your still having issues, you might need to use an ruu but you would need to root again.
Sent from CM7

Meaple said:
If its only doing it using osmand then don't use it. Use something else. If its doing it without using it do a full factory wipe, then format the system and boot mounts then reflash. You should be alright. If your still having issues, you might need to use an ruu but you would need to root again.
Sent from CM7
Click to expand...
Click to collapse
It first reset using OsmAnd and Google Navigator but now I have reflashed back to the stock HTC 2.29.405 RUU using PB99IMG.zip and it's still doing it during normal use.
I'm also getting the HTC white screen when I just turn off and back on.
When I flash the stock RUU, does that reformat the system and boot mounts? I know the phone feels like everything is gone since I have to reenter my google acc details.

Yeh, an RUU will completely wipe the whole phone, the boot, system, data, recovery, hboot, cache and what ever else there is, all gets replaced. Yes it is a pain but it will return your phone back to stock and if your still getting errors, then most likely it will be a hardware issue, specifically, the motherboard. Tbh, it's a small price to pay instead of having to send it off.

Related

HELP! Stuck on HTC Incredible power up screen after restore

Installed Cyanogen Mod 6 on my Incredible, backed it up before hand, my SD card didn't work with the MOD, so I restored the back up. I went to reboot after the restore and now it's been stuck on the HTC Incredible power up screen, for about 20 minutes now.
I hear pulling out the battery during anything root related is bad, so I'm avoiding that, but I don't see another option. Any help?
jaredkent said:
Installed Cyanogen Mod 6 on my Incredible, backed it up before hand, my SD card didn't work with the MOD, so I restored the back up. I went to reboot after the restore and now it's been stuck on the HTC Incredible power up screen, for about 20 minutes now.
I hear pulling out the battery during anything root related is bad, so I'm avoiding that, but I don't see another option. Any help?
Click to expand...
Click to collapse
This belongs in general.
You might be able to type "adb reboot recovery" with ur phone plugged in. That depends if ur phone is communicating with the computer. If not just pull ur battery and boot into recovery. Try to reflash cm6, make sure u wipe data, cache, and dalvik cache beforehand.
Sent from my ADR6300 using XDA App
if i were you, i go back to ruu and start all over again.
I ended up pulling the SD Card out, putting an old backup I had stored on my computer onto the card, and restoring from that backup. Works like a charm now.

[Q] [Solved] Stuck at HTC One Screen

Got a HTC One X a while back and decided to keep it stock as long as I dont find a stable recovery. So my HOX was completely stock. Had no issuses with it for the time I have used it which should be around 15days. I did experience some random reboots. Overheating was a problem too.
Last night was using gameboid to play while watching soccer. After match, I tried to use inbuilt browser but it could not be launched. Everytime I started it, a menu opened with sending a report or not. Then tried google play store to download another browser, but that failed too. Even apps did not upadate. got a error. Dont remember exactly but most probably that was error 492.
Then i decided to reboot. After the HTC quietly brilliant screen, came the HTC ONE screen with some sound, and then hung up there. Tried a hard reboot but same thing happened but this time onwards sound vanished.
So what should I do?
Thought of going to bootloader and then factory reset but I have some important data in HOX and then doing factory reset might not solve the problem.
What should I do?
Just to tell you, Now when I went to bootloader and turned off and back on while plugged to laptop, its still on the same screen but this time its charging.
It does not charge while turned off.
Again,
Im unrooted - completely stock and not unlocked via htcdev.
Edit: The phone is charging now with the power adapter.
Edit2: Just did a factory reset via bootloader , back to normal now.
When still completely on stock and haven`t done anything.
I would say return it..
There would be answers and suggestions but why void warranty.
while my phone hangs up at htc one screen, is there any way the data can be restored? Im assuming running ruu erases everything since its virtual sd card.

[Q] HTC Desire Looping "quietly brilliant" startup screen

My HTC desire with the official ginger bread update on is now looping the "quietly brilliant" startup screen - my battery run out and when I started charging it and switched it on, this happened, completely random
I have tried recovery mode etc, however this doesn't work
Does anyone know if there is anything I can do?
Does it go to
- bootloader mode vol- and power
- fastboot mode back and power
I had the same problem, after doing some research I came to the conclusion that the issue was with the partition type of my memory card.
Try this, remove the memory card insert the battery and then restart [do not insert the memory card]. If it works now then you have the same problem I was facing. If not then this could be something different.
Reply, if the same i will provide the solution.
try deleting (wipe) user data and dalvik cache if you don't have something important.
Sent from my HTC Desire using xda app-developers app
Key phrase here is "with official gingerbread update".
via xda app
yes it has the official gingerbread update on it from the htc dev site - ie I have never rooted it or put a custom made rom on it
recovery or fast boot, ie switching on with volume buttons doesnt work
I have tried without the memory card and without the sim card still loops
I just cant seem to stop it looping this screen!
*edit*
oh wait, I just tried fast boot, back and power and that worked!
what can I do now? reinstall rom?
The only option you have right now would probably be to run the official gingerbread RUU again. Unless you wanna root it from this point forward.
You'll probably lose all your data which is probably lost at this point anyway.
My concern is that it just went crazy and you are on stock so I feel something else might be broken.
via xda app
Get the 2. 3. 3 RUU from htcdev only and run it from pc.

Seems like a boot loop condition

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

[Q] JellyTime gets stuck on bootanimation

Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
You could try dirty flashing, but if that doesn't work you'll have to reflash.
bananagranola said:
You could try dirty flashing, but if that doesn't work you'll have to reflash.
Click to expand...
Click to collapse
Thanks for the tip, but it didn't help, gets stuck still on bootanimation.
Time to full wipe and flash it again then. Wipe&FlashTime
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
GuyInTheCorner said:
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
Click to expand...
Click to collapse
I did battery pull several times considering that the phone refused to shutdown even when holding the power button for 10 secs, so battery pull was needed every time.
Anyway, it's now running fine when I reflashed.
910263 said:
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
Click to expand...
Click to collapse
I have the same problem since a crash on opening the outlook-email App (JellyTime 4.2 R9).
I found, that the "data" partition causes the trouble when booting. Formating the "data" partition with "4ext recovery" fixes boot-freezing. But this is not an option for me as my last (working) backup is a couple of months ago (yes, I know - should backup more frequently...).
I was able to backup the up-to-date "data" partition (with 4ext recovery) but when restoring it (even on an fully wiped and updated system) boot sequence freezes again.
Any ideas???
Many thanks!
Solved the problem with the data-backup. Instead of restoring complete partition the APP "AppExtractor" works fine for restoring data of the partition backuped.
For now, system runs perfectly.
Conclusion:
If system hangs in Boot-Animation use Recovery for backup of up-to-date system. Full wipe system and install ROM of your choise. After that restore SMS, contacts, etc. with "AppExtractor". Apps should be installed from PlayStore as far as possible. "AppExtractor" allows restoring of app, data+app, data.

Categories

Resources