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.

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

Barely responsive brick.

Hi.
I just bought used Nexus 5. Everything worked flawlessly until I managed to discharge the battery to 0%. When charging, the phone started looping at the "Google" screen, rebooting every ~2 seconds. (I left it like that for full duration of charging, about 2 hours). It continued rebooting after unplugging charger cable. I think i fixed it by mashing the power button few times.
Now, I'm unable to boot system, mount any of the partitions or load any images in fastboot mode...
Recovery takes few minutes to load but shows 100% battery.
Device info:
* hammerhead D821(E) 32GB
* HW Version: rev_11
* Bootloader version: HHZ20h
* Lock State - Unlocked
* Secure Boot - Enabled
* Device tampered: true
* Device Unlocked: true
* off-mode-charge: true
Issues:
* permanent boot loop when loading system (i even left it overnight to check if it eventually loads - 10h+ no luck)
* TWRP takes few minutes to load and works really slow. no partitions can be mounted. ADB shell works (i don't know any commands).
* Flashing factory image fails. fastboot uploading okay. writing fails (FAILED (remote: flash write failure))
Edit:
* I'm able to load stock recovery via fastboot boot recovery.img (.img from google factory images).
Errors:
Code:
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)
Per this thread, flashing cache.img in fastboot fails:
Code:
fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.210s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.023s
Edit2:
Per this thread, reapairing data gives error:
Code:
adb shell
~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/userdata: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name/userdata
/dev/block/platform/msm_sdcc.1/by-name/userdata: ********** WARNING: Filesystem still has errors **********
Doing the same operation, but directly from TWRP:
Code:
sbin/e2fsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair Data.
In TWRP:
Looks like I can mount /system - it doesn't throw any errors.
Mounting MTP freezes TWRP, but doesn't throw any errors. On PC, device is visible, but no memory.
Mounting /Data freezes TWRP for few seconds and throws error (failed to mount /data (Invalid argument))
Mounting /cache freezes TWRP briefly and throws error (failed to mount /cache (Invalid argument))
Mounting /persist throws error (failed to mount /persist (Invalid argument))
"Select Storage" shows "Internal Storage (0mb)"
Is my memory chip really dead? Could it be due to hidden flaw in my phone? Could it all break by just draining battery to 0%?
Some screenshots attached:

Is my eMMC chip fried?

Have you tried to flash stock via Nexus Root Toolkit? Wug's toolkit should help you out.

Rondeau7 said:
Have you tried to flash stock via Nexus Root Toolkit? Wug's toolkit should help you out.
Click to expand...
Click to collapse
Code:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.122s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.609s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.835s
rebooting into bootloader...
OKAY [ 0.112s]
finished. total time: 0.113s
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.493s]
writing 'boot'...
OKAY [ 0.762s]
finished. total time: 1.258s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.210s]
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' (10014 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.704s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.117s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.158s
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.211s
rebooting...
finished. total time: 0.002s
Failed. I think I know why - these partitions are invisible / not existent / corrupted... picture in description.
Is there some way to try reformat / repartition the eMMC chip?

MarcysVonEylau said:
Code:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.122s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.609s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.835s
rebooting into bootloader...
OKAY [ 0.112s]
finished. total time: 0.113s
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.493s]
writing 'boot'...
OKAY [ 0.762s]
finished. total time: 1.258s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.210s]
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' (10014 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.704s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.117s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.158s
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.211s
rebooting...
finished. total time: 0.002s
Failed. I think I know why - these partitions are invisible / not existent / corrupted... picture in description.
Is there some way to try reformat / repartition the eMMC chip?
Click to expand...
Click to collapse
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301

Saw this before. The thing is I I cannot get the device to show up as "Qualcomm HS-USB QDLoader 9008", or anything COM port-y. In fastboot it shows up like that:
Edit: I read more about it. Looks like a solution, but how to enter that mode?

Follow the directions on the guide from that link.

Okay, then you must help me. I get stuck at step 3:
Select the Com Port you see in Device manager
Click to expand...
Click to collapse
My device doesn't show up as a COM device.

