Develop Bugs

[Q] {Q} Bootloader

Apologies in advance if this makes some of the vets here really angry.
My EVO is stuck at the bootloader after I tried flashing a ROM in which an error was received. I Nand restored, as I always back up prior to flashing, and I'm still stuck at the booaloader. Any chance I can download a ROM right onto my SD card and then flash? I can get into recovery.

Find the PC36IMG thread dl it and put it on the root of your sd card then get to bootloader. Should fix you up...

Thanks guy.
How can I mount the SD card though? My comp won't recognize the device at all.

It should let you reboot to your recovery from there. What does it do when you try to select it?

I can get into my recovery no problem but getting my SD card to mount is the issue now, even after toggling USB-MS.

GhettoOthello said:
I can get into my recovery no problem but getting my SD card to mount is the issue now, even after toggling USB-MS.
Click to expand...
Click to collapse
ohh, just give it a seconds after you turn USB-MS on. Sometimes it takes its time recognizing it.

10 mins? lol

Alright guys, my apologies. Looks like my terminology is off. I'm not stuck at the bootloader, but stuck at the HTC White screen.

GhettoOthello said:
Alright guys, my apologies. Looks like my terminology is off. I'm not stuck at the bootloader, but stuck at the HTC White screen.
Click to expand...
Click to collapse
Manually Boot into recovery restore the nandroid backup and continue where you left off
Sent from my PC36100 using XDA App

GhettoOthello said:
Alright guys, my apologies. Looks like my terminology is off. I'm not stuck at the bootloader, but stuck at the HTC White screen.
Click to expand...
Click to collapse
It probably doesn't like the kernel the ROM is using, try flashing one of Netarchy's universal kernels or the Stock #17.
I'm not sure about the usb-ms thing though, ten minutes is definitely too long. You may need to use ADB while in the recovery and push the files.

Manually going into recovery and then going nand restore = at least 5 times. Even the nand didn't work, which is making me a little uneasy. However, the USB-MS has worked (needed a new cable).
I'm downloading Virus's Airborne 4.6 onto my SD card, so lets see what this does.

GhettoOthello said:
Apologies in advance if this makes some of the vets here really angry.
My EVO is stuck at the bootloader after I tried flashing a ROM in which an error was received. I Nand restored, as I always back up prior to flashing, and I'm still stuck at the booaloader. Any chance I can download a ROM right onto my SD card and then flash? I can get into recovery.
Click to expand...
Click to collapse
Did you flash the new radio?

ALRIGHT after the weirdest experience with my EVO (mainly my fault), everything is back to normal. I downloaded a newer version of Virus's Airborne rom via USB MS (needed a new cable) then flashed. After that I went back into recovery and restored the Nand that wasn't working earlier. Weird, but im back.
Sent from my Evolution using XDA App

[Q] I need help

Early this morning, I rooted my Droid Incredible using the Unrevoked 3 method. After doing so, I completely forgot to create a nandroid backup and went ahead to install a custom ROM (Cyanogen Mod). Now here's the issue. I want to get back to the Stock 2.2 sense. I tried to unroot my droid, but nothing seems to be working. Can someone please help?

You need to flash a stock rom back before unrooting.

Where can I get a stock ROM. I think I just bricked it now because it won't even boot Cyanogen Mod. It's stuck at the HTC Incredible white screen.

Do you know what type of screen you're using? Slcd or amoled ? Each method has a different way of unrooting. Just in a Google search engine type in who to unroot Droid incredible, and then the what screen it is. You can potentially brick your phone if you use the amoled method on a slcd one.
With the amolcd screen it's as simple as finding the right file, hence doing the search engine. When you get the file, all you have to do is just place it in the root of your phone, and turn off your phone and press and hold the power button and the volume button at the same time.
With slcd you have to do it different way. Assuming you haven't messed with the radio, if you did, you have to flash a 07.28 radio. But assuming you didn't touch that, you have to flash something that puts s-on. Ans then after that you have to put a file into the root of your SD card and then flash appropriately.
Now I did this multiple times, rooting and unrooting, and for some reason there's always so
Something drawing me back into rooting and flashing a new rom. There's no greater satisfaction than knowing you can do anything with your phone. But it's entirely your choice.
Oh yeah, to figure out what screen you have go to settings then about phone then hardware information and 002 is amoled and 003 is slcd. Google is your best friend after you figure out what screen you have. Good luck!
Sent from my Incredible using XDA App

