Howdy all, long time cappy user and now I'm running into a problem that i can't solve. I'm hoping others have encountered this problem and can provide a solution.
When my phone is completely powered off, a grey battery icon intermittently and will continually flash when the phone is unplugged. Normally i wouldn't care but in this instance, i can NOT power the phone back on unless i plug the phone into a power source. When i plug the phone in, instead of getting the green horizontal battery indicating it's charging, i get a white battery instead that's vertical.
This creates an inconvenient problem because if i encounter an instance where i either A) need to do a battery pull, B) 3 button hold to reboot or C) the phone randomly turns off, unless my charger is near, I'm screwed. No matter what combination of buttons i push when the phone is powered off, it will not power on from an off state unless it's plugged in and i get the white battery indicating it's charging.
Some background info..I noticed this happening when I initially started flashing JB ROM's. I've odined with every package out there, replaced my battery, flashed several different ROM'S and nothing has fixed this issue.
Thanks for reading and a bigger thanks to anyone that can offer some insight.
TLDR; Phone, when in an off state and unplugged, shows an intermittently flashing grey battery and will NOT turn on unless connected to power source.
Sent from Mars via Curiosity
Hey, sorry I don't have an actual answer for you, but I can throw this in-- I'm also running JB on my Captivate (Slim Bean 2.7 atm, having previously run SB 2.6 and Cyanogen 10, 10/03), and I also notice some weirdness with the charger. The main thing is, the phone no longer seems to notice when the charger is connected. It actually charges, so it hasn't been too big of a deal, but the battery status still *says* "discharging", and once it's fully charged up, the battery statistics don't reset like they did on Gingerbread. This has only been an issue once-- I ran the battery all the way down to where the phone turned itself off. So I plugged in the charger and restarted it. It came up, briefly, only to complain about the battery and immediately shut itself down again-- it didn't realize the charger was connected. With the phone off, but the charger plugged in, the screen just stayed black. I didn't get the green battery icon that GB used to give when it was charging while off. However, it did charge, and I was able to restart it fine in the morning.
So again, sorry that's not a solution, but it does seem there's something weird about the charger recognition.
Oh, and I'm pretty sure it's not my cable. It's the same cable I've been using for two years, and it worked fine with GB.
ulbonado said:
Hey, sorry I don't have an actual answer for you, but I can throw this in-- I'm also running JB on my Captivate (Slim Bean 2.7 atm, having previously run SB 2.6 and Cyanogen 10, 10/03), and I also notice some weirdness with the charger. The main thing is, the phone no longer seems to notice when the charger is connected. It actually charges, so it hasn't been too big of a deal, but the battery status still *says* "discharging", and once it's fully charged up, the battery statistics don't reset like they did on Gingerbread. This has only been an issue once-- I ran the battery all the way down to where the phone turned itself off. So I plugged in the charger and restarted it. It came up, briefly, only to complain about the battery and immediately shut itself down again-- it didn't realize the charger was connected. With the phone off, but the charger plugged in, the screen just stayed black. I didn't get the green battery icon that GB used to give when it was charging while off. However, it did charge, and I was able to restart it fine in the morning.
So again, sorry that's not a solution, but it does seem there's something weird about the charger recognition.
Oh, and I'm pretty sure it's not my cable. It's the same cable I've been using for two years, and it worked fine with GB.
Click to expand...
Click to collapse
Thanks for taking the time and acknowledging my conundrum. I stay pretty current in the threads of the ROMS i run and haven't noticed any other comments remotely near either of our experiences.
I'll have to keep my eyes open, but I'd venture to guess your USB port has corroded connectors and needs replacing. Shine a flashlight in there and take a look
Sent from my SGH-I897 using xda premium
brianray14 said:
I'll have to keep my eyes open, but I'd venture to guess your USB port has corroded connectors and needs replacing. Shine a flashlight in there and take a look
Click to expand...
Click to collapse
Unfortunately, I plugged it in one night running Gingerbread and it worked fine, upgraded to JB the next day, plugged it in that night and got this issue. It would be a mighty big coincidence for a hardware problem to have developed just then. But I guess it's not impossible.
ulbonado said:
Unfortunately, I plugged it in one night running Gingerbread and it worked fine, upgraded to JB the next day, plugged it in that night and got this issue. It would be a mighty big coincidence for a hardware problem to have developed just then. But I guess it's not impossible.
Click to expand...
Click to collapse
Yeah, i agree with you. It's so tough to pin down these little oddities that occur with these phones because not all phones are manufactured with the same components. It appears Samsung used whatever was on sale during that period of time of production
Sent from Mars via Curiosity
Bump, no love from the experienced cappy users, huh?
Sent from my SGH-I897 using xda premium
Related
Ok so this nook was bought brand new in December 2010 For my mother In-law. She hasn't used it much. So I asked if I could put Android on it? She said sure cause she hasn't used it at all. As a matter of fact the NC was totally dead when she gave it to me. So I get back to my house and put it on the stock charger. I let it charge for 2 hours. I picked it up and turn it on and all I see is this message: Battery too low to power ON. I did a search and turned up similar problems but the nc where all rooted. I'm wondering if other people have had this same problem? And what they did to solve this as it is more then likely an easy fix. A. Take it back to the store and exchange it. Or. B. Send it off for repairs. C. Someone On XDA has the answer.
Also I've done some trouble shooting like trying to reset it. Also I've used 3 Other chargers and its still not charging or turning on.
Edit: It turns on it just stays at the screen with a red battery displaying the message in the title. Also after charging for a while the screen kind of lites up like its going to turn on but only goes black after that and then comes back to the same red battery screen.
jvillejoe said:
Ok so this nook was bought brand new in December 2010 For my mother In-law. She hasn't used it much. So I asked if I could put Android on it? She said sure cause she hasn't used it at all. As a matter of fact the NC was totally dead when she gave it to me. So I get back to my house and put it on the stock charger. I let it charge for 2 hours. I picked it up and turn it on and all I see is this message: Battery too low to power ON. I did a search and turned up similar problems but the nc where all rooted. I'm wondering if other people have had this same problem? And what they did to solve this as it is more then likely an easy fix. A. Take it back to the store and exchange it. Or. B. Send it off for repairs. C. Someone On XDA has the answer.
Also I've done some trouble shooting like trying to reset it. Also I've used 3 Other chargers and its still not charging or turning on.
Edit: It turns on it just stays at the screen with a red battery displaying the message in the title. Also after charging for a while the screen kind of lites up like its going to turn on but only goes black after that and then comes back to the same red battery screen.
Click to expand...
Click to collapse
what are you charging from? are you using the stock nook cable and plug?
Yes. And charging it from the wall outlet. Did that with the stock charger. my charger from my HD2 and also tried with the charger from my vibrant. All have the same affect. It has the red battery and the messege below and it also has been a total of 6 hours of charging 2 hours each with the all the chargers.
That stinks. You may have to contact B&N for it. If your using the stock and other chargers then it must be a battery failure.
altimax98 said:
That stinks. You may have to contact B&N for it. If your using the stock and other chargers then it must be a battery failure.
Click to expand...
Click to collapse
Yeah seems to me thats what it must be I'll post back what I find out.
When that message is displayed, try holding the power button for 30+ seconds and then turning it back on.
That has worked for me the couple of times it seemed stuck on that screen.
RobertsDF said:
When that message is displayed, try holding the power button for 30+ seconds and then turning it back on.
That has worked for me the couple of times it seemed stuck on that screen.
Click to expand...
Click to collapse
Nope its not working at all. I was wondering is there an SD card that come with the NC bought brand new from B & N?
jvillejoe said:
Yes. And charging it from the wall outlet. Did that with the stock charger. my charger from my HD2 and also tried with the charger from my vibrant. All have the same affect. It has the red battery and the messege below and it also has been a total of 6 hours of charging 2 hours each with the all the chargers.
Click to expand...
Click to collapse
If you're using other chargers, it's possible that you've damages the usb port. The NC uses a non standard usb port, which has two stages. The first stage is standard 5 pin uusb communication, the second stage is non-standard 12 pin charging...
Sent from my Nexus One using XDA Premium App
Non-Standard chargers...
As far as I can tell it works fine with any microusb cord.
Their charger cables break...(bend and break) very easy. I have gone through 2.
The upside is that their charger provides power far faster than the normal microusb cords.
At this point...I'm charging mine almost exclusively from my stock evo cord.
If you don't turn off the screen when charging...it may not have enough power coming in to actually build a charge without their cable.
danger-rat said:
If you're using other chargers, it's possible that you've damages the usb port. The NC uses a non standard usb port, which has two stages. The first stage is standard 5 pin uusb communication, the second stage is non-standard 12 pin charging...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I never used another charger besides the stock charger that came with the NC. Up until this happened all that was ever used was the stock cable for charging. I only used another charging cable once I ran into these problems cause I figured the cable was damaged. Its happened to me before with other devices. But the same results happen with every cord I use. When I plug it in it lights up and shows the red battery screen. So that tells me that the cord or USB port couldn't be the problem. Cause its clearly getting power its just not charging.
Fattychance said:
As far as I can tell it works fine with any microusb cord.
Their charger cables break...(bend and break) very easy. I have gone through 2.
The upside is that their charger provides power far faster than the normal microusb cords.
At this point...I'm charging mine almost exclusively from my stock evo cord.
If you don't turn off the screen when charging...it may not have enough power coming in to actually build a charge without their cable.
Click to expand...
Click to collapse
When charging I can not turn the screen off it's stuck on the screen with a red battery.
jvillejoe said:
Nope its not working at all. I was wondering is there an SD card that come with the NC bought brand new from B & N?
Click to expand...
Click to collapse
No. They sell it without one...the 8GB internal storage is enough for looooottts of books. The microsd was just a nice + for people with lots and lots of music.
I had this issue as well, but I found a fix!
No matter what I did or how long I let it charge, it would always have that red low battery icon.
What I ended up doing to fix it was opening up the back of the unit and disconnecting the battery cable from the unit. I then plugged it directly into the wall without the battery connected to see if it would boot, though I don't know if that was necessary, I don't even remember if it booted that way or not.. I think it did not.
Anyway I unplugged the power cable again, reconnected the battery, then plugged in the power cable and tried to boot and it booted up perfectly after that. The battery icon indicated 13% charge, but it quickly charged back up just fine.
FYI I left the unit in the car overnight right before this happened, and it was pretty chilly that night, 10-20 degreed Fahrenheit. I suspect that caused the issue for some reason, so I've been sure not to do so since.
P.S. I had to do a fair amount of googling around before I found good instructions on taking apart the NC. I think I had to take off the 2 screws under the SD card slot and use a butter knife to just pry the back off. It's just held in with clips and you can't tell it was opened except for the little stickers over the screw holes.
bstock said:
I had this issue as well, but I found a fix!
No matter what I did or how long I let it charge, it would always have that red low battery icon.
What I ended up doing to fix it was opening up the back of the unit and disconnecting the battery cable from the unit. I then plugged it directly into the wall without the battery connected to see if it would boot, though I don't know if that was necessary, I don't even remember if it booted that way or not.. I think it did not.
Anyway I unplugged the power cable again, reconnected the battery, then plugged in the power cable and tried to boot and it booted up perfectly after that. The battery icon indicated 13% charge, but it quickly charged back up just fine.
FYI I left the unit in the car overnight right before this happened, and it was pretty chilly that night, 10-20 degreed Fahrenheit. I suspect that caused the issue for some reason, so I've been sure not to do so since.
P.S. I had to do a fair amount of googling around before I found good instructions on taking apart the NC. I think I had to take off the 2 screws under the SD card slot and use a butter knife to just pry the back off. It's just held in with clips and you can't tell it was opened except for the little stickers over the screw holes.
Click to expand...
Click to collapse
Thanks for the feed back. I'm wondering by un-pluging the battery from the nook if it resets it. Kind of like if a phone freezes or if your computer freezes and you pull the battery. Seems like a plan. Not sure if this is what I'll do as I'm sure its still under warranty. If it comes back and its not covered or B & N wont replace it I guess thats my only hope.
im having the same problem as well it was off for a while and now its at the red batter screen. i guess ill try and take it apart?
CLMT said:
im having the same problem as well it was off for a while and now its at the red batter screen. i guess ill try and take it apart?
Click to expand...
Click to collapse
If your not worried about voiding the warranty then sure I guess its worth a shot.
So I got it fixed right. All it was was a faulty cable lol!
jvillejoe said:
So I got it fixed right. All it was was a faulty cable lol!
Click to expand...
Click to collapse
I had this problem too, but I'm not sure "faulty" is the right word for the cable.
My friend borrowed my nook and returned it with a dead battery (Thanks asshole). So I plugged it into my computer at work and just got the always-on low battery message. After 45 minutes I took it to my car so I wouldn't forget it. I plugged it into my USB charger in the car using a different cable. Two hours later, same state.
When I got home I pugged it into the Nook wall charger with yet another cable (not the nook's original) and got the same thing. I searched here to see if I could figure out what was going on and decided to try the original cable with the wall plug. literally two seconds after plugging it in it started booting into Froyo.
I'm sure I didn't have four "faulty" cables. I think those that are saying you should be using the original are correct. The others worked fine when the battery wasn't empty, but mine only responded to the original once it got to the point of the unending low-battery message.
Original charger / cable required with totally empty battery
Same here. With battery completely empty and non standard cable,stuck at red battery sign forever. With orginal cable, boots fine and charges.
solution I found
Have CM7 installed on SDCard, got the battery icon, even with the unit plugged into the charger with oem equipment. Held the power button 'til the unit turned off completely, removed the sdcard, rebooted. Nook booted into stock fine, turned off, re-inserted sdcard and rebooted. All is well.
Hey,
My Galaxy Note recently decided to stop charging. Whenever i plug the charger in it shows the "first white charging logo", the one you see before the green battery being filled up - after about half a sec the logo goes away only to return 5 seconds later.
I've tried to blow into the socket, and i've looked into it with a light to make sure nothing seems off, and everything looks perfectly fine. So far i have tried with 2 cables, one third party and the original one, no difference there. Both these cables work well with my Galaxy S2. Therefore i am willing to say for certain the problem is in the actual USB port, which i find weird because I've never mishandled it in any way.
Another thing is the battery gets warm after cycling like this for a few minutes. I tried to take the SGSII-battery and fire the Note up, by holding the battery in place according to the connectors, it fires up perfectly.
Do any of you have any experience with these kinds of issues?
I am currently running Paranoid Android Hybrid-ROM, I guess my only real option here would be to borrow a friends charged battery to flash back into a stock ROM and plead ignorance with the warranty claim. The phone is no older than 4 months. Does anyone know how thorough they are when placing an RMA on a phone?
Thanks, any input greatly appreciated.
AndrewXXV said:
Hey,
My Galaxy Note recently decided to stop charging. Whenever i plug the charger in it shows the "first white charging logo", the one you see before the green battery being filled up - after about half a sec the logo goes away only to return 5 seconds later.
I've tried to blow into the socket, and i've looked into it with a light to make sure nothing seems off, and everything looks perfectly fine. So far i have tried with 2 cables, one third party and the original one, no difference there. Both these cables work well with my Galaxy S2. Therefore i am willing to say for certain the problem is in the actual USB port, which i find weird because I've never mishandled it in any way.
Another thing is the battery gets warm after cycling like this for a few minutes. I tried to take the SGSII-battery and fire the Note up, by holding the battery in place according to the connectors, it fires up perfectly.
Do any of you have any experience with these kinds of issues?
I am currently running Paranoid Android Hybrid-ROM, I guess my only real option here would be to borrow a friends charged battery to flash back into a stock ROM and plead ignorance with the warranty claim. The phone is no older than 4 months. Does anyone know how thorough they are when placing an RMA on a phone?
Thanks, any input greatly appreciated.
Click to expand...
Click to collapse
Did you try to wipe your battery stat in recovery mode.
jonpaslim said:
Did you try to wipe your battery stat in recovery mode.
Click to expand...
Click to collapse
No I did not infact, I'll give that a go and see if it helps. The problem is the SGSII battery doesnt fit completely, so i need to hold it by force at the pins, not sure ill pull that off while entering the recovery menu, but i'll try and see!
Edit: Tried it and it did not help unfortunately. At least i can use the SGSII-battery to safely get into menus etc.
Hell, might even be a broken battery?
I interpret the problem as "charging starts but battery refuses.." since the 1st logo keeps flashing. I read elsewhere that it might be a moisture-related problem aswell.
This I do not disregard completely because the phone has been lying near an open window, even though it's summer it cannot be fully ignored.
Either way, in the other thread they suggest putting the phone in rice (which soaks up moisture) for a few days to see if it helps. I even put one of those silica-anti-moisture-bags in there with the rice. Fingers crossed.
If nothing helps I think I'll just borrow a mates charged battery to flash back into stock, get rid of evidence etc - and place it in RMA.
Why don't you try a new Note battery or from another Note. If it fired up with a Gs2 battery perfectly then it must be your battery!
Sent from my GT-N7000 using xda premium
Leave your phone without any battery for about 30 min., this helped me when my phone was refusing to charge somtimes and was giving me discharging while on the charger, after i pulled the battwry for about 30-45 min it is perfectly charging now, btw iam on paranoid also and my phone doesnt charge when it is turned off, have to turn it on frist to charge
Sent from my GT-N7000 using xda premium
easy fix
hey i had a similar problem...was a bit frightened at first....ok connect your phone to your computer, if the computer recognizes then you cables and USB port are just fine.....this means that your phone has some firmware issues....ok here's the simple fix......allow your battery to die completely, then remove the battery from the phone for about 30 minutes......plug in the charger with the battery still out of the phone for 30seconds....now unplug your charger, reinstall your battery into the device and connect your charger again.....this may also work if your device refuses to power on....
I'll start off by saying that I sell phones for a living, so I probably see a higher concentration of problems per phone. I'm a pretty big fan of the AHD and highly recommend it since I own one. Last week was just weird though.
Is anyone having an issue with their device just randomly powering off and not coming back on? Last week I had 5. Count it 5 AHDs come in the store that randomly powered off while being used with a charge and would not turn on. Most would show a green light when charging, but it would come and go. I used the power + volume button method to fix all but 2 of them. Absolutely stumped as to what's going on.
Any input guys?
You're saying it was plugged in and charging when the problem occurred? It may be that you are using the wrong charger. The charger that comes with the phone is rated for 5.1V output so you have to use that or plug it into a computer USB port. I had a weird issue that sounds similar to your problem when I inadvertently plugged my Atrix HD into a Samsung charger.
No no, I meant that the phone was charged, and that it didn't die because the battery went dead. They all claimed they were using factory chargers, and I know for a fact that one I couldn't revive was using a factory charger.
http://forum.xda-developers.com/showthread.php?t=1876036&highlight=green+light
maybe?
AzraelsVoice said:
I'll start off by saying that I sell phones for a living, so I probably see a higher concentration of problems per phone. I'm a pretty big fan of the AHD and highly recommend it since I own one. Last week was just weird though.
Is anyone having an issue with their device just randomly powering off and not coming back on? Last week I had 5. Count it 5 AHDs come in the store that randomly powered off while being used with a charge and would not turn on. Most would show a green light when charging, but it would come and go. I used the power + volume button method to fix all but 2 of them. Absolutely stumped as to what's going on.
Any input guys?
Click to expand...
Click to collapse
Mine had the same problem, but it started after I tried taking the battery out and ripped the connector on it. The battery wasn't the issue though, I tried two other batteries and had the same problem.. Sometimes it wouldn't turn on at all and just show the green led. I flashed the stock ics sbf hoping for something and It kept doing it daily for about a week but it slowly started doing it less and less. Now it just doesn't happen at all anymore. Very strange.
My nook was idle for a day or two, as I remember I hv shut it off.
But then yesterday I try to charged it, the light was green then turn to red, n then it went off, usually the nook would turn on right after I plug the charger. So I didn't notice it until today, and I tried to turn it on by pressing the power button, and the N button together as well, both didn't work.
It seems that I can't charge it or turn it on. Everytime I tried to re-plug it to power or press power button while its connected, the light went on in green to red then off again.
Sent from my GT-N7000 using xda app-developers app
Connect your charger. Let it stay on charger 20 min. Then try push n button. If this not bring screen on then try push power button for 5 sec. Again if not then try power and n button combination.
Hope this helps.
Thx! Turns out tht external charger didn't work.
Sent from my BNTV600 using xda app-developers app
I think that last opinion is make CWM sd card (without CM10) and insert it do device, then try to switch the device on (with charger trick or power button). If you then get it live all is ok. If not then last change is wait when battery goes empty and charger wakes it up.
Actually i predict that item is itself faulty and you must return it for change (maybe not faulty at hardware side, only OMAP inside code got corrupt).
I don't know, that might because I rooted my device, and I did sth wrong. Sometimes it would reboot itself, since my cmw card was inserted, it would load tht root page so I found out. But I live in Asia so returning the device might be too costly, probably won't do it.
Sent from my BNTV600 using xda app-developers app
ling_1118 said:
I don't know, that might because I rooted my device, and I did sth wrong. Sometimes it would reboot itself, since my cmw card was inserted, it would load tht root page so I found out. But I live in Asia so returning the device might be too costly, probably won't do it.
Sent from my BNTV600 using xda app-developers app
Click to expand...
Click to collapse
It could be several things. The most likely is it was trying to update itself and could not because the CWM card was there. I don't think your device is defective.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
It could be several things. The most likely is it was trying to update itself and could not because the CWM card was there. I don't think your device is defective.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Now i can say same. With first information things was other.
...It's more or less a known bug to those of us who use CM10 (even to some who use stock), the battery simply often can't tell how much she has left. So she may fluctuate from 1% to 26% to 0% a moment later . In one such moment my Nook HD+ shut down (went from 26% to 0%). So I put it up for charging thinking (naively) that it would boot up ... it didn't, now all I get is a charging icon that never goes away (orange led remains lit). What's more I *know* it has some charge (the "26%" was the right value) and I know the battery works, so what prevents it from starting is the "battery charge sensor".
It's a pretty silly way to lose your (my) tablet over. Even more so given how much I grew attached to it for my workflow. So what's next? Is there a secret way to convince it to boot. As I said both the hardware and its software is in top condition. I guess an alternative would be to ship it back for replacement but I'm afraid that I've lost my receipt and -as I said- it's a silly way to lose your tablet over, there *has* to be a (fast) way out...
BTW when connected to my PC my device manager briefly shows an "Omap 4470" unknown device (with an exlamation mark) which goes away few secs later, so I cannot attain ADB control over my devices either (sadly)....
Stevethegreat said:
...It's more or less a known bug to those of us who use CM10 (even to some who use stock), the battery simply often can't tell how much she has left. So she may fluctuate from 1% to 26% to 0% a moment later . In one such moment my Nook HD+ shut down (went from 26% to 0%). So I put it up for charging thinking (naively) that it would boot up ... it didn't, now all I get is a charging icon that never goes away (orange led remains lit). What's more I *know* it has some charge (the "26%" was the right value) and I know the battery works, so what prevents it from starting is the "battery charge sensor".
It's a pretty silly way to lose your (my) tablet over. Even more so given how much I grew attached to it for my workflow. So what's next? Is there a secret way to convince it to boot. As I said both the hardware and its software is in top condition. I guess an alternative would be to ship it back for replacement but I'm afraid that I've lost my receipt and -as I said- it's a silly way to lose your tablet over, there *has* to be a (fast) way out...
BTW when connected to my PC my device manager briefly shows an "Omap 4470" unknown device (with an exlamation mark) which goes away few secs later, so I cannot attain ADB control over my devices either (sadly)....
Click to expand...
Click to collapse
If you are running CM10 or 10.1, there is an easy way to connect with ADB. Do it wirelesly over wifi. That is built into CM. Just enable it in the developer options. No need to mess with the USB cable and windows drivers. You can do the same thing with rooted stock by installing an app called ADBWireless.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
If you are running CM10 or 10.1, there is an easy way to connect with ADB. Do it wirelesly over wifi. That is built into CM. Just enable it in the developer options. No need to mess with the USB cable and windows drivers. You can do the same thing with rooted stock by installing an app called ADBWireless.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
At the time that could not happen , since (as I had implied) my nook was not booting to begin with...
Anyhow, what I did was to leave it for three solid hours on the charger, and after that period of time it booted on its own wiithout warning. It's the first that such behavior was/is ever present to my nook and it's deeply worrying. A battery fix for the CM kernel couldn't come any sooner; now, if only verygreen was around
There's a few ideas on a couple of other threads including putting it in the fridge, etc. Question, if you plug it in, does the charging light come on? Does it come on after pushing the power button or the N button? If so, take your SD out, leave it charging overnight and try again. It often reboots when in this state and if there's an update problem, that could be the issue. Also, it is sometimes erratic on when and how it charges, be careful with the connections.
dbh369 said:
There's a few ideas on a couple of other threads including putting it in the fridge, etc. Question, if you plug it in, does the charging light come on? Does it come on after pushing the power button or the N button? If so, take your SD out, leave it charging overnight and try again. It often reboots when in this state and if there's an update problem, that could be the issue. Also, it is sometimes erratic on when and how it charges, be careful with the connections.
Click to expand...
Click to collapse
As I said it came up on its own, without warning after leaving it for 3 hours on the charger...
As for your question, the led (charging light) was on all the time but it would only show me that it had no battery (couldn't charge even though it was ... charging?)
Maybe the fridge makes sense in those situations, as it was indeed into a (relatively) hot environment and maybe it couldn't charge as a safety against overheating and since (at the same time) it also thought it had 0 battery. But what I can't understand is why needed 3 hours before starting to charge up, it was already cool enough long before ... strange things are/were happening with my battery all along and I worry...
Stevethegreat said:
As I said it came up on its own, without warning after leaving it for 3 hours on the charger...
As for your question, the led (charging light) was on all the time but it would only show me that it had no battery (couldn't charge even though it was ... charging?)
Maybe the fridge makes sense in those situations, as it was indeed into a (relatively) hot environment and maybe it couldn't charge as a safety against overheating and since (at the same time) it also thought it had 0 battery. But what I can't understand is why needed 3 hours before starting to charge up, it was already cool enough long before ... strange things are/were happening with my battery all along and I worry...
Click to expand...
Click to collapse
Yep, I've noticed the same thing a few times. It no longer panicks me. When it doesn't turn on, I take out the SD, plug it in, wiggle the connector a few times, and let it alone. So far, it has always eventually rebooted, often as you say on its own. Quirky, but not fatal at least. One poor guy on here never did get his to turn on, but the key was the charging light,his didn't come on.
Need help cannot turn on Nook HD+ at all
Hi!
I cannot turn it on at all and it won't reboot.
It went out some point I didn't watch it. When I connected it to the charger the LED next to the connector starts blinking amber and green for a few seconds and then stays blinking red and makes a high pitched noise.
The only reaction I get is when I press power on an volume down after some time - it display turns on an shows a charging sign - but it never really seems to fully charge. I left it on the charger over night - still the same. Once the display blinked and showed “nook” but went out immediately after a few milliseconds.
Might it be some kind of bootloop!?!?
What combination to press to make a reset?
Thanks in advance for any help
Medizinmann
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
DroidGuy321 said:
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
Click to expand...
Click to collapse
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally: https://www.amazon.com/gp/product/B00S7IBDGW/ref=oh_aui_search_detailpage?ie=UTF8&psc=1.
Also, are you unlocked? If so, what battery percentage does TWRP say?
TheSt33v said:
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally:
Also, are you unlocked? If so, what battery percentage does TWRP say?
Click to expand...
Click to collapse
Thanks for the quick reply. It does seem like a battery problem, however it is just so coincidental that it stopped working after I let the battery drain to 0%, when only hours previously it was in use and charging without any issue at all.
Also, if there was a problem with the micro-usb port, I would think that a computer wouldnt be able to read the phone, but when I plug it in it is recognized as an ADB device.
I have another turbo with a cracked screen, I'm thinking about dissecting both and putting that battery in this phone as a replacement.
And unfortunately I am not unlocked :/.
Update
Well, after some further experimentation, I've gotten it working again. The solution was to charge it for like 5 hours, then let it sit off charge for an hour, and then it would boot... bizarre combination of actions. It has since dies twice and I've had to use this method.
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
DroidGuy321 said:
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
Click to expand...
Click to collapse
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
mrkhigh said:
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
Click to expand...
Click to collapse
Septfox said:
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
Click to expand...
Click to collapse
Thanks for the pointers. So strange, first it died at 40%, then 30% then 15%. Now, it is still dying early but I am no longer facing the issue I originally had, it will show normal charging when off, and boots up right away. Sure hope its not some ticking battery time bomb, its still a relatively new refurb.
I attempted the charge calibration so we shall see if it helps. I also did a factory reset for the hell of it, since I am on stock and can't reflash. Perhaps I'm in the clear, that would be awesome. Still no idea what the issue was in the first place though, which will annoy me to no end.