Develop Bugs

[Q] Desire won't boot

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.

Please help me help him... Thx ____

I sold my old incredible to a kid. It sat for about 7months due to me upgrading to new phone. It had CM7 on it running fine when sold it. When he went to activate it, problems problems problems. I took it back him and told him I would fix it before paying me. I'm having troubles.
- No working recovery. can't get it to boot properly. I had the "5 vibrates of death" couple times.
- I'm trying a couple ruu's but when finished it will get to the lock screen, look normal, then reboot to lock screen then after a couple times will 5 vibrates then black screen.
1. I've tried [HOW-TO] Fix 5 vibrate and black screen (http://forum.xda-developers.com/showthread.php?t=1110865) I can seem to do the sdcard fix but not sure how to complete the usb fix or if that will even help me along. I can't "run terminal in anroid" because I can't get the Rom to boot up. All I can do is fastboot.... Compouter recognizes device.
2. I've tried multiple RUU's including PvilleComp's at http://pvillecomp.com/?page_id=22
3. I'm using hboot .92 and radio is 2.15.10.07.07 s-off
I realize problems like these have been asked before, I've looked through them, uesd the search button, etc.... But I'm still really stuck and would like to fix this before reimbursing kid money.
Thanks

red3razor said:
I sold my old incredible to a kid. It sat for about 7months due to me upgrading to new phone. It had CM7 on it running fine when sold it. When he went to activate it, problems problems problems. I took it back him and told him I would fix it before paying me. I'm having troubles.
- No working recovery. can't get it to boot properly. I had the "5 vibrates of death" couple times.
- I'm trying a couple ruu's but when finished it will get to the lock screen, look normal, then reboot to lock screen then after a couple times will 5 vibrates then black screen.
1. I've tried [HOW-TO] Fix 5 vibrate and black screen (http://forum.xda-developers.com/showthread.php?t=1110865) I can seem to do the sdcard fix but not sure how to complete the usb fix or if that will even help me along. I can't "run terminal in anroid" because I can't get the Rom to boot up. All I can do is fastboot.... Compouter recognizes device.
2. I've tried multiple RUU's including PvilleComp's at http://pvillecomp.com/?page_id=22
3. I'm using hboot .92 and radio is 2.15.10.07.07 s-off
I realize problems like these have been asked before, I've looked through them, uesd the search button, etc.... But I'm still really stuck and would like to fix this before reimbursing kid money.
Thanks
Click to expand...
Click to collapse
Have you tried reflashing cwm recovery thru hboot? Then wipe everything and flash a rom.

Yes I did try this. Got CMW re-installed, and when I tried to select any option in recovery just goes to picture of hat and hangs there. I press power button and goes back to CMW main menu.
I also tried a fix from your post:
cmlusco said:
Not sure where you got those instructions or files from, but there not for the incredible.
Heres what you do.
Download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and put it on the root of your sdcard in no folders.
Pull the battery, reinsert, and press vol down +power for 5 secs then wait for 5 mins not touching anything.
Press vol up and then wait for 20 minutes touching nothing. The phone will reboot once during the process, this is normal just let it be.
Press vol up, the phone should reboot and come up being able to see things and boot to the os normally.
Click to expand...
Click to collapse
This is where I've gotten the furthest. Got thru HTC quietly brilliant. Droid animation (red computerized looking stuff), "Droid" sound, then got to lock screen. Sit there for 5sec or so then would reboot, do the same thing over again and get to lock screen. Reboot again, then usually "5 vibes of death"

The kid does not have a phone other than this one I'm trying to fix, and they would really like it fixed and in their hands by Friday.
I just tried re-installing CMW again, and just hangs on white HTC screen, doesn't even make it to CMW menu. This is kicking my butt.

Fruitcake? Back to stock? That worked on my phone once..not sure if it was sim or not
Sent from my MB860 using Tapatalk 2

He would like back to stock. S-off or S-on. Root or no root. Just working properly.

