[Q] CM9 Battery Stuck - Motorola Droid X2

hi everyone i looked around but couldnt find anything on my problem. i installed CM9 beta 1 on my x2 last night and love it. it has ran great all day today and the battery did decent holding up. when i put it on charge it wont go past 50% and when i take it off charge and use it it doesn't fall below 50%. any ideas?

DieselJunkie88 said:
hi everyone i looked around but couldnt find anything on my problem. i installed CM9 beta 1 on my x2 last night and love it. it has ran great all day today and the battery did decent holding up. when i put it on charge it wont go past 50% and when i take it off charge and use it it doesn't fall below 50%. any ideas?
Click to expand...
Click to collapse
Try to battery pull unplugged and turn it on, then plug in see if it goes any higher. If it doesn't change try it a few more times. If still no change redownload the rom and gapps and do flash it again. Then let me know what it does.

s.morgan0310 said:
Try to battery pull unplugged and turn it on, then plug in see if it goes any higher. If it doesn't change try it a few more times. If still no change redownload the rom and gapps and do flash it again. Then let me know what it does.
Click to expand...
Click to collapse
Thank you for that i tried the battery pull a bunch of times and it didnt work. so i re-flashed everything and that seemed to work thank you!!

Related

[Q] SGS2 died?

I am the (un) lucky owner of a sgs2 since three days.
past days everything was fine, no probs. at all. Then this morning my phone isnt responding at all. wont go on, tried battery pull en stuff, nothing works. Is it possible it is broken after only 3 days?
are there any other tricks? anyone has the same problem?
or do i just have to go back to the store and get a new one? (problem is i bought it online so it will take a couple days for a new one )
thanks.
mathijsalbrecht said:
I am the (un) lucky owner of a sgs2 since three days.
past days everything was fine, no probs. at all. Then this morning my phone isnt responding at all. wont go on, tried battery pull en stuff, nothing works. Is it possible it is broken after only 3 days?
are there any other tricks? anyone has the same problem?
or do i just have to go back to the store and get a new one? (problem is i bought it online so it will take a couple days for a new one )
thanks.
Click to expand...
Click to collapse
Hold volume down, home and power all at the same time, it should boot into download mode. If it doesn't I'd say it's dead
i tried but wont work...
thats f*cked up
mathijsalbrecht said:
i tried but wont work...
thats f*cked up
Click to expand...
Click to collapse
Take/send it back to where ever you bought it from and get a refund/exchange, I think you're right, it's f***ed
mathijsalbrecht said:
tried battery pull en stuff
Click to expand...
Click to collapse
i don't know if you tried this in the part "en stuff", but did you try to charge the phone? maybe the battery drained out over the night...
m4nu said:
i don't know if you tried this in the part "en stuff", but did you try to charge the phone? maybe the battery drained out over the night...
Click to expand...
Click to collapse
Yeah that's probably a pretty good idea actually mate, try charging the thing before you make a total arse of yourself in the shop
did you charge the battery?
try another battery
LOL my SGS2 just did the same thing. I was gonna reboot it after having played around with default homescreen in default.prop, it had a 100% charged battery and now it won't start up again. Its completely dead. Not even download mode works...
Gonna try to leaving it without battery for a while or drain the battery somehow (with my tounge ) and try again. If that doesn't work, it's back to the store with this one. And it was all working so well until now...
EDIT: One hour later it magically started working again!!! I didn't do anything! just left it with the battery plugged in!
thnx im going to try charging it for a day, but i think its completely dead...
My brother's just told me that his S2 has died... he's not been able to get a 3G signal all day, and when he hard-reset the phone, it's come back with "Processing Error" and won't start.

[Q] Problem Booting

