Did I brick my Nexus?

artician

Member
Dec 28, 2015
11
0
0
I think I bricked my device by trying to boot into recovery!

Working my way through Cyanogenmod installation instructions:
https://wiki.cyanogenmod.org/w/Install_CM_for_grouper

I'd updated to Marshmallow 6.0 prior to this. Device unlocked and in fastboot. Attempted to install new recovery (TWRP) and received this:
"error: cannot load '<recovery image filename>'"

Held volume+power buttons down, waited for the screen to flash. Instead the screen dimmed slightly, then went black. Released the buttons; nothing. Waited. Pressed the power button; nothing. Waited some more.
The device seems dead, but all I did was OEM Unlock, put it into Fastboot, and try to reboot into Recovery. WTF?

Thanks in advance for any help confirming the state of the device.
 
Device lives again! I do not know why!

The battery was not dead. After it's presumed "bricking" I disconnected it and moved it aside to focus on other work. From time to time I'd sadly reach over and press the power button, or press and hold a combination of buttons. Sometimes a long press, sometimes just a click. Probably did it a dozen or more times, and for a full day it didn't make a peep, but just now I literally gasped outloud in surprise when I reached over and clicked the power button and the damn thing sprang to life again.

Obviously this is phenomenal news to me, but what the hell, man?
 

No, flo. I realize the steps I was following were for the 2012 model, but at that stage I was certain it didn't matter. Was I wrong? This is my first android, but I'm an experienced tinker and this absolutely confounds me.
 
No, flo... the steps I was following were for the 2012 model, but at that stage I was certain it didn't matter. Was I wrong?...

In future, pay strict attention to which model you are using. The devices are very similar but have quite significant differences, and you could cause yourself some grief. The 2012 has no rear-facing camera, for example, and the devices use a different key press combination to access the bootloader (although pressing the extra middle key didn't seem to mess you up this time).

Any landing you can walk away from is a good landing, though, as they say. Glad your device is up.

I'd suspect hardware if I were you... loose internal connection? Battery 🔋?
 
I wrote a reply and then it disappeared... It seems my bad luck with the device is rolling over into my desktop experience. ;)

Thank you for your reply and help!