Nougat update bricked my Moto Z Force 11-30-2016

[Jimmy10mm]

I installed it this morning when it was shown on my phone as ready to go. Two hours later, the screen flickering on and off every few minutes, I drove over to VZW and they are having a refurbished device sent to me.

Fortunately for me they didn't accept my old Razr HD Maxx as a trade in because of a cracked screen. So at least I have a phone in the meantime. They reactivated the old device.

I still have the Moto Z Force. I'm supposed to send it back when I receive the replacement. I know better than to do an update when they are newly released, but I figured I'd dodge the bullet. No such luck.

 

[Ry]

I installed it this morning when it was shown on my phone as ready to go. Two hours later, the screen flickering on and off every few minutes, I drove over to VZW and they are having a refurbished device sent to me.

Fortunately for me they didn't accept my old Razr HD Maxx as a trade in because of a cracked screen. So at least I have a phone in the meantime. They reactivated the old device.

I still have the Moto Z Force. I'm supposed to send it back when I receive the replacement. I know better than to do an update when they are newly released, but I figured I'd dodge the bullet. No such luck.

Not sure what waiting is going to do if it's the same update though.

 

[Jimmy10mm]

In the event that the update is buggy, as this one apparently is, I would read on the forums posts such as mine. Once it seemed all was cleared up, fixed, then install the update. I don't like beta testing unless I volunteer for it.

 

[Ry]

In the event that the update is buggy, as this one apparently is, I would read on the forums posts such as mine. Once it seemed all was cleared up, fixed, then install the update. I don't like beta testing unless I volunteer for it.

That's rare though.

There usually isn't an update to address anomalies with a previous update (in the case of most Android OS updates).

 

[Jimmy10mm]

Past few years I recall reading about updates on the Razr, and what not, where the update bricked the device. Doing a google search for nougat update this morning showed many had problems like mine with their Nexus devices following a nougat update a couple of months ago. I should have googled first and updated later, if at all.

 

[dookie.]

I had a similar issue caused by an incompatible 3rd party app. Based on timing of the crash, I was able to guess which app, boot in safe mode, and uninstall. Solid for at least a week now, without the problematic app.

 

[doogald]

Past few years I recall reading about updates on the Razr, and what not, where the update bricked the device. Doing a google search for nougat update this morning showed many had problems like mine with their Nexus devices following a nougat update a couple of months ago. I should have googled first and updated later, if at all.

