Hello, I'm new to the forum and I may need your help for a problem I've had today. I've been an happy owner of a Nexus 5X until this morning, when I was regularly using it while on charge and at one point it freezed for a few seconds with the screen still on. I pushed the standby button, the screen went off and from then on it was completely bricked. No signs of life, nor access to recovery mode via bootloader. Nothing. Already tried all the possible physical buttons combos, nothing.
It was on Android 8.1 (beta, very happy about that by the way), no root and with locked bootloader. I did some flashing experiments one year ago but in the end I reverted it back to totally stock and I haven't had issues ever since. Never had bootloops or similar problems, it just happened all of a sudden.
Hope to receive your help, by the way it should still be under warranty, so let's see...
Thanks for your help.
Same problem heare. I tried to install the factory image but now, the phone is completely death.
I beleve thet it was a android 8.1 issue because it was not a bootloop problem.
Same problem heare. 8.1 need a reboot but now, the phone is completely death
It might be an 8.1 issue then. By the way, being under warranty I sent it to customer assistance. I've had some signals of life before this morning though. The LED was flashing red indicating very low battery. I connected it to the charger and followed the instructions by Google themselves:
"If you see a red light, your battery is fully discharged. If the red light is flashing, there isn't enough power to turn on. Charge your phone for at least 30 minutes before restarting".
This seemed to resemble my case, so I waited for about 40 minutes (by that time the charging battery icon did show up with the phone still off) and tried to turn on. The only thing that I got has been the Google logo before the boot animation for a few seconds. Then the screen has gone off again and back to death.
From your comments it seems it might be an 8.1 related issue. Watching videos on Youtube about 5Xes with similar behaviours I was actually thinking about a motherboard failure, or a battery failure (the latter is more unlikely though). Disassembling and heating up the motherboard providing a temperature shock seemed to be a decent temporary solution to bring it back to life. I have warranty though so I sent it to assistance, we'll see... I'll probably unenroll my phone from the beta program just to stay safe.
Thanks for your answers.
My nexus 5x had same issue. A few weeks after 8.1, it totally bricked. I was able to get bootloader on once, but it was locked and fastboot didn't see it. Then after i let it discharge, I haven't been able to get it to recharge or get to boot screen at all. I bought another nexus 5x, but bit worried that 8.1 will kill it.
Related
Howdy, guys.
I've got my One rooted, unlocked, and was running a CM10.2 nightly build. Everything was working fine until yesterday, when my battery started to rapidly discharge. I woke up with 100% battery, and after about 15 minutes of playing music it was down to 30%. I recharged it and started noticing rapid battery loss, about 10% per 15 minutes when the phone was idle.
Worried that this had to do with my ROM, I flashed the Eclipse Google Play Edition v1.2 ROM. However, the drain issue continued. I decided to let the phone fully discharge, then try powering it up again.
When it was fully discharged, I tried plugging in the phone. No LED came on and I couldn't turn the phone on. I've let it sit for over 2 hours now with the same result.
Some posts with similar symptoms have mentioned plugging the phone into a Windows PC and experiencing the "USB device plugged in" sound alert. I am not having any such luck, and what I currently have is a very aesthetically pleasing paperweight with no function whatsoever.
Has anyone else experienced a similar issue, or found a fix?
none
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Last Sunday, listening to music with HTC One (bought on Sep 11) on the charger, it suddenly went dark. Would not reboot, no charge light either. Went to a VZW store, they're shipping me a warranty replacement.
I wonder whether my habit of leaving it charger-connected whenever it's sitting on my desk (i.e., way beyond the fully-charged point) somehow stressed the battery (or the charging circuitry) -- though that habit never impacted my two previous HTC models.
When you hold Vol+Down and Power do your home and back arrows blink? If so, point the phone sensors (the two on the front on the left hand side) into a bright light. Then hold down Vol+Down and Power. It should boot. I'm not sure why. But it worked for me today after installing a custom recovery. -shrugs-
musicman625 said:
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Click to expand...
Click to collapse
I've got a replacement being shipped to me, and I'll send them the old one when it comes in. Currently using an old Samsung Stratosphere as a replacement, I was just hoping there'd be an easier fix or something simple. Thanks, though!
My mother's nexus 5x has just died.
no fastboot no recovery nothing.
I have tried to charge it, but after more than an hour connected to the charger still nothing.
I checked that this charger works on my nexus 5x so it's not the problem.
I also tried to connect it to a computer, but the computer detected nothing.
the phone had 7.1.2 stock (either april or may security update I don't remember which one).
Anyone has an idea why it happened or how to fix this?
Thanks,
Orma
Wow, my 5X just died this morning. Wonder if it isn't just a coincidence or maybe some update like to the Fi app or something messed it up. So I'll post in case others have also had the same thing happen. The Fi app was last updated May 8, so that's not it. But maybe there was some other app or something updated that caused problems. Some of the core apps were recently updated and my phone tried to update some behind the scenes type app, but it didn't work. So I tried manually and it did work. Maybe I shouldn't have done that. Can't remember which app, but checking on my Google playstore apps, maybe it was Google Connectivity Services.
Mine was fully charged and I was using it while still connected to the charger after waking up in the morning. It just went black suddenly. I tried holding power button to shut it down, but it never made any vibration as if it was force shutting off. Power button and volume down button didn't work to shut down or boot either. The computer recognized it the first time I plugged it in showing Qualcomm HS-USB QDLoader 9008 has completed setup. But after that it would show as device unrecognized.
The only way I got anything to look like it was starting ok was by disconnecting the battery for a while. Then it started booting and then the screen just went black again. I unhooked the battery again for a while, reassembled, and plugged the phone in and the battery charging screen showed up, but then went black again without showing the filling up graphics.
So it seems to momentarily kinda act ok, but then soon goes black. Disconnecting the battery seems to reset it to a state where it can try again.
The battery read as 4.16 volts, so seems to be fully charged as I thought it was. I'm going to try doing the battery disconnect again, but I'm thinking this thing is done.
This may not just be a random thing. Several people on Google forums have the same sounding issue from yesterday or today.
https://productforums.google.com/forum/#!topic/nexus/iKXTmQ04YeM;context-place=forum/nexus
https://productforums.google.com/forum/#!topic/nexus/DINPhe1nb4c;context-place=forum/nexus
https://productforums.google.com/forum/#!topic/nexus/lWKu7eEfHhc;context-place=forum/nexus
By disconnecting the battery and then reassembling, I was able to get to the recovery menu. I chose Restart Bootloader, and after a few moments, go a screen showing the android character laying on the ground with a triangle with an exclamation point and "No Command" text at the bottom.
Holding power button and volume down got it to go back to the menu.
So I tried Recovery and it showed Google in white letters, then went black. Trying Start does the same thing.
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
kakah2011 said:
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Click to expand...
Click to collapse
Voicebox said:
By disconnecting the battery and then reassembling, I was able to get to the recovery menu. I chose Restart Bootloader, and after a few moments, go a screen showing the android character laying on the ground with a triangle with an exclamation point and "No Command" text at the bottom.
Holding power button and volume down got it to go back to the menu.
So I tried Recovery and it showed Google in white letters, then went black. Trying Start does the same thing.
Click to expand...
Click to collapse
if I open the phone to disconnect the battery will it void the warranty?
any one has any idea on why it happened?
my nexus 5x is totally fine
edit: I tried again to turn it on, but this time the notification light turned red, so i tried to connect it to the charger again and it seems to be alive now,
that's really weird but it turned on with 1% meaning that for some reason when I charged it yesterday it wasn't really charging
orma1 said:
if I open the phone to disconnect the battery will it void the warranty?
any one has any idea on why it happened?
my nexus 5x is totally fine
edit: I tried again to turn it on, but this time the notification light turned red, so i tried to connect it to the charger again and it seems to be alive now,
that's really weird but it turned on with 1% meaning that for some reason when I charged it yesterday it wasn't really charging
Click to expand...
Click to collapse
Sounds like you got lucky.
As far as I could see, there is nothing inside the phone that would indicate that you had opened it up. There's no glue, except under the battery, and maybe under the motherboard. But you don't need to lift those to disconnect the battery connector. However, it does require prying the back off and then unscrewing 10 screws. Then lifting off two pieces with stuff like the fingerprint sensor and speaker attached to them. If you make any dings in the plastic back cover while prying, they could see that. And the screws have lock tite on the threads so take some care to remove. I think I slightly stripped the top of one. So if someone really looked, they could see that. But otherwise, except for leaving fingerprints on parts or debris or whatever in there, I don't think they'd notice. I highly doubt they'd have someone go check for other than obvious signs of prying the back off. I'm 2 months past warranty so it was a non-issue for me.
Following someone's advice on the Google forum, I cooled the phone down in an ice bath (in a bag of course) and was able to get it to boot to recovery and even installed the OTA via adb. It then booted to the point of the 4 colorful circles and died again. After putting it in the freezer, it then returned to acting somewhat normal, as in it showed the battery charging graphic while off. The battery is about 1/2 full. But then I booted and it would get pretty far into the 4 circles spinning, then boot looped. So mine is bootlooping and I'm going to see if I can get Google to step up even though it is 2 months past warranty since I bought it from them. The Google people say to contact them with the bootloop problem. I hope they are quietly replacing them since this this appears to result from the last OS update for many people.
That other person was able to boot it and pull their pictures off it. But looks like mine is down for the count. I luckily had backed up pictures and most of my other stuff recently before I went on a trip. And I uploaded pictures while on the trip and pulled pictures off the phone right after the trip. But I've lost some info that I hadn't copied off the phone.
---------- Post added at 02:17 PM ---------- Previous post was at 01:59 PM ----------
kakah2011 said:
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Click to expand...
Click to collapse
I'm 2 months out of warranty, so I hope Google does something since I bought it from them and they seem to be providing some relief since this seems to be due to the most recent OS update. Or at least some of the people in their forums seem to imply they'll do something.
Well here you go. Explanation was at XDA all along. There's a class action lawsuit against LG for using solder that didn't withstand the level of heat or heating and cooling cycles. Started with the G4, but in April the 5X and other phones were added to the class action. So I guess I could try touching up solder points and get my phone maybe to start up, or try for warranty repair since they seem to have extended the warranty because of this lawsuit.
https://www.xda-developers.com/lg-bootloop-lawsuit-adds-nexus-5x-lg-g5-v20-case/
One guy at bottom of this thread has screen capture and says his 18 month old 5X shows as covered by warranty in their system.
https://productforums.google.com/forum/#!topic/nexus/PZrVO8g9Y9M;context-place=forum/nexus
Same here.
Nexus died after some freezes. After 7-10 failed boots it suddenly booted, just to freeze again after 1 or 2 minutes.
Tried every button combo with and without power plugged, no luck at all, just a dead brick with no signs of life at all.
Device was perfectly working till yesterday. No issues at all
Latest purenexus version. Everything was fine.
Don't get it.
Only thing what came to my mind was that we have been to the beach the day before. Had the phone in the backpack, but it went still really hot since the sun was strong.
But hey. Have been to definitiv hotter places last year in Croatia.
I thought i try the revive Motherboard in oven trick, since this oven thing already worked once for my laptop graphic chip which died also from overheating.
Put the MB in the oven for 12min at 200C.
No luck. Dead brick.
Any ideas?
Thanks for reading!
When my Nexus 5x died, LG replaced the motherboard and then everything was even much better than before.
quark-lepton said:
When my Nexus 5x died, LG replaced the motherboard and then everything was even much better than before.
Click to expand...
Click to collapse
Well. Got it from ebay.. No invoice.
Don't know if i can claim warrenty?
SchWeinSAuG said:
Well. Got it from ebay.. No invoice.
Don't know if i can claim warrenty?
Click to expand...
Click to collapse
LG has agreed to extend warranties on a case by case basis after they were sued. One lawsuit was dropped as a result, but the other remains. So they may be more willing than usual to fix it without proof of purchase, but only way to know is to call them.
http://www.androidpolice.com/2017/05/25/one-lawsuits-lg-nexus-5x-bootloop-dropped/
If you can't get any warranty help, then you can try the heatgun method. This seems to basically melt the solder again so that it'll work. If you're lucky, you get the one or few connections that are messed up.
Using a heatgun, I got mine from completely dead to where it performed normally for 9 hours. I thought I was back in business until it rebooted. Then it lasted a bit before rebooting, and every time would get shorter and shorter before rebooting. Now it is bootlooping at startup, but still alive. So I can adb the OTA back on there, clear cache and factory reset. And it charges. But it just bootloops.
https://www.youtube.com/watch?v=KQrsC2VZY0c
https://www.youtube.com/watch?v=wxQehPw4yPY
By they way, I tried a hairdryer for 30 seconds and it did boot to where I could unlock it, then it froze. The hairdryer just doesn't get hot enough to melt solder and only just heats things up to where there might be a temporary restoration of whatever connection or solder is broken. So I tried about 2 minutes and I could boot and swipe one screen left before it died. The heatgun took 1 minute 30 seconds to get it to where it would boot and work. I'm not going to go at it again since I have a chance at just getting a warranty swap if they extend it since I'm 2 months past the year coverage.
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
I have had the exact same problem, mine only occurs when the phone is ran down to 0% and powered off. I never let that happen but I have a 3 year old son who repeatedly does it, and every time i hold my breath, praying it will come back on. Well i am holding my breath and praying once again this morning,hoping it will power back on. Do you think it could be some kind of "protected mode"to keep the battery or something else from overheating or whatever?
alezmoroni said:
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
Click to expand...
Click to collapse
If you need the phone and are confident, try unlocking the bootloader, reflashing stock factory image and relocking the bootloader again. You will lose all the data, though.
If you can live without a phone for a while, just send it to Google/LG. Nothing else one can do imho.
When my phone was in the last steps of dying (eventual bootloop), I could disconnect the battery and it'd get farther through the boot cycle, or even once booted. Basically, after it wouldn't react to any buttons or combos, I would disconnected and reconnected the battery. Then I could give things another shot. So I'd start it, it'd make it to the colored circles, or I could boot to the recovery menu, and try some things, but at some point it would go black. Then it would not react to anything unless I disconnected the battery. Then it would react to the buttons again and eventually one of the steps would make it go black. And then take a disconnect to get another try.
It sounds like your phone may be close to dying.
By the way, I only opened it up since I was past the warranty expiration date, and LG extending the warranty to about 18 months wasn't a known thing at the time. It is actually easy to get everything apart, but hard not to make dings in the plastic cover even using plastic tools.
I would say, back up everything you can from it and expect it is going to get worse. Redoing the OS didn't save mine.
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
SuperGlueG4 said:
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
Click to expand...
Click to collapse
All devices up to March 2016 (so 603) are affected by the ilapo. Your story above sounds exactly like the ilapo. Read my signature for the ilapo fix list which may bring up some hours/days/months life back.
Sent from my LG-H815 using XDA Labs
SuperGlueG4 said:
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
Click to expand...
Click to collapse
You need a new battery
deltadiesel said:
You need a new battery
Click to expand...
Click to collapse
Lol
Sent from my LG-H815 using XDA Labs
I had something similar happen, except it is a 2016 model, I believe, to sum it up:
The battery seemed to be starting to die, so I bought a battery of eBay, but it also was having pretty bad battery life, so I drained the battery, to calibrate it, but now my G4 (H812) refuses to show any sign of life when I plug it in, or try to turn it on, is it also the Ilapo/Bootloop issue, or something else?
Hey, my zenfone 3 deluxe would freeze and go into a bootloop for some minutes, until booting normally again. Sadly, recently he went on a permanent bootloop. I can't even turn it off, it only stops until the bactery is completely drained. The max I can do is booting into fastboot mode (in fastboot mode I can't do anything, but it does not reboot), and "turn it off" (if i press power, volume up, and volume down buttons at the same time the phone stops bootlooping and the screen goes black. But in reality it is not turned off! Because the bactery drains anyways. Some hours later it shows the phone ran out of bactery). The phone is still in warranty, but the store where I bought it is asking for 112€ because my back camera is "broken" (literally has a scratch and works normally; biggest scam of my life). I'm still willing to pay the 112€. The thing is, i'm afraid this issue might happen again eventually, after being repaired. I tried to flash it (followed a tutorial in this forum) but I failed. I was afraid to go any deeper because I knew the warranty would end if i did so. So im asking now: Should I pay the 112€ and get a long term solution when my phone is able to boot normally again, or is this issue easily solvable and i'm just dumb (aka don't get scammed)? Or, perhaps, will this issue be permanently fixed when it comes from warranty (I've seen many people saying that they experience the same issue some months after their phones are repaired)?
I believe this is a common problem with these phones. Same thing happened to me and I'm pretty sure I recall reading other posts about the same problem. I'm led to believe this is engineered obsolescence but other than the few posts I've read and my own experience, I've no proof.
If the payment is to repair the phone or to replace it with the same model is advise against it.