I tend to use my pad for traveling mostly, so it has been unused for about 6 weeks.
I turned it on a couple of days ago and all was fine until overnight it went into a reboot loop (or so I thought).
The following day it was dead, so I recharged it (during which it was rebooting constantly).
It would reboot every 10-15 seconds, even it it was in Recovery or FFBM mode.
The fact that it would reboot whatever mode it was in meant (IMO) that it was a hardware issue and not a software one, and the likely culprit was the power button. (It was acting like the power button was constantly depressed).
Using a pin I was able to lift the power button slightly and sure enough the pad booted and showed that it had pretty much fully charged even whilst rebooting.
As soon as I removed the pin it went straight back into a reboot loop.
Does anyone have any ideas how i may proceed to fix this issue? (It may even just be a humidity issue on the fingerprint sensor as I live in a highly humid country.)
I can't even work out the best way to open the case as there don't seem to be any tear-downs..
Thanks
Mine happen same issue with this, solve it by using
Step 1 : Spray 3M™ Quick Drying Contact Cleaner 16-102, around the Power Button Area.
Step 2 : Apply 3M™ AR-100 Anti-Rust lubricant.
So far after 1week, not more repeated
Related
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...
I encountered my first problems with my Nexus 5, which i am very happy with, about 1-2 weeks ago. After about 11 months of happy, problem free use, without dropping it or anything else, it started misbehaving (about a month with Android L so far). It crashed and wouldn't start up farther than the 'android' screen most of the times. Rarely it would fully boot, but the seemed to go into the lock screen and crash after a max. time of about 1 Minute of normal use. After going through this a few times I checked some forums and found a solution suggesting to repeatitly press the lock screen button while it boots. This solution worked quite good, even though i had go through the process multiple time the following days.
Last thursday evening (today is saturday) though my phone crashed fully once more (just after checking and having an 80% charged battery) , but now the quick hits on the Power button did not work at all. Instead my phone wouldn't react at all. Neither pressing the volume rockers alone or together with the power button would work either. Having plugged in the Nexus though acheived it to at least reach a state which seems to be a more common problem. It has been discussed and solved for many (seemingly everyone) in another thread called '[Q] Nexus 5 constantly rebooting at 'Google' ' (Link to this at bottom). Long explanations and videos of the situation have been given here, depicting my exact situation along with two solutions:
1. Using magnets near the power button (to apparently loosen two magnets used when pressing the power button)
2. Two flick and quickly press the button (for some this had to be done many minutes)
After seeing many (surprisingly) positive reactions to both methods, I tried them myself. I began with the magnet method and without having it connected to a charger it would boot to the google screen twice (note: As said, without a charger nothing happened). First once about as long as when connected to power and once very briefly. This method didn't prevail more than once and i couldn't start it up any diffrently than before.
So next I tried the flicking method and (maybe because of the magnets) it booted al the way to the 4 colored dots flying around. I let go and it crashed once more. I fooled around with the magnets again and tried the flicking method again, without stopping, as other users mentioned a long time needed (15-30 Min.) and after about 20 Minutes I stopped. My Nexus did not crash, but it is now 'stuck' at the colored Dots. I have tried connecting it to a power outlet, my PC and again started pressing the power button and volume rockers, without effect. It has been so for about an hour if not more. I will try to drain the battery and then continue, but if any other solutions are known Please help, thank you!
Link to other Question: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-constantly-rebooting-google-t2809617
Update
After having drained the battery completely and then charging it again, the normal 'charging battery' icon popped up. Trying to start the phone, however resulted in getting into the flying dots loop again... I am able to go into fastboot mode, but neither start or Power Off help the situation. Should I go into recovery mode? I would strongly dislike losing all my data....
(Update)
I tried going into recovery mode, but the only thing that happened was that a little android figure, lying down with a red exclamation mark showed up (which should be normal as I recall going into recovery mode before my problems), and a text saying 'no command' above it. What now? I'm all out of ideas and back up plans, except calling google as it should still be under my warranty. But I don't want to give up my data as I haven't saved anything and I don't want to give up my phone either.
This is kind of a last resort - to see if anyone has any experience with this problem. I have Googled around for similar problems and haven't quite found the same issue anywhere.
OK, so let me emphasise, this is not a bootloop - there is clearly some kind of hardware or firmware problem where the phone is interpreting the power button as being pressed.
I can power on, and the phone will get to various points before then rebooting, as though the power button were being held down:
- often it only gets to the splash screen and then reboots
- sometimes I can get it into recovery, but whatever option I happen to highlight (I have about a second or two to do so) just gets selected as though the power button were pressed
- sometimes the phone will even boot and can be used for a little while (enough even for me to back up the files off it), but sooner or later a message will pop up saying something along the lines of "Continue holding power button to reset", again - OBVIOUSLY the system thinks the power button is pressed down.
The problem happened while the phone was under guarantee, the repair place kept it for weeks, eventually "replaced the motherboard" (so they say) and it seemed to work for a time. Now the problem is back and there is no more warranty. A reputable repair place has had a look and said they can't do anything.
I have tried taking the top cover off and fiddling with the microswitch (only thing I could think of) to see if there is anything obvious going on there, but that doesn't seem to be the cause of the problem.
Any ideas, before we ditch the phone as a $XXX loss?
Just to update - I managed to catch the phone when it wasn't going crazy, go into fastboot and flash CM10.2. Could've restored to stock I suppose, but I am concerned that may somehow have been the cause of the problem in the first place.
As of 12 hours later the phone is behaving itself. Can't be sure a new ROM is what did it, but fingers crossed...
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.
Hi,
My S7 crashed randomly and was stuck in a loop of the recovery menu. The short version is, I was fairly convinced it was a battery issue, and after changing the battery I was able to boot up successfully and (eventually) backup / copy off all my files. It wasn't esasy as it was constantly crashing and very unstable.
So, I did a full factory reset. This was via the settings menu after booting up and logging in because I couldn't access the recovery menu method. Factory reset has not solved my issue is still crashes usually after a few minutes at best.
Things that work
- Screen not broken, works perfectly, no dead pixels.
- No water damage / not dropped
- Volume Up and Down keys work (for volume and force power off when its crashed)
- Speakers / Microphone
- Both Cameras
- Wireless charging
- Cable Charging
- Full factory reset to latest stock android 8. Never rooted. Totally stock.
Things that don't work
- Vol Up + Home +Power to get to recovery menu / safe mode. Never managed to successfully do this
- I think it could be running a bit hotter than before, this may be subjective.
- Sometimes it crashes, screen powers off, but red charging light remains even when unplugged and it runs hot. Basically until the battery dies.
- Often crashes on first boot, e.g. during "samsung" boot screen. - Will restart and often gets to login on second attempt.
I've been testing via the diagnostics menu *#0*# (What a cool feature!) - Generally this is working ok, and nothing jumps out as failing, but its not easy as it crashes so randomly anyway. Can anyone recommend anything specific I should test?
So - Have I got a new Brick? Is there anything else I should do to try to save my phone? If it was smashed I could begrudingly write it off, but its in otherwise perfect condition! (3 months out of warranty!)
First time poster, any help appreciated.
Thanks
Sandstone Stickman said:
Hi,
My S7 crashed randomly and was stuck in a loop of the recovery menu. The short version is, I was fairly convinced it was a battery issue, and after changing the battery I was able to boot up successfully and (eventually) backup / copy off all my files. It wasn't esasy as it was constantly crashing and very unstable.
So, I did a full factory reset. This was via the settings menu after booting up and logging in because I couldn't access the recovery menu method. Factory reset has not solved my issue is still crashes usually after a few minutes at best.
Things that work
- Screen not broken, works perfectly, no dead pixels.
- No water damage / not dropped
- Volume Up and Down keys work (for volume and force power off when its crashed)
- Speakers / Microphone
- Both Cameras
- Wireless charging
- Cable Charging
- Full factory reset to latest stock android 8. Never rooted. Totally stock.
Things that don't work
- Vol Up + Home +Power to get to recovery menu / safe mode. Never managed to successfully do this
- I think it could be running a bit hotter than before, this may be subjective.
- Sometimes it crashes, screen powers off, but red charging light remains even when unplugged and it runs hot. Basically until the battery dies.
- Often crashes on first boot, e.g. during "samsung" boot screen. - Will restart and often gets to login on second attempt.
I've been testing via the diagnostics menu *#0*# (What a cool feature!) - Generally this is working ok, and nothing jumps out as failing, but its not easy as it crashes so randomly anyway. Can anyone recommend anything specific I should test?
So - Have I got a new Brick? Is there anything else I should do to try to save my phone? If it was smashed I could begrudingly write it off, but its in otherwise perfect condition! (3 months out of warranty!)
First time poster, any help appreciated.
Thanks
Click to expand...
Click to collapse
Can you flash latest unbranded stock? If still happens then it's battery failing. S7 is old phone now
cooltt said:
Can you flash latest unbranded stock? If still happens then it's battery failing. S7 is old phone now
Click to expand...
Click to collapse
Thanks, I've replaced the battery with a new one. Tried full factory reset a second time but it crashed and hasn't restarted since.
I think it must be a hardware issue. It thinks its charging when unplugged, gets hot when "off" won't switch off when crashes so need to wait for battery to die before recharging and trying again.
Yes, its old ish, but really only just over 2 years. My S3 lasted 4.5 years so getting half the lifespan from the S7 is really dissappointing. It was in perfect condition until this happened .