Boot Loop - Bricked? :(

Have you tried flashing a .img file from fastboot to the phone?
like:

fastboot flash recovery recovery.img

edit, if you haven't you can grab clockworkmod v.2.6.0.1 in img format here:

http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.6.0.1-supersonic.img

I would grab that, rename it to recovery.img, copy it to your fastboot folder and type the above command.

One more question - When you upgraded hboots the first time around with the RUU, do you remember your phone reboot after it updated one or two sections then going right back to the upgrade?
 
Last edited:
manwiththeevo, that was a no go on the pc36img you linked, i'm still in boot loop. however, i noticed the bootloader image didn't flash, instead it said "bypassed," is that to be expected because I'm in bootloader? And could bootloader be causing the problem?

fred, yeah, i've tried flashing clockmod in command with fastboot before, and unfortunately same old boot loop. I decided to go ahead and try the one you just linked me to for giggles, but my hboot is 2.10 now after flashing all these different PC36IMGs, and instead of successfully flashing it said "FAILED (remote: not allowed)" Should I go ahead and knock hboot back down to .76 like we did before?

And yes, RUU definitely reset my evo when that file was flashing, I remember vividly because I thought I had messed up when it first happened and was worried.

I'm trying to keep my first post up to date on what I have tried, so if you want to see if I've tried something check there. I really appreciate the effort you guys are putting in for this, thank you very much.
 
Last edited:
Something that I just remembered that may (or may not) be important information: Before my evo went haywire I was using a CM7 nightly for about a week or so. It was understandably unstable so I decided to flash CM6 and wiped out data, cache, davlik, and yet for some strange reason when CM6 came up google apps was already there. I tried to wipe all the data again and reflash CM6... google apps was still there. I was so confused because I felt like that should have been formatted. This was the oddest "sign" before I went into the boot loop.

And another question... I see that there is an S-On tool by unrevoked. If I lose my root privileges I should be able to get a new phone under warranty correct? I've got two tests coming up in the next two days and am only going to be able to spend so much more energy trying to get this to work.
 
Last edited:
The s on tool is not really a big deal right now.

Try every option where it says clear storage, then re run the ruu from fastboot. There's is no reason why I shouldn't work. Your evo is being picky or something...
 
When you say errors are you referring to the bootloader image being bypassed instead of flashing? I just assumed it couldn't flash a partition I was currently using.

Anyways, going through RUU right now. The only option I saw for clear storage was Clear Storage > Delete All User Data, so I did that. Didn't see any other options.

Edit: RUU, the exe, finished. I'm still in boot loop... I just don't get it. It seems like everything is actually flashing correctly.
 
Last edited:
Hmm, ill see if I can get the stock recovery and an update.zip for you to use

Edit, might take awhile for be to get home and do that.
 
Last edited:
It's fine I understand. Can't be on here all the time.
Anyways I've been doing my own research, and a guy on XDA detailed all the exact same problems as I have and apparently a certain PC36IMG worked for him... it didn't work for me :/ I was so excited about it to.
 
I've never came across a situation like this, its bugging me to be honest.

Format your SD card and redownload the Ruu / pc36imgs. Maybe bad downloads.?
 
Honestly, I just reformatted my SD card thinking the same thing and flashed a PC36IMG, but not RUU, I'll try that...

Anyways, I have searched the internet up and down trying to find a solution and this is the only person I can find who detailed the same problems, and actually fixed it. He flashed a file, eng-PC36IMG.zip, from a very old toastctfh tutorial, and that did it for him. However he said he was messing with NV files (I don't even know what those are) when he broke his. I don't think I was doing the same. Anyways, I found and flashed the same file he used and it didn't for me :/ Anyways, here is that thread
Help! Evo stuck in boot loop... - xda-developers
 
Yea, RUU is still a no go. I'm really starting to consider just trying to take it back to Sprint somehow. I know that technically I should be able to fix it... but I don't have a clue how, and it doesn't seem to matter what I flash.
 
Do you know if there is any way i can turn my root off before I go in?

Without getting a working recovery, i dont think you can flash the S-On tool from unrevoked. (This is why i dont recommend UR, among other things)

Maybe sprint will have mercy on you, or you will get a new employee.
 
Should I try flashing an old nandroid backup? If I try and make my own pc36img, what would I put in the android-info.txt file?
 
I thought the nandroid was just a bunch of image files? I was just going to throw them in a zip and rename it to PC36IMG.zip