I have a nexus 5x which got into a boot-loop when I applied android 8 beta.
this is for like about 10 months ago, so I barely remember what happened.
I do not remember how I managed to get the device locked again. :|
but I heard from my friend that the boot-loop fix image is out and I wanted to fix the phone because my current phone is killing me.
as I got it up and running I saw the locked text in the bootloader. I user fastboot flashing unlock but got an error that stated that it could not be done.
I tried enabling usb-debugging from adb but I had/have no clue what went on. the only thing I know is that I'm seriously stuck with a phone that I need.
So, PLEASE help me. I absolutely have no idea what to do. as far as I'm concerned I only need to get past the usb-debugging and therefore the locked state. after that I'm all good and able to flash the boot-loop fix.
so, what should do guys? (desperately asks)
mrafee113 said:
I have a nexus 5x which got into a boot-loop when I applied android 8 beta.
this is for like about 10 months ago, so I barely remember what happened.
I do not remember how I managed to get the device locked again. :|
but I heard from my friend that the boot-loop fix image is out and I wanted to fix the phone because my current phone is killing me.
as I got it up and running I saw the locked text in the bootloader. I user fastboot flashing unlock but got an error that stated that it could not be done.
I tried enabling usb-debugging from adb but I had/have no clue what went on. the only thing I know is that I'm seriously stuck with a phone that I need.
So, PLEASE help me. I absolutely have no idea what to do. as far as I'm concerned I only need to get past the usb-debugging and therefore the locked state. after that I'm all good and able to flash the boot-loop fix.
so, what should do guys? (desperately asks)
Click to expand...
Click to collapse
Can you boot into the stock recovery? Try sideloading the latest Oreo update zip. I'm not sure that will do anything, but worth a try.
Sent from my [device_name] using XDA-Developers Legacy app
I can boot into bootloader and stock recovery, but doesn't that action require usb-debugging to be enabled?
mrafee113 said:
I can boot into bootloader and stock recovery, but doesn't that action require usb-debugging to be enabled?
Click to expand...
Click to collapse
No, it shouldn't.
Sent from my [device_name] using XDA-Developers Legacy app
Related
Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!
Hi,after i wiped all data in twrp my nexus 5x stucked in bootloader mode(when you have to choice between recovery,power off,reboot etc.) and my bootloader is locked,before i had an android 7.0 rom, what can i do?
Please help me ,i've got any idea.
Can you still boot to twrp? You can sideload a custom Rom zip from you pc if you can.
Sent from my Nexus 9 using XDA-Developers mobile app
Any chance OEM Unlock was already enabled to run bootloader unlock command? Long shot I guess.
Otherwise use TWRP if you can get it.
If you ever Unlock you bootloader. Never lock it.
Sent from my Nexus 5X using Tapatalk
I can't go to twrp and i've got no chances to unlock oem bootloader.
I think i will try to flash the .tot file from pc.
Any idea?
I have the same problem now. Bootloader Locked, OEM and USB debugging not enabled in developers mode.
A few hours after android 7 update, phone booted itself and getting stuck at google dot animation.
I have tried adb sideloading stock image, it would finish successful but will get stuck at same google dot animation on reboot.
Please help. I'm out of ideas.
Have you found any solution?
vmchakka said:
Have you found any solution?
Click to expand...
Click to collapse
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
Yes, for some reason, a number of N5X devices are having an issue after recent updates where they subsequently will not boot and it is not possible to boot to Recovery Mode - in effect when they try the system continues trying to complete the system reboot that occurs at the end of the update. It would appear this happens because the update reboot didn't finish properly and did not clear a well defined in memory post box. I have raised this issue with the Community Manager for escalation to the development team as something is wrong (hardware or software still to be determined). In the meantime, if this occurs all that can be done is return the device for warranty replacement.
Click to expand...
Click to collapse
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Huskehn said:
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Click to expand...
Click to collapse
I have exactly same problem like you Huskehn.
So far I tried with all OTA's with a successful installation, yet wouldn't stop it get stuck at dot animation.
I also mailed back my seller for warranty replacement. Turn's out the seller disappeared from ebay and the office contact is unreachable. Talked to ebay helpline and the passed it on to paypal 180 days money back guarantee. Paypal asked me to chargeback from bank as the seller is out of reach. I have managed to talk to bank and get chargeback.
I am not sure if I want to risk buying same 5x now also it is constantly bugging me that I wasn't able to get a success fixing this device. Waiting for a Solution, If you can get yours to work, let me know. cheers
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.
Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...
enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.
Mine is @ LG as I haven't bought from Google... Let's see...
talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.
Nexus are impossible to brick, unless you flash stock factory image...
I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
ADB
Omnitrix4m3 said:
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
Click to expand...
Click to collapse
I sideloaded via ADB in the recovery. But now the recovery wont even showing
indian84 said:
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Click to expand...
Click to collapse
Ok the device suddenly boot up. I acted fast and unlocked the bootloader. But when everything is going fine. THE DEVICE BOOTLOOPED AGAIN. But now my bootloader is unlocked. So I flashed 6.0.1 it booted up and again bootlooped :crying:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
iSimon said:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
Click to expand...
Click to collapse
LG never claimed it was a hardware issue for the 5X officially. Though due to some lawsuits they are extending the warranty on a case by case basis. The did acknowledge a hardware issue for the G4, which started production around the same time as the 5X.
What seems to happen is the later OS updates expose a hardware issue. Maybe by running a bit hotter. Some people, like me, had slightly reduced battery life after 7.1.2, which means the phone was drawing more power and heating up slightly more than before. My phone was on 7.1.2 for about 2 weeks before it just died while I was using it. Didn't seem to be a bootloop issue at first, but after fiddling around with it, and trying to fix it, that's what it ended up doing. Mine would never get into recovery either, until I used a hair dryer to heat the CPU on the motherboard since I didn't have a heat gun. I managed to reinstall the OS, but it took a heat gun to actually to get it to boot again. However, it lasted 9 hours then started bootlooping.
synesthete said:
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
Click to expand...
Click to collapse
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
aerolock said:
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
Click to expand...
Click to collapse
I had mine fixed for free under warranty, so you should too, as long as it doesn't have significant other damage from drops or water, etc. I had rooted, unlocked and flashed many times. I did send it in stock, though, by flashing the stock factory images (mainly to clear personal data). I don't know what the official rules are about rooting and warranties, but I think that usually the Nexus phones allow you to unlock the bootloader and flash third party software without completely voiding the warranty. They are partly made as affordable developer units, anyway. Obviously, if you brick the phone by doing that stuff it is your fault, but if it is due to a defective part in your device, then they should be responsible to fix it. Even in the past I have been able to get an HTC phone repaired that was fully rooted/unlocked, because it had nothing to do with the hardware issue. Even if they say that your warranty is voided in the fine print from unlocking, sometimes companies will do the right thing and remedy issues that they are at fault for. Contact them, be polite, explain the problem/symptoms and ask if there is something they can do to help. When I contacted LG on their web chat system, I basically told them that the symptoms were most likely caused by a hardware issue and it seemed that the flash chip was failing. I told them that Google recognized the issue and has been refunding customers with the problem. I asked LG if they could repair, replace or refund my phone. The process went as smoothly as it could have gone for a situation like that (Other than unrelated issues with Fedex).
I would recommend just contacting LG, if you device is otherwise in good condition (aside from the bootloop). It can't hurt to try. Just know that the process of shipping it out, repairing, and shipping back might take about a week. Good Luck!
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
aerolock said:
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
Click to expand...
Click to collapse
I bought mine brand new on eBay. I rooted, Rommed, and otherwise tinkered with it unapologetically then ran into this bootloop issue almost a year later. I was able to contact LG support, send them a copy of my invoice from eBay showing that it was bought new and the date. I sent it off and they fixed it for free (replaced the main board) under warranty. Just go through LG support and they will almost certainly get you taken care of. It took a little over a week, but it sounds like you have a phone you can use during that time.
I purchased a 5x through Amazon over year ago and it is now bootlooping. I have tried all known fixes. I am in the US and I purchased the international version unknowingly. The LG US support site does not recognize my H791 version and I doubt that I can send it overseas. Am I out of luck getting this phone fixed?
Sent from my Nexus 6P using XDA-Developers Legacy app
Hi. So here is the state of my N 5X.
Phone has bootloops. I cannot get into recovery mode since as soon as I try to do it, the phone just restarts and then bootloops.
Right now, I'm stuck on the bootloader screen. It shows secure boot enabled and device state locked.
I've donwloaded the factory image from Google, however I won't be able to flash it since the phone can't boot and I can't disable allow OEM unlocking. What should I do?
abhilash2908 said:
Hi. So here is the state of my N 5X.
Phone has bootloops. I cannot get into recovery mode since as soon as I try to do it, the phone just restarts and then bootloops.
Right now, I'm stuck on the bootloader screen. It shows secure boot enabled and device state locked.
I've donwloaded the factory image from Google, however I won't be able to flash it since the phone can't boot and I can't disable allow OEM unlocking. What should I do?
Click to expand...
Click to collapse
There's lots of threads discussing this same issue. You're not a special snow flake. Look for BLOD in this and the general sub forum.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
There's lots of threads discussing this same issue. You're not a special snow flake. Look for BLOD in this and the general sub forum.
Click to expand...
Click to collapse
Lol, chill dude. I never said that I was a snow flake. No need to get angry.