Same error here. Did you get it sort out?
---------- Post added at 03:52 AM ---------- Previous post was at 03:08 AM ----------
MarcysVonEylau said:
Okay, then you must help me. I get stuck at step 3:
My device doesn't show up as a COM device.
Click to expand...
Click to collapse
You have to turn the device off and then press volume up + volume down + Power.
You should be looking at the device manager while pressing the buttons.
When it appears under PORTS let go the buttons.
By the way it did not fix our problem.

It didn't work for me. Nevermind, the phone is in service undergoing memory replacement.

I owe you all an update. Memory replacement didn't work. Most likely the memory controller in the processor itself is fried. Bricked.

what is to be done? you can throw it away?
I also have a nexus 5 who died today,suddenly. I was dowloading an update from google play and just freeze.
On restart, only show the google logo and stay that way. I can enter fastboot mode and tried to reflash with Wug Nexus Toolkit but without succes. It gives me the same errors like in you're post above.
What should I do? :/

Yes, in my case it's absolutely bricked. I don't think a software update would brick it in the same way though. I cannot assist you, but keep trying

Well, I managed to revive him! As i said before it was stuck on Google logo and I could only enter on fastboot mode. Recovery wasn't working. The phone had unlocked bootloader before the brick.
What I did:
1. Open Nexus Root Toolkit v 2.1.9
2. Advanced Utilities > Launch
3. Started the phone on Fastboot mode (volume down + power button) and connect to pc
4. First I tried to boot Custom Recovery temporarily and I saw it was working.
5. Fastboot Erase > checked all!
6. Closed the window
7. Flash Stock + Unroot with current status: Soft-Bricked|Bootloop
8. All finished ok! Single problem: operation wipes all user data and can't be recovered.
Hope this helps someone!

Not being able to install ROM LOS 17. 1, stuck in TWRP

HI All , I need some help . Since I did manage to get a new battery for my broken n5, I decided to get onboarded with LOS17.1 .
Managed to get the 3.4 TWRP HH from @z3DD3r and followed the repartition process. However I am not able to enable adb, nor can I abd sideload , everytime I try to sideload I get an error 7.
Furthermore I cannot mount data partition , nor does the OTG cable work i.e. nothing comes up in my comp. I did install Google drivers / CWM USB drivers, and I do see Google nexus ADB interface popping up in the device manager(win10) however nothing gets listed as a storage/MTP device. I did try searching but not being able to get the solution . I am not able to move beyond this .
N5 doesnt have a sdcard slot either . Can any one advise how to get the LOS zip and gaps into the storage ? Only thing which is working is TWRP HH recovery from @z3DD3r. I will appreciate any help . Let me know if I need to post this in another thread. Thank you

I am not able to mount /cache and /system - it says failed when I wipe or format them .
I only have /data which can be mounted . I have searched and have seen that its to do with partition tables. Any way to get back the partition table done ?
I have checked the following links -
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
and
https://forum.xda-developers.com/go...o-repairing-corrupted-data-partition-t2577447

quest2012 said:
I am not able to mount /cache and /system - it says failed when I wipe or format them .
(...)
Click to expand...
Click to collapse
Wipe -> Advanced Wipe -> Check "Cache" -> Repair or Change File System -> Repair File System
If that doesn't help, do it:
Wipe -> Advanced Wipe -> Check "Cache" -> Repair or Change File System -> Change File System
If your cache partition does not have ext4, set ext4.
If your cache has ext4, change it to FAT and restore it to ext4 when finished.
If something succeeds, repeat the steps for the system partition.
Good luck with the repair. :good:

Did You manage to find the solution?

Thanks , however with TWRP I get error 16 unable to repair system , same thing with cache , neither can I change the filesystem , since I think the partitions dont exist

Enteb27 said:
Did You manage to find the solution?
Click to expand...
Click to collapse
Nope, need a way to repartition as per stock .

