Develop Bugs

Possible brick. Bootloader access but no recovery. Any suggestions?

EDIT: Check post 10 for an update on progress after running the stock RUU
Been reading XDA for awhile, first time posting. I'll try to put as much information on here as possible so please excuse the long drawn out post.
Have been running MIUI 11.16 release on Evo 4g until two days ago. My evo began bootlooping in my pocket, which happens sometimes but usually on the splash screen. This is usually fixed by a battery pull and a ROM reflash in Clockwork Recover. However, on this occasion my phone has been bootlooping on the HTC screen. I booted into bootloader and attempted to then boot into recovery but the loop continued.
I have the original PC361.zip still on my SD card so decided to run the update and see if that would reset things. The update was successful and I attempted to boot recovery . The HTC screen flashes and proceeds to a black screen with 5 vibrates and a blinking LED. This now happens every time I turn on the phone with booting into the bootloader.
I attempted (perhaps incorrectly) to flash clockwork recovery through Fastboot USB through my Mac Terminal, but have been unable to do so as it won't allow a remote flash.
./fastboot flash /recovery /Users/****/Desktop/android-sdk-mac_x86/tools/recovery-clockwork-1.8.1.7-supersonic.zip
sending '/recovery' (808 KB)... OKAY
writing '/recovery'... FAILED (remote: not allowed)
So, to recap. Normal boot results in 5 vibrates and a green LED flash that is only reset by a battery pull. Fastboot access is available, but perhaps not usable by remote access. No access to recovery. Cannot mount SD card onto my Mac (not sure if that's a given). Top of bootloader screen says the following:
Supersonic EVT2- 3 ship s-off
HBOOT-0.79.0000
MicroP-041f
Touch Panel-ATMEL224_16ab
Radio-1.39.00.04.26
April 14 2010, 15:41:34
I've done a lot of forum hopping and reading and it seems like this is the most relevant information for trying to fix this problem. At this point, my only real goal is to make a phone call or two so I'm not worried about keeping my root since that can be fixed later. Any suggestions would be much appreciated and I can furnish any information you might need.
Thanks

Have you tried flashing a stock ROM RUU updater from www.shipped-roms.com?
This may not get you into your rooted state with your custom rom, but should at least get you into a usable state.
You should still be rooted afterwards, but will need to run UNREVOKED FOREVER, to get your clockwork recovery back.

Just downloaded an executable RUU filed from Shipped ROM's. I'll go find a Windows system and give it a shot. I'll update in a bit.

I think the .exe is finding the android device, but doesn't do anything after update is hit. Is there a way to connect my phone to the computer to run this .exe through bootloader?

agrim0091 said:
I think the .exe is finding the android device, but doesn't do anything after update is hit. Is there a way to connect my phone to the computer to run this .exe through bootloader?
Click to expand...
Click to collapse
Select hboot usb and make sure the drivers install (probably windows only, sorry) then run the ruu. I think the needed drivers are included with the htc sync software (windows only as well I believe)

DomSim said:
Select hboot usb and make sure the drivers install (probably windows only, sorry) then run the ruu. I think the needed drivers are included with the htc sync software (windows only as well I believe)
Click to expand...
Click to collapse
Just tried with hboot usb plug hooked up and it didn't recognise. I'll try to install HTC Sync and give it another shot. Thank you guys for the help so far.

The RUU successfully installed and booting the phone no longer causes the 5 vibrations and the green LED. The phone is still bootlooping at the HTC screen going to a black screen and then rebooting.
This is the first breakthrough I've made in days. Any ideas on where I should go from here?

I would think maybe flash radio, then they to flash recovery. Maybe wait until someoe else chimes in though

DomSim said:
I would think maybe flash radio, then they to flash recovery. Maybe wait until someoe else chimes in though
Click to expand...
Click to collapse
I tried to flash recovery through Fastboot and my Mac terminal, but I'm still being denied remote access.

A quick update on the situation to try to consolidate any progress so far...
I successfully flashed the stock RUU which should have returned everything back to stock. I'm still stuck in a bootloop from the HTC screen to black screen but no longer have the 5 vibrates and the flashing green LED.
My Bootloader heading is as thus...
Supersonic EV2-3 Ship S-off
hboot- 0.93.0000
microp-014f
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010, 16:41:47
Booting into recovery from Bootloader still causes the boot cycle meaning that the RUU didn't fix everything. Also, S-OFF still seems to mean that the root appears to be in place (maybe?) so no luck of returning it to sprint. Still cannot remote flash from the command prompt in windows.
I'm not sure what to do next. If I had to wager a guess it would have something to do with the PC36img.zip file, even though I'm not totally sure what this means or which one I should attempt to load. If this is the case, I can go buy an SD card reader today and attempt to load another up if anyone can suggest one.
Again, thanks for all of the help.

agrim0091 said:
A quick update on the situation to try to consolidate any progress so far...
I successfully flashed the stock RUU which should have returned everything back to stock. I'm still stuck in a bootloop from the HTC screen to black screen but no longer have the 5 vibrates and the flashing green LED.
My Bootloader heading is as thus...
Supersonic EV2-3 Ship S-off
hboot- 0.93.0000
microp-014f
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010, 16:41:47
Booting into recovery from Bootloader still causes the boot cycle meaning that the RUU didn't fix everything. Also, S-OFF still seems to mean that the root appears to be in place (maybe?) so no luck of returning it to sprint. Still cannot remote flash from the command prompt in windows.
I'm not sure what to do next. If I had to wager a guess it would have something to do with the PC36img.zip file, even though I'm not totally sure what this means or which one I should attempt to load. If this is the case, I can go buy an SD card reader today and attempt to load another up if anyone can suggest one.
Again, thanks for all of the help.
Click to expand...
Click to collapse
did you try to unroot don't know if you used unrevoked but if you did try to flash the s-on tool and then flash the 3.29 ruu that should put you back up to stock and load good but if it doesn't then you may have a corrupted nand. Don't take my word for it cause i know computers more than these phones i know enough to get me by thats about it but if they are anything like computers i would venture that as the problem

Jbcarrera said:
did you try to unroot don't know if you used unrevoked but if you did try to flash the s-on tool and then flash the 3.29 ruu that should put you back up to stock and load good but if it doesn't then you may have a corrupted nand. Don't take my word for it cause i know computers more than these phones i know enough to get me by thats about it but if they are anything like computers i would venture that as the problem
Click to expand...
Click to collapse
Any idea how to flash this through Fastboot or the Bootloader?

agrim0091 said:
Any idea how to flash this through Fastboot or the Bootloader?
Click to expand...
Click to collapse
adb but i'm trying to find out how for you

Jbcarrera said:
adb but i'm trying to find out how for you
Click to expand...
Click to collapse
Just realized my old BlackBerry has microSD support. So I can load something onto my Evo SD card via that quite easily if you think a certain PC36img.zip file would work. I just have no idea what those PC36img.zip files are or do. :/

Jbcarrera said:
adb but i'm trying to find out how for you
Click to expand...
Click to collapse
Just found a PC36img.zip file for clockwork recover. Update was "Successful" but the Boot cycle continues.

Is this the pc36img you tried? If not try it.
http://forum.xda-developers.com/showthread.php?t=780141

Try hboot usb and start adb type push unrevokeds-on.zip that should give you s-on then run the 3.29 Thu that should work
sent from my EVO at the edge of hell

No internet access last night at the apartment for some reason :/. I'll try flashing the PC36img.zip and if that doesnt work i'll try to adb push the s-on file and get it back to total stock to bring it back to sprint.
Thinking about it though, I'm not sure if I had adb access from hboot. I'll update you guys soon.

DomSim said:
Is this the pc36img you tried? If not try it.
http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
Flashed this PC36IMG.zip. Update was successful but the phone is still looping.
Jbcarrera said:
Try hboot usb and start adb type push unrevokeds-on.zip that should give you s-on then run the 3.29 Thu that should work
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I can't get adb to recognize my device with hboot usb plug showing. I tried adb devices and nothing will pop up.

I'm having this same exact issue you did. Did you ever end up finding a solution?

[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] Phone won't boot, can't get into recovery.

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

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

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

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

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

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

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

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

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

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

HELP! Constant Network Error! Tons of info inside, please help :(

I know. It looks like a lengthy read. But all the information you could possibly need I've provided. Please let me know what you think. Also, I've done some searchign around but none of the scenarios I found were a result to flash back to stock sprint RUU.
The error reads as follows: "Attention. A network error has occurred. Retry, or cancel and return to the previous screen."
What actually happens: Anytime I open Marketplace, Facebook app, send a message through KakaoTalk or GroupMe, pretty much anything that uses the 3G, 4G data, it doesn't work. The message only comes up when I try to use the marketplace app. All other apps just say there was a connection error, connecting to the server, etc.
When I hit "Retry" it goes right back to the same dialog pop up, as if it doesnt even re"try". The top notification bar goes from 3G and then disappears, then goes from 3G and just continually disappears. It doesnt matter if I have 4G on or WiFi, it will just goes back to 3G when attempting to gain data, and then disappears and the error happens.
My Timeline of events: I first had been running Synergy and everything was fine. Suddenly my wall charger (or any wall charger for that matter) stopped working when plugged in. The car charger still works, but no HTC wall chargers, odd. So I decided to use that insurance for good and bring it into sprint. Gotta unroot and all that jazz first though. I downloaded the "RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe" and found a way to connect my phone to the PC, and finished the wizard. Mind you, before I did this, I went into recovery (while on synergy) and did a dalvik cache wipe, data/factory wipe and cache wipe, then went back into hboot and ran the wizard from there. Everything went fine, the ROM install was successful, I no longer have recovery and it was the stock sprint ROM.
Where things got fishy...: After it was running through all the constant reboots and things, I let the phone sit while I did other things. I came back to it, signed into my gmail and facebook fine, then went to marketplace. I started downloading all my purchased apps and since that was going to take some time, I let it sit again and went off.
Fishy part: I come back to he phone, and would normally just pull down notification taskbar, and hit clear all notifications, since it said a bunch of things had sucessfully installed, but I notcied it also said "System update complete." Hmmm, I didn't start any system update...did it do it automatically? It had to of. I went to check for an OTA (HTC software update) and it found "System upgrade 1.47.651.1 (30.15 MB) - FOTA update." I canceled it since I pretty sure doing an OTA update on a rooted ROM is a no-no.
So what the heck is the problem here, I never had these issues before until I went back to the stock sprint ROM. I've already updated PRL a few times, does nothing.
Should I go back and reflash it and this time make sure it doesnt do a system upgrade until I've turned S-OFF back to S-ON? Once the phone is S-ON is it safe to update OTA?
My About Phone details are a sfollows:
Firmware version: 2.1-update1
Baseband version: 1.39.00.05.31
Kernal version: 2.6.29-a2443432
Build number: 1.32.651.6 CL171253 release-keys
Software number: 1.32.651.6
Browser version: WebKit 3.1
PRI version: 1.90_003
PRL version: 60683
Any help, advice, suggestions are welcome!!!!! Please hook me up fellas, I'm a little bogged down about the upset.

UPDATE:
Okay. Since I am an impatient person and the last resort was going to re-flash the RUU, I'm just going to do that. And then make sure there is no system update. Once that is done, I'll run the S-ON tool from somewhere, hopefully I won't need recovery for anything, aaand then we'll see where we are. If you're reading all this PLEASE reply with something, anything to let me know somewhere out there is alive! lol, please.

With phone s on and stock ruu loaded it should be fine to accept update...wow u might get froyo lol. And it might help with your data issue...idk much but I know a little.
Edit: maybe try a newer ruu that might help with the data as well. not sure how HTC updates but i think it goes one at a time instead of newest available
Sent from my PG86100 using xda premium

Well the phone is still S-OFF right now, but now that I'm on the stock sprint RUU I dont have a custom recovery anymore, so how am i supposed to flash the unrevoked-forever-son.zip and the PCIMG36 thing!!??! How do I get back a recovery, do I just reflash something like synergy...!?

Here is amon ra recovery. Put on root of SD card and flash in bootloader. http://db.tt/TOsdM52P
This should get u recovery back so u can flash the s on tool. Then run a newer ruu, there is a thread in the EVO dev section with the latest, and hopefully it will also fix your data problems
Sent from my PG86100 using xda premium

gunfromsako said:
Here is amon ra recovery. Put on root of SD card and flash in bootloader. http://db.tt/TOsdM52P
This should get u recovery back so u can flash the s on tool. Then run a newer ruu, there is a thread in the EVO dev section with the latest, and hopefully it will also fix your data problems
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Okay, I downloaded the file, put it on SD card, unplugged it, opened hboot and it tried loading the PC36IMG file, it said wrong image or soemthing like that about 6 times and then went back to the regular screen. Although, it has ALWAYS said wrong image for me, so I'm not worried about that.
So now I just went down and hit recovery and its a no go.

OKAY! Now my phone goes straight to the black screen with a Phone on it, and a little red triable with an exclamation point inside everytime now. It used to only come up when i tried going into recovery. now it comes up everytime i load up the phone. does this mean, its bricked...
EDIT: nvm, I was able to load HBOOT thank god, but still having trouble getting the damn recovery.

Well go to amon ra thread in the EVO dev section and dl th pc36img from there...maybe u got a bad dl...
It's here: recovery-RA-supersonic-v2.3.img - MD5Sum: c00243750cc79e4a1dd4888db175b19f
Sent from my PG86100 using xda premium

Okay, so downloaded the file "recovery-RA-supersonic-v2.3.img", put it (recovery-RA-supersonic-v2.3.img) on SD, turned phone off, and now powering on in HBOOT.
After its finished doing whatever it does, can i go straight to recovery, or do i need to reboot again for changes to take effect?

Well, it did the wrong image no image thing again like it always does, and then i tried going into recovery aaaand it didnt work.

Also u should read these I think:
http://forum.xda-developers.com/showthread.php?t=1151733
How to Unroot Your Phone if Using Unrevoked 3
Or
http://forum.xda-developers.com/showthread.php?t=1245649
***How to unROOT Revolutionary from HTC Evo 4G*** EASY! UnROOT and ROOT! 10/20/11
Depending on which method you used to root your phone..
Sent from my PG86100 using xda premium

Did u rename it PC36IMG.ZIP? Be sure not to name it PC36IMG.ZIP.ZIP Sometimes windows hides extentions
Sent from my PG86100 using xda premium

gunfromsako said:
Did u rename it PC36IMG.ZIP? Be sure not to name it PC36IMG.ZIP.ZIP Sometimes windows hides extentions
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Yyyeeaaah, about that. I forgot to rename it. *facepalm* Just did it, powering in through HBOOT AGAIN. still did the wrong image no image thing, but this time, about it actually did some progress bar thing on the right hand side. but just for a second, and then went back to saying it was the wrong image or no image.
I highlighted the entier file name "recovery-RA-supersonic-v2.3.img" and renamed it to "PC36IMG.ZIP" and then it turned into a zip file. restarted the phone in nboot and didnt work.

Oops I posted the .img for adb sorry here is the pc36img...*facepalm*
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Sent from my PG86100 using xda premium

Okay, so check it out.
I ran the "RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe" before and flashed that, but i remember that i had to unroot my gf's phone back in june, so i went to my downlaod list and saw that i used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe"
So I just did that, and the 3G data seems to be fine. [email protected] Now onward to unrooting.
Now that I have stock ROM, do I just run a S-ON tool and fix it? But I dont have custom recovery, wtf this is effing confusing...

gunfromsako said:
Oops I posted the .img for adb sorry here is the pc36img...
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
AH HA! lol, okay cool. So when I download this, and put it on my SD and then reboot into hboot, i'll have custom recovery? and then i can run s-on with 3.70? then eventually update OTA...?

Maybe I am wrong and it won't flash recovery with a non rooted ROM but I thought would because of s-off it should... Should of flashed the s on before u ran the ruu. It's signed with HTC keys and would of been fine.
Sent from my PG86100 using xda premium

gunfromsako said:
Maybe I am wrong and it won't flash recovery with a non rooted ROM but I thought would because of s-off it should... Should of flashed the s on before u ran the ruu. It's signed with HTC keys and would of been fine.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
YOU DID IT! Horrayy!!!! Thank you my kind, kind kind kind sir!
I am on recovery right now. So now do i follow these instructions...
How to Unroot the HTC EVO 4G
◄●REQUIRED DOWNLOADS●►
Unrevoked S-On Tool
PC36IMG
◄●SIMPLE INSTRUCTIONS●►
If you're comfortable with everything Android related(flashing, recovery, etc.) then its just 2 simple steps:
If you used Unrevoked Forever at any time, flash unrevoked-forever-son.zip from recovery until hboot shows S-ON
Flash the PC36IMG.zip from hboot
◄●DETAILED INSTRUCTIONS●►
If you need a little more guidance, follow these instructions.
◄●If you have used Unrevoked forever, start here●►
Make sure you have downloaded the files linked above. Do not extract them
Connect your phone to your computer via USB and change to "Disk Drive" by dragging down from the notification bar.
If you have NOT used Unrevoked Forever, skip to the instructions below. If you have, transfer unrevoked-forever-son.zip to the root of your sdcard. Do NOT transfer the PC36IMG yet. It'll only cause a hassle and make this take longer.
Once complete, power off the phone
reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Depending on what recovery you're using, you need to flash a zip. Select the unrevoked-foreverson.zip that you just transferred and complete the flash.
When complete, power off the phone. Reboot into the bootloader by holding VOL DOWN + POWER until it boots to the white screen. If it says S-ON at the top, select RECOVERY and skip to step 9. If it says S-OFF, repeat steps 5-7 Until it does.
◄●If you have NEVER used Unrevoked forever, start here●►
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Connect via USB. There is an option for this in both Amon RA and Clockwork.
Transfer the PC36IMG.zip to the root of your sdcard.
EJECT THE PHONE FROM THE COMPUTER and then turn off USB in Recovery
Power off the phone and reboot into the bootloader by holding VOL DOWN + POWER until it boots to the white screen.
It should check the PC36IMG.zip and then ask you YES/NO to apply the update. Press VOL UP for YES
Once complete, Press VOL UP to reboot.
You are now unrooted!
Have I ever used unrevoked? idk if i have! where do i start, or do i just run the s-on tool...?

Yes as long as u rooted with unrevoked and NOT REVOLUTIONARY... make sure to remove/rename the recovery pc36img on root of SD...once s on is achieved either run a ruu or the pc36img from that thread...off to kickboxing I go glad I could help...
Sent from my PG86100 using xda premium

How did u root your phone? When did u root it?
Sent from my PG86100 using xda premium