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

Root Location Specific Boot Loop Issue

L

LumpyLouis

Newbie
I have an odd problem that I cannot figure out. I have had my EVO LTE for a year and a half and have always driven the same way to work. About a week ago, my phone reset on the way to work and looped for about a quarter mile down the road. It then happened in the same place on the way home (and boot looped) and has happened every day since then. I was running the latest Viper4G Rom at the time but have since done a complete wipe and installed CM10.2 stable. The issue is still happening. I put my phone in airplane mode this morning and no bootloop. Any suggestions (other than a new route to work)? Thanks much
 
I am s-Off. I'll follow the steps of your guide and report back, thanks.

Update: I have successfully updated to 1.13.11.0830. I will see if I have the issue again on my way home today.
 
OK, no dice. boot looped on the way home and on the way in this morning. Airplane mode still protects it though. Its a pretty busy road and part of town. I wonder if Im the only one having this problem. Any other suggestions?
 
I'm running an older version of PAC ROM with Haunted Kernel. I've been on this build for awhile without issue.

I don't have this all tacked down, yet, but I've been experiencing odd boot loops from out of nowhere for the last 2-3 weeks. The device is completely unreliable - even when it wakes, apps will not update and some are simply inaccessible. Issues started random and got worse [or so it seems]. I haven't noticed a specific pattern, only that sometimes the phone works perfectly...others, the screen is off and won't turn back on. The device lights up, but no screen action. Simulating a battery pull does nothing. There is no way to get into Recovery.

The device boot loops in two different ways. the first is like a power issue. No charging lights and the phone sits there buzzing every 20 seconds like it wants to start up, but cannot.

The only way I've been able to get the device out of this state has been to plug it in and out of a power supply - sometimes, when I'm lucky, the screen will light up and the phone will work. The device is not recognized in ADB, so I can't use the command prompt to interact with it.

The last time I got the phone screen to come on, it was boot looping the Welcome screen. I immediately dove into Recovery to find there was no storage recognized...so, no ability to restore back ups. I was able to boot directly into the phone from there without issue.

I did notice Goo was prompting me for a ROM update prior to these issues. I'm curious if somehow the ROM was updated via Goo without my interaction. It seems unlikely, but the issue kinda stinks of a botched update.

Snooping around the various forums, I'm seeing people report devices working perfectly, then displaying these symptoms, so I thought I'd share my experiences.

If I can get the device to wake up again, I might play with kernel settings to see if it helps. If I am able to identify a root cause or fix, I'll circle back to share.

Three.
 
Sorry, I didn't add the detail, because I can't check my device to be certain. Based on my notes, which should be correct, I'm running PAC 9-1-2013 [super stable] with Haunted 29 (ver 3, maybe).

I'm going to say I'm on the latest firmware, unless I missed something in the last two weeks.

I've been S-OFF.

Yesterday, I was able to get the device working, but there's no method to it. Sometimes, I'll plug it in and I'll get a screen response, which is all I need to get into recovery - from there I can boot normally and the phone runs fine. I can't restore anything [no drives are recognized in recovery], but I can reboot system and get the phone to come up. Everything worked until right before bed, I set my phone on the table and it went to sleep. Within a minute it was bootlooping...and has been since.

It's like a non-responsive bootloop - no lights, no screen, just a buzz every 30 seconds until the battery finally dies.

I was settled that it was failing hardware until I saw a few random reports that seem similar to me in symptom and timing. I don't know...I enjoy a good mystery.
 
Not to repo the thread, but my issue has inexplicably stopped happening. Probably had something to do with the data towers in the area on the fritz.
 
Yea dude, I hijacked your thread.

If necessary, I can start a new one. :)

Was able to get into recovery and noticed the internal storage is hosed...twrp says it can't mount sdcard and similar errors. When I get into the office, I'm going to try to reformat, then reinstall. Right now, I have no OS, can't install new roms or restore backups.

The good news is I'm not boot looping! ...and, I at least see some corruption that I hope can be fixed by reformatting. Worse case...returning to stock and relocking? I'll report back after I reformat.
 
Quick follow up...she's dead, Jim. It was a slow crawl to the bottom, but I eventually lost (most) signs of life. The best I could get was a charge light to come on for about 20 seconds before it went into a dark-buzzing-bootloop. No more HTC screens...no access to recovery...no ability to reach the device via the command prompt.

Honestly, it's the closet thing to a brick I'd ever seen. I'm still completely at a loss as to what happened.

Replacement device is on its way.
 
You must log in or register to reply here.
Back
Top Bottom