HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
The Stig 04 said:
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
Click to expand...
Click to collapse
I would love to go back to stock if I could get the device to turn on.
This was the first SuperSU update that I can remember having installed, so yes, I've always installed through recovery. The update even prompted me that, for HTC devices, better luck is had via updates through recovery.
dottat said:
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
Click to expand...
Click to collapse
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
devmage said:
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
Click to expand...
Click to collapse
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
devmage said:
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
Click to expand...
Click to collapse
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
dottat said:
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
Click to expand...
Click to collapse
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
devmage said:
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
Click to expand...
Click to collapse
I would suggest warranty route through HTC. You have got a brick.
dottat said:
I would suggest warranty route through HTC. You have got a brick.
Click to expand...
Click to collapse
That is my fear. Thank you for your help.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
Thanks TIA for any help!
Matt
Click to expand...
Click to collapse
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Thanks for the info...I appreciate the response. I'm hoping that there's something that can be done but after 2 hours, trying every trick I could find via
Google with nothing to show for it, I'm keeping fingers crossed that it's something simple I'm missing. If I could just get into the dang bootloader!
Thanks again!
Sent from my SM-P600 using XDA Free mobile app
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
Click to expand...
Click to collapse
To add to this, I've let the phone sit for about an hour, untouched, and now the green light is blinking like it does when there's a SMS/email. Pushing the power button doesn't do anything.
devmage said:
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Click to expand...
Click to collapse
For what it's worth for anyone that finds this info useful...can't take credit for this as I found it over in the One M8 forum. Thanks to @mpogr
I quote his post: "The problem was that my phone's screen was going blank after the normal boot screen, so I couldn't see when it gets turned off. I was simply pressing the Vol Up + Power for too long, so it would go into full reboot. I just measured the amount of time it was taking to do this (was ~12 seconds). So I pressed Vol Up + Power for ~10 secs, then released those and pressed Vol Down. That finally brought me into Fastboot.
I could have probably gotten the same result by pressing Vol Down + Power, however, the phone screen was blank all the time, so it was difficult to understand when I should have released the Power button to let it go into Fastboot."
I held Power/Vol Up for 10 seconds (as he described) and then let go and immediately held Vol Down only...after about 3 seconds, bootloader screen came up and I was able to get into recovery and restore a backup.
Related
I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
That almost sounds like some sort of power issue. Have you left it sit turned off until the battery was full?
Yes, I left it overnight and it just keeps flashing the battery screen and then resets. I also have an external charger and used it to charge the battery, so it's not an issue with the battery actually being empty.
Have you been able to get the phone into download mode previously?
Have you have dealt with a boot loop and performed an Odin recovery previously? If not, remember it can take a few tries to get download mode to pop up.
If you can't get Odin to go, you might try flashing with Kies.
I am wondering if your phone met with some kind of disaster when you weren't around (trauma or liquid).
anyone747 said:
I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
Click to expand...
Click to collapse
This sounds almost exactly like the problem I had with my Sidekick. In my case, it turned out to be a bad battery and a loose ribbon cable on the motherboard. I'd check those two things.
This happened to me as well, and the three-button method to get into download mode wasn't working. For some odd reason, for me to get into download mode all I have to do is hold down the power button + track pad, and it goes right into download mode... Maybe slightly different model?
Try that - power button + trackpad
Bootloops.
Not a guaranteed fix by any means but for troubleshooting purposes you may want to consider making a USB JIG. It will most definitely help you figure out just how serious the problem is and if it IS software related with a way to get it working again you will need the JIG anyway so its worth a shot. If nothing else you learn a new skill and you're the proud owner of an incredibly useful tool that you can say you made yourself. good luck!
I know this post is kind of old, but it just happened to me last week (same circumstance, a rooted phone, but stock). I ended up just pulling the battery out and pressing the power button a couple times to hopefully drian it and letting it sit for 15 minutes, and then I put the battery back in and it worked again. I now have another rom flashed on it, I hate stock.
I know this forum is ancient, but I'm working on an E-Bay phone with this exact issue. I found the following thread the most useful and informative on the problem:
http://forum.xda-developers.com/showthread.php?t=1996709
Hopefully this helps other.
what i did was hold the power volume and button between the menu n back with the left hand YES HOLD IT UNTILL THE PIT IS UPLOADED. then u can let go then slide in the vattery with the right.while checking off the flash bootloarders on the heimdall with it fixing my phone XD
I had this happen, I dissassembled the phone, and used an alcohol pad to clean the power button area, and manipulated the button a lot, let it dry, reassembled...it still bootlooped.
BELOW IS RISKY BUT WORKED FOR ME
So while the back cover was off (exposing the cicuit board but everything still connected) I inserted the battery and watched it boot loop...during this, I used a flathead screw driver to "short" the power button pins...this let it boot fully, and it has been fine since.
i smacked the phones power button a few times and it worked
Today, my family was going to celebrate Canada Day. I was running Root-Box *with Halo!* and everything was well. I charged up my phone to 80%. Cleared the necessary caches, resets, and then proceeded to restore to my now 20 day old ViperXL Backup. I restored and booted , everything was working well, but the phone was hot as it always is when i restore a ROM. So i went to go get ready, when i came back i turned the phone on from standby and it didn't respond. I unplugged it and did all button combinations ( volume up and down and power, volume down and power,just power). I did lots of research and I all I could find was that leave it to cool down then charge. So I left it and came back after 3 hours and it was still the same. Another finding from my research was to charge it. Now, when i do it flashes the red led. and thats all. Its supposed to go to solid red after a while but its been 3 hours and still blinking red. I tried to adb things (adb reboot, addb flash recovery <file link here>). But nothing. So now Im here hopefully you guys can help me out. Thanks for reading.
Also, when i plug it into the computer, it detects installs a driver thens stops. It keeps on making connect and disconnect sounds on the computer. Not detected by adb or htc sync manager. I tried all the power cables, stock HTC, apple power block, samsung and even blackberry!
mr.5106411 said:
Also, when i plug it into the computer, it detects installs a driver thens stops. It keeps on making connect and disconnect sounds on the computer. Not detected by adb or htc sync manager. I tried all the power cables, stock HTC, apple power block, samsung and even blackberry!
Click to expand...
Click to collapse
hope it doesn't detect QHSUSB_LOAD when you connect it to your PC...
cr1960 said:
hope it doesn't detect QHSUSB_LOAD when you connect it to your PC...
Click to expand...
Click to collapse
thanks for the reply it connect but disconnects. If you go to device manager it keeps refreshing as it connects and disconnects and then reconnects. When you do however go to human interface devices you see HID interface, and USB input devices. Thanks for replying. I cant get into the bootloader either. Charged it all night and its still the same thing.
mr.5106411 said:
thanks for the reply it connect but disconnects. If you go to device manager it keeps refreshing as it connects and disconnects and then reconnects. When you do however go to human interface devices you see HID interface, and USB input devices. Thanks for replying. I cant get into the bootloader either. Charged it all night and its still the same thing.
Click to expand...
Click to collapse
Have you tried the simulated battery pull?? Just hold down power until captive lights start flashing.. let it keep flashing for I think 10-12 times and release power button.
Sent from my HTC One XL using xda premium
31ken31 said:
Have you tried the simulated battery pull?? Just hold down power until captive lights start flashing.. let it keep flashing for I think 10-12 times and release power button.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I tried all combinations, it wont go to boot loader, it wont do a simulated battery pull it wont re calibrate the chagring mechanism. (vol up + vol down + power).
mr.5106411 said:
I tried all combinations, it wont go to boot loader, it wont do a simulated battery pull it wont re calibrate the chagring mechanism. (vol up + vol down + power).
Click to expand...
Click to collapse
lights wont flash. The only thing that flashes is the red LED. it flashes quickly, not slowly like it does when you put it for charging after its dead (no battery).
mr.5106411 said:
lights wont flash. The only thing that flashes is the red LED. it flashes quickly, not slowly like it does when you put it for charging after its dead (no battery).
Click to expand...
Click to collapse
you got warranty?
mr.5106411 said:
I tried all combinations, it wont go to boot loader, it wont do a simulated battery pull it wont re calibrate the chagring mechanism. (vol up + vol down + power).
Click to expand...
Click to collapse
Stay away from vol up + power. It will put the phone in QHSUSB_LOAD, which nothing good will come from.
You should not be trying "all combinations" just the right one for bootloader. Make sure you are holding vol down, the press power for 5 seconds or so (do the capacitive buttons flash at all if you do that?) release the power button, but do not release the vol down button until the hboot screen comes up. Or of course, you are convinced the phone is still not responsive.
Try this with the charger plugged in and unplugged.
Make sure you charge for several hours on the wall charger, not connected to your computer.
---------- Post added at 09:44 AM ---------- Previous post was at 09:40 AM ----------
cr1960 said:
you got warranty?
Click to expand...
Click to collapse
There have been some cases of the phone becoming suddenly unresponsive like this, apparently due to hardware failure. These reports seem to be getting a bit more common as the phone is getting a bit "older" (over a year).
However, since the OP was just futzing with it (restored a nandroid), I tend to believe its not a hardware failure. And that he can still possibly recover.
But that is just a gut feeling (and maybe being too optimistic).
redpoint73 said:
Stay away from vol up + power. It will put the phone in QHSUSB_LOAD, which nothing good will come from.
You should not be trying "all combinations" just the right one for bootloader. Make sure you are holding vol down, the press power for 5 seconds or so (do the capacitive buttons flash at all if you do that?) release the power button, but do not release the vol down button until the hboot screen comes up. Or of course, you are convinced the phone is still not responsive.
Try this with the charger plugged in and unplugged.
Make sure you charge for several hours on the wall charger, not connected to your computer.
---------- Post added at 09:44 AM ---------- Previous post was at 09:40 AM ----------
There have been some cases of the phone becoming suddenly unresponsive like this, apparently due to hardware failure. These reports seem to be getting a bit more common as the phone is getting a bit "older" (over a year).
However, since the OP was just futzing with it (restored a nandroid), I tend to believe its not a hardware failure. And that he can still possibly recover.
But that is just a gut feeling (and maybe being too optimistic).
Click to expand...
Click to collapse
I tired both of your suggestion but no hboot menu. and my warranty just ended last month. ( any other ideas?
Here is a video showing what happens. I appreciate the help BTW. http://www.youtube.com/watch?v=0lzm5PKlp-E&feature=youtu.be
This is going to be a long question/story thanks for your patience!
Whenever i try to reboot my phone, regardless of method, it takes an elaborate set of actions (elaborate as in it requires a power cord, a complex series of button presses, chanting, chicken blood, etc...) for the phone to turn back on.
I'm going to include a lot of details, relevant or not, i cannot decide.
I was using SlimBean Build 7 for weeks. I was able to reboot normally. I had heard about an app, WifiKill, installed it, caused short lived havoc at work, no issues so far. A few hours later, I attempted to tether my laptop using the hotspot function (something I've done many times before with no problem). The wifi turned off immediately and would not come back on. My exact thought was "Huh, that's weird" and attempted to reboot the phone, it seemed to shut off normally but did not come back on. At this point i believe the battery was at 60% or close to it.
No matter how I tried the phone would not power back on.
I charged the phone over night, and it actually came back on. Of course the first thing I tried to do was reboot the phone. Same result.
Now the phone is still not starting when turn off or rebooted with the power button command, it will not reboot when done with adb, it will not reboot when I try within the recovery. Any of these things cause the phone to act as if "hard bricked" with no response from any of the buttons or screen.
My first thought was to flash a stock rom with odin, when i plugged it into my PC (windows 7 ultimate 64bit) it asked for QHSUSB_DLOAD drivers. I tracked those down and installed them of course they did not work for odin.
I ordered but have not received a download mode jig.
I thought maybe it had to do with the act of charging the phone that sparked the brief show of life so i drained my battery using another phone and then charged it in the skyrocket for two days. Battery at 100% at this point.
At this point, I've discovered that if I hold the power button long enough while plugged in the phone will vibrate over and over until the button is released and by accident I learned that if i unplug the phone wile doing it's little vibro-trance it will start normally.
If I try to reboot the phone with any of the methods I listed above, I have to pull the battery, wait 10 minutes, plug in a power cord (not connected to a computer) hold the vol+ and vol- and power buttons, wait till it starts buzzing and insert the battery, if the charging icon appears the phone will power on, if not, I have to start again.
Once I learned that trick I was able to boot the phone into download mode and flashed back to stock JB and twrp.
I have since flashed slimbean build 8 and twrp 2.6.0.0. The phone is working fine but I don't have the guts to attempt WifiKill, tethering or reboot.
If you're still with me, good on you. I think the universe is mad at me for messing with people's wifi connection.
Anybody got any ideas?
THANK YOU!!!
ilike3point14 said:
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, I'm guessing that wifi kill app had something to do with it. I've tethered on slim bean 7 & 8, so I doubt it has anything to do with that or the ROM. Is say it's like you said, karma rearing its ugly head for playing wifi gatekeeper on unsuspecting individuals
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hey guys,
My phone shut off unexpectedly today and now won't turn back on. When I try to power it on I see the Google logo for a couple seconds and then it'll just shut off again. I tried holding the volume up/down buttons to access the bootloader, but right after I get to the screen it just restarts itself again.
Connecting to power (AC or USB) causes it to constantly reboot over and over, it just shows the Google logo for a couple seconds and then restarts again.
Any ideas on what I can do?
rosscarrothers said:
Hey guys,
My phone shut off unexpectedly today and now won't turn back on. When I try to power it on I see the Google logo for a couple seconds and then it'll just shut off again. I tried holding the volume up/down buttons to access the bootloader, but right after I get to the screen it just restarts itself again.
Connecting to power (AC or USB) causes it to constantly reboot over and over, it just shows the Google logo for a couple seconds and then restarts again.
Any ideas on what I can do?
Click to expand...
Click to collapse
Provide more information for a starter - stock? unlocked bootloader? rooted? third party recovery? rom and if yes which?
If it's stock I'd RMA it.
If not what did you do immediately before the problem started?
try holding the power button for > 2 seconds which should turn it off completely, leave it on a wall charger for at least a couple of hours then turn it back on - I doubt it'll fix the problem but it's a simple thing to try...
Clancy_s said:
Provide more information for a starter - stock? unlocked bootloader? rooted? third party recovery? rom and if yes which?
If it's stock I'd RMA it.
If not what did you do immediately before the problem started?
try holding the power button for > 2 seconds which should turn it off completely, leave it on a wall charger for at least a couple of hours then turn it back on - I doubt it'll fix the problem but it's a simple thing to try...
Click to expand...
Click to collapse
Everything on it is stock, no ROM, not rooted. I had just taken it out of my pocket to check the time, put it back in my pocket and then felt it vibrate, took it back out to see it at the Google logo and haven't been able to get it started since. There was one or two times when it got past the Google logo and started to show the start up animation (the four colours bouncing around or whatever it is) but then it shut off again.
I tried holding the power button to completely turn it off, but plugging it into the wall charger just causes it to repeatedly attempt to boot like I mentioned earlier. I'll leave it for a while and hope for the best
Sounds like the mobo is bad. Most likely will have to rma it.
rosscarrothers said:
Hey guys,
My phone shut off unexpectedly today and now won't turn back on. When I try to power it on I see the Google logo for a couple seconds and then it'll just shut off again. I tried holding the volume up/down buttons to access the bootloader, but right after I get to the screen it just restarts itself again.
Connecting to power (AC or USB) causes it to constantly reboot over and over, it just shows the Google logo for a couple seconds and then restarts again.
Any ideas on what I can do?
Click to expand...
Click to collapse
Do you have a case on? The case could be faulty.
Sent from my Nexus 5 using Tapatalk
jd1639 said:
Sounds like the mobo is bad. Most likely will have to rma it.
Click to expand...
Click to collapse
Maybe not. Sounds like a stuck power button to me.
OP does the phone just endlessly repeat this cycle? If so it's rebooting itself do to a stuck power button. One other users already reported similar issues and his power button was indeed stuck. Mash the power button hard for a minute to see if you can unstick it.
theesotericone said:
Maybe not. Sounds like a stuck power button to me.
OP does the phone just endlessly repeat this cycle? If so it's rebooting itself do to a stuck power button. One other users already reported similar issues and his power button was indeed stuck. Mash the power button hard for a minute to see if you can unstick it.
Click to expand...
Click to collapse
You got it!
Thanks so much, really wasn't looking forward to waiting for weeks while the RMA went through. The button didn't appear to be stuck - it was still clicky - but after mashing it for a minute it started up normally and appears to be fine now.
Did you flash any ROMs or anything previously?
Sent from my Nexus 5 using xda app-developers app
scottdouglasdick said:
Did you flash any ROMs or anything previously?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
brother the issue is gone, as mentioned "sticky power button" was causing it. read the thread before posting. btw thanks for effort anyway... haha
:laugh::silly:
Hi all. Sorry to reopen an old thread (but xda suggested I check here before making my own thread).
I think we have the exact same problem with a Nexus 5. Unfortunately, bashing the power button doesn't seem to be helping (and makes me feel slightly silly .
Anyone know how much effort it would be to take it apart to get to the part that's stuck? Any good instructions?
Thanks.
Weird, I have the same issue starting a few hours ago. I updated to the Oct 17 beta of Cataclysm then a hour later it happened. But was told it sounds like the power button issue.
Took it apart, tried to fix it. If plugged in I can get into the bootloader, but then it reboots again. I've tried tapping it on a hard surface, and it gets seems like it almost fixes it because it'll connect to my laptop but then reboots again.
Could it be the battery? It was fully charged but then died as I was deleting hundreds of photo's in Dropbox to move photo's over from my phone because it was full.
I too am running into this same issue. My screen cracked so I replaced the digitizer with some success. In the process I damaged the battery and needed to replace it. When I got the new battery and replaced it my phone is now unusable.
When unplugged: I turn on the phone and it's running the ANDROID animation then turns off.
When plugged in: I turn on the phone, the ANDROID animation runs then the phone restarts and continues the process over and over again.
I then flashed the phone with Marshmallow and the same thing happens. Except now that I flashed it I get the Android icon with the spinning gear. So; I flashed it back to 5.1.1, but the same result.
Could I have physically damaged something inside or is it a battery issue? Thanks for any insight.
Sorry if this has been covered, didn't see it when I did a search and found similar issues doing a google search but not the exact same one I'm having.
Sometimes when I try to restart my G3, it won't boot back up. I'd say 1 out of every 5 boots or reboots. I'll hold down the power button to restart the phone, click on restart, it will prompt me and I will click ok, then it will say it's restarting, then goes black and doesn't come back on. I have to pull the battery and usually the only way I can get it to come back is I have to hold down the power button and THEN insert the battery and then it will start booting up. Not a HUGE issue because I can take my case off in only a few seconds, but man if I had one of those huge extended battery cases that take like 10 minutes to put on and off, I'd be hatin' it
SPECS: D850, Lollipop, rooted.
Now I did not have this issue unrooted. This only happened after I rooted the phone. I used it for about 2 weeks unrooted. I'm sorry I don't recall the exact method I used to root it. So I can live with it but I'd just thought I'd ask and see if anyone has a solution or understanding why this is happening. Thanks for reading my post.
Yeah.. this is a weird issue.
Did you ever end up finding further information on this issue? I just rooted and installed TWRP yesterday and I am experiencing an identical problem. When it happens the screen is dark and power button unresponsive, in addition the LED does not light when plugged in. I can recover using one of three methods:
1: Unseat/reseat the battery once or twice (most times twice)
2: Plug into USB charger with no battery, wait for "?" screen and insert battery...then it powers up
3: Insert battery while holding down power button as you mentioned.
I rooted using this method (only method that would work) , and bump'd / installed TWRP using ImagprepGUI
i have this problem as well. Would like a permanent solution.
kvl19 said:
i have this problem as well. Would like a permanent solution.
Click to expand...
Click to collapse
Unfortunately the only permanent fix at this time is to reinstall stock recovery.
Got the exact same problem on my G3. Rooted and twrp installed. Any solution yet?
I have a similar issue. Mine reboots every time, but when I power down the phone overnight and try to turn it on the next morning, I have to take out the battery to get it to respond to the power button. I have held it for a full minute waiting for it to come on with no response. This has happened twice now. Not a big issue since it only happens when powering down the phone overnight. If I power it off then turn it back on immediately, the power button works perfectly. I bought the phone already rooted, updated twrp to 2.8.7.0 and installed jedi kernel and rom.