Develop Bugs

[Q] rooted evo... bricked evo... help!

got my evo about a month ago. rooted lastnight since unrevoked finally pushed out their 3.3 version which is updated for my version of hboot (2.02). the root went very smoothly. i installed the latest cyanogenmod rom, only to discover there was no market or gmail app with the rom! wish i had known that before. after doing some research online, i found out i needed to flash or install a "gapps" apk. so, looked around for that for a couple hours and couldn't find it. i downloaded what i thought would be the right .zip file to get the market on my phone (a vending.apk that was listed in another thread having to do with this same issue). so anyway... downloaded that, moved it to the root of my sd card, flashed it through clockworkmod recovery (by the way, everything up until this point was perfect) and finally rebooted my phone... only it never rebooted. the white htc EVO 4G screen was there. then, black screen, as if it was about to begin the cyanogenmod boot screen and fully boot. but, no. it went from white evo screen to black screen... to OFF. after this, i couldn't even turn it on to get it into hboot or access recovery. tried to do that for two hours. and finally i was able to get in... so i tried doing a factory/data reset through recovery, then a cache clear, then reboot. nothing. same thing. went back into recovery, tried reflashing cyanogenmod rom again. nothing. tried flashing myn's rom. nothing. all i get is installation aborted.
i am pretty sure that this is not a complete brick since i am now able to access hboot and recovery. but if i can't flash anything... and i'm stuck in hboot and recovery and cant boot my phone... what the hell do i do now? please help me figure this out!! anybody have any good advice or a known fix...??

Boot into recovery. Do a factory reset. then wipe cache and dalvik catch. Re flash cynagon and let it boot. You then need to find gapps.zip. Boot into recovery flashing gapps.zip.

i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...

brtnygrey said:
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
Click to expand...
Click to collapse
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.

evolishesh said:
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
Click to expand...
Click to collapse
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.

brtnygrey said:
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
Click to expand...
Click to collapse
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk

mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
ok is the install through recovery supposed to be almost instantaneous? it didn't take a minute like every other rom. and after reboot (10 minutes ago) i'm still sitting on the white htc EVO 4G screen. i don't think this is working either. but i really do appreciate your help. any other suggestions? is there anything else through recovery that I can do (since i cant make it past that) that might fix my system? anything in partition? i'm so stuck!

mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
and also... when i go into hboot, and it runs through the "checking sd" thing before i can select options... it says "no image or wrong image". what?

Nothing is working!!

Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.

SilverZero said:
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
Click to expand...
Click to collapse
i am using clockwork. i've wiped so many times... but i can't make anything happen. and, i did format the sd card eventually, but not until a couple of hours ago... and only as a last resort because nothing else worked and i've been trying to fix this since last night, so i figured it couldn't hurt. but if that is part of the problem... how can i fix it? thanks for your response. i don't know what else to do other than take it in for a switch.l but if i can get into hboot... then sprint can too... and they will see that i'm rooted and void warranty. so am i completely screwed?

I had same issue.
I just reflashed the sprintlover rom (PC36IMG.ZIP) which came with Amon_RA recovery.
Then i installed the CM6 with Amon_RA recovery and everything works fine now.
Good that i did Titanium backup few days before

This is happening to me too. Almost everything he's describing is the same. Except I installed a gapps.zip and then it wouldn't boot after that. No matter what I flash, it either gives me a status 7 error and aborts the install or it may "install successfully" but it never boots. Also tried the pc36img.zip as well. I had a nandroid backup and tried to restore that, but that aborts saying cannot flash boot image. Tried a rooted and also an unrooted stock ruu, they won't work and the .exe version on a pc can't find my phone when I plug it in and power it on. Anyone have any Ideas for me. I can get more specific error messages and hboot numbers, etc. if needed.

