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.
Related
Hello, I've been lurking around this forum for awhile and this is my 1st post! I've used the search feature and many other websites for my problems but cannot find anything similar =[.
My phone is 100% factory and the battery energy was around 80% at the time of incident, what happened was I received a text message but didn't check up on my phone till 30minutes later where then I pressed the home button to turn the screen on but the screen didnt power on but the phone's audible volume was working and the other 2 keys next to the home button lit up. I could click around my phone and function everything properly with no visual image to the screen (I even started my music player). I got frustrated so I attempted to soft reset it multiple ways and problem still persisted, I then decided to leave the battery out overnight to see if it would fix things, I did so and the same problem persisted, so I decided to plug it into the original usb wall charger and when I did i left the room, came back 10 minutes later tried turning it on and it doesn't even power up any more. Anyone have any ideas? The phone doesn't even turn on while plugged into the wall charger. (I do remember something about a phone update on my notifications list)
I had dropped the phone 2 months ago and the screen cracked but functioned normally and I'm afraid that I will not be able to claim warranty because they will blame the cracks.
Factory reset the device by booting into recovery.
If the screen will not function in recovery mode, or after boot. ...it's not good.
The digitizer may be toast. ..g
kpjo4 said:
Hello, I've been lurking around this forum for awhile and this is my 1st post! I've used the search feature and many other websites for my problems but cannot find anything similar =[.
My phone is 100% factory and the battery energy was around 80% at the time of incident, what happened was I received a text message but didn't check up on my phone till 30minutes later where then I pressed the home button to turn the screen on but the screen didnt power on but the phone's audible volume was working and the other 2 keys next to the home button lit up. I could click around my phone and function everything properly with no visual image to the screen (I even started my music player). I got frustrated so I attempted to soft reset it multiple ways and problem still persisted, I then decided to leave the battery out overnight to see if it would fix things, I did so and the same problem persisted, so I decided to plug it into the original usb wall charger and when I did i left the room, came back 10 minutes later tried turning it on and it doesn't even power up any more. Anyone have any ideas? The phone doesn't even turn on while plugged into the wall charger. (I do remember something about a phone update on my notifications list)
I had dropped the phone 2 months ago and the screen cracked but functioned normally and I'm afraid that I will not be able to claim warranty because they will blame the cracks.
Click to expand...
Click to collapse
sounds like the drop has caught up to the device. as the post above if it doesnt work in recovery the digitizer is TOAST
why would the digitizer be toast if it logged my screen touches while the screen went dead before not being able to power on? I cannot get into recovery mode mode because the phone will not even turn on =[.
bump... can anyone help?
Sounds like the phone is gone if it won't even show charging or any kind of screen. Is there any flicker or anything?
Sent from my SGH-I317 using xda premium
roughneckboren said:
Sounds like the phone is gone if it won't even show charging or any kind of screen. Is there any flicker or anything?
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
nothing at all =[, do you think samsung will warranty it even with the cracked screen? It was functioning normal for couple of months after i cracked the screen.
kpjo4 said:
nothing at all =[, do you think samsung will warranty it even with the cracked screen? It was functioning normal for couple of months after i cracked the screen.
Click to expand...
Click to collapse
I don't think they will, you're probably gonna have to eat this one.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Agreed. ..
You could try. ..but they will likely reject warranty and offer a repair. ..
Or offer a refurbished device at a reduced price. ..imho...g
If u bought warranty you can eat the cost of deductible. They have open enrollment til May 30th I think. I am not sure what the requirements are.
My G4 seemed to be running hot yesterday and I had to charge it several times more than normal. All of a sudden it shut down would not boot back up. I tried everything but it will not go in to recovery or download mode. No lights come on at all when charger is connected either. One time I was able to get the MEIE number to flash and it said press power to reboot before it blanked out again. I called Verizon and they said it sounded like a complete system/software crash. I am rooted but haven't made any changes to my phone in several weeks. Verizon overnighted a replacement to me and it should be at my house when I get home. I wonder if this is the same issue that has been happening to the Sprint version that was recalled? Possibly the phone was just mad at me because it happened an hour after I ordered my Nexus 6p......lol
Now that it's cooled off can you boot it up?
I would think you could have just rebooted it when you first noticed it was hot.
Colchiro said:
Now that it's cooled off can you boot it up?
I would think you could have just rebooted it when you first noticed it was hot.
Click to expand...
Click to collapse
No it still doesn't boot up. I can get to the LG screen for maybe a second and it shuts back down. When I first noticed that it was hot I could reboot it. I let it cool off before restarting it but the problem persisted. What ever was causing it to overheat was also draining the battery. I had to charge the phone up twice by 2:00 pm. My "certified like new replacement" arrived on Friday and initially everything was good. On Saturday the Wifi disconnected and would not turn back on. The icon just sits there and blinks at me. If I go in the settings menu it is grayed out and doesn't give me the option to turn it on. I just got off the phone with Verizon and they are sending me another G4. Hopefully I will have better luck with this one. I would like to have a working phone that I can sell when my Nexus 6p arrives.
Sorry this is totally off topic but, did you have to pay a deductible to get a new phone?
sefirosu0522 said:
Sorry this is totally off topic but, did you have to pay a deductible to get a new phone?
Click to expand...
Click to collapse
No I didn't. It was Warranty replacement so it didn't have to go through insurance.
I had a similar issue last week, no root, running 12a. Phone shut itself off during normal usage (checking football scores). Running a little hot so let cool. Never booted past Verizon splash screen. Tried fresh battery, factory reset, safe mode. Nothing. Got my "certified like new" model. So far so good, but 6P here I come.
Sent from my VS986 using Tapatalk
Hmmm well good timing if you ordered a Nexus 6P. You can sell it like new.
Haha I was just watching "The Nexus 6P will bend in half if you try to bend it in half" video. I'd be interested in a size comparison between the 2.
So this exact thing happened to me, just several days after I got it (same thing, also rooted, nothing much done to the phone).
I had figured the battery ran dead (because I knew it was low), but it just wouldn't power on. Chargers wouldn't light it up. I put it on the charger for hours, and nothing happened. Lost all hope.
Then, randomly, I decided to see if Download Mode would work on my phone. I don't know why I tried it.
I pulled battery, and put it back. I held on Volume (up?) on the phone, and plugged it into the computer.
OH MY GOD -- IT CAME TO LIFE -- ! DOWNLOAD MODE!
I shut it down from download mode, then turned it back on (I think a battery pull) and it worked again.
I was completely relieved.
This happened to me a second time, weeks later.
The same solution worked.
I hope that this helps someone.
TL;DR: Try Download Mode (pull battery and put it back in -- then, while holding the volume Up key on the phone, plug USB into your computer)
I just unlocked my phone and swiped down to check notifications. It immediately froze and the screen stayed on for awhile. Then the screen went black and I can't get the phone to start up. Tried holding power for a real long time and also volume down + power but still can't get it to start up. After messing with it for awhile I got it to briefly show the boot screen once and then once more I had it in the bootloader and I was able to scroll through the boot options but when I tried booting to recovery it died again. Connected to my computer the device manager sometimes shows it as "Qualcomm HS-USB QDLoader 9008". Any ideas if there's anything else I can try, or am I totally screwed?
I'm sorry to hear this, but is the known bootloop problem with hardware. It's caused by loosing solder balls on CPU. The best option tries to RMA, if you have a warranty.
That's what mine did. I was able to put it in the freezer and get a little life out of it, but never booted all the way. I used the hair dryer (following youtube videos on using a heat gun) heating of the CPU and motherboard and got some life out of it, but not a full boot.
So I bought a heat gun and got it to boot and for me to take most of the data off of it. Then it had issues, so I did a longer heating and it booted and acted normally. I thought it was actually fixed. But after 9 hours of acting like is was normal, it rebooted itself. It lasted for a while, then rebooted and lasted less time, and the cycle reduced really quickly to just bootlooping. I gave the heat gun one more try and pressed the CPU down with a wooden spoon to see if that made a difference, but it started the reboot cycle maybe 30 minutes into trying to set it back up. Google replaced mine though it was a few months past the end of the 12 month warranty since I bought it from them.
LG is extending the warranty on the 5X on a case by case basis. So you should give them a try.
Thanks guys. I did get it to boot into the bootloader a couple more times last night, but I wasn't able to get it to do anything meaningful. Whenver I tried booting to system or recovery it just hung up on the Google screen. I have it boxed up now and looks like it's going back to LG again.
UPDATE: Got an update from LG that my phone is undergoing repair. When I started the RMA and gave my IMEI they warned me the phone may not be under warranty. But according to the update they sent me they're indicating that it is covered under warranty - so apparently it's true that they're extending warranties to cover the hardware boot loop issues from faulty solder connections. Hopefully they'll even send my phone back with the SIM tray this time...
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.
About a week ago, with my battery at 39% i plugged my z5 premium in to charge and it never came back on again.
I have tried all the usual tricks, pwr and vol up, removing the battery, the sim slot button, and pretty much any combination of buttons and still nothing.
It will charge just fine, but will only reach the white sony xperia screen and no further. it will flash up the white screen then go black with the notification light flahing red 3 times and then staying red. once or twice it has started to load the 'powered by android' screen and then just blackness. If i hold vol down and plug into laptop the notification light will turn blue and it shows up as 'adb android device'. Thats the extent of the life left in it.
So what would people suggest as my next step? is it still possible to recover the data thats on the phone or is it a total loss?
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Pixelado said:
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Click to expand...
Click to collapse
hello,
im having the same issue, but how it would be flashed and the computer didn't detect it?
what's the trick in that? thank you
Nidhal AKA the king said:
hello,
im having the same issue, but how it would be flashed and the computer didn't detect it?
what's the trick in that? thank you
Click to expand...
Click to collapse
If your computer cant detect the phone, it could be one of the following:
- Bad usb cable
- Bad usb charging port on the phone
- Dead battery
- Dead motherboard
If your computer doesn't make any sound when plugging the phone in, then missing drivers shouldn't be the problem and you should troubleshoot each of the possibilities I mentioned.
Pixelado said:
If your computer cant detect the phone, it could be one of the following:
- Bad usb cable
- Bad usb charging port on the phone
- Dead battery
- Dead motherboard
If your computer doesn't make any sound when plugging the phone in, then missing drivers shouldn't be the problem and you should troubleshoot each of the possibilities I mentioned.
Click to expand...
Click to collapse
Thanks for the tips.. I will check again and i hope it will be detected.
Sent from my Sony H8416 using XDA Labs
2-minute reset.
I thought mine was bricked after only 2 months. I came across this fix on the Sony website and it fixed mine where it could work again. I had to factory reset it. It was just locking up and freezing. Be sure to hold that button in for 2 solid minutes. I watched the clock. Longest 2 minutes of my life.
https://support.sonymobile.com/glob...em-&-performance/i-cannot-power-on-my-device/
Pixelado said:
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Click to expand...
Click to collapse
I am just adding a list of similar threads that have been recently posted regarding this strange sudden death issue, battery not charging, weird non-software bootloop.
Sudden Death
InfiniteBootLoop
Unable to Turn On
My Phone Just died (april2019)
Not charging (user is rooted though)
I think i will also collate many of the similar threads into titles and post it as a new thread. As this forum is extremely bloated and repetitive whilst simultaneously being confusing for some users.
I guess Z5P is old now, but trust me the XZ3 is complete garbage so support for Z5P should be much cleaner and better organised now.
Any news for this?