Develop Bugs

[Q] evo wont boot and RUU fails with error

I tried one of the rooting processes today and it didn't work. Now when I turn my Evo on it goes no further than the white HTC screen that you get when you turn it on. When I try to run the RUU it gets a connection error and won't go through. Can someone please help?

Robes1 said:
I tried one of the rooting processes today and it didn't work. Now when I turn my Evo on it goes no further than the white HTC screen that you get when you turn it on. When I try to run the RUU it gets a connection error and won't go through. Can someone please help?
Click to expand...
Click to collapse
If you pull the battery can you get to the bootloader screen? (hold volume down and power button when turning on)

You should be able to do what Greenfieldan suggests. It is possible to work through this issue, so don't fear but it make take a few tries.

Greenfieldan said:
If you pull the battery can you get to the bootloader screen? (hold volume down and power button when turning on)
Click to expand...
Click to collapse
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.

Robes1 said:
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.
Click to expand...
Click to collapse
Thread stalking is fun, I see which thread you are reading, but you may have to reset you phone.
Do you either:
Have a recovery installed (if you aren't sure, then you may not)
have a PCIMG36 on the root of your sdcard, (if you aren't sure then you may not)

Robes1 said:
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.
Click to expand...
Click to collapse
Go in to fastboot and you should see something toward the top that says "FASTBOOT USB", once there run the RUU

SnoopDawg said:
Thread stalking is fun, I see which thread you are reading, but you may have to reset you phone.
Do you either:
Have a recovery installed (if you aren't sure, then you may not)
have a PCIMG36 on the root of your sdcard, (if you aren't sure then you may not)
Click to expand...
Click to collapse
I have a pc36img file on the root of my sd card. It says that it can't open it when i select flash zip from sd card.

Just download the actual ruu from http://forum.xda-developers.com/showthread.php?t=884060. It will be one of the .exe files same version of you had on the phone will prolly work best. Then do what xhausx said and run the ruu file once there. Thanks xhausx btw cause i was confused too.

aclearersky said:
Just download the actual ruu from http://forum.xda-developers.com/showthread.php?t=884060. It will be one of the .exe files same version of you had on the phone will prolly work best. Then do what xhausx said and run the ruu file once there. Thanks xhausx btw cause i was confused too.
Click to expand...
Click to collapse
or download an unrooted version of your software in pc36img.zip format and boot into the bootloader and it will restore your phone to stock if you cant run any ruu

Need Help
I know this is an old thread, but I'm working on an old phone. Hopefully some of you guys are still following this.
My father has an EVO 3D that showed up one day stuck on the white HTC screen. The only remedy was to pull the battery. I thought it would be no big deal to just go into the boot menu and either try and run recovery, or at worst do a factory reset. Both of these options failed. I even made a few attempts at trying from the SD card with a ROM or two. So I downloaded the RUU direct from HTC thinking that would finally take care of the problem. But after connecting up in FASTBOOT mode and running the RUU, it eventually fails when the update gets to the point that it's supposed to restart the phone in bootloader mode. Because at that point the phone just restarts to the white HTC logo again, and the software times out telling me that it can't connect to the device. Any help here other than passing me a trash can Thanks in advance!

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

Constant bootloop

My Incredible is in a bootloop. I have gone back to stock. The phone will work for a few minutes then just reboot non-stop. I did a factory reset and that did not help.
I can't keep the phone on long enough to do anything. The irony in all of this is that it started to do this 2 weeks after I became eligable for an upgrade...
Smells fishy...now I either wait for Incredible 4G or get the Rezound.
[email protected] Verizon...

Do you have a recovery on the phone still or did you get rid of it when returning to stock? I'm not sure I've heard of this before but if you post the status of your hboot that might be able to help someone help you.
and personally between the two I would go with the Incredible 4G but that's just me being loyal to HTC i guess.

Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.

binaryhat said:
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
Click to expand...
Click to collapse
Post hboot version, s-on or off, and current android version.

cmlusco said:
Post hboot version, s-on or off, and current android version.
Click to expand...
Click to collapse
Will do tomorrow...left the phone at work.

S-off
HBOOT-0.92
Radio-2.15.00.07.28
Stock Android

I know it sounds very round-about but you may need to flash CWM back on to the phone so you can flash unrevoked's s-on tool, I don't know for sure that this is what is causing the problem but you want s-on when you are in stock, especially if you plan on giving the phone to Verizon- if it has been messed with they won't want to handle it because they will say it is not their problem. (I have heard that Verizon has admitted to not checking very carefully, but it can't hurt to be careful yourself)

How can I flash CWM if I can't keep the phone on for more than a minute?

sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.

that is a very valid point. It still can't hurt to try, I remember when I rooted my phone, it didn't take all that long to flash CWM.
You also might want to consider booting into safe mode to see if that keeps in on longer, I am copying and pasting these instructions from technipages.com because xda won't let me post links until they trust me more or something:
Sometimes services and apps you install on your HTC Droid Incredible can interfere with its functionality. If you’ve reached a point where the phone freezes at startup or malfunctions in a way that you can’t remove the problem, Safe Mode is the answer. Booting in Safe Mode will load only software and drivers from factory defaults. This should allow you access to remove whatever ails your smartphone.
1. Turn the device off. If the power button doesn’t do the trick, remove and replace the battery.
2. Power the device on.
3. When the logo appears, press and hold the Menu button.
4. Continue holding the Menu button until you see the home screen.
The words Safe Mode should appear in the lower left corner if you performed the steps correctly.
Click to expand...
Click to collapse
I apologize if you don't have any luck, but I am only trying to help

I'll try safe mode (should have) and see if that works.

binaryhat said:
I'll try safe mode (should have) and see if that works.
Click to expand...
Click to collapse
Does the phone shut off when your in hboot too? You need to do as sugested and flash cwm thru hboot, and then see if you can access recovery long enough to wipe everything in mounts and storrage except sd and emmc, then flash superuser, and a rom.

scoobntaz1996 said:
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
Click to expand...
Click to collapse
Whats your hboot and android version? Have you tried an ruu?
EDIT: Nevermind i forgot i was allready talking to you in the other thread.