Tuesday, August 9, 2016

Nexus 6 physically damaged, fastboot works but adb does not

So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".

Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.

Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?


from xda-developers http://ift.tt/2aKylTg
via IFTTT

No comments:

Post a Comment