Develop Bugs

[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.

Possible brick on my hands. could use some help.

alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?

PhxkinMassacre said:
alright here is what happened. i was in twrp2 rc0.2 and was flashing a theme .zip made from the zipthemer app. i wiped cache and dalvik and flashed like normal and then after the flash it gave me an option to reboot system. i clicked it and it should have booted into my rom. instead it showed what would have been the white htc evo splash screen (mine is different) and then went to a black screen, vibrated 5 times, and i have the green notification light flashing.
i pulled the battery. booted into the bootloader and tried to go to recovery. ended up doing the same black screen vibrate etc. so i went back to bootloader to try to reflash the recovery since i still had the pc36img.zip on my sd. it scanned for the file looked like it read it but instead skipped past it and never gave me an option to flash the recovery. i tried multiple times, a series of battery pulls and no luck.
anyone got a clue as to whats up? im thinking i have a bad block and i heard of some jtag program or something to fix it but i have no idea what it is or how to use it.
p.s. yes i did google and i didn't find anything of much use... hell of a Christmas huh?
EDIT: odd. i have been rooted since january and now after this started it says im s-on. think i could use an ruu? the sd wont mount and im pretty sure they run from your sd so is there a way of using and ruu from a computer?
Click to expand...
Click to collapse
You can run a ruu through fastboot
Sent from my PC36100 using XDA App

evo4gnoob said:
You can run a ruu through fastboot
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
im downloading a 2.2 ruu. ill get back to you as to if it works or not

ok. i try to run the ruu and it gives me a main-version ERROR so i hit close and disconnect my phone. but then a window pops up saying update. so i plug in my phone again go to fastboot but then fastboot freezes and i cant navigate up and down with the volume keys. i then hit update but it just hangs at rebooting to bootloader and wont do anything...

If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU

HipKat said:
If you can get back to Hboot, try to find a pc36img for the ruu you need and use the Ruu for the phone you have, not just any Ruu.
Use this site: http://goo-inside.me/supersonic/ruu to find your RUU
Click to expand...
Click to collapse
i tried the sdcard ruu for the latest gb update. it goes through. installs everything ok. but then when it reboots it goes back to the same 5 vibrates and black screen with flashing light.
after i did the sdcard ruu the windows ruu was able to go through unlike before. so i plugged in my phone it did its thing successfully. and again to no avail its still got the 5 vibrate etc.
and other options such as a block remap? i was running decks at the time which is based off cyanogen and i heard that cyanogen had been screwing blocks lately...
edit: i have no idea how a block remap would work... i just saw it in a thread that i believe you posted in like 3 days ago or so...

The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.

HipKat said:
The 5 vibrates means it's in maintenance mode. (Diagnostics?)
I'm not sure what that means, exactly, but I don't think you're bricked, however, you DID say you were S-on, I believe, so if you are, try to re-root (look up root method for your hboot version) and them flash a recovery (Prefer Amon Ra) if it is successful.
If that works, wipe everything you can, except SD Card, wipe Dalvik Cache and Cache twice, then flash a ROM.
Click to expand...
Click to collapse
He can't get sd to mount
Sent from my PC36100 using XDA App

ok. i went to a friends house and just let my evo chill out on my desk and when i got back it booted right up since i got 1 successful ruu in. now that being said it only stays up for about 3 minutes and then shuts off and goes into the vibrate and blink stage so im gonna try a logcat and see if i can get anything useful out of it. there is some hope here boys

ok. i have tried ruu 2 more times. i tried to root a few times. all to no avail. nothing works. i still turns on for only 3 minutes at a time and then goes blank and vibrates.
my device is less than year old but i didn't get a warranty so does anyone know what the deal is with getting a replacement? my bootloader says s-on and its on a stock rom due to the 934759345734 ruu's i did so they won't know i was rooted. so is there like a 1 year manufacturer warranty for this without having to break out $100?

Best bet is to just call Sprint and find out. They may just offer you a trade in.

[Q] Bricked Evo, have tried many things and out of ideas

Background:
I have an Evo 4g of my own that I have rooted / flash custom ROMs all the time, etc. so I am not unfamiliar with the processes BUT:
I was given a stock Evo that supposedly froze on an OTA update and had been stuck in a bootloop ever since. Over the course of several days I have tried various methods to flash new recoveries etc. with very little luck, but I am making progress, I think I am still missing something.
I have read several places that if I can access the bootloader all is not lost, but I am losing hope.
Phone Status:
*** UNLOCKED ***
SUPERSONIC EVT2-3 SHIP S-ON
H-BOOT 2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
DEC 21 2011, 12:50:32
Enable USB Debugging OFF - Nothing I can do about this??
Things I have tried / Results:
Standard Recovery (from boot loader) - Sends device into boot loop.
PC36IMG - I have flashed back to newest stock and it seemed to be successful but no change in behavior... I have since tried to use this method to flash the recovery but it fails every time seemingly no matter what recovery I use.
HTCDev - Successfully unlocked bootloader
Fastboot - Flash recovery (amon ra and clockwork) / FAILED (remote image update error) - I have tried several recovery.img files with same result.
HTC Super Tool: Prep uising ZergRush seemed to be successful, Attempt Perm Root - Hangs forever.
ADB: ADB does not find device.
UnrEVOked3: Does not find device.
H-Boot Drivers successfully installed
HTC Sync is uninstalled, no antivirus or anti-malware on (win7 x64)
RUU - Connection Error 170 every RUU every time.
Thoughts:
I appreciate any help and if I can provide any more information useful let me know. Remember this is stuck in boot loop so as far as I know there is no way for me to turn on USB debugging.
The device connects to my computer successfully in both H-BOOT USB PLUG and FASTBOOT USB. fastboot device command finds device, adb device command does not.
I am not too desperate to get this device working, I will be using it to test ROMs before installing them on my "production" phone, and I am not worried about permanently killing it because it was free and if nothing else I can use it for parts. (TLDR: I am willing to try risky fixes)

sounds like what happened to my old evo to an extent. do you know if that device happened to be running twrp 2.0 recovery before the bootloop? because if so, it is un repairable. twrp on a select bunch of devices messed up the internal nand and messed up the memory blocks to the point of no repair. the closest i came to a fix was through like 7 ruu's. it eventually caught and then booted up but would only stay on for 2min 15seconds on the dot consistently. also when it freaks does it happen to go to a black screen and vibrate 5 times? because that was another thing mine did.

Thanks for the reply, No the phone was completely stock before the OTA failure, the guy I got it from knew nothing about the phone, I just happened to be doing a network install at his house and he saw mine and asked if I wanted it for spare parts. I asked if it was rooted and just shrugged and said it was just like he got it from Sprint.

PhxkinMassacre said:
sounds like what happened to my old evo to an extent. do you know if that device happened to be running twrp 2.0 recovery before the bootloop? because if so, it is un repairable. twrp on a select bunch of devices messed up the internal nand and messed up the memory blocks to the point of no repair. the closest i came to a fix was through like 7 ruu's. it eventually caught and then booted up but would only stay on for 2min 15seconds on the dot consistently. also when it freaks does it happen to go to a black screen and vibrate 5 times? because that was another thing mine did.
Click to expand...
Click to collapse
If this is the truth, the cheapest option is to order a new motherboard from a good source for the EVO. Otherwise, you are stuck with having to dish out $200+ for a new phone.
Sent from my PC36100 using XDA

Again, no custom recovery has previously been flashed.

ratchetandclankf said:
If this is the truth, the cheapest option is to order a new motherboard from a good source for the EVO. Otherwise, you are stuck with having to dish out $200+ for a new phone.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
nope since it was s-on because magically from twrp when it fried my stuff it went s-on when i brought it to sprint because of the ruu it looked stock they claimed it as a manufacturer fault and gave me a replacement for $37
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
cartmage said:
Again, no custom recovery has previously been flashed.
Click to expand...
Click to collapse
his suggestion is still valid. if there was an error during an ota then its most likely dead for good. so either get a new board or see if you can get it replaced by sprint.

Ok, Thank you for the advice, I will keep that in mind.
However, now that we have established that it had nothing to do with TWRP, and that I should just give up and replace the hardware, are there any ideas from the development aspect? Remember this phone is just a spare freebie so it is just a pet project and it was never mine so Sprint isn't even remotely an option. I will not put any money into the phone, but I will time. That being said;
Here is some more info from the past couple hours:
I finally got a custom recovery (clockwork) to flash onto the recovery partition via fastboot:
Code:
fastboot flash recovery recovery.img
-OKAY
~Still wouldn't boot into recovery so then
I used:
Code:
fastboot boot recovery.img
to reboot into clockwork recovery from the image on my PC... after picking up my jaw from the desk in surprise that it worked, I wiped everything, then flashed CM7 Stable ROM and rebooted... (I know the ROM is good because I have the exact file I used running on my phone currently.)
Still no love, back to bootloop.
The fact that I got it to boot into a recovery (sorta) and did a successful flash from zip gives me new hope, it just seems there is something between the bootloader and the system that is borked...
Also, it seems like I should be able to connect with ADB even without USB Debugging on if that is just a setting in the OS and I am doing most of this below OS level? Or does ADB require a functional OS?

Update:
I finally got the phone to boot but as soon as it completely loads the OS it reboots. I am beginning to think it is an actual hardware issue or that part of my file system is corrupt.
Does anyone know of a way to clear and rebuild the file system?

ratchetandclankf said:
If this is the truth, the cheapest option is to order a new motherboard from a good source for the EVO. Otherwise, you are stuck with having to dish out $200+ for a new phone.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
PhxkinMassacre said:
nope since it was s-on because magically from twrp when it fried my stuff it went s-on when i brought it to sprint because of the ruu it looked stock they claimed it as a manufacturer fault and gave me a replacement for $37
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
his suggestion is still valid. if there was an error during an ota then its most likely dead for good. so either get a new board or see if you can get it replaced by sprint.
Click to expand...
Click to collapse
bandbrain said:
Whenever I ran the first command in terminal emulator I would get a “Cat/sdcard/flash_image: not found” the same thing with "mtd-eng.img" this is starting to frustrate me because I cannot find a fix for the USB, which is causing my phone to boot then vibrate 5 times right after splash screen.
Click to expand...
Click to collapse
kalehua4791 said:
Make sure you unzip the file to your sd card first which will actually make a flashable image......i use win rar to unzip files.....try that and see ...then try again in terminal emulator.....
Make sure you are rooted or this is for naught.....peace
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Did you ever get this fixed with the phone shutting down? I just had that happen with one of my other phones and it took me 3 days to figure it out.....had to upgrade the hboot to 2.18 then root using the new root method from htcevohacks.com and then down grade after that.....i did have root before this so don't understand why this happened in the first place....after that had to use fastboot again to have computer see card and then had usb fixed with the method here.....ALL WHILE PHONE WAS PLUGGED INTO COMPUTER......HOPE THIS WORKS FOR YOU!!!!!
Sent from my PC36100 using xda premium
Sent from my PC36100 using xda premium
Sent from my PC36100 using xda premium
Sent from my PC36100 using xda premium

[Q] S-ON, invalid recovery/system partitions, boot loop, bricked device?

Hi all,
Was attempting to root my desire HD and install CM7. Somehow, I managed to screw up the phone. I was using ACE so at some point I had root, and was able to flash different partitions (which is where I screwed up). Here are the facts:
1. Phone boot loops
2. There's no working recovery partition (I manually flashed that when I did have root), and a completely busted system partition
3. the phone is still S-ON (not sure how this stayed this way) - which means I can't fastboot
I tried downloading and installing the stock ROM, and it loaded, and installed - but then neither 'recovery' nor 'factory reset' do anything. Both still lead to boot loops...
From researching the web, I understand that:
1. If I don't have S-OFF - I can't fastboot, and even the PD98img.zip won't install
2. I can't get S-OFF without having a working system first (either via HTC's tools or some root'ing app).
Am I SOL, or does anyone have ideas of what I should try?
thx.
Blake

http://forum.xda-developers.com/showthread.php?p=31722797
Post#7, it may help.
Sent from a dream.

You haven't tried running an RUU yet? It restores your phone to factory state. Best way is to flash an RUU and start over with the Advanced Ace Hack Kit. I'm pretty sure you didn't read the manual properly and follow it word for word. By RUU I don't mean the PD98IMG.zip, I mean the exe file. Connect your phone to the computer and run the exe.
http://shipped-roms.com/download.ph...60.29_26.14.04.28_M_release_225512_signed.exe

sashank;31725074]You haven't tried running an RUU yet? It restores your phone to factory state. Best way is to flash an RUU and start over with the Advanced Ace Hack Kit. I'm pretty sure you didn't read the manual properly and follow it word for word. By RUU I don't mean the PD98IMG.zip, I mean the exe file. Connect your phone to the computer and run the exe.
Click to expand...
Click to collapse
I tried - but i got the 'failed to communicate with your phone, make sure USB is connected and phone is in debug mode'...As I understand it, running the exe requires that phone to be in a working state. I only have hboot now...
Am I mistaken?

