• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Bootloop with no recovery.

MizzouBrent said:
What? Why were you running an RUU if you're rooted? All you need to do is flash a ROM to do an update, even if you wanted to update a stock rom. Running an RUU will overwrite everything, including your recovery. Do you still have S-OFF? If so, then all you need to do is flash a custom recovery (Amon RA) via the bootloader. If you have S-ON, then you will need to run Revolutionary again.

All you have as your recovery right now is the HTC recovery, which is meant to do one thing....install HTC OTA updates.
Click to expand...

ocnbrze said:
yep mizzou is correct. so just to make sure can you boot up still? if not then running revolutionary will not work. which ruu did you run? try this one:PC36IMG_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed.zip
Click to expand...

At the moment I cannot get into any recovery I flash; clockwork or amon ra. I still have S-OFF. Even though the recovery seems to flash successfully.

The phone bootloops at the white HTC splash screen. I can get into bootloader, but cannot access a recovery.

I will try to find a custom rom I can flash via bootloader and see if i can get the phone to boot past the white HTC screen.

I was running MIUI before it self rebooted then landed in the boot loop. Before that I had flashed the latest stock RUU then re-rooted (after loosing root) with revolutionary.io. Now I have tried to flash the newest/any stock RUU in the hopes that it would put the phone in a workable state. No luck so far.

Thanks for the replies.
 
ocnbrze said:
ok, now i see the picture. do you know what your hboot was when you first rooted the phone?

here is te sprint lovers rom that you can flash via hboot:
[ROM] 08/03/11 | SPRINT LOVERS | 2.3.3 | 4.24.651.1 | Radio/Wimax/PRI All-In-One
Click to expand...

Thanks for the rom. Sadly I do not know what Hboot I was at before all of this.

I am currently now on 2.16.0001.

I flashed the Sprint Lovers rom, everything flashed fine. Rebooted, same symptoms.

I then flashed Amon Ra, flash went fine. Rebooted, same symptoms.

edit:

currently at hboot 0.76.2000

EVT3 ENG S-OFF

got there with eng-PC36IMG.zip
 
busyychild said:
Thanks for the rom. Sadly I do not know what Hboot I was at before all of this.

I am currently now on 2.16.0001.

I flashed the Sprint Lovers rom, everything flashed fine. Rebooted, same symptoms.

I then flashed Amon Ra, flash went fine. Rebooted, same symptoms.

edit:

currently at hboot 0.76.2000

EVT3 ENG S-OFF

got there with eng-PC36IMG.zip
Click to expand...

ok so now you have hboot .76. out of curiosity what did you use to accomplish this?

before you rooted were you on froyo or gingerbread? when you rooted was your phone updated to the current ota (at the time)?

i'm just trying to get a timeline and see if we can figure out what your specs were intially. also did you first root with unrevoked? or revolutionary?

my thinking is that you have messed around with hboots and different ruu's that it might be confusing the phone. if you have an old hboot with newer software or radios could be a bad combo.

and one last thing, what is your baseband or radio now?
 
Comments are in line.

ocnbrze said:
ok so now you have hboot .76. out of curiosity what did you use to accomplish this?

used this:

eng-PC36IMG.zip

before you rooted were you on froyo or gingerbread? when you rooted was your phone updated to the current ota (at the time)?

Gingerbread. When I initially rooted i used unrevoked, when I got my phone back in oct 2010. When i lost root (a week ago) due to flashing the most current RUU i used revolutionary to gain root back.

i'm just trying to get a timeline and see if we can figure out what your specs were intially. also did you first root with unrevoked? or revolutionary?

I initially rooted the phone back in oct 2010 with unrevoked.

my thinking is that you have messed around with hboots and different ruu's that it might be confusing the phone. if you have an old hboot with newer software or radios could be a bad combo.

and one last thing, what is your baseband or radio now?

Right now I have radio 1.36.00.04.02. I am running HW Ver 4
Click to expand...

To give a background. I was getting fed up with CM7 which I had been running for months. I wanted to go stock for a while. So I ran the latest RUU. When I did I lost root (I was still S-OFF). So I ran Revolutionary.io to gain root back. After doing that I decided to give MIUI a shot. Flashed it, it worked great. Flashed the latest available radios that I found on calkulins site:

http://forum.xda-developers.com/showthread.php?t=715485.

Everything was running fine till something FC'd on MIUI, it rebooted and went into the boot loop of death. Since then I have flashed about every RUU/zip I could get my hands on to rectify this problem. No help so far. I have been able to downgrade from the latest HBOOT which may be a good thing for everyone. Im not sure.
 