red3razor said:
Yes I did try this. Got CMW re-installed, and when I tried to select any option in recovery just goes to picture of hat and hangs there. I press power button and goes back to CMW main menu.
I also tried a fix from your post:
This is where I've gotten the furthest. Got thru HTC quietly brilliant. Droid animation (red computerized looking stuff), "Droid" sound, then got to lock screen. Sit there for 5sec or so then would reboot, do the same thing over again and get to lock screen. Reboot again, then usually "5 vibes of death"
Click to expand...
Click to collapse
What button are you using to select things in recovery? Pressinh power on the main menu brings up the orange hat, press the trackball to select items power to go back.

I have to admit I was using the power button (used to my Rezound) but now I cannot even get CMW to work. Flashed it with the .zip in hboot/bootloader. Tried both restart and not restart after running recovery update. Both ways, phone will just hang at white HTC screen and not enter CMW anymore. Sometimes screen goes black then back to white screen or just stays on white screen indefinitely.

Could a bad battery be causing this? I'm trying 2 different ones. I'm not sure if either are bad, just trying to troubleshoot. Is there a way to check battery health on a non-bootable phone?
Any other suggestions to try? Thanks everyone for your help. I'm giving this phone just a few more hours of me fussing with before it gets retired.

UPDATE:
after battery sitting on charger all day while at work (10hrs or so), tried to boot up phone. went well. got to OS right away. I let it sit for 1/2hr to see if it would reboot or not. it stayed alive. i tested making a phone call: OK. I browsed the the XDA website for less than 1 minute, it then rebooted on me. white HTC screen then black. white HTC. then black. white HTC then rebooted fine. couple seconds later shuts off again. this time the same white HTC then black 3 times same as before. then instead of rebooting, got the 5 vibes of death.
the phone while working also asked me to update to lastest android 4.08.605.2
i'm not sure which RUU i ran to get this far, but must have been an earlier.
so i guess now i will attempt the 5 vibes fix, that's if i can get the phone booted for long enough to install terminal emulator from market and follow the steps.
any ideas guys? thanks in advance.

i did the sd card fix and attempted 5 vibes fix: http://pvillecomp.com/?page_id=33
pulled the battery. put it back in. powered on the phone. once the first white "HTC Droid Incredible" screen came up, I plugged phone into PC. instead of one audible ding from computer saying device connected, i recieved 3 very quick dings from PC and phone shuts off. no charging light indicator. if i single press power button, unresponsive still.
now i unplug device from PC, remove battery, put battery back in, hoping for it to reboot normally. instead i get white HTC then black. white HTC then black screen with no boot up.

I believe so far I've tried the GB RUU from PvilleComp and the RUU provided by cmlusco in my post #3.
I guess now I'll try the Froyo RUU from PvilleComp's site: http://pvillecomp.com/?page_id=22

It could be your battery, but usually the phone will just turn off not reboot. 4.08.605.2 does not have a PB31IMG.zip so you have to use an ruu exe, but that requires you to be able to boot. You could try the froyo PB31IMG and hope it works. My only other sugestion would be to try and upgrade your hboot to the new 1.02, and then use the htcdev site to unlock it. Then fastboot flash cwm recovery and hope you can access it.

i upgraded the hboot. unlocked via htc site. reinstalled CMW and was working fine. flashed ota stock GB. same problems still. i left him long enough without a phone, so the fixer project is ended.
thank you all for your help, greatly appreciated

red3razor said:
i upgraded the hboot. unlocked via htc site. reinstalled CMW and was working fine. flashed ota stock GB. same problems still. i left him long enough without a phone, so the fixer project is ended.
thank you all for your help, greatly appreciated
Click to expand...
Click to collapse
No problem. Sounds like it may be a hardware issue.

[Q] Is my EVO Dead/Gone for good?

