Nexus 5 stuck in boot animation?

Search This thread

grefr

Member
Feb 19, 2017
8
0
Hi,

my Nexus 5 was plugged on my laptop.

After a while I saw, that my phone rebooted. I saw the google logo.
I pressed and hold the "Power Button".
My phone booted again and stuck in the booting animation.

This happened three days ago.

I tried so many things. It's not working. :(
Maybe I messed up the partition.

The first thing I tried was to flash the android factory image like this (Flashing instructions - don't forget to press the button "ACKNOWLEDGE"):
https://developers.google.com/android/images

I first thought, that maybe the eMMC is fried.
I checked this like this ( https://forum.xda-developers.com/showthread.php?t=1284196 ):
Code:
adb shell
dmesg | grep mmc0

I didn't get a message like this:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed

I read, that I should change to usb 2.0 port and the usb cable.

I've also a Galaxy nexus. I've tried to flash a new stock with WugFresh. Everything worked with the usb 2.0 port and the usb cable.

When I tried to do that with my nexus 5 nothing works. I get this failure messages:
FAILED (remote: flash write failure)

I used TWRP (twrp-3.0.3-0-hammerhead.img) and clockwork mod (recovery-clockwork-touch-6.0.4.4-hammerhead.img).

The main errors I get:
Can't mount /data
...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovers/log
E: Can't open /cache/recovers/log
...

I really don't know what to do.

Is there a method to build the partition new? Or what else can I do?

Thank you for any help.
 

grefr

Member
Feb 19, 2017
8
0
Do you mean Kit Kat? No, I didn't. I've tried only the new versions like 6.0.1 (MOB31E), 6.0.1 (M4B30Z, Dec 2016).

I will try KK Rom later.
 

grefr

Member
Feb 19, 2017
8
0
I've downloaded this factory image:
"hammerhead" for Nexus 5 (GSM/LTE)
4.4.4 (KTU84P)
from here: https://developers.google.com/android/images

This is the original "flash-all.bat" file:
Code:
@ECHO OFF

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip

echo Press any key to exit...
pause >nul
exit

I've changed the "flash-all.bat" a little bit. I added this line "fastboot oem unlock". When I not add "fastboot oem unlock", I get a message like "not unlocked":
Code:
@ECHO OFF

PATH=%PATH%;"%SYSTEMROOT%\System32"
[B]fastboot oem unlock[/B]
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip

echo Press any key to exit...
pause >nul
exit

I've started the "flash-all.bat". This is the output:
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [  0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
rebooting into bootloader...
OKAY [  0.094s]
finished. total time: 0.094s
< waiting for any device >
...
OKAY [  4.109s]
finished. total time: 4.109s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [  1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.844s
rebooting into bootloader...
OKAY [  0.109s]
finished. total time: 0.109s
< waiting for any device >
...
OKAY [  6.250s]
finished. total time: 6.250s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Creating filesystem with parameters:
    Size: 13725835264
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8144
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 3351034
    Block groups: 103
    Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
wiping cache...
Creating filesystem with parameters:
    Size: 734003200
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 7472
    Inode size: 256
    Journal blocks: 2800
    Label:
    Blocks: 179200
    Block groups: 6
    Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 04ae306b2524b05b
--------------------------------------------
checking product...
OKAY [  0.109s]
checking version-bootloader...
FAILED

Device version-bootloader is 'HHZ20f'.
Update requires 'HHZ11k'.

finished. total time: 0.594s
Press any key to exit...
 

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,914
5,049
Toronto
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
 
  • Like
Reactions: ILA

ILA

Senior Member
Sep 14, 2012
769
301
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.

I have the same problem and after doing that I can see that my eMMC is in fact fried since the bootloader relocks. I was wondering, where is the bootloader/fastboot stored on the device? On the CPU/GPU/RAM stack or on the eMMC. If I swap out the eMMC chip, will I still be able to access it (the bootloader) with a blank eMMC or is it on the eMMC as well? I'm trying to find out what are the steps to format and partition the eMMC after a new one is installed...
 

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,914
5,049
Toronto
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
 
  • Like
Reactions: ILA

ILA

Senior Member
Sep 14, 2012
769
301
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.

Thank you very much for sharing your experience!
I would assume that the bootloader is located on the eMMC since I can't write to the bootloader (or any other) partition from fastboot. I'll have to look into solutions during the weekend since I don't have much time until then, but replacing the MB is a no go for me because of the price.
 

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,914
5,049
Toronto
I'm not sure where you are located but I live in a big city in Canada where I can find deals for people selling Nexus 5 phones with smashed screens and working internal components.

Good luck and please share your results. Thanks.
 

grefr

Member
Feb 19, 2017
8
0
@audit13: When I unlock the bootloader and then reboot the phone into fastboot. The bootloader relocks. :(

Is the memory chip now really damaged? Can't I do nothing? My N5 is three years old. I don't want to pay a lot of money for a main board.
 

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,914
5,049
Toronto
The cheapest solution for a damaged emmc chip may be to buy a used Nexus 5 with a smashed screen and working motherboard. This is what I had to do for 2 phones with self re-locking bootloaders.
 
  • Like
Reactions: grefr

grefr

Member
Feb 19, 2017
8
0
I bought a display damaged nexus 5. It arrived today. Changed the main board. And Voila! It's working.

The other guy has installed this build:
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (MOB30H)

No my question: Which factory image should I install?
https://developers.google.com/android/images
"hammerhead" for Nexus 5 (GSM/LTE)
...
6.0.1 (MOB30H)
6.0.1 (MOB30M)
6.0.1 (MOB30P)
6.0.1 (MOB30Y)
6.0.1 (MOB31E)
6.0.1 (M4B30X, Oct 2016)
6.0.1 (M4B30Z, Dec 2016)

I'm not sure, because the last two has dates. Are they meaning something (I mean, are they special builds), because the other factory images don't have dates.
 
Last edited:

grefr

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

Is OTA better than factory images?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
    1
    I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
    1
    The cheapest solution for a damaged emmc chip may be to buy a used Nexus 5 with a smashed screen and working motherboard. This is what I had to do for 2 phones with self re-locking bootloaders.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone