[Q] tf101 table and dock won't charge after full drain - Eee Pad Transformer General

Hello all,
I recently installed Cyanogenmod JB (v5 then to v6, issue happened on both) for the transformer and it seemed to have some really bad battery issues. It would die really fast and the dock stopped charging. I was able to get it charging again after a hard reset, but then it stopped after a full drain again and hasn't been able to get it to take a charge since. The tablet as well has been acting really flaky as well. It stopped taking a charge and wouldn't turn on, but randomly would start taking a charge again, completely drain, take charge, drain , etc. and now it will only randomly turn on while plugged in for a few minutes then die (about once a day). I have done numerous hard resets when I can catch up powered up, taken apart the tf101 and unplugging the battery and plugging back in, holding down every possible combination of buttons, and even tried freezing the power brick. I also tried booting into APX, thinking I managed to get into a loop somehow, but nada. I can tell the tf101 is getting power from the wall because if I put my ear really close to the port on the tf101 I can hear the distinct hiss of power being delivered to the battery and lack-there-of when it is not plugged in.
I've run completely out of ideas at this point. I feel like it has to do with the fact that the tablet battery went to 0%, but I'm not positive. Considering it happened damn near in toe with the Cyanogenmod install, I feel that has played a role in it as well.
I'm wondering if anyone else has something I can try. If I can catch it randomly powered on (who know if it will even do that anymore) I was going to try and flash a new rom and kernel really fast and hope I don't lose it. But I feel that is very risky. So I'm open to all suggestions anyone has.
Thank you in advance! =D

Just an update:
I was able to flash the AOKP ICS rom and it seems to boot more regularly, but the battery is still refusing to charge. Wiped battery stats, cache, factory reset, cold boot, the works. Just says "Charging, 0%" on the homescreen.
Thanks again!

Another update. I was able to start getting a charge on my tf101 after flashing the ICS aokp rom. However, it is doing a trickle charge. Not sure why or how, but I suppose my power brick decided to die at the same time of me flashing the JB rom. I've tried the freezer trick, but no go on that. I was reading around and I saw that you need a usb 3.0 cable to get the 15v charge, but that didn't seem quite right, considering I was getting 15v with my USB 2.0 cable. Anyway, looks like I'm heading over to Amazon to pick up a new charger.
Thanks to everyone who checked out my issue. I'll leave this here as a brain dump for anyone else who may have this issue.

It's most definitely your charger man. It seems to be a common problem with these tablets. Mine died too so I just made my own from a spare 12V power supply I had laying around and a piece of USB cable.

Related

Phone thinks its connected to USB

I put DL09 on and then added stupidfast v1.54. Worked fine at first but now it thinks its plugged in all the time and if i turn it off it wont boot unless plugged in. Is this a hardware issue or an issue with the kernel? Thanks for your help.
Had the same thing too. Started from scratch with Odin. Good as new now.
So i plugged my phone in and the notification for the USB went away. I havent tried to reboot yet, but the battery meter keeps going from 68% which the phone is at to 100%. Its very odd.
Is there a way to reset the battery? That might be way off but i dont know enough about it really.
see this thread
http://forum.xda-developers.com/showthread.php?t=919770
My computer sees my phone. The battery stopped jumping too. Im gonna try to clean the port when i get home from work. I still need to plug it in to get it to boot. I was gonna try reverting to stupidfast 1.98 to see if the kernel is the issue. If it makes a difference i had flashed the circle battery and it started about 12 hours after i did so. I reverted to a backup i had saved. As this didnt completely fix the problem i assumed it was the kernel. Battery life is good with the kernel as expected but the phone just seems a little testy, some things are just a little laggy like its struggling. Any additional help would be greatly appreciated. If i cant find a solution im just gonna have to re-odin everything.
Well, seems it was a dirty port. Throughout the night things got better. Got home didnt have any rubbing alcohol so i stuck some heavy paper in there to try to rub off the port. When i tried to reboot it was hit or miss, when i held the power button the battery charging screen would come up as if i was plugging the phone in while it was off to charge. Could be due to weather here maybe i had salt on my fingers from the snow and i touched the cable before i plugged it in. However GPS isnt locking in any better than it did with DI01. Ill take it for now, vast improvement over this afternoon.

[Q] Green LED when plugged into (wall) charger, but no boot