Hi Friends,
I did a lot of searching and tried a bunch of things, but I am not very successful. Can you experts please tell me if my EVO is dead/gone for good?
Symtoms:
My Evo was charging (it was rooted and S-Off), I took the charger cable off, and the phone rebooted.
It went to the White HTC Evo screen that comes before any ROM boots, and basically looped their infinitely.
Since then, the symptoms have switched back and forth from Bootloops on the white screen OR STUCK on the white screen, infinitely.
Currently, I am getting white screen boot loops
Things I have tried:
1. Cleared Storage (via Bootloader/Fastboot)
2. Chose "Recovery" from Bootloader/Fastboot (nothing happens, reboots and stuck on the white screen or loops)
3. Reverted back to S-ON
4. Flashed other Recovery zips
5. Upgraded the Fastboot version
6. Flashed the RUU
Current Situation:
Nothing changed guys... and after the RUU flash (out of which the Radio flash was the only component that FAILED) my PC31IMG.zip files are no longer being promoted for updates in my Fastboot/Bootloader menu.
While the reboots continue on the white screen...
Can't access Recovery
Can't run PC36IMG.zips anymore
Am I done here guys, or is there still anything I can do to save my EVO?
Appreciate ALL your help!

Man I have the same problem execept I'm not rooted or s off if you change the battery and let it sit for awhile off it will turn on but it will reboot in about 5 mintues then get stuck on the sprint 4g screen of the htc screen

Hey theneguy,
Thanks for your response... My phone was rooted, but is now S-On and Unrooted, I believe (I can't tell because I am not able to get in the OS).
I can't get into Recovery and my PC31IMG is not being read now...
Any ideas, friends?
theneguy said:
Man I have the same problem execept I'm not rooted or s off if you change the battery and let it sit for awhile off it will turn on but it will reboot in about 5 mintues then get stuck on the sprint 4g screen of the htc screen
Click to expand...
Click to collapse

same thing happened to my son, pulled sd card and it would boot fine, found and deleted a corrupt .img file on sd...all is fine

Latest Update guys:
I tried flashing the RUU via HBoot/Flashboot, and the update failed, but the progress bar at the screen was full/successful. The on-screen wizard tried to take me to the "Recovery" steps, nothing was fixed.
The computer wizard was stuck at: Sending Signature....
And the phone had the full progress bar from the previous flash.
So I yanked the battery out, cause I had no options left.
Well, needless to say, now, NOTHING turns on. The phone doesn't charge, and blah, blah, blah.
So guys, can someone give me a verdict... is my EVO done for good?
Thanks for your help.

I can't get in the recovery eather I tryed pulling the sd card out it is still doing the same thang

ProFragger said:
Hey theneguy,
Thanks for your response... My phone was rooted, but is now S-On and Unrooted, I believe (I can't tell because I am not able to get in the OS).
I can't get into Recovery and my PC31IMG is not being read now...
Any ideas, friends?
Click to expand...
Click to collapse
It should be PC36IMG not 31.
Sent from my PC36100 using Tapatalk 2

Thanks Mark,
But I don't think it matters anymore... I think with the battery pulled out after a failed RUU.exe installation has truly bricked my phone for good.
It doesn't charge, the battery was good, NOTHING lights up, and I just think it's game over...
MarkEv0 said:
It should be PC36IMG not 31.
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse

I think you're right...

Phone is "looping" while booting.

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

Phone not booting

Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.

Why don't you try flashing the latest version of ICJ (3.4) with a full wipe and see whether the problem persists? Can you enter recovery now??
However, there's always a possibility of a hardware failure... and your situation with the random reboots / recovery reboots suggests somethings wrong!

ViktorN said:
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Click to expand...
Click to collapse
Sounds alot like a issue I had on ICJ quite a while ago.
If you select recovery at the bootloader, do you see the recovery for a split second and after that it reboots? I did flash multiple recoveries but it all didn't help. The luck I had is that fastboot was still working
I tried everything to get it to work, but nothing seemed to help. The only luck I had was that fastboot worked, and with that I managed to flash a RUU. What actually happend I don't know, but it worked again.