Android 7.0 Nougat update permanently damages some Nexus 5X devices

One of the joys of owning a Nexus device is the pure, unadulterated Android experience. When it comes to update time, while most other Droidsters must deal with carrier and OEM delays, Nexus owners generally can kick back -- cigar in one hand, device in the other -- and bask in the knowledge that they'll be among the first recipients. If you're a Nexus 5X owner with designs on Android 7.0 Nougat, however, you might want to put that champagne on ice for now; there's a slim chance your device could be snared by an inescapable barrage of random reboots.

Apparently, the update causes / exposes a hardware issue within a small number of Nexus 5X handsets. Once updated to Nougat, devices randomly reboot, and while Google is aware of the issue, there's apparently no fix other than to get the device repaired or replaced. 

According to a Googler:

Folks stuck with the continual reboots have reportedly tried several of the usual fail-safes such as clearing the cache, applying a factory reset and even booting in Safe Mode, to no avail. Bottom line, if your Nexus 5X keeps rebooting, it's probably not going to stop on its own. Rather than waste your time trying to figure out how to fix it, you should instead seek repairs as recommended above. 

Has your Nexus 5X been playing up since you installed Android 7.0 Nougat? Do share your story with us in the comments!

No images

source: Google via Phandroid

Related phones

Nexus 5X
  • Display 5.2" 1080 x 1920 pixels
  • Camera 12.3 MP / 5 MP front
  • Processor Qualcomm Snapdragon 808, Hexa-core, 1800 MHz
  • Storage 32 GB
  • Battery 2700 mAh(20h talk time)



1. meanestgenius

Posts: 22290; Member since: May 28, 2014

I'm going to say the same thing for Google that I've said for Apple: This is unacceptable. A company of Google's magnitude should not have this happening to one of their own Google branded devices with their own OS, especially with no apparent fix available.

3. Acdc1a

Posts: 475; Member since: Jan 21, 2016

Unlike a battery that explodes or a device that bends or doesn't make calls when you hold it wrong, sometimes you just don't know what a software release is going to do until it's released. I would hope that Google/LG quickly repairs these devices under warranty.

8. meanestgenius

Posts: 22290; Member since: May 28, 2014

Sometime unexpected things do happen, and sometime they happen because of lax QC. Google should, at the very least, test software on all Google branded devices before releasing it to the masses.

14. RebelwithoutaClue unregistered

But like it says in the article, not all devices are damaged. It is the result of a hardware failing coming to light with the new update. I am pretty sure Google has tested Nougat on plenty of Nexus devices before they pushed it. Not to mention all the people giving feedback who ran the preview version. I do hope those faulty devices will be replaced by Google.

17. meanestgenius

Posts: 22290; Member since: May 28, 2014

I'm not claiming that it's on all devices, but the fact that it's happening to some Google branded devices with no fix other than to get another device is not acceptable. This is something that could have been avoided with thorough testing.

23. Finalflash

Posts: 4063; Member since: Jul 23, 2013

First off, if it is a bootloop issue, that is fixable by just going to the previous version of android which can usually be easily done via sideloading over adb if you can get to the recovery (which people seem to be able to). Secondly, good thing they do a staged roll out because that means a subset of a subset will have this problem, which will be solved and then delivered to the rest. Finally, if you read the source, it isn't as bad as iPA is making it out to be. Random reboots are happening but people are able to get into their phones. Turns out some apps are causing the reboots and uninstalling them helps. So this is one of those things that are difficult to even test with a beta due to the insane number of apps out there.

27. meanestgenius

Posts: 22290; Member since: May 28, 2014

Did you see me type anything about it being really bad? No? Good. Because I didn't either. So far, there is no fix for it. And if it is indeed a combination of hardware/software issue, how will it get fixed for devices already infected?

40. Mxyzptlk unregistered

Trust me when I say this but I don't want to admit he's right but unfortunately he's right. Every time Apple has an issue like this, the Android fans come in full force. Now the shoe is on the other foot.

48. meanestgenius

Posts: 22290; Member since: May 28, 2014

The sky must be falling, because we agree.

50. trojan_horse

Posts: 5868; Member since: May 06, 2016

He agrees with you because you're now saying what he likes to hear. Did he agree with you when you said the same software/updates failure about Apple? Of course, not.

59. Mxyzptlk unregistered

No one asked you for your comment.

76. JunitoNH

Posts: 1946; Member since: Feb 15, 2012

No, because he's being honest, and is not bias. Even after it became factual about the exploding phones, some of you were in denial.

58. Mxyzptlk unregistered

...don't remind me.

61. meanestgenius

Posts: 22290; Member since: May 28, 2014

I'll be reminding you of it for the rest of your life. :)

72. AlikMalix unregistered

Aww, just hug already...

73. RebelwithoutaClue unregistered


74. trojan_horse

Posts: 5868; Member since: May 06, 2016

A kiss and make up after all the battle and beef they've had against each other. This is too good to be real. You dig, bruh?

83. Mxyzptlk unregistered

Do me a favor and just shut the f*bleep* up, ok.

81. meanestgenius

Posts: 22290; Member since: May 28, 2014

He's not my type, lol.

84. Mxyzptlk unregistered

We all know you're a drag type.

87. meanestgenius

Posts: 22290; Member since: May 28, 2014

Keep your relatives out of this, please.

82. Mxyzptlk unregistered

Please don't...

89. meanestgenius

Posts: 22290; Member since: May 28, 2014

Stop begging. It's pathetic.

85. Mxyzptlk unregistered

Don't push it...

88. meanestgenius

Posts: 22290; Member since: May 28, 2014

I'll push it as far as I want.

69. vincelongman

Posts: 5728; Member since: Feb 10, 2013

Its probably because of LG The G4, G5 and V10 all had hardware issues with bootloops

30. VZWuser76

Posts: 4974; Member since: Mar 04, 2010

I've said what you are many times before, but I've also qualified that saying that due to the varied apps and setups and alterations made by the end users, it's near impossible to put out an update that accounts for everything. For all we know it could be a combination of certain apps running and settings set a certain way that causes this issue. As I said, with so many variables, for them to fully test these devices to gst even 90% issue free updates, by the time they'd have it ready to go, theyd have to start all over again because the next update would be ready. In this case, we have to settle for them addressing the issue quickly.

41. Mxyzptlk unregistered

Your comment boils down to one word, technicality.

54. VZWuser76

Posts: 4974; Member since: Mar 04, 2010

Close. The word you're looking for is reality. I'm not surprised you didn't recognize it.

60. Mxyzptlk unregistered

I'm not surprised that you're going in circles after being put on the spot.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.