Database Info

[Completed] Htc One M8 hardware buttons working weirdly

Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim

Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.

Continuous reboot with HTC One S - almost certainly a HARDWARE problem - any ideas?

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...

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.

Please help me with my phone.

Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.

rawon3 said:
Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.
Click to expand...
Click to collapse
You might be having hardware issues, such as a faulty power button. If you are the type of user that frequently presses the power button to lock/unlock the screen, this leads to excessive wear on the button components, this is why some users prefer to use the "tap to sleep" and "tap to wake" feature, to avoid wearing the power button out. On my LG, this feature is called "KnockOn", it's located in Accessibility settings.
Sent from my LGL84VL using Tapatalk

Samsung J7 Prime (2017) SM-G610Y Boot Looping Problem

Good day, this would be a pretty lengthy post. I'd like to describe my experience clearly since I don't know what I possibly skipped over as I am very positive that my efforts have been correct basing on prior XDA forums. I even made this account solely for posting this to ask for help formally along with archiving this problem I'm having for those having a similar experience.
I've been working on my mom's phone this whole day and there are fruits of my current hard work. I am immensely stressed and despairing with my situation.
The Problems
Infinite boot looping
Can't access the recovery menu (power, volume+, even with home button)
Can access the ODIN / Download menu
Can't turn off either (holding down power button has no effect)
What I've done so far
I read XDA forums about similar experiences. Can't really access the recovery menu so I've factory reset.
We live in the Philippines and this phone is open line, so I went with those requirements while searching stock ROMs.
I downloaded the stock ROMs of the phone model via galaxyfirmware.com which was positively shared in the forums.
Did trial and error with it and eventually got the right one. I have formed a level of understanding with the filenames and eventually knew which is compatible.
Used Odin3 to Flash the BL, AP, CP, CSC, and even go Nand Erase and got the PIT file inside the CSC (Opened it using winrar)
The flashing is actually successful and quite fast to be honest.
The phone reboots itself and shows that it is still sadly boot looping.
Also, despite the several files used for the Flash, still can't access the Recovery Menu.
With that said, I have also tried using Frija which automatically downloaded the stock ROMs based on the model name and CSC type. Placed it in ODIN again and no changes, still boot looping.
I also can't put the TWRP I got here because of the FRP Lock, which can be undone via the settings of the phone. But since it's boot looping, I can't really do much about installing a custom ROM.
Currently, my dad is letting the phone drain its battery, since we can't really turn it off. The phone model doesn't have easily detachable battery as well, unlike the old days.
For some additional notes of what happened prior to this incident
My mom was just playing with her phone as her usual days went on. That day, she installed a new hotel-themed game she saw on Google Play. As I assume that it's from the app itself and not on some shady apk website, I saw no problem with it and didn't think it was the cause of all this. I went with the theory anyway and with the flashing, using CSC instead of HOME_CSC (which apparently saves the existing data on the phone from wiping), and even used the Nand Erase in the end. It's still stuck at boot looping.
I would appreciate anyone's reply to this discussion. I am truly desperate to fix this for my mom. If worse comes to it, I'll save money to buy her a brand-new phone.

You don't have a working android, so you won't remove the RFP. TWRP will not help you with this.
The symptoms you describe indicate a defective power button.
You manage to enter download mode because the power button is constantly on.
Because of the constantly on power button, you have no way to turn off the phone. Bootloop can also be the result of a constantly on power button.
To sum up, you should fix the power button.
1. The easiest way is to blow with compressed air and press the edge of the button with your fingernail, rapidly releasing the pressure. Perhaps the fuzz has blocked the button. Unfortunately, this rarely works.
2. Take the phone to a local service center.

Hi ze7zez! Me and my dad greatly appreciates your insight and we were definitely enlightened on this angle.
We didn't really think that the power button was stucked pressed on because you can clicking sounds when you press on it. The phone never had problems with the buttons along the 6 years it accompanied us, perhaps its age does start to show.
We're going to look into it tomorrow. Thank you very much! You gave us the idea that it may be shorted inside or some sort. Thank you again!

A bit of update.
I pried open only the back case of the phone so I can see and clean up the power button. I used tools specifically for it and made no damage on the phone during the process.
We couldn't really see anything busted from there. The buttons on the circuit still do the neat clicking sounds on it. Battery still looks the same.
Testing out the theory that the power button was stuck on:
We tried to only press and hold the volume down and power button. It didn't go to the download menu. We needed to press down all three together to access it. It is confusing since we believe it would be a power button issue too, as the phone instantly turns on by itself when plugged to a power source (it's completely drained by now and we still can't turn it off manually)
Perhaps it's an internal circuit problem with the power button? It's confusing with the fact we still have to press on it to access the ODIN menu if it was like "on" the entire time it's looping.
Thank you in advance for further insights.

Try restarting by pressing home, power and volume up all at once.

Hi Pranav2406,
I have tried that as well in order to access the Recovery menu to factory reset, but no luck.
We have given up on repairing the phone and went out yesterday to buy a new one in a rush.
We will still send this broken phone to a repairman.
If he fixes it, I'd ask what he did on it so I can post an update on this problem as well.
It's better to let the expert troubleshoot it.
I do suspect the problem in the phone's hardware. I'm pretty confident with all the stock ROM flashing I've done so it's not a software problem.
Thank again for everyone's insights.
Perhaps this case is too much for an amateur to fix.