Database Info

Bricked N5 needs to be fixed! Update: RMA

Update 11/19/13: I contacted Google and as they sent me a new n5, my old one is now on it's way "home".
I'll update again in case they don't accept it bc of my unlocked bootloader and custom recovery.
Thanks for everyone who tried to help!
What I know so far:
- Flashing Google's factory image does not change anything
- I have access to ADB and fastboot
- fastboot oem lock will be reverted after reboot
- fastboot flash recovery recovery.img succeeds, but as I boot to recovery there will always be twrp 2.6.3.0
- twrp keeps asking me for a password
- I can pull and push files, however all changes made seem to revert as I reboot
- I can't flash zip or factory reset through recovery
- I can't mount internal storage, cache, persist (only system)
- My phone will somehow boot to the welcome screen, but give me permanent fc's, I reached the settings once
- The guides on going back to stock etc succeed (in cmd), but actually it feels like no changes are beeing made
I will provide you any information you need, as long as you tell me how to get it.
Hey, when I woke up this morning, my nexus was stuck on a boot loop.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2513701 but it didn't fix my issue. Also, my device would still have TWRP instead of stock recovery (even tried to flash cwm). TWRP can't mount data or cache, can't factory reset and keeps asking me for a password.
When I boot my device (to the welcome, choose language screen) it will only show me all kinds of force closes.
As I set it up, it will tell me my storage is full (at 0mb).
Edit: SuperSU was running after setting up.
I hope that someone has an idea on how to fix my issue..
Click to expand...
Click to collapse

here is my dmesg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If at least I could get rid of TWRP in order to RMA..
fastboot flash recovery recovery.img succeeds, but as I start recovery, it still is twrp

George_Mn said:
If at least I could get rid of TWRP in order to RMA..
fastboot flash recovery recovery.img succeeds, but as I start recovery, it still is twrp
Click to expand...
Click to collapse
Is the recovery.img the stock recovery or it's It twrp?

jd1639 said:
Is the recovery.img the stock recovery or it's It twrp?
Click to expand...
Click to collapse
it is the stock recovery.

I really don't like it when ppl push their own threads, but as mine went to page 3 without any attempt to help me, I feel like pushing.
Something messed up my partitions and i have no clue how to solve it. Could it be twrp? When I try to decrypt data it asks me for a password I dont have!

Try cwm twrp has done that to the nexus 7 a few times since 2.5 or so
Sent from my Nexus 5 using Tapatalk

George_Mn said:
Hey, when I woke up this morning, my nexus was stuck on a boot loop.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2513701 but it didn't fix my issue. Also, my device would still have TWRP instead of stock recovery (even tried to flash cwm). TWRP can't mount data or cache, can't factory reset and keeps asking me for a password.
When I boot my device (to the welcome, choose language screen) it will only show me all kinds of force closes.
As I set it up, it will tell me my storage is full (at 0mb).
Edit: SuperSU was running after setting up.
I hope that someone has an idea on how to fix my issue..
Click to expand...
Click to collapse
I had the same issue.
I fixed it by booting into fastboot, doing a bootloader lock and then a bootloader unlock. All your data gets wiped and the storage gets formated.
But it worked for me and was worth the data loss

Harry GT-S5830 said:
Try cwm twrp has done that to the nexus 7 a few times since 2.5 or so
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can't. When flashing any other then twrp, upon booting recovery it still shows twrp.

maaximal said:
I had the same issue.
I fixed it by booting into fastboot, doing a bootloader lock and then a bootloader unlock. All your data gets wiped and the storage gets formated.
But it worked for me and was worth the data loss
Click to expand...
Click to collapse
I already locked and unlocked once, but I will try again.

