Database Users

Nexus One battery problem

Okay so i've updated to Cyanogen 5.0 beta 2 no problems installed 2.6.32 then went back down to 2.6.29.6 and extra ram works and everything but now my phone wont charge the battery.
I'm quite sad as this is the problem, someone mentioned to let the charge die and then try charging it then. So i did that and now its stuck at 0 and when i remove the charger it instantly dies. Only one other member had the same problem but he hasn't replied to my pm or the thread yet so i'll wait for him as he had this abit earlier.
I've done multiple wipes, reinistalls, nandbackups and now i'm too afraid to do anymore flashing as the phone's battery is on 0%. If at any point it requires phone battery to flash it will die and i'll have a brick.
Hopefully someone out there might have a solution

I dont think its a ROM problem since you wiped. Perhaps its a hardware problem?

i dont know. Does anyone know if its safe to flash? As in if the charger is in it should be okay right?
Okay i think i'm screwed for awhile. The battery is drop dead and now i cant enter bootloader mode. Theres a orange led at top indicating its still working but wont enter bootloader due to insufficient power. Damn i was going to try to flash it
Now i need someone with either a nexus one or another battery
FML

Have you tried another charger or the USB cable?

Same problem here
I'm experiencing the same problem myself.
Installed Cyanogenmod 5.0b2, everything worked fine for the day.
tried JIT, had reboots, reverted back to fast
Upgraded to .32 kernel, my sdcard wasn't compatible so re flashed 5.0b2
called it an evening, my battery was full but I plug it into the charger overnight since it's my alarm clock.
Yesterday morning on the way to work, was playing music and noticed my battery had jumped from full down to around 12% in 30minutes. plugged it into car charger, and while it didn't drop anymore it didn't charge either.
Left it in pc usb charger off and on all day where the off times it dropped down to around 9% and never got above it. Eventually let it die on the way home thinking I'll re train the battery.
Left it off and plugged into wall charger for 4 hours, but batter stays at 0%
I'm glad I didn't sell my Dev G1 yet, as at least I have a working phone for the moment.

FYI I ran into this same problem running superboot himem on ERE27. My battery died and then nothing would charge it, even sitting it on AC power for 8 hours (while I slept) when I woke up my battery was stuck at 0% and would auto shutdown if I unplugged it.
I nandroid restored to stock ERE27 and immediately my battery started again. I think there might be some weird problem with himem mods. Not sure. Just to be safe I am totally over flashing custom stuff on my phone. My phone is too important to me to risk stuff like this happening.

[Q] Mytouch 4g randomly turns off, wont turn back on until the battery is pulled out

I have had three Mytouch 4gs replaced because every one of them I get turns itself off and wont turn back on until the battery is pulled out and put back in. This happens about 6 times a day.
I have tried a new SIM card, new sd card, new battery, factory reset, factory reset with a format of the sd, and they still turned off even without any apps installed and not signed into google.
I am baffled. Does anyone here know what could be wrong here?

i dont know why this has happened to you so many times but it happened to me this morning and immediately after the battery was pulled and reinserted i went to rom manager and fixed permissions. took a while to finish cause i have buku apps but hasnt happened since.
hope it helps ya!

I was running completely stock when this happened, but I've since upgraded to virtuous fusion. Is it better to boot into recovery using CWM to fix permissions or am I fine doing this from the app?

Well I fixed permissions through CWM and it just turned off on me again. Ugh. I'm guessing its not a problem with the rom but with my hardware. Should I try flashing the latest radio?
Does anyone else here have this problem? Wtf is going on?

idk if its the same problem you're having but mine has recently started turning the screen off, the buttons still turn on as well as the led blinking if i have a notification but the screen wont come back on until i do a battery pull
so i'm also wondering what the problem is, fyi i'm using the kernel that came with cm7 and the latest radio

Hmm not sure. When my screen wont turn on I get no lights at all.

One of the causes can be the battery going bad.
I had the same issue until they sent me a new battery.

Sfkn2 said:
One of the causes can be the battery going bad.
I had the same issue until they sent me a new battery.
Click to expand...
Click to collapse
I have tried many different batteries with no effect.
I have noticed however that if it goes unresponsive and I plug it in the charging light comes on and I am able to boot the phone. It will turn off rather quickly though. Like in 20 minutes as opposed to 2 hours. Very weird.

Wow has anyone found a solution for this Problem? I can go into recovery and flash roms with no problem but as soon as it boots to the home screen its just automatically shuts off. Only twice have I gotten it to actually stay on for an hour or so. Also while charging it flashes green then orange, I have two different batteries, any ideas?

Well mine is the same it started after a small six to eight inch drop on the floor and it randomly freezes and when i boot it up just goes into boot loader and after a while of it being off it will go into OS any ideas anybody I am thinking it has something to do with bad chip but what do i know lol tel me know if anybody finds anything out thanks in advance

I've begun encountering the same problem after flashing MIUI 2.3.30 ROM. And I've also noticed that my phone started to get hot. It never did this before. I know my battery is fine, I also re-calibrated my battery and everything. I am even also thinking that for some reason my phone is bricked. It holds charge for about 10 minutes before it dies, even on the new battery, which I have tested on another MT4G and works perfectly. The other phone is my nephews. I wonder if this has to do anything with the bad EMMC chip?
Any input for solving this will greatly help.

Reboots
drunk21 said:
I've begun encountering the same problem after flashing MIUI 2.3.30 ROM. And I've also noticed that my phone to get hot. It never did this before. I know my battery is fine, I also re-calibrated my battery and everything. I am even also thinking that for some reason my phone is bricked. It holds charge for about 10 minutes before it dies, even on the new battery, which I have tested on another MT4G and works perfectly. The other phone is my nephews. I wonder if this has to do anything with the bad EMMC chip?
Any input for solving this will greatly help.
Click to expand...
Click to collapse
You might have already looked at this but have seen in some other roms I have been working with is to make sure to check the md5 sum before flashing just because it flashed doesent
mean it was right it takes is slight hickup in a download and a bit of garbage where it don't belong. Better to check it do the full wipes even a couple times or maybe even mounting and format the boot n system partitions so if on a particular rom ask in its section.
Hope that helps, wish ya well

I would agree with the above post making a clean wipe, and even the format does help. I have been trying out almost all of the newest ICS roms avaliable and I notice it helps when wiping everything/format system and boot. Even the newer ICS rom Awesomev2.1 suggest doing so for the system partition.

As others have stated, you might not have performed a FULL wipe.
Reflash, but do the wipe (I did also wipe battery stats..seemed to help in my case)

