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] Recovering from unusual boot loop

Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.

jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.

RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?

jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there

I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.

This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719

RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.

jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.

jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.

[Q] Bricked if I cannot reach recovery?

Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!

Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.

Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk

Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]

Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone

Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk

popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon

hope that helps

@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk

popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.

popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.

Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.

That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk

You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked

I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad

Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.

Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.

I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.

popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?

[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.

[Q] Boot Loop Help, even tried flashing back to stock Un-rooted

Initial Phone Details:
S-OFF
HBOOT .95
Virtuous 3.2 running since dawn of time,
4.08 radio (flashed 9 days ago)
CM 3.0.0.8
It Started:
In the middle of downloading Market updates … bootloop at the droid red circle
I tried:
- Remove battery, wait five min ... bootloop at red circle
- Nandroid restore of recent backup … “failed to format /data” (three attempts)
- Wipe data/factory reset, clear cache, clear dalvik, clear battery stats … failed nandroid (twice)
- Flash Virtuous (after full clears) … bootloop at red circle
- Flash Skyraider (after full clears) … bootloop at twirling Skyraider logo (twice)
- Flash stock-rooted rom (after full clears) … bootloop after red circle (twice, once with original SD card, another with a different card, freshly formated FAT32 and only the ROM image)
- Flash stock-UNrooted 3.21.605.1 rom (after full clears) … bootloop after “DROOOID” (two times)
Now of course I’m sitting at S-OFF, Stock Unrooted NOV ROM, 7.28 radio and stock recovery. I could still get into Recovery before I flashed unrooted (obviously to need to reroot again when I get home from work). I can still get to HBOOT. By every measure I have I should be able to get out of this situation sans-brickage, but I’ve exhausted my toolbox.
Well Ok I suppose I haven’t tried an RUU flash yet nor going back to S-ON but really are those even likely to make a dent?
What do I try now?

Try everything. If the RUU is the only thing left then do that. And S-ON. I would have done that before flashing the stock unrooted. I don't know if these will work, just giving my 2¢. Hope you figure this out.

Were your nand backups made with 3x clockwork? Or a 2.5 version?
Sent from my ADR6300 using XDA App

silverxbv2 said:
Were your nand backups made with 3x clockwork? Or a 2.5 version?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
3.0.0.8 ... took the phone to verizon, they are now sending me a replacement.

Would love to know what phone they send you for the refurbished one
Sent from my ADR6300 using XDA App

jumperalex said:
3.0.0.8 ... took the phone to verizon, they are now sending me a replacement.
Click to expand...
Click to collapse
bud that coulda been fixed easy

jumperalex said:
3.0.0.8 ... took the phone to verizon, they are now sending me a replacement.
Click to expand...
Click to collapse
What happened was somehow you corrupted your data partition so in turn you could not format data which caused the bootloops.... coulda fixed it 2 ways the hard way is using parted through adb and the easy way would be just to flash an RUU and reroot.... but I guess getting a new phone works to
Sent from my ADR6300 using XDA App

I'm listening.
The phone is still here until I send one of them back and my new phone arrives tomorrow.
So let me add some more info. I am now unrooted with S-OFF. I can't boot and despite my best attempts I can't find how to re-root without a fully booted phone. When I try to use unrevoked in hboot/fastboot it says it is still waiting for the phone to connect. I assume this is becaues according to the instruction I need to be in USB debug mode, something I can't do if I can't boot to the OS.
I have the hboot drivers installed in Win7 and show the phone in device manager as "Android Bootloader Interface" I tried adb and I couldn't seem to connect to the phone while in hboot/fastboot. But I'm going to try a few other things after I post this ...
I'd love to get this phone up and running just in case the new phone is SLCD and I decide I don't like the SLCD. My current phone is AMOLED.
So how do I flash RUU. That was what I was going to try to do but couldn't find a way to do it.

PS oh yeah and I tried running HTC Sync to install the RUU file that way and HTC Synch doesn't see my phone in bootload/fastboot which isn't much of a surprise.

still can't get adb to connect. it just tells me there are no devices connected. my computer sees the phone, the phone says "fastboot usb" or "hboot usb plug" depending on which I'm in of course.
oohhh kay ... I accidentally sent myself into recovery (stock not CM since I already tried pushing an unrooted image to solve my issue) and NOW adb says the device is connected but offline

jumperalex said:
still can't get adb to connect. it just tells me there are no devices connected. my computer sees the phone, the phone says "fastboot usb" or "hboot usb plug" depending on which I'm in of course.
oohhh kay ... I accidentally sent myself into recovery (stock not CM since I already tried pushing an unrooted image to solve my issue) and NOW adb says the device is connected but offline
Click to expand...
Click to collapse
You on here?
Sent from my ADR6300 using XDA App

yup i'm on here

doh ... did you send me a gtalk request?

any updates to this my phones basically in the same position. However ive tried doing the ruu.exe and ruu in pb13img.zip update and those didnt work now im looking for instructions as how to get adb to see my device to try the parted portion to see if that solves my issue.

[Q] Bootloop of Death...

Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated

tropicalbrit said:
Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated
Click to expand...
Click to collapse
have you attempted to reflash recovery?

Had this happen the other day and pulled battery and then held power button and volume button down and it went right into Recovery... 1st time ever for me

Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying

Give it some time some times after a crash/hotstart takes a little longer..
Sent from my EVO using XDA App

tropicalbrit said:
Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying
Click to expand...
Click to collapse
Tried a ruu yet?
Sent from my PC36100 using XDA App

evo4gnoob said:
Tried a ruu yet?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.

tropicalbrit said:
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.
Click to expand...
Click to collapse
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP

No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....

evo4gnoob said:
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP
Click to expand...
Click to collapse
Nice of you to think of me!
Umm, yeah . . . my problem was a little bit different, as I was still able to boot into a ROM. So, any suggestions I offer here will be purely theoretical. But, perhaps the same fix will apply. Maybe the misc partition needs to be "reset"? Since you have access to fastboot, we'll need you to flash a bootloader version where fastboot commands will work. Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Put the mtd-eng.img in the folder with fastboot and open a command prompt. Navigate to that folder and issue the commandEDIT: I just tried this and it didn't work. I think you're going to have to go with the above method . It was a good ol' college try, I guess.
Code:
fastboot flash misc mtd-eng.img
It should flash successfully, since you're S-OFF. Once that's done, try rebooting the bootloader, and see if you can get into recovery.
The mtd partition seems to be the thing that messes everything up, so I figure that's the best place to start and see if it's that easy to fix .
EDIT: I guess if the above doesn't work, HipKat's method will be the next thing to try. I don't envy you if you have to try that . . .

Captain_Throwback said:
Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Click to expand...
Click to collapse
I get the error attached below in attachments, fails to write. I am up to 2.18.0001 HBOOT S-OFF with the HBOOT you included
HipKat, the RUU is downloading. The Evo Softbrick.zip link you have in there leads to me to: "The file link that you requested is not valid."

very simple
reflash by doing adb push update update.zip then format sd
by adb mount/sdcard
then adb erase sdcard
then do fastboot flash update update.zip
erase all data
then should be good to go.....
thats how i fixed mine

HipKat said:
No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....
Click to expand...
Click to collapse
I just ran the RUU, that is all I've done because of the down link. I'm now at 0.79.0000 HBOOT S-OFF with 1.39.00.0426 radio. Now whenever I turn on my phone it goes straight to bootloader. Entering recovery gives me 5 vibrations with notification light blinking green
Edit: It no longer goes to bootloader whenever I turn it on. It gives me 5 vibrations with blinking green notification light. Still have access to HBOOT

That means it's in maintenance mode. As for that document, it's s few months old.maybe you can do a search for that missing file.
Swyped From The Hippest MIUI'd phone Using XDA Premium

I now have HBOOT 2.10 ENG S-OFF (Hex-edited one from here). So I have fastboot command capabilities. Trying to flash mtd-eng.img gives me the attached error.
Going to start searching for that file. I have fastboot capabilities, so I think I need the nv.img so it's time to go hunting
Edit: So I had HBOOT 2.10 ENG S-OFF. I followed the document HipKat posted, was unable to erase nv, microp, and radio. I flashed nv.img, then I ran the RUU again.
Back to .79 HBOOT S-OFF. Turning the phone on vibrates it 5 times and flashes green light. No access to recovery either.
Starting to think we are out/almost out of options... Guess it is time to start talking about getting S-On with somewhat recent HBOOT and radios.

you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it

HipKat said:
you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it
Click to expand...
Click to collapse
I can still access HBOOT, however. I have a couple of friends at the local Sprint store (due to a Samsung Intercept for my sister - worst phone ever). The problem is, several of the managers there check the HBOOT. They've checked it in front of me (I had S-On) and for recovery on the Intercept. When I asked why they checked, they said they support repairs but not replacements (could go through Asurion) with rooted devices.
Sent from my SPH-M900 using xda premium

Wow, that's the first time I've seen that someone at Sprint checks for Root.

HipKat said:
Wow, that's the first time I've seen that someone at Sprint checks for Root.
Click to expand...
Click to collapse
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.

atapia984 said:
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.
Click to expand...
Click to collapse
I've seen so many posts about Sprint doing updates without consent. If you ask them to not do the update, they ask questions.
Well, I shall search for a way to get S-On with no access to recovery; I'll continue flashing to see if I can get something to stick before that though. My fallback plan is a Samsung Moment I have sitting around...