Develop Bugs

[Q] EVO 4G won't boot, stuck at HTC EVO 4G screen

Hi, hoping someone can help me. My phone seems to have bricked itself. A few weeks ago i had CM6 on my phone then i reverted back to the stock rom from HTC. The phone worked fine for a few weeks then about a week ago i started having random data connection issues, yesterday the phone started resetting by itself, after the third or fourth reset the phone stopped booting at all. all i get now is the white HTC EVO 4G screen or the bootloader when i hold the volume down button.
Here are the version numbers on the bootloader screen.
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
i can only get windows to recognize the phone through usb by using the HBOOT USB option and installing the android bootloader interface driver. I don't really know how to use ADB and i'm not even sure if it is seeing the phone. All i want to do it get this back to official firmware.
any and all help is appreciated
thanks.

Well, it's not bricked if you get into that menu. Can you get into your recovery? If so, try wiping everything and reflashing the rom.

No i can't get into recovery, i even tried reapplying clockwork recovery trough there and all it does is install it, say it's installed ok then i reboot and try to go to recovery mode and it just goes to the white HTC EVO 4G screen

What version of hboot do you have?
*Nevermind* Apparently I can't read. xD
What root method did you use?

that's if i even installed it right.

i'm not sure if it even is rooted anymore because i had put the official firmware back on, when i had CM6 installed i used clockwork recovery and unrevoked

well if you were able to install a custom rom like cm6 then you are more then likely rooted. you say that you cant get into recovery? you should just try running the ruu.exe and returning to complete stock and then reroot if you want.

the official RUU.exe doesn't see the phone. when i connect hboot in the bootloader, device manager see's the phone as android bootloader interface and it i let the boot normally and let it crash at the evo 4g screen it show's up as "Qualcomm CDMA Technologies MSM" and doesn't have a driver. I am running Windows 7 x64

maybe you should try slashing the stock pc36img.zip maybe that will get you back on track.
Edit: this is the link to the thread with the stock pc36img.zip
http://forum.xda-developers.com/showthread.php?t=791019
and just for future reference. it is not that hard to do a search of the information that is needed. while i was here posting these things i found with the search all the info i hae given. just food for thought.

What caguirr4 said. With that file (or since you have s-off you can TRY getting a rom zip and renaming it to pc36img.zip) your phone will read it automatically when you boot using the volume down technique. That should at least get your phone to boot up and you can continue trouble shooting from there if you have more problems.
Remember: Conserve your battery! You don't want the juice to run out while the phone is in the middle of flashing something. THAT is how bricks are made.

i ran the update you gave me, the phone said that all the stages of the update were sucessful and asked me to reboot, i did so and now my phone won't power on and when i plug it into the wall it won't show any charging lights.

zerozr1 said:
i ran the update you gave me, the phone said that all the stages of the update were sucessful and asked me to reboot, i did so and now my phone won't power on and when i plug it into the wall it won't show any charging lights.
Click to expand...
Click to collapse
You ran the updates that who gave you? Various things were suggested on this thread.

sorry for not clarifying,i ran the original stock image that was linked to me by caguirr4 in post #9. According to the update it ran fine but after that the phone died when it had me reboot.

zerozr1 said:
sorry for not clarifying,i ran the original stock image that was linked to me by caguirr4 in post #9. According to the update it ran fine but after that the phone died when it had me reboot.
Click to expand...
Click to collapse
Ok, so you press the power button, and it does nothing? That doesn't sound good at all. Hopefully, your battery is just dead and the drivers for the USB port didn't install right. In which case, you need this:
http://forum.xda-developers.com/showthread.php?t=695243
Do you have any extra batteries you can try to make sure that battery isn't just dead?

I ended up taking it to a sprint service center, they tested the phone with thier own battery and the phone was dead. they are replacing the phone for me now. thanks you everyone for trying to help.

You could of just overwritten the ENG bootloader u had installed...

