Develop Bugs

Am I bricked?

I posted this in the Official Radio Thread over in the dev section, but I don't want to steer that discussion off topic. Here's the gist:
I rooted my stock 2.2 Inc yesterday with Unrevoked 3.2, everything worked fine. I then loaded the 2.15.00.09.01 radio linked here, again, worked great. This morning I decided I was going to remove some bloatware (CityID, Skype, etc), so turned off the phone so I could boot into recovery. Went into HBoot, but realized I still had the PB31IMG.zip file from the radio update on my SD card. The HBoot was waiting at a "Do you want to update?" prompt, so I pulled the battery. That's when things turned to crap. I haven't been able to boot past the white logo screen since then. I can still boot into HBoot, but everything I select from there results in the same logo screen lockup.
UndergroundWire suggested:
Boot into Hboot. When it asks you if you want to apply the update, select NO (down volume I believe). Go Into recovery. Reboot Phone.
BE VERY CAREFUL NOT TO APPLY THE UPDATE AGAIN.
It happened to me before. I panicked and did the same thing like you before. It seems the phone had a hiccup and the only way to boot it normal is to go into hboot --> Recovery --> Reboot.
As long as you see any kind of screen, it's not bricked. Again be very careful not to apply the update twice.
Click to expand...
Click to collapse
Which I tried. I went into HBoot, selected No when asked if I want to update, then No when asked if I want to reboot. I then select Recovery, but I get the same results. White logo screen and nothing more. I remembered to press the power button to try to get into recover, did so at various stages, but no success.
So at this point, I'm dead in the water. Does anyone else have any suggestions? It seems that I can get into HBoot, but any option I select ends up hanging on the logo screen. Also, can anyone tell me, If I'm s-off, can I simply put the older radio's PB31IMG.zip on the sd card and apply it (to downgrade from this 2.15.00.09 radio), or do I need to do some prep work first?
Thank you.
Doc

Delete that radio from your SD . Do you have root? If you do restore your nandroid backup. If you did not look around and find a stock 31 to flash are you s off whats your software version?
Sent from my ADR6300 using XDA App

Don't jack with the radio anymore find a stock image to run from hboot and run the update . Just make sure the image is compatible with your radio version.
Sent from my ADR6300 using XDA App

Jonathan062 said:
Don't jack with the radio anymore find a stock image to run from hboot and run the update . Just make sure the image is compatible with your radio version.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
So I downloaded the 2.15.00.07 radio from the previous thread, installed it, and got the phone back!
Thanks a lot to everyone who helped me along, big sigh of relief ;-)
Incidentally, Yes, I was s-off with Froyo. And I couldn't do a nandroid restore because it would never boot far enough to get to that menu.
Thanks again!
Doc

Glad you got it fixed. Be super careful with radios! Congratulations.
Sent from my ADR6300 using XDA App

If there's a next time, don't panic and pull the battery again.

Just an FYI, all the radios in that thread are full images not incrementals. Flashing the same radio twice will not brick the device. That was only true for a leaked update a while back.
http://forum.xda-developers.com/showpost.php?p=8029185&postcount=99

Rooted DINC, can't get past recovery?

Just rooted my new DINC, got into the main screen. Went into Clockwork and flashed a nandroid from a different device. Now I cant even get back into CWM. If I hold down and power I get hboot, but anything after that gives me 5 vibrations and blinking green lights. wtf?>

I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?

DroidHam said:
I can actually see CWM for a second, then i get the errors. Is there a bootable CWM, like the NookColor?
Click to expand...
Click to collapse
not really that i know of
best bet is to ruu back to stock and start over
EDIT: first link i sent wont help you
http://d01.megashares.com/index.php?d01=CHoQD3B
put this on your sdcard, rename to PB31IMG.ZIP
boot into hboot, when it asks to apply the update, say yes
give that a shot
for future reference, nandroids from phones are not interchangeable

I dont know how to use ADB, and that tutorial assumes you can run zips via recovery, which I cant...

Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock

DroidHam said:
Isn't there a PMBTG113.zip or whatever file I can boot off of in recovery that will restore my phone to stock
Click to expand...
Click to collapse
yea sorry, use the new link and destructions instructions i posted, should get ya running

damn, that link wont start the download

Do you have a micro sd card reader that you can put into your pc or laptop? You need to get that PB31IMG on the root of your card. Then get into hboot to flash.
Sent from my ADR6300 using XDA App

Yea, I put it onto the root, applied the PB31IMG and rebooted. Same fcking problem. WTF?!?!

DroidHam,
try pulling the battery, wait around 10 minutes, put the battery in and boot the phone. Yes, it is very important to wait for that long.
Post your results if it booted or not, i had the same issue.
Also let me know if this is a refurbished phone.

ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?

Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App

DroidHam said:
Any ideas?? Going on day 3 w no phone......
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I noticed you mentioned that while powering on you say you are holding down...down is diagnostic mode, you should be holding up to get to recovery.

After applying the ruu. Try re rooting
Sent from my ADR6300 using XDA App

How do I root if i can't get past hboot??!
Sent from my LogicPD Zoom2 using XDA App

I attempted to root a new Incredible for a friend and had the same thing happen a few days ago. I was able to create a nandroid backup via CWM recovery, and then flashed CM 6.1. CM then bootlooped when trying to boot for the first time. After this point I was unable to get into recovery. The screen would just go blank and would vibrate multiple times. At one point I did manage to succesfully get into CWM recovery without the screen going blank, but then recovery would not recognize the SD card. I restarted and was never able to get back into recovery.
I then attempted to flash a PB31IMG.ZIP from HBOOT that was supposed to restore it to factory state. At this point the phone when blank in the middle of flashing and would not do anything other than vibrate when I would attempt to power it on.
I told them the phone just inexplicably died and they exchanged it at the Verizon store. Everything went perfect with the replacement phone. I figured what happened was a one time thing, but after reading this I would definately be hesitant to root anyone elses Incredible.

Do all phones have hboot?? I don't wanna get screwed. But this was sent was Asurion.... i really need to fix this. There must be a way please!!!
Sent from my LogicPD Zoom2 using XDA App

Just got off work... do the battery pull, wait 10 min, then the start phone see what happens.
I'm not sure at what point you are with the RUU image at this point so take out your sd card just to be safe.
You are getting into the Qualcomm diagnostic mode, which is basically 5 buzzes and then the green light keeps flashing green correct?
I will be on and off for the next few hours to see your results.
DroidHam said:
ya its a refurb...
I downloaded this:
build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG
Renamed it and it flashed. Then when I rebooted, it doesn't show me CWM anymore, just the HTC screen, a "popping, kind of electric noise", and then 5 vibrations and blank screen, with green blinking LED.
I downloaded the restore above, and renamed it. It doesn't allow me to flash it. It scans it, but never gives me the option to press up to flash.
Keep in mind, S-ON is now set, whereas it was S-Off before.
Previously I was seeing CWM for a split second then it would crash. I dont see CWM anymore but its still crashing at the same point.
If I copied a nandroid backup onto a different phone, it cant be COMPLETELY ****ed right? Just needs to be rebuilt somehow?
So when I put the battery back in in 10 minutes, should I reflash that RUU I mentioned above, or what?
Click to expand...
Click to collapse

5 vibrate = defective usb plug/phone... time for nother refurb. theres a couple posts on it, happened to me.

I don't know much.. but I'm pretty sure this thread is in the wrong section. Mods should move this to Q&A or General...

[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] Possibly bricked EVO, can get into bootloader S-OFF

I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!

raidernation said:
I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
Click to expand...
Click to collapse
I don't even recognize that as any radio I've seen for the Evo. The last one ended in. 11.19 or something like that. The one before that ended with. 01.09 I believe. I don't recognize the one you used. Are you positive it was an Evo radio...? Your situation doesn't sound good though. I would try running an RUU from fastboot, but if you did flash a non evo radio, your probably in trouble...someone correct me if im wrong and that is indeed an evo radio.
Sent from my PC36100 using XDA App

Have you attempted running a 3.29 RUU?
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.29 version, boot your phone into the bootloader, select fastboot, connect to your pc. Once it shows fastboot usb on the phone, run the ruu exe.

k2buckley said:
I don't even recognize that as any radio I've seen for the Evo. The last one ended in. 11.19 or something like that. The one before that ended with. 01.09 I believe. I don't recognize the one you used. Are you positive it was an Evo radio...? Your situation doesn't sound good though. I would try running an RUU from fastboot, but if you did flash a non evo radio, your probably in trouble...someone correct me if im wrong and that is indeed an evo radio.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It is, I just checked; its rolled back 3 versions from the 11.19 version.

Can't he place a PGimg.zip on root of his SD card and fastboot from his phone to return him to stock s -off ?
sent from a sweet paper weight.

ibsk8 said:
Can't he place a PGimg.zip on root of his SD card and fastboot from his phone to return him to stock s -off ?
sent from a sweet paper weight.
Click to expand...
Click to collapse
He can place a PC36IMG form of the RUU and do it that way, but if he wanted s-on, he'd need to flash the unrevoked s-on tool from recovery, which he can't get to.

raidernation said:
I can get my Evo into the bootloader, but it won't allow me to reboot (it goes to the HTC Evo screen, then the screen goes dark and vibrates 5 times), I'll pull the battery and go back into the bootloader, I'll try to go into recovery and its does the same as rebooting. If someone can advise me what I can do to fix this, I would appreciate it. I messed up when I flashed an old Radio (2.15.00.07.21) Wont do that ever again :-(!
Specs: HBoot 2.10
Radio: 2.15.00.07.21
S-Off
3.29.651.5
I am a noob at this so please be nice, I also get the radio_v2 fail-pu when trying to update the phone, I'm not sure if i have the right PC36IMG file, thank you for your time!
Click to expand...
Click to collapse
Try to basicaly reroot id try to hook to pc and run the hboot driver to fix the driver hopefully that will get you back into recovery. And id stick with flashin roms not radios its to risky. Did you back up your wimax keys?

Borked
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.

Enmund said:
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
Click to expand...
Click to collapse
Make sure your sdcard is formatted FAT32.
Sent from my Galaxy Nexus using Tapatalk 2

fastboot oem enableqxdm 0
fastboot reboot
Use these commands through adb
Sent from my PC36100 using xda premium

That will remount your SD card
Sent from my PC36100 using xda premium

stevenskanse said:
fastboot oem enableqxdm 0
fastboot reboot
Use these commands through adb
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Hey that sounds like it would work, but my question is...How do I get the phone detected on the pc, if the phone cant read the sd card? You get what I'm saying? Like, what buttons do I press to enable the USB to be picked up on the computer? Thnks a lot man.

That happened to me. You have to hold BOTH the Vol+ and Vol- Buttons at the same time until it starts vibrating. You also have to connect it to the computer in order to make it vibrate.
EDIT: You have to take out the battery while plugged in. Sorry for forgetting

When u put the PC36IMG.zip (named exactly like that) on your SD card, are u sure it wasn't named PC36IMG.zip.zip or any other variant of the correct name? Use a card adapter to put file in main folder of SD then put it back in phone. Then boot to bootloader n test. What recovery did u have installed when you tried to flash a radio? Clockwork will not flash radios

{ParanoiA} said:
When u put the PC36IMG.zip (named exactly like that) on your SD card, are u sure it wasn't named PC36IMG.zip.zip or any other variant of the correct name? Use a card adapter to put file in main folder of SD then put it back in phone. Then boot to bootloader n test. What recovery did u have installed when you tried to flash a radio? Clockwork will not flash radios
Click to expand...
Click to collapse
Yes I did... It says wrong image

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.