Database Info

[Q] Error flashing 5.0 (LRX21O)

I downloaded the image from google and flashed it manually. I checked the MD5 and it is correct. At the end of flashing it give me a space error (see log below). Does anyone get this too or i did something wrong?
EDIT: follow the link posted by simms22 (http://forum.xda-developers.com/google-nexus-5/general/getting-memory-error-flashing-5-0-t2937800) i am able to get my phone to work. Pretty much we have to flash all the files manually. The link above have a modified script. Just follow instruction there. It took almost 5 mins to finish loading at the boot screen. Give it some time.
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
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 117.363s
Press any key to exit...

Getting the same error. redownloaded, re-unzipped using different programs, always the same result.
sumasage said:
I downloaded the image from google and flashed it manually. I checked the MD5 and it is correct. At the end of flashing it give me a space error (see log below). Does anyone get this too or i did something wrong?
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.21
Serial Number........: 06d18290f0e96e6d
--------------------------------------------
checking product...
OKAY [ 0.099s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.099s]
sending 'boot' (8852 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.761s]
sending 'recovery' (9552 KB)...
OKAY [ 0.582s]
writing 'recovery'...
OKAY [ 0.790s]
erasing 'system'...
OKAY [ 1.335s]
sending 'system' (981596 KB)...
OKAY [ 32.305s]
writing 'system'...
OKAY [ 66.348s]
erasing 'userdata'...
OKAY [ 12.875s]
formatting 'userdata' partition...
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
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 117.363s
Press any key to exit...
Click to expand...
Click to collapse

Flash the img's manually, the script is corrupt

i have the same problem but it rebooted and now its booting

what software did you use? nexus roo tolkit is not working.

vlc_marcos said:
what software did you use? nexus roo tolkit is not working.
Click to expand...
Click to collapse
minimal adb fastboot toolkitt
you should copy the files to flash to the folder and click flashall

Boot.img
I keep doing it with the fastboot on my phone and extracting the file from the zipped file and dropping them in to the platform tools and hitting flash-all batch file
and this in the pic is what I get everytime

Does your phone boot?

sumasage said:
Does your phone boot?
Click to expand...
Click to collapse
yes it boots

Same problem here

yes mine boots as well but it just doesn't get beyond the missing boot.img error

cpvm said:
i have the same problem but it rebooted and now its booting
Click to expand...
Click to collapse
what did you do to fix it?
I copied all the files to the platform-tool (fastboot location) and ran the flash-all.bat script

all you guys are searching for a fix, but it seems as the far majority arent even looking.. http://forum.xda-developers.com/google-nexus-5/general/getting-memory-error-flashing-5-0-t2937800

sumasage said:
what did you do to fix it?
I copied all the files to the platform-tool (fastboot location) and ran the flash-all.bat script
Click to expand...
Click to collapse
then press power button to reboot, then the phone will do a factory reset and it should boot normally.

I read someone suggested to update your SDK. Has anyone done this and still got the error?

Guys, don't use a tool kit. Just download the image, extract it then when booted into the bootloader with your device connected to your pc double click the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app

the script errors out just like the n9 release you need to manually flash the partitions with fastboot to everyone thats having issues.

me too
Buckii said:
I keep doing it with the fastboot on my phone and extracting the file from the zipped file and dropping them in to the platform tools and hitting flash-all batch file
and this in the pic is what I get everytime
Click to expand...
Click to collapse
i had seen the state like that too.

I flashed the images manually through fastboot. After that, I booted into stock recovery and factory reset the phone. Booted up with no problems.

Not able to access Recovery Mode menu

Some time ago the power button of my Nexus5 was stucking once in a while, and kept rebooting.
So I bought a new power button and asked an assistance center to replace it.
This apparently resolved the power button issue, since it does not reboot anymore.
BUT, when i power on my Nexus5 it doesn't goes over the animation of the google logo (the colored one).
It keeps showing the moving dots animation looping forever.
I would like to try to do a soft or hard reset but I can't reach the recovery mode menu.
I can enter the bootloader, then I select the "Recovery mode" and press the power button.
After that it shows the screen with the robot, the exclamation mark and the "No command" message.
From this screen I've tried to press the Volume Up once with Power Button, but it does nothing; it just reboot.
Actually from this screen, even without doing anything, after a few second it automatically reboot without showing the Wipe/Reset menu.
Then i've tried to unlock the bootloader (in order to flash the google stock rom), but I'm not able to get it unlocked permanently:
After running "fastboot oem unlock" on the phone it actually tells the phone is unlocked, but a soon as I let it Power on or Reboot, the phone get back to the locked state.
Indeed, if I unlock the bootloader and, without rebooting it, I try to flash the google nexus 5 factory image (command "sh flash-all.sh"), I get the output I'm copying further down.
Anyone knows how to handle this issue?
------------------------------------------------------------------------------------
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ bash flash-all
bash: flash-all: No such file or directory
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ sh flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.099s]
finished. total time: 0.099s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.608s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.708s
rebooting into bootloader...
OKAY [ 0.055s]
finished. total time: 0.055s
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...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.27
Serial Number........: 039e4cbc2518d798
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
FAILED
Device version-baseband is 'M8974A-2.0.50.2.27'.
Update requires 'M8974A-2.0.50.2.28'.
finished. total time: 0.600s
You have new mail in /var/mail/marcello
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$