I have been running Das Bamf 1.7 Stripped no for quite some time without any problem, but recently I have been having quite a few random reboots. This morning I try to turn my phone on and It will not respond. This has happened before and all I had to do was plug it into the charger for a few minutes and then do a battery pull and it would start up. I tried that and all that it will do is give a small vibration and then do nothing.
Any help is appreciated.
I would try leaving it plugged in for like an hour and then give it a shot to see if it'll start up. The problem is every reboot eats a good percentage of battery so if you have enough of them you'll pretty much drain it down to where it will not power on.
I had this issue a long time ago but after leaving it plugged in for about an hour I was able to bring it back up easily.
Its kernal related
trentreed said:
Its kernal related
Click to expand...
Click to collapse
please enlighten us oh great one...
Hey, i am using thory GB rom lastest release 3.5.1 and it works perfectly but when i did the speedtweak.sh and set it to extreme my phone will not boot now it stays stuck at HTC and reboots itself but never goes past it how could i fix this please.
Was there a resolution?
No. I finally was able to boot into recovery and i deleted the kernel and re installed it and it finally booted back up idk why that did that if the speedtweak.sh preset settings should be safe.

100% Bricked ?!

Here's how it happened :
Flashed latest Dorimanx kernel last night on the latest Disaster Rom and then began texting,watching some youtube,usual stuff and then went to sleep.
In the morning I couldn't turn it on.
Then I hold the power button but it went bootlooping and kept staying on that Dorimanx starting image.
I succesfully booted and it showed battery at 9% ( it was at 90% when I went to bed).
My first thought was to wipe cache so I did that.But here's the problem.
It got stuck at wiping cache and nothing happened so I removed the battery and then it was dead.No sign of life.
So my question is: It's completely bricked and I can get it returned whitout them knowing that I have been using custom ROM's ?
Cheers
alex6vasy said:
Here's how it happened :
Flashed latest Dorimanx kernel last night on the latest Disaster Rom and then began texting,watching some youtube,usual stuff and then went to sleep.
In the morning I couldn't turn it on.
Then I hold the power button but it went bootlooping and kept staying on that Dorimanx starting image.
I succesfully booted and it showed battery at 9% ( it was at 90% when I went to bed).
My first thought was to wipe cache so I did that.But here's the problem.
It got stuck at wiping cache and nothing happened so I removed the battery and then it was dead.No sign of life.
So my question is: It's completely bricked and I can get it returned whitout them knowing that I have been using custom ROM's ?
Cheers
Click to expand...
Click to collapse
Did you tried to charge it for at least 20 minutes?
If it won't charge, try to replace battery...
Bootloop is not a big deal (wipes will do the job) try replace/charge battery first, then if you still have problems just flash stock via odin and start over...
What I'm trying to say it's that it doesn't show any sign of life.No download mode,no recovery,no nothing.
I've left it with the charger plugged in for about 3 hours and nothing.
alex6vasy said:
What I'm trying to say it's that it doesn't show any sign of life.No download mode,no recovery,no nothing.
I've left it with the charger plugged in for about 3 hours and nothing.
Click to expand...
Click to collapse
check the battery voltage, and or charge the battery externally. make sure its not a power issue first.
And what we're trying to say is try another battery. If that doesn't work, finita la musica.
alex6vasy said:
What I'm trying to say it's that it doesn't show any sign of life.No download mode,no recovery,no nothing.
I've left it with the charger plugged in for about 3 hours and nothing.
Click to expand...
Click to collapse
MistahBungle said:
And what we're trying to say is try another battery. If that doesn't work, finita la musica.
Click to expand...
Click to collapse
Yoh. It happened to me before. Some said charge your phone for a while. If it becomes warm near the battery, you can unbrick it a jig.
But my phone didn't get warm. So, I send it to the Samsung service center and yesterday I got it back.
Samsung messed with me for two times! I'm not going to buy another samsung.
That's nice. I've had my phone 15 months & had zero problems with it. Funny about that (there's a hint in there for people clever enough to figure it out).
kl13710 said:
I'm not going to buy another samsung.
Click to expand...
Click to collapse
kl13710 said:
Yoh. It happened to me before. Some said charge your phone for a while. If it becomes warm near the battery, you can unbrick it a jig.
But my phone didn't get warm. So, I send it to the Samsung service center and yesterday I got it back.
Samsung messed with my life for two times! I'm not going to buy another samsung.
Click to expand...
Click to collapse
They make the best phones.You could maybe try another brand.
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
{go back to your iphone since you are an android noob}
kl13710 said:
Yoh. It happened to me before. Some said charge your phone for a while. If it becomes warm near the battery, you can unbrick it a jig.
But my phone didn't get warm. So, I send it to the Samsung service center and yesterday I got it back.
Samsung messed with my life for two times! I'm not going to buy another samsung.
Click to expand...
Click to collapse
Get a Nokia 3310, It should be more suited to you.
Oh, you bought it.........
{go back to your iphone since you are an android noob}
Do This
Hey no worries bro I have bricked 2 sgs2's already and 1 sgs3. Yours is not bricked, happened to me as well. All you must do is connect usb to pc, while keeping the battery out. Then try turn it on normally. then, while it is on, insert your battery again and leave it to charge via usb for a while(tille batt is at least 85%, what I did). Then, before unplugging usb, turn phone off. Unplug usb and go into recovery and flash as per usual. You should be good now. Hope it helps.
kicker09 said:
Hey no worries bro I have bricked 2 sgs2's already and 1 sgs3. Yours is not bricked, happened to me as well. All you must do is connect usb to pc, while keeping the battery out. Then try turn it on normally. then, while it is on, insert your battery again and leave it to charge via usb for a while(tille batt is at least 85%, what I did). Then, before unplugging usb, turn phone off. Unplug usb and go into recovery and flash as per usual. You should be good now. Hope it helps.
Click to expand...
Click to collapse
Tried but no luck

[Q] Phone randomly turns on and off after mod

Hello all. So here is my situation.
Motorola Milestone X2
Last night I successfully rooted the phone and installed CMOD 10 using these directions
http://forum.xda-developers.com/showthread.php?t=2101633
Everything went fine. Charged the phone overnight, went for a jog this morning running both Pandora and c25k app. Absolutely no issues.
So I get to work and the phone just shuts off. Will not power back on or into fastboot. When plugged into USB, green light comes on.
After several minutes it will randomly power back on. Then after using it for a few minutes, it will just shut off again. Powering on and shutting down seems to happen randomly.
Any suggestions? Thanks in advance
doogie87 said:
Hello all. So here is my situation.
Motorola Milestone X2
Last night I successfully rooted the phone and installed CMOD 10 using these directions
http://forum.xda-developers.com/showthread.php?t=2101633
Everything went fine. Charged the phone overnight, went for a jog this morning running both Pandora and c25k app. Absolutely no issues.
So I get to work and the phone just shuts off. Will not power back on or into fastboot. When plugged into USB, green light comes on.
After several minutes it will randomly power back on. Then after using it for a few minutes, it will just shut off again. Powering on and shutting down seems to happen randomly.
Any suggestions? Thanks in advance
Click to expand...
Click to collapse
Quick update. It is draining the battery. The next time it booted up I watched carefully, and the red light in the corner was flashing and it said 5% battery, even though it had a full charge just a couple of hours ago. Something must be draining it badly if it will not even run very long while plugged in. Again, any fix for this would be greatly appreciated.
doogie87 said:
Quick update. It is draining the battery. The next time it booted up I watched carefully, and the red light in the corner was flashing and it said 5% battery, even though it had a full charge just a couple of hours ago. Something must be draining it badly if it will not even run very long while plugged in. Again, any fix for this would be greatly appreciated.
Click to expand...
Click to collapse
SBF back to stock and see if it still does the random power downs. If it still does than I'm sorry to say but its your phone
TheTechnicalBoss said:
SBF back to stock and see if it still does the random power downs. If it still does than I'm sorry to say but its your phone
Click to expand...
Click to collapse
Is there a reason to think that flashing to CMOD 10 actually broke the hardware? I have never had battery issues before. SBFing back I am sure would resolve the issue but then what?
And I am not talking "I used to get 12 hours, now I get 10" I am talking "I used to get 12 hours, now I get 12 minutes."
Even when plugged in, if I use it very much, it will die. Surely this is an issue of the phone incorrectly reporting the battery levels. I ran the battery calibration app (not at 100% charge since I cannot seem to get it that high) and it seemed to have no effect.
When I try to have the OS boot into recovery to try clearing the battery data, I just get an icon that look like the little android guy standing in front of a caution sign.
doogie87 said:
Is there a reason to think that flashing to CMOD 10 actually broke the hardware? I have never had battery issues before. SBFing back I am sure would resolve the issue but then what?
And I am not talking "I used to get 12 hours, now I get 10" I am talking "I used to get 12 hours, now I get 12 minutes."
Even when plugged in, if I use it very much, it will die. Surely this is an issue of the phone incorrectly reporting the battery levels. I ran the battery calibration app (not at 100% charge since I cannot seem to get it that high) and it seemed to have no effect.
When I try to have the OS boot into recovery to try clearing the battery data, I just get an icon that look like the little android guy standing in front of a caution sign.
Click to expand...
Click to collapse
cyanogen 10 has issues on our phone. plain and simple. also check the battery stats and see whats running. i had an issue once with facebook running 99% of the time consuming way too many resources. id sbf and try again from stock. if theres still issues try running cm9 it runs nicely and its my daily driver.
...............................
Lorenzo VonMatterhorn said:
cm9 is a bit better in quite a few aspects. i would try it over cm10. for battery life alone. i have stayed on it the longest now, surpassing eclipse, which used to be my favorite. :good:
---------- Post added at 12:15 AM ---------- Previous post was at 12:13 AM ----------
battery life on cm10 is absolutely horrible. it will never be anything close to stock, and you will be lucky if you can get it to last you a whole day. even when working properly.
Click to expand...
Click to collapse
Not necessarily, I've gone two days with 3g radio on but with minimal use on cm10 it really just depends on the hardware variations. Just like how two phones of the same model over clock differently because of minor flaws and variations durring manufacturing.
Sent from my Nexus 7 using XDA Premium HD app
So I was finally able to get it to charge to 100% and then used the battery calibration app.
I could not tell immediately if that did anything, but it seems to be holding its charge today. Guess we will see how it does over the next couple of days.
Thanks!

[Q] DNA boots to recovery, battery dies, reboots to recovery

So I'll start off by saying I'm on Cyanogenmod 11.0 12/15 nightly, running CWM 6.0.4.5, and crpalmers kernel for nightlies 5.2.11.
While trying to take a picture today my phone turned off (had 50% battery left) and would not turn back on. When I plugged it into power it took a little while to power on, as if the battery was dead. When it finally turned on it booted to recovery, stayed on for a bit then turned off before I could do anything. When it restarted again I tried to re-install the rom but it died again before it could start. So i figured i would just keep it turned off and let it charge. As soon as I plug it in, it boots. Plug it into the computer, same thing. Any ideas???
Update: So I found a more powerful charger, 1150mV over a 1000mV, and that was enough to keep the screen on and charge the battery enough to let the phone boot normally. But now the phone only stays on for about 20 min before it reboots. Still not sure whats going on but atleast it boots.
Sounds like a bad battery to me.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Yeah that's what i was thinking. Strange considering it was a warranty phone.
i have the same problem do you fix it ?
GaMaRS said:
i have the same problem do you fix it ?
Click to expand...
Click to collapse
Once I let the battery charge fully I just returned back to stock. The how-to is in the forum some where, I can find it later but I'm on my way out the door. As of right now I'm s-off but completely stock and seems to be working fine. Maybe try a different kernel first and see if that helps.
steve013 said:
Once I let the battery charge fully I just returned back to stock. The how-to is in the forum some where, I can find it later but I'm on my way out the door. As of right now I'm s-off but completely stock and seems to be working fine. Maybe try a different kernel first and see if that helps.
Click to expand...
Click to collapse
it's my problem http://forum.xda-developers.com/showthread.php?t=2588101

Categories

Resources