I am having the exact same problem. I can get to the bootloader but not recovery. Here's my specs
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.21
I had cyanogen 6.1.1 installed on it and it was was working fine. I just felt the thing vibrate and took it out of my pocket to see the "htc EVO 4G" screen and it just keeps rebooting unless I hold the volume button to get into the bootloader.
I REALLY don't want the stock firmware back on here and would like to avoid loosing root if possible.
I tried putting the PC36IMG.zip from here and at first it asked me if I wanted to flash it and after the first thing it restarted and now gives an error Main Version is older!
Update Fail!
Any ideas? I would really like to keep this phone.
Thanks,
Justin

I've tried basically everything I can think of. After attempting to flash the first PC36IMG.zip file I get the main version error for every other one.
Is there somewhere I can get the latest PC36IMG that will be newer and I can try to flash? At this point I don't really care if I lose root (if I haven't already) I just want my phone back.

embmicro said:
I've tried basically everything I can think of. After attempting to flash the first PC36IMG.zip file I get the main version error for every other one.
Is there somewhere I can get the latest PC36IMG that will be newer and I can try to flash? At this point I don't really care if I lose root (if I haven't already) I just want my phone back.
Click to expand...
Click to collapse
Just run the ruu.exe and get it back to stock.
Sent from my PC36100 using XDA App

I tried that. I even tried flashing the stock PC36IMG.zip (which flashed successfully) but I had the same problem. I finally gave up after like 8 hours of working on it and took it into Sprint. I am going to pick it up at 7. They said if they couldn't fix it they would give me a new one for $35 since I'm out of warranty which doesn't seem bad.

[Q] Boot Looping + No Recovery Access

Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!

Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
Many of us are racking our brains trying to figure out what is causing this situation. Everyone who are experiencing this were using CM7, like you, and it happened to of nowhere and for no known reason. I don't think anyone has figured out a workaround, but I could be wrong. I haven't ready through the forums today regarding this issue. Just know that you are not alone, my friend....

Well, it doesn't look too hopeful from what I have seen so far, but thanks for the support. It's good to know that I am not alone.

If you can still access the bootloader, you should still be able to run an RUU through fastboot.

It happened to me, I was one of the first on the forum it happened to, in January. Was never able to fix it, you could spend a loonnngggg time, and get no results. If you search for my threads you can see the ones I started about the subject.
Long story short, I was never able to fix the problem or get S-On. However by doing a battery pull while flashing a rom with a different radio, during the radio installation, I bricked my phone to the point that it wouldn't even turn on. So thats basically your only way out that I know of. You'll have to perform the battery pull upwards 20 times probably before you get the phone to fully brick.

I'm on CM7 nightlies. What are the HW specs of those having these problems? I thought it was due to CWM but there have been some on RA experiencing this too. Just wondering if this is more specific to the newer HW builds/hboots or occurs with all phones.

My Evo is hardware version 003 for what it's worth.

Westibone said:
My Evo is hardware version 003 for what it's worth.
Click to expand...
Click to collapse
When you select recovery, what happens?

I had same issue in Jan after flashing miui.
tried the suggestions on this thread..but nothing worked:
http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html
Had to replace my phone...that seems to be the only way out of this.

This is the reason I have stayed away from CM for so long. I keep seeing these horror stories about bootlooping, etc. I know its awesome when its running, but when it comes to the point where bricking your phone on purpose is a good thing, something is wrong For those that it has happened to above, did you get your new one and go back to CM (or any other AOSP rom)?

teh roxxorz said:
When you select recovery, what happens?
Click to expand...
Click to collapse
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again

My God, another one. It's weird these seem to be happening more and more...

Westibone said:
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.

teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Hopefully, your RUU will work. Others who have attempted to this this very thing still couldn't make it work. Me, k2buckley and others have yet to figure it out and believe me, we've tried everything within our experience range. A solution will be found, I have no doubt about that, but "when" is the question that I cannot answer.

teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.

k2buckley said:
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
Click to expand...
Click to collapse
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.

Same Here
Wow, what a coincidence, this just happend to me last night. I had just finished installing and flashing the new, SavagedZen(MOD)-RC1-Evo4G, Rom. Went to bed and sometime during the night the phone got stuck on restarting on the EVO white screen and turning off and on continusly. I have tried all the efforts of putting the stock ROM back on and everything else mentioned in this thread, but to no avail. Like you said, cant get into recovery or anything, just keeps looping through startin and stopping.
With all that is said so far on this thread, it looks like a new phone is the only way to fix this.
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse

By some awkward chance, have you tried a full wipe, and then flash a sense rom?

teh roxxorz said:
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Click to expand...
Click to collapse
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.

k2buckley said:
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
Click to expand...
Click to collapse
I hope my case doesn't come back to haunt me. Seems like we got a T Virus of phone crashings going around...those already along their way [like you and I] are imune...the newer ones get sucked in. we haz to fix this soon-ishly.

[Q] Yup my evo is bricked..need help serious

Supersonic evt2-3 ship s-off
hboot-2.02.0000
microp-041f
touch panel-atmel224-16ab
radio-2.15.00.09.01
root evo, i flashed my phone with some kind of rom i forgot the name, it flashed in all on clockwork, then after a day it the battery went dead and then when i charged it it boots to the htc evo 4g white screen and just sits there..i did the pow+vol down..went to the bootloader, then go to recovery and it still sits on the white screen,i did the pcimg36 method that didnt work either.....i think this phone is screwed

501rockstar said:
Supersonic evt2-3 ship s-off
hboot-2.02.0000
microp-041f
touch panel-atmel224-16ab
radio-2.15.00.09.01
root evo, i flashed my phone with some kind of rom i forgot the name, it flashed in all on clockwork, then after a day it the battery went dead and then when i charged it it boots to the htc evo 4g white screen and just sits there..i did the pow+vol down..went to the bootloader, then go to recovery and it still sits on the white screen,i did the pcimg36 method that didnt work either.....i think this phone is screwed
Click to expand...
Click to collapse
What did you flash a PC36IMG of? An RUU, or did you try to reflash a recovery. My first suggestion would have been to reflash recovery, using a PC36IMG, and see if that gets you recovery back. Is that what you already tried? If not, try it. I will attatch a PC36IMG of Amon Ra recovery. Flash it with the bootloader, and see if you can get into recovery once it's finished flashing. If that works, then try doing a complete wipe (wipe EVERYTHING except your sd card, maybe even use a Format all.zip). Then reflash a rom. If you're unsuccessful with flashing the recovery, I'd suggest trying an RUU or a PC36IMG of an RUU again.
Again, the PC36IMG I attatched is of Amon Ra V 2.3.
Find RUU's and PC36IMG's here: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Or try this PC36IMG of the 3.70 RUU here: http://db.tt/gqTAPS1

"Some kind've ROM"?
That's a little vague, isn't it?

501rockstar said:
Supersonic evt2-3 ship s-off
hboot-2.02.0000
microp-041f
touch panel-atmel224-16ab
radio-2.15.00.09.01
root evo, i flashed my phone with some kind of rom i forgot the name, it flashed in all on clockwork, then after a day it the battery went dead and then when i charged it it boots to the htc evo 4g white screen and just sits there..i did the pow+vol down..went to the bootloader, then go to recovery and it still sits on the white screen,i did the pcimg36 method that didnt work either.....i think this phone is screwed
Click to expand...
Click to collapse
You don't remember the rom you flashed? Seriously? Did you not download it from somewhere and if so, can you not get on your computer, go to that particular site where you downloaded the rom from and retrieve its name? After flashing the rom, what other changes, if any, did you make to your device? Was the phone performing fine before the battery drained? C'mon man, help us help you?....
posting & replying via the XDA Premium app.

