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] 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] Unique problem(Stuck at splash screen.Cannot get into recovery mode, only Hboot

I thought I had it all figured. Root, with Clockwork Recovery, Rom Manager. Nothing could go wrong. Now I am stuck at the splash screen with no Clockwork Recovery.
I searched fourum after forum to find a solution, but mine seems to be different. Just so you know I am 21, and a freelance computer technician so I am not afraid of the command line
What have I done to my device:
=Originally it had 2.1
=I rooted the phone via exploid method
=I installed CyanogenMod 6.1.1
+My computer only recognized my phone in HBoot mode, I think usb debugging is turned off though because I cannot acces my sd while it is in my phone.
I do have a microsd card reader
+I tried Esprimg.zip updates. It works .but I still cannot get into recovery mode.
For extra precaution, I backed up all of my sd card data on my pc.
Symptoms and problems:
+I am stuck at the white My tough slide 3g splash screen.
Holding up and power for at least 30 seconds does not get me in recovery mode. All I see is the white My tough slide 3g splash screen. No Black screen with a triangle(Biggest Problem)
+Holding down and power does get me into the HBoot.
+The recovery option will make the Mytouch slide reboot, but it will freeze at the splash screen.
+The clear storage option executed, but it did not solve my problems.
+I have also removed the battery, sim, and sd card.
Summuaray-
I need to get Into Recovery mode, but when I press up and power it does not work. I only see a white.I never though there would be a day where I could not get into recovery.
Also, I constantly charge the device so it wont turn off during an update.

Do you have S-OFF? If you do it should not be hard to recover.
If you don't I can't think of any other method now. But just to make sure which Esprimg.zip method did you tried? Because that should work in the first place.

Mine says S-On
Esprimg.zip
I used my microsd card reader to put esprimg.zip on the sd card. Boot the device while holding down and power. I let the phone check for the esprimg.zip and then the update was successful.
Conclusion:
I hold up and power and i cannot access recovery mode.
Possible causes:
By doing the clear storage, would that change my device to s-on. Honestly I never noticed s-on until now. However, I was able to root and get clockword mod 6.1.1 and it ran smoothly for a weeks.

darko4 said:
By doing the clear storage, would that change my device to s-on.
Click to expand...
Click to collapse
No. Only by flashing another bootloader will you get S-ON back. You probably did not have S-OFF before anyways but FYI Esprimg.zip does flash the bootloader so you're stuck on S-ON for now.
If the Esprimg.zip update method was successful it should have flashed back the stock recovery for you. I can't think of anything that could go wrong at this point except that u have a bad or corrupted Esprimg.zip. Did you use the champion build or the ENG build? If me I'd try to download it again and give it another go.
Good luck!

Ok so Esprimg.zip may be bad, and pretty much that is my only saviour;ok I understand.
I was using Esprimg.zip from other guides. Those were 137 mb
This time I used the one from here.
HOW-TO * Flash the Eng-Release to the Slide *6/15/2010
http://forum.xda-developers.com/showthread.php?t=703076
I am going to assume this the the eng build. It was 137.1 mb.
If this does not work the I guess I have to go champion build.
------------------------------------------------------------------
Failed
Champion build esprimg.zip is next.
A few more ideas.
manually install the recovery using fastboot.
troubleshooting without simcard?
My spl s-on so would that be possible?
Is there a way to maybe re root?
I read in one post that a guy sold it on ebay..i would hate to do that with just a month of ownership. would Htc make a warranty request even though I bought it used. Besides you only see bootloader and hboot spl s-on so how could they tell?

So you reach the screen where it asked you whether you want to install the update, you choose "yes" and it goes on to flash everything, radio, bootloader, yada yada, and it fails to boot?
Basically with S-OFF you can boot into fastboot and run
fastboot flash recovery recovery.img
in this case recovery img is CWM recovery. With S-ON fastboot flash is disable so it's not possible.
EDIT: If you do have the champion build on it's basically stock.

I have this exact same issue right now, I've tried the champion and engineering builds of ESPRIMG but with no success. I can't think of anything else that would be causing this in the first place, which is making it so difficult to troubleshoot. The only difference is that I was using CM7 instead of 6, but the exact same thing is going on. I have tried everything that the OP has with no luck. The only possible cause I can think of is that something was somehow corrupted while the phone was on and sitting on my table...because when I picked it back up, it was off and when I tried to boot, I got splash screen... Any other ideas?? I'm all out and just sitting here waiting for some genius light bulb to go off....attic's kinda dusty though..

With S-ON fastboot flash is disable so it's not possible.
So basically these are my options
esprimg.zip (if that does not work then use different)
Hboot clear memory,
with S-ON I have limited option
and keep it charged.
Although with fastboot and s-on is there something I could do?
Would rerooting be an option

darko4 said:
Would rerooting be an option
Click to expand...
Click to collapse
I don't see a root method in the forum that does not involve booting into a usable system.
Wait, you guys were able to flash the esprimg.zip right? Because in the guide when it says it requires root it's for flashing the mtd0.img first before rebooting into HBoot. Since you don't have a working system you cannot do that and if HBoot refuse to take your esprimg.zip then you need to do the Goldcard method. Otherwise I don't see why having root will make a difference.

So at this stage of the game I should do this..
1.get on my knees
2.put my hands together.
3.and just pray?
ok all jokes aside. Continue to try Esprimg.zip and update(all are successful but I still get splash)
I can't change my recovery since I have s-on
and no way of getting s off since i cant get in the phone, not even recovery,just h boot
So in a sense i have a lovely soft bricked mytouch 3g slide.
Later I might compose a list of the programs i had on the device, but i doubt that would make a difference. I appreciate the help and assistance, I am going to click the thank button for you gents.
In the mean while i got a tmobile comet for 136 one day shipping..No rooting on this one cause finals are coming and I do not have time to troubleshoot for hours. I love android cause of custom roms, but not being able to get in recovery mode...ah say no more. I am going to be one of those people who just downloads free software and complain to phone carriers about OTA.

Same here. I held off rooting and all until my exams were over because I know I'm going to go all the way until I get S-OFF.
I know many discourage S-OFF because it can potentially brick during the process but if you do read up and follow instructions very carefully it is really not that risky. And it'll be very useful in situations like this.
I'm sorry to hear you have a soft-brick. Maybe a dev will stumble upon and provides new insights but I afraid this is all we have in the forum for now.

to be honest i skimmed through the post, and im sure you did try this but just want to ask have you tried the official RUU update to see if you can get things back up running that way?

yeah I understand following directions carefully, but when you follow all of directions and get it working,and make backups, but then you turn the phone off and then turn it on. Then all of this happens.
ah let me stop my whining and download more esprimg.zip .
I just want to know what caused it. was it an application, cause if that is the case then I want to know so no one else get hurt.
(one interesting note, avg antivirus said my device was infected with viruses. It said with the apps, I did not clean it. i uninstalled avg. I presumed it was a false alarm cause the phone is rooted with applications with high privileged) Oh well
---------------------------------------------------------------------------------------------------------------------------------------------------
oh well. back to the esprimg.zip
never tried RUU, if it comes in a esprimg.zip then i guess i can try. if not then i do not know how to use it with mine in its current state
S on (so no advanced fast boot options
Hboot only
no recovery.
clear memory
only productive thing is successful esprimg.zip updates

its the official update to froyo, and need HTCsync and the RUU from htc how the installs procces goes i dont really know, but im sure there is a RUU update that you can use to update via bootloader,

ok i got htc sync
and the official exe.
my pc only detects the device in hboot. The device will read usb hboot.
1 might fiddle around for 20 mins to see whats what.
.
If it was like a esmprimg.zip then it would seem more feasible.

goood luck hope you get your phone back up and running

well a week ago it finally booted. I felt that it was a fluke so I pressed the power button to reboot. I tried to turn it back on then it was stuck at the splash screen.
I am now starting to think it is a hardware problem. Either way the unrooted tmobile comet,yes it is small, is doing wonders. The battery life is way better then a iphone 3g.
Just remember guys, if you get an android phone, make sure it is a popular one. That way you are more likely to get support because of the bigger fan base. Oh well it was fun while it lasted. The only thing I hate is that i could have gotten an xbox 360 for the same price. oh well, thanks for the assistance. i will lets you know any further updates.

[Q] I think i bricked my evo, (Tried downgrading hboot) help please!

Hello everyone. Let me start off with saying that i had rooted my evo a few months ago and I love all the possibilities that opened up when i did so, but last week i think i made a mistake while doing something
I had read around about how snap turbo 7.6 could get you quadrant scores of around 2,000 and wanted to see this for myself. I tried snap turbo on Cyanogen 7, even though it was made for cyanogen 6, and already the quadrant scores shot up to over 1,500! But unfortunately, because it wasn't intended to be used on Cyanogen 7 there were problems i couldn't overlook, which made me decide to flash Cyanogenmod 6.
After trying to flash Cyanogenmod 6, i found out i couldn't flash it unless i downgraded my hboot menu (which was running at 2.10) down to .97. So i tried the method listed here http://forum.xda-developers.com/showthread.php?t=883548 and that is what caused the problem.
That method made it so that my evo whenever it starts up goes directly into fastboot. I can use the fastboot commands, and i can go into bootloader, but i can NOT go into recovery, and an attempt to do so lands me right back in the fastboot menu. And even though i can use the commands in the fastboot menu, it always says that whenever i try to flash a new rom, kernal, anything via a PC36IMG.zip file or fastboot commands, it always fails.
Any help on the matter would be highly appreciated. Thanks!

i hate to say it, but that probably wasnt the smartest move.
btw, for next time, you just need s-off, not neccesarily a downgraded hboot.
if you are still s-on, you should be able to have sprint fix it up because of your little 'upgrade' mishaps.

You try a RUU?
Fyi quadrant scores mean nothing, absolutely nothing. Worthless I'm trying to say.
At this point you just need your Evo to work again. Grab the 3.70 RUU from the thread in dev that lists them and try running it from a Windows pc

princecharmin12 said:
Hello everyone. Let me start off with saying that i had rooted my evo a few months ago and I love all the possibilities that opened up when i did so, but last week i think i made a mistake while doing something
I had read around about how snap turbo 7.6 could get you quadrant scores of around 2,000 and wanted to see this for myself. I tried snap turbo on Cyanogen 7, even though it was made for cyanogen 6, and already the quadrant scores shot up to over 1,500! But unfortunately, because it wasn't intended to be used on Cyanogen 7 there were problems i couldn't overlook, which made me decide to flash Cyanogenmod 6.
After trying to flash Cyanogenmod 6, i found out i couldn't flash it unless i downgraded my hboot menu (which was running at 2.10) down to .97. So i tried the method listed here http://forum.xda-developers.com/showthread.php?t=883548 and that is what caused the problem.
That method made it so that my evo whenever it starts up goes directly into fastboot. I can use the fastboot commands, and i can go into bootloader, but i can NOT go into recovery, and an attempt to do so lands me right back in the fastboot menu. And even though i can use the commands in the fastboot menu, it always says that whenever i try to flash a new rom, kernal, anything via a PC36IMG.zip file or fastboot commands, it always fails.
Any help on the matter would be highly appreciated. Thanks!
Click to expand...
Click to collapse
Try fastboot devices. If you get 123456789012, your screwed for sure. Turn it in
Uncle Jimmy says hello

dkdude36 said:
i hate to say it, but that probably wasnt the smartest move.
btw, for next time, you just need s-off, not neccesarily a downgraded hboot.
if you are still s-on, you should be able to have sprint fix it up because of your little 'upgrade' mishaps.
Click to expand...
Click to collapse
Actually i have s-off, and i tried taking it to sprint but they said there was nothing they could do.
I've also tried an RUU, but it always fails when i try and flash it either as a PC36IMG.zip or via fastboot commands.

snandlal said:
Try fastboot devices. If you get 123456789012, your screwed for sure. Turn it in
Uncle Jimmy says hello
Click to expand...
Click to collapse
Seriously? Because that's exactly what i get. Dangit! Oh well, guess i'll just have to get a new one. Thank you guys for replying so quickly!

yea next time i woudn't do that. quadrants mean nothing, and you'll perform better on cm7 w/ tiamat than cm6 w/ snap turbo any day of the week. either way, i may be wrong, but you just need s-off (i think) not an engineering hboot.

princecharmin12 said:
Actually i have s-off, and i tried taking it to sprint but they said there was nothing they could do.
I've also tried an RUU, but it always fails when i try and flash it either as a PC36IMG.zip or via fastboot commands.
Click to expand...
Click to collapse
S-off and it won't let you flash a PC36IMG? What does it say when it fails?

i kno i saw an experimental partition fix somewhere around here. will require some hard coding to get, but you might be able to get ur evo back up and running again.
the problem is your partitions are messed up. that's why nothing will install. fixing them might help you out.

here's my best effort at saving you. i'm attaching 2 zips to this. one is the 2.10 hboot. i whipped it up using calkulin's hboot.img. no reason it should flahs, but try it. rename to pc36img.zip, and put it on the root of ur sdcard. try to flash that through hboot. if it works, fantastic. rename and flash recovery.zip, flash a rom from recovery, and boot. if not:
try flashing recovery.zip first. that's a fix broken recovery zip made by zikronix. if it flashes successfully, then try booting into recovery. if that works, flash a rom, and boot up. if not, try flashing the hboot zip i attached. if none of that works, then idk i think you're out of luck.

Incredible won't boot into CM7 or Recovery

I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?

This is a known issue. This happened to my phone and 2 subsequent replacements before I got one that it didn't happen to.
I'd call Verizon or take it in - hopefully you're still in your warranty.

thumpernc24 said:
I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?
Click to expand...
Click to collapse
If you can get into hboot. you should be able to RUU to stock and re root.

synisterwolf said:
If you can get into hboot. you should be able to RUU to stock and re root.
Click to expand...
Click to collapse
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?

thumpernc24 said:
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?
Click to expand...
Click to collapse
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on

synisterwolf said:
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on
Click to expand...
Click to collapse
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!

In order to get s-on you will need a custom recovery installed and then use the s-on tool provided by unrevoked. So you will need to flash a custom recovery thru hboot and then flash the s-on tool thru recovery, and then ruu either thru hboot with a PB31IMG.zip, or with a ruu.exe with your pc. You can get the recovery image and ruus from here http://www.pvillecomp.com. You can get the s-on tool from the unrevoked forever site.

thumpernc24 said:
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!
Click to expand...
Click to collapse
same way you got it off.
unrevoked.com has this info see link below. i also quoted the area you need to look but read it all please.
http://unrevoked.com/rootwiki/doku.php/public/forever
Installation Instructions
To install unrevoked forever on your phone, perform the following steps.
If your phone does not already have a custom recovery, use unrevoked3 to root your phone.
The installation process cannot take place if the phone does not have a custom recovery installed.
Download the most recent ''unrevoked-forever.zip'' to a temporary location on your computer.
The update can be installed like any custom .zip file. Simply flash it from your custom recovery. Both Amon_RA and Clockworkmod Recoveries support custom .zip installs from the sdcard.
Either select the option to install a .zip from your SD card, or apply it as an update.zip as follows:
Place the update.zip file into the root of your SD card. You can do this with adb with the command: adb push unrevoked-forever.zip /sdcard/update.zip
Reboot your phone into recovery mode. You can do this by removing your phone's battery, holding down the VOLUME DOWN button, and inserting the battery; at the menu, press VOLUME DOWN to highlight recovery, then press POWER to select it.
Did you read the important safety information above?
Do so now before continuing.
Select apply sdcard:update.zip from the menu.
Press VOLUME DOWN until Yes is highlighted, then select it.
Review the output to determine if there were any errors.
If messages beginning in E: appear, stop! If possible, join IRC for support.
Restart the phone normally, then reboot the phone into the bootloader. This can be done by holding VOLUME DOWN while powering the system up. Observe at the top that S-OFF appears.
Optional, but recommended: show your support (and your S-OFF bootloader) by flashing a custom splash screen!
"How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update."
---------- Post added at 12:10 PM ---------- Previous post was at 12:01 PM ----------
i also found this video for you. i hope it helps.
http://androidforums.com/incredible...ideo-howto-unroot-incredible-downgrading.html

I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say

thumpernc24 said:
I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say
Click to expand...
Click to collapse
So you can get into hboot and your s-off, but you cant get clockwork recovery to flash as a PB31IMG.zip? What does it say when it auto searches for the file? You say you cant get into recovery, what exactly happens when you select recovery in hboot?

Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!

thumpernc24 said:
Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!
Click to expand...
Click to collapse
Well if they cant get into hboot they cant check if you are rooted so your good to go. once it gets to factory they just plug it into a machine and it reflashes everything so they dont check it.

as I said before - when I select recovery it does the same thing as when i tried to normal boot (well now the recovery option isn't even there anymore)
But what it did was go to the white HTC Incredible screen and then just start rebooting over and over....

similar problem
i flashed the new cyanogen 7.1.0 stable earlier today and did a complete wipe. 3g wouldn't work no matter what i tried. suddenly, the phone is now in a boot loop (just rebooted on it's own). I get one vibrate, the white "HTC Incredible" screen and it reboots, rinse, repeat. I do have access to hboot (0.92).
I have attempted to flash what appears to be every available option for recoveries including clockwork, RA, and stock. it says everything installs fine and i reboot. still unable to access recovery in any way, just starts the same boot loop.
attempted RUU both via PC and .zip extraction. PC method says i'm not connected via usb despite proper drivers and phone recognition by window 7 and .zip acts as if everything applies appropriately then produces the same boot loop.
I have tried everything I can find over the last 6 hours of searching various forums. Anyone have an idea on a potential fix or a way to get s-on without being able to access recovery?
I'm about to exercise my insurance plan and put this phone under my tires and slowly back up...all replies are greatly appreciated