I've been tasked to fixing a friends Nexus 5x bootloop issue, I've have having difficulty getting into the recovery partition even after a flash. Any hint or tips to fix the bootloop issue? Have tried using the Fastboot Erase/Format, but I'm still hitting the bootloop.
It's written often here: try to get more access by heating or cooling the phone. If you succeed, you can use a kernel which turnes the big core off.
Related
I have a LG G3 with rooted stock rom running xposed.
So I pulled my phone out of my pocket today only to see the Verizon boot logo in effect. I was thinking "that's weird, guess my phone needed to reboot? Strange." But the only problem is it never stopped. It will only boot up to the lock screen and occasionally it will display an error message telling me the systemui has stopped. Then about 10 seconds later, it reboots itself. It continues this process until I pull the battery.
I've tried booting into safe mode, no luck. It doesn't even actually boot into safe mode (it doesn't say safe mode in the bottom left corner.)
I tried wiping the cache, no luck.
I don't want to just do a factory reset because that hasn't seemed to help anyone else with this issue as far as I've seen. I have not found any helpful information on how to fix this problem.
My question is, what do I do? I feel lost on this subject. Normally I've always been able to diagnose problems on my own, but not in this situation.
I have all my apps and data backed up to Titanium Backup on my SD card.
Any suggestions?
Xposed is more than likely the cause. Boot into TWRP and open a terminal, then type the commands as shown in the OP of this thread to bypass it...
How to Disable Xposed on Lollipop when stuck in Bootloop
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
My screen froze today so I rebooted. It immediately went into a bootloop. Ive been running Pure Nexus ROM with no problems for months now so I have no idea what happened. I can get into fastboot mode however it will not reboot nor boot into recovery. Wusfresh toolkit detects my phone in fastboot but no commands work. I tried booting into recovery then I even tried to flash stock. It went thru the whole flash procedure but goes right back into the bootloop. I am unable to manually flash stock because as I stated nothing works past fastboot mode and since it flashed stock now my usb is not enabled. Bootloader IS unlocked. I have no idea what to do at this point. Ive been messing around with Nexus phones for years and have never been unable to at least flash stock to fix any problems. Its been months since Ive messed around with my phone and its killing me that out of the blue it does this and I might have to spend Christmas money to replace my phone. Any help would be greatly appreciated!
Variant-LGH790 32GB
HW Version- rev_1.0
Bootloader Version-M8994F-2.6.36.2.20
It's a HW problem, because LG used some ****ty solder for the emmc and cpu. So the connection between the cpu and the motherboard is weak after some time, especially if you do stuff on your phone that heats up the cpu. You can try to put in in the freezer for like 10 minutes, then it started working for some people. Or you can open your 5x, and then take a heatgun or hair dryer and heat up the cpu for some time and press on it (you can find a picture of each chip on the motherboard on ifixit). This isn't a fix that will work for years, but at least, you can backup your data, flash stock and then send it to the repair centre.
Sent from my Nexus 5X using Tapatalk
When the phone bootloops, did you try pressing the volume down button? If it launches recovery then it means bootloop is caused by stuck power button.
Thanks for the suggestions guys. Nothing worked so I'm just going to call LG and see about a refund.
Recently, whenever I restart or cold boot my Nexus 5X, it boots into TWRP. I can still get to the OS by selecting Reboot>System in TWRP. But the weird thing is that I haven't changed TWRP version or done anything to the OS recently, this just started happening. Does this mean the bootloop is coming for me or is something else going on?
This is happening to me as well. Planning on reflashing factory images along with TWRP and seeing where that takes me. Have you started bootlooping or stayed the same?
Did anyone figure out how to fix this issue? It isn't a huge deal, but I'm worried that if my phone crashes, it may reboot during the night and I'll miss an alarm. Did you guys just reflash factory images to resolve this?
Check settings of apps related to booting or TWRP (not from recovery mode)
jmath07 said:
Recently, whenever I restart or cold boot my Nexus 5X, it boots into TWRP. I can still get to the OS by selecting Reboot>System in TWRP. But the weird thing is that I haven't changed TWRP version or done anything to the OS recently, this just started happening. Does this mean the bootloop is coming for me or is something else going on?
Click to expand...
Click to collapse
Mine has been doing this also ever since I got a replacement phone, I thought it was weird but thought maybe it was something I flashed that isn't sitting right... Its a minor issue and I dont reboot too often so I havent done anything about it. I have this replacement for about 3 months and no other problems have started....
try reflashing bootloader and recovery via fastboot
I was trying to backup using Titanium backup 8.0 and my phone hard crashed, I allowed it to reboot and tried again (same thing), however this time it is very-very messed up. It continually cycles at the LG screen, I've been able to get into TWRP twice, but then it randomly reboots from there as well after the screen locks up, after about 20 seconds. At this point the phone is stuck in a boot loop and is unable to proceed, now luckily I have a v20 coming, sadly not for over a week. I can not see how titanium backup resulted in a boot loop that does not end unless it corrupted the system partition, but even then it should not have affected TWRP, which is also encountering issues and is not stable enough to attempt a recovery of the system. So any suggestions as to a cause and a solution to it looping on the LG screen?
After the first crash from TI it booted fine and ran well enough (no issues encountered), and doing a reboot restarted cleanly, it was the second crash that seems to have done it in.
ERIC
egandt said:
I was trying to backup using Titanium backup 8.0 and my phone hard crashed, I allowed it to reboot and tried again (same thing), however this time it is very-very messed up. It continually cycles at the LG screen, I've been able to get into TWRP twice, but then it randomly reboots from there as well after the screen locks up, after about 20 seconds. At this point the phone is stuck in a boot loop and is unable to proceed, now luckily I have a v20 coming, sadly not for over a week. I can not see how titanium backup resulted in a boot loop that does not end unless it corrupted the system partition, but even then it should not have affected TWRP, which is also encountering issues and is not stable enough to attempt a recovery of the system. So any suggestions as to a cause and a solution to it looping on the LG screen?
After the first crash from TI it booted fine and ran well enough (no issues encountered), and doing a reboot restarted cleanly, it was the second crash that seems to have done it in.
ERIC
Click to expand...
Click to collapse
This may not be necessarily an app fault but cpu intensive processes like restoring many apps can enforce a very known hardware fault. Check the first 3 digits of your serial. Starts it with 5xx or 600-602? Then you will likely have the ilapo/bootloop issue which means you need to replace the main board / warranty replacement.
.
Sent from my LG-H815 using XDA Labs
Yep, that is likely it 505K.... Serial. oddly I can get into TWRP sometimes, but can not get to fastboot at all, sometimes I can even get Android to boot, but never complete, so it does not seem completely crashed, only mostly so.
Glad I odered a new phone today,
Eric
Phone frozen on boot screen
Today at 4am, i woke up to this bizzare response of my galaxy f41.
Don't know why this has happened?
The phone was idle the night before.
No buttons work to force restart this device.
Waiting for battery to run out.
Tried holding the power button for 30 seconds, google says motherboard failure, or failure at auto restart (i did not set auto restart)
This might help.
blackhawk said:
This might help.
Click to expand...
Click to collapse
Thanks
Did not try method 1 (because Android system repair was required)
Method 2 worked flawlessly
Vivek_Singh_Awesome said:
Thanks
Did not try method 1 (because Android system repair was required)
Method 2 worked flawlessly
Click to expand...
Click to collapse
Yay!
Clear the system cache from the boot menu.
Phone freezes and restarts- sometimes gets stuck at boot loop.
It keeps happening several times a week. I usually use that (hard restart) method to solve it. But it became quite a nuisance. Any way to solve it for good? I still don't know what's causing it.
Claws_77 said:
Phone freezes and restarts- sometimes gets stuck at boot loop.
It keeps happening several times a week. I usually use that (hard restart) method to solve it. But it became quite a nuisance. Any way to solve it for good? I still don't know what's causing it.
Click to expand...
Click to collapse
Does it stop happening in safe mode? If so you likely have a very buggy 3rd party app. Remove it.
Otherwise, possible malware or rootkit.
Factory reset. Reflash to stock rom if that fails.
If all that fails possible hardware failure.
Take any signs of system instability on an Android seriously as its not normal. Often the only warning you get before a boot loop.
blackhawk said:
Does it stop happening in safe mode? If so you likely have a very buggy 3rd party app. Remove it.
Otherwise, possible malware or rootkit.
Factory reset. Reflash to stock rom if that fails.
If all that fails possible hardware failure.
Take any signs of system instability on an Android seriously as its not normal. Often the only warning you get before a boot loop.
Click to expand...
Click to collapse
I don't always have access to this phone. Plus this issue is highly random.
There is an option to send log reports to Samsung devs. Is there Any way i can access these logs? I think these logs will help in finding out if there is a hardware or software issue.