Random restarts and won't load
Had the same issue when I switched to Virtuous Unity... battery wouldn't hold a charge and would randomly restart.
After basically nuking my phone (full wipe, cache/battery wipes, etc.), as well as installing Creamed Glacier, the battery life is better but the random restarts are not. Plugging the phone in is the only way to keep it from restarting constantly, where it will load the T-Mobile splash screen but turn off either immediately after or as the home screen loads. But the battery is always at least 50% when I plug it in and it stays on. It also seems to take forever to recharge (plugged into laptop).
I want to think it's a battery issue, but the fact that it's not dead when I plug it in makes me think it's a hardware issue. I can't send it in to T-Mobile (shipping charges and time would be huge, as I'm in a foreign country and I rely on it so much for communication), and I'm loathe to buy a new phone.
Anyone have any ideas?

ivioi3ius said:
Had the same issue when I switched to Virtuous Unity... battery wouldn't hold a charge and would randomly restart.
After basically nuking my phone (full wipe, cache/battery wipes, etc.), as well as installing Creamed Glacier, the battery life is better but the random restarts are not. Plugging the phone in is the only way to keep it from restarting constantly, where it will load the T-Mobile splash screen but turn off either immediately after or as the home screen loads. But the battery is always at least 50% when I plug it in and it stays on. It also seems to take forever to recharge (plugged into laptop).
I want to think it's a battery issue, but the fact that it's not dead when I plug it in makes me think it's a hardware issue. I can't send it in to T-Mobile (shipping charges and time would be huge, as I'm in a foreign country and I rely on it so much for communication), and I'm loathe to buy a new phone.
Anyone have any ideas?
Click to expand...
Click to collapse
I really hate to be redundant, but you formatted /system and data? System gets missed a lot and you didn't specifically mention it.
Sent from my HTC Glacier using XDA

I have had the same problem with ics zips 4.01 all of a sudden the phone stops responding to the power button and have to take out the battery and boot up the phone but as of yesterday with the 4.02 I have had the problem. I don't know if it due to the heat cause where I live it hot and its just the beginning of summer too?

[Q] Strange problem

As the title says I have a strange yet very annoying problem. I am running my HD2 with hyperdroid cm7 Nand build (from april 29th). The problem is that when my battery is deleted, as is the case now, and I put my hd2 in the charger it will automatically boot. I think this is due to a setting or something. However since booting drains energy faster than the hd2 charges, the phone will by turned of before it has completely booted. After a while it get's stuck in a pattern of starting to boot and turning of. I don't know why this is the case because I think my phone just used to boot fine before when connected to a charger.
So my questions are:
1. does anyone has a suggestion how to turn on the phone?
2. this automatic booting, can it be turned off?
3. Why is it actually happening?
Maybe it's a very stupid or obvious problem, but I hope someone can help me though.

Do you have installed MGLRD?, it's a Known fact, search in the forum for answer (I'm sorry, I'm with SD Builds and don't use MGLRD, so I can not help you anymore).

I had the same problem with some rom i used earlier. The only way i could solve the issue was to remove the battery and put it back, then I could insert the charger without the phone booting up. Charge it for a while and start it.
Hope this way works for u 2.
Sent from my Desire HD using XDA App

I guess this is what I used to do as well. However now, if I remove the battery and put it back in it keeps automatically booting. Also if I put the charger in the phone and then remove the battery same thing happens. But thanks for the help though.

I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.

slbenz said:
I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Well, this cycle I think is caused by the fact that the charger is not strong enough. Normally if plugged in the phone would just boot. The reason that it fails to boot is that is doesn't have enough power to complete the boot cycle even though the phone is plugged in (don't know if booting consumes a lot of power?).
A month ago I bought a new usb cable. Maybe that's where the problem lies? Because I have been using the hyperdroid rom for a while now. Although I don't know if one cable can be stronger than the other.
I have found a solution btw: Though it is a bit hit and miss cause it didn't work a few hours ago. When booting I let it go into mgldr and let it charge there. After a while I'll let it boot when it has enough power to complete the boot.

slbenz said:
Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Humm, now you making me think lol, the 1st time I installed Android on my HTC HD2 was the NexusHd2 rom one and he had the same problem, no battery but once I plug it to the wall charger it would do the full(normal)boot, I thought was the rom so I changed to Hyperdroid Cm7, but, still does the same..
The wipe you talking is the one, wipe data/cache right?

if it happens to you a lot, I think it's time to invest in a third-party battery charger. you can charge it out of the phone for a bit, and then you're safe to put it back in a continue charging using the phone

Tried some different roms and all them do the same.. so I reckon its normal.. Thank You.

[Q] Battery error after flashing CM9.