do you have a link as to where you got the eng PC36IMG file? and can you get into recovery? in your previous post, you mentioned that you rebooted after flashing amon ra. just curious of you can get into it at all.
 
ocnbrze said:
do you have a link as to where you got the eng PC36IMG file? and can you get into recovery? in your previous post, you mentioned that you rebooted after flashing amon ra. just curious of you can get into it at all.
Click to expand...

The link to the engineering PC36IMG is embedded in my post. You can click it. Or just go here :)

http://www.mediafire.com/?m3wnmtguf4l]eng-PC36IMG.zip

I can not get into any recovery. I tried flashing many different versions of Amon RA and ClockworkMod with no success. When I choose recovery in HBOOT it bootloops each time (no matter what recovery I have "successfully" flash).
 
Yuck, there have been several of these cases posted here lately and there is a thread on XDA that details this. There is no workaround at this point. Are you still under warranty? It seems to occur more on phones that are running AOSP builds. It seems like something is corrupted (maybe the recovery partition) and it makes it impossible to boot your phone because you can't get into recovery to do anything. From what I have seen, no ruu files or anything that is flashable via the bootloader will work.

I find it hard to believe the the AOSP software is causing this. If it's a hardware issue, then any rom should be fair game. But maybe there is something to it. It makes it a lot less appealing for me to run AOSP, which I am doing seemingly 90% of the time on my Evo.

With all that said, it is SO important to make sure you read about everything that you flash to your phone. Obviously there was no reason to flash an RUU on a rooted phone. Nothing against you busyychild, but avoiding stuff like ROM manager, flashing unneeded RUU files etc has got to contribute a little bit to situations like this.
 
I have the same problem I have tried everything no luck.
does your phone show up in? adb devices
my phone does not show up in adb devices, it will show up in fastboot devices, when I go to fastboot flash recovery recovery.img it starts to flash and and then locks up phone.

I downloaded ruu 4.54.651.1.
when installing the ruu go to start, run, cmd, type %temp%
leave your mouse on the folders to highlight and see the size of the folders.
look for anything over 200mb
inside you will find the rom.zip, you have to search while ruu is running other wise
when ruu is complete the files delete. copy and paste rom.zip. then put on the sdcard and lable PC36IMG.zip
(make sure the rom is not labled zip.zip)
here is what I get in hboot vol up to update

parsing sd zip
1 radio v2 OK
2 recovery REBOOTs phone
3 bootloader OK
4 wimax
5 splash1
6 boot
7 userdata
8 system

reboots and comes back to bootloader

1 recovery ok
2 wimax ok
3 splash ok
4 boot ok
5 user data ok
6 system ok

finishes do you want to reboot device vol up yes

reboots back into boot loop, no recovery, adb devices nothing listed, fastboot devices has my serial number
but when I try to command fail bad signature.
I am s-on
hboot 2.16.0001
radio 2.15.00.080

stumped can anyone shed some light?
 
Took it into Sprint today. I have a new one on order. I have give or take 5 days before I have to exchange it to play with it if anyone has any suggestions or wants me to try something out.

Thanks for the help so far everyone.
 
This always seems to happen in waves. There will be no reports of it for months and then all of a sudden everyone has it.
 
swiftdevil said:
Thanks for replying, and I'm not trying to threadjack or anything. Unrevoked, and hboot is currently the ENG .76 with the 2.10 hex fix.
Click to expand...

don't worry about thread jack as this thread is old so it is all good.

we need a little more info as to what happened. were you doing anything in particular to get you in this situation? what rom were you on? have you tried any ruu's?
 
I wasn't doing anything out of the ordinary, just the usual txting/video chat/web surfing. It had been rebooting itself a lot lately though, like 3 times a day for the past 2 or 3 months, but I thought it was because the outdated ROM I was running (SavagedZen RC5) needed to be updated or something, or that the broken GPS needed to be fixed. Then I woke up last Monday to find my phone in a continuous bootloop.

When I first installed SavagedZen almost a year ago, the GPS had stopped working, and I finally got around to fixing it about a month ago. This involved creating a NAND backup, flashing back to a rooted Sense ROM, running the ##CLRGPS## fix, then restoring the NAND backup. It worked fine (except for the reboots) until the other day.

I have tried RUUs, but almost everything I attempt leads to the same bootloop; the one exception is when I flash a CWM recovery via fastboot, and then try to boot straight into recovery from the bootloader, the phone gets to the white "EVO 4G" screen and just stays there, no looping whatsoever.

