Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google Lollipop Bricking Nexus 5 and Nexus 7 Devices

Posted by timothy on from the upgrade-is-not-always-the-right-word dept.

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.

4 of 179 comments (clear)

  1. Not Brick by srwood · · Score: 3, Insightful

    Boot Loop does not equal brick.

  2. Re:Google updates by spacepimp · · Score: 3, Insightful

    If they let people upgrade their own phones this wouldn't happen

  3. Re:Cutting edge journalism by ceoyoyo · · Score: 3, Insightful

    I guess that's why he suggested Google ask Apple how they handle it. The article is specifically talking about Google branded phones (which are only available from Google, not through carriers, no?), not Samsungs running Android or something. If you get an iPhone from AT&T, Vodaphone or Ethiopia Tel, Apple takes responsibility for updates to that phone. They absolutely can "go on to the Verizon/T-mobile/AT&T/Sprint network and update your phone. It's called the Internet. It's a good system that works well.

  4. Re:Cutting edge journalism by silas_moeckel · · Score: 4, Insightful

    Apple limited carrier choice for a very long time, that whole 5 year exclusive to AT&T.

    --
    No sir I dont like it.