Develop Bugs

TP2 low battery, in reboot loop

I've got a TMOUS TP2 which appears to be stuck in a reboot loop of sorts cause I can't charge the battery.
I've read through the forums and I saw a few similar problems like this but it seems like it those they were stuck at the bootloader, and that's not the case for me.
Basically the battery was down to 14% and I turned off the phone last night intending to charge it this morning. Somehow the battery dropped to 1% by the time I went to turn it on this morning, and it shutdown (really just lost power) right after I started it. So I go to plug it into the wall charger and then:
charge light comes on
after a few seconds charge light goes off
the phone tries to boot (does little vibrate, shows splash)
after the splash screen, phone loses power
charge light comes back on
then tries to boot after a few seconds.
repeat
If left unplugged the phone just sits there dead, but upon plugging it in, it tries to boot.
I've seen it where the phone doesn't have enough power to boot and just needs to be charged for a while, but I can't seem to do that here.
Anyone have any idea how to prevent it from trying to boot after the AC adapter is plugged in?
Thanks

arimp said:
I've got a TMOUS TP2 which appears to be stuck in a reboot loop of sorts cause I can't charge the battery.
Thanks
Click to expand...
Click to collapse
If you're desperate...you might try doing a hard-reset.
Why would that help? I don't know...except sometimes when really stuck it helps to just change the situation...try something completely different.
Of course, a hard-reset deletes all data and applications that you've put on the phone, which is why I suggested it as a recourse if desperate.
Probably keep the phone plugged in while doing hard-reset.

Same problem, solved by itself
Hi,
I had a similar problem with a standard TP2, it was clear a battery fault. Phone was working well with a new battery and, of course, another working phone couldn't boot up with the faulty battery.
I took out the defective battery and let it aside for almost 2 weeks. After that it started to work, but the capacity is clearly smaller.
So from my experience, a hard reset wouldn't help you.
Radu

nradu said:
Hi,
I had a similar problem with a standard TP2, it was clear a battery fault. Phone was working well with a new battery and, of course, another working phone couldn't boot up with the faulty battery.
I took out the defective battery and let it aside for almost 2 weeks. After that it started to work, but the capacity is clearly smaller.
So from my experience, a hard reset wouldn't help you.
Radu
Click to expand...
Click to collapse
Yes, it goes without saying -- though it's good you did -- that if you have access to another battery that's an obvious thing to try first.
The hard reset is worth trying, in general, for otherwise-unresolvable phone issues.

It's a dead battery. Same exact thing you describe happened to me. Granted, it was because of water damage but same symptoms. Thinking the phone was dead I went and bought a new one. Then I decided to try the new battery, bam, phone back alive. Returned the phone and bought a new battery. By the way, the dash2 battery fits as well. Tmobile stores didn't know it... But the connectors were the same do I tried in the store and it worked.

devis said:
It's a dead battery. Same exact thing you describe happened to me. Granted, it was because of water damage but same symptoms. Thinking the phone was dead I went and bought a new one. Then I decided to try the new battery, bam, phone back alive. Returned the phone and bought a new battery. By the way, the dash2 battery fits as well. Tmobile stores didn't know it... But the connectors were the same do I tried in the store and it worked.
Click to expand...
Click to collapse
So it was indeed a dead battery. Oddly I found someone who had a CMDA TP2 from Verizon (mine is GSM TMO), and was able to pop my battery into their phone for a minute or two and charge it to about 5%, then put it back in my phone and all was well. With their phone, plugging in the charger did not cause the phone to start up and then power cycle.
That's really weird "glitch" if you want to call it that. So mental note, don't let the battery run down too far.

[Q] Charging issue that defies common sense...

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.