You haven't officially bricked it until you can't power it on at all. Try taking out the battery and then holding the power button and volume down. If you can access the white boot screen where it gives you a choice of accessing recovery there is still plenty of hope. Don't freak out you haven't bricked your phone
Sent from my Incredible using XDA App

I can't load anything. The farthest I can go is to ClockWord Recovery, and when I try to reboot the phone, it's stuck on HTC Incredible. That being said, I can't check what screen type I have. However, before it was bricked, I did flash a file to make S- on. And, when I tried degrading my firmware, nothing happened. :/

OK first off the name of the first that you flash should start with a "p" I don't exactly remember the exact file name. Make sure you have s-on, I'm sure you do. And then put that p something file into the root of your SD card. root as in, it isn't in any folder.
Now when you flash this, you don't do it in clockwork recovery, you do it through hboot I believe. Hboot is the white screen when you hold on the power button and volume down. It should automatically read the p something file. And it'll ask you if you want to update. Say yes and then just let it install
Sent from my Incredible using XDA App

PB31IMG, I attempted to Flash it in HBOOT, but it didn't work. Now, I can't even connect my Droid to my computer.
I'm screwed.

Sorry for the double post, but I just followed some whacked-out tutorial that told me to format everything via Clockworkmod Recovery...now when I boot my phone, it goes straight to HBOOT and won't do anything...

OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App

lazysleepyboi said:
OK what can you do exactly, you can get to hboot and what else. Also when did you buy your Droid incredible ? We might be able to figure out which screen you have based on that. Oh yeah and where did you buy it from? Also, even if you can't mount it you can still easily take out your SD card to flash files that way. Don't lose hope, we can still get back to stock
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.

Can't remember exactly how to tell but know you can tell by the model #under the battery on the phone.
Sent from my ADR6300 using Tapatalk

If you could get to clockwork u should be able to flash a rom if your sd wont mount use a card reader and plug directly into your comp
Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
HTC Incredible 2.3.1

Meetii said:
I bought it near the beginning of October, I believe it was the 9th? And, I bought it at Verizon.
Aside from being able to get to HBOOT, I can get to Clockworkmod Recovery...but that's about it.
Click to expand...
Click to collapse
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader

lazysleepyboi said:
my brother bought his dinc before you and he got a SLCD screen, chances are that's what you have.
here's the page i used to unroot my brother's SLCD screen,
http://dougpiston.com/?p=7
follow it exactly, and just like jaysckap said, you can always take out your microsd card and put it into a usb reader
Click to expand...
Click to collapse
That's the exact tutorial that I followed, but it didn't work.

Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
ok can you tell me how you flashed the included file? did you put it into the root of the SD card?

For now i would get a rom on your sd so your phone will boot up and do a nand backup so you at least have a working phone when i get home ill try and help you out
Meetii said:
That's the exact tutorial that I followed, but it didn't work.
Click to expand...
Click to collapse
HTC Incredible 2.3.1

Ok if you have a card reader for you SD card load it in and open you card on your PC. You need to make sure that the sd card is in FAT32 format otherwise when you try to load the PB31IMG file it wont read it. To check this go to my computer, find the removable drive for the SD card right click and go to properties, you should see what format its in. If it's FAT format copy everything from your sdcard to a folder on your PC, go back and right click on the removable drive and format the card to FAT32. Then of course copy everything back to your card. Then try the PB31IMG file again in hboot.
I would personally just go in recovery and wipe to factory, then choose the option to install zip from card and install the rom or which ever rom you want so the phone loads again. Good luck!

For now, I'm going to flash a new rom and hopefully I can fully boot my Droid again. Afterwards, I'll try to flash that file again. BUT, the first time I did it, I put it in the root of my SD card and booted HBOOT and nothing happened.
EDIT: This ROM is going to take close to 30 minute to download , so I guess I'll be back in 30 minutes; don't leave me please.

do you have a sd card reader? if you do, pop out your sd card and make sure it's format is FAT32, nothing will happen if it isnt FAT32

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

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

Possible brick on my hands. could use some help.

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

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

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

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

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

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

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

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

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

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

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