Hi All,
My Nexus 5x 32 GB phone suddenly died on me last night. The situation as of now:
1. Cannot boot normally. Shows Google logo and everything goes dark.
2. Can boot into Fastboot with holding down power and volume down buttons
3. But not able to go into recovery. When I select Recovery in Fastboot mode, it just tries to reboot and the screen stays dark. Nothing happens.
4. The bootloader is locked. I think OEM protection in Developer tools is on, so not able to unlock bootloader through Fastboot commands.
What an I do?? Factory reset would be great, if option is there.
Please help!! Thanks.
Try to flash Factory image by command adb and fastboot if your pc recognized your nexus 5x
unlock oem if necessary After
Funny enough, I've got a very similar issue
I can boot into recovery though, but there's a catch, and I think it applies to everything past boot, the phone freezes and restarts after like 3-5 seconds.
I can't boot to system, as it takes way too long to boot up, but I can only see the first panel of the recovery before it dies and restarts.
I have flash official images, and even TWRP recovery to see what I can do, but this doesn't work out in the long run, as the issues are ever persistent
Thanks for the quick replies!
Tried everything, including Nexus toolkit... But nothing worked. So I finally took it to service center as its still in warranty. They said the problem is hardware related and it might have happened because of recent update. They also said they have been getting lots of phones with this problem. So they they are replacing the motherboard free of cost. Wish they could have given a new phone
Once again, thanks all!
Dude that's wild, this same exact issue literally happened to me 2 weeks ago while I was on tour. Was on 7.1.1 (Pixel ROM to be specific) and my 5X just died on me out of nowhere. Absolutely the same things happening here, would boot up, go black, and then start bootlooping. Could access fastboot, but I couldn't get into recovery. Called Google and got a replacement because it was definitely hardware failure and I was still under warranty (just a few days past a whole year). I wonder if the new 7.1 betas are breaking peoples' phones
Sent from my Nexus 5X using Tapatalk
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Scratch. said:
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Click to expand...
Click to collapse
Have you tried flashing the stock images? If you can get to fastboot, you can flash the stock image and unroot your phone. You should also then be able to lock your bootloader (if it is unlocked) and then do your warranty at that point.
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
so people saying android 7.1.1 brooking devices, so will that be safe to upgrade the phone from 7.0 to 7.1 .1 when stable release will be available ?
Scratch. said:
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
Click to expand...
Click to collapse
Sounds like the hardware bootloop issue that has been hitting 5x devices hard lately. Mine started looping last week and I had to send it in.
Are you still within your 1 year manufacturer's warranty? If so, you can call LG and report the issue to them. Your device may get fixed, but it was also reported Thursday that LG has started issuing full refunds because they ran out of the needed part.
The company have started offering refunds
https://www.neowin.net/news/lg-to-issue-full-refunds-to-customers-with-faulty-nexus-5x-handsets
Related
Hey Guys,
I've been rooting, unlocking bootloaders etc on android devices for a few years now but never had this problem.
I had a nexus 7 which was not rooted or unlocked and decided to do a factory reset from within android.
Device rebooted and was stuck on erasing data for 3 hours so I decided to boot into recovery, everytime I tried the device would reboot back to erasing data with the green android.
Next I tried fastboot, device is recognized but when attempting to unlock the bootloader using fastboot oem unlock command it gets stuck on 'erasing userdata'
I have also tried the fastboot erase user data and I'm getting the same issue.
I hope someone can help because I am out of ideas!!
Thanks
There is no known fix for this issue. Unfortunately Asus charged me $200.00 to fix mine (by replacing the motherboard).
Sent from my Nexus 9 using Tapatalk
fastboot oem unlock / erasing data hang
I know the last response was not very positive but as I seem to have hit the same problem as the original poster I thought I would try asking again with my scenario (which is slightly different) in case anyone has any ideas.
I have a Nexus 7 (2013) wifi. I have never tried rooting or playing with custom ROMs on it but after some suggestions that personal data (e.g. passwords, etc.) could be recovered from an Android device, even if you had done a factory erase I decided to encrypt it. This all went fine and this was while I was still back on 4.4.
I when through the upgrades to lollipop (5.0.1) all successfully but a few days ago I started to get an error 'com.android.vending has stopped' popping up every few minutes. I then noticed that the play store was not working and from some looking around these two issues seemed to be related. I then started to get some crashes (I could see these as when I went to use the tablet it was prompting for my encryption password). This seemed like a good time to try and clear down the tablet and start again so I decided to do a factory reset...
The first problem was the device just hung with the Android working logo (the one with the chest open and gears turning) with a message about 'erasing...' but seeming to make no progress. I then tried booting into the recovery mode but this just seemed to take me back to the same screen. Getting a little desperate now I decided to give ADB and Fastboot a go. Clearly ADB was not going to work as I didn't have a running Android but Fastboot connected to my device OK.
So I then tried to reflash the system but was told that by bootloader was locked. When I tried unlocking the bootloader (fastboot oem unlock) I get stuck with 'erasing data ....' again.
Any suggestions???
Just and update for you guys. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain! Not Happy.
Mo
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
So while i was browsing around with Firefox on my 1 year old Nexus 5X, it suddenly froze and after about 20 secs automatically reboots.
After it shows the google boot logo for about 10 seconds it reboots again in a loop.
Bootloader is unlocked, its rooted and Cyanogenmod is installed. This worked fine for about 1 year. I havent done any updates since this CM install 1 year ago.
I can get into fastboot by pressing power and volume down. I can stay there forever but if I choose anything else from there, it goes into the reboot cycle again.
So I can not get into recovery mode from fastboot because it reboots before it gets there.
I can sometimes get into download mode by pressing power and volume up but after a few seconds it again reboots from there.
Is there any way to at least save my data? I do have some very important account data on it.
I assume from fastboot mode alone you cant save anything or is there a trick?
Thanks for any help!
sounds very similar to my situation, bought mine about a year ago as well, except I was running stock 7.1.2
It should be easy to save the phone, but for the data - that's going to be trickier.
As long as you have fastboot you can always just flash it back to stock but that will wipe your data.
So you could try to to:
fastboot erase cache and fastboot erase recovery and then reflash recovery and see if you can get into it now.
Once in recovery you should have adb access if you have the correct drivers installed and you can flash a full OTA image in ADB which will reflash every partition, but not wipe your data.
For both methods read this: https://developers.google.com/android/images
Once you have adb you could also just pull the entire content of your data partition. The question is if and how that account data is stored and if you could get it back that way.
If you really need that app data I would try to get the OS working by flashing the OTA image in adb, then reinstall the app and hope your account data is still there...
And then look into backup options. It's pretty risky to have important data not backed up or duplicated somewhere else on a mobile device that could be lost or stolen any second...
It sounds like the bootloop problem, its a problem that many people are facing
berndblb said:
It should be easy to save the phone, but for the data - that's going to be trickier.
As long as you have fastboot you can always just flash it back to stock but that will wipe your data.
So you could try to to:
fastboot erase cache and fastboot erase recovery and then reflash recovery and see if you can get into it now.
Once in recovery you should have adb access if you have the correct drivers installed and you can flash a full OTA image in ADB which will reflash every partition, but not wipe your data.
For both methods read this: https://developers.google.com/android/images
Once you have adb you could also just pull the entire content of your data partition. The question is if and how that account data is stored and if you could get it back that way.
If you really need that app data I would try to get the OS working by flashing the OTA image in adb, then reinstall the app and hope your account data is still there...
And then look into backup options. It's pretty risky to have important data not backed up or duplicated somewhere else on a mobile device that could be lost or stolen any second...
Click to expand...
Click to collapse
I dont know about the OP, but my 5X will not get into fastboot, no matter what option I pick, I see the Google screen then it goes black and back to the Google screen and then is unresponsive for hours
I'm having the same issue as of this morning. I find it a little suspicious that it happened on the same day that my billing restarted and they had just updated the app a few days ago...
But I am unable to get to recovery mode either. Just shows the Google logo and reboots.
It's happening to me right now, the exact same thing, guys, this is not a coincidence
Another one here, started Friday night 3 days ago. Really weird that all of a sudden so many 5X users are experiencing the same problem.
mine just started this today, but after about ten reboots it finally started. Its almost like someone took control of the phone to install something remotely... weird
Sent from my Nexus 5X using Tapatalk
I'm having the exact same issue. Was watching a youtube video and suddenly the screen froze and my phone rebooted. When i tried to get into the recovery i still only got the google logo and a reboot. Fortunately i have my bootloader unlocked. I was able to reflash android and it worked again. After an hour or two the same started to happen again. Extremely frustrating.
Best thing you can do is flash just the recovery and try to get your files out that way.
so even until now many Nexus 5x still got bootloop? nothing to fix it still?
planning to get an used Nexus 5x and afraid also got this bootloop problem, should I or shoudn't I get it?
after reading so much bootloop stories, seems the timing to bootloop is just matter of time? on how much the phone is used? heavy use got bootloop first and lighter use got bootloop last but still get it sooner or later?
I will not buy it
DON2003 said:
so even until now many Nexus 5x still got bootloop? nothing to fix it still?
planning to get an used Nexus 5x and afraid also got this bootloop problem, should I or shoudn't I get it?
after reading so much bootloop stories, seems the timing to bootloop is just matter of time? on how much the phone is used? heavy use got bootloop first and lighter use got bootloop last but still get it sooner or later?
Click to expand...
Click to collapse
Two days ago I was facing the same problem, I managed to reload the stock rom and relock the bootloader so I can claim the warranty. But even though they replace me the phone I am pretty sure that sooner or later you will face this problem. This is an amazing phone and for the time I buy it, I believe was a smart choice, now I believe you can find something at same range price with even better specs.
I am facing the exact same issue. I was watching a Youtube video when the phone suddenly froze and shutdown itself. Then impossible to boot again. Sometimes I can boot to fastboot (after few hours without touching the phone or 20 min in the freezer). I tried to flash factory images (https://developers.google.com/android/images) but it does not fix it.
Has anyone been able to fix this? I don't think it's a hardware issue as I replaced the screen (the last one had a small crack on it) as well as the battery...
Look in the general subfourm for BLOD. https://forum.xda-developers.com/showthread.php?t=3683926
Sent from my [device_name] using XDA-Developers Legacy app
Hi
I have a Nexus 5X that recently started bootlooping. I didn't flash anything new, it just started randomly yesterday. Most often it cycles between the Google logo and the yellow triangle warning about the unlocked bootloader. Sometimes yesterday it would boot to the spinning colorful objects turning into Android logo, freeze and reboot from there. A few times it event booted fully, but I didn't have a PC nearby to pull the files.
Today it didn't even once get to the colorful objects. Then I found some threads about the fix with the big cores of the processor and flashed the boot.img that solved it for many. Sadly, however it didn't work for me. The only thing that I can reliably boot into is fastboot.
Also tried booting into TWRP, but it froze and rebooted from the Google logo.
Does anyone have an approach to pull my files from the device? I bought a new phone yesterday and don't care to recover the full functionality of the device. I only care to recover the files via TWRP or booting into Android one more time. RMAing it might be hard, since I have unlocked the bootloader (despite currently running stock and not even root, I think).
Any help will be appreciated.
Cheers
Andi
Have you tried 'updating the build ' via fastboot without erasing userdata? Section 9 from SlimSnoopOS's guide @ https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
LG do offer a 2 year warranty (in the UK at least) and you can relock the bootloader through fastboot before you return it once you've recovered the data and/or factory reset it.
Did you install standard twrp or the one modified to boot on 4 cores?
Sent from my SM-G930F using Tapatalk
I feel like an idiot because I installed the modified boot.img, but the regular TWRP, assuming that the boot.img would be used to alter some fundamental configuration of the Cortex no matter what would be booted afterwards. The modified TWRP worked like a charm.
Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.