Think my phone is bricked now :(

My phone won't turn back on or charge anymore. The last thing i did was pause Google Music, then the phone just sat there. It wouldn't go to the home screen or anything, it froze. I pulled the battery and now it won't turn on or charge at all. Won't display the battery charging when i have it connected to the computer or wall. Can't enter fastboot either. I'm currently at work and the computers here wont recognize it when i connected via USB.

mhm motherboard sudden death..? it doesnt seems to be a brick.

fabulous69 said:
mhm motherboard sudden death..? it doesnt seems to be a brick.
Click to expand...
Click to collapse
idk but my own laptop won't recognize it either =/

Painkiller006 said:
My phone won't turn back on or charge anymore. The last thing i did was pause Google Music, then the phone just sat there. It wouldn't go to the home screen or anything, it froze. I pulled the battery and now it won't turn on or charge at all. Won't display the battery charging when i have it connected to the computer or wall. Can't enter fastboot either. I'm currently at work and the computers here wont recognize it when i connected via USB.
Click to expand...
Click to collapse
I doubt it's bricked. Will it start up into the bootloader?

Again, try pulling the battery for a few minutes. Then put everything back together but wait until you have access to a true USB charger, not a USB port on a computer. I've noticed with a few phones in the past (GNex included) that sometimes when I had a bad crash and the phone went unresponsive, that trying to get a hint of life while using a USB port didn't work as well as a charger. You'll probably have to leave it plugged in for a little bit, but after 15-30 minutes you should once again at least get the white battery charging icon to display front-and-center if you give the power button a single push. At that point, try booting into fastboot, then recovery and clean things up a bit before rebooting into android (Wipe Caches, Fix Permissions).
If not, seriously, do everything again, and wait with it charging overnight. I had a similar issue with my Nexus 10 after doing my first unroot and flashing on it. It took nearly an hour, but then I finally got the charging icon (in that case though, a battery pull wasn't feasible).

sporkette said:
I doubt it's bricked. Will it start up into the bootloader?
Click to expand...
Click to collapse
nope, won't start at all.

stefpap said:
Again, try pulling the battery for a few minutes. Then put everything back together but wait until you have access to a true USB charger, not a USB port on a computer. I've noticed with a few phones in the past (GNex included) that sometimes when I had a bad crash and the phone went unresponsive, that trying to get a hint of life while using a USB port didn't work as well as a charger. You'll probably have to leave it plugged in for a little bit, but after 15-30 minutes you should once again at least get the white battery charging icon to display front-and-center if you give the power button a single push. At that point, try booting into fastboot, then recovery and clean things up a bit before rebooting into android (Wipe Caches, Fix Permissions).
If not, seriously, do everything again, and wait with it charging overnight. I had a similar issue with my Nexus 10 after doing my first unroot and flashing on it. It took nearly an hour, but then I finally got the charging icon (in that case though, a battery pull wasn't feasible).
Click to expand...
Click to collapse
Yeah i tried all of that since 1 pm yesterday, that's when it just died on me. I have left the phone charging for over an hour and still don't get any sign of life, not even the white battery charging icon. Left the phone charging overnight, that didn't work also. I tried the OMAP fix but that also failed, it isn't recognized by my laptop.

That's a bummer. Once I had an Epic 4G that I also thought was bricked but the "leave it charge overnight" method worked even though the charging led wasn't on at all. I'm surprised that I now have seen an actual thread with a truly bricked device, not the usual "my phone is going into boot loops its bricked!" thread. Sorry to hear it man.
This may be irrelevant to you, but mine is on verizon and was having charging problems. I went into one of their stores and they had a replacement on the way in under 15 minutes of me coming in. Great service from them if that's who you're with carrier-wise.

crowmallet said:
That's a bummer. Once I had an Epic 4G that I also thought was bricked but the "leave it charge overnight" method worked even though the charging led wasn't on at all. I'm surprised that I now have seen an actual thread with a truly bricked device, not the usual "my phone is going into boot loops its bricked!" thread. Sorry to hear it man.
This may be irrelevant to you, but mine is on verizon and was having charging problems. I went into one of their stores and they had a replacement on the way in under 15 minutes of me coming in. Great service from them if that's who you're with carrier-wise.
Click to expand...
Click to collapse
Everything was working perfectly on mine, the battery was at 80%. I'm with T-Mobile and i know they don't carry the Galaxy Nexus. Would a Verizon store let me check if a new battery will be turn it back on? If not, guess i have no other choice but to call Samsung =/

Painkiller006 said:
Everything was working perfectly on mine, the battery was at 80%. I'm with T-Mobile and i know they don't carry the Galaxy Nexus. Would a Verizon store let me check if a new battery will be turn it back on? If not, guess i have no other choice but to call Samsung =/
Click to expand...
Click to collapse
The Verizon gNex uses a different batter than the GSM model.

3rdstring said:
The Verizon gNex uses a different batter than the GSM model.
Click to expand...
Click to collapse
Well that sucks Guess, it's time to call Samsung

[Q] Phone gives no response, but heats. Fixable?

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

Replaced screen and battery, now in (another) bootloop!

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