Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,802,998 Members 39,334 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Bootloop - Have tried just about everything

Tip us?
 
PainFly23
Old
#1  
Junior Member - OP
Thanks Meter 3
Posts: 15
Join Date: May 2014
Default [Q] Bootloop - Have tried just about everything

Well here I am, stuck in a bootloop after trying everything imaginable.

The bootloop popped up out of nowhere while after using Xposed to perform a soft reboot. The Google logo comes up, the bootanimation begins to play, then the phone restarts back to the Google logo. At the time I was running LiquidSmooth with DirtyV.

I've tried:
-Disabling Xposed
-Reflashing my ROM
-Clearing Data, cache, dalvik
-Flashing a new ROM
-Formatting everything I could find in CWM recovery
-Flashing the stock 4.2.2 factory image
-And even using TWRP to reformat from ext4 to f2fs for the heck of it.

And still the problem persists. I'm really at a loss here with no idea what could be causing it, other than some sort of hardware issue. The bootloader and recovery both work perfectly, and the logcat I was lucky enough to pull had no indication that anything was going wrong during boot. If anybody has any idea as to what could be causing this and if it can be fixed, or if anybody has a similar problem, please share.
 
mrgnex
Old
#2  
mrgnex's Avatar
Senior Member
Thanks Meter 287
Posts: 974
Join Date: Jan 2013
Location: Vlaardingen
Did you flash the factory image via fastboot? It could be a dead emmc.. To check that just lock the boot loader again. If it's unlocked on reboot your emmc is dead.

Sent from my Galaxy Nexus using XDA Free mobile app
SΛMSUNG/Google Galaxy Nexus
ROM: Vanir Nightly
Kernel: A.S.K.P. Patty Remix

SΛMSUNG/Google Nexus 10
ROM: Vanir Nightly
Kernel: Stock Vanir
 
PainFly23
Old
#3  
Junior Member - OP
Thanks Meter 3
Posts: 15
Join Date: May 2014
Quote:
Originally Posted by mrgnex View Post
Did you flash the factory image via fastboot? It could be a dead emmc.. To check that just lock the boot loader again. If it's unlocked on reboot your emmc is dead.

Sent from my Galaxy Nexus using XDA Free mobile app
Factory image was flashed from fastboot, yes. The emmc appears to be fine too, judging by the check you suggested. I locked and unlocked the bootloader again powering off each time in between, and the changes stuck.

I'm not entirely sure what it could be at this point. I was messing around with some new overclocking settings at 1.6 GHz, but I'd imagine that if that caused a problem with the processor then recovery and fastboot wouldn't be working like they are. That and the reboots are too predictable and consistent for me to consider it a processor problem (but what do I know). I'm starting to think the soft reboot I did may have messed something up...
 
DR3W5K1
Old
#4  
Senior Member
Thanks Meter 215
Posts: 402
Join Date: Aug 2012
Quote:
Originally Posted by PainFly23 View Post
Factory image was flashed from fastboot, yes. The emmc appears to be fine too, judging by the check you suggested. I locked and unlocked the bootloader again powering off each time in between, and the changes stuck.

I'm not entirely sure what it could be at this point. I was messing around with some new overclocking settings at 1.6 GHz, but I'd imagine that if that caused a problem with the processor then recovery and fastboot wouldn't be working like they are. That and the reboots are too predictable and consistent for me to consider it a processor problem (but what do I know). I'm starting to think the soft reboot I did may have messed something up...
IMO sound like /system is stuck in a read only state. Possibly all of your partitions.

---------- Post added at 01:18 AM ---------- Previous post was at 01:17 AM ----------

Also let it be noted there is no known fix for this issue.
 
PainFly23
Old
#5  
Junior Member - OP
Thanks Meter 3
Posts: 15
Join Date: May 2014
Probably not a read-only problem since I can flash a ROM and see the new bootanimation come up. Flashing images (like factory images or custom recoveries) through fastboot also works fine.

Regardless, this problem probably goes pretty deep (definitely a hardware failure) and doesn't seem like anything I'd be able to fix.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes