FORUMS
Remove All Ads from XDA
H10 Turbo

Barely responsive brick.

21 posts
Thanks Meter: 7
 
By MarcysVonEylau, Junior Member on 4th June 2017, 11:40 AM
Post Reply Email Thread
Hi.

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.

Device info:

* 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

Issues:

* 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))

Edit:
* I'm able to load stock recovery via fastboot boot recovery.img (.img from google factory images).
Errors:
Code:
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)
Per this thread, flashing cache.img in fastboot fails:
Code:
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
Edit2:

Per this thread, reapairing data gives error:
Code:
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 **********
Doing the same operation, but directly from TWRP:
Code:
sbin/e2fsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4 
Unable to repair Data.
In TWRP:
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:
Attached Thumbnails
Click image for larger version

Name:	Screenshot_262.png
Views:	136
Size:	22.4 KB
ID:	4171459   Click image for larger version

Name:	Screenshot_263.png
Views:	134
Size:	3.7 KB
ID:	4171460   Click image for larger version

Name:	Screenshot_265.png
Views:	142
Size:	6.1 KB
ID:	4171461  
The Following User Says Thank You to MarcysVonEylau For This Useful Post: [ View ] Gift MarcysVonEylau Ad-Free
 
 
4th June 2017, 12:13 PM |#2  
OP Junior Member
Thanks Meter: 7
 
More
Is my eMMC chip fried?
4th June 2017, 08:44 PM |#3  
Member
Thanks Meter: 6
 
More
Have you tried to flash stock via Nexus Root Toolkit? Wug's toolkit should help you out.
4th June 2017, 09:31 PM |#4  
OP Junior Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by Rondeau7

Have you tried to flash stock via Nexus Root Toolkit? Wug's toolkit should help you out.

Code:
Flash Stock + Unroot [WugFresh Development]
 ------------------------------------------------------------------


target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [  0.306s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [  0.120s]
finished. total time: 0.122s

target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [  1.609s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.835s
rebooting into bootloader...
OKAY [  0.112s]
finished. total time: 0.113s

target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [  0.493s]
writing 'boot'...
OKAY [  0.762s]
finished. total time: 1.258s

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

target reported max download size of 1073741824 bytes
sending 'recovery' (10014 KB)...
OKAY [  0.522s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.704s

target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.117s

Creating filesystem with parameters:
    Size: 29236371456
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 7137786
    Block groups: 218
    Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.158s

Creating filesystem with parameters:
    Size: 734003200
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 7472
    Inode size: 256
    Journal blocks: 2800
    Label:
    Blocks: 179200
    Block groups: 6
    Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.211s

rebooting...

finished. total time: 0.002s
Failed. I think I know why - these partitions are invisible / not existent / corrupted... picture in description.

Is there some way to try reformat / repartition the eMMC chip?
Attached Thumbnails
Click image for larger version

Name:	Screenshot_265.png
Views:	82
Size:	6.1 KB
ID:	4171464  
4th June 2017, 09:47 PM |#5  
Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by MarcysVonEylau

Code:
Flash Stock + Unroot [WugFresh Development]
 ------------------------------------------------------------------


target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [  0.306s]
writing 'bootloader'...

FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [  0.120s]
finished. total time: 0.122s

target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [  1.609s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.835s
rebooting into bootloader...
OKAY [  0.112s]
finished. total time: 0.113s

target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [  0.493s]
writing 'boot'...
OKAY [  0.762s]
finished. total time: 1.258s

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

target reported max download size of 1073741824 bytes
sending 'recovery' (10014 KB)...
OKAY [  0.522s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.704s

target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.117s

Creating filesystem with parameters:
    Size: 29236371456
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 7137786
    Block groups: 218
    Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.158s

Creating filesystem with parameters:
    Size: 734003200
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 7472
    Inode size: 256
    Journal blocks: 2800
    Label:
    Blocks: 179200
    Block groups: 6
    Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.211s

rebooting...

finished. total time: 0.002s
Failed. I think I know why - these partitions are invisible / not existent / corrupted... picture in description.

Is there some way to try reformat / repartition the eMMC chip?

https://forum.xda-developers.com/goo...mm-hs-t3043301
4th June 2017, 10:08 PM |#6  
OP Junior Member
Thanks Meter: 7
 
More
Saw this before. The thing is I I cannot get the device to show up as "Qualcomm HS-USB QDLoader 9008", or anything COM port-y. In fastboot it shows up like that:

Edit: I read more about it. Looks like a solution, but how to enter that mode?
Attached Thumbnails
Click image for larger version

Name:	Screenshot_261.png
Views:	96
Size:	3.4 KB
ID:	4171479  
4th June 2017, 10:44 PM |#7  
Member
Thanks Meter: 6
 
More
Follow the directions on the guide from that link.
4th June 2017, 11:59 PM |#8  
OP Junior Member
Thanks Meter: 7
 
More
Okay, then you must help me. I get stuck at step 3:
Quote:

Select the Com Port you see in Device manager

My device doesn't show up as a COM device.
7th July 2017, 04:52 AM |#9  
Junior Member
Thanks Meter: 0
 
More
Same error here. Did you get it sort out?

---------- Post added at 03:52 AM ---------- Previous post was at 03:08 AM ----------

Quote:
Originally Posted by MarcysVonEylau

Okay, then you must help me. I get stuck at step 3:


My device doesn't show up as a COM device.

You have to turn the device off and then press volume up + volume down + Power.
You should be looking at the device manager while pressing the buttons.
When it appears under PORTS let go the buttons.
By the way it did not fix our problem.
7th July 2017, 01:51 PM |#10  
OP Junior Member
Thanks Meter: 7
 
More
It didn't work for me. Nevermind, the phone is in service undergoing memory replacement.
13th January 2018, 02:07 PM |#11  
OP Junior Member
Thanks Meter: 7
 
More
I owe you all an update. Memory replacement didn't work. Most likely the memory controller in the processor itself is fried. Bricked.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes