I was playing hearthstone as usual with my 8 month old nexus 5x. Then all of a sudden it froze and restarted itself. I wasn't mad cause it was the first time in 8 months. Then after 2 hours my phone started bootlooping. I was able to see the android boot screen and launcher sometimes, but now i can't get past through google screen. I am able to use fastboot mode and flash images via nexus root toolkit or skipsoft but i can't use twrp. I've tried:
-Nexus Root Toolkit's flash stock+unroot option
-Flashing Pixel Rom
-Can't LGUP and tot image cause i get the "there is no handset connected. Please, connect a handset." error.
I'm now considering baking or freeze my nexus 5x. I know there are lots of people having the same issue these days but I still have a bit of hope because i can access fastboot mode and flash roms.
any help would be very appreciated, thanks.
atahanu said:
I was playing hearthstone as usual with my 8 month old nexus 5x. Then all of a sudden it froze and restarted itself. I wasn't mad cause it was the first time in 8 months. Then after 2 hours my phone started bootlooping. I was able to see the android boot screen and launcher sometimes, but now i can't get past through google screen. I am able to use fastboot mode and flash images via nexus root toolkit or skipsoft but i can't use twrp. I've tried:
-Nexus Root Toolkit's flash stock+unroot option
-Flashing Pixel Rom
-Can't LGUP and tot image cause i get the "there is no handset connected. Please, connect a handset." error.
I'm now considering baking or freeze my nexus 5x. I know there are lots of people having the same issue these days but I still have a bit of hope because i can access fastboot mode and flash roms.
any help would be very appreciated, thanks.
Click to expand...
Click to collapse
I had the same issue 3 weeks ago. I had access to just the fastboot and the recovery lgup did not work either. It went to repair and the verdict was motherboard out of service and to change
androcib said:
I had the same issue 3 weeks ago. I had access to just the fastboot and the recovery lgup did not work either. It went to repair and the verdict was motherboard out of service and to change
Click to expand...
Click to collapse
the point is i bought this phone from u.s and there is no repair service for it in my country.
Related
I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.
Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK
use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.
DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.
If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app
Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.
If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app
Enter stock recovery then flash the full ota via adb sideload
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
My phone bootloops into teamwin logo with no commands, it's not recognize by my PC even though it was before I flash new vendor and a custom rom. it will allow me to go into fastboot.
It happens to me now, but with stock 7.1.1 (beta program).
rodrigo82 said:
It happens to me now, but with stock 7.1.1 (beta program).
Click to expand...
Click to collapse
How did you fix it? I am a Mac-user and Nexus Root Toolkit is not available for me
yychun1217 said:
How did you fix it? I am a Mac-user and Nexus Root Toolkit is not available for me
Click to expand...
Click to collapse
I googled it and I discovered that there's no fix.
It's a hardware problem, specifically on emmc controller.
End of story: I bought a Samsung J5 Metal and I still missing my dearest N5X.
And my N5X only works on bootloader.
I'm having a similar issue my phone froze and was bootlooping. I was able to access recovery and recover files from the SD. However Im now having a hard turning on the phone and when I do, I can get it into bootloader/ recovery but computer won't recognize it. So I can't lock the bootloader and unroot to send it in for repair. I'm probably going to send I'm the phone as is and hope it gets fixed. It's crazy that it just froze while I was using YouTube and started bootlooping. Now using my Nexus5
Sent from my Nexus 5
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.