I am on my 3rd Fire in less then 60 days, the first two died from the same thing. Powered off but when I went to power it on the next morning the light would briefly turn green then turn off. The screen would not come on, and when I plugged the charger in the light would turn green then change to a bright orange then immediately dim to a pale orange. Like I said the first two did the same thing, they were both flashed with the latest gedeROM and OC to 1200Mhz, I have shied away from flashing the third one until I can find a common denominator , either that or my luck is just that poor. I have googled this issue for the last few days and haven't found anybody with the same issue. Any help would be awesome thanks.
sarsius said:
I am on my 3rd Fire in less then 60 days, the first two died from the same thing. Powered off but when I went to power it on the next morning the light would briefly turn green then turn off. The screen would not come on, and when I plugged the charger in the light would turn green then change to a bright orange then immediately dim to a pale orange. Like I said the first two did the same thing, they were both flashed with the latest gedeROM and OC to 1200Mhz, I have shied away from flashing the third one until I can find a common denominator , either that or my luck is just that poor. I have googled this issue for the last few days and haven't found anybody with the same issue. Any help would be awesome thanks.
Click to expand...
Click to collapse
Well it sounds like its not charged. When u plug it in, do you have enough time to hold the power down for the 20 seconds required to force it off. If you can do that then you could let it charge while its forced off. But it sounds to me it wont stay on long enough. This might require a factory cable, not sure though. This same thing happened to me, ad with me being stupid I made a charger that is more voltage than default charger and I fried my kindle. I suggest not to do what I did
powerpoint45 said:
Well it sounds like its not charged. When u plug it in, do you have enough time to hold the power down for the 20 seconds required to force it off. If you can do that then you could let it charge while its forced off. But it sounds to me it wont stay on long enough. This might require a factory cable, not sure though. This same thing happened to me, ad with me being stupid I made a charger that is more voltage than default charger and I fried my kindle. I suggest not to do what I did
Click to expand...
Click to collapse
Yes I attempted a reset but it wouldn't respond and I tried to let it charge, but after about an hour it got extremely hot and I didn't feel I could leave it plugged in safely. When I contacted amazon for support I did all this for the tech on the phone and when I plugged it in and told him about the light, he said something about the usb port had come off the board which I know is possible but to happen twice in 60 days with two different devices is just ridiculous. I'm not sure what I am doing wrong if anything both devices were fully charged when the errors occurred. I just don't want to have to get a fourth before the month is out, the only positive is the fast turn around from amazon.
Related
I have a stock Tmobile G2 that I have not rooted or done a thing too. I've been enjoying it just like it is.
Last night, I plugged it in at night and went to bed. This morning, the green LED was on saying it was fully charged, but it wouldn't power on? I finally pulled the battery and it powered on to the standard white HTC screen, but hung there for 5+ mins. I pulled the battery and again and I think the HTC screen came up again and hung again. After that battery pull, I could no longer get it to even power on.
Here's what I've noticed.
-After a battery pull and then plugging it in, I get an "orange" LED, but nothing happens. Can't power on, and it doesn't ever seem to turn green even after hours on the charger. When I remove the plug, the orange LED stays on and nothing happens.
- If I pull the battery and try to turn it on before plugging it , nothing happens, but in the same token, it won't show the orange LED if I plug it in.
The only thing different I did last night was that I used a Mini to Micro converter plug for the first time. I have a ton of Mini-USB plugs, so just ordered 2 of these. Could have been coincidence, but thought I would mention it.
My battery has been fine and has shown no issues of being bad, but wondering if they just crap out or something? The no charging LED after trying to turn it on is strange?
Any ideas?
Return it and call shenanigans?
That's really quite strange. Have you modded anything on the system that would affect it at all?
yeah, the hardware in your phone is simply broken. to make sure this is true, try doing a recovery. pull the battery, put it back in, hold the volume DOWN key, while hitting the power on button, use the volume rocker to go down to recovery, and then follow the instructions to recover the phone. but it sounds to me like water damage of some sort around the plug, or you pulled out the charger wrong and broke it. **this will remove all apps you have installed, but its better than having to wait for t-mo to send you a new one**
dietotherhythm said:
Return it and call shenanigans?
That's really quite strange. Have you modded anything on the system that would affect it at all?
Click to expand...
Click to collapse
Haven't touched a thing on this phone. I have an older G1 I've played with ROM's on and stuff, but I've left the G2 alone.
Only thing is standard apps from the market.
jenlow said:
yeah, the hardware in your phone is simply broken. to make sure this is true, try doing a recovery. pull the battery, put it back in, hold the volume DOWN key, while hitting the power on button, use the volume rocker to go down to recovery, and then follow the instructions to recover the phone. but it sounds to me like water damage of some sort around the plug, or you pulled out the charger wrong and broke it. **this will remove all apps you have installed, but its better than having to wait for t-mo to send you a new one**
Click to expand...
Click to collapse
Just tried the recovery, but nothing.
No water damage or anything. Phone has been well taken care of and looks new.
I guess its just a failure. Only had it a month or so. Guess I'll contact tmobile about a replacement.
These things happen, my original G1 died after about a week of use, though I would have expected that after a month you would be in the clear.
raitchison said:
These things happen, my original G1 died after about a week of use, though I would have expected that after a month you would be in the clear.
Click to expand...
Click to collapse
Yeah, kind of surprised myself. Electronics do fail though.
BlueLghtning said:
I have a stock Tmobile G2 that I have not rooted or done a thing too. I've been enjoying it just like it is.
Last night, I plugged it in at night and went to bed. This morning, the green LED was on saying it was fully charged, but it wouldn't power on? I finally pulled the battery and it powered on to the standard white HTC screen, but hung there for 5+ mins. I pulled the battery and again and I think the HTC screen came up again and hung again. After that battery pull, I could no longer get it to even power on.
Here's what I've noticed.
-After a battery pull and then plugging it in, I get an "orange" LED, but nothing happens. Can't power on, and it doesn't ever seem to turn green even after hours on the charger. When I remove the plug, the orange LED stays on and nothing happens.
- If I pull the battery and try to turn it on before plugging it , nothing happens, but in the same token, it won't show the orange LED if I plug it in.
The only thing different I did last night was that I used a Mini to Micro converter plug for the first time. I have a ton of Mini-USB plugs, so just ordered 2 of these. Could have been coincidence, but thought I would mention it.
My battery has been fine and has shown no issues of being bad, but wondering if they just crap out or something? The no charging LED after trying to turn it on is strange?
Any ideas?
Click to expand...
Click to collapse
I'm on my 4th G2. The screen kept going out on two of them and the other one, all the apps were force closing on me. I almost gave up on this phone and went to a nexus s but I love the quality of this phone as in it don't feel or look cheap. Also I would have missed my hardware keyboard for my fat fingers lol. I was not going to get a mytouch 4g. Wanted to get as stock vanilla android as I could.
Just send it back and get a new one. Hopefully the next one won't give you these problems.
Sent from my T-Mobile G2 using XDA App
Those are usually the signs of water damage or a fried battery
Sent from my HTC Vision using XDA App
Tmobile assisted me and all is well!
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.
Hi guys!
I bought my new HTC One X on contract with three UK about 10 days ago. Been working great and I've flashed several different roms on it, the latest being the AOKP jelly bean.
I was in the middle of setting up my Go Launcher last night, when the phone suddenly died. I thought it must have just crashed following some rom/kernel issue, so I tried to turn it back on, no luck. Also tried holding the power button down but to no avail.
I supposed that it might have run out of battery, as it was fairly low at the time, so I left it charging on USB (with the indicator light flashing) all through the night (around 9 hours) and this morning it still won't turn on.
The screen won't come up at all, and the phone doesn't vibrate or make any noise but if I connect it to my computer it will sometimes be detected and I can see the device in ADB.
"adb devices" first shows the device as offline, then if I run "adb kill-server" and try again then it shows the device as "HT23YW105462 recovery".
I've then tried running commands such as "adb reboot", "adb reboot-bootloader", "adb reboot -p" but no luck. The phone seems to recognize the command as it disconnects, but it doesn't turn back on.
Any theories guys? I hope my new toy hasn't been bricked somehow! If this happened to my Desire HD I'd just take the battery out to make sure it was fully off and try again... is this a good idea here?
Thanks in advance for any help you can give! Many cookies will be given as reward. (sorry for the long post )
- P.s. This is pretty urgent as I use this number for work!
:victory:
Ok, it seems to have been resolved at last... just for anybody who gets the same issue, here's what worked for me.
After doing some more searching I found someone mentioning this method: Leave the phone plugged in to your USB port for a while until the orange LED flashes. Leave it flashing for a few minutes, then quickly swap the lead from your USB port to a wall charger. If you leave it unplugged too long then it seems the LED stops flashing and it won't work, so do it quickly.
If successful the LED will keep flashing while plugged into the wall, and it will start to charge up. Give it a while (I left mine for about 25 minutes) then try and turn it on. This worked for me, but even after this period of time it had only charged up to 2%!
:S This is an odd phone indeed.
Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton
Croaton said:
Very strange resolution IMHO.
This problems must be caused by discharging the battery more than it should (which I guess custom ROMs can cause)
/Croaton
Click to expand...
Click to collapse
Very strange indeed... I tried pretty much everything I could before this, but this was the only thing to get the phone to boot. Charging and working fine now :S. I'll have to make sure to never run it flat if I can help it, this would be a right pain if it it happened while I was out
Just saved from similar issue
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)
silenttalker said:
My battery run out last night when I had the phone connected to the tv through USB>HDMI when i put it on the charger the charging light would not switch on. Phone wouldnt switch on either it was really dead!. Left it all night hooked up to charger and this morning still nothing, wouldnt switch on.
So I Hooked it up to the PC and after 10 minutes or so the light started to flash and I quickly inserted the usb charging cable and it started to charge.
Pretty sure I either discharged the battery to much (did update to 7.2.2 yesterday with 30% bat), OR something to do with having the USB>HDMI cable inserted when the battery run out.
Odd but brought it back to life (phew!)
Click to expand...
Click to collapse
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)
wont turn on
chrisoverson said:
Hmm, seems like a pretty common fault. Maybe an app that cuts power to the phone when it reaches a critical limit might be a good idea... I noticed that most phones seem to turn themselves off before fully dead, whereas ours now seem to completely flatten themselves. At least if it shut down at 1% you could still turn it back on when you found a charger, and it could tell you why your screen was about to go black rather than "poof, gone".
Anybody know such an app? Or should I make one (been wanting to get my hands dirty)
Click to expand...
Click to collapse
im unable to see led light i believe unsupported kernel fryed phone
My HOX just seems to have died overnight. It has been completely fine and stable at least a month on AOKP ICJ 1.3.0. Have not done any form of meddling with the rom/kernel/anything since then.
Yesterday the phone was working completely fine, but this morning, the phone screen won't turn on, it won't boot(at all), holding power button/power + vol down doesn't do anything.
The phone is now behaving very weirdly:
Charging does not turn on any LED lights, and it still would not boot during/after charging for hours.
However, it seems the LED will start flashing red if I leave it charging for a while(it's not overheating as far as my hands can tell).
The default action for charging normally is a always-on red LED.
Also, after a some plug-in time, it seems the the HTC sync manager will detect it and auto-run.
Phone remains unable to be turned on.
I kinda panicked here and unplugged the phone to see if the effect can be reproduced; it could not. Phone now remains undetectable.
After plugging it out, the red LED continues flashing for a few minutes, the phone can be noticeably felt to be getting hotter gradually.
But still nowhere near overheating levels.
Could anyone perhaps help me troubleshoot? Any help would be greatly appreciated.
I'll try to see if I can get into get it to be detectable again later after it cools down a bit; see if I can at least get into bootloader.
-Reproduced, but adb reboot bootloader seems to reset the cycle, bringing it back to undetectable.
leave it charging
Oh wow. It really works. Thanks tomascus!
Alright phone's useable again. What a panic attack.
Any idea why the first 2 hours of charging before I posted this didn't seem to do the trick? Is this just some internal checkpoint thing?
ULAMSS5 said:
Oh wow. It really works. Thanks tomascus!
Alright phone's useable again. What a panic attack.
Any idea why the first 2 hours of charging before I posted this didn't seem to do the trick? Is this just some internal checkpoint thing?
Click to expand...
Click to collapse
It likes to take its time
The light blinks when the charge is really low....
Sent from my HTC One X using Tapatalk 4 Beta
Today, when i was charging my phone when it was around 20%, it didnt charge well and gave a message that the phone was draining more than it was charging. I shut my phone at let it charge, but the orange light started to blink on and off so it wasnt charging right. I tried different plugs and chargers but same deal.
Now the light doesnt come on at all, so im assuming all the battery is dead. I checked online a bit for solutions like pressing the power button and up/down button for a while, doing so under a light, leaving it charging for a while, trying to charge with my laptop usb. But nothing seems to be working.
When I try the power and up/down combo and then charge it, the light comes back for a few seconds but then vanishes. I dont know if this means anything, but in any case, I cant get my phone on so i need help. Is there anything I havent tried?
Sounds like a hardware problem, but I'm no expert. I'd take it to a repair place.
Shiverfire said:
Today, when i was charging my phone when it was around 20%, it didnt charge well and gave a message that the phone was draining more than it was charging. I shut my phone at let it charge, but the orange light started to blink on and off so it wasnt charging right. I tried different plugs and chargers but same deal.
Now the light doesnt come on at all, so im assuming all the battery is dead. I checked online a bit for solutions like pressing the power button and up/down button for a while, doing so under a light, leaving it charging for a while, trying to charge with my laptop usb. But nothing seems to be working.
When I try the power and up/down combo and then charge it, the light comes back for a few seconds but then vanishes. I dont know if this means anything, but in any case, I cant get my phone on so i need help. Is there anything I havent tried?
Click to expand...
Click to collapse
I had a similar issue months back with my m8. The micro usb port contacts had weakened and I had to put pressure on top of the area where the cable connects to the phone just to get it to charge. I was still under warranty, so I ended up taking mine back to ATT and getting it replaced for free, with them calling it a defect.
Try putting pressure on different parts of the cable when you charge it, and use a program like gsam battery monitor, to make sure it's drawing power. This will only be a temporary fix, though.