Since the bootloader is relocking itself at reboot, the emmc chip is defective and the problem cannot be resolved with software. This will require a motherboard swap.

gufo84 said:
Some time ago the power button of my Nexus5 was stucking once in a while, and kept rebooting.
So I bought a new power button and asked an assistance center to replace it.
This apparently resolved the power button issue, since it does not reboot anymore.
BUT, when i power on my Nexus5 it doesn't goes over the animation of the google logo (the colored one).
It keeps showing the moving dots animation looping forever.
I would like to try to do a soft or hard reset but I can't reach the recovery mode menu.
I can enter the bootloader, then I select the "Recovery mode" and press the power button.
After that it shows the screen with the robot, the exclamation mark and the "No command" message.
From this screen I've tried to press the Volume Up once with Power Button, but it does nothing; it just reboot.
Actually from this screen, even without doing anything, after a few second it automatically reboot without showing the Wipe/Reset menu.
Then i've tried to unlock the bootloader (in order to flash the google stock rom), but I'm not able to get it unlocked permanently:
After running "fastboot oem unlock" on the phone it actually tells the phone is unlocked, but a soon as I let it Power on or Reboot, the phone get back to the locked state.
Indeed, if I unlock the bootloader and, without rebooting it, I try to flash the google nexus 5 factory image (command "sh flash-all.sh"), I get the output I'm copying further down.
Anyone knows how to handle this issue?
------------------------------------------------------------------------------------
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ bash flash-all
bash: flash-all: No such file or directory
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ sh flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.099s]
finished. total time: 0.099s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.608s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.708s
rebooting into bootloader...
OKAY [ 0.055s]
finished. total time: 0.055s
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...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.27
Serial Number........: 039e4cbc2518d798
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
FAILED
Device version-baseband is 'M8974A-2.0.50.2.27'.
Update requires 'M8974A-2.0.50.2.28'.
finished. total time: 0.600s
You have new mail in /var/mail/marcello
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$
Click to expand...
Click to collapse
I have a motherboard for sale, all u nerd to do is swap it out, did the device work at all when u got it back from the shop, maybe they didn't remove the battery and shorted ur emmc chip out, anyway, u can pm me if you wanna talk about the motherboard, its from my old device, works fine, only about 5mths of useage on it
Sent from my XT1526 using Tapatalk

PC?
Have you tried to access the bootloader menu through pc?like cmd?

Hi siddu,
you mean from a pc instead of a mac?
what command would you run?

I am having the same problem and my phone freezes at the animation dots then reboot back to GOOGLE logo. Is it really motherboard problem? Every time I reboot the phone, it will be locked again even though I have OEM unlocked it previously. My recovery mode is the same as you where there's a dead robot with exclamation mark in a triangle. I tried pressing volume up button with power button many times but it doesn't show the menu and after a while it will automatically reboot again. Anyone please help meee!!!

If the bootloader relocks itself after a reboot, the motherboard needs to be replaced.

Stuck on boot animation after resetting to stock