Guys, I got a(nother) problem.
Yesterday, I was able to flash CM9 on my Defy+. Everything worked fine, had signal, wifi, camera, etc. When the battery was at 20% I put it in the charger. An hour later I wanted to install some apps, so I stopped charging, and when I did that, my Defy+ rebooted.
Only it did not boot correctly, it gives the motorola logo for about 5 seconds, then gives a screen with a question mark in an empty battery. I can't do antything after that. When it is at that state, there's a red LED constantly on (at the top of my defy+) and the 4 android buttons stay light up.
When I take it out of the charger, it goes dead.
When I plug it in the PC, nothing happens, except a white LED is constantly on (at the top of my Defy+)
I can still go into recovery (pressing volume down when booting+blue led).
I can also go into (another recovery?): holding volume down, then turning my defy on.
I hope you guys can help me, this is really annoying me
(Also, does these things happen with custom roms often? Cause if so I will switch back to stock ASAP)

vankja said:
Guys, I got a(nother) problem.
Yesterday, I was able to flash CM9 on my Defy+. Everything worked fine, had signal, wifi, camera, etc. When the battery was at 20% I put it in the charger. An hour later I wanted to install some apps, so I stopped charging, and when I did that, my Defy+ rebooted.
Only it did not boot correctly, it gives the motorola logo for about 5 seconds, then gives a screen with a question mark in an empty battery. I can't do antything after that. When it is at that state, there's a red LED constantly on (at the top of my defy+) and the 4 android buttons stay light up.
When I take it out of the charger, it goes dead.
When I plug it in the PC, nothing happens, except a white LED is constantly on (at the top of my Defy+)
I can still go into recovery (pressing volume down when booting+blue led).
I can also go into (another recovery?): holding volume down, then turning my defy on.
I hope you guys can help me, this is really annoying me
(Also, does these things happen with custom roms often? Cause if so I will switch back to stock ASAP)
Click to expand...
Click to collapse
Which build have you used, buddy?
This is the one I used and the battery was charging and everything completely normally:
http://quarx2k.ru/cm9-nightly-defy+/
Those are the only CM9 builds that are REALLY for the DEFY+, since Quarx has recently got his hands on a DEFY+ himself.
P.S. I have never had that problem with any ROM I've tried. I've even used some ROM's for normal DEFY for some time, even thought they couldn't charge the battery over 90%.

MB525
The same was happen with me. But my Defy is MB525
I have installed the kernel froyo, and cm9 Quarx for defy. I used for a little time and put on charger. After this I see M logo for 5 sec and my phone will not turn
When I connect USB cable, the device is not recognized and sometimes don't turn on the white LED.
I charged the battery on universal charger and not solved my problem
Sorry my bad english. I'm brazilian, thanks.

Battery error
I have the same issue, after successful flash my Motorola Defy to CM9 next day phone died.
it gives the motorola logo for about 5 seconds, then gives a screen with a question mark in an empty battery. I can go to recovery mode only when usb cable is plug in.
Does anyone know what should be done?
I was able to flash one more time CM9 but it hasn't helped.

Is the problem solved? i got same one and dont know what to do wit it

I had the problem running quarxs defy+ build on a regular defy. I flashed the battery fix for defy from recovery and it solved the problem.
Sent from my MB526 using XDA

MBM256
I have the same issue, after successful flash my Motorola Defy to CM9 next day phone died. I tried reinstall, etc. but nothing helped.
---------- Post added at 03:46 PM ---------- Previous post was at 03:29 PM ----------
I flashed the battery fix solved the problem me too, thanx the suggestion

Phone wont lasted 10 seconds without plugging in ,But not battery problem.

Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 

Jz Chong said:
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks 
Click to expand...
Click to collapse
Have you tried making a clean wipe and trying either stock or another ROM, to see if it works then?

Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.

DrFredPhD said:
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
Click to expand...
Click to collapse
Hello, much appreciate your reply. I flashed back to stock 5.1.1 now and yet this problem is still persisting. Thus pretty obvious thats an hardware faulty.
In another forum, a guy with Nexus 7 had similar situation as me, and he suggests that its the battery or the circuit board at the charging port went kaput.
Guess nothing else I could do right now, gonna send in the phone for repair and hope the bill wont cost as much as a used nexus 4