Google Lollipop Bricking Nexus 5 and Nexus 7 Devices

First time accepted submitter Zape (303550) writes The Lollipop update has turned sour for me and several other Nexus 7, Gen 2 (and Nexus 5) owners. It seems that I'm not alone in having my tablet boot to the Google Logo since a couple of days after updating to Android 5.0.2. Now Nexus 5 owners are reporting a reboot loop in Android 5.1. My device, like many others, is a couple of months out of warranty, but worked great until the latest OTA update from Google. They branded it, and they updated it, but Google claims it is between the buyers and ASUS, the manufacturer.

Comments

Re:Google updates

[snowgirl]

But that's the provider's problem, isn't it?

Google can't force providers to use AOSP, and unlocked bootloaders, and all that...

Re:I had the same problem

[xyzzyman]

It is the power switch. Started happening with mine and confirmed it on the Nexus 5 subreddit. Entire thread dedicated to it. There's two different width power switches they've used and it's happening on both. It's in a very tough spot to solder a new one on so around here none of the cell phone repair places would do it for me. Now I just use a program called "gravity" that lets me turn wake it up with a swipe of my finger across the proximity sensor, and a flick of the phone itself to put it to sleep.

Re:Cutting edge journalism

[Pieroxy]

Google figured out that the carriers were a barrier so they went around them.

Google didn't, Apple did. Not one iPhone ever sold has ever been touched by a carrier before getting into the hands of the final user, where the vast majority of Android devices get crapped by carriers before they get sold.

Apple said: Carriers are crap, let's protect all of our phones (and thus users) from them.
Google said: Carriers are crap, we're going to provide users that care with phones that are untouched by them.

As always, Apple forced their views on everyone while Google offered a choice. I think Apple was right on this one.