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.
Related
Hi all !!! Sorry for my English but I need your help
I commented what is happening with my phone N5 (which for good and evil is always stock without root or anything, with corresponding OTA updates.)
1- Yesterday afternoon at lunchtime while reading a book in playbooks, I notice that suddenly disappears one line and then appeared intermittently. I close the app and noticed the same thing happening on the screen menu. I shut down the cell and turn on again and I thought it must be an application be kidding. But still does.
2 Also yesterday I happened to change the security on the phone screen. After a while of normal operation, try to turn it on the screen with the button, nothing, the screen goes "black", with light and retrolight turned on but no picture no nothing .
Called the cell to see if it works or is turned off and the phone rings but the screen nothing. Try turning it off and on again by holding the on / off / lock button and the phone restarts, but the screen nothing. In one such attempt to do the above it is seen that managed to turn it off. And I get it on and do a normal boot, except that the picture of my screen is changed to the original. Change the lock screen which was previously using (slip). And it seemed that out or some conflict with the lock. In one of those again pressed the ON / OFF / lock as would normally and it starts all over again.
After I magically back to life, I want to make a full wipe as I think it should be an app that is doing some conflict or something. BUT ....
3I turn off the phone and then press the keys VOLUME UP / DOWN and ON / OFF is normally off, squeezed the first screen with the options but options RECOVERY / BOOTLOADER appears in red I choose RECOVERY give the ok with the key and .... andriod robot appears with the legend below that says something (I do not remember well) without or without controls options appears. So its seems thatI dont have recovery.
After that keep pressing the key ON / OFF and the phone turns off and / or reboot normally. All this I did it again to see if the error reappears and looks that I do not have recovery.
The failure of the screen is increasing. I dont know if they are separate problems or is it all the same problem.
Sorry if I was too long but I need the help of you.
UPDATE Now it seems that the screen died, since I do not achieve to turn it on as before, the light and the retrolight its ok. The phone receives calls and notifications but the screen stills black.
Thanks all.
Matias M 73
the android laying on its back IS the atock recovery.
simms22 said:
the android laying on its back IS the atock recovery.
Click to expand...
Click to collapse
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Matias M 73 said:
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Click to expand...
Click to collapse
sometimes things just "derp". itll happen more often if you dont reboot your phone often. also, your phone will be a little bit more responsive if it gets reboot once a day or two.
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
republicano said:
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
Click to expand...
Click to collapse
Thank you Republicano!!
I think too that its a hardware issue. I already see on you tube problems like mine.
Thanks again!!
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.
An hour or so ago everything worked fine, and then I updated my playstores pending apps (only Fleksy was pending) and the "force touch" feature of the phones seems to have completely stopped working, no matter what setting I turned on or off it didn't work...
Anyone has a clue as to what can cause this?
General notes:
1. Using stock Exynos unlocked variant
2. I am using package disabler (which btw didn't improve much my battery life, but that might be just me using the phone too much ) so maybe one of the packages decided that it depends on a disabled one?
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
RazoE said:
I noticed mine stops working after a reboot and takes about a minute or two to get back up and running. Try a restart after clearing caches, if nothing still, reboot in safe mode. If it works, then its an app you installed interfering.
Click to expand...
Click to collapse
Mine also stop working after I restart my S8 Plus, it will again work if I wait around 20 minutes. Is this software or hardware problem? Any solutions?
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Ady1976 said:
Wish mine would stop working permanently! can't stand that feature forever brushing across it and waking the phone up!
Click to expand...
Click to collapse
How does it act up on your part? Mine would just stop working if I restart the phone & I should wait sometimes hours before it would work again.
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Ady1976 said:
Every time i'm installing my phone in my car mount I need to hold the phone from the bottom to install it correctly and brushing my fingers across the bottom is constantly waking the phone up, I've lowered the sensitivity to it's minimum.
Click to expand...
Click to collapse
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
bladefrost said:
I see, problem is not the same. On my part the tactile home button simply doesn't work when you press on it. I have to double tap to wake the phone when on lockscreen.
Click to expand...
Click to collapse
Unless your phone is unlocked no pins etc the phone will just go to the lockscreen, it's a useless feature, most people have the phones locked and thus it's a complete waste of time, it sounds to me the capacitive home button part of the screen was an afterthought because they couldn't install the fingerprint reader under the screen, just had a software update yesterday and still can't turn it off, basic stuff Samsung should enable an ON/OFF toggle switch for this.
Had the same problem with my S8 Plus India Variant(SM-G955 FD), I got my screen replaced from service center, Device was not rooted back then, so was under warranty.
But it is an hardware issue, as since then it has never gone off.
I mean when I press the home button hard it doesn't wake the phone up & no vibration. It happens when I restart the device then it would stop working for few minutes to a few hours sometimes, then it would start working again normally until I restart the phone again. I think this is just a software issue.
Hi everyone, I'm throwing this out there because I've run out of ideas about what has just happened to my U12+ (64gb) today.
I woke up and used my phone as normal, caught up on Twitter and the news, the usual apps etc. nothing untoward. The same routine I've had with my phone for the past 18 months of owning it with zero issues. My handset is stock OS (Android 9) and so not rooted or anything like that. Virtually all the apps I use are standard issue from the Play Store, nothing really "out there" and I have BitDefender installed to look after security. Same setup I've had for over a year. The battery was around 35% so I plugged it into my wall charger while I went off to grab some breakfast. When I returned a couple of hours later the light on the handset was green, I unplugged the charger and attempted to unlock it with my fingerprint.
The phone asked for my PIN, no big deal so I entered it. Black screen. Tapped the power button again, it requested my PIN again, I entered and... black screen. Okay, I was a little bit concerned now. I held down the power button so the haptic buzz occurred, held for 10/20/30 seconds, a minute... nothing, no restart. Tap the power button and it asks me for my PIN again and shows yet another black screen. I held down Power + Volume Down but again, nothing and no restart.
I asked someone to call me, the screen came to life and I could take the call but each time I tried to pull down the system tray in order to try and reach Settings to restart it asked me for my PIN, I entered it = black screen. The call was unaffected.
I removed my SIM + microSD card tray = same deal as above.
The phone is clearly responsive in some way and the screen does display to ask for my PIN but I can't get into it in order to reboot it. Extremely worrying.
Does anyone have any advice? At the moment I am faced with the prospect of simply allowing the battery to run out so the phone shuts down naturally but that is going to take the best part of 2 days.
I'm really disappointed because I was planning another 1-2 years use for this handset as I just bought a 1TB microSD card which has been fine in the phone for weeks so I don't think that's the cause. It is also genuine SanDisk.
Any suggestions or advice? Thanks in advance.
Hello, I hope you have made a backup with google backup recently... This does not happen often on android, but sometimes the system could have a problem. You can try this go the bootloader with the power and volume buttons , after recovery.. after apply a wipe data/ factory reset.. is will make a factory reset of your phone except the sd card. You should by fine after that and profit again.
Thanks, I appreciate your reply.
At the moment I am running the battery down until the handset switches off naturally. When it comes back on I will try to launch the phone normally, if that doesn't work I'll run the battery down again and attempt to reach the bootloader.
My photos are backed up to the cloud, I may lose some text messages but I managed to transfer the majority of my 2FA over to another Android device bar one.
At the end of the day if it's a choice between wiping it or a bricked/unusable handset then I don't really have one. What a pain.
Magimix^ said:
Thanks, I appreciate your reply.
At the moment I am running the battery down until the handset switches off naturally. When it comes back on I will try to launch the phone normally, if that doesn't work I'll run the battery down again and attempt to reach the bootloader.
My photos are backed up to the cloud, I may lose some text messages but I managed to transfer the majority of my 2FA over to another Android device bar one.
At the end of the day if it's a choice between wiping it or a bricked/unusable handset then I don't really have one. What a pain.
Click to expand...
Click to collapse
At the moment I am running the battery down until the handset switches off naturally <----- why that??? Even on a bootloop or a black screen you can reset it hold the buttons power and the volume, you can go on the bootloader.
Max128 said:
At the moment I am running the battery down until the handset switches off naturally <----- why that??? Even on a bootloop or a black screen you can reset it hold the buttons power and the volume, you can go on the bootloader.
Click to expand...
Click to collapse
The first thing I tried to do was hold down the power button or the power button in tandem with the volume buttons but the handset won't restart. I tried loads of times holding it for different amounts of time and... nothing.
Trust me, I tried.
The only way I can get the device to switch off is by draining the battery. I'm almost at 20% so it shouldn't be too much longer.
Well I already got a black screen after flashing a module magisk.. I have holding the power button and the phone have restart no problem, same thing on bootloop. You need to be sure to hold the button correctly.
Max128 said:
You need to be sure to hold the button correctly.
Click to expand...
Click to collapse
Yeah, I'm certain I was holding the buttons correctly. I tried about 20 times using different combinations just to be sure but the device would not restart. The haptic shock buttons are one of my least favourite features of the u12+, it's got to be said.
Anyway, the phone ran out of battery about 15 minutes ago. I left it alone for few minutes and switched it back on. It allowed me back in and the device appears to be fully functional again. I can unlock by thumb print, face or PIN without issue.
Basically, it's fixed. My only concern is I have no idea what caused it or if it will happen again.
Thanks for offering help though, I appreciate it. I'm not sure if this thread can be closed/locked now? I'll look into that.
Cheers.
Yes.. i love the buttons too i never got a problem with this. Great if is fixed! Maybe make a factory reset the next time.
I am wondering if the new flagship have haptic buttons too.. htc will announce it Tuesday.