So recently for some reason my Nexus 5 gets stuck on the booting animation. I think it was updating to 6.0.1 or something but I'm not sure, because I just woke up one day and the phone wouldn't boot, and when it finally did it just gets stuck on the boot animation. I've tried to flash stock images and etc but I need an unlocked boot loader and for some reason if the phone doesn't boot completely after unlocking the bootloader, then it gets re-locked. So now my last option is to use the stock recovery to wipe data or something but when I go to the screen with the dead android guy, no combination of buttons seem to make the recovery options show up. If anyone could help that would be great, even if it doesn't involve the stock recovery!
unlock
shylittlezerg said:
So recently for some reason my Nexus 5 gets stuck on the booting animation. I think it was updating to 6.0.1 or something but I'm not sure, because I just woke up one day and the phone wouldn't boot, and when it finally did it just gets stuck on the boot animation. I've tried to flash stock images and etc but I need an unlocked boot loader and for some reason if the phone doesn't boot completely after unlocking the bootloader, then it gets re-locked. So now my last option is to use the stock recovery to wipe data or something but when I go to the screen with the dead android guy, no combination of buttons seem to make the recovery options show up. If anyone could help that would be great, even if it doesn't involve the stock recovery!
Click to expand...
Click to collapse
You only need to go back to the bootloader to unlock and then flash factory images, why do you need recovery?
If the bootloader is relocking itself after a reboot, the emmc has probably gone bad and can only be fixed with a motherboard swap.
audit13 said:
If the bootloader is relocking itself after a reboot, the emmc has probably gone bad and can only be fixed with a motherboard swap.
Click to expand...
Click to collapse
aw that's unfortunate. thanks anyway
I had two Nexus 5 phones that would bootloop and, eventually, the bootloader would keep relocking each time I rebooted.
I bought a couple of used N5s with busted screens, swapped motherboards, and everything went back to normal. A new motherboard is way too expensive.
Related
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
Hey everyone
My Nexus 5 White suddenly reboots and shows up and stuck at Google Logo startup. It drained battery very quick and turned off while i was going back to home. At home I entered to Bootloader (Vol Down + Power) and then Power+Vol Up for additional menu to Clear cache. It worked and appears it cleared cache and rebooted but it stuck at the logo again.
So I decided to follow guides to Flash everything again. But when I try to flash Cache, Bootloader and System error msg shows up "FAILED (remote: flash write failure)" .
Some guides claim memory is dead? Anyone experienced this situation?
PS: Yes I unlocked the bootloader and I tried 6.0 and 5.X
Does the bootloader remain unlocked?
The bootloader in mine would unlock then re-lock at reboot. Also, mine would be stuck at the screen with the spinning balloons. Tried latest 5.1 and 6 too.
Wound up getting a used N5 with smashed screen and swapped motherboards.
audit13 said:
Does the bootloader remain unlocked?
The bootloader in mine would unlock then re-lock at reboot. Also, mine would be stuck at the screen with the spinning balloons. Tried latest 5.1 and 6 too.
Wound up getting a used N5 with smashed screen and swapped motherboards.
Click to expand...
Click to collapse
Yep it remains unlocked. Can't even see the balloons. Now it starts directly to Bootloader. Anyone have this issue fixed?
Nope , it's dead Jim. eMMC is fried.
audit13 said:
Does the bootloader remain unlocked?
The bootloader in mine would unlock then re-lock at reboot. Also, mine would be stuck at the screen with the spinning balloons. Tried latest 5.1 and 6 too.
Wound up getting a used N5 with smashed screen and swapped motherboards.
Click to expand...
Click to collapse
I am having same problem, after I try to reset NExus 5 stuck at 'erasing', I tried to unlock bootloader but as soon the Phone reboots bootloader gets locks again, I tried nexus toolkit to flash stock rom, I tried flashing custom recovery but phone wont boot in custom recovery, Please tell whats wrong, should I give up on this phone??
Thank you
The emmc is damaged and cannot be replaced. A motherboard swap was required to fix mine.
audit13 said:
The emmc is damaged and cannot be replaced. A motherboard swap was required to fix mine.
Click to expand...
Click to collapse
Can confirm, had the same. Emmc fried, could not be repaired, fix: replace mainbord
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Just ran into the same issue with a friend's Nexus 5... Gone for good sadly, time to get a Nexus 5X.
A relatively cheap fix would be to find a used N5 with a smashed screen and working motherboard. I picked up phones between $30 and $50 CAD on Kijiji.
Turuunen said:
Yep it remains unlocked. Can't even see the balloons. Now it starts directly to Bootloader. Anyone have this issue fixed?
Click to expand...
Click to collapse
Same as Turrunen. Maybe this symptom can't be referred to the EMMC bridge...Still seeking for solutions...
Or maybe even though we don't get the point, we still need to swap a main board or buy a new one...
With a unlocked bootloader, failure to flash a stock ROM to the phone, especially, anything above 4.2.2, is also an indicator that something is wrong with the emmc.
Turuunen said:
Hey everyone
My Nexus 5 White suddenly reboots and shows up and stuck at Google Logo startup. It drained battery very quick and turned off while i was going back to home. At home I entered to Bootloader (Vol Down + Power) and then Power+Vol Up for additional menu to Clear cache. It worked and appears it cleared cache and rebooted but it stuck at the logo again.
So I decided to follow guides to Flash everything again. But when I try to flash Cache, Bootloader and System error msg shows up "FAILED (remote: flash write failure)" .
Some guides claim memory is dead? Anyone experienced this situation?
PS: Yes I unlocked the bootloader and I tried 6.0 and 5.X
Click to expand...
Click to collapse
Weired but worked for my sis nexus 5
boot ur phone into bootloader
flash stock 6.0 thru Wug fresh's tool but while flash when it comes in downloading boot or what ever in your phone restart it in middle of flashing ! and then again flash! if this dosent work them Emmc id fried for sure
I've tried Carbon but that one wouldn't actually boot up, just shut my screen off and would shut itself off.
AospExtended ROM, is just sitting at these bouncing dots.
Ressurection Remix, sits at the boot screen of whatever that...logo is supposed to be.
I'm at my witts end here and about to smash this piece of junk. Nothing on this phone has ever worked right since I got it. Figured I'd fix it by getting rid of their trash UI and do custom roms but apparently it can't even do THAT right.
Upgrade your device to EMUI 8. Then flash one of the Treble ROMs.
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Spykez0129 said:
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Click to expand...
Click to collapse
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
SuperSwordSmasher said:
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
Click to expand...
Click to collapse
That's something I do automatically without thinking. That stuff was finicky back in the OG Droid days so I always do it like 3 times just to make sure.
Anything else that would cause it to get stuck at the booting up screen? I get passed the blue screen and the your device is insecure or whatever. Then it just goes into the fancy booting logo and just sits there. Never on any of the phones I've rooted over the past decade ever got stuck like this.
WOHOOO! I MADE PROGRESS!
My phone is now stuck in a never ending bootloop and can't seem to get into any recovery. Can't even shut the phone off because it just turns itself back on. Backwards progress is where it's AT!
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Spykez0129 said:
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Click to expand...
Click to collapse
What honor 8 model do you use? It should not be Bootlooping then, if there is no solution you can always go to stock.
You could flash twrp again, with fastboot
Boot with power + volume up to boot into twrp
Use dload method
So I have a Google Pixel Verizon locked model, that has never been modified, and just recently started boot looping.
It shows the GOOGLE logo on the white background for a few seconds before the screen goes black and tries to boot again.
I am able to get to the recovery mode sometimes (usually when the phone is cold and then can boot into it, otherwise just goes into the same above boot loop.
I have been able to chill the phone by putting it in the fridge, then able to get into the recovery mode.
I have attempted a factory wipe and boot, but when I attempt boot, it just goes back to the boot loop of google screen and black screen
am I bricked? I wanted to try flashing a new rom, but since its locked, and I have no way to get into the phone to activate developer mode, I don't think I can do anything
It sounds like a hardware problem, especially when you mention that chilling the phone helps. Unless someone else has some ideas, your only other option might be to go through Google support.
When in recovery, have u tried booting to bootloader and flash stock firmware with fastboot?
Cheers
Sent from my Google Pixel using XDA Labs
yes, i get an error 21, which i believe is due to the locked bootloader
Since u can't go into fastboot, I think it's best to go to a service center or something.
Good luck.
Cheers
Sent from my Google Pixel using XDA Labs
How would I get my hands on the stock boot logo I kinda wanna remove the unlocked bootloader message
GbnrVR said:
How would I get my hands on the stock boot logo I kinda wanna remove the unlocked bootloader message
Click to expand...
Click to collapse
That message is produced by the bootloader. There's nothing you can do to remove it other than relock the phone.
Well then where can I get a custom logo for it then that's really the question here if either replacing or getting rid of the bootloader message is impossible without relocking the phone then that's the real question I'm asking where can I get a custom logo for the phone
Don't mess bootloader warning message and boot logo (animation) during OS boot.
As mentioned above, the first one you can't change or remove without relocking bootloader.
Changing second is possible.
Yea I wondered this as well. My older Motorola phones (Razr HD MAXX and Turbo) you could reflash a modified boot logo after your were rooted and make it go away. There was still a N/A on the screen but better than seeing what you normally do. I don't think it would be as bad if it did add like an extra 5 seconds to boot.