What happens with one device has no effect on another device. Each device has a specific update, and the reports of bricked devices from this update are rare (frankly, I think that yours is the only one I've seen on this forum.) If there was a widespread issue, there would have been reports all over this forum. I think that you were just unlucky.

 

[beeare]

What happens with one device has no effect on another device. Each device has a specific update, and the reports of bricked devices from this update are rare (frankly, I think that yours is the only one I've seen on this forum.) If there was a widespread issue, there would have been reports all over this forum. I think that you were just unlucky.

I totally agree! This is the first instance I've heard of anyone making this claim. It would be better not to create posts like this without more data to back it up. It gives the readers here a false impression by warning of a widespread issue as if there's reason for all of us to be concerned, especially for those who are still mulling over the possibility of going through with the update. If I were to follow the same logic based on my personal impression of the new software, I'd come to this forum imploring everyone to download it right away based on how smoothly everything is currently operating. But I would never do that because there's always some level of risk involved, and occasionally some people under anomalous circumstances, such as this, end up with bad luck, and I would hate to feel responsible by having that type of influence over anyone experiencing that who made the decision even partially because of me or my advice. But in this case, this will influence people not to download the software and miss out on what many are enjoying and perceive as benefits. If you have an issue, please come here to ask for help and of course feel free to question whether others are experiencing something similar, but don't report problems as if they're widespread unless you have good reason to believe it's not isolated, which does not seem to be the reality at all with this update on this particular phone.

 

[eversonnc]

I installed it as well. I should have known better. It's super buggy. Phone lags big time now. Swift key keyboard crashes often and I've resorted to using the Google keyboard for now. I've rebooted my phone more today than I have in weeks and its running hot. Hindsight is 20/20 I guess. Don't install the update yet!

 

[benjamminh]

It stinks when you install an update and it ruins a previously good phone. It seems like this update for the vast majority of people has been fine, but I'd you're one of the unlucky ones your failure percentage is 100%. Still good to share as it's a valid experience.

 

[ASD Dad]

No bugs for me and I installed the day it came out and have had the phone a while. I use Swiftkey as well as my only keyboard with no issues. I do normally wait for updates as they can be buggy but 7.0 made a huge difference on my 5x so I jumped when it showed up for the Z Force. My 5x was a like a new, nicer phone after 7.0. The Z Force wasnt as drastic but it is still butter smooth and my BT headphones actually connect more reliably.

 

[YAYTech]

I installed it as well. I should have known better. It's super buggy. Phone lags big time now. Swift key keyboard crashes often and I've resorted to using the Google keyboard for now. I've rebooted my phone more today than I have in weeks and its running hot. Hindsight is 20/20 I guess. Don't install the update yet!

Sounds like time for a factory reset.

 

[Ry]

I totally agree! This is the first instance I've heard of anyone making this claim. It would be better not to create posts like this without more data to back it up. It gives the readers here a false impression by warning of a widespread issue as if there's reason for all of us to be concerned, especially for those who are still mulling over the possibility of going through with the update. If I were to follow the same logic based on my personal impression of the new software, I'd come to this forum imploring everyone to download it right away based on how smoothly everything is currently operating. But I would never do that because there's always some level of risk involved, and occasionally some people under anomalous circumstances, such as this, end up with bad luck, and I would hate to feel responsible by having that type of influence over anyone experiencing that who made the decision even partially because of me or my advice. But in this case, this will influence people not to download the software and miss out on what many are enjoying and perceive as benefits. If you have an issue, please come here to ask for help and of course feel free to question whether others are experiencing something similar, but don't report problems as if they're widespread unless you have good reason to believe it's not isolated, which does not seem to be the reality at all with this update on this particular phone.

If an update bricks your phone, I'd expect you to make a thread about it here.

 

[beeare]

If an update bricks your phone, I'd expect you to make a thread about it here.

Agreed, it's the ideal place to come; and having frustrations is totally justified. I certainly would be royally dismayed myself.

I only took issue with the fact that his grievances seemed to imply it was an issue with the software as opposed to a more isolated issue with his particular phone. On a forum with many visitors looking for sound advice and information, I wouldn't want anyone to draw false conclusions and be fearful of future updates based on one experience and generalized speculation. Given how well this update has apparently faired with the vast majority of users, I take issue with cautioning other users in the broader sense by attributing the problem to something more systemic the way that he did, especially considering there doesn't seem to be a lot of evidence to support that. At the same time, I apologize if the tone of my post was harsh and insensitive to someone who clearly is frustrated, had a very negative personal experience and has absolutely every right to write about it, even if it's just for the sake of griping.

 

[Ry]

Agreed, it's the ideal place to come; and having frustrations is totally justified. I certainly would be royally dismayed myself.

I only took issue with the fact that his grievances seemed to imply it was an issue with the software as opposed to a more isolated issue with his particular phone. On a forum with many visitors looking for sound advice and information, I wouldn't want anyone to draw false conclusions and be fearful of future updates based on one experience and generalized speculation. Given how well this update has apparently faired with the vast majority of users, I take issue with cautioning other users in the broader sense by attributing the problem to something more systemic the way that he did, especially considering there doesn't seem to be a lot of evidence to support that. At the same time, I apologize if the tone of my post was harsh and insensitive to someone who clearly is frustrated, had a very negative personal experience and has absolutely every right to write about it, even if it's just for the sake of griping.

Just going by the title, it was clear to me that it was the OP's particular device.