Related
Hi all. I have years of rooting under my belt but this is the first Samsung phone i've owned and I've got quite an issue. I was playing a game and the phone just shut off on me. I went to restart it and nothing. Did a battery pull, i felt it vibrate like it was trying to turn on and still nothing. So I tried to boot into cwm using volume up/down and power and the Samsung splash screen flashes for a split second and then shuts off and the phone just vibrates like it's going to turn on but won't do it.
So I tried battery pulls, holding power down, and now when I plug it into the computer it vibrates every two seconds but won't turn on. What's the deal this seems like a major hardware malfunction and Odin/CWM none of that stuff is usable because it just won't boot into anything.
So last resort do you guys have any suggestions i'm all ears :-(
I've had this a few times before... I forget which one exactly but either vol up + power button...or vol down + power button gets you to download mode and then you can flash the softbrick fix.
or if you do manage to get to CWM, you'll need some quick fingers to get to the "install zip" option before it reboots. once in there you're good to flash your ROM.
or, get a USB jig to get to download mode and flash soft brick fix.
Sent from my SAMSUNG-SGH-I727 using XDA App
NO dload mode either? if not make sure you have charged battery and than try to get into dload mode.
2leaponover1 said:
Hi all. I have years of rooting under my belt but this is the first Samsung phone i've owned and I've got quite an issue. I was playing a game and the phone just shut off on me. I went to restart it and nothing. Did a battery pull, i felt it vibrate like it was trying to turn on and still nothing. So I tried to boot into cwm using volume up/down and power and the Samsung splash screen flashes for a split second and then shuts off and the phone just vibrates like it's going to turn on but won't do it.
So I tried battery pulls, holding power down, and now when I plug it into the computer it vibrates every two seconds but won't turn on. What's the deal this seems like a major hardware malfunction and Odin/CWM none of that stuff is usable because it just won't boot into anything.
So last resort do you guys have any suggestions i'm all ears :-(
Click to expand...
Click to collapse
False alarm, apparently there is a battery bug reported on other forums. My phone had read 100% for quite awhile and I was digging the battery life but apparently i was over zealous. The meter was reading 100% but the battery was draining and the phone died. It wouldn't fire up until i left it on the charger for awhile. Very odd, guess I will delete this post and research this battery issue... unless someone else knows more about it
I have the same battery issue, but only when I use my car charger. When I take it off the car charger, it will read 100% till I reboot. Only after reboot will it start reading the battery state correctly. I DO NOT have this issue with the house charger...... Strange.
you guys after charging for 100% go to cwm and format battery status this will probably resolve ur issue.
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
Hello.
I have searched the forums about my issue, and although there are a lot of threads about phones rebooting, there was none about such exact problem as I am experiencing. I apologize if I missed a thread which tackled this problem.
Symptoms:
1. my galaxy S 4G reboots about every 3 seconds: it only gets to the very first "Samsung Galaxy S 4G T-mobile" logo, and reboot
2. it is possible to access boot menu (volume up+down), but only for a split second, and phone reboots again
3. rebooting starts as soon as in put battery in, no need to even press the power button
All that started by itself yesterday. I thought it was a mechanical fault with power switch, I opened the phone, unscrewed covers, cleaned everything, but found no mechanical issue. I switched batteries, tried starting the phone of plugged-in charger, on usb cable, took out sd card, sim card, put a different sim card in... and nothing helped.
Phone runs on Gingerbread 2.3, stock by T-mobile, never had any other roms on it. Device is rooted.
If anyone has an idea how to approach this issue, please let me know. Or reply with a link to somewhere I can read more. I was not able to find much on this...
Thank you!
Malarz
The phone sometimes does a reboot loop if u take the battery out of the phone without turning the power off. Just keep trying to turn it on, and eventually it would reboot properly. Take the battery out of the phone for a few minutes, put it back and try to turn it on again. Do this a few times to see if it boot back properly.
Hit the thanks button if it helps. It's my motivator to be more helpful.
gizmoscoop said:
The phone sometimes does a reboot loop if u take the battery out of the phone without turning the power off. Just keep trying to turn it on, and eventually it would reboot properly. Take the battery out of the phone for a few minutes, put it back and try to turn it on again. Do this a few times to see if it boot back properly.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Click to expand...
Click to collapse
Thank you for a prompt reply!
I did take out battery for a long time, well over one hour, and took out sim card and sd card as well. Unfortunately reboot loop started immediately when I placed battery back in the phone. That's what made me think it was a mechanical issue with power button.
I will try keeping battery out a few times again today.
One other thing: the phone had been in hot and humid environment for about 30 minutes before this happened. Not the first time for this phone to experience high humidity, though. However, I did not find any moisture inside the unit.
Malarz
I had this happened to my phone. Just wait it out and keep trying to reboot, it will come around. Take the battery out and put it back on. Keep on repeating this step.
Also, when the phone is on, try to hold the volume - + and power button at the same time to see if u can get into boot mode.
Also u can use hair blow dryer to blow dry area around the power button.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Or, batt is dead...
You have a stuck power button. Take apart the phone and clean the power bottom with compressed air. Then rapidly push the button in and out for a while.
Resolution:
I took the phone apart, and checked the power button (which had been my first guess), and was seemingly all right.
The battery was also not the issue, as I tried 3 different batteries.
Having no other choice, I put the battery back in, and let the phone happily reboot at its own leisure. After over 20 reboots, the system came on. Then a few minutes later the device rebooted again, and the loop started all over. After a while it booted up again. This time I did not wait for the device to reboot by itself, and I switched the phone off with power button, and then turned back on, and it booted normally. Repeated this once more - normal boot again. One more power off, and I entered the boot menu and did factory reset. Once the stock reinstalled, everything would work perfectly - no more issues with boot loop.
So it seems to me as a software problem more than anything else.
Side note: for the last several weeks the phone displayed strange behavior, that is the screen would light up for no reason by itself, and quickly go off. Sometimes it happened once every few minutes, sometimes it happened several times a minute. Did it have anything to do with the boot loop? No idea. But it strengthens my hunch about a software issue, as that behavior also went away after factory reset.
Sorry for the lengthy post, but since I have not found a similar case anywhere in the forums, I though someone might find this interesting. I do not deal with phones except as a user, but some of you guys do it maybe professionally, so maybe this will be a curious puzzle for you to solve.
Malarz
It sounds like Gremlins....
Sent from my Amazon Kindle Fire using xda app-developers app
Do you have notifications set up? It could notify that u have incoming messages such as a text or an email.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Malarz said:
Resolution:
I took the phone apart, and checked the power button (which had been my first guess), and was seemingly all right.
The battery was also not the issue, as I tried 3 different batteries.
Having no other choice, I put the battery back in, and let the phone happily reboot at its own leisure. After over 20 reboots, the system came on. Then a few minutes later the device rebooted again, and the loop started all over. After a while it booted up again. This time I did not wait for the device to reboot by itself, and I switched the phone off with power button, and then turned back on, and it booted normally. Repeated this once more - normal boot again. One more power off, and I entered the boot menu and did factory reset. Once the stock reinstalled, everything would work perfectly - no more issues with boot loop.
So it seems to me as a software problem more than anything else.
Side note: for the last several weeks the phone displayed strange behavior, that is the screen would light up for no reason by itself, and quickly go off. Sometimes it happened once every few minutes, sometimes it happened several times a minute. Did it have anything to do with the boot loop? No idea. But it strengthens my hunch about a software issue, as that behavior also went away after factory reset.
Sorry for the lengthy post, but since I have not found a similar case anywhere in the forums, I though someone might find this interesting. I do not deal with phones except as a user, but some of you guys do it maybe professionally, so maybe this will be a curious puzzle for you to solve.
Malarz
Click to expand...
Click to collapse
Hardware not software. You had a stuck power button. By forcing the reboot with the power button you unstuck it. If you don't believe it research Occam's razor. Glad you got it fixed(unstuck) though.:victory:
EDIT: Here are some other people who have had the same issue on samsung phones.
Stuck power button
Stuck power button
Stuck power button
If you need any more let me know. lol
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.
Hey y'all this is my friends phone and he messed up. He was always having battery issues where it wouldn't take a charge and was constantly fighting with it over something. He thinks the phone is cursed. Here's what went down at the end;
Friend was flashing stock firmware to phone. Phone was stuck on one of the flash spots, not sure if BL, AP, CSC, etc as I was not there. Because it didn't appear to do anything and he didn't know to wait it out, he rebooted phone in the middle of flash. Now the phone is completely unresponsive! Plug it in, no response. Hold any buttons, no response. Changed battery, no response.
At my wits end with this phone Anyone have anything or any advice that will help save this phone? Mint condition, would hate to have to write it off.
You sure the battery has enough charge to power on? If you say the battery wouldn't take a charge originally
Holding: Power - Home - Volume Down until the device reboots a 2nd time sometimes gets them back into download mode
A bad ROM flash should not prevent the phone powering up, that sounds more like the original power issue
*Detection* said:
You sure the battery has enough charge to power on? If you say the battery wouldn't take a charge originally
Holding: Power - Home - Volume Down until the device reboots a 2nd time sometimes gets them back into download mode
A bad ROM flash should not prevent the phone powering up, that sounds more like the original power issue
Click to expand...
Click to collapse
Holding those buttons does nothing. Even when plugged into USB. I have tried multiple cables. I even installed new battery for s7 and nothing. Screen remains dead and phone has no image or vibration response. It just stopped working after his failed flash.