Boot Loop - Bricked? :(
I'm rooted, unrevoked; currently stuck in a boot loop, with no way to access recovery, only bootloader, and my rom won't boot. Any ideas on how I can get out?
So far I have taken these steps:
Ran two different RUU exe's (with and without sd card in evo)
Flashed RUU as PC36IMG in bootloader
Flashed Amon Ra's Recovery and Clockwork using fastboot in command prompt
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in bootloader
Flashed Sprint Lover's as PC36IMG in bootloader
Each of these methods flashed successfully as far as I can tell... yet I still go into an infinite boot loop.
Anyways I'm at my wits end here, pretty worried, and phoneless, so any help would be amazing.
- 02-01-2011, 08:14 AM #2
- 02-01-2011, 09:59 AM #4
Try this. Download your ruu zip file from link rename pc36img and move to root of phone.
It will be the stock ruu so you would have to root the phone again.
Sent from my PC36100 using Tapatalk
I'm sorry, I wasn't specific about how I "flashed" RUU, that was actually the method I used already :/
And it was actually you're thread that I used to do it! So I appreciate you previously posting the method before, and then even suggesting it to me.
Unfortunately even once I used bootloader to install the ruu PC36IMG.zip it still went straight into a boot loop
- 02-01-2011, 12:06 PM #6
- 02-01-2011, 12:15 PM #7
If your recovery is borked, maybe you can try using the PC36IMG.zip file that thefredelement posted in another thread...
-Stay thirsty my friends.
Fredelement, it actually said ok for all, even boot, radio, everything. I posted this same question on xda, and someone suggested trying Sprint Lover's file, it being similar to the ruus. Same result, I got all ok's but I'm still in a constant boot loop.
I'll try flashing Clockmod, but as RA's successfully, yet staid in loop I have a sinking suspicion it's not going to help me. If I could just reach recovery!
I do have nandroid backups, but know little about them, outside of using them in recovery. Can I rename those to PC36IMG.zip and try flashing them?
- 02-01-2011, 01:29 PM #9
My hboot has changed twice.
From .92 or .97, I don't remember
Fastboot is working.
So about this formatting/flashing partitions?
Btw, thankyou very much for the help, I will say whatever is going wrong I think is happening very early in the boot sequence, because all my flashes are successful, it just doesn't seem like the phone "gets" far enough in the boot sequence before cycling.
One last question, I don't think I have changed my actual bootloader. I tried to flash two PC36IMG's that had bootloader in them (RUU didn't) and they both said "bypassed," should I maybe try and do something about flashing a new bootloader?
- 02-01-2011, 01:58 PM #11
Lets just verify a few things first to see where to go.
What hardware version is your phone?
Do you still have S-OFF? (right next to the hboot version number)
hboot 2.10 doesn't provide a lot of fastboot usb commands.
edit: What most likely happened is that the partitions got a little wonky when you went to hboot 2.10 but if you're on 003 hardware with S-OFF then we can flash back to .76, where you can probably re-flash and get to a recovery, you'll have to re-flash a ROM, not just nandroid restore when that's over (because of changed partition information), then after that you *could* potentially get a nandroid back.
- 02-01-2011, 02:04 PM #13
I'm unsure what it was when I very first got the phone, November 4th. No one ever told me to keep tabs of that stuff. However I know that when this mess started, yes it was. However fastboot didn't work, and I read that I should move down to .76, and so I did that to enable fastboot commands. They worked then.
- 02-01-2011, 02:10 PM #15
If you had one problem with a bootloop (most likely a kernel / boot partition problem), then while you had that you flashed down to .76 hboot on 004 hardware the partitions can be pretty screwed up. BUT - since you're able to get in to the bootloader you're probably OK...
Before I have you downgrade your hboot again (from 2.10 to .76), I was wondering what RUU version you had tried.
If the hboot changed your partition information and you were trying a RUU prior to version 3.7 with hboot 2.10 your phone still won't work because the RUU isn't allowed to over-write hboot (which is probably reading where /boot is wrong).
The bootloop started when I was .97. It continued after .76.
I was unsure of which RUU to try, and maybe should have done some more research. At the time I just assumed I go with the most recent, so I used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip"
- 02-01-2011, 02:18 PM #17
- 02-01-2011, 02:27 PM #19
PC36IMG.zip), Put that on your sdcard AFTER you're back to hboot .76..
Important to note, the first file will give you hboot .76 but will say hboot 2.10!
To no avail
When I flashed the .76 (the fake 2.1) and selected recovery it just went straight to my splash screen. Interestingly (maybe? maybe not) it didn't boot loop forever like the way it did before, it instead went back into fastboot, something its never done before.
Anyways, I then tried the clockmod img, and it went through the exact same process... but neither got me to recovery
Edit: Well I have to get to an important class unfortunately. I'll be back at it after a while.
- 02-01-2011, 02:59 PM #22
Well how about that, after running to class it was canceled. haha. anyways yeah, the clockmod file you linked me to. I've tried flashing RA's two different ways, and now I've tried to flash Clockmod... and they've all been successful as far as installing goes... it seems like everything thats wrong happens in the boot sequence. But... I'm a noobie, so I can't say that with certainty.
- 02-01-2011, 05:56 PM #24