Phone in bootloop all in a suddent, unable to access Bootloader/Fastboot - Nexus 5 Q&A, Help & Troubleshooting

Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.

Blitztorm said:
Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.
Click to expand...
Click to collapse
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.

pigstew said:
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.
Click to expand...
Click to collapse
Good Lord!! It actually did work, but how to explain the ART and Dalvik thingy?!
thanks

Related

Stock and unrooted but acting weird

I was using an app on Sunday, when the app froze completely and the screen of the s3 went black. The only thing I could see was the status bar up top, but even that was unresponsive. So I pulled the battery and turned it back on, and it was acting extremely slow so I got impatient and started trying to get into settings, when it went unresponsive again.
This time I held down the power button to see if I could get it to respond and the lock screen came up, without my wallpaper and instead of Verizon Wireless at the top, it said "No Service". After a couple of seconds my wallpaper showed up and then it said Verizon Wireless. After I get through the lock screen, I would go through the same whole routine - e.g. try and get into settings, freeze, hold power, have it come back up, etc. So I battery pulled again.
Finally, I got it to boot OK, by just letting it be for 10 minutes and completely ignoring it.
However, today my battery drain was pretty fast, it was on for 12 hours and was down to 40% after only 30 minutes of screen time. The culprit was "Android System" at 61%, i've never seen this that high before. Because of the high "Android System" power usage, I thought it might be good to power it down. Upon boot up, I assumed I'd be able to use it immediately, so I started going into Settings, and yet again it went unresponsive.
Are the two issues unrelated? What should I do?
As a warning, I'm extremely new to anything smarter than a Nokia brick, so be patient - Thanks!
As inconvenient as it is, I would recommend a full system wipe and go back to out of the box. That seems to fix everything and unfortunately it is rather difficult to diagnose issues on phones, especially unrooted.
In order to do a wipe you can do one of two things, goto settings then backup and reset, then hit factory data reset.
-OR-
Turn off the phone. When you start it again hold volume-up, power, and home to get into recovery. Then do the factory reset.
Ok, I thought that's what my option was. Thanks dwibbles.

Dead N5?

