Related
I searched here and google and found various charging issues but none quite like what I am seeing. The night before last, I plugged my A100 in before bed like I normally do and saw the power light turn orange. In the morning, I unplugged it without even looking at the LED because I just expected it to have charged completely. When I got to my car and turned it on, it was at 32%. I thought maybe I had something running that was eating battery or I didn't plug it in all the way overnight so it didn't charge. I plugged it into the car charger and went to work. When I got to work it was still at 32% but I didn't use it the whole time so I thought that was odd. I pretty much didn't use it the whole day since I knew it was low on power and I didn't have a charger at work. I got home and saw that it was at 28% so I plugged it in. About an hour later, I checked and it was still at 28%. Thinking that was odd, I turned it off and left it charging with it off for an hour. Turned it back on an hour later and still at 28%. I spent a little time using it while plugged in trying to kill off apps and things but it drained to 18% even though it was plugged in, the power LED showed orange, and the battery icon on screen showed charging (lighting bolt). At this point I started to worry that something was seriously wrong. I turned it *off* and left it plugged in all night after checking to make sure the LED was orange. In the morning, the LED had turned off completely (not blue or orange). I turned it on and saw that it was still at 18% even after charging all night turned off. I unplugged and replugged and the LED came on orange again.
So here is where it gets really strange.. I decide to go through RMA process since I'm still under warranty. I don't want my private data on it when sending it to them so I do a wipe. On a whim, I plug it back in after the wipe and guess what? It's charging! What the heck?!?! I had thought maybe I installed something that was causing problems but since it wasn't charging even when turned off, I figured it couldn't be an app. Can an application cause the device not to charge even in the off state? I thought maybe my battery stats had gotten corrupted so the percentage readout wasn't accurate but right after wiping the data, the battery was reading 18% just as before the wipe.
Any thoughts? Anyone ever see anything similar? My gut says to RMA it still.
Reboot the device.
It's a bug that happened to me on Honeycomb all the time with A100. (No longer happens on ICS)
Did you actually read the OP?
Sent from my Acer Iconia Tab A100 using Tapatalk
Yes, multiple reboots didn't help. No charging even when off. Started charging after wipe. Very odd.
So, after my wipe, I set out to see if I could get it to fail again. I loaded a couple of apps that I had loaded a couple of days before this happened and it stopped charging again. Unloaded each of those apps and still no charging. Did another wipe and still no charging. Conclusion is it's busted and just randomly charges on occasion. Sending it in for RMA today. Still very odd that it was reliably charging after that first wipe.
I myself am experiencing exactally the same problem. Any fix found?
Sent from my A100 using xda premium
Similar thing happened to me. The only thing is I didn't realize it wasn't charging until it was too late and the battery was at 5%. After it shut off, the only way i could get it to turn on was by holding down the power button and plugging in the charger. It didn't get to try a data wipe (didn't have enough time lol). I sent it back and they replaced the system board. Said it was not recognizing the battery properly.
I own two tabs, and one had this issue, the fix is actually quite simple. Let the tab die. No battery life at all. Then, when your sure its dead, plug it back in, and let it charge to full. I haven't had the issue on the tab since.
Sent from my Bad-Ass Acer Iconia Tab a100
Ciao. Same problem: my a100 only power on when plugged on charger.
i'm using a cooked ics with ulocked bootloader and i tried wipe, new installation, varius reboot, etc... and nothing heeelp!
thnx
flskio said:
Ciao. Same problem: my a100 only power on when plugged on charger.
i'm using a cooked ics with ulocked bootloader and i tried wipe, new installation, varius reboot, etc... and nothing heeelp!
thnx
Click to expand...
Click to collapse
Blow in the charge hole (in the tab) and try again, i had a similar problem, my charge was stuck into 3%, i tried that and worked for me : )
Enviado desde mi A500 usando XDA Premium HD app
luisxd said:
Blow in the charge hole (in the tab) and try again, i had a similar problem, my charge was stuck into 3%, i tried that and worked for me : )
Click to expand...
Click to collapse
my charge is on 3% too, but no good luck for me. seems a most serius problem
thanks.
any news guys? I bought a old ACER A100 and only power on while it plug in, so I went ahead and changed the battary, it still does not get charge.
Is the happening on complete stock? Or a custom ROM, if so, which one.
Also, reflash said ROM if applicable, and make sure the data is wiped.
I like the drain the battery idea, although its risky, these tabs can brick if it gets below 10%, current/voltage act weird when its low and blow a breaker inside and keep it from turning on.
Sent from my A100 using Tapatalk 2
What percent does it show the battery at while it's on?
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
My tab has the charging issue, but it is self inflicted. It was dropped, which cracked the lcd screen. I ordered one after a week or so and replaced it. At this point is when the charging issue cropped up. It powers on only if plugged in, and will get to 3% charge no matter how long it is plugged in. It will also only show the 3% if the charger is unplugged. It will then run for a few minutes until the battery dies. Also, the orange charge blinks about one minute after the charger is plugged in.
I found a reference on the web that if the battery charge gets too low the A100 can't charge it. I also found references that people had this problem, and Acer replaced the mb. I took a shot on the battery since it was a lot cheaper. Still the same. That doesn't the battery was not the issue since it was an ebay battery. So for now I just use it in the living room, plugged into outlet. Works good for that.
Jim
Ha! Found my own post by doing google query. Wow, didn't know this thread was still somewhat alive. So, I sent mine back as I mentioned in my last post back in February and they took a week and sent it back to me completely untouched. Basically said it was fixed but the same problem existed. I sent it in after a wipe but I did configure my wifi access point before I sent. When I got it back, my access point connected immediately and it still would not charge. I called them right back furious and demanded they provide shipping back to them because they clearly did nothing. They finally agreed and I shipped it back. After another two weeks of transit and repair time, I got my tablet back and this time it appeared to be fixed.
So, flash forward to 3 weeks ago. One morning I woke up and the tablet wouldn't power on. Black screen but the home "button" would light up when touched and power button would light up when plugged in and such. After several attempts to reset by holding down power button and using the recessed reset button, it was still not responsive. Tried up volume (and down volume) while powering pressing power button.. tried holding down reset button while pressing power button.. all with no result. Submitted rma request and was immediately granted without review. Sent it in and after about two weeks, got it back and it appeared to be working fine. Just this past weekend (about a week after I got the tablet back), I noticed that it was 3% after sitting on the charger for 2 days straight over thanksgiving. ARG!! Looks like another round of RMA here. I have not tried wiping but last time the charging issue happened, it was intermittent for about 2-3 weeks getting worse and worse before finally never charging. I am now near the end of my warranty period and I worry that if I send it back now, they will just turn it around and say it started charging after a wipe. What a piece of ... this is? This will be the 4th times in one year of ownership. I've almost spent the difference in cost between this tablet and other more expensive options in time and shipping alone.
I will try wiping it and then running it all the way down. Although I almost want it to fail hard right now so I can get it RMA'd before my warranty is up.
Howdy, guys.
I've got my One rooted, unlocked, and was running a CM10.2 nightly build. Everything was working fine until yesterday, when my battery started to rapidly discharge. I woke up with 100% battery, and after about 15 minutes of playing music it was down to 30%. I recharged it and started noticing rapid battery loss, about 10% per 15 minutes when the phone was idle.
Worried that this had to do with my ROM, I flashed the Eclipse Google Play Edition v1.2 ROM. However, the drain issue continued. I decided to let the phone fully discharge, then try powering it up again.
When it was fully discharged, I tried plugging in the phone. No LED came on and I couldn't turn the phone on. I've let it sit for over 2 hours now with the same result.
Some posts with similar symptoms have mentioned plugging the phone into a Windows PC and experiencing the "USB device plugged in" sound alert. I am not having any such luck, and what I currently have is a very aesthetically pleasing paperweight with no function whatsoever.
Has anyone else experienced a similar issue, or found a fix?
none
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Last Sunday, listening to music with HTC One (bought on Sep 11) on the charger, it suddenly went dark. Would not reboot, no charge light either. Went to a VZW store, they're shipping me a warranty replacement.
I wonder whether my habit of leaving it charger-connected whenever it's sitting on my desk (i.e., way beyond the fully-charged point) somehow stressed the battery (or the charging circuitry) -- though that habit never impacted my two previous HTC models.
When you hold Vol+Down and Power do your home and back arrows blink? If so, point the phone sensors (the two on the front on the left hand side) into a bright light. Then hold down Vol+Down and Power. It should boot. I'm not sure why. But it worked for me today after installing a custom recovery. -shrugs-
musicman625 said:
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Click to expand...
Click to collapse
I've got a replacement being shipped to me, and I'll send them the old one when it comes in. Currently using an old Samsung Stratosphere as a replacement, I was just hoping there'd be an easier fix or something simple. Thanks, though!
I've been away from the Xperia S forums for about 4 months now, since my Xperia S died. I've been using a Samsung Galaxy S II, but i'm pretty tired of it, don't like amoled screens, battery issues, constant reboots, radio problems and it goes on and on.. SO I want to try to revive my Xperia S.. Here is what happened:
4 Months ago, I had just finished flasing a Paranoid Android ROM (4.4.2 KK) and was setting up the phone, had just finished installing some apps and was testing some CPU Governors, I/O Schedulers and things like that, running AnTuTu and Quadrant benchmarks. In the middle of an AnTuTu bench, the phone just shut down (with about 50% battery left) and woudn't turn on again. When connecting the charger, the LED woudn't light up, the phone wouldn't vibrate, Vol Up + Power wasn't working, coudn't enter recovery/download modes. Hard bricked. So I opened up the phone and removed the battery, tryed plugging in again and nothing, so I left the battery outside the phone for a couple of days. After that, I made a quick "short circuit" with the batter, about 1/2 seconds, and plugged it back in, connected the charger and the phone came back to life. Now I could enter fastboot mode, so I re-flashed the stock .96 using Flash Tool, re-rooted, and re-flashed a newer build of Paranoid Android and everything was working fine again. I managed to backup all my photos and documents, and left the phone charging overnight while downloading some apps from the Play Store. When I woke up: dead again, but this time it's different. When I connect the charger the RED LED lights up, but it turns off after a couple of minutes. The rest is exactly the same: can't enter recovery, can't boot, can't fastboot, Vol Up + Power isn't working.. So I took off the battery and tryed a short circuit again, but this time nothing happend.. The first time the the cables heated up quickly and this time nothing happened. So I don't know what exactly is going on. Is the battery completely dead (2 years old phone)? Or is my device unable, somehow, to charge the battery? If there is no charge at all, the short circuit won't work.
Anyone with any experience or any guess? I'm searching for a new battery so I can test it but it's kind of expesive here, about 60USD. I can't stand the SGS2 anylonger, and I'm not buying any phone until the Snapdragon 810 shows up.
I'm having a similar problem: After installing uCyan everything except the battery drain (irrational jumps in the curve) seemed to work. Then at some point the phone died and now is in a charging (red light, some minutes), bootup loop. Sometimes it reached the sys to then instantly die again. I was able to get into TWRP when I fortunately saw the next bootup. But the battery is too low to get stock or any other recovery back. So everything seems broken. I have tried with two USB cables. The phone/battery is over 2 years old.
If any further actions could help, please let me know. Would also love to revive this phone.
ChriMo said:
I'm having a similar problem: After installing uCyan everything except the battery drain (irrational jumps in the curve) seemed to work. Then at some point the phone died and now is in a charging (red light, some minutes), bootup loop. Sometimes it reached the sys to then instantly die again. I was able to get into TWRP when I fortunately saw the next bootup. But the battery is too low to get stock or any other recovery back. So everything seems broken. I have tried with two USB cables. The phone/battery is over 2 years old.
If any further actions could help, please let me know. Would also love to revive this phone.
Click to expand...
Click to collapse
try the rubber band trick from here.
Ok I will try rubber band trick then. I think I already did it two times. I would have liked to avoid flashing the stock.ftf back and then doing again the unlocking, rooting and custom ROM flashing.
ChriMo said:
Ok I will try rubber band trick then. I think I already did it two times. I would have liked to avoid flashing the stock.ftf back and then doing again the unlocking, rooting and custom ROM flashing.
Click to expand...
Click to collapse
I thought You hadn't done that. You don't need to unlock bootloader again even if You flash stock ftf. And if You intent to flash a Kitkat or Lollipop based ROM, then You can simply skip rooting and all and follow the method from here.
Hello!
First of all - yes, I am completely aware that there are MANY similar threads, I've spent almost 3 hours now finding solution, no luck. I hope some good soul out there will be able to shed some light on my case So here it is:
Today, I was caught in a bad moment with low battery, and the phone discharged completely and turned off. I've connected it to the charger just about 5 mins later max, but the blinking LED of death got me there I have it on a charger for about 4-5 hours now (original HTC charger, of course tried both, the wall and the usb), the LED is still blinking, phone is cold (it's getting quite hot when it's charging normally), no reaction whatsoever, can't even enter any fastboot or recovery or anything. I've tried every possible combinations I have found, vol+ & power, vol- & power, both volumes & power, long, short, nothing helps. Now what's different than any other threads out there? The phone was NEVER rooted, I didn't unlock bootloader, flash, nothing. It was as stock as it could be since I had motherboard replaced (2 years ago, on warranty in HTC service). Now the warranty has ended, so I'm really hesitating to send it there, as it's propably gonna end up with new motherboard again, no matter what the problem really is (I live in Poland, and that's just a common "fix" no matter what the problem is). Current motherboard is the one with CID B25 (the one that never got any update, so it's stuck on Kitkat for 2 years now). Everything was working completely fine just a few hours ago, nothing indicated any battery problems, it just discharged, and now I can't get it to work.
Does anyone have any helpful ideas?
Thanks in advance
@edit
Forgot to add it's a single sim version, model OPFJ400 D820n
Hello Scar9,
I had the same problem. To fix it, I had to charge my phone for 30 minutes. After that, I remove the back cover (to access to the battery). I connected the phone to my PC and I disconnected the battery. I wait any seconds (maybe 10 seconds) and I reconnected my battery (still the phone connected). The screen display a law charge of my battery (around 5 percents) but I can start my phone. After that I fully charged it and all seems OK !
I hope that can help you.
Regards.
Scar9 said:
Hello!
First of all - yes, I am completely aware that there are MANY similar threads, I've spent almost 3 hours now finding solution, no luck. I hope some good soul out there will be able to shed some light on my case So here it is:
Today, I was caught in a bad moment with low battery, and the phone discharged completely and turned off. I've connected it to the charger just about 5 mins later max, but the blinking LED of death got me there I have it on a charger for about 4-5 hours now (original HTC charger, of course tried both, the wall and the usb), the LED is still blinking, phone is cold (it's getting quite hot when it's charging normally), no reaction whatsoever, can't even enter any fastboot or recovery or anything. I've tried every possible combinations I have found, vol+ & power, vol- & power, both volumes & power, long, short, nothing helps. Now what's different than any other threads out there? The phone was NEVER rooted, I didn't unlock bootloader, flash, nothing. It was as stock as it could be since I had motherboard replaced (2 years ago, on warranty in HTC service). Now the warranty has ended, so I'm really hesitating to send it there, as it's propably gonna end up with new motherboard again, no matter what the problem really is (I live in Poland, and that's just a common "fix" no matter what the problem is). Current motherboard is the one with CID B25 (the one that never got any update, so it's stuck on Kitkat for 2 years now). Everything was working completely fine just a few hours ago, nothing indicated any battery problems, it just discharged, and now I can't get it to work.
Does anyone have any helpful ideas?
Thanks in advance
@edit
Forgot to add it's a single sim version, model OPFJ400 D820n
Click to expand...
Click to collapse
Have you got any solution for this problem.
I too have same problem..
Hi everyone,
I'm trying to revive an HTC Desire 820 (dual-SIM model) that I have. There were several hardware issues with the phone - main one being the battery _completely_ blown and bulged out! So, I replaced the battery, along with the complete battery charging board, and the complete LCD display (which was also gone!)
Now, the issue I'm facing is, even after replacing 3 of the major parts with new ones, the handset is just not coming back to life! The red/orange LED on the front just keeps blinking (indicating that the mainboard is still working) but the phone simply does not respond to any combination of buttons, or even when I connect it to my laptop!
My core question is: Do I really need to have the _original_ HTC charger and USB charging cable (both of which I don't have) to get this thing up again?
If I can get some help and some clues as to what exactly is wrong here, I'll be really, really, REALLY thankful to you...!!!
Thanks a ton in advance!
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Bootloops/shutdowns are going to corrupt your data. I would RUU the thing before looking for hardware trouble, which you've likely sorted out by replacing the battery (of course, we're assuming the new battery is good).
BUT before that, is there a memory test in the bootloader or recovery? If so, I would run that very first thing.
bluedimensional123 said:
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Click to expand...
Click to collapse
Whatever happened to your phone? I have the exact same problem. Infinite boot loop, no illuminated LED, and no way of getting into recovery or anything else with it bootlooping. It occurred after I made the mistake of trying to restart it at 25%. I have the new battery and screen. i'm going to attempt to open this Pandora's box. Seriously going to have to turn my back on HTC. The 10 is so full of software issue problems regarding the batteries that they never bothered to address.
I did the exact same thing a few days ago and my phone won't charge or boot, but I do think the problem is with the button strip, that's what i think, because i tried turning it on before re assembling it and it did turn on successfully and was charging normally but when i re Assemble it, the phone got this problem, now i think when i turned it on before assembling i pressed the power button with a screw driver because i couldn't press it with my fingers, I think there i messed it up, any advice how to fix the button strip and remove a slip nut would be very much appreciated
I had the exact same issue as you(shutting down at 50%), have you found any solution to it?
edit: I THINK clean flashing oreo firmware then latest RUU then twrp then lineage fixed my issue, charging to full rn will drain it over the next day and report back if its gone for good