not boot looping, just nothing at all. The phone won't power on.
The battery ran completely out, but now, after charging it overnight, it will not power on at all. I've seen various threads saying to take the battery out for 30 min or so, try pulling the battery & SD card WHILE it's plugged into the charger, try booting it with no battery at all (just charger), and all of them state to use the wall charger, as being in a PC USB port won't be enough.
I've tried everything, but nada.
My phone is/was running the rooted gingerblur leak, which I installed correctly by SBFing first beforehand and doing a total wipe. I honestly didn't even bother reinstalling very many apps, I've been so busy at work over spring break. The phone HAD been shut down and restarted a few times since flashing the gingerblur, so this wasn't the first time it rebooted since then or anything.
Had a few force closes and random reboots over the time on gingerblur, and was actually not that excited about it, but now I'm stuck with a brick it looks like.... any ideas?
I had the same problem on mine it would stay at the boot logo and wouldnt go past that I called Verizon and they are sending me a replacement.
tyvallely said:
I had the same problem on mine it would stay at the boot logo...
Click to expand...
Click to collapse
Mine doesn't do *anything*... no boot logo, no nothing.
just got back from verizon with a new battery, works fine again... just posting as a followup. I thought it would be odd that even with a dead battery in the unit, it wouldn't power on with the wall charger attached, but with a new battery (got the extended one while I was at it) it works fine again.
another update: ate thru that battery, and died again. Recharging the new battery does nothing. Mine seems to have a hardware failure in general that it won't recharge batteries at all. New batteries come with some juice in them, but once that's gone it's gone.
Bought one more battery just to SBF it back to vanilla before I send it in for warranty service. Will keep this thread posted just in case anyone else runs into this... I hate finding threads with problems that just trail off with no resolution.
I'm not sure if they intended the DX to work like this, or whatever; but if my battery runs completely dead, the phone cannot charge it. I get the same green light you do, annnnd nothing when I try to power on.
What I have done to solve this in the past was to cut open the cable for either a 5v power supply or a usb cable. Either tape off the unused wires or be seriously careful not to go crossing wires, plug the charger in, and touch the appropriate cables to the battery terminals, (battery out of the phone). About a minute is all it takes to give it enough juice to charge in the phone with a standard charger.
Someone else posted a more in dept guide on this process, if you are unsure of any steps, please search for that rather than causing damage.
Not my fault if something bad happens from anyone following this; however, I have done this numerous times with zero issues.
happened to me twice and each time verizon replaces just after hearing the symptom. must be hw failure
LIH said:
happened to me twice and each time verizon replaces just after hearing the symptom. must be hw failure
Click to expand...
Click to collapse
Replaces Battery or phone?
yeah, final post on this, but Verizon is sending me a replacement phone. I've had the DX since launch, and this will be my third one, but they've always been good about sucking it up and just sending me a new one free of charge.
I bought two replacement batteries in total (which were both returned) -- one thinking that it was just a bad battery and another when it became apparent that wasn't the fix. I thought I'd be sending it to motorola for warranty, and wanted to flash the SBF back on to return it to vanilla.
Anyway, long story short: if you found this thread because you're having the same issues, just buy another battery, flash it back to stock, and take it in for replacement. Then you can return the battery.
Cheers.

Spontanious Brick?

so i'm running the latest CM7. have been doing so for a while now. updated to the latest nightly on friday i think. charged up the phone last night, was using it just fine this morning. plugged into computer when i got here to work. all was good.
so i was getting ready to leave... unplugged the phone, and it showed the "M" for a few seconds and then shut itself off.
now i can't even get it to power into anything. no regular boot, no recovery boot, nothing. literally nothing happens when i hold the power button. it's like the phone it completely dead.
could i have shorted something out when i unplugged it? or is it possible to have like a spontaneous brick for no reason?
i'm perfectly comfortable sbf'ing, but not sure how i'm going to access the phone without any kind of power-on.
suggestions? thanks gents.
well... not sure why, but it appears as though my cable at work sucked the phone dry rather than charge it!
when i got home and connected to the regular charger... it fired right up.
anyway, all good now.
I've noticed that if I have any apps running on my X, or I'm using the radio on it a lot by streaming music or whatever, the USB cable can't supply enough juice to charge it. It slowly drains over the day. Was something on it running during the day that would be causing it to use more juice than it was supplied?
When I was overclocked I sucked so much battery
Sent from my DROID X running MIUI

dead

