Help Nexus 5 stuck in the start up screen

[jGagliarde]

Here's the sequence of steps to follow to flash the stock images

1. your computer - IIRC, you need to confirm that activity on your phone as well, and wait for that to complete - I don't know if you did that - did you? ---YES
2. Run the following command in the command prompt window : fastboot reboot --- MISSED THIS REBOOT
3. The phone should reboot now. Let it boot up - may take up to 10-15 minutes.

 

[lunatic59]

Until you confirm that you are not unlocked and nothing beyond that point will work. That's why you've been seeing the failures even though fastboot reported it completed. You've never been unlocked.

 

[jGagliarde]

Until you confirm that you are not unlocked and nothing beyond that point will work. That's why you've been seeing the failures even though fastboot reported it completed. You've never been unlocked.

I confirmed the message in the phone and after that it was written UNLOCKED at the bottom, now it's LOCKED again. I'm thinking if I'm going to do it again or give up, I'm really scare of messing something up

 

[jj14x]

I agree with lunatic59 - the failures in the flashboot steps are indicating that the device didn't unlock. (it won't lock by itself till you explicitly run the fastboot command to lock it).

When you issue the OEM UNLOCK command, it will expect you to respond on the device. I see your note that you did it. How long did that take?
And yes, do the fastboot reboot after that, and let it boot up. That won't lock your bootloader.
Now, when you power down, and then power back on, you should see an unlocked 'lock' icon at the bottom of the screen - that confirms that you are unlocked. If you don't see that unlocked icon, your bootloader unlock didn't work.

 

[lunatic59]

On this screen ...

has it EVER said "unlocked" next to lock state?

 

[jj14x]

I confirmed the message in the phone and after that it was written UNLOCKED at the bottom, now it's LOCKED again. I'm thinking if I'm going to do it again or give up, I'm really scare of messing something up

Believe me, I can relate to your concern. It was not that long ago when I started tinkering with my Nexus device. I can't say for certain that it won't mess up, but since this is a Nexus device, and you seem to be familiar with Fastboot, it should be relatively safe.

Despite all the goof ups that I've done, I'm yet to brick any of my devices. But from what I've heard, it certainly is possible (if you flash the wrong images, or use a bad cable, or interrupt a flash etc)

 

[jGagliarde]

On this screen ...

has it EVER said "unlocked" next to lock state?

YES. That's what I'm saying. It was UNLOCKED and then after I tryed the bootloader.img it failed. I did the bootloader reboot and the phone waas back on this screen locked again.
After that I thought about putting the phone into the box, pretend it never happened and go to the store haha

 

[jj14x]

have you tried with fastboot reboot after the oem unlock?

Edit: It should work even without it, so this can't be the problem

 

[jGagliarde]

have you tried with fastboot reboot after the oem unlock?

No. Still scared of trying again. I'm still trying to get up the courage to do this

 

[jj14x]

So, to recap, you did the following

