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

Root Need help: Stuck in boot loop, can't install recovery

D

dieselmachine

Lurker
I was listening to music on my phone (EVO 4G w/ Cyanogenmod 7) and it just shut down. I tried to turn it back on and the 'HTC EVO 4G' white screen came up, disappeared, then came up again. It will keep doing this. I can get into the bootloader, but attempting to select 'recovery' instantly loads the white screen again and sends it back into the loop. I have tried updating the recovery to AR 2.3 using HBOOT, and it claims the installation was successful, but rebooting and attempting to select recovery results in the same thing.

My device does NOT show up when running 'adb devices'

My device DOES show up when running 'fastboot devices'

I CANNOT flash anything via fastboot. I get an error message which looks like this:

sudo ./fastboot-linux-i386 flash boot boot.img
sending 'boot' (1976 KB)... OKAY
writing 'boot'... FAILED (remote: not allowed)

I CANNOT get into Android at all, which means I CANNOT enable USB debugging. As ADB seems to rely on USB debugging to be enabled in order to 'register' the device, this means anything involving ADB is out of the question (correct me if this last point is wrong, I've not seen it posted anywhere (and I've been searching for hours), and is based solely off my own tests involving another phone which failed to register until USB debugging was enabled)

The info at the top of the bootloader screen reads:

SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19

I haven't added or edited anything on this phone in months. I've been running cyanogen (the same version, never updated) for months now, which no issues at all. This error came out of nowhere, and because it was through no action of my own, I have absolutely no idea what could be causing it.

What specifically is preventing me from flashing via fastboot? Is it that my version of HBOOT does not allow it? What is generating the "remote: not allowed" error when I try to flash? It states at hxxp://wiki.cyanogenmod.com/wiki/Fastboot "You must have an Engineering SPL, or an SPL that is S-OFF.". I don't know what an SPL is, but my HBOOT indicates S-OFF. Is this what it's referring to? Is it possible that, because my phone is S-OFF, and supports SOME functions of fastboot, that the preceding statement is true, and doesn't actually indicate the ability to flash, only to run basic commands?

Today was abnormally warm in Seattle, and I left the house wearing a leather jacket, not expecting it to be nice out. My phone was in a pocket of a leather jacket in 70 degree weather, could I have overheated it and caused permanent damage? Does this failure sound like it could stem from that?

What would be the best plan of attack here? Sorry for so many questions, but I'm trying to learn as much as I can about a bunch of new things, I don't want to miss any important details.
 
Welcome to the forums!:D

Unfortunately, thats where the good news stops. Sounds like the bootloop of death to me. :(

There is no known cure for it or cause to why it happens. Some say CM7, some say rooting via unrevoked
 
Rxpert83 said:
Welcome to the forums!:D

Unfortunately, thats where the good news stops. Sounds like the bootloop of death to me. :(

There is no known cure for it or cause to why it happens. Some say CM7, some say rooting via unrevoked
Click to expand...

I believe this problem is from unrevoked as they intitialy Root Froyo ROMs by using an exploit in the NV Most issues I have seen from the bootloop of death stem from froyo.It was a way at the time to achieve S-OFF. I have talked with guys who were ruuning CM7 or MIUI when the breath of death ciezed thier precious phones Best we can guess at this time is that the NV is becoming corrorupt. At my last count none who rooted with revolutionary has suffered the fate it seems more and more people are becoming a club to a nasty ending
 
Yup, I've heard that NV corruption is the most likely culprit, but we still don't have a diffinitive explanation as to what causes it. I rooted my OG with Unrevoked and I rarely ran AOSP roms.
My wife runs the EVO now and it's still going strong.

I hope you don't have any issues getting it replaced. Sorry. :(
 
So I took my phone into Sprint, they saw it was rooted and said they couldn't deal with it there, and directed me to their replacement service. I paid the 100 dollar deductible and they overnighted a phone to me.

So I go into the bootloader to see my phone info, and they sent me a rooted phone. LOL. It says 'revolutionary' at the top, and has S-OFF already set.

Hilarious!
 
dieselmachine said:
So I took my phone into Sprint, they saw it was rooted and said they couldn't deal with it there, and directed me to their replacement service. I paid the 100 dollar deductible and they overnighted a phone to me.

So I go into the bootloader to see my phone info, and they sent me a rooted phone. LOL. It says 'revolutionary' at the top, and has S-OFF already set.

Hilarious!
Click to expand...

Wow, I've never heard of that before! :confused::confused:
 
You must log in or register to reply here.
Back
Top Bottom