I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Edit: I posted the Amon file and all you have to do is rename it to PCIMG.zip. Also I think the gapps you were looking for you can find on the cm site itself or within that thread. Sorry if it sounds like I a being negative but I see alot of people get on noob and I wondered why but unfortunately its because things like this happen. In the OP for CM6 it says to use Amon and backup your keys. Now if you get your phone backup you got to first check and make sure your RSA keys are in tact unless you backed them up already.
Joeykrim has a app on the market to check or there are numerous threads on what to do. Sorry and hope it works out for you if not INS is your friend
View attachment PC36IMG-Amon-V2.2.1.zip

playya said:
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Click to expand...
Click to collapse
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.

tailsthecat3 said:
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
Click to expand...
Click to collapse
Yea but have you tried Amon and from what I read and this is from developers Amon has a much better handle on things as far as backing stuff up, partitions and protection of keys.
I ran Clockwork on my wifes phone because to me its simple and works with Rom manager but after a while I just said F it and switched since it was messing up my backups. Hey to each his own..

Ok, I don't believe that your device is bricked. You may have flash the wrong gapps or something, but is should be easy to fix.
First, download these 3 files and put them on the root of your SD card:
Cyanogen 6 stable for evo
Latest gapps for HDPI
Calkulin's format all
Red through first, then follow my instructions EXACTLY:
1.) Boot into recovery.
2.) Flash Calkulin's all format. This will wipe everything that needs wiping. (everything but the SD card)
3.) Without exiting recovery immediately flash the CM6 .zip. Do not flash the gapps yet.
4.) Reboot the device now. It will boot into cyanogen, but will not have market or anything. Once fully booted, reboot to recovery.
5.) Do not wipe or anything, just flash the gapps HDPI.
6.) Boot the phone and enjoy.

Evo won't load any roms, can only get into clockwork recovery
Okay, so if I try your steps, just like before The install gets almost to the end, then I get:
"assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/update-cm-6.1.2-supersonic-signed.zip
(Status 7)
Installation aborted.
Sorry Playya, I wanted to try this one more time first. I'm going to try loading Amon Ra now. do I need to rename it to pcimg.zip or should i just flash the current file name?
In case it helps anyone, I have
ClockworkMod Recovery v2.5.0.1
my boot loader screen shows
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUBH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010

Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!

hcavlnch said:
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
Click to expand...
Click to collapse
it may say oops if you battery level is low... I think Amon is so much better its just that Unrevoked puts Clockwork in with their root so people get lazy and leave it in... Amon - its the way to go.
1. Charge your battery and try again
2. Backup your wimax keys - then check how big the file is and hopefully its like 12 megs... If so keys may be ok

Evo Loops At HTC White Screen - No Recovery

I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?

BrashL said:
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
Click to expand...
Click to collapse
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3

k2buckley said:
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
Click to expand...
Click to collapse
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.

Lol, I gave him detailed instructions on how to flash it using the bootloader, don't worry. I was pm ing with him.
Sent from my PC36100 using XDA App

r916 said:
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Click to expand...
Click to collapse
He uploaded a recovery image in a PC36IMG, so it NEEDS to be flashed in the bootloader.

Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)

100proof said:
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
Click to expand...
Click to collapse
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app

Think we have different problems. Every time I try to flash something new it completes fine, but it still boot loops. Hell, yours might be fixable.
I've tried everything now with no luck. Everything updates and completes but has absolutely no effect on the boot looping. This is really insane and my advice to anyone would be to stop using CM7 immediately as it seems to be confined to that ROM.
If anyone else has had this exact problem please post, I want to get a tally of how many people are affected and try to find a commonality.

Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.

teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
But my phone ran for a month without any problems except for some random reboots which seem to be common with this phone in general. I didn't add software or flash anything before this happened, it just happened. That seems to be the experience most people are having, the only thing in common is that they were running CM7 or had been running it recently and tried to flash to a different rom.
What software problem wouldn't be corrected by a successfully completed reflash with a stock RUU? That's the major question.

Hmm, that is awkward; at that point, I would just take it in if you're still getting random reboots. Been on CM7 for the longest and no random reboots on my end.

teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....

dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I agree, that is exactly what they should.

dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.

BrashL said:
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
Click to expand...
Click to collapse
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.

teh roxxorz said:
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
Click to expand...
Click to collapse
Already tried it, no dice. Goes through fine but then keeps bootlooping. On a side note, is there a way to get S-On through the bootloader since I can't access recovery?

You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.

teh roxxorz said:
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
Click to expand...
Click to collapse
Did that buy still S-Off

http://www.shipped-roms.com/shipped/Supersonic/ Did you run the right RUU for your software version?
And I'm heading tot he gym for ~1hr; you can pm me in the meantime and I'll answer when I get back if you still need assistance.

dougjamal said:
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Click to expand...
Click to collapse
I'm sorry I wasn't clear . Days of reading every post in any thread I can find has left me running on no sleep. The huge problem is that no matter what recovery rom is flashed it wont let me boot into RECOVERY MODE. It flashes fine whether it is from the sd or through cmd using fastboot (Ive tried almost every version including the newest of both Amen RA and Clockwork). This gets me stuck in the white HTC screen boot loop. If I flash a RUU it will at least hang with a partition error and get stuck in the four triangle error, which will at least let you charge the battery so I can start all over again. Is there maybe a way to wipe the partition or reformat in fastboot as that is really the only thing working (regular adb wont detect). It seems a ton of people have been popping up with this same problem out of the blue the last few days.

[Q] Bad .zip error

I get the error:Can't open /sdcard/.....zip(bad)
Any other solutions besides the one in the older thread. It's directions were not clear at all.

It's a bad dowload.....try redownloading....happens to me all the time when DL'in from my PC....not sure what the other responses to u were.....but that's what's happeneing
Sent from my PC36100 using XDA Premium App

Reverepats...I downloaded two different MikG Roms and neither worked, I also tried Kings Alliance it had the same error. When I ran the Rom I was running before, SalvageRom, it worked. I see you are running MikG, where did u download from?

I'm assuming that you've tried reflashing recovery? Or possibly switching recoveries?
(from... Evo/MIUI/Tapatalk)

The file corrupted, and you just need to download it again.

No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?

corey140 said:
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
Click to expand...
Click to collapse
2.3 is the latest version. If you choose to reflash just do it via PC36IMG; though I'm positive its just a bad download.

teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!

corey140 said:
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
Click to expand...
Click to collapse
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.

teh roxxorz said:
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
Click to expand...
Click to collapse
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.

corey140 said:
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
Click to expand...
Click to collapse
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.

teh roxxorz said:
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
Click to expand...
Click to collapse
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.

corey140 said:
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
Click to expand...
Click to collapse
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!

corey140 said:
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
Click to expand...
Click to collapse
Yea, unfortunately, that backup is corrupted, and you'll have to scrap it. Hopefully you have another one, or in a position to create a newer one.

Can I just Reboot and go back to what I was using?

corey140 said:
Can I just Reboot and go back to what I was using?
Click to expand...
Click to collapse
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.

teh roxxorz said:
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
Click to expand...
Click to collapse
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.

corey140 said:
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
Click to expand...
Click to collapse
Well I'm certain it is.
IF all else fails, go to the link on your evo, then download the zip from your phone, make your backup, do a full wipe, then locate it in the folder when you flash.