George_Mn said:
I already locked and unlocked once, but I will try again.
Click to expand...
Click to collapse
After that use the stock image flash-all.bat/.sh from the google factory tgz (https://developers.google.com/android/nexus/images?hl=us#hammerhead)

bump

Try this. Download the factory image if you haven't done so already: https://developers.google.com/android/nexus/images#hammerhead and extract it down to the images.
Boot into the bootloader and use these commands:
Code:
fastboot format boot
fastboot format cache
fastboot format recovery
fastboot format system
fastboot format userdata
Then run the flash-all.bat
Report back.

El Daddy said:
Try this. Download the factory image if you haven't done so already: https://developers.google.com/android/nexus/images#hammerhead and extract it down to the images.
Boot into the bootloader and use these commands:
Code:
fastboot format boot
fastboot format cache
fastboot format recovery
fastboot format system
fastboot format userdata
Then run the flash-all.bat
Report back.
Click to expand...
Click to collapse
Unfortunately this didn't change anything, also still on twrp. edit: internal storage also still at 0mb.
Code:
E:\Users\George_Mn\Desktop\tools>fastboot format boot
formatting 'boot' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.101s
E:\Users\George_Mn\Desktop\tools>fastboot format cache
erasing 'cache'...
OKAY [ 0.217s]
formatting 'cache' partition...
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
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.883s]
finished. total time: 2.103s
E:\Users\George_Mn\Desktop\tools>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.105s
E:\Users\George_Mn\Desktop\tools>fastboot format system
erasing 'system'...
OKAY [ 0.213s]
formatting 'system' partition...
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
sending 'system' (18800 KB)...
writing 'system'...
OKAY [ 2.400s]
finished. total time: 2.616s
E:\Users\George_Mn\Desktop\tools>fastboot format userdata
erasing 'userdata'...
OKAY [ 0.491s]
formatting 'userdata' partition...
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
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.469s]
finished. total time: 14.964s
Code:
sending 'bootloader' (2506 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.401s]
finished. total time: 0.688s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.096s
sending 'radio' (42033 KB)...
OKAY [ 1.467s]
writing 'radio'...
OKAY [ 2.847s]
finished. total time: 4.317s
rebooting into bootloader...
OKAY [ 0.089s]
finished. total time: 0.090s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: 032ac31c08e6b033
--------------------------------------------
checking product...
OKAY [ 0.101s]
checking version-bootloader...
OKAY [ 0.098s]
checking version-baseband...
OKAY [ 0.098s]
sending 'boot' (8620 KB)...
OKAY [ 0.488s]
writing 'boot'...
OKAY [ 0.726s]
sending 'recovery' (9202 KB)...
OKAY [ 0.541s]
writing 'recovery'...
OKAY [ 0.763s]
erasing 'system'...
OKAY [ 0.254s]
sending 'system' (692940 KB)...
OKAY [ 22.651s]
writing 'system'...
OKAY [ 44.442s]
erasing 'userdata'...
OKAY [ 0.509s]
formatting 'userdata' partition...
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
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.418s]
erasing 'cache'...
OKAY [ 0.241s]
formatting 'cache' partition...
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
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.871s]
rebooting...
finished. total time: 87.765s
Press any key to exit...

Hmmmm. Alright try 'fastboot erase recovery' instead.
Then just flash the recovery.img.
'fastboot flash recovery recovery.img'
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Hmmmm. Alright try 'fastboot erase recovery' instead.
Then just flash the recovery.img.
'fastboot flash recovery recovery.img'
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
actually tried that right after the first attempt. no luck.

I've found some similar cases around xda. Specifically with the N7. When twrp asks for a password can you hit "back" to get to the menu where you are able to factory reset?
Maybe @efrant has an idea. He's pretty good with this stuff.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
I've found some similar cases around xda. Specifically with the N7. When twrp asks for a password can you hit "back" to get to the menu where you are able to factory reset?
Maybe @efrant has an idea. He's pretty good with this stuff.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can hit cancel but factory reset fails.
Code:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
also, on the mount menu, there is an option to decrypt data which asks me for the password.

