LG Nexus 5X dead after sudden freeze - Nexus 5X Q&A, Help & Troubleshooting

My Nexus 5x (bought 6 months ago) turned off unexpectedly while I was using it.
I was reading an email, when the screen suddenly stopped updating. It was totally unresponsive, no video (unless that I was seeing before the freeze) and no sound. I didn't have a way to bring it back.
After some seconds the screen turned off. I tried to turn the phone on, but I wasn't lucky. It didn't react to power button, usb, power cable, volume buttons combos, nothing. No vibration or sound.
I thought the phone was still on, so I disassembled it, I removed the back cover and the things that prevent the battery to be removed. I didn't removed the battery, but I detached the small cable that connected the battery and the phone, and then I attached it again. I reassembled it.
Then, still no results.
Can someone please help me? I'm using an IPhone 4s now (which I bought for 15€), and I feel such an horrible person...

Try plugging it into the wall charger for about 30 minutes then use the 3-button combo to get into the bootloader. I thought my 5X died one time but it eventually responded to my attempts to turn it back on after a time.

Same issue here, its 99% dead, no vibration, no led light, nothing on screen....
It happen to me while flashing stock rom via fastboot, it rebooted once and droped dead on me.
I opened the phone and did the same thing with the battery, and.. the same , nothing.
It gets detected by my PC, but i cant use the LGUP tool to flash the tot file, LGUP says "model unknown"...
Trying now with QFIL, but i need to find all the needed files..
By the way, it gets auto-detected as Qualcomm HS-USB QDLoader 9008 on my PC, it charges(gets warm).. but no life out of it yet.

I charged it all the night, and the combo didn't work (I tried just 10 minutes ago)...
I'll try using that tools, but I think it won't be recognized at all. Mine doesn't become hot when I charge it...

On which android version are you guys?

7.0.1 stable, I think

i was on 7.0.0 (NBD90W, Oct 2016)

Same thing happened to me. I am going to try sideloading an earlier OTA update through ADB. I will let you know the outcome.

I sent the device to the LG support, hopefully I'll have it back in janurary

Im going to send it for repair too, i have lost my receipt for it, but i got a copy, and now can ask a repair

same here.

Related

wet phone = dead phone

