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

Root Most hard to figure out bootloop I've experienced or read about.

Y

yamiyugi00

Newbie
Okay everyone, I've got a stumper for you.


My EVO 4G is stuck in a bootloop, it gets to the white EVO splash screen, stays for 3-5 seconds, then reboots to the same endlessly.

I had been using my phone normally all day, randomly it just started bootlooping in my pocket.

It was flashed to CyanogenMod 7.1, rooted with Revolutionary.

In my bootloader, when I hit recovery it just goes into the same splash screen bootloop. I know for sure I do have a recovery installed.

Things I've already tried:

-"Clear storage" option in bootloader

-Using RUU Supersonic the PC way to get my phone back to stock (takes me through the whole process with the loading bar and everything but then on reboot I get looped again)

-Reflashing ClockworkMod Recovery from my PC (doing this actually changed what happened when I hit recovery, it would stick at the white screen instead of looping)

-Copying a zipped PCIMG36 to my SD card. (It does the whole update process then I'm bootlooping once again. Also, this stopped the "stuckness" listed in the above parenthesis, now recovery bootloops me like normal.)

-Booting with no SD card inserted (nothing different)

If anyone has any ideas I'm willing to try anything because I absolutely do not want to spend money on a new phone and I'm not eligible for an upgrade for another six months.
 
Welcome to AF!!! I've heard of this happening before and there's no rhyme, reason, or solution to it....But before we jump to conclusions, which recovery are you running?
 
frenchy714 said:
Welcome to AF!!! I've heard of this happening before and there's no rhyme, reason, or solution to it....But before we jump to conclusions, which recovery are you running?
Click to expand...

The most recent recovery I flashed was ClockworkMod, before that I believe it was the one that came standard with Revolutionary which I believe is just a branded version of ClockworkMod.

frenchy714 said:
This seems to be something that only happens to Evo's running CM. If you haven't already, I want you to read this thread:

[Q] Evo 4G Stuck in Bootloop - xda-developers
Click to expand...

='(
 
We can try flashing a different recovery (Amon RA), found here. If you still continue to bootloop after that, well, you've read the thread.....There doesn't seem to be too much you can do except take it to Sprint.
 
I've seen a few cases just like this one. This is the main reason I do not run any cm roms.
I'm sorry my friend, I wish there was something we could do, but even the heads over at xda can't find a solution.
Best bet is to remove all evidence of root and take it back in. Ie: flash the s-on tool from hboot for your hboot version and take it in for a replacement. :(
 
frenchy714 said:
We can try flashing a different recovery (Amon RA), found here. If you still continue to bootloop after that, well, you've read the thread.....There doesn't seem to be too much you can do except take it to Sprint.
Click to expand...

Succeeded in flashing Amon Ra. Still didn't work. =\

What's the best way, having used Revolutionary and not Unrevoked that I can regain S-On?
 
yeah i do not think that amon ra will help this situation, but you are naming the file incorectly. the file name needs to be exactly PC36IMG with only the zip at the end. windows hides extensions so make sure that you have not added an extra zip to the name.

and you can't get to recovery correct?
 
ocnbrze said:
yeah i do not think that amon ra will help this situation, but you are naming the file incorectly. the file name needs to be exactly PC36IMG with only the zip at the end. windows hides extensions so make sure that you have not added an extra zip to the name.

and you can't get to recovery correct?
Click to expand...

That is what I named the file. And no, I cannot enter recovery.

At this point, I'd be happy with just regaining S-ON. I know my Sprint guy fairly personally, so he'd probably help me out if I just got back S-ON.
 
yamiyugi00 said:
That is what I named the file. And no, I cannot enter recovery.

At this point, I'd be happy with just regaining S-ON. I know my Sprint guy fairly personally, so he'd probably help me out if I just got back S-ON.
Click to expand...
are you placing it on the root of the card? that means not in any folder, just on the card.

what is your hboot?

also you can try this ruu:
PC36IMG

this is the s-on file. however, you will still have a cutsom rom and recovery. but from the looks of it you can't access either so it should not matter. if you want you can flash the latest ruu from here:xda-developers - View Single Post - Supersonic Shipped ROMs 9/8/2011.
 
ocnbrze said:
are you placing it on the root of the card? that means not in any folder, just on the card.

what is your hboot?

also you can try this ruu:
PC36IMG

this is the s-on file. however, you will still have a cutsom rom and recovery. but from the looks of it you can't access either so it should not matter. if you want you can flash the latest ruu from here:xda-developers - View Single Post - Supersonic Shipped ROMs 9/8/2011.
Click to expand...

Yes, I'm aware of that.

My hboot is 6.16.1002

I listed that answer before I tried that first RUU it gave. It got me S-ON status! My phone is otherwise still fubar though.

I tried the step-by-step guide on that site and nothing came of it.
 
Wow, I'm glad I read this thread. Sorry it happened to your evo, but I was just thinking of switching to CM in the near future. Hopefully this has been reported to the CM guys right? Is there any other AOSP rom someone can suggest that would be as good as CM?
 
theTrashcanMan said:
Wow, I'm glad I read this thread. Sorry it happened to your evo, but I was just thinking of switching to CM in the near future. Hopefully this has been reported to the CM guys right? Is there any other AOSP rom someone can suggest that would be as good as CM?
Click to expand...


Most of the aosp roms are cm based. But as every Dev says when they put a rom flash at your own risk. Were all taking chances flashing these roms . So the best we can do is not take chances on ones that have known issues especially ones like this that brick your phone.
 
This is an issue that has been brought up randomly over the past year or so. The cm team no doubt knows about it.
Unfortunately there hasn't been a solution found. If there was a way to provision all of the radios and such from hboot there might be a chance, from what I've read, but no one has figured out how yet. :(
Yet another EVO down. :(
 
You would think so, but everyone whose had this problem seems to have cm7. A quick search over on Xda shows a few threads of people experiencing it.... all running cm7

Causation....no

Correlation....yes


Its still a very small number of cm7 users
 
Rxpert83 said:
You would think so, but everyone whose had this problem seems to have cm7. A quick search over on Xda shows a few threads of people experiencing it.... all running cm7

Causation....no

Correlation....yes


Its still a very small number of cm7 users
Click to expand...

I was actually running MIUI but it's a variation of CM so.........

But after doing many different things to get my phone out of the death boot, I'm beginning to believe it has something to do with the latest radios for the Evo and CM. I wish I could get some feed back from all the users that have had the death boot and determine what radio they were on, PRI, NV.... and see if there is a correlation between the death boot and the newer radios. But unfortunately, there are so many different scenarios that there may never be an answer to why this is happening.
 
Well, I'm running all the current radios and CM7 has always worked fine, and all other roms whether they be aosp based or sense based. Maybe something about the source code for CM7 is more likely to cause it (note, maybe. Obviously it's all guessing) but hardware issues happen. My first Evo had to be replaced due to frequent reboots. Ocnbrze had the same issue. A friend of mine got his replaced due to the usb port always wanting to put the phone into car mode. You just never know. I'll gladly take the chance of a failure (again, assuming that running cm7 has anything to do with it) because you can find used Evo's online. And there are MANY users who flash like there's no tomorrow who never have any issues. So you just never know.

Good luck getting your evo returned. I guess one thing I would wonder about is in a situation like this where you can get into hboot (and thus your hboot version is viewable, with the big revolutionary heading) I wonder if that screws you out of the chance of getting your phone swapped out for a new one.
 
MizzouBrent said:
Well, I'm running all the current radios and CM7 has always worked fine, and all other roms whether they be aosp based or sense based. Maybe something about the source code for CM7 is more likely to cause it (note, maybe. Obviously it's all guessing) but hardware issues happen. My first Evo had to be replaced due to frequent reboots. Ocnbrze had the same issue. A friend of mine got his replaced due to the usb port always wanting to put the phone into car mode. You just never know. I'll gladly take the chance of a failure (again, assuming that running cm7 has anything to do with it) because you can find used Evo's online. And there are MANY users who flash like there's no tomorrow who never have any issues. So you just never know.

Good luck getting your evo returned. I guess one thing I would wonder about is in a situation like this where you can get into hboot (and thus your hboot version is viewable, with the big revolutionary heading) I wonder if that screws you out of the chance of getting your phone swapped out for a new one.
Click to expand...

Funny thing is, I rooted froyo and was NOT able to get s-on, thus I went and purchased a new Evo. And even stranger, I can change my hboot to whatever I like and even running older ruu's changes the hboot. So, this issue with the death boot is very strange and no one has any answer of how to fix it. Plus, if it's an issue with the NV, then you are screwed forever. :eek:
 
andygu3 said:
Funny thing is, I rooted froyo and was NOT able to get s-on, thus I went and purchased a new Evo. And even stranger, I can change my hboot to whatever I like and even running older ruu's changes the hboot. So, this issue with the death boot is very strange and no one has any answer of how to fix it. Plus, if it's an issue with the NV, then you are screwed forever. :eek:
Click to expand...

Exactly with the nv. It's rumored, not confirmed, that its the nv causing the death boot. If there was a way to clear those partitions out, reformat em, then reflash the good radios etc, it "should" fix the issue.
Accomplishing this is like trying to fix stupid.
 
Update, everyone!

I just got back from the Sprint store. The Sprint guy was someone who was on my side. He sat there for about thirty minutes trying to flash different recoveries and images to my phone. Eventually he threw his hands up and ordered a new phone. I smartly bought the insurance protection, so the whole thing didn't cost me a dime.

So my advice to anyone who has this happen, get the S-ON status and delete whatever may be on your SD card that could be incriminating. And buy the insurance! My new EVO is on its way, so I suppose this all has a happy ending.

Thanks so much to ocnbrze whose flash got me to S-ON.
 
yamiyugi00 said:
Update, everyone!

I just got back from the Sprint store. The Sprint guy was someone who was on my side. He sat there for about thirty minutes trying to flash different recoveries and images to my phone. Eventually he threw his hands up and ordered a new phone. I smartly bought the insurance protection, so the whole thing didn't cost me a dime.

So my advice to anyone who has this happen, get the S-ON status and delete whatever may be on your SD card that could be incriminating. And buy the insurance! My new EVO is on its way, so I suppose this all has a happy ending.

Thanks so much to ocnbrze whose flash got me to S-ON.
Click to expand...
nice i'm glad it worked out for you in the end. if you need help rooting your new evo when it comes in, you know what are where to go.;)
 
So what happens if you change the splash screen and then get hit by this bug? You're screwed right? It's a dead giveaway that your phone was rooted at some point.
 
You must log in or register to reply here.
Back
Top Bottom