Just installed CM9 A0.6. All looks nice except it will not charge. It quickly ran out of battery even with charger connected.
Any suggestions?
Check your charging wall wart - make sure it didn't spin loose. If that's good did you try a reinstall? clear cache and your user settings flash again?
Yeah, I noticed that also. It does charge on WebOS though. So I just switch over to that when I need to charge the device.
rgwebster said:
Just installed CM9 A0.6. All looks nice except it will not charge. It quickly ran out of battery even with charger connected.
Any suggestions?
Click to expand...
Click to collapse
Boot back to webos if u can. or u could have real trouble according to other threads about tp not charging.Then try a different rom and see or even flash cm9 again.
It charges fine when I boot into webOS, so the connections are fine. i have tried to re-flash the rom, but it still does not charge.
Still experimenting...but it may be due to flashing the rom with the charging cable attached. I re-flashed after removing the cable, and it looks to be charging now. Fingers crossed
One of the bugs in CM9 Alpha 0 is that the tablet charges very slowly. But there’s already a fix for that. You can download the update-chargerFix-alpha0.zip file from goo-inside.me(Sorry wont let me put url since I am a "Noob")
"goo-inside.me/roms/teamdouche/tenderloin/alpha"-url
1.Place the zip file in the root directory of your TouchPad’s storage (or in a folder that you can remember).
2.Press-and-hold the power button to reboot the touchPad.
3.From the Moboot menu, choose ClockworkMod.
4.Use the volume keys to scroll down to the entry that says “install a zip from SDcard” and tap the home button to select.
5.Using the volume and home keys, highlight the update-chargerFix file and select it.
6.Scroll down to select yes.
7.When it’s done installing reboot into CyanogenMod.
My wife's TP is doing the same thing. Mine isn't. What I did to help her was to install Cyboot from webOS nation through preware.
With Cyboot you can set it to boot into webOS rather than cm9. Also, the time can be set up to 9 seconds.
When she plugged the charger in and then left it, it would turn on and boot into cm9. For some reason the TP in cm9 drains the battery faster than it charges. Now it boots into webOS and charges.
Sent from my DROIDX using XDA App
I have the same issue with mine in CM9.0a6. After running it down the first time, I had to boot to WebOS to recharge to 100%.
I rarely unplug it (using it as a wall-mounted slate more than anything), and CM has no troubles keeping it at 100% or charging it to 100% from being off the charger for a few minutes. I'd imagine there is a point of no return, though, that once you hit won't permit a full recharge in CM.
Same issue here; installing the charge fix caused some error n couldnt boot try using ice buttah n same issue...
Still having an issue with this.
I believe it has something to do with booting up with the charger plugged in.
If I boot-up when it is not plugged-in I can subsequently attach the charger and it will charge.
However if the charger is plugged-in during the boot-up it will not charge and will eventually completely discharge.
It then becomes impossible to re-start cos you are forced to re-boot whilst charging....with the consequent inability to charge.
Catch 22
Related
Rooted using Indirect's sd method, installed CM7 to internal using clockwork mod. I installed CM7 around tuesday, and nothing happened for a while. Then, I woke up this morning to try and do stuff with it and it booted up fine. My touchscreen was acting wonky (a hardware problem) so I turned it off to reboot, and when I went to turn it back on it got to the CM7 splash, and turned off and rebooted itself. It kept doing that for a while, and I let the battery run out. I then plugged it into my PC and it gets to the "N" screen (where it says powered by adobe reader technology or whatever) and it reboots. It has not gotten past that screen. It makes my computer spaz out by starting the "Found New Hardware" wizard for "OMAP4430". I have no idea what that is. My computer then thinks I am unplugging the Nook and plugging it back in (It makes that sound when you unplug a USB and plug it back in). Any help would be appreciated.
TL;DR My nook is in what I think is a bootloop, I can't access the internal storage from a computer, omfgwtfbbq.
EDIT: I have taken my SDcard out, that was suggested earlier. Could this possibly have something to do with the fact that I cleared all my SDcard contents from the CM7 options menu? I also cannot access my nook or SDcard by plugging it into my computer, I suspect that has something to do with the unplugging and plugging back in sound mentioned above.
off course will do this
My computer then thinks I am unplugging the Nook and plugging it back in (It makes that sound when you unplug a USB and plug it back in
Click to expand...
Click to collapse
because you have it plugged in to your computer so every time it reboots (bootloop) it unmount your sdcard and mount it again when it start to boot.
You should not "charge" it while plugged in your computer , charge it as normal with the adaptor for a while first (remove your sdcard better) once it's charged start troubleshooting it.
~ Veronica
lavero.burgos said:
off course will do this
because you have it plugged in to your computer so every time it reboots (bootloop) it unmount your sdcard and mount it again when it start to boot.
You should not "charge" it while plugged in your computer , charge it as normal with the adaptor for a while first (remove your sdcard better) once it's charged start troubleshooting it.
~ Veronica
Click to expand...
Click to collapse
Unfortunately, that's where I first figured out it was doing the bootloop thing. The sd card is not in the nook, and it's still in the loop while plugged into a wall adapter. It's almost like it doesn't have enough power to start up, but the charger is giving it just enough to get to the "N" screen.
Maggot226 said:
Unfortunately, that's where I first figured out it was doing the bootloop thing. The sd card is not in the nook, and it's still in the loop while plugged into a wall adapter. It's almost like it doesn't have enough power to start up, but the charger is giving it just enough to get to the "N" screen.
Click to expand...
Click to collapse
No bootloops are cause more for a software issue, and sometimes sdcard can be the root of the problem.
let it charge for an hour at list. Then turn it off boot into CWM and see if you can flash the ROM again. Report back if you get any error while trying to use CWM as normal but please do not take the plunge to format everything you find in there or you will regreat it.
It is safe to wipe data, cache, dalvik cache and format system... that is your limit.
~ Veronica
lavero.burgos said:
No bootloops are cause more for a software issue, and sometimes sdcard can be the root of the problem.
let it charge for an hour at list. Then turn it off boot into CWM and see if you can flash the ROM again. Report back if you get any error while trying to use CWM as normal but please do not take the plunge to format everything you find in there or you will regreat it.
It is safe to wipe data, cache, dalvik cache and format system... that is your limit.
~ Veronica
Click to expand...
Click to collapse
That's the problem, it can't charge. As soon as it gets enough juice to power on, it uses all of it and powers down again.
It's been charging, from a wall charger, with the sd card out, for around 4 hours now and it's still doing the loop thing.
Maggot226 said:
That's the problem, it can't charge. As soon as it gets enough juice to power on, it uses all of it and powers down again.
Click to expand...
Click to collapse
This happened to me a while back. You just have to leave it alone for a while, and it will eventually (~20 minutes or so) power on correctly.
ckevinwelch said:
This happened to me a while back. You just have to leave it alone for a while, and it will eventually (~20 minutes or so) power on correctly.
Click to expand...
Click to collapse
Leave it alone as in unplug it from the charger? Or keep it charging?
Maggot226 said:
Leave it alone as in unplug it from the charger? Or keep it charging?
Click to expand...
Click to collapse
Plugged in.
Left it alone unplugged (After leaving it plugged in for around 3 hours) and it appears there is absolutely no juice left in it. I reinstalled CWM on my SD card and put CM7 on my brother's Nook, and now I'm waiting to see if CWM will boot... Crossing my fingers.
Maggot226 said:
Left it alone unplugged (After leaving it plugged in for around 3 hours) and it appears there is absolutely no juice left in it. I reinstalled CWM on my SD card and put CM7 on my brother's Nook, and now I'm waiting to see if CWM will boot... Crossing my fingers.
Click to expand...
Click to collapse
So you're saying it would not boot after leaving it alone (plugged in) for three hours? I'm assuming you were plugged into the stock charger and cable? Perhaps try plugging into a PC for a while. I'd also try turning it on while plugged in (if you didn't already).
ckevinwelch said:
So you're saying it would not boot after leaving it alone (plugged in) for three hours? I'm assuming you were plugged into the stock charger and cable? Perhaps try plugging into a PC for a while. I'd also try turning it on while plugged in (if you didn't already).
Click to expand...
Click to collapse
It would turn on, but yes, it would not boot to the menu. It wouldn't get past the "N" screen as stated in the OP. I was plugged into the wall charger and using the cable I received with the Nook. I've had it plugged into the computer for around a half hour, and I have attempted to turn it on with no success. I'm really wondering what this "OMAP4430" thing is. My computer is wanting to find software for it, the "Found New Hardware" wizard starts up every time I plug my nook in.
It's fixed, I let the battery run completely out, booted from CWM and wiped everything. I reinstalled CM7 and it's working like a charm. Mods can lock this thread.
Hello everyone,
I have an SGP 5.0 that I've been using for sometime. Everyday I let it charge overnight and usually in the morning its warm but full. Today it was burning hot and the device keep on boot loading and failing. I've tried going into recovery mode but it fails completely, I just keep going into the boot looping. Download mode works but that's about it. The device was working yesterday with no problems with the rom/kernel listed in my signature.
If I disconnect the power cable and leave it disconnected it will NOT boot. Not even into download mode. Only when I plug in power and leave it for a minute will it try to boot.
I've tried writing the rom and kernel (http://forum.xda-developers.com/showthread.php?t=1863004) but it dies before it ever finishes (By die I mean the battery runs out). I've pushed only the kernel (Entropy's DailyDriver) and it does work but its still boot looping.
I've stopped the above and the device is getting hot. I presume if left without a kernel/rom that it will recharge and I can continue what I'm doing? (The download logo stays on for about a minute and disappears and appears a minute later repeatedly. )
Just so you know, when you flash CM10 (Paranoid, or just Cyan) that these flashes provide a new kernel, hence that you do not still use the daily driver from Gingerbread. You'll probably notice the different in CWM changes from five to version six.
With that said, it might be best if you tried adjusting your voltage, I've had the same issues with an over heated device with Gingerbread / CM10 modifications which a member of the community did offer some assistance ( Check Page 75 on Cyan Thread)
Wouldn't hurt starting from scratch, flashing the stock, and working your way back up. Only suggesting this because I'm unsure of other factors that could cause this.
I forgot about that since I went from PM 4 to PM 4.1. That's what my goal was by starting with galaxy_player_2.3.6.tar.md5 and working up but I got nothing since the device dies, from no power?, when I try to write a rom. I guess I have no choice but to charge the device and hope that after many boot loops, the battery have enough juice for one run? That being said I've just opened the device and figured out how to remove the battery.
Google isn't helping with batteries and a quick search of ebay shows that everyone is happy with their device. Is there any place you recommend to get a new or semi-new battery for the thing?
By Write your referring to flashing.
Have you been able to get into the download mode? What do you also mean by recovery fails?
Yes. Download mode works fine. As I've stated the device will stay on for just one minute before it dies, not enough time to flash on a new rom. If I pull the plug, regardless of if I'm flashing, it will die. By die I meant that the device shuts off. The screen is black and the backlighting on the buttons is off.
I've held the power + volume up button on boot and it kicks into download mode.
I've left the device plugged it and its generating a lot of heat, with battery inside.
UnsignedZero said:
Yes. Download mode works fine. As I've stated the device will stay on for just one minute before it dies, not enough time to flash on a new rom. If I pull the plug, regardless of if I'm flashing, it will die. By die I meant that the device shuts off. The screen is black and the backlighting on the buttons is off.
I've held the power + volume up button on boot and it kicks into download mode.
I've left the device plugged it and its generating a lot of heat, with battery inside.
Click to expand...
Click to collapse
Are you using the stock cable? This device is super picky about cables, I'm actually talking to a samsung product support agent right now asking for a new cable. Mine shows the initial battery/charging screen, then reboot, ad infinitum. Does this happen to you?
bmxer4130 said:
Are you using the stock cable? This device is super picky about cables, I'm actually talking to a samsung product support agent right now asking for a new cable. Mine shows the initial battery/charging screen, then reboot, ad infinitum. Does this happen to you?
Click to expand...
Click to collapse
Mine also shows the charging screen then bootloops. If I powerdown my GP5 then plug in the cable, everything works fine. So for me it only performs reboots if I powerdown the device while it is plugged in.
bmxer4130 said:
Are you using the stock cable? This device is super picky about cables, I'm actually talking to a samsung product support agent right now asking for a new cable. Mine shows the initial battery/charging screen, then reboot, ad infinitum. Does this happen to you?
Click to expand...
Click to collapse
I haven't had any issues with any cables used. I've switched to stock cable + stock charger yesterday and nothing there but a boot loop. I wish there was a place to buy a new battery just to check.
I'm not sure what happened. My US Galaxy Player was working fine yesterday, but this morning when I went to wake it from sleep it was acting like it had a dead battery. I plugged it into a charger and rebooted it, and the battery manager said I had 45% charge. I unplugged it and it shut down. Not a soft shutdown, like when you select the option from the power menu, but a hard shutdown, like when you pull the plug on a computer.
I'm running the ROM, Kernel, and GApps found here: http://forum.xda-developers.com/showthread.php?t=2264671
(the first two downloads)
It's been a few days since I last flashed it, so I'm wondering if there might be a hardware issue.
PS: I also am noticing that when I do power it on while plugged into the wall, it skips the Samsung Galaxy S & CyanogenMod screen (and the one before that, I can't remember what it says), and goes straight to the CyanogenMod loading wheel. Every time I've tried to start it up, I've been unable to do so before it shows the Battery Charging icon (for charging when shutdown). I haven't noticed an animation for the charging icon, but my Player is now reporting that it's at 60% charge, so it seems to be working.
I've tried leaving the microUSB end of the charging cable in and unplugging the wall part, but it shut down as well (not totally unexpected, but I'm asking for help so I figure I should include as much info as possible).
Thanks in advance for any help you can give!
Fixed it (at least for now). Re-flashing the kernel was all it took.
JUST FYI
AFAIK, All of the newer kernels out there for the YP-G70 have this problem where, if you boot your device plugged in and then unplug it, it shuts off. If you boot your device not plugged in and then plug it in afterwards it's fine. I could be wrong but I think it's a problem in the kernel that everyone is using for a base (CM 10.1) . It's not really that big of a deal but it's something to keep in mind.
Boot with cable connected -> Shutdown before disconnecting cable.
Boot without cable -> Everything is normal...
I wanted to share this experience in case it happens to anyone else. I rooted my nook tablet and installed CM and everything worked great. This is a full install to the OS, not running from SD card at all, no SD card present. However, the battery ran low into the red zone and shut down the tablet. I plugged it in and it tried to start up without me even hitting the power button, as if it was in deep sleep and tried to wake up when it saw power. But, because it didn't have enough juice it would only get to the CWM menu screen and it would power cycle and start over again. I did the power/volume reset but that wouldn't shut down the tablet completely because every time I would plug it in it would try to restart again. Finally I was able to get it to run long enough to get to the CWM recovery menu and quickly choose power down option at which point it began charging without trying to restart. After I let it charge for an hour it reached about 60% at which point it started fine and has been fine since. It's a reminder to not let the battery drain too low because I'm not sure if this was a one time thing or if it is going to happen every time the battery drains low.
I had the same issue, my solution was to keep powering it on until it drained the battery completely. Finally I got a warning message that the batter charge was too low to power up. At this point you can plug it into the charger and it won't try to auto start.
I have a similar (maybe the same issue). But I have an additional one, because I am using a SD card. 2 Things to care about:
1. Use a powerful enough charger and just plug it in, it might boot cycle automatically, but at some point it will boot correctly... For me the charger of my Motorola Defy (850mA) with the original Nook charging cable works.
2. Leave the SD card removed while booting (I just "click" on it, so it is removed but still "connected" to the case), otherwise I also just get never-ending boot cycles for some reason - but maybe this SD card is "partially bootable" for some reason (though I never used it as a bootable SD card...)
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.