Related
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.
Hey all for some odd reason once I plug in the usb cable, the NT just reboots and starts bootlooping on cyanoboot screen while loading emmc. if i don't have the usb cable plugged in it will boot just fine with no bootloops whatsoever. have any of you encountered this problem? I had cm10 running on it and thought it was a bad flash, reflashing didn't help and restoring to a cm7 backup didn't do the trick either...
any ideas?
Can you charge with wall socket plug and usb?
demetris_I said:
Can you charge with wall socket plug and usb?
Click to expand...
Click to collapse
determines on your definition of charging. since it keeps on bootlooping endlessly on cyanoboot is it considered charging?
when i had flashed your cm10 rom on the cyanoboot screen it says charging disabled. so i assume that means its not charging?
if i have the usb cable plugged in and i turn the NT off completely by holding the power button, it will shut off but then come straight back on since the usb cable is sitll plugged in.
boots fine without the usb cable, but once the usb cable is inserted it just instant reboots and the bootlooping on cyanoboot starts.
do you think it may be hardware failure?
ShinnAsuka said:
determines on your definition of charging. since it keeps on bootlooping endlessly on cyanoboot is it considered charging?
when i had flashed your cm10 rom on the cyanoboot screen it says charging disabled. so i assume that means its not charging?
if i have the usb cable plugged in and i turn the NT off completely by holding the power button, it will shut off but then come straight back on since the usb cable is sitll plugged in.
boots fine without the usb cable, but once the usb cable is inserted it just instant reboots and the bootlooping on cyanoboot starts.
do you think it may be hardware failure?
Click to expand...
Click to collapse
Cyanoboot screen saying charging disabled is normal.
Before we can say is a hardware failure, if you hold N can you stop Cyanoboot?
If you can stop it select recovery and leave it there 20-30 minutes.
demetris_I said:
Cyanoboot screen saying charging disabled is normal.
Before we can say is a hardware failure, if you hold N can you stop Cyanoboot?
If you can stop it select recovery and leave it there 20-30 minutes.
Click to expand...
Click to collapse
yeah i can stop it and select recovery and it will boot into recovery. this is assuming the usb cable is not plugged in. whatever state the NT is in, once the usb cable is plugged in, it will auto reboot and start bootlooping on cyanoboot.
i have already requested for a replacement from B&N, so i don't know if leaving it on for 20-30 minutes is an option at this point. i plan to wipe the thing completely using adam's total wipe before i send it back to them.
i am afraid that if i leave it on for 20-30 minutes the battery will die and i won't be able to boot from sd to initiate the total wipe by adamoutler.
ShinnAsuka said:
yeah i can stop it and select recovery and it will boot into recovery. this is assuming the usb cable is not plugged in. whatever state the NT is in, once the usb cable is plugged in, it will auto reboot and start bootlooping on cyanoboot.
i have already requested for a replacement from B&N, so i don't know if leaving it on for 20-30 minutes is an option at this point. i plan to wipe the thing completely using adam's total wipe before i send it back to them.
i am afraid that if i leave it on for 20-30 minutes the battery will die and i won't be able to boot from sd to initiate the total wipe by adamoutler.
Click to expand...
Click to collapse
You are right, is a hardware problem. Go get a replacement.
so i got the replacement a week or so ago, and this replacement is now having the same problem... what in the world is going on. i am using your rom with the sgt7 enhancements. is it possible that the governor being on hotplug may be the problem?
EDIT: changed it back to the default ondemand governor... the problem is still there... how is this possible.
All this make me think is a bad flash.
Check your rom for any corruptions
demetris_I said:
All this make me think is a bad flash.
Check your rom for any corruptions
Click to expand...
Click to collapse
i restored to the 1.4.2 factory stock image that i made with cwm when i first got my replacement nook. same problem exists... i think it has something to do with the usb port getting bent or something...
How you manage to bent a brand new usb port?
So, take it back again for a replacement.
demetris_I said:
How you manage to bent a brand new usb port?
So, take it back again for a replacement.
Click to expand...
Click to collapse
thats the plan lol... the replacement nook was a pre-certified one. this time around they say they are going to send me a brand new one....
Same Problem on nook tablet cm 10.1 acclaim
I had the same problem with my tablet after I allowed the battery to drain completely while using it. I have to mention in my situation I had lost the original charger that came with my nook and I've been using a wall charger from my cell phone. When I had the stock barnes & noble nook tablet plugged in I noticed that the device would say that it's not charging even though it really was. It just took a longer time to charge. More than likely i had a voltage difference between the two devices. I too was stuck in that cyanoboot loop where there was not enough power to load the operating system and cyanboot wouldn't indicated if my battery was in fact charging. I had two solutions to this; I left my endless loop on overnight and in the morning low and behold i was booted into cyanogenmod. My other solution was to leave the device off for a long period of time and then try again. Hopefully this helps anyone else out in the future.
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.
Hi,
long story short: I connected my Z5C to a bad (apparently, I don't want to test ) charger and now I have some strange issues. Is there any change that my h/w isn't fried?
Full story: As I said I connected my Z5C (newest CyanogenMod provided here) to a charger and it instantly did a hard reset. Afterwards it did turn on and continued to work for some time. As I was on the road at that time I could not charge it elsewhere and later that day it ran out of power. When I tried to charge it with a known good charger some days later, it did not boot. I suspect the boot process to healthd or whatever draws this cool animation takes more power than my working but small charger provided.
It did charge at my laptop, especially when I put it into fastboot mode.
Now thats where I am stuck; the phone won't turn off completely and keeps rebooting when I turn it off (via os menu or hard reset, no chance).
I can charge it after it runs out of power (managed to charge to 100%), but it won't charge if I unplug and replug it. It is not recognised by a pc after I reconnect it one or two times (checked with device manager and lsusb), only chance to get to fastboot or flash mode again is drain the battery to 0%. It does show a loading animation and I can boot into android from there. Battery drain in Android seems to be a little higher than usual (100 to 0 after 2 1/2 days of pure standby without any radio stuff on).
I have already reflashed the original Sony firmware and erased everything that came to my mind (cache, data....).
Any hope that I did not kill some piece of hardware?
Thanks for your answers, any help appreciated
tell me more about your z5c's software, why you mentioned Cynogenmod? did you flash it with cynogenmod?
seems to me that z5c was running on custom rom and did not support fast chargers and bricked your device!
if that so, try flashing it using flashtool with original stockrom.
i don't wana go in to details however there is possiblity that battery.sys file is corrupt and atleast I was never able to fix my LT18i when it got bricked and battery status use to become zero in 2 seconds and android keep rebooting, later it got silent for good! no charge no nothing and i still have the device sitting. I was running it on coconut (cynogenmod) when all this happened!
Thanks for your reply.
The charger was no kind fast charger, just a common 12V to USB adapter with an output of 800mA (when it worked). I was running CM 13 when I connected it to the bad charger, but as I mentioned I have since then reflashed it with Stock ROM. No real improvement.
I have continued trying and I found out that the device seems to believe it is still connected via usb.
Code:
cat /sys/class/power_supply/usb/present
gives me "1" with nothing connected, can you check if this is normal?
The file is -rw-r-- r--, would changing its value change anything or is it just some kernel thing (can't check, don't have root permissions now as I flashed Stock ROM)?
Also after I charged it on my PC today it still shows me the notifications for USB connection and adb (I can add a screenshot if necessary), also looks like it still believes to be connected.
It seems I found the solution: I was playing a bit with a USB-OTG adapter (the ones to connect regular usb devices like keyboards or storage to your phone). After I connected a USB keyboard I tried (just for fun) if the Linux "Magic" SysRq hotkeys were enabled. So I did press Alt-Print-o, which is the Linux hotkey for "turn off now". It did not turn off, it also stayed off (no instant reboot). After I started the phone again it also properly turned off via the power menu!
I will have to test whether the charging issues are fixed, too, but as far as I can tell the problem seemed to be something software-related
Sadly did not work for long. I think I will go for official repair, think this is still cheaper than buying a new phone (after completely killing it with some DIY "repair" attempt). This annoying brick simply does not turn off, no matter what I do (apart from draining battery to 0%). Guess its my fault, still to afraid to try that broken charger again.
Hi there - bit of a weird variation of the bootloop 'feature' here.
The phone works fine for while powered on, all features are available, and as far as I can tell, the phone seems in perfect working order. However, a second after I insert a USB cable to charge the phone, it locks up and then restarts. If you leave the USB cable in, the phone bootloops (doesn't reach the boot animation, just the LG splash screen).
You can actually charge it if you force the phone to reboot into recovery mode, where you're presented with the two options (factory reset or quit) and just don't choose anything, but this is a full-brightness screen that never turns off so is agonisingly slow to charge. This suggests to me that it might not be a hardware issue, just an issue with the ROM or something.
Unfortunately, this also happens when you plug the USB into a PC so I can't even wipe with LGUP or root/unlock bootloader. It is currently completely stock, international unlocked H850, running V20a-234-10. According to the guy that gave me the phone, this developed very recently at random, not after a software update etc.
I've also tried disabling USB charging using apps (but they require root anyway), and looked into disabling the power on my computer's USB port (and keep data transfer) but that doesn't seem to be possible.
Obviously factory reset it a few times, tried different cables and chargers, and I can't find any other threads/anything on the web about it.
Can anyone think of anything I can try? Any way I can make it flash/downgrade software without using a USB cable? Wireless adb would be perfect but requires a USB during the initial setup
Thanks in advance!
Most likely a battery defect, try to buy an original one, they're not so expensive. it should fix the issue. otherwise, it's an issue in the USb port, but i don't think it is.
Interesting - I can charge the battery using an external battery charger kit (the one I bought for my G4 actually, as the pins are in the same place) so I assumed the battery was ok, but I'll get a second just in case - thanks.
For info, I can have the device stay on with the USB plugged in in download mode too, and I've also updated the software to the latest available with no change.
New battery arrived today, no change unfortunately. I also bought a replacement standard module (charging port and speaker) but the phone won't accept it, shows the 'swap module' screen on boot and won't go any further.
Does anyone have any tips about trying to bypass/prevent that screen?
jackfacespoon said:
I also bought a replacement standard module (charging port and speaker) but the phone won't accept it, shows the 'swap module' screen on boot and won't go any further.
Click to expand...
Click to collapse
Having done some searching I bought a second replacement phone chin, same as the module I referenced above, which has solved the issue!
I can't find anyone else with this issue, but for posterity, it looks as if there are regional variations of the chin unit which the device detects on boot. My original chin had the code 'GLB 32' on it, the one that didn't work had 'GLB 46' (I think). I specifically asked for one from eBay with a similar number to my original, which when it arrived was 'GLB 33'.
This worked, but only on the second reboot, once I'd reattached it.
Hope this helps anyone else in my position.
EDIT: Mods can mark thread as Solved if they want!
jackfacespoon said:
Having done some searching I bought a second replacement phone chin, same as the module I referenced above, which has solved the issue!
I can't find anyone else with this issue, but for posterity, it looks as if there are regional variations of the chin unit which the device detects on boot. My original chin had the code 'GLB 32' on it, the one that didn't work had 'GLB 46' (I think). I specifically asked for one from eBay with a similar number to my original, which when it arrived was 'GLB 33'.
This worked, but only on the second reboot, once I'd reattached it.
Hope this helps anyone else in my position.
EDIT: Mods can mark thread as Solved if they want!
Click to expand...
Click to collapse
Dude, thanks for posting this! It's been happening to me for the last 4-5 weeks and I couldn't find any posts on this. Was it worth buying a new module? Has it lasted up until now? Thanks!