You didn't happen to flash a recovery or boot image that was for a device other than the N5 did you? I think that would be one cause of what you are seeing.
There is still a way to recover the device by flash the stock TOT file in download mode.
Let me see if I can find the right DLL for the N5, and I'll post in this thread.

George_Mn said:
I can hit cancel but factory reset fails.
Code:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
also, on the mount menu, there is an option to decrypt data which asks me for the password.
Click to expand...
Click to collapse
It's asking you for a password because you didn't boot into android after flashing TWRP. For some reason, you cannot boot directly into TWRP right after any wipe (of userdata) without booting into Android first. It causes issues.

[Q] corrupt cache, can't format ext4

Last Friday I tried to flash android 5 lolipop to my Nexus 5. It froze in the erasing part.
Eventualy switched the phone off and on. There was a loop where you could only see the droid, even in recovery mode.
I got around that loop by flashing TWRP to the recovery partition.
Al recovery ROM's however all state that they can't mount /cache.
I formatted the hell out of it but sadly it didn't solve the problem.
So using adb shell I removed the cache partition, recreated it and formatted it.
So here is my partition table:
Code:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 15.8GB 13.7GB ext4 userdata
29 15.8GB 15.8GB 5632B grow
Notice the missing ext4 for partition 27. After deleting and recreating the partition I formatted it with the following command:
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
this resulted in:
Code:
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
44832 inodes, 179200 blocks
8960 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=184549376
6 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override
So at this point I wanted to check the my partition table again, but this time i got an error message:
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
Mounting results in:
Code:
mount /cache
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed: Invalid argument
Did I make any mistakes here? I did not rooted the phone (yet). Is this necessary?
The re partitioning part comes from a guide here originally for the kindle.
Current status is that I re flashed stock droid 4.4.4. It starts, but all Google applications crash and I have no cellular network .
Guess they all depend on the cache directory.
Any help on making the cache partition work again would be much appreciated!

Oh jeez. I guess by now you know what you've done wrong. In case you don't, you should have just flashed the stock cache.img via fastboot as the very first step.
When you say you flashed stock, how?
What is the output of fastboot flash cache cache.img?
Sent from my Nexus 5 using Tapatalk

My bad! I should have mentioned that I had tried all the basic steps.
So I flashed the original cache.img many times. Because some say it takes more then 1 try to fix a corrupt cache.
Also tried a manual erase and a format of the cache partition.
Flashing the cache is somewhat strange, I have 2 variants. One is done in a heartbeat saying everything went well:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
OKAY [ 0.511s]
sending 'cache' (13348 KB)...
OKAY [ 0.627s]
writing 'cache'...
OKAY [ 1.026s]
finished. total time: 2.169s
And then if I run it again it gets stuck at erasing:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
I once left it overnight but the following morning it was still erasing...
All the time the result is the same. A phone with crashing apps and no cellular network.
To answer your other question. I used fastboot to do a flash-all from the stock image from Google (image-hammerhead-ktu84p (4.4.4)).
Also did the manual version where I manual erase the partitions and flash them.
After this I get a working 4.4.4 with the exception that all Google apps crash (including Play etc, so the basic needs) and I have no cellular network.
Resulting in a useless phone.

The first output looks normal. Try and get it to that stage again so there is a successful flash, then try And fix persist partition as that has similar symptoms. Guide linked in my signature
Sent from my Nexus 5 using Tapatalk

Thank you so much for your reply.
I followed this guide.
The repair did nothing so I entered:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Since my dev/block/platform/msm_sdcc.1/by-name directory was empty is also did that same command for the cache:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
initially that looked like a good thing. The mounting error's where gone after i rebooted the phone.
But things took a turn for the worst. Where before i had a 50% chance on failing to erase the cache. I now have gained a 50% chance to fail at the writing stage.
Resulting in the device not being flash-able because there is more than one part that needs to be flashed.
Also, Philz is not usable. Although flashing states successful, It just won't boot into it. TWRP is the only thing that still works.
Did I do this myself by creating that cache bit? Or is corruption more likely?

Its hard to say. But I think it needs a professional repair now.
Sent from my Nexus 5 using Tapatalk

I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.

Dujinga said:
I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.
Click to expand...
Click to collapse
It cannot break things further. Have you tried dd zero out cache? If there is an I/O problem then that most certainly will break the dd command. You can also try to read back the cache partition with dd command to /data or to / if have enough space on / to confirm there are no I/O errors. If you havent find any I/O errors then I can imagine two things. Something got messed up in the gpt partition or the mmc is fauilty.

I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s

Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s
Click to expand...
Click to collapse
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Sent from my Nexus 5 using Tapatalk

Thank you for your reply. But running this command wil be a problem as it requiers Philz and ADB.
I can still flash Philz in the recovery, but it won't boot into the recovey afterwards
Guys, I want to thank you for all the help, but I'm giving up.
Gonna contact the supplier with the question how to resolve this issue.

Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk

Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.476s
Click to expand...
Click to collapse
rootSU said:
Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Pretty sure "FAILED (remote: flash write failure)" error means that the emmc is hosed.
It's best you claim warranty/insurance.
-Sent from a Lollipop'd Hammerhead!

Ok, so I flashed Philz again (btw TWRP always kept working but that one has a strange shell (limited)).
This time instead of booting straight into recovery after I flashed it, I turned it off and on again.
Now I could get into Philz.
So I ran:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Expecting it to fail, but this was the result:
Code:
dd: writing '/dev/block/mmcblk0p27': No space left on device
1433601+0 records in
1433600+0 records out
734003200 bytes (700.0MB) copied, 41.996465 seconds, 16.7MB/s
That seems OK to me
So I'm going to try a bit more. I already openend a case with the reseller though.
One way or another this will get resolved

I didn't see that error. Yes, hosed.
Sent from my Nexus 5 using Tapatalk

The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh

Dujinga said:
The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh
Click to expand...
Click to collapse
It's a wild goose chase mate. Do you even know what the error stands for? "Flash write failure" means the emmc is toast and hence nothing can be written on it. It's kinda become read only now. Even if the flash is successful, a quick reboot will roll everything back.
It's best you take it up with your seller and claim warranty. There;s nothing you can do.
Good luck!

I got the return instructions. Gonna mail it tommorow.
Once again a huge thanks to all of you guys. :good:

[Q] Can't flash a modem image I grabbed after Rogers/Fido KitKat OTA

Anyone know why I can't flash the modem partition I pulled right after the Fido/Rogers Kit Kat OTA? My steps were
Code:
[email protected]_u:/ # ls /dev/block/platform/msm_sdcc.1/by-name/modem -la
lrwxrwxrwx root root 2014-12-03 11:12 modem -> /dev/block/mmcblk0p1
Then I did this to copy it to a file which I then pulled off my SD card:
Code:
dd if=/dev/block/mmcblk0p1 of=/storage/sdcard1/modem.img
Trying to flash it I get:
Code:
C:\Android\XT925>..\tools\fastboot.exe flash modem modem.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (27889 KB)...
OKAY [ 2.210s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 4.063s
Using mount, I see that we can see it in the /firmware folder. I confirmed the contents in Windows using LinuxReader... Looks like it's a properly extracted partition... File size shows as 104,857,600 bytes...
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,defcontext=u:object_r:modem_file:s0,seclabel,nosuid,nodev,relatime,data=ordered 0 0
So, anyone have a clue why this isn't working?

Are you trying to downgrade the modem or switch to another carrier modem? From what I see, you're trying to flash 4.4.2 modem from Rogers; did you successfully OTA to 4.4.2 from Rogers?
EDIT: Maybe try mfastboot instead of fastboot?

Unable to mount cache while doing factory reset.

Hi everyone,
So I got a nexus 5 from a friend that he said was broken. He told me that he was doing and update and was taking too long so he rebooted his phone. Now the phone is stuck in a boot loop. Everything is stock on the phone and he said he never rooted it. I followed the steps on this thread(method 2 manually flashing each img) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 Here is the output from the CMD window:
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash bootloader bootloader.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.298s]
writing 'bootloader'...
OKAY [ 0.515s]
finished. total time: 0.813s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash radio radio.img
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.622s]
writing 'radio'...
OKAY [ 3.120s]
finished. total time: 4.743s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 1.065s]
sending 'system' (981472 KB)...
OKAY [ 31.005s]
writing 'system'...
OKAY [ 66.272s]
finished. total time: 98.341s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 13.676s]
sending 'userdata' (137318 KB)...
OKAY [ 4.514s]
writing 'userdata'...
OKAY [ 9.179s]
finished. total time: 27.369s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (8852 KB)...
OKAY [ 0.485s]
writing 'boot'...
OKAY [ 0.749s]
finished. total time: 1.233s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9552 KB)...
OKAY [ 0.517s]
writing 'recovery'...
OKAY [ 0.782s]
finished. total time: 1.299s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.452s]
finished. total time: 0.452s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>
Now when I select recovery after I flashed everything the phone turns off and doesn't come back on until I push the power button. Is that normal?(Not sure if this matters as well but sometimes when I push the power button + volume up and down the phone won't turn on. I have to just push the power button and let it boot loop, turn if off with the power button and try getting into fast boot again.) So I pushed the power button and load back into fastboot go into recovery and get the droid with the red exclamation mark. Push power + volume up and get into the options.
At the bottom of the screen it says:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)​
When I try wipe data/factory reset I get:
--Wiping data...
Formatting /data...
E:failed to mount /cache (Invalid argument)
Formatting /cache...
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
So I tried to wipe cache partition command and basically get the same thing as above the only string that is different is:
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/mis(I/O error)
Anyone know where I can go from here?

From what I can see you erased cache partition but didn't flash it back.
You need to flash cache partition also.
Code:
fastboot flash cache cache.img

varuntis1993 said:
From what I can see you erased cache partition but didn't flash it back.
You need to flash cache partition also.
Code:
fastboot flash cache cache.img
Click to expand...
Click to collapse
Yeah. My mistake. Doing that right now but now it's stuck.....
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
Been like this for about 20 minutes.

workonyou said:
Yeah. My mistake. Doing that right now but now it's stuck.....
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
Been like this for about 20 minutes.
Click to expand...
Click to collapse
20min, it should only take seconds to flash it.
I hope you are using usb 2.0 ports.

varuntis1993 said:
20min, it should only take seconds to flash it.
I hope you are using usb 2.0 ports.
Click to expand...
Click to collapse
Yes I am.

workonyou said:
Yes I am.
Click to expand...
Click to collapse
Have you tried disconnecting and connecting again?
I am not sure whether you should do that or not, but you have no other choice right now.

varuntis1993 said:
Have you tried disconnecting and connecting again?
I am not sure whether you should do that or not.
Click to expand...
Click to collapse
I tried something else. I flashed the 4.4.4 stock img using flash-all. Phone booted into android but now camera, google play and gallery are constantly crashing. As well when I try to do a software update it won't download. So I tried to download a random file using chrome and when I did it said "NO SD CARD." What can I do now?

workonyou said:
I tried something else. I flashed the 4.4.4 stock img using flash-all. Phone booted into android but now camera, google play and gallery are constantly crashing. As well when I try to do a software update it won't download. So I tried to download a random file using chrome and when I did it said "NO SD CARD." What can I do now?
Click to expand...
Click to collapse
Try factory reset from stock recovery.
Are you able to lock the bootloader? lock it, reboot and check whether it got locked or not.
Code:
fastboot oem lock

varuntis1993 said:
Try factory reset from stock recovery.
Are you able to lock the bootloader? lock it, reboot and check whether it got locked or not.
Code:
fastboot oem lock
Click to expand...
Click to collapse
When you say factory reset from stock recovery do you mean going into fastboot>recovery>factory/data reset?
I'll try locking the bootloader now.
Not sure if this helps. But when I flashed the 4.4.4 cache IMG it worked fine. Why doesn't the 5.01 work? See output for 4.4.4:
OKAY [ 14.446s]
erasing 'cache'...
OKAY [ 0.525s]
formatting 'cache' partition...
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
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.862s]
****
EDIT
I am able to lock the bootloader

workonyou said:
When you say factory reset from stock recovery do you mean going into fastboot>recovery>factory/data reset?
I'll try locking the bootloader now.
Not sure if this helps. But when I flashed the 4.4.4 cache IMG it worked fine. Why doesn't the 5.01 work? See output for 4.4.4:
OKAY [ 14.446s]
erasing 'cache'...
OKAY [ 0.525s]
formatting 'cache' partition...
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
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.862s]
****
EDIT
I am able to lock the bootloader
Click to expand...
Click to collapse
Since you are able to lock the bootloader, there should not be any issue with nand.
yep I meant that.
how did you install fastboot? you have latest files? Replace them with these
https://www.androidfilehost.com/?fid=95784891001607611

varuntis1993 said:
Since you are able to lock the bootloader, there should not be any issue with nand.
yep I meant that.
how did you install fastboot? you have latest files? Replace them with these
https://www.androidfilehost.com/?fid=95784891001607611
Click to expand...
Click to collapse
Hmmm. I think I was using an older version of fastboot. I was going to try and re-flash everything so I went ahead and unlocked the bootloader and now it's stuck erasing again.

workonyou said:
Hmmm. I think I was using an older version of fastboot. I was going to try and re-flash everything so I went ahead and unlocked the bootloader and now it's stuck erasing again.
Click to expand...
Click to collapse
It takes quite some time to erase when unlocking the bootloader.

varuntis1993 said:
It takes quite some time to erase when unlocking the bootloader.
Click to expand...
Click to collapse
I was still erasing after 1hr+ so I powered off the phone went back into fastboot(unlocked) and flashed 5.01 images using the fastboot you linked. Output:
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot devices
04a9c8e213afcb97 fastboot
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>flash
-all
sending 'bootloader' (2579 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
OKAY [ 0.463s]
finished. total time: 0.765s
rebooting into bootloader...
OKAY [ 0.122s]
finished. total time: 0.123s
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.618s]
writing 'radio'...
OKAY [ 3.124s]
finished. total time: 4.743s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.120s
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........: 04a9c8e213afcb97
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8852 KB)...
OKAY [ 0.489s]
writing 'boot'...
OKAY [ 0.753s]
sending 'recovery' (9552 KB)...
OKAY [ 0.545s]
writing 'recovery'...
OKAY [ 0.797s]
erasing 'system'...
OKAY [ 0.950s]
sending 'system' (981472 KB)...
OKAY [ 30.993s]
writing 'system'...
OKAY [ 66.258s]
erasing 'userdata'...
OKAY [ 11.154s]
erasing 'cache'...
OKAY [ 0.449s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
OKAY [ 1.029s]
rebooting...
finished. total time: 114.872s
Press any key to exit...
Now when the phone restarted I get the android and gear, it stays on for about 2 minutes and reboots and does the same thing again. Boot loop again.

Just do factory reset from stock recovery.

varuntis1993 said:
Just do factory reset from stock recovery.
Click to expand...
Click to collapse
When I go into recovery I get the same thing now. Sigh

workonyou said:
When I go into recovery I get the same thing now. Sigh
Click to expand...
Click to collapse
You mean those same cache errors?

varuntis1993 said:
You mean those same cache errors?
Click to expand...
Click to collapse
No I get the android with the gear just spinning.

workonyou said:
No I get the android with the gear just spinning.
Click to expand...
Click to collapse
Sorry mate, I am out of ideas now. Hope @abaaaabbbb63 or someone else can help you.

varuntis1993 said:
Sorry mate, I am out of ideas now. Hope @abaaaabbbb63 or someone else can help you.
Click to expand...
Click to collapse
Darn. Thanks for trying. Really appreciate it. I did the oem unlock again and it's still hanging.
C:\Users\brad\Desktop\hammerhead-ktu84p-factory-35ea0277\hammerhead-ktu84p>fastb
oot oem unlock
...
Is what I get and the phone says erasing.... Going to leave it for 2hrs+ this time.
If anyone has more ideas please let me know!

workonyou said:
Darn. Thanks for trying. Really appreciate it. I did the oem unlock again and it's still hanging.
C:\Users\brad\Desktop\hammerhead-ktu84p-factory-35ea0277\hammerhead-ktu84p>fastb
oot oem unlock
...
Is what I get and the phone says erasing.... Going to leave it for 2hrs+ this time.
If anyone has more ideas please let me know!
Click to expand...
Click to collapse
Just came to my mind, how about flashing custom recovery, flash twrp, check how much internal storage it shows. If its 0MB.
Then try this
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Also how much time are u waiting for it to boot?

Impossible to install any ROMs on Nexus 5

Hi Everybody
I have a Nexus 5 on which I installed different OSes (LineageOS, /e/, Ubuntu Touch). I had a lot of problems and now I'm trying to install a stock ROM but without success. Besides, I can't install anything on it anymore.
I downloaded 2 stock ROM => https://androidmtk.com/download-google-nexus-stock-rom-models
the 4.4 (KRT16M)
the 6.0.1 (MMB29Q)
Whatever the stock ROM used, here is the return of the script :
Code:
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$ ./flash-all.sh
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
OKAY [ 0.480s]
finished. total time: 0.790s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.830s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.729s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
extracting android-info.txt (0 MB)...
extracting boot.img (8 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (8 MB)...
archive does not contain 'recovery.sig'
extracting system.img (676 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$
Could you help me to fix that phone ?

lool_lauris said:
Hi Everybody
I have a Nexus 5 on which I installed different OSes (LineageOS, /e/, Ubuntu Touch). I had a lot of problems and now I'm trying to install a stock ROM but without success. Besides, I can't install anything on it anymore.
I downloaded 2 stock ROM => https://androidmtk.com/download-google-nexus-stock-rom-models
the 4.4 (KRT16M)
the 6.0.1 (MMB29Q)
Whatever the stock ROM used, here is the return of the script :
Code:
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$ ./flash-all.sh
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
OKAY [ 0.480s]
finished. total time: 0.790s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.830s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.729s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.150s
extracting android-info.txt (0 MB)...
extracting boot.img (8 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (8 MB)...
archive does not contain 'recovery.sig'
extracting system.img (676 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead/stock_rom/hammerhead-krt16m_4-4$
Could you help me to fix that phone ?
Click to expand...
Click to collapse
Get the latest factory image from here... https://developers.google.com/android/images#hammerhead
You can use this guide to flash... https://forum.xda-developers.com/t/...rn-to-stock-unroot-save-your-nexus-5.2513701/

Lughnasadh said:
Get the latest factory image from here... https://developers.google.com/android/images#hammerhead
You can use this guide to flash... https://forum.xda-developers.com/t/...rn-to-stock-unroot-save-your-nexus-5.2513701/
Click to expand...
Click to collapse
Thank you for your reply and to try to help me.
What you mention, I've already done it. This is what is indicated between the code tags in my previous message.
The problem is indicated at the very bottom of the return of the comand line:
Code:
...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
It seems that the organization of the partition is not correct. How to put this back in the studs?

lool_lauris said:
Thank you for your reply and to try to help me.
What you mention, I've already done it. This is what is indicated between the code tags in my previous message.
The problem is indicated at the very bottom of the return of the comand line:
Code:
...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-XjhxWS: Function de bibliothèque ext2 non implémentée lors de l'initialisation du superbloc
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
It seems that the organization of the partition is not correct. How to put this back in the studs?
Click to expand...
Click to collapse
Not sure. Maybe try a factory reset or format data in TWRP?

There is something that prevents the writing of a rom (rom stock or other).
I managed to install a TWRP recovery but not the latest version, only 3.0.0-0.
When I'm under the recovery, I can use adb :
Code:
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ wget http://iwf1.com/iwf-repo/parted.rar
--2021-01-31 19:17:30-- http://iwf1.com/iwf-repo/parted.rar
Résolution de iwf1.com (iwf1.com)… 2001:19f0:5:9cd:ad7b:2365:9457:e3cd, 45.63.15.195
Connexion à iwf1.com (iwf1.com)|2001:19f0:5:9cd:ad7b:2365:9457:e3cd|:80… connecté.
requête HTTP transmise, en attente de la réponse… 301 Moved Permanently
Emplacement : https://iwf1.com/iwf-repo/parted.rar [suivant]
--2021-01-31 19:17:30-- https://iwf1.com/iwf-repo/parted.rar
Connexion à iwf1.com (iwf1.com)|2001:19f0:5:9cd:ad7b:2365:9457:e3cd|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 158898 (155K) [application/x-rar-compressed]
Enregistre : «parted.rar.1»
parted.rar.1 100%[=======================>] 155,17K 727KB/s ds 0,2s
2021-01-31 19:17:31 (727 KB/s) - «parted.rar.1» enregistré [158898/158898]
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ unrar e parted.rar
UNRAR 5.61 beta 1 freeware Copyright (c) 1993-2018 Alexander Roshal
Extracting from parted.rar
Would you like to replace the existing file parted
346680 bytes, modified on 2010-08-19 12:56
with a new one
346680 bytes, modified on 2010-08-19 12:56
[Y]es, [N]o, [A]ll, n[E]ver, [R]ename, [Q]uit n
No files to extract
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ sudo adb push parted /
[sudo] Mot de passe de lool :
parted: 1 file pushed. 3.1 MB/s (346680 bytes in 0.107s)
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$ sudo adb shell
~ # chmod +x parted
~ # ./parted /dev/block/mmcblk0 p
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 2291MB 2098MB ext4 system
26 2291MB 2322MB 31.0MB crypto
27 2322MB 3056MB 734MB ext4 cache
28 3056MB 31.3GB 28.2GB ext4 userdata
29 31.3GB 31.3GB 512B grow
~ # exit
[email protected]:~/Bureau/Bureau_old/eelo_hammerhead$
It seems that the partition 29 (grow) hasn't the good size : 512B instead of 5632B.
But probably this is not the only trouble...

I've been trying to bring a Nexus 5 back to life for quite a few months. Now I manage to reach the bootloader but I can't install any rom, either a stock rom or a custom rom.
I even have difficulties to install a recovery. For example for TRWP images ( https://eu.dl.twrp.me/hammerhead/ ) :
* possible to install an old twrp-2.8.7.1-hammerhead.img image and access it ;
* on the other hand if I install this image twrp-3.0.0-0-hammerhead.img I can access it but the phone shuts down as soon as I try to enter the menus.
* and for images of higher versions, nothing happens.
I think this phone has a partitioning problem. I followed this tutorial to try to go back to a standard partitioning or rather original partitioning but it is impossible to install twrp-3.3.1-HH-hammerhead.img.
So the only way to see what's going on via adb shell is to install this TRWP image twrp-2.8.7.1-hammerhead.img .
I tried to follow this : repartition method but it seems that it does not work out.
Could someone please help me to save this Nexus 5?

Try opening the flash-all.sh and remove the - w flag at the last line.

lool_lauris said:
[...] but it is impossible to install twrp-3.3.1-HH-hammerhead.img.
[...]
Click to expand...
Click to collapse
What do you mean by this exactly? Fastboot throwing errors? Please post the log