I've had my nexus 5 for awhile now and decided that I should try to root it. So I followed a guide and youtube and it worked. I then followed a guide to install the android M developer preview, just to check out what had changed. From there I decided to install Cyanogenmod 12.1 . So I was looking at this guide when all of a sudden i noticed my root was gone for some reason. (im new to all this, not sure if that was supposed to happen). So then I followed the same rooting steps I used for the first youtube guide I watched. everything seemed to go fine until i realized that i was in a boot loop. I then decided to go ahead and install Cyanogenmod 12.1 anyway. It worked and my phone was fine. Until i woke up this morning and saw that it was in a boot loop again, but now I can't even get into my custom recovery (TWRP). I dowloaded this program to completely return my phone to stock but every time it tries to flash something to my phone, it gets this "flash write failure" message. Now I'm really lost and do not know what to do. I really rather not buy a new phone.
If anyone can help it would be really appreciated!!! If you do, I will need you to assume I do not know anything, as I'm not very familiar with everything.
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
ldubs said:
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I tried to flash it.. After trying to turn my phone back on, it tries to load up with the cyanogenmod logo still there.
Mathieus-MacBook-Pro:hammerhead-lmy48i mathieulaflamme$ ./flash-all.sh
sending 'bootloader' (3119 KB)...
OKAY [ 0.202s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.403s
rebooting into bootloader...
OKAY [ 0.110s]
finished. total time: 0.110s
sending 'radio' (45425 KB)...
OKAY [ 1.535s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.759s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 06ed88372115a3f5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.752s]
sending 'recovery' (9696 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s
Related
Hi,
my NSdoesnt boot and I cant flash another ROM because my NS cant mount SD anymore, so I tryed to restore it back to stock and flash the .imgs with fastboot. Boot.img, recovery.img, userdata.img, without problems, but the system.img gives me the message "write failed" or something. Tryed it multiple times with the Gingerbread system.img, and ICS system.img, same problem.
I can boot into recovery, but the phone doesnt recognize the SD and also the system partition.
Any solutions?
Sorry for my english.
What recovery you using?
Sent from my Nexus S using xda app-developers app
Tried 2 different CMW Recoveries, it's not a recovery problem. My System and SD storage is corrupt or something, I think.
It can't be all that corrupt as you are able to install boot loader and recovery. Try and adb sideload CyanogenMod 10.1. Once you got a booting phone, things tend to play nicely.
Sent from my Nexus S using xda app-developers app
Just tried the adb sideload method.
"Installing update..." for 5 Minutes now. I think it cant write on /system.
I've also tried to erase /system partition via fastboot it gives me also the "failed" message.
system.img write fail error
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
I've had a similar experience when installing stock ROMs after installing cwm and cm 10. Can you guys not even install cm10?
Sent from my Nexus S using xda app-developers app
Deus Tempestas said:
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
Click to expand...
Click to collapse
Same problem here! Did u find solution?
My Nexus 5 recently had some hardware issue and I requested an RMA. The following error comes up when I try to flash the stock recovery system back. Is it okay if I send the Nexus 5 with TWRP installed?
sending 'bootloader' (2508 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.479s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (42049 KB)...
OKAY [ 1.520s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.741s
rebooting into bootloader...
OKAY [ 0.123s]
finished. total time: 0.124s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 07219a4613c86dd0
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8628 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.728s]
sending 'recovery' (9210 KB)...
OKAY [ 0.541s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.641s
I hate to be the bearer of bad news, but it appears the flash memory is bad on your N5. See here. As for whether it's okay to send it with TWRP installed...hmm. I dunno. I don't think an eMMC failure could be caused by installing TWRP so it shouldn't be considered your fault, but they might make you pay for the repair because of it.
Brushstroke said:
I hate to be the bearer of bad news, but it appears the flash memory is bad on your N5. See here. As for whether it's okay to send it with TWRP installed...hmm. I dunno. I don't think an eMMC failure could be caused by installing TWRP so it shouldn't be considered your fault, but they might make you pay for the repair because of it.
Click to expand...
Click to collapse
Okay, I will post back when I get told about paying for the repair. Thanks.
Wellin said:
Okay, I will post back when I get told about paying for the repair. Thanks.
Click to expand...
Click to collapse
How did you fare with Google and this issue?
Hi,
I got a notification today that the 5.0 OTA update is available for my Nexus 5. I tried doing the update and Clockwork Mod complained and the update didn't work. I decided to try doing a manual install. I downloaded the 5.0 stock image, adb executable and fastboot executable. I ran flash-all.sh script included with the stock image. It seemed the ROM installed fine but I was stuck on the boot animation for over an hour. I decided this was too long and tried flashing 4.4.4 with the same problem (downloaded the 4.4.4 stock image and ran it's flash-all.sh script), boot animation kept going.
I tried installing a TeamWin as a recovery because some googling told me that the Dalvik Cache may not have been wiped correctly. I tried wiping Dalvik (and everything else) but they all errored out. I completely formatted everything (had the type "yes" for TeamWin to let me). Once again I tried installing 5.0 and had the same problem.
I did some more googling and some people suggested using ClockworkMod. I flashed ClockworkMod, wiped everything (user data, cache and dalvik) and am now stuck on the boot animation of 4.4.2. I'm running out of ideas and I hope someone else knows what's going on.
Every time that I tried running the flash-all.sh script of any of the stock images I get output very similar to the following:
ERROR: could not get pipe properties
sending 'bootloader' (2508 KB)...
OKAY [ 0.191s]
writing 'bootloader'...
OKAY [ 0.478s]
finished. total time: 0.669s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
sending 'radio' (42049 KB)...
OKAY [ 1.427s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.317s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not get pipe properties
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 0489450843835f19
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8628 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.745s]
sending 'recovery' (9210 KB)...
OKAY [ 0.535s]
writing 'recovery'...
OKAY [ 0.773s]
sending 'system' (702500 KB)...
OKAY [ 22.241s]
writing 'system'...
OKAY [ 48.088s]
erasing 'userdata'...
OKAY [ 14.391s]
erasing 'cache'...
OKAY [ 0.550s]
rebooting...
Also, for what it's worth, when trying to figure out my problem with TeamWin I noticed that a message to the effect of "full SELinux support is present".
Does anyone happen to know what's going on?
EDIT: I'm doing this on OS X 10.9
Did you try turning it on and off again?
Quit using custom recoverys and root, in fact, dont even try to root after you install Lollipop. If you are in Fastboot mode/bootloader and it isnt working then you should verify the integrity of the file and try a better USB cable that is dedicated for file transfer, not the cheap stock one. I flashed mine in 2 mintues no problem 5 mintues to load
EDIT: You also have to update your fastboot drivers and adb, there is a new one
Well...I fixed it. I can't say for sure but I think I may have had a bad fastboot executable. I followed this guide and installing 4.4.2 worked perfectly.
Try extracting the .img files and use fastboot to flash them manually. It installed fine for me without errors.
Hi there,
First, sorry for my english.
I'm not a newbie in rooting, but it's the first time i've got a N5. So, after getting my N5, the phone update to 4.4.4, after to 5.0.1 and after to 5.1.1.
After that, i've flash CWM, but i don't know why but this method give me many error (like the /sdcard cannot be mounted, etc) and i'm in a bootloop. So i've install TWRP, and i've see something weird, it's like all the folder /system, /data, etc cannot be mount because is not there.
So, i'Ve decide to download the factory image 5.1.1 (LMY48B) of the N5, and execute the "flash-all.bat", but it's stock to "writing 'system' ...
sending 'bootloader' (3119 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.719s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
sending 'radio' (45425 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 3.235s]
finished. total time: 4.797s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: (sorry it's personal)
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8980 KB)...
OKAY [ 0.501s]
writing 'boot'...
OKAY [ 0.766s]
sending 'recovery' (9696 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 0.798s]
sending 'system' (1021744 KB)...
OKAY [ 32.562s]
writing 'system'...
Click to expand...
Click to collapse
What's the problem????
Try flashing the individual files separately
Sent from my Nexus 5 using Tapatalk
This phone is totally stock other than unlocked bootloader.
I was in the middle of using the web browser when out of the blue it rebooted and now no longer gets past the initial "Google" screen, it doesn't even get to the animated screen.
I tried flashing the latest software hammerhead-mob30h from within fastboot, everything worked fine and flash seems to have been successful ..still it will not go past "Google" screen.
I already tried wiping cache, it was the first thing I tried.
Any suggestions?
PS F:\android\nexus 5\hammerhead-mob30h> ./flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.272s]
writing 'bootloader'...
OKAY [ 0.524s]
finished. total time: 0.798s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.101s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.544s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.667s
rebooting into bootloader...
OKAY [ 0.103s]
finished. total time: 0.104s
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'
--------------------------------------------
Bootloader Version...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 03518dc5213ea9a2
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9146 KB)...
OKAY [ 0.509s]
writing 'boot'...
OKAY [ 0.777s]
sending 'recovery' (10004 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 0.824s]
erasing 'system'...
OKAY [ 1.486s]
sending 'system' (1020577 KB)...
OKAY [ 32.513s]
writing 'system'...
OKAY [ 69.708s]
rebooting...
finished. total time: 107.206s
Press any key to exit...
PS F:\android\nexus 5\hammerhead-mob30h>
Verify the checksum of the factory image - just to be sure that the downloaded file isn't corrupted. For MOB30H the official checksum is
Code:
MD5: e44f4b7b25f918c8ab011ddf8d08b5a5
SHA-1: 66d165e6643366a89287414f11c247ef626ed930
However, if the checksum is fine I assume it's a hardware-related issue.
Yeah they match, damn I really wanted to wait for the next Nexus.
Damn.. maybe someone else can hop in! I'm sorry...
If memory was messed up wouldn't the flash fail?
Did you flash the userdata.ing file too?
audit13 said:
Did you flash the userdata.ing file too?
Click to expand...
Click to collapse
Was holding off on that in hopes of recovering the data.
But, could userdata affect the initial boot up? I would think the other partitions would be the ones that are used so early in boot process.
Yes, I have found that, in some cases, flashing userdata.img and immediately performing a factory wipe will allow the phone to boot.
Made some progress...
Used NRT to launch a custom recovery, do a backup of data and wipe the phone. It now has gone past "Google" screen for the first time and is on animation ....hopefully I'm back in business.
YES!
It booted back up clean, I then used NRT again to get back into custom recovery and did user data restore, booted back up and everything is as if nothing had happened
Thought she was a gonner for sure.