In hboot, press power on fastboot. When FASTBOOT shows up in a red background, then connect it to the computer and try running the RUU.

If that doesn't work download the htc sync (drivers). You need to switch of the antivirus before installing. The program will prompt you before.
Sent from a dream.

Teichopsia said:
If that doesn't work download the htc sync (drivers). You need to switch of the antivirus before installing. The program will prompt you before.
Sent from a dream.
Click to expand...
Click to collapse
Ok - I managed to get the right RUU from shipped-roms, and I used it to flash the ROM. It took a few mins, and then told me that it was successful.
However, I'm still stuck in a boot loop...
Any ideas?
Blake

Thanked you by mistake. Tell me, how long are you waiting after turning on the phone before considering it to be boot looping? For any ROM, the first boot always takes time. Not too long, but a few minutes. In that time it will just show the HTC splash screen. This happens because the dalvik-cache has to be built and the time it takes depends on the number of apps. Maybe I'm wrong, but I think you're assuming too soon that it's bootlooping. Wait for some time and see.
Sent from my Desire HD using xda premium

sashank said:
Thanked you by mistake. Tell me, how long are you waiting after turning on the phone before considering it to be boot looping? For any ROM, the first boot always takes time. Not too long, but a few minutes. In that time it will just show the HTC splash screen. This happens because the dalvik-cache has to be built and the time it takes depends on the number of apps. Maybe I'm wrong, but I think you're assuming too soon that it's bootlooping. Wait for some time and see.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
The phone boots, I see the white screen with the HTC logo, then a few seconds later, it reboots, and I get the same logo, and so on, and so forth...It just keeps on rebooting, even though the RUU worked.
thx.
Blake

blakey1 said:
The phone boots, I see the white screen with the HTC logo, then a few seconds later, it reboots, and I get the same logo, and so on, and so forth...It just keeps on rebooting, even though the RUU worked.
thx.
Blake
Click to expand...
Click to collapse
Any ideas, anyone?
B.

Try booting without the sd card.
Sent from a dream.

blakey1 said:
Any ideas, anyone?
B.
Click to expand...
Click to collapse
That seems to be a bad emmc chip. Many devices suffer from that.
Sent from my GT-N7000 using xda app-developers app

blakey1 said:
Hi all,
3. the phone is still S-ON (not sure how this stayed this way) - which means I can't fastboot
Click to expand...
Click to collapse
This is not true. I have still S-ON (but unlocked via htcdev.com) and I can do fastboot, flash recovery etc. But flash works only from fastboot menu, not from running system or recovery mode.