It appears dead. It's late at night so i've yet to try googling about recovery through a pc of some such, truth be told while i can flash a rom with instructions, i'm no guru or anything. It was running CM 10.2? the latest stable release for N10, think that's the one.
I was just browsing a forum, and after posting, the disply started to stutter as i scrolled up, when i stopped scrolling, the stuttering decreased, and then as i scrolled and scrolled fasster, the stuttering increased until display turned black (stoned curiosity...) and now i can't get anything out of my N10. Holding power, trying to reboot into recovery. Nothing. No lights, sounds, vibrations. None of the normal stuff.
anyone got any ideas for me to awke up to? I think that if i can't get any life out of it, then would it be a case of trying to sideload or such with ADB? as i say, i'm a complete rookie, just a couple of flashes under my belt.
Second question, i probably have the answer to, but am i right in thinking custom roms void the warranty?
edit: Plugged it into the wall a few minutes ago. It had had about 40% remaining, but when i plugged it in, i got the battery simbol on the screen (big white battery charging in center) and any time i press or hold the power button, or with volume buttons, i get nothing but the icon. I'll keep it plugged in for now and see what happens. But by the look of i assume if it can do that when plugged into the wall i sohuld hpoefully be able to connect via my computer in some manner
If by stuttering you mean blinking, this has happened to me when my N10 was on charger with a dead battery and it drew more power than what the charger could provide. When you scroll, the CPU frequency gets bumped up and the tablet consumes more power. After a while it just turned off for me (when I changed to an other app I think), when there just wasn't enough power.
So I would suggest leaving it on charge for a few hours, then try holding all buttons and see if you can get into bootloader. I've had the battery levels not display correctly on some custom ROMs, (for example I would do a reboot at 60% battery and after it reboots it only said 13%) so just charging it a bit might solve the problem.
bee55 said:
If by stuttering you mean blinking, this has happened to me when my N10 was on charger with a dead battery and it drew more power than what the charger could provide. When you scroll, the CPU frequency gets bumped up and the tablet consumes more power. After a while it just turned off for me (when I changed to an other app I think), when there just wasn't enough power.
So I would suggest leaving it on charge for a few hours, then try holding all buttons and see if you can get into bootloader. I've had the battery levels not display correctly on some custom ROMs, (for example I would do a reboot at 60% battery and after it reboots it only said 13%) so just charging it a bit might solve the problem.
Click to expand...
Click to collapse
Thanks. As of 5 minutes ago it got back to life. All battery apps showed 40 odd. Strange.
i think your battery has gone/ on its way out, exact same happened to mine, you need a pogo charger and the original wall adapter to provide enough power to switch it on. Only thing which worked for me, hope it works for you.
hellomynameistj said:
i think your battery has gone/ on its way out, exact same happened to mine, you need a pogo charger and the original wall adapter to provide enough power to switch it on. Only thing which worked for me, hope it works for you.
Click to expand...
Click to collapse
Might be the battery, might be glitchy software. Plugged it in via USB and it worked sometime later. Will be keeping an eye on it.
It will probably be fine. I thought I had a bricked N10 but turns out the battery was dead. It is fine now. THought I had a bricked N7 also, turned out the battery plug got loose, (screen would flash every 2 seconds with static on the screen) popped it open and oushed the plug in and that is fine now too.
If it continues to die around the 40-50% mark, you'll need to send it in for repairs. Make sure they don't just try replacing the USB port on it, the battery itself is the culprit.
http://forum.xda-developers.com/showthread.php?p=44068051#post44068051

Overheating while charging

This issue began several days ago. I had plugged my phone in to the LG charger it came with and went on with my normal routines. Normally about an hour later I disconnect it as its usually fully charged. This time i noticed my phone was off, and extremely hot, almost unbearable to touch. Since then, the past few times I've plugged my phone in to charge, when I come back to check on it, it's turned off and extremely hot. I assume the phone is turning itself off after reaching a temperature threshold.
In normal operation, the phone does not overheat or get too warm. This only happens when I plug the phone in to charge on its normal charger.
I am going to do some experimenting tonight and let the phone charge off of my PCs USB 2.0/1A port, as I think maybe it could be the fast-charger going bad?
Has anyone else experienced this?
It's an LG V20 VS995 flashed previously to US996 firmware/rom after my switch from Verizon to T-Mobile. It's been flashed like this for a while and this issue is relatively new so I doubt its the rom (I hope!)
Edit: Figured I should also mention, battery life is just fine. I get the pretty much the same amount of life from the battery as I did when I purchased the phone give or take a few minutes.
You should test with another charger, preferably compatible with quick charge. Can't you borrow one from the neighboorhood ? Test with another charger and other good cable that the ones you used.
Could be anything from a faulty battery, charger, cable or kernel change, app update in the background, sudden amounts of wakelocks, anything really. Your best bet is to eliminate hardware as a factor, starting with trying a different power source -> charger -> cable -> battery, testing the charge temperature after changing each thing. Failing all of those variables changing having eliminated the problem, flash the latest KDZ for your model to your phone and run it dry on nothing but a stock OS. Plug it into the charger and see if the same thing happens. If not, then you know it was software, if so, then you know it's the phone.
I've also started having this issue. However, my case is slightly different.
After leaving it on the charger for a while, the screen goes to a black background with a ghost verizon logo on top of that black background. Holding power down, unplugging, replugging, etc. does not reboot the phone. I have to pull the battery in order to get it to respond. The issue only occurs after it's been charging a while. I've tried reflashing fw 15a as well.

Categories

Resources