I just bought used Nexus 5. Everything worked flawlessly until I managed to discharge the battery to 0%. When charging, the phone started looping at the "Google" screen, rebooting every ~2 seconds. (I left it like that for full duration of charging, about 2 hours). It continued rebooting after unplugging charger cable. I think i fixed it by mashing the power button few times.
Now, I'm unable to boot system, mount any of the partitions or load any images in fastboot mode...
Recovery takes few minutes to load but shows 100% battery.
* hammerhead D821(E) 32GB
* HW Version: rev_11
* Bootloader version: HHZ20h
* Lock State - Unlocked
* Secure Boot - Enabled
* Device tampered: true
* Device Unlocked: true
* off-mode-charge: true
* permanent boot loop when loading system (i even left it overnight to check if it eventually loads - 10h+ no luck)
* TWRP takes few minutes to load and works really slow. no partitions can be mounted. ADB shell works (i don't know any commands).
* Flashing factory image fails. fastboot uploading okay. writing fails (FAILED (remote: flash write failure))
* I'm able to load stock recovery via fastboot boot recovery.img (.img from google factory images).
E:failed to mount /cache (Invalid argument) E:can't mount /cache/recovery/log E:Can't open /cache/recovery/log E:failed to mount /cache (Invalid argument)
fastboot flash cache cache.img target reported max download size of 1073741824 bytes erasing 'cache'... OKAY [ 0.210s] sending 'cache' (13348 KB)... OKAY [ 0.629s] writing 'cache'... FAILED (remote: flash write failure) finished. total time: 1.023s
Per this thread, reapairing data gives error:
adb shell ~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata e2fsck 1.42.9 (28-Dec-2013) /dev/block/platform/msm_sdcc.1/by-name/userdata: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway<y>? y yes e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name/userdata /dev/block/platform/msm_sdcc.1/by-name/userdata: ********** WARNING: Filesystem still has errors **********
sbin/e2fsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4 Unable to repair Data.
Looks like I can mount /system - it doesn't throw any errors.
Mounting MTP freezes TWRP, but doesn't throw any errors. On PC, device is visible, but no memory.
Mounting /Data freezes TWRP for few seconds and throws error (failed to mount /data (Invalid argument))
Mounting /cache freezes TWRP briefly and throws error (failed to mount /cache (Invalid argument))
Mounting /persist throws error (failed to mount /persist (Invalid argument))
"Select Storage" shows "Internal Storage (0mb)"
Is my memory chip really dead? Could it be due to hidden flaw in my phone? Could it all break by just draining battery to 0%?
Some screenshots attached: