Mi vídeo es igual al de uno de los que postean aquí:
http://9to5google.com/2015/04/10/nexus-5-nexus-7-bricked-android-lollipop/
But it appears as if it’s not just the Nexus 7, as several users say their Nexus 5 are experiencing a similar problem. One user says their device is rebooting “again and again”:
Today my Nexus 5 stopped working. When restarting, it started to reboot again and again:
https://docs.google.com/file/d/0B8hjVfgXaRZnS0RXVnZsR1M4Znc/edit?usp=docslist_api
Help!!!
And another user, who translated his post from German, says his Nexus 5 is “dead,” and that “nothing works.”
Hello! (German translation below/Deutsche Übersetzung unten)
My almost a year old Nexus 5, that worked like a charm until just now is dead. No matter which buttons i press, no matter in which order and how long, nothing works. The only sign of life is when i plug it into the wall. The Google logo then comes up, screen blacks out after about 2 secs and the procedure starts new.
I didn’t do anything to it, just got my OTA Update to the newest Android Version (which is 5.1 or 5.0.1, i can’t remember).
I installed an App from the Play Store(a level with ~700kb) which worked, then crashed, then worked again and crashed again but my phone still did it’s job. 10 Minutes later i needed my flashlight, which worked as expected, put the phone back in my pocket and 2 minutes later it was dead.
What can i do? It was almost fully charged. I should still have some warranty left.
I hope i can get it back quickly. Thanks in advance!
Paul
One user says that this happened to his friend’s Nexus 5 as well:
Yikes. This happened to my buddy’s N5 as well- I was there when it happened, and he had just updated the OS a couple days prior. But the N5 went into a rapid bootloop: the Google logo would appear for barely a second, then the screen would shut off for a second, then the logo would reappear for a second, etc. (I never did try to adb his phone to see if it might be recoverable. He just took it to T-Mobile and bought an upgrade instead.) This bootloop behavior is slightly different than the N7-2013 brick, where it simply hangs up on the Google logo. But this N5 bricking does seem similar now to the N7 bricking- both are experiencing motherboard failure a short time after a 5.X update. So it seems there is something in the software update that is affecting the hardware in an incremental fashion such that the problem is not immediate upon updating, but builds up rapidly over time. Both devices have Qualcom chips, though different ones. Someone on another forum suggested that maybe the update is causing a write-loop to the NAND; since flash memory can only sustain a limited number of write cycles, this could eventually cause it to fail. Interesting theory.[/i]
