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
Related
Cannot copy anything into my nexus 5 it gives an error, device stopped responding or has been disconnected. I am in stock 4.4.4, i tried to reflash stock images but it takes a lot of time to flash image especially the system image. Takes more than 20 mins! I previously used adb push while in twrp but could not make the push so i had to (ctrl+c) to break it. What could be the problem?
Tried different cable / USB port / computer?
rootSU said:
Tried different cable / USB port / computer?
Click to expand...
Click to collapse
Checked different ports and USB cables.
The thing is right after I flash or reset via stock recovery I could copy into the phone, after a few tried especially after enabling/disabling usb debugging I get the error. I can open the memory and browse through the phone in the system but i simply cannot copy into it after the first 2-3 times.
gamer.11 said:
Checked different posts and USB cables.
The thing is right after I flash or reset via stock recovery I could copy into the phone, after a few tried especially after enabling/disabling usb debugging I get the error. I can open the memory and browse through the phone in the system but i simply cannot copy into it after the first 2-3 times.
Click to expand...
Click to collapse
Weird - really not sure. A full flashing factory would be my best advice, but if you cant do that...
rootSU said:
Weird - really not sure. A full flashing factory would be my best advice, but if you cant do that...
Click to expand...
Click to collapse
I'm returning back from lollipop to kitkat. I am sure the flashing of stock images do not take so much time. It takes forever for the system.img and userdata.img to flash both using flash-all.bat and doing them individually.
Are the time duration of the flashes proper? This is the 4th time I'm flashing, are the finish times reasonable this time?
Code:
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.499s]
finished. total time: 0.796s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
sending 'radio' (45409 KB)...
OKAY [ 1.950s]
writing 'radio'...
OKAY [ 3.104s]
finished. total time: 5.054s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
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...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.17
Serial Number........: 047d536313afb183
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8700 KB)...
OKAY [ 0.530s]
writing 'boot'...
OKAY [ 0.749s]
sending 'recovery' (9284 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 0.780s]
erasing 'system'...
OKAY [ 0.905s]
sending 'system' (721400 KB)...
OKAY [ 29.437s]
writing 'system'...
OKAY [ 48.984s]
erasing 'userdata'...
OKAY [ 13.759s]
sending 'userdata' (139109 KB)...
OKAY [ 5.819s]
writing 'userdata'...
OKAY [ 9.344s]
erasing 'cache'...
OKAY [ 0.562s]
sending 'cache' (13348 KB)...
OKAY [ 0.764s]
writing 'cache'...
OKAY [ 1.061s]
rebooting...
finished. total time: 114.099s
Press any key to exit...
Edit: Still getting the error. This was easily fixable for devices with external storage but what about our?
gamer.11 said:
Are the time duration of the flashes proper? This is the 4th time I'm flashing, are the finish times reasonable this time?
Code:
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.499s]
finished. total time: 0.796s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
sending 'radio' (45409 KB)...
OKAY [ 1.950s]
writing 'radio'...
OKAY [ 3.104s]
finished. total time: 5.054s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.062s
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...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.17
Serial Number........: 047d536313afb183
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8700 KB)...
OKAY [ 0.530s]
writing 'boot'...
OKAY [ 0.749s]
sending 'recovery' (9284 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 0.780s]
erasing 'system'...
OKAY [ 0.905s]
sending 'system' (721400 KB)...
OKAY [ 29.437s]
writing 'system'...
OKAY [ 48.984s]
erasing 'userdata'...
OKAY [ 13.759s]
sending 'userdata' (139109 KB)...
OKAY [ 5.819s]
writing 'userdata'...
OKAY [ 9.344s]
erasing 'cache'...
OKAY [ 0.562s]
sending 'cache' (13348 KB)...
OKAY [ 0.764s]
writing 'cache'...
OKAY [ 1.061s]
rebooting...
finished. total time: 114.099s
Press any key to exit...
Edit: Still getting the error. This was easily fixable for devices with external storage but what about our?
Click to expand...
Click to collapse
Yes your times are good. Did you reboot the computer? I wonder if it is a driver issue. Maybe uninstall all drivers, reboot and try again?
rootSU said:
Yes your times are good. Did you reboot the computer? I wonder if it is a driver issue. Maybe uninstall all drivers, reboot and try again?
Click to expand...
Click to collapse
Will try that out too.
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
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!
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.
Trying to flash stock, because of the boot loop.
Terminal log shown below
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.508s
rebooting into bootloader...
OKAY [ 0.127s]
finished. total time: 0.128s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.616s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.841s
rebooting into bootloader...
OKAY [ 0.121s]
finished. total time: 0.121s
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........: 0b1323fd02b659ea
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ12k'.
Update requires 'HHZ20h'.
finished. total time: 0.577s
Press any key to exit...
Device has an unlocked bootloader? Tried flashing the oldest stock Google ROM for the phone?