Two Nexus 5 16b stuck in reboot loop! - Nexus 5 Q&A, Help & Troubleshooting

I have two Nexus 5 (one is mine, one is my wife's) that have recently following OTA updates from Google stopped booting.
They get to the Google logo, then to the animation and at this point switch off and reboot ad nauseum.
What can I do to bring them back to life?
Never known a phone so prone to firmware issues as this phone!

If the bootloader is unlocked, you re-can flash a stock ROM. Just be aware of the fact that unlocking the bootloader will factory reset the phone which results in complete data loss.

Its locked currently.
Is there a way of unlocking the bootloader whilst in this state?

MattWildOne said:
Its locked currently.
Is there a way of unlocking the bootloader whilst in this state?
Click to expand...
Click to collapse
Try holding the power and volume down button together, you should see it boot into fastboot mode, you can press the volume down button till u see recovery highlighted, press the power button and boot into it. From there just try to factory reset and see if that works, if it doesn't then I'll help you unlock your bootloader with the best knowledge I can offer if u got a PC.

Try booting into fastboot mode and leave it here for about 5 minutes. If it reboots by itself, it could be a defective/faulty power button.

Flash a factory image and it will be fine. i had same problem already, just google nexus factory images all instructions are there as well as factory images.

Related

It won't Boot and shows a lock on the screen!!

hello frnds,
i am from india (duh) ...my friend bought a galaxy nexus s two days ago..
she had it up an running and it was working as it should.. but yesterday when she woke up..what she saw was that the phone won't boot up and a it shows a lock sign on the boot screen below google and that it was heating up badly... even the pc is not detecting it..i have the phone right now and i promised her that i'll fix it...
what should i do to keep up my promise!
bootloader is locked, phone won't boot
Hello,
The lock simply means that the bootloader of the phone is currently locked (as it is from the factory).
If it won't boot past the Google screen, try removing the battery of the phone for 10 seconds, then trying again.
If this fails, remove the battery again, replace the battery, hold down the UP volume button while pressing power until you see a green android screen. If you can see this screen, then use One Click Root 5.1 in the Development Thread for Nexus S or Nexus S 4G.
hmmm..
thank for the relpy,
well i have tried all that stuff i.e removing the battery for 10 sec..(didn't work)...
wen't to recovery mode(the green android thingi...) and tried recovery option won't work..
do you mean i should flash the firmware again by using one click?
thanks in advance!!:angel:
The lock sign means that the bootloader is UNLOCKED. If you didn't see the lock it would mean that the bootloader is locked (stock). The recovery option won't work because you haven't flash any custom recovery. In fastboot mode (volume up+ power button) it should say: LOCK STATE - UNLOCKED. This means that bootloader is unlocked. Use the toolkit (found in nexus s android development) to flash stock image.
Someone tried to do stuff to the phone and messed up.
thanks
i will try this let you know.:fingers-crossed:
thanks for the help:good:
What causes this though? I have codename jb And cwm 6 on my device and it randomly gets stuck on the boot screen through out the day

Nexus 5 stuck in "four dots animation" [Please help]

So my nexus 5 was running android 6.0.1 July security update, and I flashed 4.4.4 factory image yesterday so that I can maybe root it more easily. However, after I flashed the ROM it got stuck on "four dots animation", so I left it for an overnight booting. It didn't boot up. I also cant access bootloader because when I press the Volume Up+Volume Down+Power button combination it just restarts the "four dots animation". My Nexus 5 now isn't recognized by my windows so i don't know what to do. If anyone has any idea please comment your suggestion.
Tnx in advance.
Lazar
keep holding just Power+Volume Down, should work. If not, let it fully drain the battery, then plug it into wall charger for like 30 min, and unplug it. Only then press and hold Volumedown and power
Hopefully this is just a software issue because I had something similar to this before where it would bootloop at the Google logo and it turned out that I needs to get my power button replaced. Since yours has got past the Google logo tho and on to the animation, I'd imagine its just software and you should be able to fix it.
If you plug it into your PC while its off and it starts charging, you may be able to boot through to fastboot from there using the ADB & Fastboot Utility's on your computer, boot into recovery mode and swap the rom.
Best of luck!
If your phone is stuck at bootloop. Easy fix is to mount system/cache again. See the following guidefor whole procedure.
https://itechify.com/2016/04/01/fix-failed-mount-cache-invalid-argument/
Hard fix is to flash the ROM again.
I had the same issue, first method worked out for me.
Best of luck.
After unlocking the bootloader, does it re-lock when the phone is rebooted into fastboot? When unlocking the bootloader, does it only take a few seconds for the phone to wipe the data paritions? If the answer is yes to either question, the emmc chip is damaged and the motherboard needs to be replaced.
Try flashing the older stock Google ROM image you can find and flash the userdata.img file last. Immediately after flashing userdata, use the physical buttons to boot into recovery and factory reset. If the factory reset can't mount or wipe the partitions, it's probably a hardware issue.

Getting "No Command" on boot

I think I may be in brick mode, but if someone has an answer I would sure appreciate it.
On boot I'm stuck in "No Command". I do the volume down and power and I'm able to get the menus recovery, shut down etc and the only thing that works is to shut down. Recovery just loops me to "no command". Is there a possible solution to get back to goodness. I had my bootloader unlocked and tried to install TWRP recovery but started having issues so in using SkipSoft toolkit I relocked my bootloader and that's where the issue began.
Big thanks in advance if I can possible recover my device.
:crying:
tiger505 said:
I think I may be in brick mode, but if someone has an answer I would sure appreciate it.
On boot I'm stuck in "No Command". I do the volume down and power and I'm able to get the menus recovery, shut down etc and the only thing that works is to shut down. Recovery just loops me to "no command". Is there a possible solution to get back to goodness. I had my bootloader unlocked and tried to install TWRP recovery but started having issues so in using SkipSoft toolkit I relocked my bootloader and that's where the issue began.
Big thanks in advance if I can possible recover my device.
:crying:
Click to expand...
Click to collapse
When you get to the no command screen, press and hold the power button and then push volume up. That should boot it into recovery.
robocuff said:
When you get to the no command screen, press and hold the power button and then push volume up. That should boot it into recovery.
Click to expand...
Click to collapse
Thanks, but I've tried that a few times and it still loops me back to the "no command" screen...
Well I was able to get to the recovery screen, thanks...I tried to do a factory restore and did not work. Called Google and was able to return. Bootloader says locked so I'm hoping there will not be a hiccup when they get the replacement.
I had a similar issue (phone had unlocked bootloader, rooted, phone shut off unexpectedly and wouldnt charge after that. Had the same issue of not being able to get into recovery mode, would just bootloop after selecting recovery) and ended up doing an RMA through google. I have a question in terms of recovering data from a Pixel phone in this state, is it possible? I was unable to recover my data, just curious if it is possible.
llong31 said:
I had a similar issue (phone had unlocked bootloader, rooted, phone shut off unexpectedly and wouldnt charge after that. Had the same issue of not being able to get into recovery mode, would just bootloop after selecting recovery) and ended up doing an RMA through google. I have a question in terms of recovering data from a Pixel phone in this state, is it possible? I was unable to recover my data, just curious if it is possible.
Click to expand...
Click to collapse
I cannot answer that question but I'm glad you were able to get your data. My Pixel was toast so not a chance to get data back!!!
:cyclops:

I broke mit Pixel 3 !?

Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)
MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.
From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.

Pixel Stuck in Bootloop, ADB Unauthorized, Bootloader Unlocked

Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!
mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger

Categories

Resources