Hi,
A friend asked me to look at his Nexus 5.
It seemed as though his son was trying to flash a custom rom but somewhere along the way things went wrong and it got stuck on the boot animation.
I tried resetting it to factory using this thread.
Followed method 2 and finished it up with "Wipe data/factory data" reset. I did not however relock the boot loader.
I used the factory image 6.0.1 (MMB29S).
Everything went well, no errors, but even after doing all that the phone is still stuck on the boot animation. I tried redoing the "Wipe data/factory data" reset, but the phone is still stuck on boot animation.
I left for around 20 minutes with no change.
All the other threads I have read seem to indicate doing the "wipe data/factory data" reset should correct this issue but it hasn't seemed to help.
I also found this thread. The last post could possibly be another option.
Is there anything I can try? or is there a log I can look?
Any suggestions would be greatly appreciated.
Cheers

Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.

audit13 said:
Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.
Click to expand...
Click to collapse
Thanks for the reply.
I did as you suggested, unfortunately I am still stuck on boot animation.
Output from command
Code:
c:\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.014s]
sending 'userdata' (137318 KB)...
OKAY [ 4.510s]
writing 'userdata'...
OKAY [ 9.149s]
finished. total time: 21.673s
I was just looking at the contents of the zip I downloaded from the developer site. The data stamps on the images seem old. Most date back to 2009. Perhaps I have downloaded the wrong files?

Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?

audit13 said:
Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?
Click to expand...
Click to collapse
Yes the userdata.img did come from the mmb29s ROM. I have no other ROM files downloaded.
Yes I did I believe, if I recall correctly, these were my steps:
Booted phone into fastboot by pressing the power and down volume key
flashed the userdata.img using the command provided
Used the volume rocket to select "Recovery"
When the dead Android appeared I pressed the power button and up volume rocker to display the menu
Proceeded to the option to wipe and reset data
Rebooted the phone
I am pretty sure those were the steps I used.
Should I have rebooted first before going directly into Recovery?

Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?

audit13 said:
Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?
Click to expand...
Click to collapse
No I didn't notice any error messages unfortunately.
And I don't recall seeing any error messages during any of the other steps I have performed.
The commands all seem to successfully execute with no errors.
Does it at all make sense for me to go back and completely redo all the steps from the tutorial in my first post?
I can post the outputs from all the commands if you think that would at all be helpful?

I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.

audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Okay perfect. I will give method 1 a try tonight (I am unfortunately at work right now).
I will report back tonight... hopefully with good news

audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Sorry for the late reply on this.
I got around to doing the steps above.
Unfortunately I am still stuck on the boot animation screen.
Here is the output from the commands I ran
Code:
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.797s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.078s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.540s]
writing 'radio'...
OKAY [ 3.125s]
finished. total time: 4.665s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.063s
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.28
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.781s]
sending 'recovery' (10012 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (1020413 KB)...
OKAY [ 32.163s]
writing 'system'...
OKAY [ 69.508s]
erasing 'userdata'...
OKAY [ 8.326s]
sending 'userdata' (137318 KB)...
OKAY [ 4.500s]
writing 'userdata'...
OKAY [ 9.138s]
erasing 'cache'...
OKAY [ 0.672s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.078s]
rebooting...
finished. total time: 130.775s
Press any key to exit...
////// -------- AFTER COMPLETE POWER OFF AND REBOOT -------- \\\\\\\\
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.625s]
finished. total time: 0.641s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.384s]
finished. total time: 8.399s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.220s]
sending 'userdata' (137318 KB)...
OKAY [ 4.516s]
writing 'userdata'...
OKAY [ 9.156s]
finished. total time: 21.892s
Everything seemed to go okay.
Does everything in the output above look okay?

Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?

audit13 said:
Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?
Click to expand...
Click to collapse
Yes I did do that and did the clear of the cache as well since it posted that error message like you said it would.
So I did both as you explained.
I took a picture of the phone itself after the userdata wipe.
https://www.dropbox.com/s/k05s06avrha1lfv/IMG_20160206_153435.jpg?dl=0

Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.

audit13 said:
Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.
Click to expand...
Click to collapse
Well that sucks!
I had read that in some cases this can be caused by a hardware issue. Any chance it could be that?
Btw, the links I provided to the stock Google images, were they the correct images?

These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?

audit13 said:
These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?
Click to expand...
Click to collapse
hi,
sorry for my late reply. I got sick and just didn't have it in me to try anything new.
I tried flashing 5.0.1 tonight and unfortunately wound up in another boot loop. I will have to try the steps again where you manually reflash userdata. Hopefully I will have time tomorrow!

Hi
My phone has the exact same problem as stated by OP. I even tried flashing kitkat and lollipop but the problem persist. The phone still stuck at boot animation screen. PLS help.

Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?

audit13 said:
Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?
Click to expand...
Click to collapse
The bootloader is now locked. Still, I can't boot the phone completely. stuck at Google boot animation.

At this point, I would conclude that something is wrong with the memory chip.

NEXUS 5 Stuck @ Boot Animation, Possible EMMC Failure?

Hi guys,
I woke up to find my Nexus off, still plugged in, which was strange. When i tried to turn it on, the Google Logo appeared, then the 4 Dots as per Marshmallow Boot animation...only they remained there 35 mins after I attempted to put on the phone.
I figured something was up with the boot, so I left it for a while after restarting, but and it was still stuck.
Since then I've tried reloading Stock Roms, (From KitKat to Marshmallow), installing custom recovery and trying anything I could find online to try to get this to work, but sadly I haven't been able to.
If i try to Reset, I get failed messages on some partitions.
I'll attach some logs showing the messages from some of these attempts.
Can anyone assist or help diagnose?
Attempt at Flashing KitKat with Nexus Root Toolkit
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.285s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.487s
rebooting into bootloader...
OKAY [ 0.129s]
finished. total time: 0.130s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.627s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.854s
rebooting into bootloader...
OKAY [ 0.119s]
finished. total time: 0.120s
target reported max download size of 1073741824 bytes
sending 'boot' (8700 KB)...
OKAY [ 0.494s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.230s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.211s]
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' (9284 KB)...
OKAY [ 0.504s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.687s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.115s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.186s
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.214s
rebooting...
finished. total time: 0.003s
If you require more information, ask and I will provide where I can.

did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk

Terfysgol said:
did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Yup, I tried flashing Stock Roms aka Factory Images for KitKat, Lollipop and Marshmallow as indicated in my original post.

Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?

audit13 said:
Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?
Click to expand...
Click to collapse
I did, and this also produces the Fails as before.

Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.

audit13 said:
Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.
Click to expand...
Click to collapse
I'm beginning to think this may be the case

Have you got an old nandroid that you know that works?
Inviato dal mio P6000 Pro utilizzando Tapatalk

I had similar issue but at least I could boot into bootloader to do this :
http://forum.xda-developers.com/showthread.php?t=2513701
I had the failed also then went to step 2 and did that:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
*tip* Substitute lastest images by dragging and dropping them into cmd window, tip** hit arrow up on keypad to enter in last text to save a bunch of typing
It took FOREVER to boot but it did come back. BUT I have weird fc's and rando0m turn offs so I suspect new phone is coming.
I did phone the google and they connected me with LG for a repair option which will come back in max 9 days but I think even 100 bucks or whatever the cost ( they will phone with tally ) is more than the phone is worth.
Read the whole of the link I sent and Thank abaaaabbbb63 for his work
YMMV HTH
Zo0

Nexus 5 stuck in boot animation?

Hi,
my Nexus 5 was plugged on my laptop.
After a while I saw, that my phone rebooted. I saw the google logo.
I pressed and hold the "Power Button".
My phone booted again and stuck in the booting animation.
This happened three days ago.
I tried so many things. It's not working.
Maybe I messed up the partition.
The first thing I tried was to flash the android factory image like this (Flashing instructions - don't forget to press the button "ACKNOWLEDGE"):
https://developers.google.com/android/images
I first thought, that maybe the eMMC is fried.
I checked this like this ( https://forum.xda-developers.com/showthread.php?t=1284196 ):
Code:
adb shell
dmesg | grep mmc0
I didn't get a message like this:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
I read, that I should change to usb 2.0 port and the usb cable.
I've also a Galaxy nexus. I've tried to flash a new stock with WugFresh. Everything worked with the usb 2.0 port and the usb cable.
When I tried to do that with my nexus 5 nothing works. I get this failure messages:
FAILED (remote: flash write failure)
I used TWRP (twrp-3.0.3-0-hammerhead.img) and clockwork mod (recovery-clockwork-touch-6.0.4.4-hammerhead.img).
The main errors I get:
Can't mount /data
...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovers/log
E: Can't open /cache/recovers/log
...
I really don't know what to do.
Is there a method to build the partition new? Or what else can I do?
Thank you for any help.

Does the bootloader relock when rebooted after being unlocked? Have you tried flashing the stock KK ROM?

Yes. It relocks when rebooted.

Do you mean Kit Kat? No, I didn't. I've tried only the new versions like 6.0.1 (MOB31E), 6.0.1 (M4B30Z, Dec 2016).
I will try KK Rom later.

I've downloaded this factory image:
"hammerhead" for Nexus 5 (GSM/LTE)
4.4.4 (KTU84P)
from here: https://developers.google.com/android/images
This is the original "flash-all.bat" file:
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've changed the "flash-all.bat" a little bit. I added this line "fastboot oem unlock". When I not add "fastboot oem unlock", I get a message like "not unlocked":
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
[B]fastboot oem unlock[/B]
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've started the "flash-all.bat". This is the output:
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
< waiting for any device >
...
OKAY [ 4.109s]
finished. total time: 4.109s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.844s
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
< waiting for any device >
...
OKAY [ 6.250s]
finished. total time: 6.250s
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'
wiping userdata...
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
wiping cache...
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...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 04ae306b2524b05b
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ20f'.
Update requires 'HHZ11k'.
finished. total time: 0.594s
Press any key to exit...

Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.

audit13 said:
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
Click to expand...
Click to collapse
I have the same problem and after doing that I can see that my eMMC is in fact fried since the bootloader relocks. I was wondering, where is the bootloader/fastboot stored on the device? On the CPU/GPU/RAM stack or on the eMMC. If I swap out the eMMC chip, will I still be able to access it (the bootloader) with a blank eMMC or is it on the eMMC as well? I'm trying to find out what are the steps to format and partition the eMMC after a new one is installed...

I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.

audit13 said:
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
Click to expand...
Click to collapse
Thank you very much for sharing your experience!
I would assume that the bootloader is located on the eMMC since I can't write to the bootloader (or any other) partition from fastboot. I'll have to look into solutions during the weekend since I don't have much time until then, but replacing the MB is a no go for me because of the price.

I'm not sure where you are located but I live in a big city in Canada where I can find deals for people selling Nexus 5 phones with smashed screens and working internal components.
Good luck and please share your results. Thanks.

@audit13: When I unlock the bootloader and then reboot the phone into fastboot. The bootloader relocks.
Is the memory chip now really damaged? Can't I do nothing? My N5 is three years old. I don't want to pay a lot of money for a main board.

The cheapest solution for a damaged emmc chip may be to buy a used Nexus 5 with a smashed screen and working motherboard. This is what I had to do for 2 phones with self re-locking bootloaders.

I bought a display damaged nexus 5. It arrived today. Changed the main board. And Voila! It's working.
The other guy has installed this build:
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (MOB30H)
No my question: Which factory image should I install?
https://developers.google.com/android/images
"hammerhead" for Nexus 5 (GSM/LTE)
...
6.0.1 (MOB30H)
6.0.1 (MOB30M)
6.0.1 (MOB30P)
6.0.1 (MOB30Y)
6.0.1 (MOB31E)
6.0.1 (M4B30X, Oct 2016)
6.0.1 (M4B30Z, Dec 2016)
I'm not sure, because the last two has dates. Are they meaning something (I mean, are they special builds), because the other factory images don't have dates.

Or should I do this:
https://developers.google.com/android/ota
OTA binary image files that allow you to manually update your Nexus or Pixel device. This has the same effect of flashing the corresponding factory images, but without the need of wiping the device.
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (M4B30Z)
Is OTA better than factory images?

OK. I've installed this version 6.0.1 (M4B30Z, Dec 2016). Everything works.