Related
My TF has done this three times now since yesterday's FOTA. The device hasn't crashed as I can still use ADB and the notification bar relects the true battery status, time etc. I can also turn the screen on and off with the power button but I can't unlock it due to the screen not accepting touch input.
This happens regardless if use a custom rom or not.
Has anyone else had this experience?
Roach2010 said:
My TF has done this three times now since yesterday's FOTA. The device hasn't crashed as I can still use ADB and the notification bar relects the true battery status, time etc. I can also turn the screen on and off with the power button but I can't unlock it due to the screen not accepting touch input.
This happens regardless if use a custom rom or not.
Has anyone else had this experience?
Click to expand...
Click to collapse
My device had this issue, but with the 3/25(?) firmware (it came from overseas -- Taiwan). I basically thought I had a brick, but yesterday I used not-quite-pristine US system.img via a nandroid backup, and it brought it back to life. Still working, 18 hours later (and with the latest OTA update).
If you still have cwm / nandroid access, PM me and I'll post up the system.img that I used to fix my issue, yesterday. It was basically an image I found on Android Central, and I yaff2'd it and added my own md5sum so that nandroid could recognize it. My ongoing concern is that the permissions could be all screwy and softlinks could be broken. But, given the choice of that versus a bricked tablet, I could live with broken softlinks.
mine has done it 3 time while playing fruit ninja but only while playing that and not whit normal use as browsing and all that
Fisken said:
mine has done it 3 time while playing fruit ninja but only while playing that and not whit normal use as browsing and all that
Click to expand...
Click to collapse
Same here. Touchscreen stopped responding while playing that game, but that happened even before the OTA.
How can you get it to start responding again or force a reboot? I just got mine in the mail, pushed the lock button, and now it won't respond to any of my touches. Stuck at the lock screen.
jonnyktyler said:
How can you get it to start responding again or force a reboot? I just got mine in the mail, pushed the lock button, and now it won't respond to any of my touches. Stuck at the lock screen.
Click to expand...
Click to collapse
Hold the power button for 10-12 seconds to force power it off. Release button. Wait a couple seconds. Power on as normal (a 5-6 second hold down of the power button). If still no joy... you're screwed perhaps.
ok thanks a lot holding the power button down for a long time did force it to turn off, now it's working again.
OK - since the recent ota upgrade to ICS we've been having a few problems with the table touchscreen freezing - unfortunately now it seems to have got stuck almost all the time. Just at the moment, it is not responding at all to touch - just displays the lock screen when powered on, and then times out a little while later to black. I have to push power to get it back on - but the touch screen simply won't respond to unlock it. So far I have tried:
Holding down power until restarts - no effect - reboots still locked.
Using Vol-Down power on and doing factory reset - no effect - reboots into android setup screen touchscreen not working.
Draining power until it won't turn on. Then recharged. This worked! However...
After going through the setup process, resintalling apps etc., I hit the power button to go into standby. I then thought I'd go straight back in, but as soon as I hit the power button again, it wouldn't respond! Left it charging for a couple of hours, and turned on, this time got in - but same again - hitting the power button and coming straight back in, it's not responding again.
So I'm now back with a fully charged tablet that won't respond to touch at all. - perhaps if I leave it a few hours it might respond again - until it goes into standby!? The device is fully stock with WW_epad-9.2.1.11-20120221 (according to the screen at boot up when you hold down vol-d).
Is this likely to be software or hardware related? Do I need to send it for repair/replacement, or is there something else I can try first? Any help much appreciated. (Oh - I don't have external keyboard btw - so without screen it's pretty limited what i can do!)
Cheers,
Colin.
I have already encountered the same problem but with a cutom rom. to find my touch, I had to do a full wipe and new intallation.
I did full wipe using the Power/Vol-D but the touch screen didn't start working again until I let the battery completely drain.
Then I reinstalled everything (screen was working to begin with), however after I'd set everything up and reinstalled all my apps it stopped again.
Yesterday I managed to get an ota update to 9.2.1.17 (it started working for a short time). But then aftger rebooting again, it stopped again.
This morning it is working again, and I have uninstalled all my apps - just the core stuff on there now. For the moment it appears to be working (which is the longest for a while!) - going to see if it stops again while there aren't any extra apps installed...
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.
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.
hi all, ive had my s7 for 3 years now, amazing phone, but a few weeks ago this freezing reboot problem appeared and idk whats going on, my phone isnt rooted, and ive never messed with custom OS or any of that, its on android 7 stock, the battery is still good, but im wondering if this freezing problem is software or hardware related, when it freezes and reboots it gets stuck on the first logo, if i dont force it to shut off it will stay that way or keep rebooting till it runs out of battery, so after i force it to shut off sometimes it reboots immediatly and sometimes it stays black for a while and boots randomly, i try to go into recovery menu and most times it freezes on no command screen and if i leave it there the phone gets incredibly hot, so i force shut it again and this time with the charger connected so it shows charging icon as if its shut down... i leave it for a while then turn it on and its working untill it freezes again... i am considering installing lineage os incase the firmware is corrupt but im not very familiar with all of this and after reading other posts where the user did way more complicated stuff and the problem maintained... im not sure if its really gonna work, so im looking for advice on here