x PhoneArena is hiring! Reviewer in the USA
  • Hidden picShow menu
  • Home
  • News
  • Android 7.0 Nougat update permanently damages some Nexus 5X devices

Android 7.0 Nougat update permanently damages some Nexus 5X devices

Some Nexus 5X device owners are getting more than they bargained for with the Nougat update

Some Nexus 5X device owners are getting more than they bargained for with the Nougat update

_
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:

We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options. We’re sorry for the inconvenience and appreciate your continued patience.

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!


source: Google via Phandroid

90 Comments
  • Options
    Close





posted on 21 Sep 2016, 12:53 14

1. meanestgenius (Posts: 15046; Member since: 28 May 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.

posted on 21 Sep 2016, 13:04 1

3. Acdc1a (Posts: 333; Member since: 21 Jan 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.

posted on 21 Sep 2016, 13:12 5

7. Bm888 (Posts: 516; Member since: 06 Jul 2015)


agreed.. and you wonder what a beta version is supposed to do if not for quality assurances at the end updates

posted on 21 Sep 2016, 13:13 2

8. meanestgenius (Posts: 15046; Member since: 28 May 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.

posted on 21 Sep 2016, 13:14

9. meanestgenius (Posts: 15046; Member since: 28 May 2014)


Exactly.

posted on 21 Sep 2016, 13:26 1

12. Doakie (Posts: 2170; Member since: 06 May 2009)


:-/ I love Android, but Nexus software has always been to buggy to me. All Nexus software is stuck in RC1 phase.

posted on 21 Sep 2016, 13:29

13. Scott93274 (Posts: 5218; Member since: 06 Aug 2013)


"I'm going to say the same thing for Google that I've said for Apple:"

"Yeah, but there really is only so much a company can do in regards to troubleshooting before a release. I mean, you have a product that will reach millions upon millions of consumers and the complexity of the mobile OS is only growing each year. Apple has it easy as they only have their own lineup of devices to account for. Then again, Google also has it's Nexus Guineapigs that are sorta like beta testers that get the updates before anyone else. I know I've already reported issues with the latest release, and hopefully my input makes for a better 7.1 release for everyone else."

posted on 21 Sep 2016, 13:31 5

14. RebelwithoutaClue (Posts: 3256; Member since: 05 Apr 2013)


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.

posted on 21 Sep 2016, 13:43 1

17. meanestgenius (Posts: 15046; Member since: 28 May 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.

posted on 21 Sep 2016, 13:45 1

20. meanestgenius (Posts: 15046; Member since: 28 May 2014)


There's no excuse for this. The big boys are slipping in the QC department.

posted on 21 Sep 2016, 13:56 1

23. Finalflash (Posts: 3393; Member since: 23 Jul 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.

posted on 21 Sep 2016, 14:10

25. Scott93274 (Posts: 5218; Member since: 06 Aug 2013)


So just that we're clear, it's Google's fault for a "hardware issue" on an LG phone that impacts only "a small number of Nexus 5X handsets"?

I've spent 6 years in quality control and in my experience a lot of product defects are identified by the consumer. Not all the time, but a majority of the time, it's the 3rd party manufacturer that's to blame for the issue, and not actually the result of a defective design.

What's more important than anything is how the company responds to the reports and it looks like Google is handling things. I think right now you're just overwhelmed by all the reported problems that accompany sloppy phone launches and major software updates.

posted on 21 Sep 2016, 14:12 1

27. meanestgenius (Posts: 15046; Member since: 28 May 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?

posted on 21 Sep 2016, 14:15 1

28. meanestgenius (Posts: 15046; Member since: 28 May 2014)


Isn't it really a combination of hardware and software? Because the hardware was fine before the release of Nougat.

I'm not "overwhelmed" by anything. These issues cropping up are definitely a QC issue. Not entirely in all cases, but QC plays a part in all of them.

posted on 21 Sep 2016, 14:22

30. VZWuser76 (Posts: 4681; Member since: 04 Mar 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.

posted on 21 Sep 2016, 14:26

32. Scott93274 (Posts: 5218; Member since: 06 Aug 2013)


It has to be a hardware issue, if they're working on an exchange program already and there's no report of a pending patch then the defect has to be isolated to the hardware.

Besides "We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue".

The details are in the article.

posted on 21 Sep 2016, 14:28

33. VZWuser76 (Posts: 4681; Member since: 04 Mar 2010)


But like I said above, with all of the variables in devices like these, how things are set in the settings, apps installed and running, differences in drivers and kernels, hardware tolerances, and end user alterations, it's impossible to put out a flawless update. And since QC will never be 100% either, it's just one more variable that can cause issues.

Something else to consider is that the more intricate and complicated something becomes, the higher probability for issues to occur. I believe it was famed engineer Montgomery Scot that said "The more they over think the plumbing, the easier it is to stop up the drain."

posted on 21 Sep 2016, 14:41 3

37. TerryTerius (Posts: 2101; Member since: 10 Apr 2014)


All I see is yet another LG device with bootloop problems.

posted on 21 Sep 2016, 14:53

40. Mxyzptlk (Posts: 16281; Member since: 21 Apr 2012)


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.

posted on 21 Sep 2016, 14:54

41. Mxyzptlk (Posts: 16281; Member since: 21 Apr 2012)


Your comment boils down to one word, technicality.

posted on 21 Sep 2016, 14:56 1

43. Subie (Posts: 1273; Member since: 01 Aug 2015)


I agree.

posted on 21 Sep 2016, 15:12 1

47. meanestgenius (Posts: 15046; Member since: 28 May 2014)


Even if it is just a hardware issue, which I don't believe, it's a Google branded device. Where is the QC for devices that are carrying the Google name?

posted on 21 Sep 2016, 15:13 1

48. meanestgenius (Posts: 15046; Member since: 28 May 2014)


The sky must be falling, because we agree.

posted on 21 Sep 2016, 15:15 1

49. meanestgenius (Posts: 15046; Member since: 28 May 2014)


But it's much less of a variable because it's one brand of device carrying Googles name on it. Like I said earlier, Goggle should be applying the best QC practices possible with a device with their name on it.

posted on 21 Sep 2016, 16:06 1

50. trojan_horse (Posts: 3678; Member since: 06 May 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.

posted on 21 Sep 2016, 16:29

51. NarutoKage14 (Posts: 783; Member since: 31 Aug 2016)


Both Apple and Google need to move to a 2 year OS update cycle now. Both OS's are far too advanced and complicated to fully hash out in only 1 year. The fact that every year each new release arrives with more bugs than the last can attest to that. Even Apple who claims to not release anything until it's 110% ready is plagued by so many bugs they don't get them all fixed until just before the next OS version.

posted on 21 Sep 2016, 17:08

52. Scott93274 (Posts: 5218; Member since: 06 Aug 2013)


Well, I've been using Nougat for a while now and aside from the battery issue which is being addressed, it works amazingly well. As for Apple, they wouldn't be able to go to a 2 year update cycle for their OS because many of their primary apps don't get updated unless there's a full system update.

posted on 21 Sep 2016, 17:16

54. VZWuser76 (Posts: 4681; Member since: 04 Mar 2010)


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

posted on 21 Sep 2016, 17:22

55. VZWuser76 (Posts: 4681; Member since: 04 Mar 2010)


This isn't the first time a small number of devies have had issues. It happens on every update on pretty much every device. Some say the update trashed their device, some say on the same update their device runs better than before. I've already seen one comment in here saying that. So how do you figure it's Google's QC issue when some are running fine or better and some are bricked? It's the same software going to every 5x right? Then doesn't that point to an issue where it's most likely has to do with the setup of certain devices?

posted on 21 Sep 2016, 17:43

58. Mxyzptlk (Posts: 16281; Member since: 21 Apr 2012)


...don't remind me.

Want to comment? Please login or register.

Latest stories