Is this N5 hosed?
Android 5.1.1
( I know the following because I have a second N5 that was purchased at the same time that Is still running flawlessly and they both would update within a day or so of each other, assuming this info is the same)
Baseband Version
M8974A-2.0.50.2.26
Kernel Version
3.4.0-gbebb36b
[email protected]#1
Tue Mar 10 18:17:45 UTC 2015
Build Number
LMY48B
I have a completely stock N5 that started presenting problems some months ago with random reboots, just occasionally. It would just restart no big deal, didn’t worry to much about it pretty soon the restarts came more often.
I installed the “Device Assist” App as suggested in a google forum group, to which it immediately started to recognize “Device Randomly rebooting? Try Safe Mode” ( which I didn’t at that time) it did give me the option to call a google tech and speak with them about the issue, they saw, through device assist that indeed the device had been randomly restarting. The tech ran me through clearing the device cache from the recover menu, I rebooted and everything worked fine for several weeks.
Then the reboots started again, but this time more seriously, often the unit would just power down and attempt to reboot would be meet with a short vibrate with a flash of the word google.
Eventually it would boot back up, often it would run through an “optimizing apps” routine.
I remembered as well, often the reboot(s) would begin with the “power off” screen coming up, even if I didn’t choose it it would shut down anyway and often if I dismissed it, it would wait 10 seconds or so then shut down.
All really strange.
So I got a hold of a google tech again, this time they suggested rebooting in safe mode and running several days like that to see if it was a software or hardware issue.
In safe mode it ran without issue for 48 hours( normally this would have resulted in a handful of restarts at best. Google tech seemed to think it was an app issue since the problem didn’t return in safe mode and suggested a complete factory restore,( and to setup the phone as a new phone rather than restore any back info form google) I was backed up so I ran the factory restore from system settings “back up and restore” .
Once restored it worked fine for a day and then it all went downhill from there, power off screen would appear (often when I short pressed the power button to sleep the unit) and again if I dismissed that dialogue it would power down anyway and it would take numerous tries to get it to power back up, almost every time it would run through the “optimizing apps” routine.
Within a day, it just stopped powering up. If I plug the unit in to charge it does this odd cycle of black-screen/short vibrate/Flash the word Google, about every 2 seconds, it never shows a battery charge indicator
If it is not plugged it won’t do anything, if it is plugged in when I tried to boot into recovery, the recovery screen would appear for a brief second and then it will start the vibrate/flash “google “ cycle.
It does nothing when placed on a wireless charging plate.
Google tech said it is out of warranty ( which I knew) and gave me a number to LG to see what options they suggested.
I suspect it has something to do with a sticky or malfunctioning power button, but wanted to see if anyone here has and experience with this type of issue or has a suggestion.
Thanks

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

Is this the end of the line for my N5?

I'm a serial lurker here and hate to ask for help, but want to reach out (and finally start hitting thanks).
My N5 was on MMB29S 6.0.1, SuperSU version 2.65 for root, xposed v79 (gravitybox, APM+, snapprefs), and ran perfectly fine up until a few weeks ago when I started having issues. Apps would sometimes FC, and (not always right after) system would hang and then reset. Sometimes the screen would go black but notification light still would blink.
Upon reset, it would either (a) get stuck at google screen and bootloop or (b) get stuck at some point during the boot animation. If the phone did start, it would usually work for a variable amount of time - minutes, hours, but usually not more than a day. Other times, the phone simply would not start and required a slowly increasing amount of time to boot while holding down the power button, sometimes not even booting at all. The phone would sometimes be unresponsive to holding the power button for up to 12 hours before the phone booted up again. Not saying I help the power button that long, but tried frequently over that period of time.
Over the past few days I've taken to troubleshooting in the ways I could think of and what I've read here on xda (I can link to any of the threads if you are curious) and the rest of the web. I started by disabling xposed, restoring stock boot image and removing root, and have since flashed completely to stock MMB29V and have followed the advice of @audit13 to even flash the userdata.img file and perform a factory wipe before booting the phone for the first time.
Nothing works. Even after being bone stock now there are still random resets, with the power button having to be held down for quite some time to power back on (if at all). The only difference is that it hasn't been getting stuck on the boot animation when it does power on.
I'm a bit sad, and realizing that this is probably the end of the line for my venerable Nexus 5, but any help/suggestions are welcome. Thank you in advance!
Download the Nexus Root Toolkit for your computer to try to restore your Nexus.
Could be a power button issue that's causing the resets? Have you tried removing the motherboard and quickly pressing and releasing the power button several times in a row using more pressure than normal?
audit13 said:
Could be a power button issue that's causing the resets? Have you tried removing the motherboard and quickly pressing and releasing the power button several times in a row using more pressure than normal?
Click to expand...
Click to collapse
I have yet to try that, but will try that in the next couple days. Might not get to it tomorrow as I have an upcoming exam.
I'm not completely sure if that's it though since the system seems to hang/freeze before powering down, but I can give it a shot. Thank you for the idea!
FelipeRodrigo said:
Download the Nexus Root Toolkit for your computer to try to restore your Nexus.
Click to expand...
Click to collapse
As a last resort I could try that -- how do you think that would solve my issue? Thank you!
Maybe a battery problem? I'm just guessing at the different things that may cause a boot problem or resets.

Please Help! Stuck at boot screen...

Hello. Sorry in advance if this is the wrong thread. I own a pretty old 1 year old tablet that currently has a problem.
Important info: Android 5, No access to a computer for 2 weeks (vacation), slightly cracked screen (still works), I had to install a Play Store apk as the one I had previously was corrupt. Tablet was functioning fine until the moment of the incident (except for the play store apk, which I later fixed).
Minor detail: Once the screen turns on after a restart the pixels near the top of the screen seem to turn purple for a second when I tilt the tablet.
Here is the story:
I was watching a YouTube video and suddenly my tablet froze. I thought: "Uhh, another freeze how annoying," and waited for it to load. I did not unfreeze. I thought: "Well, I guess I'll be fine if I turn my tablet off and on. This is where I got worried. My Power key was not responding. I tried the volume keys. Nothing. I tried connecting a mouse and moving it around. Still nothing. I thought "Ok, lets try restarting it" I did that by holding the Power key down for 10 seconds. To my relief, it turned off. But when it was turning back on again, it was at the loading screen for a little to long. It usually takes 5 seconds to get past the loading screen and enter the boot screen. I decided to wait. 1 minute: nothing. 5 minutes: nothing. I got worried. I tried restarting the tablet again. I restarted successfully but was stuck at the loading screen again. The was no movement on the screen. Only the loading screen. I decided to try the restart backup button which I could activate by putting a pin in a small hole at the back. It had the same effect holding down the power key had. I decided to ue my backup plan: recovery mode. I successfully entered recovery mode. I chose the option "clear cache" and tried to boot again. No changes. I did a scan for any root errors. it said that there were 5 errors, but there was nothing I could do about that. I tried doing a factory reset, then booting up. The reset was successful, but I got the same effect as always. No changes. I gave up and tried to google a solution on my phone. Most of them told me to install a PC program, but one told me to do the same thing I already did: reset, restart. So I decided to let the tablet sit with the boot screen for 2 hours. When I came back, there was no change at all. I tried searching again for a solution. A YouTube video said that the boot time after factory resets may be long, so I decided to reset and let it sit for a bit. 20 mins later, no changes at all. Finally, I gave up and now try to ask for help here.
Norqw said:
Hello. Sorry in advance if this is the wrong thread. I own a pretty old 1 year old tablet that currently has a problem.
Important info: Android 5, No access to a computer for 2 weeks (vacation), slightly cracked screen (still works), I had to install a Play Store apk as the one I had previously was corrupt. Tablet was functioning fine until the moment of the incident (except for the play store apk, which I later fixed).
Minor detail: Once the screen turns on after a restart the pixels near the top of the screen seem to turn purple for a second when I tilt the tablet.
Here is the story:
I was watching a YouTube video and suddenly my tablet froze. I thought: "Uhh, another freeze how annoying," and waited for it to load. I did not unfreeze. I thought: "Well, I guess I'll be fine if I turn my tablet off and on. This is where I got worried. My Power key was not responding. I tried the volume keys. Nothing. I tried connecting a mouse and moving it around. Still nothing. I thought "Ok, lets try restarting it" I did that by holding the Power key down for 10 seconds. To my relief, it turned off. But when it was turning back on again, it was at the loading screen for a little to long. It usually takes 5 seconds to get past the loading screen and enter the boot screen. I decided to wait. 1 minute: nothing. 5 minutes: nothing. I got worried. I tried restarting the tablet again. I restarted successfully but was stuck at the loading screen again. The was no movement on the screen. Only the loading screen. I decided to try the restart backup button which I could activate by putting a pin in a small hole at the back. It had the same effect holding down the power key had. I decided to ue my backup plan: recovery mode. I successfully entered recovery mode. I chose the option "clear cache" and tried to boot again. No changes. I did a scan for any root errors. it said that there were 5 errors, but there was nothing I could do about that. I tried doing a factory reset, then booting up. The reset was successful, but I got the same effect as always. No changes. I gave up and tried to google a solution on my phone. Most of them told me to install a PC program, but one told me to do the same thing I already did: reset, restart. So I decided to let the tablet sit with the boot screen for 2 hours. When I came back, there was no change at all. I tried searching again for a solution. A YouTube video said that the boot time after factory resets may be long, so I decided to reset and let it sit for a bit. 20 mins later, no changes at all. Finally, I gave up and now try to ask for help here.
Click to expand...
Click to collapse
Was your device rooted? Did you have TWRP custom recovery installed? If you don't have either of these two things then your only option is to flash the stock firmware via PC.
Do a google for:
"Return to stock (your model number)"
If what you need is out there somewhere, that woll find the instructions, the tools and the file(s) you need.
Sent from my LGL84VL using Tapatalk

Categories

Resources