I looked around and searched first for similar threads before posting this one.
On my rooted NT, I have noticed that charging only works when it is powered off. (I rooted immediately so have no point of reference to non-rooted behavior.)
1. When powered on and plugged in to charge(A/C), I look under Settings/Battery and it shows discharging.
2. Also, the light on the micro USB is green, not orange, if the NT is on.
3. I turn off, the light turns orange until fully charged then turns green.
Could someone confirm that this is the correct NT behavior? I was thinking that it should charge if plugged in whether powered on or off.
it charges on or off if you have the nook tablet cable plugged in, the only time you need the nook off is if you are using a micro usb normal cable via computer to charge, so in answer
no not normal behavior
lenardo said:
it charges on or off if you have the nook tablet cable plugged in, the only time you need the nook off is if you are using a micro usb normal cable via computer to charge, so in answer no not normal behavior
Click to expand...
Click to collapse
Thanks. That is what I feared. Unsure what might be causing so hope someone with broader insight might be able to give direction.
Interesting. My NT was charging but after rooting it, it doesn't charge either. I did a search and came across your post. I blocked it from receiving further updates but that shouldn't be the cause.
Berryblue said:
Interesting. My NT was charging but after rooting it, it doesn't charge either. I did a search and came across your post. I blocked it from receiving further updates but that shouldn't be the cause.
Click to expand...
Click to collapse
Mine charges fine when off and have not heard from anyone on a solution or potential cause. As such, I just plug in each night with power off.
I did a nook hardware test and it detects the USB just fine but no charging from what I can tell when power is on.
Nook not charging while turned on
johninsf said:
I looked around and searched first for similar threads before posting this one.
On my rooted NT, I have noticed that charging only works when it is powered off. (I rooted immediately so have no point of reference to non-rooted behavior.)
1. When powered on and plugged in to charge(A/C), I look under Settings/Battery and it shows discharging.
2. Also, the light on the micro USB is green, not orange, if the NT is on.
3. I turn off, the light turns orange until fully charged then turns green.
Could someone confirm that this is the correct NT behavior? I was thinking that it should charge if plugged in whether powered on or off.
Click to expand...
Click to collapse
I have the same issue. It started this morning. I rooted my nook yesterday using this method http://forum.xda-developers.com/showthread.php?t=1354487. Before rooting my nook it charged fine while being plugged in to the wall socket. After rooting last night I could charge the nook (Plugged into the wall) while it was turned on. This morning I can not charge the nook while the device is turned on. Rooting and blocking OTA's using the link above is the only thing i have changed. Thank you guys in advance.
Also, don't have a problem, but I am scared to break the connector since I have heard it is really fragile, so I don't use it plugged up.
lostwhat83 said:
I have the same issue. It started this morning. I rooted my nook yesterday using this method http://forum.xda-developers.com/showthread.php?t=1354487. Before rooting my nook it charged fine while being plugged in to the wall socket. After rooting last night I could charge the nook (Plugged into the wall) while it was turned on. This morning I can not charge the nook while the device is turned on. Rooting and blocking OTA's using the link above is the only thing i have changed. Thank you guys in advance.
Click to expand...
Click to collapse
Interesting,,,, I used Indirect's rooting method and I am charging right now as I write this on my NT. The only differences I can think of is I used one of his earliest root versions (in mid November) so I don't have some of the later script additions. Also to block the OTA update, I just uninstalled the update service instead of the steps to get mine to show as version 9.9.9
To make sure I understand what people have done. You follow Indirect's rooting method, and then use TiBu to restore the DeviceManager app, in order to block OTAs, correct?
Nothing else? You haven't touched the /system directory otherwise?
cfoesch said:
To make sure I understand what people have done. You follow Indirect's rooting method, and then use TiBu to restore the DeviceManager app, in order to block OTAs, correct?
Nothing else? You haven't touched the /system directory otherwise?
Click to expand...
Click to collapse
Well like I said, I used an early version of Indirect's script to root. Then I backed up the DeviceManager app in Titanium backup (just in case I caused problems) and then deleted it completely. That's why I said my software version doesn't show 9.9.9 like others who have used the db version workaround.
cgdash said:
Well like I said, I used an early version of Indirect's script to root. Then I backed up the DeviceManager app in Titanium backup (just in case I caused problems) and then deleted it completely. That's why I said my software version doesn't show 9.9.9 like others who have used the db version workaround.
Click to expand...
Click to collapse
Ok, so you deleted your DeviceManager.apk? I'll see if I can replicate your bug by deleting that apk. That might be what caused the problem.
----
Nope, still charging while powered on...
cfoesch said:
Ok, so you deleted your DeviceManager.apk? I'll see if I can replicate your bug by deleting that apk. That might be what caused the problem.
----
Nope, still charging while powered on...
Click to expand...
Click to collapse
Oh - I don't have the charging bug. I was saying that maybe I can charge because I rooted with an older version of the script and just deleted the DeviceManager APK to avoid firmware upgrade. Whereas others used a newer version of Indirect's script plus the work around to make the version 9.9.9
Not sure why some can't charge while on cause it works fine for me on my rooted NT.
Basically, where I am at as well. I've rooted numerous times, ever since the 24th, and I've never had this no charging problem.
Figuring out what is different about what they did, and what others who don't have the problem is difficult. There is nothing in the rooting process that should make a difference. Except perhaps if they all reverted from 1.4.1 to 1.4.0 ... Indirect, and I both can charge, but never had 1.4.1 on our tablets.
There could be something left over from 1.4.1 that is screwing things up? (Unlikely, but possible?)
cfoesch said:
Indirect, and I both can charge, but never had 1.4.1 on our tablets.
There could be something left over from 1.4.1 that is screwing things up? (Unlikely, but possible?)
Click to expand...
Click to collapse
Yeah I never have had 1.4.1 on mine either and no charging problems.
That is exactly what I did...nothing else.
---------- Post added at 11:49 PM ---------- Previous post was at 11:47 PM ----------
That could be a possibility as I finally rooted after getting the 1.4.1 OTA. Everything else is fine, just the charging issue.
cfoesch said:
Basically, where I am at as well. I've rooted numerous times, ever since the 24th, and I've never had this no charging problem.
Figuring out what is different about what they did, and what others who don't have the problem is difficult. There is nothing in the rooting process that should make a difference. Except perhaps if they all reverted from 1.4.1 to 1.4.0 ... Indirect, and I both can charge, but never had 1.4.1 on our tablets.
There could be something left over from 1.4.1 that is screwing things up? (Unlikely, but possible?)
Click to expand...
Click to collapse
I had to downgrade to 1.4.0 using the zip to SD card method, before rooting, to mod the apk to version 9.9.9.9 to block OTA'S.
Sent from my SGH-T959 using Tapatalk
I used the Factory Reset option since my NT came originally with 1.4.0 so I didn't have to do the SD card. I'm thinking about (banging my head on desk) going back to factory setting and re-installing Indirect's files. Maybe after the New Year.
cgdash said:
Yeah I never have had 1.4.1 on mine either and no charging problems.
Click to expand...
Click to collapse
I started with 1.4.0; never had to downgrade to root. But since I rooted and blocked the OTAs using Indirect's methods, my nook will not charge unless it's off.
I'm not sure I'm all that thrilled with the Nook anyway, but this could be a deal-breaker. I'd hate top be in the middle of something and suddenly have to turn off my Nook for three hours before I could finish with it.
kevalin said:
I started with 1.4.0; never had to downgrade to root. But since I rooted and blocked the OTAs using Indirect's methods, my nook will not charge unless it's off.
I'm not sure I'm all that thrilled with the Nook anyway, but this could be a deal-breaker. I'd hate top be in the middle of something and suddenly have to turn off my Nook for three hours before I could finish with it.
Click to expand...
Click to collapse
Just to be clear, you are plugging it into the wall, and it will only charge with the screen off, or completely powered off? If you are plugged into a computer and it is only charging with the screen off, that is normal.
Sent from my BNTV250 using Tapatalk
ckevinwelch said:
Just to be clear, you are plugging it into the wall, and it will only charge with the screen off, or completely powered off? If you are plugged into a computer and it is only charging with the screen off, that is normal.
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
This is plugging into the wall and using the charger that came with the Nook (when I initially charged it up, I used the cord, etc., from my Samsung Captivate. It charged up completely in about three hours).
The cord indicator shows orange, as if it's charging, but in Settings, it says, "Not charging," as opposed to "Discharging," which is what it says when there's no charger connected--and the battery continues to drain. I have the screen set to go dark after two minutes, so it spent most of the time "Not charging" with the screen dark. Also, it took around five hours for it to charge back to 100% from a low of 15%.
I'd really rather not, but I'm about ready to give a go to sending it back to stock and seeing if one of the other rooting methods will give me back my "on charge." That is, unless someone has some ideas for how to make Indirect's root and OTA block allow for charging regardless of whether it's on or off.
Related
My fascinate will not turn on unless its plugged in. Once it turns on it runs fine. If you hold the power button to turn it on it will show the battery icon, but will not turn on. If you plug it in it will turn on and work fine. It also thinks its in usb debugging all the time. not plugged into anything and it thinks its debugging.
Very strange.
Are you on Froyo? Using a rom? You might have the screen of death. If you have clockwork recovery you can turn it on that way.
Read this:
http://forum.xda-developers.com/showthread.php?t=960080
Keep me Fascinated
SC 2.9.2
EC10 Voodoo Lagfix
Honeycomb v4 - Animated
My friend had this issue.. It was hardware. Get a new one
sent from my frozen yogurt filled fascinate!
neh4pres said:
My friend had this issue.. It was hardware. Get a new one
sent from my frozen yogurt filled fascinate!
Click to expand...
Click to collapse
My son's had the same thing, left the battery out for a day with the intention of returning it under warranty, put the battery back in and it fired right up without an issue, and havent had one yet.
Another question, are you using the stock battery or an after market job?
Without one of the tweaked kernels, the after market batteries wont work at all...
I forgot about this thread. My problem is when the phone is turned off, it will not turn on unless its plugged in. you push the power button and you see a picture of an empty battery. You plug it in and wait for the battery to turn green, and the phone will fire right up. Tried a new battery, and nothing. I am going to call vzw and see what they say.
Any resolution on this? I am having the exact same issue with my Infuse (AT&T).
Clean the contacts with a pencil eraser.
Sent from my SCH-I500 using XDA App
Thanks Terror for the tip, but still having the same issue.
hokey777 said:
Thanks Terror for the tip, but still having the same issue.
Click to expand...
Click to collapse
NP I had to do it all the time on my wifes alias.
Did you try a different battery?
At this point I would go stock and see if a verizon store will try another battery for you.
Good luck!
Sent from my SCH-I500 using XDA App
iamnotafanofgravel said:
My fascinate will not turn on unless its plugged in. Once it turns on it runs fine. If you hold the power button to turn it on it will show the battery icon, but will not turn on. If you plug it in it will turn on and work fine. It also thinks its in usb debugging all the time. not plugged into anything and it thinks its debugging.
Very strange.
Click to expand...
Click to collapse
exact same problem as quoted above.
Some times the USB port gets gunk in it, try taking a piece of paper fold it a few times make sure the width is like half the size of the usb micro jack and slide it in to the usb port. fold it so it is snug but not tight move back and forth, do both top and bottom of the port but be careful on the thin side. basically your cleaning the contacts to remove and film.
Good Luck
If that still doesn't do the job chances are it's a hardware issue.
iamnotafanofgravel said:
I forgot about this thread. My problem is when the phone is turned off, it will not turn on unless its plugged in. you push the power button and you see a picture of an empty battery. You plug it in and wait for the battery to turn green, and the phone will fire right up. Tried a new battery, and nothing. I am going to call vzw and see what they say.
Click to expand...
Click to collapse
This is a very accurate description of the issue. I too am having the problem however it is on AT&T captivate. In my case, it only occurs when I am using a MIUI ROM. I have flashed multiple ROMS, both prior to and after discovering the problem and only have this issue when using MIUI ROM (Which is awesome in every other way). Two other things I would note. I have purchased another battery and it behaves identically, and MIUI drains batteries like a mother. Even swapping out a completely charged battery does not resolve the issue. Maybe someone brighter can explain how the phone "reads" the battery charge level while off.
does anyone have this problem with 'stock' phone?
I'm having the exact same issue with my Continuum. Thought maybe the USB port had issues, but it charges a battery just fine. It just won't acknowledge it's charged and turn on unless it's connected to a power source. Without a cable plugged in it just shows the big empty battery icon with a non-moving progress wheel on top of it for 3-4 seconds then screen goes black. With a cable plugged in it displays that, then changes to show the true charge of the battery at which time I can start up the phone. I restored my phone to factory defaults earlier today, but this problem persists.
Has anybody found any solution to this?
drumtrucker said:
does anyone have this problem with 'stock' phone?
Click to expand...
Click to collapse
My friends did this last year. It was a hardware issue afaik
Sent from my SCH-I500 using xda premium
I have the same issue with my Samsung Epic. Anyone find a fix?
I also have this problem. I have discovered, however, that while I must plug the phone into a USB cable, that USB cable need not be plugged into a power source or anything at all. I can reliably (100% of the time) power up with a USB cable just laying in my drawer. I can also reliably (100% of the time) not power up without plugging into a USB cable.
In other news, I have also discovered that certain low-level actions tends to screw up lots of things. I can Odin just fine. I can flash ROMs, kernels, etc. just fine. However, I cannot restore a nandroid. Whenever I restore a nandroid, as best as I can tell, my partitioning gets all jacked up. When this happens, I can't do anything but boot into recovery (although once this happens, I can no longer flash ROMs) or Odin. Doing a full Odin flash restores functionality (in the sense that we all see where we need a USB cable to boot up), though. So ultimately, I think these phones have defective memory and that's what is ultimately causing this.
I bought this phone a couple days ago for $100 so I'm not out much (and can probably get most of that back even acknowledging the issues). Sure would have been nice for that person to have told me there were these issues. But oh well. C'est la vie!
---------- Post added at 10:06 AM ---------- Previous post was at 10:03 AM ----------
BTW, curious, what radio are you all using? I have only used EH03. I haven't yet tried EC09...
I have a Motorola Atrix 4G on Bell Mobility. Currently the phone will not boot at all. The phone is out of warranty.
When this started I began by searching through the xda forums and found several similar problems. Most pointed to the sleep-of-death or a charging adapter problem. I have tried charging with the Motorola adapter that came with the phone, a USB cable and the Motorola Lapdock. None of these have provided any happy. Each time I tried, I left the phone overnight, when I checked on it, the phone and battery were cold. I tested a known-working battery from another Atrix and the phone would still not boot.
Some other searches point to a factory cable. I bought one on Ebay however the phone will not boot. I tested the cable on a known-working Atrix and it works fine. I did notice that when I plug the factory cable in to my phone and in to my Windows 7 PC, it detects *something*. Under device manager I see an unknown device called "APX". So far Google and xda searches haven't been able to provide me with a correct answer.
When I plug in the regular USB cable the green LED turns on for a while, if I touch the power button, the green LED goes out. RSD Lite does not detect anything, I assume this is because the phone is not in RSD mode.
I have tried combinations of volume buttons/power button as well, both with the wall charger and with the factory cable. Nothing displays on the screen at all no matter what I've tried. The phone had the stock install from Bell however was rooted with SuperOneClick (obtained from xda forums and installed many months ago) and had no third-party apps on it.
This death seemed to start slowly, at first battery life was at times terrible, then it moved on to not wanting to power on for a while if the battery died or the phone was turned off when the battery was low. Removing/re-inserting the battery several times typically helped. Eventually the phone got so bad, when it booted it would just crash repeatedly with a message about motorola.home.something (sorry I don't remember exactly what). Hitting force close would just bring the message back up again. I left the phone off overnight and the next morning, R.I.P. my Atrix
I have access to Windows XP or 7 as well as Linux.
Any help would be appreciated. Also I apologize for the long-winded post, I'm trying to provide as much information as I can.
I had this problem to, I freaked out, what I needed to do was to get another Atrix (in this case my Uncles) and make sure that the battery in it is FULLY CHARGED, then I took out my battery (in the broken phone) and put in his, then I got a solid green LED, then I had to leave it on the charger overnight, after that the M would show, but that was it, so I then went into fastboot and flashed the ICS Leak, and ta-da.
Xerox98 said:
I had this problem to, I freaked out, what I needed to do was to get another Atrix (in this case my Uncles) and make sure that the battery in it is FULLY CHARGED, then I took out my battery (in the broken phone) and put in his, then I got a solid green LED, then I had to leave it on the charger overnight, after that the M would show, but that was it, so I then went into fastboot and flashed the ICS Leak, and ta-da.
Click to expand...
Click to collapse
I had tried that before, but I can't remember if I had charged the battery full. I'll give it a shot today, thanks!
jonbruce said:
I had tried that before, but I can't remember if I had charged the battery full. I'll give it a shot today, thanks!
Click to expand...
Click to collapse
I've tried that with no luck. I should also note that the factory cable bypasses the battery, potentially eliminating any battery problems.
It's possible that your phone is finished. The 'motorola.home' error is usually caused by something you've updated (google search?) but I would doubt that it would cause your phone to not even start up.
At this point, I might be inclined to open the phone up (http://www.ifixit.com/Teardown/Motorola+Atrix+4G+Teardown/4964/1) and see if you can see anything obvious?
barry_ said:
It's possible that your phone is finished. The 'motorola.home' error is usually caused by something you've updated (google search?) but I would doubt that it would cause your phone to not even start up.
At this point, I might be inclined to open the phone up <url removed so I could reply> and see if you can see anything obvious?
Click to expand...
Click to collapse
I will check that out tonight and report back, thanks!
jonbruce said:
I will check that out tonight and report back, thanks!
Click to expand...
Click to collapse
Nothing obvious when I took it apart, no visible damage or problems. Any other thoughts? I've been told to try ADB from a Linux box and see if it will do anything. I've started installing ADB but looking for more insight.
jonbruce said:
Nothing obvious when I took it apart, no visible damage or problems. Any other thoughts? I've been told to try ADB from a Linux box and see if it will do anything. I've started installing ADB but looking for more insight.
Click to expand...
Click to collapse
Update. I found this ... http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75 and now instead of "APX" in Windows device manager, I have "NVIDIA USB Boot-recovery driver for Mobile devices".
It looks like NVFlash might be something I need next. In other news, the phone when plugged in via the factory cable, is actually very slightly warm. It's the first new sign of life I've seen in this thing for a few days.
jonbruce said:
Update. I found this ... http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75 and now instead of "APX" in Windows device manager, I have "NVIDIA USB Boot-recovery driver for Mobile devices".
It looks like NVFlash might be something I need next. In other news, the phone when plugged in via the factory cable, is actually very slightly warm. It's the first new sign of life I've seen in this thing for a few days.
Click to expand...
Click to collapse
I've had no luck at all since my last reply. http://forum.xda-developers.com/showthread.php?t=1046994 seems to have something to do with my problem, but I'm not able to dig up a solid answer. As best as I can tell, I manged to hard brick the thing and I'm up the creek without a required paddle.
Any other thoughts on this would be great. Even if I'm able to ensure the device is wiped, I could send it in. There are work files on there (I know, I know, I'm an idiot) I can't have out in the wild.
Just bought a replacement Atrix for $100. It included three cases, three batteries, wall charger with cable, car dock and a metric ass-load of screen protectors.
I do want to thank everyone for offering help and ideas, it was a good learning experience!
jonbruce said:
Just bought a replacement Atrix for $100. It included three cases, three batteries, wall charger with cable, car dock and a metric ass-load of screen protectors.
I do want to thank everyone for offering help and ideas, it was a good learning experience!
Click to expand...
Click to collapse
I've just encountered this issue and cannot find a solution anywhere online. I've come to terms with my phones fate by now. Just wanted to ask where I could find this Atrix replacement for 100 w/ all the neat stuff you've listed above? Please advise
thanks
Cheekan
cheekan said:
I've just encountered this issue and cannot find a solution anywhere online. I've come to terms with my phones fate by now. Just wanted to ask where I could find this Atrix replacement for 100 w/ all the neat stuff you've listed above? Please advise
thanks
Cheekan
Click to expand...
Click to collapse
I found mine on Kijiji, luckily right in my city.
Hello, so much time searching for this on the web, spanish is my birth language... so i wanted to know some update from this of any of you if posible, thanks in advance.
i couldn't describe better the problem and situatiob, is exactly the same, same phone of course.
I was about to try to make a factory cable, so i ended here, i think is not going to help me then is that right?
PD: i don't know what more to do with the atrix, sell for parts, even that is difficult over here, and the services don't help either, i've tryied 2 of them already, only ignorance they have
Ok i rooted with sd_root_NT16or8gbV4_7 and have go launcher installed. This is my wifes nook so she might have installed something that is keeping it from working i plan to look at it closer tonight. My problem is that it will not connect to the computer and it will not charger while turned on with the wall charger or with the computer. If i turn the nook off it charges fine. When the nook is on the LED is green while in wall or computer. Power off and the led turns orange till its full then turns green. Ill post more info tonight but if youve had this problem please let me know what has helped you.
outridger
outridger said:
Ok i rooted with sd_root_NT16or8gbV4_7 and have go launcher installed. This is my wifes nook so she might have installed something that is keeping it from working i plan to look at it closer tonight. My problem is that it will not connect to the computer and it will not charger while turned on with the wall charger or with the computer. If i turn the nook off it charges fine. When the nook is on the LED is green while in wall or computer. Power off and the led turns orange till its full then turns green. Ill post more info tonight but if youve had this problem please let me know what has helped you.
outridger
Click to expand...
Click to collapse
My nook occasionally does this also, but if the green light is on while charging its still charging the battery. Its not recommended to charge the nook while off(one reason why it will turn on while charging.)
ive left it plugged in over night with the screen off and powered on in the morning it was off and had no battery it had about 50% when i plugged it in.
outridger said:
ive left it plugged in over night with the screen off and powered on in the morning it was off and had no battery it had about 50% when i plugged it in.
Click to expand...
Click to collapse
Maybe just the root method not allowing it. Have you tried any other methods? If you have an SD cards around you can try making a boot able cm10 card and see if it charges. It won't affect any of your nook's internal settings,apps,etc.
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write to an SD card and put it in your nook. If it charges from there then the root method you have is messed up. Make a backup and try another or a custom ROM.
maybe its been rooted for about 6 months though and this is a new problem within the last month. Thats the kicker i guess since it shouldnt update i dont know if there is a setting somewhere that would stop it from charging. Im going to look into the go launcher widges to see if one of them has that option first i think. ill update in about 8 hours once im home. thanks for your help though m8
ok im home and reset go launcher to stock form. my software version in 1.4.0 ota blocked.
still get a greed light on cord and its still not charging. also if i run NookHWTest and try to run the usb/charge it says that the cord is not connected
outridger said:
ok im home and reset go launcher to stock form. my software version in 1.4.0 ota blocked.
still get a greed light on cord and its still not charging. also if i run NookHWTest and try to run the usb/charge it says that the cord is not connected
Click to expand...
Click to collapse
I found a few threads that suggested to restore back to factory reset and re-root your device. You can use a backup app like Titanium Backup to save all the apps, pictures etc.
Something in the /system directory gets messed up, but no one knows why.
My NT will only start charging if I turn the screen on after I plug it in, or plug it in with the screen turned on. After that, I can let the screen sleep, or turn it off right away.
If I don't do this, the light on the charger stays green and it won't start charging.
Connecting to the computer isn't affected by this, though.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
well reset to factory and still doesnt charge while on. The cord works in the other nook so im going to say the port in the nook is going bad. On a side note went to [ROM]{WIP} SGT7+CM10.1+Cherry Picks,By meghd00t. 24/02/13 and it seems to be very stable so far compaired to the others ive tried in the past
outridger said:
well reset to factory and still doesnt charge while on. The cord works in the other nook so im going to say the port in the nook is going bad. On a side note went to [ROM]{WIP} SGT7+CM10.1+Cherry Picks,By meghd00t. 24/02/13 and it seems to be very stable so far compaired to the others ive tried in the past
Click to expand...
Click to collapse
Oh, you should have said something about it working with the other one. The ports for these can get messed up all the time. Happens a lot.
Turn the nook off when charging. This is a known bug.
Sent from my NookTablet using xda app-developers app
Updated "Please help: VZW S4 not charging..." (The refurb/replacement is busted)
First of all, big thanks to this whole community and the wealth of info that led me through my first time rooting and flashing ROMs. But now on to the sour part (search didn't bring up anything useful to my situation).
Short history of phone in case it helps:
I've been rooted since June (rooted on MDK). I've been on the CM 10.1 and then 10.2 nightlies ever since. I've followed all directions, and am glad to say that I had a great experience (a few hiccups from dirty flashing a few times, but nothing that couldn't get sorted). Last ROM I was on was CM 10.2 nightly from 2013-10-11.
Anyway, last night my battery gets low, but I didn't charge it right away. It got down to about 8%, and then I try to charge, but the battery icon doesn't indicate charging. Indeed after a few minutes fiddling, the % drops to 7%. Trying to charge it while powered off caused the phone to vibrate once every 5-10 seconds or so, but no LED or on-screen indication it's charging. I tried my wife's S4 charger and cable. Same result, not charging. I restored to a previous CM nightly backup I had from September. Same result, still not charging. I restored to my rooted stock ROM backup made right after I first rooted in June. Same result, not charging. Charging from the wall or PC doesn't make a difference. I ended swapping batts with my wife, using her stock never-been-rooted S4 to charge my batt, which worked just fine.
The USB port on my phone does work since I could see the device in Odin. Tried reflashing the stock kernel. Still not charging. I spent the rest of last night restoring to out-of-the-box stock. Now I'm back to a completely stock, unrooted S4 (still on MDK kernel, haven't accepted update to ME7), and it still won't charge. No notices or anything that the charger is connected. Except this morning, for no reason discernible to me, I now get the following warning message when I connect my or my wife's charger:
"The connected charger is incompatible with this phone. To prevent damage to your phone, charging has been stopped. To continue charging, use the original charger and cable that were provided with this phone."
Thoughts, please? And thanks in advance to you all.
Update 1 at 2013-10-13T17:30EDT
So I did some more digging and came across what looks like a similar problem (that's what I get for not using Google for search anymore). Sorry, can't post links yet.
forums.androidcentral.com/rogers-samsung-galaxy-s4/297925-samsung-galaxy-s4-not-charging-grey-battery.html
The biggest difference is that I don't get the grey battery symbol when plugged in while powered off, just the cyclic vibrating. And mine doesn't charge at a reduced rate at all (I lost 7% battery in 45 minutes while plugged in and powered off due to all the vibrating).
Further, my "incompatible charger" warning has ceased. I'm just back to the phone not recognizing a charger is plugged in at all. Phone still talks to my PC just fine though.
Is it likely I need to replace the USB charging port flex cable as suggested in the Android Central post? Thanks for anyone reading and pondering.
Did you try to flash back to stock?
kheltek said:
Did you try to flash back to stock?
Click to expand...
Click to collapse
Yes. I flashed via Odin back to unrooted stock (MDK kernel) and stock recovery, which is the phone's current config. I haven't yet done the ME7 update, but it auto-downloaded today, just haven't installed it.
How long have you had the phone? My suggestion would be to make another backup and put it on your computer. Then restore back to full stock, no root or anything. Take it to Verizon / Best Buy and tell them it's not charging. Hopefully it's not water damaged.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Quentin.Sheley said:
How long have you had the phone? My suggestion would be to make another backup and put it on your computer. Then restore back to full stock, no root or anything. Take it to Verizon / Best Buy and tell them it's not charging. Hopefully it's not water damaged.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had the phone since the end of May (so I've owned it 4.5 months). Since I've already restored to full stock, I'm thinking tomorrow I'll take it to a VZW store near me to see what they say. Is Samsung's manufacturer warranty handled through VZW? Or do I deal with Samsung directly? Note, I have no extra insurance/warranty on the phone.
That should be manufacture warranty and you normally have1 year from purchase. Good luck and again just ensure you completely wipe it off all root and custom Roms. They'll try to blame it on that.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Back to VZW to replace the replacement phone
Update:
I went to my local VZW store on Monday and they tried cleaning the USB port. No luck, so they shipped me a refurb since this is still under the 1 year hardware warranty. I paid the extra for overnight shipping. My refurb phone arrived yesterday. I moved over my sim, micro SD, and battery from the old phone to the refurb/replacement phone, and plugged in the wall charger. BOOM, battery starts charging no problem :victory:. I spent last night getting my phone all set up. I also checked and this phone has the ME7 update so no more CM or any other ROM for now :crying:.
But otherwise, everything looked good with the replacement device...until this morning. I had the phone powered off all night, tried turning it on this morning and it won't turn on. Won't boot normally, won't boot into recovery, won't boot into download. Tried a battery pull...no luck. The phone had like 95% battery when I shut it off last night. Now, when I plug in the wall charger, the phone buzzes once, the grey battery icon with the circle shows up for 10-15 seconds, then the screen goes blank, then that sequence repeats.
Back to VZW today to get the replacement phone replaced .
dang...you have some bad luck. I had some similar issues and the phone seemed to fix itself?? Did not want to lose custom recovery, so actualy ordered an external charger and two batteries and of course the day the batteries came, the phone started charging normally again. Anyways...good luck...hopefully the new device wont have the newest update (which i dont think it's ota yet...just over wire). Dont let the store update anything at all or you may not even be able to root!
I have a Kindle Fire HDX 7" that I purchased a couple of months ago for my son. It was rooted and running Thor with Gapps. He plugged it in before going to bed and when we looked at it the next morning it had the Google X showing. We unplugged it and now it will not power up unless it is plugged into a wall charger. It will boot into safestrap, but bootloop before it gets into an OS. I bought a ChargeDR to up the power output on the USB, but as soon as I try to switch to sync it will turn off again. My theory was that if we could get it to fastboot with sync on then we could ADB, but that is out. Not sure if there is any way to salvage this one or not. What is odd is that safestrap still thinks it has 67% battery, but calibration must be off, which is why this happened to begin with.
tuttle36 said:
I have a Kindle Fire HDX 7" that I purchased a couple of months ago for my son. It was rooted and running Thor with Gapps. He plugged it in before going to bed and when we looked at it the next morning it had the Google X showing. We unplugged it and now it will not power up unless it is plugged into a wall charger. It will boot into safestrap, but bootloop before it gets into an OS. I bought a ChargeDR to up the power output on the USB, but as soon as I try to switch to sync it will turn off again. My theory was that if we could get it to fastboot with sync on then we could ADB, but that is out. Not sure if there is any way to salvage this one or not. What is odd is that safestrap still thinks it has 67% battery, but calibration must be off, which is why this happened to begin with.
Click to expand...
Click to collapse
If I read you correctly, you are assuming that you have not developed a hardware problem, but that the software is preventing the battery from charging. That seems highly unlikely.
Sorry for the confusion, I would say there appears to be a hardware issue as well. I am concerned that since it has safestrap installed that if I were to return it to Amazon for repair it would not be covered. Without being able to access it from a computer, I cannot remove safestrap. I have thought about force charging the battery by opening up the case, but it sounds like a complete disassemble would be in order. I cannot find any information about other occurrences of this problem.
tuttle36 said:
Sorry for the confusion, I would say there appears to be a hardware issue as well. I am concerned that since it has safestrap installed that if I were to return it to Amazon for repair it would not be covered. Without being able to access it from a computer, I cannot remove safestrap. I have thought about force charging the battery by opening up the case, but it sounds like a complete disassemble would be in order. I cannot find any information about other occurrences of this problem.
Click to expand...
Click to collapse
Not to worry. If it's still under warranty, tell them it's broken and they'll send you a new one. They don't ask about the software you may or may not have installed.
Thanks. It should be under warranty, it is nice to hear Amazon isn't taking such a hard stance on development for these devices.