LG Nexus 5X stuck in boot loop - Nexus 5X Q&A, Help & Troubleshooting

This morning while using my phone, it froze and rebooted. While trying to reboot, it will continue to go to the Google screen then reboot and go to the Google screen, again and again. Recovery mode does not work, it enters the bootloop again if I try to boot into recovery mode.
I tried the following:
- This: https://www.xda-developers.com/nexus-5x-bootloop-fix-boot-phone/
- I tried to flash different versions found here: https://developers.google.com/android/images
- I tried the freezer method which got me in once.
- I tried the hairdryer method which actually worked for about 20 mins, when it failed I did it again and got another 10-15 mins out of it. Now the hairdryer trick does nothing.
I assume the CPU has failed and am going into a mobile repair shop tomorrow to see about a CPU swap. Would that be a surefire fix or is the Nexus 5X bootloop issue due to a different piece of hardware?

I bought my 5X from Google two years ago, and faced the BLOD just last week. Despite the device being out of warranty for over a year, they patched me through to LG, who agreed to repair it for free. You could try this (or calling LG support directly) if you don't want to pay for repairs.

Dr. Chaos said:
This morning while using my phone, it froze and rebooted. While trying to reboot, it will continue to go to the Google screen then reboot and go to the Google screen, again and again. Recovery mode does not work, it enters the bootloop again if I try to boot into recovery mode.
I tried the following:
- This: https://www.xda-developers.com/nexus-5x-bootloop-fix-boot-phone/
- I tried to flash different versions found here: https://developers.google.com/android/images
- I tried the freezer method which got me in once.
- I tried the hairdryer method which actually worked for about 20 mins, when it failed I did it again and got another 10-15 mins out of it. Now the hairdryer trick does nothing.
I assume the CPU has failed and am going into a mobile repair shop tomorrow to see about a CPU swap. Would that be a surefire fix or is the Nexus 5X bootloop issue due to a different piece of hardware?
Click to expand...
Click to collapse
Flash (7.1.2 (N2G47Z, Jul 2017) this one and do no update the sistem, stay in android 7
I flashed it with nexus tool kit you do have to have unlockbotloader
after first boot you can flash N2G47Z_4Cores.img if bootloops.

jose daniel said:
Flash (7.1.2 (N2G47Z, Jul 2017) this one and do no update the sistem, stay in android 7
I flashed it with nexus tool kit you do have to have unlockbotloader
after first boot you can flash N2G47Z_4Cores.img if bootloops.
Click to expand...
Click to collapse
I'll try flashing this version. I am using fastboot to flash.

I flashed that version, 7.1.2 (N2G47Z, Jul 2017). It stayed in bootloop.
I then flashed N2G47Z_4Cores.img and it still stayed in bootloop.

I got a quote for a total motherboard replacement, including all new parts on the mobo for $200 USD.
A total mobo replacement would fix the issue, even if it was a software issue, yes?

Dr. Chaos said:
I got a quote for a total motherboard replacement, including all new parts on the mobo for $200 USD.
A total mobo replacement would fix the issue, even if it was a software issue, yes?
Click to expand...
Click to collapse
I dont know if it maters but i did flash vendor img separately
and remember first boot takes 20 minutes
I dont know how many time will last mine, but 200$ is too much
by know 48h no bootloop
good luck

jose daniel said:
I dont know if it maters but i did flash vendor img separately
and remember first boot takes 20 minutes
I dont know how many time will last mine, but 200$ is too much
by know 48h no bootloop
good luck
Click to expand...
Click to collapse
I have also read the first boot takes 20 mins but does that mean it bootloops for 20 mins or stays stagnant on the google logo or spinning circles screen for 20 mins?

Dr. Chaos said:
I have also read the first boot takes 20 mins but does that mean it bootloops for 20 mins or stays stagnant on the google logo or spinning circles screen for 20 mins?
Click to expand...
Click to collapse
1 or 2 bootloops then google logo

Yeah... no software solution on the internet has worked for me. Going in to get a new mobo.

Ritwyk said:
I bought my 5X from Google two years ago, and faced the BLOD just last week. Despite the device being out of warranty for over a year, they patched me through to LG, who agreed to repair it for free. You could try this (or calling LG support directly) if you don't want to pay for repairs.
Click to expand...
Click to collapse
I just had the same experience. Waiting on LG to send me my shopping label so I can send it back.

LG Nexus 5x stuck in boot loop
My Nexus 5x has been a great phone for 3 years. Yesterday it got stuck in a boot loop.
I tried the solution at https://www.xda-developers.com/nexus-5x-bootloop-fix-boot-phone/
The instructions worked fine, except I ended with a black screen with a white "Google" and a white unlocked padlock at the bottom
On the same page I found a suggestion to install the factory image for 8.0 "OPR4.170623.020"
followed by the same N2G47Z_4Cores.img boot image from the first solution
It ended with a white "Google" on a black screen
There were more folks who said:
1. Flash the factory image for Android 7.1.2 (N2G48C, Aug 2017)
2. Flash the bootloop fix from the article (N2G47Z_4Cores.img)
3. Lock the bootloader with fastboot flashing lock
4. Restart the phone and wait for the bootloop to resolve.
This ended the same way
Any other suggestions?

Related

My nexus 5X H798 - 32GB is stuck in boot loop.

I got into Recovery Mode and performed a wipe cache partition and also factory reset and it did not helped.
Any help will be appreciated
Phone info:
LG H798 32GB
google/bullhead/bullhead
6.0.1/MTC19Z/2996059
Product name:bullhead
Variant:bullhead LGH798 32GB
HW version: rev_1.0
bootloader version -BHZ10p
baseband version - M8994F-2.6.32.1.13
secure boot -enabled
device state - locked
Just flash stock ROM again: https://developers.google.com/android/nexus/images
Rekan_ said:
Just flash stock ROM again: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
There are 14 ROMs for Nexus 5x, how do I know which one to choose?
jojesa said:
There are 14 ROMs for Nexus 5x, how do I know which one to choose?
Click to expand...
Click to collapse
Any of them will do, the latest is preferred.
Nexus 5x bootloop
I have the same issue. I flashed the stock rom like 4 times without success. I've read almost every troubleshooting guide here and google forums. I don't know what to do. I can't even access to the recovery.
pablohr9 said:
I have the same issue. I flashed the stock rom like 4 times without success. I've read almost every troubleshooting guide here and google forums. I don't know what to do. I can't even access to the recovery.
Click to expand...
Click to collapse
I got a security update and that's when the phone went kaput.
Did you flash the same stock ROM 4 times or did you try different ones?
By the way, I have the Nexus 5 and had the same issue I'm having now, so this will be my last LG phone and maybe my last Nexus.
jojesa said:
I got a security update and that's when the phone went kaput.
Did you flash the same stock ROM 4 times or did you try different ones?
By the way, I have the Nexus 5 and had the same issue I'm having now, so this will be my last LG phone and maybe my last Nexus.
Click to expand...
Click to collapse
I tried 3. The oldest the newest and one of the middle. I flashed them with the Nexus root toolkit and with the command prompt. I really don't know what is the problem.
Did you fix your Nexus 5? Because I read that could be a issue with the power botton. I am wondering if the N5x has the same issue?
Looks like this is a common issue at the moment.
I'm in the same boat. I can get to the bootloader screen, no issue. But if I try going into recovery mode, or standard boot. It just loops on the google logo (or sometimes just sits there at the logo for an hour).
dsayling said:
Looks like this is a common issue at the moment.
I'm in the same boat. I can get to the bootloader screen, no issue. But if I try going into recovery mode, or standard boot. It just loops on the google logo (or sometimes just sits there at the logo for an hour).
Click to expand...
Click to collapse
I posted the issue on LG USA Mobile Facebook page. I received a message: "In order for us to address your concerns, we ask that you please send us a private message. Thank you for reaching out to us. "
I suggest anyone with the same issue do the same. That way people are aware of this issue. If I knew before hand I would not have got the Nexus 5X.
deleted
I was able to get the Nexus 5x working again.
I downloaded the ROM that matched this line from the Android Recovery screen.
6.0.1/MTC19Z/2996059
I first downloaded and installed the ADB USB drivers adb-setup-1.4.3 as administrator, saying yes Y to all prompts.
I created the folder C:\nexus and placed the ROM on that folder.
On the Nexus 5X Android Recovery screen I selected “Apply Update from ADB” .
At this point I attached a USB cord between PC and phone.
At the Command Prompt I entered: adb sideload c:\nexus\bullhead-ota-mtc19z-b4cfce2c.zip (here replaced the section in bold with the name of your ROM).
When the update finished I selected the line “Reboot system now".
Voila! Phone is back to life.
Actualy there is a step by step PDF
https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view
"Okay Google",
Being a admirer of google i went into buying Nexus 5X as my smartphone. As this model was relatively costly i had many objections from friends and family. Still i insisted for the same "LG Google Nexus 5X".
Previously i had heating issues with the new phone. but the service centre guy said it will heat "abit"(i know that was not bit) as it is a smartphone.I had to keep the new phone in charging for hours and that two three times a day.
Against all the odds i was in favour of google as it sounded good to tell people which phone i had, But the people who saw me always looking for charging plug knew what i was going through.
Currently i am facing the reboot loop issue, my phone keeps on rebooting. I went to the one where i bought the phone.The guy said it requires a software update and nothing else. I had heard of the peoples having such issues worldwide and i was worried about the solution. So i had sent my phone to the LG's Service Centre their the person said if only software update is required then it will cost around 350 INR else we will let you know. So after a long wait and contacting the service centre their i finally had a talk with them and they said it seem to be a PCB problem and costsaroung 11000 INR. Hearing the figure was a shock!
I don't know what to do with the situation as my phone doesn't have the warranty. Please help me as this is a HUGE amount to spent to repair a phone.

Bootloop, soft brick?

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

H790 stuck in bootloop after random crash

Hey all, I need some assistance here. So my device is Nexus 5x H790 unlocked bootloader, stock ROM, Usb debugging enabled. I had the latest October updates (90S I believe) and everything was running just fine on it until about 5 days ago. I was using my phone like normal and suddenly it turned off. I could not turn it back on and when it did it would get stuck at the Google screen and then begin to bootloop several times before turning off. I have gotten to the recovery screen 1 time and wiped cache but still same result. There was one instance where the phone completely booted up and was receiving the numerous texts over the few days and even sent a few. Then it crashed again after 5 mins :crying:
Here is what I've tried:
-Attempted to reflash October images from googles website. I have experience doing this before from using Heisenburg's method 9 (no change)
-Then began to research and thought it was the power button getting stuck issue. Brought it to a repair shop and they opened it and checked out the power button and said it was firmware not the button and to factory reset (brought it here because the device is 13 months old and figured it was cheaper/faster than sending to LG and waiting a whole month to get it back)
-Brought home from repair shop, reflashed latest October images and still could not boot up fully.
-Now I want to factory reset but cannot get to recovery screen, when I enter bootloader and scroll to Recovery it just goes to Google image again....I believe there are commands to wipe device userdata and tried "fastboot erase userdata" and "fastboot format data" but gave errors
I will try next to use a different USB port, now that just found a thread on here saying the 3.0 ports dont seem to work with that command even though I've used the same port for every image flash I've done in past
Any help/ideas would be appreciated. Thanks in advance
Same problem...
I have the same problem. Mine started bootlooping to the Google screen the same day my warranty expired...
I'm gooing to send it off to LG, but I really wish I could get my pics and texts off before they wipe it
mjp5099 said:
Hey all, I need some assistance here. So my device is Nexus 5x H790 unlocked bootloader, stock ROM, Usb debugging enabled. I had the latest October updates (90S I believe) and everything was running just fine on it until about 5 days ago. I was using my phone like normal and suddenly it turned off. I could not turn it back on and when it did it would get stuck at the Google screen and then begin to bootloop several times before turning off. I have gotten to the recovery screen 1 time and wiped cache but still same result. There was one instance where the phone completely booted up and was receiving the numerous texts over the few days and even sent a few. Then it crashed again after 5 mins :crying:
Here is what I've tried:
-Attempted to reflash October images from googles website. I have experience doing this before from using Heisenburg's method 9 (no change)
-Then began to research and thought it was the power button getting stuck issue. Brought it to a repair shop and they opened it and checked out the power button and said it was firmware not the button and to factory reset (brought it here because the device is 13 months old and figured it was cheaper/faster than sending to LG and waiting a whole month to get it back)
-Brought home from repair shop, reflashed latest October images and still could not boot up fully.
-Now I want to factory reset but cannot get to recovery screen, when I enter bootloader and scroll to Recovery it just goes to Google image again....I believe there are commands to wipe device userdata and tried "fastboot erase userdata" and "fastboot format data" but gave errors
I will try next to use a different USB port, now that just found a thread on here saying the 3.0 ports dont seem to work with that command even though I've used the same port for every image flash I've done in past
Any help/ideas would be appreciated. Thanks in advance
Click to expand...
Click to collapse
How could ur warranty be expired when it is 24 months by buy date.
Domin_PL said:
How could ur warranty be expired when it is 24 months by buy date.
Click to expand...
Click to collapse
I'm fairly certain its 12 months for manufacturer. I did not get the extra Nexus protect
In Europe there is 24 month warranty for all sold products. Kind of bad thing or kind of good thing.
ugh wife's Nexus 5x did this same thing. Been up all night trying EVERYTHING. Fastboot works but bootloader is locked so I can't do anything. Going to recovery just reboots the phone to logo.bin and then turns off again. Download mode is unreliable and when I get it to finally trigger, it doesn't go to the second phase where it waits for a firmware update (so I can't do the LGUP thing).
So I guess this is an OTA problem? Some BS.
fanta110 said:
In Europe there is 24 month warranty for all sold products. Kind of bad thing or kind of good thing.
Click to expand...
Click to collapse
In France LG does not guarantee the 24 months since March 2016. my nexus 5x is broken down one year and 1 day after the date of purchase with this same issue. At first LG told me that the warranty was OK then they retracted. I have a beautiful invoice with the change of motherboard ....
****
androcib said:
In France LG does not guarantee the 24 months since March 2016. my nexus 5x is broken down one year and 1 day after the date of purchase with this same issue. At first LG told me that the warranty was OK then they retracted. I have a beautiful invoice with the change of motherboard ....
Click to expand...
Click to collapse
Just curious how much the new motherboard was quoted for repair? At this point I finally reached the recovery screen and performed a true factory reset but havent tried flashing latest images from google. I will update and let you know if that worked. If that doesnt work, I will be getting the pixel on Verizon on black friday for the $10/ mo

Nexus 5x bootloop after oreo update

So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
Have you flashed the 4core bootimg/kernel/recovery, or have you done absolutely no research?
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Also, the fix is really only temporary, I'd prepare to move on to a new phone.
negusp said:
Have you flashed the 4core bootimg/kernel/recovery, or have you done absolutely no research?
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Also, the fix is really only temporary, I'd prepare to move on to a new phone.
Click to expand...
Click to collapse
yeah, i was sceptical of that, so was looking for any other fixes, but as I see, there is no other choice
Remygas said:
yeah, i was sceptical of that, so was looking for any other fixes, but as I see, there is no other choice
Click to expand...
Click to collapse
The bootloop is purely a hardware issue. There is no permanent fix except to either get a replacement CPU or send the phone to LG.
Disabling the 2 big cores should allow you to use the phone for another couple of months. Don't expect it to be permanent, though.
i have faced the same issue on mine.
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
i have find this on my one too, pls reply me if u find the solution and i will give you if i find the solution.
santhoshreddy923 said:
i have find this on my one too, pls reply me if u find the solution and i will give you if i find the solution.
Click to expand...
Click to collapse
The solution is to apply the BLOD boot image patch, as was stated above. Here's a link: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Unknown025 said:
The solution is to apply the BLOD boot image patch, as was stated above. Here's a link: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Click to expand...
Click to collapse
This isn't possible if you have a locked bootloader unless you can somehow get your phone turned on... If I am mistaken I'd love to be corrected so I can fix this. If this really is a hardware issue, then I guess I'm screwed. This phone is just over a year old and Oreo has been installed for a couple weeks, so this pretty much blows.
nexus 5x bootloop brick
i have found that it is due to hardware issue and what is the best place i can get it repaired.
Is there any other way that i can replace it with another processor such as 820 r any other lower one?
Just send it in for $10 (UPS with tracking #) to LG
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, ... but now i can not get into recovery....so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
Just send it in for $10 (UPS with tracking #) to LG and they will put a new motherboard in it. I just did it with my out of warranty 5X that I purchased in May 2016. LG show status "In Warranty" and there was not charge. Phone works faster and better than ever. I upgraded to Oreo an it is running great.
If you need a temp phone buy something like and unlocked (tmobile compatible) phone like I did $70 Alcatel Onetouch Idol 3 until you get your phone back. My project Fi sim works great in that phone I just needed a micro to nano SIM adapter which I got for free at a local cell phone shop.
excuse can you please tell me the detailed process of sending phone to lg .
mrbios said:
Just send it in for $10 (UPS with tracking #) to LG and they will put a new motherboard in it. I just did it with my out of warranty 5X that I purchased in May 2016. LG show status "In Warranty" and there was not charge. Phone works faster and better than ever. I upgraded to Oreo an it is running great.
If you need a temp phone buy something like and unlocked (tmobile compatible) phone like I did $70 Alcatel Onetouch Idol 3 until you get your phone back. My project Fi sim works great in that phone I just needed a micro to nano SIM adapter which I got for free at a local cell phone shop.
Click to expand...
Click to collapse
the issue is i live in india and the phone is imported one could you pls help me.
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
Same..
My phone was working fine today till evening, suddenly it restarted and this boot loop started. I was on PixelRom (Oreo 8.0)
I tried flashing Factory image of 8.1 final release via fastboot. Its still not booting. Keeps restarting.
Any help?
continuous reboot after Oreo update
Hi,
I am facing issues with my Nexux 5x after updating to the latest version of Android. I received a notification for software update and I did it and as soon as the update was done, the phone started rebooting continously. I tried wiping the cache, factory reset via recovery mode, but nothing actually works. Could anyone of you suggest me some ways to get it corrected or to get the old version back.
Thanks
deepa
mrbios said:
Just send it in for $10 (UPS with tracking #) to LG and they will put a new motherboard in it. I just did it with my out of warranty 5X that I purchased in May 2016. LG show status "In Warranty" and there was not charge. Phone works faster and better than ever. I upgraded to Oreo an it is running great.
If you need a temp phone buy something like and unlocked (tmobile compatible) phone like I did $70 Alcatel Onetouch Idol 3 until you get your phone back. My project Fi sim works great in that phone I just needed a micro to nano SIM adapter which I got for free at a local cell phone shop.
Click to expand...
Click to collapse
Do you still have warranty when you send it?
Extended warranty on LG Google Nexus 5X
arem2015 said:
Do you still have warranty when you send it?
Click to expand...
Click to collapse
No, my phone was 1.5 years old and out of warranty. I did not buy an extended warranty. LG extends the warranty on the Nexus 5X well beyond the standard 1 year for the bootloop issue. Also, my phone was in excellent like-new condition.
My 5x was purchased November of 2015, and they covered mine at no cost under warranty. Even provided a mailing label for me to send it in on their dime. They did require me to provide original proof of purchase (which I luckily was able to lookup). I sent it in on a Monday and got it back Friday that same week. Was mind-blowing fast turnaround time.

Is it acceptable to you that a $800 phone dead in 21 months?

My pixel xl(1st gen) purchased from Google store in Jan 2017, and in bootloop a week ago.
I contact google support, they told me my device out of the 1-yr warranty, and redirect me to UbreakIfix for repair, cost on myself.
I contacted UbreakIfix, get a quote for 300+ to change motherboard.
As of today, the Pixel XL only worth $130 trade-in value, and the condition need to be perfect.
So clearly I won't spend $300 to save a device only worth $130.
About the issue, I had some level of experience with fastboot/adb command:
* tried re-image all latest Google Stock Image of Android 7/8/9 individually with boot-loader unlocked, no luck;
* tried adb sideload ota image of Android 7/8/9 individually, with boot-loader locked/unlocked, no luck;
* tried change active slot to a and b with combination of above two items, no luck;
* checked the recovery logs, the boot-loader did take whatever Android stock image I feed to to it, and I do almost every time can get in to both boot-loader or recovery-mode successfully, and has no limit to run any fastboot/adb commands, but these are all I can do, and still not to get the phone boot into Android OS.
* in a very few times, the static "Google" in the white screen did spinning into a big rainbow "G", but it was frozen right after, and eventually reboot again.
I don't know if it worth spend more time on it, and feel very frustrated about spending my time on this doomed device and dealing with the Giant company as a individual customer.
I am not a picky guy, I accept the device running slow, or buggy sometime, but doesn't accept it dead in 2 years as a premium phone.
What do you think, guys?
By the way, many thanks to XDA forum, I learnt a lot from many brilliant and kind people here.
It's not acceptable, but it's the norm. Look at buying a new tv - Some mfg warranties are like 90 days labor and 6 months to a year on parts...It's a shame you pay all that money for something that could be a paperweight in a year.
Acceptable for a phone, or any gadget worth $800 to die in 21 months? LMAO. If this acceptable to some group of people, please redirect them to the best psychic facility available on this planet.
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
lafester said:
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I used my Pixel as a regular way, never root it, never even boot into bootloader before the bootloop issue, always use ota in os to get update. No water spilt, never get drop or hit. In another word, I never "abuse" the phone, and the phone has no accident.
Yeah, whatever, for the phone issue, I'm just having bad luck, like you said, many people have no issues. What I upset about is a $800 phone became a brick within 2 years with a normal usage, and Google not even give this case as an exception to cover it out of warranty.
You may say, or like Google said, then what the warranty stands for, right? I say, if only a few people got this issue, then as a Giant company, should cover since no fault on customer, and it would be a small cost to Google; if a lot of people got this issue, then still Google need to cover, since it becomes a general issue to this phone, which indicates this is a failed model at all.
Please don't think I'm a cheap guy, and trying to take advantage from Google, just trying to think the logical here. BTW, I'm not just complaining Google without putting in effort to solve the issue by myself, I did a little bit research and pickup learning, regard this issue, I'm not alone, many other users have the same issue as well, some of them get it "resolved" by reimage, but the other just has no luck like me.
You don't have to agree with me, I'm a kind of guy would love to discuss with people no matter they have same point view as mine or not.
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Phalanx7621 said:
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Click to expand...
Click to collapse
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
I'm having the exact same issue and Phalanx7621 tried helping me out but unfortunately it looks like there's no solution for it.. Just like your issue, everything successfully flashes, but I got a little past the Google logo a couple of times, but no more. My phone wasn't dropped, never wet, nothing at all. Yesterday morning I woke up and the screen was just black and it started boot looping.
Funnily enough, 2 weeks after I paid the phone off. 1 week after Verizon called to let me know they had open enrollment on their insurance plans and I turned it down since, yanno, I don't mistreat my phone.. "Coincidence" I guess..
My post btw https://forum.xda-developers.com/pixel-xl/help/possibly-bricked-t3861057#post78033420 if any of that helps you hopefully.
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
Phalanx7621 said:
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Click to expand...
Click to collapse
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
premedicated said:
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
Click to expand...
Click to collapse
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
Sure. Gimme a couple minutes and I'll report back
---------- Post added at 08:15 PM ---------- Previous post was at 07:40 PM ----------
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
So it loaded up TWRP, then I remembered that I didn't set a pin after the latest reflash. So I went into software and setup a pin and moved the TWRP files over onto the phone as well as the kernal before it restarted. But now I can't get 'fastboot boot twrp.img' to actually load TWRP on the phone.. Command prompt says "downloading boot.img, booting, finished. And then on the phone it loads up the google logo and then just freezes and restarts.. I'll dink with it some more and see if i can make it work
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Phalanx7621 said:
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Click to expand...
Click to collapse
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
premedicated said:
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
Click to expand...
Click to collapse
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Phalanx7621 said:
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Click to expand...
Click to collapse
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
premedicated said:
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
Click to expand...
Click to collapse
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
premedicated said:
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
Click to expand...
Click to collapse
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Phalanx7621 said:
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Click to expand...
Click to collapse
Well here's the deal.. Right after I posted that it started bootlooping again. It went through about 6 bootloops before I said 'eff it' and then just plugged it into the charger and walked away. I came back to it a little bit ago and according to the Kernel manager, it has an uptime of an hour and 32 minutes. So I grabbed it and was dinking around for a minute with it. Downloaded hulu, no problems. Downloaded netflix, no problems and then I was writing out a text and all of a sudden it froze and rebooted. Bootlooped once, then on the second try it started up. It's been up for about half an hour now.
Are there some sort of .log files with Android that could possibly show exactly what it is that's causing it to restart? Maybe something in the Kernel manager could help?

Categories

Resources