I'm almost certain it's an issue with your SD card. I've seen it before, but just recently remembered what the problem was. Sorry for the late reply, I was at work.
Backup everything on your card to your computer, this will erase all of your files. Also try to have a full battery, this could take some time depending on the size of your SD card, the class, and the number of files. Then, boot into recovery and select partition SD card (I can't remember where it is, sorry). If you move apps to your SD card - which I think is kind of necessary with the ginormous Sense 3.0 roms - use a larger size for the Ext partition. I never move apps to my SD card, so I set mine to the smallest option other than zero. For the swap size you can use the default 32mb - you may want to look into this more to see if there's a more recommended size.
When it finishes partitioning, go back to the main screen in recovery, plug your phone into your computer and select USB-MS toggle. This will mount your SD card so you can move files back to the SD card. If you're using Windows, it may want to scan and fix the card... just skip it. If you want to save time and/or battery, you can power down the phone and use a card reader instead. Then you can try to restore/make a nandroid backup or flash a rom - it should work.
Good luck, hope you get it fixed!
(from... Evo/MIUI/Tapatalk)

Download MikG 1.04 from http://dev-host.org/lv6fjpxaq9x4/MikG-Sense2.1-v1.04-signed.zip
After downloading the file, get an MD5 checker application such as this one: http://getmd5checker.com/download
The MD5 sum for the zip of MikG 1.04 is: fb81c61a19b5db6d4fa67acbfb17907f
When you run the MD5 check on the downloaded zip, it should match.
If it doesn't then the download is corrupted.
If it does match but you're still having issues flashing it, then there's a pretty good chance that it's the SD card. MicroSD cards are a dime a dozen nowadays so it should be pretty trivial to get some other card that you can pop in and try to flash with.

need hepl bad

i have a rooted phone, i wanted to switch roms,
for some reason i pulled my sd card and formatted it (fat32)
and put zip for new rom on it and a cleaning tool
put it in phone and went to h boot and wipped phone and flashed rom, NO go.
then put pc36img zip on sd card and su.23.6.3 ECT zip file.
then in h boot flashed the su file still wont boot at all.
i think i screwed up deleting all files off my memory card.
phone only goes to h boot how do i fix it ?
yea i'm a noob.

when i try to flash pc36img i get E can't find update script.

Try going into the development section and downloading caulkins combo pc36img file. Place it on the root of your SD card, and restart your Evo. Make sure to delete the file you have on there first so you know which is what. You are trying to update your radios correct? Of your trying to flash a ROM, select recovery from the menu, go to choose zip from SD card, and flash away. Make sure to do a complete wipe if its a fresh install. Wipe user data, cache and dalvik. Depending on your recovery version, falcon cache might be in the advanced folder. Good luck and enjoy. Lemme know if everything works for ya.

thanks for replying,
i did exactly what you said and when i chose reboot after flashing that file the phone just went black

and it won't power back on

Don't reboot the phone after flashing the zip. To get back into the bootloader hold the volume down button while pressing power. Flash the zip & when it asks to reboot press volume down for no. From there select recovery. You may have to select bootloader again. If you do go ahead and do it but don't update again. Instead wait a sec then boot into recovery. From there you should be able to flash. You may have to download a pc36img w a recovery attached to it if you deleted everything, but Im not sure. Try the first way. If that doesn't work, flash the recovery as the zip, download a stock rooted rom via USB mount and update your radios that way. Then go to the market and get rom manager. You can flash rom's from the app
Using clockwork mod. Keep digging thru the threads if all else fails. Lemme know what happens and ill try and find the zips you need to at least get it going. Don't let this discourage you tho. Where's a will, there's always a way to fix it. Ya just gotta keep reading. The guys on this site are awesome. They've covered pretty much every scenario you could think of.
Sent from my PC36100 using xda premium

Read the guide in my signature. Start at where you get Amon Ra
Sent from my PC36100 using xda premium

when hboot runs it still says pc36img no image

tropicalbrit
i did everything you stated to a T
and after flashing rom, when i reboot phone boots right back to H boot

went through everything again and went back to warm 2.2 rom and now it's working.
a big thanks to you guys for helping me get my phone going again

It could have just been a bad download. Next time you download a rom, see if you can check the md5 to make sure its a complete file.I'm not sure if I helped at all, but I'm sure glad you got it goin. Happy flashing.

i believe it was a bad file cus it was only half the size of normal roms.

Need help fixing soft brick!

I'm having some major trouble with my Evo. I tried flashing from Classic v005 finale to v006 and I wiped everything 3 times. Now, I'm stuck in hboot and my recovery won't start. i have a PC36IMG file (TWRP 2) in my sdcard and says it updates but it really isn't. When I try to restart the phone, I get pushed back into fastboot. What can I do to fix my phone?

Twrp2 may have perm bricked your phone its done it to quite a few ppl hope you have ins cuz you'll need to flash a stock ruu thru hboot and send it in for replacement

ok. how do i push an ruu if i can't boot?

You'll have to put it on root of SD as a pc36img and boot to hboot/bootloader and run the update it should put your hboot back to a stock version so u can return it twrp2 had issues for several ppl and bricked their phones
Edit: does your hboot mysteriously say s-on now?

No, it doesn't. I might be screwed though because the only thing my computer sees when I plug in is the bootloader interface. Won't pick up the sdcard

try flashing a RUU for your phone and then Amon Ra recovery

Sounds like twrp2 borked it some ppl had s-on after but the not reading the phone on USB is a pretty sure sign twrp2 bricked it it was causing problems with bad blocks or something during the flash not sure what exactly it did to the phones but they were unrecoverable afterwards it screwed something up that wouldn't allow it to rewrite to the internal memory or be recognized by fastboot commands or adb

SprintLTE said:
ok. how do i push an ruu if i can't boot?
Click to expand...
Click to collapse
I've never used an RUU, but I believe it's an .exe file. I think you can run it from your PC while plugged into fastboot......from what I've seen posted over the years.
Until someone more knowledgeable gets back to you. Or if you have a SD card reader, do pc36img method, as was mentioned.
sent from xda app on drews ics

Try downloading shipped rom zip file. Load it on your root. Use a card reader if phone won't connect to PC. If it works you should still be s off. Just flash you custom rom back over it after you reflash a new recovery. I use amon.3.11.
See if that will work.
Shipped zip will over write recovery and should fix your problem.

ok I ran an ruu.exe so it's bootable now but I'm still getting random reboots and I can't mount my sdcard. any ideas?

It's broke. Call sprint they'll replace it with or without insurance. If your s-on running stock they won't know that you're rooted. Also sometimes stores will replace it as well. Be prepared to possibly get a upgrade for the phone.
Sent from my PC36100 using xda premium

SprintLTE said:
ok I ran an ruu.exe so it's bootable now but I'm still getting random reboots and I can't mount my sdcard. any ideas?
Click to expand...
Click to collapse
Did you flash a new recovery?
If so, wipe everything.
Try mounting via recovery.
Does it mount SD there?
You may try to partition your card again and see if that helps.
Did you already wipe and try custom rom again?

Isubbie said:
It's broke. Call sprint they'll replace it with or without insurance. If your s-on running stock they won't know that you're rooted. Also sometimes stores will replace it as well. Be prepared to possibly get a upgrade for the phone.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
It will still be s off even after running ruu I think.
To get s on you will need to flash s on before you take it back.
I would try to partition SD or wipe and flash new rom after amon recovery.

When I run the Factory Resets in Amon RA, it skips over everything on the sd card, saying, "E:Can't mount /dev/block/mmcblk0p1". The phone seems fried to me. Luckily, I have the insurance. lol, "oops I dropped it in the sink"

That sux twrp2 was a pretty neat looking recovery I'm glad I read about it after I installed it and had several failed backup attempts cuz I don't have ins so luckily I didn't attempt to proceed with flashing anything or I'd be in the same boat as you up the same creek only I wouldn't have a paddle lol

When will people check the TWRP thread and realize its a bad product ? Great idea, bad product.
Edit: I mean even after installing twrp, when will they check back to see it's hosed, before they get hosed?. This isn't a comment about you, OP. Just meant, too bad there's not a way to let all users of it know to change recoveries IMMEDIATELY.
sent from xda app on drews ics

After the backup failed twice I figured something was wrong since I had already backed up the same setup in amon ra just fine

If you ran the RUU, then either your SD Card is bad, or you're back to stock, so just take it to Sprint