Database Info

[Q] Nexus 5 CM just spins, will not boot, adp push to phone, device not recognized

I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked

iconoclasthero said:
I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Click to expand...
Click to collapse
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers

dia_naji said:
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers
Click to expand...
Click to collapse
Unzip the stock image and use fastboot to flash each part individually.

fastboot flash worked.
iPWNtehNOOB said:
Unzip the stock image and use fastboot to flash each part individually.
Click to expand...
Click to collapse
I downloaded hammerhead-krt16m-factory-bd9c39de.tgz (md5sum: 3a7b6cb66f8ec20edf661aee2d73d3a4) from hammerhead-krt16m-factory-bd9c39de.tgz, which I assume is the download site from developers dot google dot com images#hammerheadkrt16m.
When I tried to send the files with fastboot yesterday, it just hung.
I downloaded everything again this morning and got a different md5sum (36aa82ab2d7d05ee144d18546565cd5f) and instead of trying to manually fastboot the files over I executed the script
Code:
sudo ./flash-all.sh
sending 'bootloader' (2506 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
OKAY [ 0.471s]
finished. total time: 0.760s
rebooting into bootloader...
OKAY [ 0.136s]
finished. total time: 0.136s
sending 'radio' (42033 KB)...
OKAY [ 1.508s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.407s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
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........: []
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8620 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.744s]
sending 'recovery' (9202 KB)...
OKAY [ 0.536s]
writing 'recovery'...
OKAY [ 0.778s]
erasing 'system'...
OKAY [ 1.323s]
sending 'system' (692940 KB)...
OKAY [ 21.913s]
writing 'system'...
OKAY [ 47.401s]
erasing 'userdata'...
OKAY [ 19.268s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 14.185s]
erasing 'cache'...
OKAY [ 0.669s]
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.907s]
rebooting...
finished. total time: 110.048s
I guess I had a corrupt download then. Thanks for the help.
Any idea why I could boot into Clockwork but CM just hung? Any additional things to try? Will CM boot without a SIM card?
On the plus side while messing around with trying to get this fixed, I stumbled on a way to get my new nvidia drivers working for the EVGA GTX650 I bought to power my twin 27" displays, so I guess that is also a plus!

same but now works
I just reinstalled recovery again and cm 11.

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?

My phone stopped working all of the sudden

Hello,
Yesterday around midnight my phone suddenly stopped working. I wasn't using it, it was just sitting on my desk and had been for at least half an hour.
When I boot it, it stays stuck on the boot animation.
Until yesterday it was running a custom built version of CM12.1 (from this thread: http://forum.xda-developers.com/goo...unofficial-cm12-cmhammerhead-nexus-5-t2938502)
With a ElementalX-N5-4.09 kernel.
I tried:
Reflashing the ROM
Wiping and Reflashing the ROM
Wiping and Reflashing the ROM, without ElementalX
Wiping and Flashing an older version
Wiping and formating of user data too + Reflashing
complete reset by doing fastboot oem lock/unlock
flashing of the factory image of Android 6
Each time the result is the same.
When the phone was still running cyanogen I had adb while it was booting (that's no longer the case) and I saw nothing striking ... it would have one (pc) screen worth of log (logcat) and then nothing it would just stop.
I couldn't spot anything in kernel logs either (dmesg/last_kmsg).
The recovery is working fine ... I was able to start an ssh server and use it... it's just android that won't boot...
any idea to turn my expensive paperweight back into a phone?

*Update*
I flashed Ubuntu touch and it's working fine.. flashed back Android and it's been showing me the boot animation for 30 minutes now...

After flashing stock ROM, are you erasing userdata and flashing userdata.img?

I've been using the flash-all.sh script so yes.
Here is the output after flashing LMY48M (5.1.1):
Code:
[email protected]:/.../hammerhead-lmy48m$ ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.319s]
writing 'bootloader'...
OKAY [ 0.533s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.134s]
finished. total time: 0.134s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.711s]
writing 'radio'...
OKAY [ 3.111s]
finished. total time: 4.823s
rebooting into bootloader...
OKAY [ 0.137s]
finished. total time: 0.137s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: ****************
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8916 KB)...
OKAY [ 0.510s]
writing 'boot'...
OKAY [ 0.757s]
sending 'recovery' (9632 KB)...
OKAY [ 0.554s]
writing 'recovery'...
OKAY [ 0.807s]
erasing 'system'...
OKAY [ 1.053s]
sending 'system' (1021824 KB)...
OKAY [ 33.345s]
writing 'system'...
OKAY [ 68.316s]
erasing 'userdata'...
OKAY [ 6.439s]
[COLOR="Teal"]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.056s][/COLOR]
erasing 'cache'...
OKAY [ 0.548s]
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.982s]
rebooting...
finished. total time: 129.192s

After using the script, try booting into stock recovery and performing another factory wipe of data and cache.
Or, before the first boot, try erasing and reflash img userdata.img file, boot into recovery, wipe again, and boot.

I tried that and it didn't work ...
However ... I flashed a kitkat factory image (4.4.4 KTU84P to be precise) ... and it works ...
Tomorow I'll try 6.0 again.

Still not much progress.
Kitkat is working but with no service ...
In kernel logs I can see this kind of things:
Code:
<3>[ 24.333162] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 24.333211] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
<3>[ 44.848682] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 44.848937] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
but I have no connectivity issue in ubuntu.
Also I noticed the hardware clock is set to 1970. I though this may be an issue.
I tried to set it to the correct date but it won't work:
Code:
localhost / # hwclock -w
hwclock: RTC_SET_TIME: Invalid argument
I tried this on a galaxy nexus and the hwclock is set at the correct date/time and the hwclock -w command works.

f4kill said:
Still not much progress.
Kitkat is working but with no service ...
In kernel logs I can see this kind of things:
Code:
<3>[ 24.333162] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 24.333211] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
<3>[ 44.848682] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 44.848937] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
but I have no connectivity issue in ubuntu.
Also I noticed the hardware clock is set to 1970. I though this may be an issue.
I tried to set it to the correct date but it won't work:
Code:
localhost / # hwclock -w
hwclock: RTC_SET_TIME: Invalid argument
I tried this on a galaxy nexus and the hwclock is set at the correct date/time and the hwclock -w command works.
Click to expand...
Click to collapse
Seems to me you now own an Ubuntu Phone. :silly:
Are you on the latest bootloader? I have a silly idea but it just might work. Install multiROM on your phone and try to install a custom stock based marshmallow rom, either as a primary or as a secondary. Good luck!

I had a nexus 5 with a broken screen, I salvaged the motherboard and now have a fully functional nexus in my pocket.
I also salvaged the camera because it was doing slightly better shots.
The second phone has a broken screen but still working so it would be nice to have it run android too
However I wanted to turn it into a small server, and had already done so with a chroot trick ... but now I'm thinking Ubuntu touch might be better suited for that
I might try tge multiROM option but I'm not too optimistic about it.
btw the hwclock thing was nothing, the other n5 had its clock in 1970 too and the same error.

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.