• In fastboot mode (Vol down + POWER), you connected phone to PC
• Ran fastboot devices to verify that fastboot works (got back serial# in command promptt)
• Ran fastboot oem unlock command, and then confirmed the action on the phone, and then, on the phone, used the volume rocker buttons to select the option to wipe, and waited for the unlock to complete.

No errors were reported at any point of these steps, right?

 

[lunatic59]

Here's what I'm thinking now. If, after you issue the fastboot oem unlock command, and you reboot the bootloader and it says "LOCK STATE -unlocked" then you try and flash the new bootloader with

fastboot flash bootloader bootloader-hammerhead-hhz12d.img

(I see earlier you issued the command without the file extension ... try it with ".img") and if it fails.When you reboot the bootloader is then shows locked again?

 

[jGagliarde]

So, to recap, you did the following

• In fastboot mode (Vol down + POWER), you connected phone to PC
• Ran fastboot devices to verify that fastboot works (got back serial# in command promptt)
• Ran fastboot oem unlock command, and then confirmed the action on the phone, and then, on the phone, used the volume rocker buttons to select the option to wipe, and waited for the unlock to complete.

No errors were reported at any point of these steps, right?

Yes

Here's what I'm thinking now. If, after you issue the fastboot oem unlock command, and you reboot the bootloader and it says "LOCK STATE -unlocked" then you try and flash the new bootloader with

fastboot flash bootloader bootloader-hammerhead-hhz12d.img

(I see earlier you issued the command without the file extension ... try it with ".img") and if it fails.When you reboot the bootloader is then shows locked again?

I used .img. Yes, after it failed I rebooted the bootloader and it was locked again.

 

[lunatic59]

Then here is my thought on that. You've got a bad sector of RAM that the old bootloader uses and when you try to overwrite it, it fails and falls back to a locked state. This would be a hardware problem if true and there's no amount of flashing that will fix it. Warranty time.

 

[codesplice]

Then here is my thought on that. You've got a bad sector of RAM that the old bootloader uses and when you try to overwrite it, it fails and falls back to a locked state. This would be a hardware problem if true and there's no amount of flashing that will fix it. Warranty time.

That's what I'm smelling as well. The good news is that it isn't because of anything you did wrong, it's just a sort of luck-of-the-draw hardware issue. I hope they can get you sorted out quickly.

 

[jGagliarde]

I bought this phone in Budapest and I'll be there in the 19h of December now and I can take it to the store. I'll be back there in the 22nd of January, I hope they can fix this until this day because that's my last day in Hungary.

Once more, I would like to thank everyone that helped me here, it means a lot to me. I really appreciate what you guys did.

 

[lunatic59]

If my guess is true, it's not repairable ... they'll have to swap it with a new unit. Hopefully they have them in stock right away.

 

[iowabowtech]

+1. Significant signs pointing to eMMC fail.

 

[diegoalonsopm]

i have the same problem in my nexus 5, someone have skype, to add me anda try to help me please!,

 

[rusty_law]

Hi Guys,
I am facing the same issue (flying dots). I've even flashed up my N5 with hammerhead 5.1.1, but still flying dots coming up.

• Received, Failed to mount /cache(invalid agrument), after flashing the device also.
• My OEM is unlocked.
• USB debugging disabled.

Please help, if it can be resolved.

Thanks

 

[jj14x]

Hi Guys,
I am facing the same issue (flying dots). I've even flashed up my N5 with hammerhead 5.1.1, but still flying dots coming up.

• Received, Failed to mount /cache(invalid agrument), after flashing the device also.
• My OEM is unlocked.
• USB debugging disabled.

Please help, if it can be resolved.

Thanks

Did you flash the cache image? If not, do that, and format the cache as well. See if that helps.

 

[rusty_law]

Did you flash the cache image? If not, do that, and format the cache as well. See if that helps.

I have followed the following steps for flashing N5:

• fastboot flash bootloader bootloader.img
• fastboot reboot-bootloader
• fastboot flash radio radio.img
• fastboot reboot-bootloader
• fastboot flash system system.img
• fastboot flash userdata userdata.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
• fastboot flash cache cache.img

Now, after flashing cache.img I haven't received any error (/cache(Invalid Args)), but my phone is still at flying dots.

When I tried the same step for Kit-Kat (both with/without flashing cache), I was able to get into my phone, but Galllery, Play Store & other application were continuously crashing. When I tried to open Gallery, it throws error, NO SD CARD found. Sim card was not also not readable.

From KIT KAT, I performed OTA update of Lollipop, but after update, stuck again at flying dots.

Any help, what to do from here?

 

[rusty_law]

Issue got Resolved, Thanks for the providing the helping hand friends

 

[jj14x]

Issue got Resolved, Thanks for the providing the helping hand friends

Glad to hear that issue is resolved! (if possible, do share what worked - for other folks who may run into the same issue)

 

[erdmask]

Guys need your help! It's my 4 day of trying to recover my Nexus 5. It's all started with a boot loop. Then I tried the hard reset it didn't help. Unlocked it, rooted, isntalled custom recovery. Tried to install custom ROM had those uneble to mount error (unable to mount /sdcard, /system, /cahche) , downloaded stock image from google, now I'm getting "remote flash write failure." Any ideas?Pleeeeeease

 

[JuanPeeee]

I have the same problems that yuo guys, mine started with rebooting randomly, did a factory reset, no solution, intslaeed gravity (so almost didn´t have to use buttons to block/unblock), 1 week later it´s stuck with the color balls spinning when booting up

Tryed a lot of things, included a new factory reset, butthis time give me some fail stuff, and can´t get it done like the last time (a week ago), I don´t know what to do now....

Tyred the recovery mode, as soon I select it it comes back to de menu... wipe partition, gives me the same failure as the factory wipe