HipKat said:
"Some kind've ROM"?
That's a little vague, isn't it?
Click to expand...
Click to collapse
That's what I was thinking. Not remembering the name doesn't sound hopeful either.
OP, do you know if it was AOSP or Sense? 2.2 or 2.3? Did you get it from xda?
More importantly, did you do a nandroid backup before flashing? If so, you need a PC36IMG.zip of Clockwork so you can go in and restore your backup.

Recovery image of clockwork provided; remove the -1 in the name, place on the root of your sdcard, and flash it in the bootloader.

ok im gonna do it and see what happens

downloaded.. RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15. 00.09.01_NV_1.77_CNV_release_150224_signed.exe (192.95 MB)
open the app and got a error saying error 170 usb connection(the evo is and stuck at the htc evo 4g white screen)
and when i plug in my evo while its on white screen it will say drivers not install..then i check my device manage and the evo drivers are known as qualcomm cdma technologies msm

the rom that messed my phone up was Myn’s Warm TwoPointTwo, i tried flashing the zip through clockwork...but it failed. now i cant get into clockwork and flash any zip nomore ...when i go to recovery it sits on the white htc evo 4g screen

You need to connect you evo in fastboot from the bootloader, then run the ruu from the pc.

501rockstar said:
the rom that messed my phone up was Myn’s Warm TwoPointTwo, i tried flashing the zip through clockwork...but it failed. now i cant get into clockwork and flash any zip nomore ...when i go to recovery it sits on the white htc evo 4g screen
Click to expand...
Click to collapse
Nope. That particular rom did not mess up your device, unless of course, the zip was corrupted somehow. Flashing it through ClockworkMod probably did. Why are you using an older software version (3.29)? The latest version is 3.70.
UPDATE: Once you've flashed the recovery via the bootloader, as directed by others, download the SECOND FILE from the link below, copy it to your SD card and then flash it from within recovery. It is the rooted stock rom.
http://forum.xda-developers.com/showthread.php? t=884060
posting & replying via the XDA Premium app.

Ive flashed probably a hundred times and ive never had a ROM brick my phone, and that includes Myn 2.2.
Either something went wrong with the flash, which i find highly unlikely, or the rom was corrupted. Do you know for sure that the download finished completely, and that you didnt flash a corrupted ROM? And are you absolutely sure that you flashed a ROM for the evo? I dont particularly like Myn, so im not an expert on it, but are you sure you didnt flash a version not meant for the evo?
But whatever you did, it seems like your boot image is corrupted. Since you can get to the bootloader you should be able to fix any software problem through an RUU or using fastboot to flash a new recovery.
The unfortunate thing is, a lot of people seem to be having this same problem and no software flash seems to be able to fix it.
See this thread: http://forum.xda-developers.com/showthread.php?t=1009672&page=32
The conclusion ive come to, and i am by no means an expert, is that the NAND memory has worn out. Its called Read Only Memory for a reason. NAND flash memories can be written to but theyre meant to be read from and dont take to well to constant writing. Normal use wares out all types of solid state memories, particularly NAND flash memories. If you have too many bad blocks that there isnt enough good blocks to fit the files you need (boot image, recovery image, system image, etc), then no amount of software flashes will fix it because its a hardware problem.
This doesnt mean that this is your problem. I couldnt possibly know that for sure. but if RUU's and fastboot commands do not work your out of luck, and its probably a hardware problem. If you have S-on you can take it to sprint since it wont even boot and they couldnt tell its rooted. Theyll run a diagnostic tool that will tell them how many bad blocks your memory has and probably just give you a new one.
If your phone has S-off i wouldnt take it back to sprint, they wont like that. If the bootloader says S-off (and you cant fix it) your better off buying insurance and "losing" the phone. Keep trying a bunch of different PC36IMG.zip's, some people with this problem have been able to turn their phone from s-off to s-on.

yea after i looked around im becoming more convinced that its bad blocks. Look around the forums about "the white screen of death". Again, i cant be sure at all that this is the problem until you try every software solution. But this problem has just popped up a little bit ago and you have pretty much all the symptoms. I've never seen an evo not be able to boot to recovery after a flash. It simply doesnt make sense since the rom wouldn't have included new recovery or boot images. The only thing that really makes sense is that one unfortunate flash ruined one too many memory cells and the phone no longer has enough free memory to execute the boot files.
in short, fastboot and the bootloader are your new best friends. Are you familiar with fastboot commands?
Also, how old is your phone. Is the hardware version lower than 0003?

[Q] Post Skyraider 4.0 Flash, now stuck on splash screen loop.

I have had my phone rooted for about a month now. I was running CM7 and things were fine and dandy. Decided that I wanted to try a different ROM. Downloaded and installed Skyraider 4.0 today. It seemed to be working fine. It was nice to have some sense back on my phone. Out of nowhere the phone reboots. Now I am left with a phone that cycle reboots and will not even get to the boot animation. Just the HTC Incredible white splash screen...black screen....vibrate....HTC Incredible white splash screen...cycle and cycle and cycle. I am able to get to the hboot screen by pressing the volume down button. From the hboot I tried to get into recovery mode but it goes back to the splash screen cycling.
I tried to reflash a stock ROM back onto the phone through hboot and it said that it was succesful. On restarting though, it went right back to the splash screen cycling.
Any help would be GREATLY appreciated! I have searched and searched and am still stuck cycling with on the splash screen.

So you used the PB31IMG.zip that restores the phone to stock? And you can get into hboot but it wont boot into recovery from there? I'm not really sure what else to suggest, there may be some things that can be done with adb but I haven't ever gotten that far, I'm sorry. Typically the RUU is successful in getting people out of bootloops or other tough spots.
Sent from my ADR6300 using XDA App

k_nivesout said:
So you used the PB31IMG.zip that restores the phone to stock? And you can get into hboot but it wont boot into recovery from there? I'm not really sure what else to suggest, there may be some things that can be done with adb but I haven't ever gotten that far, I'm sorry. Typically the RUU is successful in getting people out of bootloops or other tough spots.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
k_nivesout
Exactly. I used the PB31Img.zip. Hboot cycled through and said that it was successful. I excitedly rebooted thinking that all of my dreams had come true. But I was none-the-better with the cycling issues. I used Doug Piston's method to get the phone to stock.
I am still in S-Off. Would it help to get the phone back to S-On before reflashing to stock or would this make a difference?

I could be wrong but I don't think S-ON would really effect anything as far as flashing the stock rom. How long have you let it try to boot up? And you can't get into recovery from hboot? It sounds like it could be a hardware issue but it seems really strange that it would just quit working like that.
Sent from my ADR6300 using XDA App

I didn't think that S-On/Off would make a difference but I'm desperate for an answer. I have let it cycle through the splash screen....phone turning off....splash screen 20-30 times before realizing that it wasn't getting anywhere. I am able to get to the hboot screen, but unable to get into recovery. I've flashed three different versions of clockwork to see if that might be the issue but no luck there.
I believe that my warranty may have ran out on the phone so I don't know what to do next.

It seems weird that you can get into hboot but not recovery. I'm really not sure what it could be, I wish I could think of something that would fix it.. I was thinking there was a tiny chance that maybe you just weren't giving it enough time to boot but if its looping that many times, its not gonna do it. Have you flashed any radios or anything else that could have possible messed something up? Is your hboot version the latest (.92)? Tried flashing the stock radio (7.28)? I'm really not sure if any of this could help, I'm just trying to think of anything you might be able to try since you can only get into hboot..
Sent from my ADR6300 using XDA App

