Related
Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c
Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.
Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?
Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck
This past week, I purchased a 2014 Note 10.1 off Craigslist. I did check it out before buying it, and the device is in pristine condition, including the screen. It booted fine, and I went partway through the setup (the guy had factory reset it) before closing the deal. It is the wifi-only model, 3G RAM, 8-core Exynos version. It's white if that matters.
Anyways, a while later when playing with it some more, completing setup, etc, it just died on me. I wasn't home, and didn't have a place to charge it until I got home, but just figured that despite the device having said the battery was 99% charged, the guy keeping it unused for a long time might have thrown off the battery calibration. My understanding is that a Li-ion battery has one or more cells, plus circuitry that protects against overcharging and undervoltage conditions, as well as tracking the current charge state. With lengthy non-usage, the circuitry's idea of the current charge can get out of sync with reality, so I figured a few charge-discharge cycles would get it back in shape.
However, the situation after I got home turned out to be a little more complex. If I plug in the device to a power source with enough current (like the charger it came with, or my 2.1A USB outlet by my bed), it will run just fine while plugged in. However, upon unplugging, it would die quickly. Naturally, I assumed the battery was probably shot, so resigned myself to spending $50 on one. This is where it started to get a little weird. It seemed that when I booted into either fastboot or Odin mode, it would stay on much longer than normal, while unplugged. I'm talking hours, rather than between several seconds and several minutes while booted into the OS proper.
This lead me to believe that perhaps it wasn't my battery itself, but rather a glitch in the OS that was causing it to shut down. When I say shut down, I mean an immediate full-off state, not a nice shutdown or one preceded by low battery warnings. It just clicks off like a light that's been turned off. However, trying several different firmwares, including a couple custom ones, has not yielded any improvement. The issue remains.
The device was stock 5.1.1 when I bought it. I tried flashing KitKat (various images downloaded from SamMobile), but for some reason, it would still say it was running 5.1.1. I tried xKat, as in this thread. That results in 4.4.2 with the associated customizations, but the shutdown issue remains. I tried CyanogenMod 13, as instructed here. It works fine, notwithstanding the same issue. In between the stock firmwares (pushed to the device with Odin) and the custom ones, I would do a full wipe through TWRP.
I've popped the back off, disconnected the battery, waited a bit, and reconnected it.
Now my question: does anyone have any idea what's going on? If it's a dying battery, then why does the device say it's got a nearly full charge, and why no low battery warnings? Why would Odin mode or recovery (TWRP now) seem to keep the device powered up so much longer? Sure, they draw less power, but hundreds of times less power? I doubt it. If it's some hardware issue with the chipset/motherboard/etc, then why does it only manifest when running on battery, or a low-current USB connection? If it's an issue with Android itself, then why does nobody else seem to have this issue (googling revealed nothing that matched my symptoms), and why did several different versions exhibit the exact same problem?
I really don't want to spend money on a new battery and wait a few weeks for shipping if there's something else I'm missing that could get my device functional for free and a lot faster.
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off. I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again. For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing. For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Sent from my SM-P600 using XDA Premium HD app
Thanks for your reply.
siralsmooth said:
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off.
Click to expand...
Click to collapse
That's a bit different from my issue. Even when the device reports full charge, if I unplug it, it usually dies within seconds, and always within 2-3 minutes.
siralsmooth said:
I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again.
Click to expand...
Click to collapse
I don't think that's going to make a difference for me. From what I was reading, all it does is delete the batterystats.bin file (hence the root requirement), which doesn't have anything to do with calibration for most devices. It just contains the stats for how much battery drain various things have caused, during this 'running on battery power' session. It's also reset every time the device is charged. Read here for more info.
Furthermore, even if this were not the case, I'd conclude that wiping the system partition (indeed, all partitions except recovery) would have cleared this data.
Still, that said, it's conceivable (though exceedingly unlikely) that some of these calibration apps might do something else, such as talk to the battery circuitry at a low level. Since I've got nothing to lose, I will probably give a few of them a shot. Do you happen to know which one it was that you tried?
siralsmooth said:
For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing.
Click to expand...
Click to collapse
In my case, the values seemed to track pretty closely, and with numerous freshly-flashed versions exhibiting the same issue, I'm pretty sure at this point it's not a software glitch. I've resigned myself to ordering a new battery. I just wish I was certain that it would fix the issue.
siralsmooth said:
For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Click to expand...
Click to collapse
My understanding is that the bootloader doesn't change with flashing. I might be wrong though; is there a way to check the version?
Just a heads up. I ordered a new battery, which arrived yesterday. It seems to have completely solved the issues I was having.
My guess is that Android itself monitors the battery more diligently, and takes a more conservative approach to preserving battery life by shutting down when the voltage drops too low, while recovery mode would just let it run down completely flat (not good for Li-ion cells).
It's a moot point now, because it all seems good.
Hi all,
I have been running my Z1 Compact on 4.4.4 for the longest time, mainly due to sound issues after updating to Lollipop.
Recently, the battery has been dropping randomly from 60 odd percent to 3 or 4 and then shutting down all within a few seconds. The last time it did this, I tried charging it when I got home but the charging light would not stay on, thus it was not charging. All typical signs of battery failure due to age.
Having already replaced the battery successfully on my Z1, I bought a replacement original Sony battery and replaced it. The problem persisted. On first boot, the phone got to the blue waves then black screen, and power off. Charging screen just showed the battery at about 40%.
I risked it and flashed the latest software with Flashtool, having done a complete wipe. The result of this proved no better, but I did get a different message on the charging screen, a message saying the phone had shut down due to overheating. Picture is attached.
The phone is in no way overheating and I've even booted it while sat on a shelf in the fridge to help dissipate any heat generated but with no luck.
So, the old battery maybe did overheat and caused the phone to shut down, I'll accept that as a probability. It may have even damaged something, but I don't think that's likely.
After changing the battery, I would have expected the problem to resolve itself, but it seems like some kind of hardware 'flag' has been raised that is now not allowing the phone to boot in case it overheats again.
Does anyone know of any way to resolve this, reset the 'flag' per se, other than going to Sony? The phone is definitely out of warranty due to its age, never mind me taking the back off lol
It is a shame because it has been a great phone over the years, and I would like to fix it if possible, even if to give it to one of the grandkids. I have my Z3 still (which I won't part with for anything) and I have an XZ too and both are great phones. I would just like to save the XZ1c if I can.
The phone is not, and has never been modified in any way, no rooting, no bootloader unlocking. Only stock roms have ever been flashed, and then only once or twice, to put it back on 4.4.4.
I have tried reflashing just the kernel, or just the system too, to no avail.
In desperation I even left it in the fridge for a few hours in case the temperature sensor was on the fritz, but that did nothing at all.
I just feel like there's nothing actually wrong with the phone, apart from this trigger that won't reset.
Any help greatly appreciated of course.
Thanks,
Mick
Maybe theres lot of consideration:
1. Rom Bugs
2. The Kernel not supported well
3. Battery Issues (But you already change it right)
There are two temperature sensors afaikin our phone. One in the SOC and another one in the battery (hence three pins).
The battery is probably the one giving the high temp report. Try yet another battery.
A bad battery normally heats up very fast inside and the battery temp sensor stops the battery from charging and/or working to protect the phone and the battery.
I changed my battery before when it had symptoms like yours 100-90-0 drop and after replacing with a battery from eBay it was OK. I gave it a full charge then complete discharge and then complete charge to full cycle the battery once and let the phone Guage its full capacity. one year later now my battery is acting funny again (not charging past 30%) and getting so hot when charging it triggers overheat control service in Android.
Any luck?
Apologies for the necro. But did you ever fix this issue, having the same problem
Karter Ires said:
Apologies for the necro. But did you ever fix this issue, having the same problem
Click to expand...
Click to collapse
No, I never did figure it out. I've been loathe to spend more money on another battery when I've got other much newer phones. I really have no idea why it would not reset once the battery was replaced, maybe it's the replacement battery.
Have you tried changing the battery?
I've tried flashing different stock roms, Kit Kat, Lollipop, and it doesn't help.
Short of going to Sony, I'm not sure what else to do.
Hello, I'm new to the forum and I may need your help for a problem I've had today. I've been an happy owner of a Nexus 5X until this morning, when I was regularly using it while on charge and at one point it freezed for a few seconds with the screen still on. I pushed the standby button, the screen went off and from then on it was completely bricked. No signs of life, nor access to recovery mode via bootloader. Nothing. Already tried all the possible physical buttons combos, nothing.
It was on Android 8.1 (beta, very happy about that by the way), no root and with locked bootloader. I did some flashing experiments one year ago but in the end I reverted it back to totally stock and I haven't had issues ever since. Never had bootloops or similar problems, it just happened all of a sudden.
Hope to receive your help, by the way it should still be under warranty, so let's see...
Thanks for your help.
Same problem heare. I tried to install the factory image but now, the phone is completely death.
I beleve thet it was a android 8.1 issue because it was not a bootloop problem.
Same problem heare. 8.1 need a reboot but now, the phone is completely death
It might be an 8.1 issue then. By the way, being under warranty I sent it to customer assistance. I've had some signals of life before this morning though. The LED was flashing red indicating very low battery. I connected it to the charger and followed the instructions by Google themselves:
"If you see a red light, your battery is fully discharged. If the red light is flashing, there isn't enough power to turn on. Charge your phone for at least 30 minutes before restarting".
This seemed to resemble my case, so I waited for about 40 minutes (by that time the charging battery icon did show up with the phone still off) and tried to turn on. The only thing that I got has been the Google logo before the boot animation for a few seconds. Then the screen has gone off again and back to death.
From your comments it seems it might be an 8.1 related issue. Watching videos on Youtube about 5Xes with similar behaviours I was actually thinking about a motherboard failure, or a battery failure (the latter is more unlikely though). Disassembling and heating up the motherboard providing a temperature shock seemed to be a decent temporary solution to bring it back to life. I have warranty though so I sent it to assistance, we'll see... I'll probably unenroll my phone from the beta program just to stay safe.
Thanks for your answers.
My nexus 5x had same issue. A few weeks after 8.1, it totally bricked. I was able to get bootloader on once, but it was locked and fastboot didn't see it. Then after i let it discharge, I haven't been able to get it to recharge or get to boot screen at all. I bought another nexus 5x, but bit worried that 8.1 will kill it.
So, I bought my HTC 10 sometime last week and I love it, I got the red 2PS6500 version. I have been excited to see people like Leedroid and Faygi working to make this phone so amazing. But I always had a rough battery experience.
At first, symptom was fast draining. It rarely got 3-4hrs SoT, but some days I had good battery life. More recently, I noticed that when using my camera around the 20-30% range, the phone would shut down, and I'd see that it was at 0%-1% and not booting.....
From my research here, this seems like I could try to re-calibrate my battery. I had it charge (powered off) for 2 minutes, then I held both volume buttons + power while still charging. I then let it go up to 100%. When I turned it on, the percent showed 70%. So while it was on, I let it go to 100%. After that, I unplugged it, and rebooted it. It went down to 70% again. I repeated the full charge to reboot. This time, I was 99%. I wanted to reboot once more, just to close the gap from 99% and 100%. USB connection is clean and good, cable works on other phones.
Then the phone just stopped working. It no longer boots up, no LED's, no vibration, buttons don't function no matter the combination. I tried connecting it to my PC and I get nothing recognized. Cannot get the screen on at all.
So I am guessing two things:
(1) Battery might have fired and the connection to the board is gone. I might have bought one that already had issues and this was the last leg of it.
(2) Motherboard damage from the battery? This is something I'm afraid of if I go and replace the battery and I still have issues with it not turning on.
I was hoping anyone with experience might be able to confirm anything I mentioned with the battery issue, and if replacing it solved that.
TL;DR, HTC 10 no longer powers on, shows no sign of life. Battery previously had calibration issues. Should I replace the battery, and then it will turn on, or could there be further damage. Most situations I found were from users that were still able to turn on their HTC 10.
I've replaced my battery recently. I had the same deal. I had to use the actual charger plugged in for a while and it eventually came on
Yayodroid said:
I've replaced my battery recently. I had the same deal. I had to use the actual charger plugged in for a while and it eventually came on
Click to expand...
Click to collapse
Thank you for responding. My issue/question was more about "if" i replace the battery, will it solve my issue. I have not replaced it yet, and I ordered an OEM battery in hopes that should fix my issue. So hopefully a new battery will allow me to boot up my HTC 10 again.
At least I still have my HTC m8, and I'm replacing it's battery too (swelling and making the screen bulge). The community around the M8 is still strong and there is even the latest RR pie available too.
I gotcha. Sorry I have a terrible habit of skimming and then assuming. Mine was similar but not exact. I was always able to get it to show life after it was on charge for a while.
When I replaced the screen once, i forgot to unplug the battery from the board before I started. I got it all back together and it wouldn't turn on. It wouldn't show that it was charging. So I went in and unplugged the battery and plugged it back in. It acted after like it never happened.
Yayodroid said:
I gotcha. Sorry I have a terrible habit of skimming and then assuming. Mine was similar but not exact. I was always able to get it to show life after it was on charge for a while.
When I replaced the screen once, i forgot to unplug the battery from the board before I started. I got it all back together and it wouldn't turn on. It wouldn't show that it was charging. So I went in and unplugged the battery and plugged it back in. It acted after like it never happened.
Click to expand...
Click to collapse
I hope after I replace the battery, it finally boots up. I had to order a new heat blower because mine broke. I'm surprised after I charged it to 100%, it hard bricked and died. I have a feeling th battery was the culprit, since it was always bad at holding a charge....and even more oddly enough, using RR pie on my HTC M8 is FASTER than it was using RR pie on the HTC 10. That battery was very likely affecting my overall experience.
Please do update us with your progress and conclusion. It might help the next person
Yayodroid said:
Please do update us with your progress and conclusion. It might help the next person
Click to expand...
Click to collapse
DEFINITELY. I hope nobody has the issue I am facing at the moment.
UPDATE
So I replaced the battery, was very easy to do with patience and the right tools.
AND, it did not fix my issue. As I opened the phone, I noticed stickers on the chips from a company that apparently did work on it prior to me buying it, and the work they did was bad. I think it is safe to say that the motherboard has suffered severe EDP damage, and it would not be worth the cost to fix it. Burnt pins near almost every chip.... It was so happy being a part of this awesome group, working on the HTC 10 and having Fagyi making the amazing Pie roms. I will be selling my HTC 10 for parts on Ebay if anyone is interested (1 new battery, 1 lcd screen in excellent condition, both cameras, charging ports. . . basically everything but the motherboard that is dead)
So, I am torn between three options. Since my HTC m8 is fixed (top third inch of touchscreen no longer works with tough), I can keep the HTC m8 until it dies and replace it's digitizer/LCD. I can buy another HTC 10 and hope it will not be a crappy one, or I can save and get the HTC u11 (that red color looks so nice!) or go for a Samsung Note 4. I've had the M8 for about 5 years now and it's running RR-P like a brand new phone. I am so sad my 10 just died like that. I was so spoiled with the HTC 10, it was the best phone I ever had. I'd love to have a new device with tons of potential for modding in the future.
Any recommendations then: any device will be modded like crazy, especially with RR or LOS
- keep M8 / replace LCD+Digitizer
- buy HTC 10
- buy HTC U11
- buy Note 4