So Wednesday my wife dropped my Xperia Play (r800x) in a vat of chicken broth. She did NOT turn it off but she put it in a bag of Rice. About 3 hours later I found out about it and immediately pulled the battery and put it back in the bag. (4:00 PM July 3)
12:00 PM July 5. I take the phone out of the rice bag. Using alcohol pads I lovingly clean all exposed surfaces of the phone and squeeze some in to each button and press it multiple times to clean out any remaining gunk.
After doing this and letting it sit for 5 minutes to let the alcohol evaporate, I put the battery back in and pressed the power button. 1 short vibration and then NOTHING.
I connected it to my PC via flashtool and re-flashed the stock firmware disconnected and powered on. 1 short vibration and then nothing.
I connected to the SE update service and was told that I had modified software and it couldn't install. So I connected back to flashtool and relocked my bootloader. Connected back to SE update service and was told I had the latest software so I used it to RE-install. Powered on phone and Voila! short vibration followed by nothing. This is where I stand now.
It would appear that I can boot in to both flashtool AND fastboot, but I cannot power on the phone.
No LED's are lit when I press the power button nor when I plug it in.
I do however have a green LED in flash mode and a blue one in Fastboot.
If I don't boot to one of those and connect to my computer it is recognized as a sony media device. after a few minutes the device disconnects and reconnects to my computer. I can't see it in "My Computer" but I know because windows makes the device connected sound and the device disconnected sound.
What next? It's back in the rice bag until I get a better idea.
Maybe battery is faulty. Does it have charging animation when you plug it to wall charger?
Bakisha said:
Maybe battery is faulty. Does it have charging animation when you plug it to wall charger?
Click to expand...
Click to collapse
I haven't actually tried it in a wall charger but I have tried it with both the extended battery that was in it as well as the original OEM battery.
I'll try plugging it directly in to the wall next.
Thanks.
It's plugged in directly to the wall using the actual Sony charge/sync cable. Still nothing. No charging animation. But I do have a Red LED.
swing4thefence said:
It's plugged in directly to the wall using the actual Sony charge/sync cable. Still nothing. No charging animation. But I do have a Red LED.
Click to expand...
Click to collapse
Now, No LED.
swing4thefence said:
It's plugged in directly to the wall using the actual Sony charge/sync cable. Still nothing. No charging animation. But I do have a Red LED.
Click to expand...
Click to collapse
Actually, i tought it was battery fault, but you test it with second battery, so i don't think battery is the problem.
Power it normally with power button (and get that single vibration), then, when you connect it to PC, is it in fastboot or flashboot mode? Maybe back or search key is stuck (short-cutted, so it's like always pressed)
Bakisha said:
Actually, i tought it was battery fault, but you test it with second battery, so i don't think battery is the problem.
Power it normally with power button (and get that single vibration), then, when you connect it to PC, is it in fastboot or flashboot mode? Maybe back or search key is stuck (short-cutted, so it's like always pressed)
Click to expand...
Click to collapse
Tried that:
"Device Connected with USB debugging off"
"For 2011 devices line, be sure you are not in MTP mode."
swing4thefence said:
Tried that:
"Device Connected with USB debugging off"
"For 2011 devices line, be sure you are not in MTP mode."
Click to expand...
Click to collapse
That message is just because you flashed stock firmware. But it means it start to boot normally.
Unless you know how to open phone and clean it inside, it's maybe better to go service. Good news is that is working (partially) and maybe only flex cable is damaged/short-cutted
I would highly recommend to take apart the phone have all the pieces in a bag of rice for 24 hours.... let it absorb all the junk, or at the least take it apart and use aclohol pads to clean it all up... then let it sit and air out for a while, the reassemble... retest.
Maybe try taking it apart and look for something that might be damaged
Sony Ericsson Xperia Play Take Apart Repair Guide
Re-House Your Xperia Play : Things to Know
Update: sorry ozzmanj1 didn't see your post
I am having a similar problem
On Wednesday, instead of making chicken I was helping a friend move on a nice, hot day. I was sweating like a filthy pig and my phone was in my pocket and would not turn on when I tried to do so. That night I really didn't know what was wrong and the next morning I tried to turn it on and the red LED would flash 3 times in succession. I looked this up and they said "dead battery." Sure enough, I charged it and it took a minute for the LED to turn on, and as it charged it was red, then orange, then green. But even once fully charged, when I tried to turn it on it would only vibrate, but no screen action whatsoever. Note: the battery was at around 60% when the phone quit responding. The next morning it was dead. I have had the phone for a year now and the battery will last me at least 2 days if I don't play games and such.
The next morning, when using the flashtool it would go into blue LED'd fastboot and green LED'd flash mode. I flashed the original 2.3.3 firmware and still nothing. I used PC Companion and it said "Problem: The phone/tablet contains modified software that cannot be updated. Details: Sony Update Engine failure (error 2003)." I contacted Sony and I am still awaiting a response. So, on friday I'm ready to take this turd into the Verizon shop and I turn it on and wait about 30 seconds and I get the SE logo. It loads just fine. I set it up and try to update, but it won't allow me. I'm thinking, great, I'm stuck with 2.3.3... until I turn the screen off and try to turn it back on. And again, nothing. No response. So I'm thinking I will bring it in Saturday. I re-lock the bootloader in some attempt to hide that I rooted the phone, and flashed the 2.3.3 again. Note: I rooted my phone in December and have had no problems. I didn't flash any ROMs or Kernels. I am a simple man.
Saturday morning, after my phone has been off for 10 hours, it turns back on again. Same thing happens. Also, I spent a while on Thursday, Friday, and today trying to research and solve this problem. My brain hurts. But alas, I only had it off for 3 hours and it turned back on, and it did the same damned thing when it turned off. It simply doesn't turn back on. I don't know if it's the screen, or if there is moisture under there, and I haven't researched taking it apart yet. Any advice? Sorry if I'm butting in on your post, but your problem is so close to mine aside from my phone actually coming back to life, partially.
-Ryan-
Streiff353 said:
On Wednesday, instead of making chicken I was helping a friend move on a nice, hot day. I was sweating like a filthy pig and my phone was in my pocket and would not turn on when I tried to do so. That night I really didn't know what was wrong and the next morning I tried to turn it on and the red LED would flash 3 times in succession. I looked this up and they said "dead battery." Sure enough, I charged it and it took a minute for the LED to turn on, and as it charged it was red, then orange, then green. But even once fully charged, when I tried to turn it on it would only vibrate, but no screen action whatsoever. Note: the battery was at around 60% when the phone quit responding. The next morning it was dead. I have had the phone for a year now and the battery will last me at least 2 days if I don't play games and such.
The next morning, when using the flashtool it would go into blue LED'd fastboot and green LED'd flash mode. I flashed the original 2.3.3 firmware and still nothing. I used PC Companion and it said "Problem: The phone/tablet contains modified software that cannot be updated. Details: Sony Update Engine failure (error 2003)." I contacted Sony and I am still awaiting a response. So, on friday I'm ready to take this turd into the Verizon shop and I turn it on and wait about 30 seconds and I get the SE logo. It loads just fine. I set it up and try to update, but it won't allow me. I'm thinking, great, I'm stuck with 2.3.3... until I turn the screen off and try to turn it back on. And again, nothing. No response. So I'm thinking I will bring it in Saturday. I re-lock the bootloader in some attempt to hide that I rooted the phone, and flashed the 2.3.3 again. Note: I rooted my phone in December and have had no problems. I didn't flash any ROMs or Kernels. I am a simple man.
Saturday morning, after my phone has been off for 10 hours, it turns back on again. Same thing happens. Also, I spent a while on Thursday, Friday, and today trying to research and solve this problem. My brain hurts. But alas, I only had it off for 3 hours and it turned back on, and it did the same damned thing when it turned off. It simply doesn't turn back on. I don't know if it's the screen, or if there is moisture under there, and I haven't researched taking it apart yet. Any advice? Sorry if I'm butting in on your post, but your problem is so close to mine aside from my phone actually coming back to life, partially.
-Ryan-
Click to expand...
Click to collapse
Ryan I think you're as screwed as I am. Still I wouldn't expect your phone to be ruined by Butt Sweat. Yeah, putting your phone in your hip pocket to help someone move is a bad idea but I would expect Mechanical damage, not moisture damage.
At this point I'm thinking of just putting it up on Ebay as As is/For parts to see what I can get out of it. It's painful to think of giving up my sweet playstation phone but looking at it logically, in the year that I had it I only used the playstation controller 4 times.
The question I have is how to be sure that all of my personal data is off the phone since I can't boot it to verify.
swing4thefence said:
The question I have is how to be sure that all of my personal data is off the phone since I can't boot it to verify.
Click to expand...
Click to collapse
Since you manage to flash stock firmware, all data is erased. Erase sd card on pc with some adaper, if you want to sell that sd card along your parts
swing4thefence said:
Butt Sweat
Click to expand...
Click to collapse
Yeah, I figured it was mechanical, but I have a heavy duty trident case and I'm only assuming it was the butt sweat. This morning I tried to turn it on and nothing happened, so I said screw it and brought it back to Verizon. My main fear of bringing it back was them seeing that it was rooted and not being able to swap it out. But alas, the guy behind the desk just processed it, dropped my phone on the floor, hahaha, then set it up for me to get a replacement. It is under a year that I have had it, and I'm only paying for expedited shipping. I wish you the best of luck.
Hahahahahahahaha!!!!
You need to open it and replace ribbon connecting dispay with board.
I fallen with my phone to river (look for my posts she is alive after swimming), I removed battery on site by stripped down after back home. For me that ribbon started falling appart. I had same symptoms, pushed power button and feeling vibration, sometimeswhen reconnected I had whole white screen.
Bought that ribbon on e-bay, replaced and all working fine.
Good luck!!!
Sent from my R800i using xda app-developers app

Phone won't turn on anymore

Hi everyone,
my phone simply won't turn on anymore. It was still working fine yesterday and before I went to sleep I plugged it in the original AC charger like everyday (the phone was on ~50% battery and still working after I plugged it in). But when I tried to wake up to phone in the morning nothing happened. I disconnected the charger and tried to turn on the phone again but still nothing. Then I tried connecting it to my computer but that did not work either. The phone does not show any signs that it is "alive".
I checked the charger and usb port of the phone if their is any visible hardware damage but there wasn't. The phone is only 3 weeks old and was working fine until yesterday. It was running on MDB08M and the bootloader was unlocked so I do not know if I can send it back on warranty.
Anyone here who got the same problem and found a solution?
(sorry for my bad english)
I would try connecting it to the PC and check device manager for any signs of life.
I had a similar problem, the charger died but luckily I had a spare charger
Sent from my Nexus 5X using Tapatalk
I have tried connecting it to my computer but there is no sign of life.
I guess there is no other choice than sending it back to google with the bootloader unlocked ...
My phone has died almost the same. It started to reboot itself like almost everytime ((( and same with unlocked bootloader.... I had mine for 2 weeks. Now I wonder if its common issue with N5X... Did you send your to repair???
This just occurred on my phone. Working just fine with 80% battery. Started GMaps to get some directions. Hung for a couple of seconds then just turned off. Won't respond to button pushes and won't go into recovery mode either. It's like the phone is dead dead.
All these threads about 5xs dying. I guess I better really start saving for a op3t. ? I've had mine a year and it's been fine but from what I've gathered from reading, someone said that's when they usually bite it is a year+... ?
Sent from my Nexus 5X using XDA-Developers Legacy app
Not sure if it has anything to do with it or not but I never leave mine plugged in all night. I zap it an hour and roll out... Always scared it would melt for some reason..lol

Nexus 5X won't turn on, bootloop when charging

So yesterday I was trying to make a phone call and the phone went dead. I tried turning it back on but to no avail. When connected to a charger, it just shows the battery for a while and then it disappears and reboots to showing it again only to reboot itself again. Needless to say, I am stuck with a bricked phone. I managed to get it up and running by flashing the stock rom but after update to Android 7.0 the problem came back after like 10 hours. Now I can't even get into bootloader without the phone being connected to a charger, which is a problem because I can't flash anything through charger obviously. Connecting the phone through USB does not work, the phone stays dead like it is out of juice. With that being said I think it might be a faulty bootloader. The power button is fine, so I think we can count this option out. Any other ideas? I am considering taking the phone to the shop where I bought it as it is still under warranty but because it is not Google they might refuse to replace it with a new one or repair it. Is there anything I can do?
EDIT: I sent it to LG.
kubatbg said:
So yesterday I was trying to make a phone call and the phone went dead. I tried turning it back on but to no avail. When connected to a charger, it just shows the battery for a while and then it disappears and reboots to showing it again only to reboot itself again. Needless to say, I am stuck with a bricked phone. I managed to get it up and running by flashing the stock rom but after update to Android 7.0 the problem came back after like 10 hours. Now I can't even get into bootloader without the phone being connected to a charger, which is a problem because I can't flash anything through charger obviously. Connecting the phone through USB does not work, the phone stays dead like it is out of juice. With that being said I think it might be a faulty bootloader. The power button is fine, so I think we can count this option out. Any other ideas? I am considering taking the phone to the shop where I bought it as it is still under warranty but because it is not Google they might refuse to replace it with a new one or repair it. Is there anything I can do?
EDIT: I sent it to LG.
Click to expand...
Click to collapse
I had the same issue just a few weeks ago, did you ever get it back? How long did it take? Was covered under warranty?
Thanks - Ed

totally unresponsive G3, no bootloop, battery good - what next?

I've got a totally unresponsive G3 - it died on me unexpectedly. It had been a little "off" when I was setting it up - telling it to reboot sometimes required a VOLUME UP+DOWN+POWER to actually boot it up, had a tough time getting the LGFlashTool to work and ended up having to use imageprepGUI to achieve root/TWRP, had it trigger the "error: boot certification verify" trouble and had to walk it back with the Qualcomm drivers... anyhow, I finally got it all set up the way I wanted for one of my kids as a Christmas present and just after getting Lucky Patcher up and running (wiped the cache, installed a modded Google Play, etc) I asked my wife to charge it as it was on low power, around 10% or so. She plugged it in and...
Well, my son went to use it hours later and it was dead.
This thing is the deadest I've ever seen a phone. It doesn't respond to having a USB plugged in. I have two other LG G3s and swapped the batteries around - all of the batteries are charged and functional (including the one originally from the dead phone). It's the actual phone that appears dead. The LED doesn't respond to plugging in, there's no vibration on plugging it in, no combo of cables seem to work. Plugging it into a computer doesn't generate any response from my laptop or the phone.
I've brought phones and specifically LG G3s back from the underworld more than once, but this has me stumped. Any ideas? So far, Googling has offered up the following solutions:
1. Remove battery
Hold down power button 10s+ to drain phone entirely
Plug in battery
Allow to charge for 20min
Hold down power button for 10s+
2. Remove battery for extended period
Plug battery in
Turn phone on
I can tell you that method #1 doesn't work here. I'm about to try method #2... but I don't have a lot of hope.
Any other ideas?
I had that probleme 4 days ago, i fixed it by burning the internal memory with a Hair Drayer.
Don't burn the screen, you must burn only the emmc on the motherboard.

[H812] G4 Died Overnight?

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?

Categories

Resources