Database Info

[Q] Nexus 5 stuck at boot, "google screen", will not flash anything

I am trying to fix my bootlooped nexus 5, but I can't flash any factory images, and factory resetting my phone does nothing. I have tried flashing roms directly from my recovery, but that doesn't work either. NOTHING IS WORKING. PLEASE HELP.
Snippet of log from flash-all batch:
Code:
flash-all
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.208s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.414s
rebooting into bootloader...
OKAY [ 0.088s]
finished. total time: 0.089s
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.573s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.804s
rebooting into bootloader...
OKAY [ 0.079s]
finished. total time: 0.082s
< waiting for device >
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
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
Cannot read image.
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
--------------------------------------------
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 03760f5f43803fbf
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.097s]
checking version-baseband...
OKAY [ 0.097s]
sending 'boot' (8852 KB)...
OKAY [ 0.497s]
writing 'boot'...
OKAY [ 0.742s]
sending 'recovery' (9552 KB)...
OKAY [ 0.553s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s
Press any key to exit...

same situation here if solmeone can help us...

bhlam2 said:
I am trying to fix my bootlooped nexus 5, but I can't flash any factory images, and factory resetting my phone does nothing. I have tried flashing roms directly from my recovery, but that doesn't work either. NOTHING IS WORKING. PLEASE HELP.
Snippet of log from flash-all batch:
Click to expand...
Click to collapse
wil123 said:
same situation here if solmeone can help us...
Click to expand...
Click to collapse
Don't use the flash-all script.
Use the Method 2 from the first post at http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Edit: read the first post completely before you do anything

/cache and /sdcard can't mount

So my phone recently had problems with the power button, and I decided to take it to a phone repair shop and they fixed it. However, now I'm having problems with a bootloop that I can't figure out.
I was running the Android M developer preview. I have tried many times to flash the 5.1.1 factory image, but it fails every time. It comes up with a writing failure for each part of the image (system, bootloader, recovery, etc.). I can go into fastboot and recovery mode, but in recovery I can not do anything, as it cannot mount the /cache and /sdcard... I tried formatting the cache many times, and it just doesn't seem to be helping...
Does anyone have any insight on how to get this to work?
I execute the flash-all.bat and this is what I get
C:\Users\reiga_000\Desktop\hammerhead-lmy48b>fastboot devices
041eda5e251e9726 fastboot
C:\Users\reiga_000\Desktop\hammerhead-lmy48b>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.313s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.531s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.578s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.828s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.031s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
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
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
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 041eda5e251e9726
--------------------------------------------
checking product...
OKAY [ 0.110s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.750s]
sending 'recovery' (9696 KB)...
OKAY [ 0.547s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.625s
Press any key to exit...
Click to expand...
Click to collapse

Problem with eMMC

Hello,
I have got a D820 16GB with CM13.
Yesterday it start to reboot constantly, today I solve it replacing the power buttom... But my problem was beginning. CM doesn't boot, it loop in the CM logo.
I entered in recovery to wipe everything but it fail with two partitions, persist and data.
I assumed the lost of my data, but I want my phone again!!!
I started with this tutorial:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Not luck...
I can't enter in download mode (vol + and conect usb cable), but I entered in other similar mode, vol + vol - and power, the I tryed with this:
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Is finished but nothing change. Obviusly I can't use LG flashtool...
If I try to flash factory image I get this:
Code:
[email protected]:/home/juan/hammerhead-mmb29k# ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.510s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.849s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
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
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: xxxxxxxxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
FAILED
Device version-baseband is 'M8974A-2.0.50.2.26'.
Update requires 'M8974A-2.0.50.2.28'.
finished. total time: 0.691s
The latest test to was write zeros in both partition but don't work.
I guess is the eMMC broken, but I really like my Nexus 5!!!! I would,t buy another phone :crying:
Ideas?
Thanks!

If the memory is damaged, try and buy a cheap Nexus 5 with a smashed screen. I did this for two different phones with bad emmc.

audit13 said:
If the memory is damaged, try and buy a cheap Nexus 5 with a smashed screen. I did this for two different phones with bad emmc.
Click to expand...
Click to collapse
I purchased a new SDIN8DE4-16G, I will replace it!

NVidia K1: flashboot fails on InvalidSize error when flashing 'system'

Hi, Following the recent problems with battery life and the latest version of android for NVidia K1 tablets, a friend of mine tried to restore the stock image. Sadly, we're encountering some issue with fastboot, and I haven't been able to find anything on internet that could explain what is happening.
Following the instructions from (hxxp://nvidiashieldzone.com/index.php/shield-tablet/shield-tablet-k1/shield-tablet-restore-to-stock-recovery) we are stuck when flashing the system.img:
Code:
$ fastboot flash system system.img
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.549s]
sending sparse 'system' (545106 KB)...
OKAY [ 21.143s]
writing 'system'...
OKAY [ 19.928s]
sending sparse 'system' (552714 KB)...
OKAY [ 21.482s]
writing 'system'...
OKAY [ 20.861s]
sending sparse 'system' (118407 KB)...
OKAY [ 4.622s]
writing 'system'...
FAILED (remote: (InvalidSize))
finished. total time: 93.270s
When doing a 'fastboot erase system', we don't have any issue:
Code:
fastboot erase system -w
Creating filesystem with parameters:
Size: 13176406016
Block size: 4096
Blocks per group: 32768
Inodes per group: 8128
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3216896
Block groups: 99
Reserved block group size: 791
Created filesystem with 11/804672 inodes and 91191/3216896 blocks
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
******** Did you mean to fastboot format this partition?
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.252s]
erasing 'userdata'...
OKAY [ 1.720s]
sending 'userdata' (137154 KB)...
OKAY [ 5.025s]
writing 'userdata'...
OKAY [ 4.666s]
erasing 'cache'...
OKAY [ 0.208s]
sending 'cache' (18800 KB)...
OKAY [ 0.696s]
writing 'cache'...
OKAY [ 0.710s]
finished. total time: 13.278s
Note that when doing 'fastboot format system', it seems to be returning something a little different (bigger partition, more nodes?), and I don't know if this is expected:
Code:
$ fastboot format system
Creating filesystem with parameters:
Size: 1342177280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 5120
Label:
Blocks: 327680
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/81920 inodes and 10749/327680 blocks
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.204s]
sending 'system' (22984 KB)...
OKAY [ 0.847s]
writing 'system'...
OKAY [ 0.873s]
finished. total time: 1.924s
I did check that the image had the proper md5, so I'm really stuck at why it doesn't work. The stock image is the same one as on (hxxps://developer.nvidia.com/shield-open-source#tablet-k1)
Interestingly (or worryingly), if I try to erase system too many times in a row, the command will fail with TimeOut, but restarting the tablet fixes it everytime, and I'm able to erase / format / write again, until I get the InvalidSize error.
The tablet is currently stuck on the NVidia logo startup screen (although we can get the bootloader to start everytime).
Do you have any idea what could be happening?
Thanks!
-- tanyiachaos

I'm having this same 'InvalidSize' problem with every recovery image I can lay my hands on, including the original factory full image. The error happens equally using fastboot for Ununtu 16.04 and Windows 10.
Device: Nvidia Shield K1
Has anybody seen this 'InvalidSize' error before? If it didn't work for most people I would say there is a bug in fastboot calculating the last data chunk size. Could this be a hardware problem?

Hi I had the same issue with my shield tablet K1. I finally got my tablet working again by flashing the last TWRP and installing lineage os 14.1.
I can't post the link as i am a newbie but you can google : "How to install LineageOS on the Nvidia Shield Tablet ".
Hope that can help someone.

Nexus 5 D820(H) hang on marshmallow logo try to flash give error plz help

see report
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.500s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.578s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.672s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.063s
< waiting for device >
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
Cannot read image.
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
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 04ac884b0a74a859
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ12k'.
Update requires 'HHZ20f'.
finished. total time: 0.500s
Press any key to exit...
try to update bootloader give error
Code:
C:\Documents and Settings\Miss my love\Desktop\fastboot_MOB30H>fastboot oem unlo
ck
...
OKAY [ 4.859s]
finished. total time: 4.859s
C:\Documents and Settings\Miss my love\Desktop\fastboot_MOB30H>fastboot flash bo
otloader bootloader-hammerhead-hhz20f.img
sending 'bootloader' (3120 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
C:\Documents and Settings\Miss my love\Desktop\fastboot_MOB30H>
try to flash this file
hammerhead-mob30h-factory-66d165e6
or
BIN_LGD820AT-00-V10d-NXS-XX-DEC-11-2013-KOT49H-USER-16G
but not success plz guide me
how to solved

Is the bootloader unlocked? Does it stay unlocked after rebooting into fastboot?

...i have the same issue, now i am looking for a working mainboard.... i think that you have emmc failure, your flash memory is dead and there is no software solution... sorry man...

audit13 said:
Is the bootloader unlocked? Does it stay unlocked after rebooting into fastboot?
Click to expand...
Click to collapse
no after reboot again lock
it's me EMMC chip problem ..?

Umm try flashing Twrp and then a custom rom!
Unlock ur bootloader 1st then flash twrp...

If the bootloader locks itself when the phone is rebooted, the emmc is damaged or defective.