I tried looking into various places and used the following site to get into the partition table using parted .
https://iwf1.com/how-to-re-partitio...ll-options-included-change-size-fs-type-etc/2
I followed instructions and found that cache, crypto and system partition were missing . Created the partitions and also managed to change the fs for two of them .
I referred to this page as well to know what partitions are available and what are their usual sizes.
https://forum.xda-developers.com/go...guide-repartition-nexus5-to-increase-t3509880
After all - I did a flash-all , it went through luckily . However somehow I am stuck in bootloop. Then I tried flashing twrp again , and my partitions are gone . Parted doesnt recognize my disk at all .
So close by yet so far
Log of flash all -
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.308s]
writing 'bootloader'...
OKAY [ 0.518s]
finished. total time: 0.830s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 2.036s]
writing 'radio'...
OKAY [ 3.126s]
finished. total time: 5.165s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
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: 29146718208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7115898
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1782368 inodes and 155902/7115898 blocks
Creating filesystem with parameters:
Size: 769654784
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 2936
Label:
Blocks: 187904
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/47040 inodes and 6087/187904 blocks
--------------------------------------------
Bootloader Version...: HHZ20h
Baseband Version.....: M8974A-2.0.50.2.30
Serial Number........: 0c35d79d02
--------------------------------------------
checking product...
OKAY [ 0.099s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.099s]
sending 'boot' (9156 KB)...
OKAY [ 0.509s]
writing 'boot'...
OKAY [ 0.778s]
sending 'recovery' (10014 KB)...
OKAY [ 0.576s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.486s]
sending 'system' (1020657 KB)...
OKAY [ 33.072s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 81.015s
Press any key to exit...

Finally managed to get into and redo parted , changed user fs to ext4. Ran flash all - boot.sig, recovery.sig, vendor img missing , however it ran successfully .
Tried to reboot , it booted up but got stuck at boot , the android 6 factory boot animation came up , but got stuck and switched off . Any workaround ?

Went into parted again - removed userdata partition and redid i.e. made a partition and changed the filesystem to ext4, then came out and flash-all stock , stuck in bootloop , is there any problem with the installation ?
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.522s]
finished. total time: 0.832s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.630s]
writing 'radio'...
OKAY [ 3.129s]
finished. total time: 4.764s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
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: 29146718208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7115898
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1782368 inodes and 155902/7115898 blocks
Creating filesystem with parameters:
Size: 769654784
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 2936
Label:
Blocks: 187904
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/47040 inodes and 6087/187904 blocks
--------------------------------------------
Bootloader Version...: HHZ20h
Baseband Version.....: M8974A-2.0.50.2.30
Serial Number........: 0c35d79d02ba
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.097s]
checking version-baseband...
OKAY [ 0.097s]
sending 'boot' (9156 KB)...
OKAY [ 0.518s]
writing 'boot'...
OKAY [ 0.783s]
sending 'recovery' (10014 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.823s]
erasing 'system'...
OKAY [ 1.433s]
sending 'system' (1020657 KB)...
OKAY [ 33.932s]
writing 'system'...
OKAY [ 68.950s]
erasing 'userdata'...
OKAY [ 13.845s]
sending 'userdata' (139105 KB)...
OKAY [ 4.599s]
writing 'userdata'...
OKAY [ 9.379s]
erasing 'cache'...
OKAY [ 0.668s]
sending 'cache' (13984 KB)...
OKAY [ 0.659s]
writing 'cache'...
OKAY [ 1.111s]
rebooting...
finished. total time: 138.050s
Press any key to exit...

Finally got all partitions working, being able to wipe all partitions through twrp.
All partitions are mounting
Factory image not booting, so trying crdroid 7.1.2
Installs pretty quickly the 350mb file.
However stuck with Google logo, not moving to the boot animation.
Any help will be appreciated.

Need to check power button , since that is also another issues which N5 users have faced and boot loop or getting stuck at boot solution has been replacing the power button/ switch

Closing the thread - Motherboard issue , thanks everyone for your help.