Never flashed any different radios. I went from stock to CM7 to Skyraider. Hboot version .92. The radio was flashed to stock when I used Doug Piston's PB31IMG.
So now, the configuration of the phone is:
INCREDIBLEXC XC SHIP S-OFF
HBOOT 0.92
MICROP 0417
TOUCH PANEL ATMEL224_16ab
RADIO - 2.15.00.07.28
Jul 23 2010, 18:06:51
I believe that I was successful in flashing the 2.5.1.2 ClockworkMod Recovery onto the phone. I previously had 3.0.0.8 or whatever ROM manager flashed onto the phone for me.
Nothing that I have done has made any difference on getting through the splash screen onto the boot animation.

Everything looks correct as far as stock settings go. I really can't think of anything else to try as my knowledge is limited to things you can do in recovery or in hboot and you've already done everything that I can think of to fix it. The only other thing I can think of is trying some things in ADB, but its been so long since I've used it I couldn't help with it. I'm assuming you've tried all the options in hboot, I think there's a data wipe/factory reset option? I'm sorry, I can't think of anything else, wish there was something I could do! If you got the phone from Verizon, you should have a one year warranty. The incredible came out like 13 months ago so I would think it would still be under warranty?
Sent from my ADR6300 using XDA App

I had the same problem months ago and i used a card reader to read my sd card and install a fresh rom in the root directory of the sd card. Reinstalled the card and flashed the new rom , make sure to erase any previous rom as it was pobably corrupt.
Sent from my PC36100 using XDA Premium App

[Q] Phone won't boot, can't get into recovery.

I've been looking through threads for hours and have tried a lot of what has been suggested. At first it just started randomly bootlooping ( white htc screen, restart). I then tried some guide on a thread that had me ADB then RUU, once that was all done It got to the white htc evo screen, turned black then vibrated 5 times and the green light started to flash. I can't get into the recovery menu, I click it and it just goes straight to white htc screen. I've flashed multiple PC36IMG's with different recoveries, with no luck.
My fuse is burnin low...
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-1.39.00.04.26
APR 14 2010, 15:41:34

*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..

IxHaku said:
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
Click to expand...
Click to collapse
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there

What rom were you running? Some users have had a bootloop of death, no coming out of it, on CM7. I think it has happened on other AOSP roms as well, but you mainly see it on CM7 - probably because of the larger user base.
I have yet to see a solution for it, I think everyone else had to report it lost and pay the $100 deductible through insurance. The only hope is to keep running RUUs and hopefully one will stick.
(from... Evo/MIUI/Tapatalk)

Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though

IxHaku said:
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
Click to expand...
Click to collapse
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.

teh roxxorz said:
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
Click to expand...
Click to collapse
Does it matter which RUU I use? (2.1,2.2)

reverepats said:
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
Click to expand...
Click to collapse
Exactly! Do not worry about flashing a RUU at this time. Click on amon RA in my signature to download the PC36IMG.zip for amon RA and place it on the root of your SD card. Remove any other file with that name. Boot onto the bootloader (simultaneously press the DOWN volume & power button until your device starts) and then follow the prompts to install. Installation should take no more than 10 seconds. Afterwards, enter your new recovery, connect your device to your computer, select the USB-MS option and then copy the contents of your SD card onto a folder on your computer. After that, select the USB-MS option again to disengage. Now go to the wipe menu and wipe EVERYTHING it. When you're done, download a fresh copy of the rom you want to flash and flash it or copy a nandroid backup to your SD card and restore it. Be patient, either way, with the initial bootup.
pecking & swyping from my EVO 4G (XDA Premium)

Alright so I tried everything I could... So I took it into a sprint store. Told the guy this happened when doing the most recent update. Right there he went into the bootloader menu, I thought I was screwed... but he didn't say anything about the S-OFF. Eventually I came back and they ordered me another one.. probably a refurb. He said it was going to be free, and I don't have insurance. Guess I got lucky.
Thanks everyone for the input.