I thought maybe the NV partition had bad blocks or something, so I ran 'fastboot oem partition_check all,' which showed a few bad blocks in the userdata and cache partitions, but everything else checked out.
 
swiftdevil said:
I wasn't doing anything out of the ordinary, just the usual txting/video chat/web surfing. It had been rebooting itself a lot lately though, like 3 times a day for the past 2 or 3 months, but I thought it was because the outdated ROM I was running (SavagedZen RC5) needed to be updated or something, or that the broken GPS needed to be fixed. Then I woke up last Monday to find my phone in a continuous bootloop.

When I first installed SavagedZen almost a year ago, the GPS had stopped working, and I finally got around to fixing it about a month ago. This involved creating a NAND backup, flashing back to a rooted Sense ROM, running the ##CLRGPS## fix, then restoring the NAND backup. It worked fine (except for the reboots) until the other day.

I have tried RUUs, but almost everything I attempt leads to the same bootloop; the one exception is when I flash a CWM recovery via fastboot, and then try to boot straight into recovery from the bootloader, the phone gets to the white "EVO 4G" screen and just stays there, no looping whatsoever.

I thought maybe the NV partition had bad blocks or something, so I ran 'fastboot oem partition_check all,' which showed a few bad blocks in the userdata and cache partitions, but everything else checked out.
Click to expand...
Have you tried flashing a Gingerbread PC36IMG in the bootloader? That should upgrade your HBOOT version, and potentially give you S-ON. If not, it should be pretty easy to do at that point.
 
If your phone was not fully booting why would you unroot it? That would just limit the options available to fix it, I'm sorry but I've heard of some dumb stuff on here. But I would think if your phone isn't booting you wouldn't want to try to unroot it because once you lose s-off you have totally screwed yourself, just saying....

sent from my evolution 4g running a bunch of awesome mods developed by some real sweet devs.
 
If he's not able to get to any recovery having root abilities isn't going to help him.

Sometimes the only solution is taking it in and getting it replaced
 
brianvillage5 said:
If your phone was not fully booting why would you unroot it? That would just limit the options available to fix it, I'm sorry but I've heard of some dumb stuff on here. But I would think if your phone isn't booting you wouldn't want to try to unroot it because once you lose s-off you have totally screwed yourself, just saying....

sent from my evolution 4g running a bunch of awesome mods developed by some real sweet devs.
Click to expand...

When people panic they don't think logically. And Rxpert has a valid point if it wont get past the boot screen S on or off isn't going to matter. S on at least you can take it to sprint and have them give you a new one or get that one fixed.

I do agree you have more options with S-off but its all circumstantial
 
brianvillage5 said:
If your phone was not fully booting why would you unroot it?
Click to expand...

Because this particular problem has been prevalent for over a year now and not a single fix or possible root cause has been posted.

brianvillage5 said:
That would just limit the options available to fix it, I'm sorry but I've heard of some dumb stuff on here. But I would think if your phone isn't booting you wouldn't want to try to unroot it because once you lose s-off you have totally screwed yourself, just saying....
Click to expand...

What would you do if your phone wasn't booting, then? Maybe your suggestion(s) will work? Just keep in mind that my ability to retain root comes a distant second to my ability to actually use my phone for something other than a fistpack.

My 4G has just been replaced by a 3D though, so I still have this one to mess with to see if I can get it to work again. If you're interested in helping tackle this problem too, then read this thread first so that you actually know why I tried unrooting.

Just one thing to note, however: you should probably try to refrain from passing judgement on others until you are certain that you're not the one saying dumb things. (just saying...)
 
CapThrowback said:
Have you tried flashing a Gingerbread PC36IMG in the bootloader? That should upgrade your HBOOT version, and potentially give you S-ON. If not, it should be pretty easy to do at that point.
Click to expand...

Haven't tried that. Are HBOOTs from rooted ROMs different from the stock RUU ROMs?
 
swiftdevil said:
Haven't tried that. Are HBOOTs from rooted ROMs different from the stock RUU ROMs?
Click to expand...
Rooted ROMs don't include HBOOT. It's an entirely different partition on the device. You can probably get your phone back to stock if you do that. I can post a link for you once I have a few more minutes (if no one else does it first).
 
I think the reason I can't get S-ON is because the phone won't boot into recovery, which is where I'm supposed to flash the unrevoked S-ON tool; so no matter what, S-ON isn't possible. Is there some ultra low-level method to get this done?
 
You must log in or register to reply here.
Back
Top Bottom