I have a HTC 10 (new old stock) that I have been using for 2 months, on stock Oreo.
Everything was fine until last week when suddenly in the middle of reading an email the screen froze, a few seconds later the screen went black and would not boot up. Nothing at all, not even with a hard reset VOL DOWN + POWER or VOL UP + VOL DOWN + POWER. Tried holding it for A LONG TIME like 5 minutes, no luck. The phone had a hard brick and that's it.
Occasionally, after a few hours, I would try to reset it just for the hack of it. Or connect it to a charger (no charging light) Eventually after about 20 hours, it booted up again after I held all three buttons for a few seconds. Then it worked like nothing has happened.
It kept running for several hours, I charged it up to 100%, ran down to about 80%, then the screen froze again and died. Same thing happened, won't boot up at all. But if I wait another day or so, kept trying, it will boot up again.
I know the HTC 10 is known for it's horrible battery drain issue, and I have experienced that myself with another HTC 10, this is not it. The battery is running fine on this one. This is something else.
After doing this for a few iterations, I was able to figure out a pattern.
When the screen froze and the phone dies, it will not boot up no matter what you do. But for some reason something is still going on as the battery is still being consumed, a day or so later, when the battery is completed depleted down to 0%, and as soon as it hits 0%, whatever causes it to not boot unlocks and allow it to boot again, as long as you have it on the charger, the charging light will come up at that time, and as soon as it gets a little bit of juice, it will boot up again normally. Except when it does boot up, the date is reset to December 31, 1969 7PM.
After testing this for two more iterations, I am reasonably sure this is what's going on. Then I did a factory reset.
Once it's factory reset, I did nothing except turned on WIFI and didn't do any further setup except surf the internet a bit on WIFI, and about 10 hours later, it died again. Now I know, if I leave it alone for 20 hours, then plug it in for a few minutes, it will boot up again.
So here are my questions.
(1) The phone appears to have bricked during the 20 hours that is was totally non-responsive. What is happening that's consuming the battery?
(2) Does this seem like a hardware issue or software issue?
Related
I've been running CM 10 on my phone without issue (besides the whole touchscreen thing that wasn't a big problem for me) for several months.
I went to cm10.1 last week and my phone started having graphical artifacts on occasion (like an overheating gfx card) and eventually started shutting off randomly and restarting with 50% less battery than it had. I did a full wipe and put back on CM10, but it's still doing it, and has gotten progressively worse.
For the past couple of days my phone would work for about an hour, and then shut off and either come back on with 50% less battery, or not at all until I plugged it in for several hours (even if it had just been plugged in all night). Now, my phone has been plugged in for 24 hours and I can't get it to turn on at all. I've held the power button for 30 seconds, held power+down, etc.
When it was on it's last legs I wanted to do S-OFF and then go to stock so I could do the warranty, but the S-OFF process hanged when trying to push the first file.
Any help?
Thanks
slash178 said:
I've been running CM 10 on my phone without issue (besides the whole touchscreen thing that wasn't a big problem for me) for several months.
I went to cm10.1 last week and my phone started having graphical artifacts on occasion (like an overheating gfx card) and eventually started shutting off randomly and restarting with 50% less battery than it had. I did a full wipe and put back on CM10, but it's still doing it, and has gotten progressively worse.
For the past couple of days my phone would work for about an hour, and then shut off and either come back on with 50% less battery, or not at all until I plugged it in for several hours (even if it had just been plugged in all night). Now, my phone has been plugged in for 24 hours and I can't get it to turn on at all. I've held the power button for 30 seconds, held power+down, etc.
When it was on it's last legs I wanted to do S-OFF and then go to stock so I could do the warranty, but the S-OFF process hanged when trying to push the first file.
Any help?
Thanks
Click to expand...
Click to collapse
If it won't power on, screen won't turn on, power led doesn't light up even when plugged in, it's bricked. Sounds like you've got some serious hardware issues.
My s3 started randomly rebooting so I flashed a new more stable Rom.I haven't used the phone since the m7 came out so figured things needed updating. Still kept getting random reboots. Now I have a bigger issue, if the battery dies or the phone is turned off then the phone will completely act dead, no lights when plugged in to any charger, no charge animation, nothing. It will not power on. I've tried every button combination known, nothing works It just will suddenly power on one random time when you hit the power button, could be minutes, hours, even days later.At first I thought it was totally dead. Took the battery out for a day then put it back in and bam booted up like nothing had happened. Well it does this every time it's powered off completely or the battery drains. However you can do a restart a hundred times and it boots fine. I thought maybe flashing firmware would solve it but it hasn't. I'm wondering if this is sds failure? Is there a fix for the Verizon version? I am out of warranty and Samsung wants to charge an arm and a leg for repair.
Things I've done: new oem battery, different roms, Odin firmware (rt66), tested power button.
Thanks!
A few days ago, my phone got pretty hot while I slept. But everything seemed fine until last night. I only bring up the heat because that's literally the only thing I can think of that might have caused this problem, even if there were a few days between that event and when the phone started behaving strangely.
Status:
Verizon SGS3. On CM11 nightly from about a week ago with the kernel it came with.
Issues:
I can't boot the phone. It'll quickly show the Cyanogen logo and then shut down again. Even if I'm on the charger, it'll just shut down. The battery will sometimes show 0% and charging, then I'll try it again a couple of minutes later and it'll show 87% and charging.
I did manage to boot the phone a couple times. It lasted long enough until I was able to get to the main screen. After a couple minutes, the power menu started flashing on and off showing the reboot/screenshot/power off menu. Like very quickly. Then the screen started turning on and off rapidly.
One of the times I managed to boot the phone, I was able to do a factory reset from settings. I reset it. The problem persists. I've tried two different batteries. Both batteries work fine in another SGS3 I have, but not in the one that's causing all the problems.
Any ideas?
Hi,
I have TMO Nexus 5, 2.5 yrs old. Suddenly, my phone shuts down with more than have battery charge remaining. I cannot do anything by pressing any buttons. it is dead. If I connect to the charger, phone goes on the loop. The google sign appears on the screen, then it goes dark in a second or 2, then sign appears again, and so on. I can access the bootloader menu but only for a second. Then the phone goes off again. I cannot even properly turn it off, even when press power/volume up/down keys together. It just will not shut off.
Happened a few times before, but I was able to revive it by charging 3-4 hours and eventually it stopped looping. This time, no luck. Between the episodes like this, it worked just fine. Stock, never rooted, latest android 6.01.
Bad battery or something else? I did order the battery and will try to swap it, but would like to know if this could be anything else.
Normally, I would try to simply remove the battery and then put it back, but this battery is a little trickier to remove. I do not want to do this until I decide the battery needs to be changed.
Thanks very much.
I've had this phone 3 years and it worked well. It's an unlocked ATT phone so no OTA updates other than the standard app updates. It's on Lollipop 5.1. Been working perfectly fine until yesterday, I was watching the CBS app, when the phone rebooted. Now it's stuck on a boot loop and initally went to optimizing apps which it rarely finishes but the times it does, the phone just powers off. It then got into another loop later last night where it'd get to the Kyocera logo then reboot over and over. I let it do that until the battery died 2.5 hours later. Then I kept attempting to boot until the batter was entirely drained to the point it wouldn't attempt to power up any more.(battery is not removable on this model). I've now charged it up, trying to enter recovery mode with power+volume down. That doesn't seem to register. Tried volume up+volume down+power with no effect. Now after charging, it will do the reboot loop mentioned earlier to the Kyocera logo. If I plug it into a charger, it will go to the optimizing apps portion and repeat the above. At the optimizing apps screen, if I unplug the charger, the phone powers off immediately. It appears to be holding a charge according to the charge indicator and the fact that I can try to boot over and over unplugged. Any suggestions? Phone wasn't dropped or damaged in anyway. Very weird what could have happened.
An update: Phone finally got past the "optimizing app" phase last night sitting on the charger. Out of no where the phone booted completely. However, it only works while plugged in. If I remove the charging cord, the phone shuts down after about 2 seconds. Booting without charging cord results in the same boot loop. I've considered the battery has failed however when plugging in the charger, battery shows 100% and it will decrease appropriately over time. I'm thinking there must be a hardware issues at this point. Somewhwere in the charging/power circuit. Any other suggestions?
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
djhurt1 said:
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
Click to expand...
Click to collapse
I have the same exact problem. It started the crazy booting process in my pocket, and I did all the same things you did. Factory reset didn't correct the problem, so I'm think the battery has had a stroke. Sine your problem and my problem are very close to the same time frame, our phones are also probably about the same age, and its a quality control issue. Not bad quality control, just that these batteries were designed to last X number of months or cycles, and probably they died. Too bad, because my E6560 is the very best cell phone I have ever owned. Built like a tank and thank God for that.