Database Info

[Q] Damaged Captivate - Any help would be appreciated.

I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?

What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium

I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.

Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry

You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.

Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin

Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.

[Q]MT4GS - wont charge

Hey so i recently rooted, im boot loader unlocked S-ON, flashed the boot.img and am running CM9 alpha 4 on my double shot.
however as of yesterday, all it does is keep blinking an orange light and and not charging, the few times i have been able to turn it on it shows 0 - 4 % battery.
i was running CWMR the latest version but i read another similar thread that was resolved and flashed stock recovery i think, i cant turn it on to check currently :/
Checked for similar threads nothing could really help.

If you have no juice to experiment, you will need a different battery thats charged in order to work with it.

Try leaving it on the on the charger for little while. Sometimes the batteries take a while to accept a charge. My Anker will take quite a while for it to start showing charge if I ran it all the way down.
Barring that get another battery and the standalone charger such as the Anker battery two pack.
Hastily spouted for your befuddlement

make sure that Tis not your charger. Did you try charging with a different charger.

Ok well i still have my broken phone(the one i have no is the warranty one i got from them, didnt send the old broken one back yet), and ive put the battery in there to charge before the problem seems to be this.
The phone isn't charging while its off. It can charge while turned on however at a VERY VERY slow rate. ive read on some thread that CWM recovery might be to blame due to a fastboot thing?

Script Kitty said:
Ok well i still have my broken phone(the one i have no is the warranty one i got from them, didnt send the old broken one back yet), and ive put the battery in there to charge before the problem seems to be this.
The phone isn't charging while its off. It can charge while turned on however at a VERY VERY slow rate. ive read on some thread that CWM recovery might be to blame due to a fastboot thing?
Click to expand...
Click to collapse
This was a known bug with the old Madaco recovery, is that the one you are using? If so, update to the latest one from rom manager in the market.

No im using the 5.0.2..7( i think something around there) CWM, finally charged the battery up, and it went from 100% - 88 like that* snaps fingers* , trying to calibrate the battery to see if that helps but the voltage is almost 4200 mv and the percentage is decreasing... so i might just flash stock, flash stock recovery lock boot loader then just see if i can warranty it...

[Q] Quasi-Pseudo-Semi Bricked?

I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..

Qhastic said:
I bought an Atrix 2 a couple of weeks ago. I rooted it and installed cm10, but did not flash any roms (I preferred to have HDMI). Last weekend, my phone ran out of batteries. Plugging it in caused the white LED to flash, but the phone did not wake up after many hours of charging. Since I was away, at a place where I didn't need a phone, I put it aside for a few days.
Upon returning, I plugged my phone into the wall again. A few hours later it woke up, booted, and began to work normally. I charged it fully and used it for a couple of days. A few hours ago it ran out of batteries again, and plugging it in gives the white LED and nothing else. Sometimes when I plug it in the LED will turn off for a moment and the phone will blink, but the screen does not turn on.
Does anyone have any advice? When the phone was on earlier today it worked and charged normally..
Click to expand...
Click to collapse
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.

1BadWolf said:
First, before you do anything else, research exactly what it is that you are doing. You say you installed cm10 but didn't flash a ROM. It might have been helpful for you to know that cm10 is a ROM. It might have also been helpful to know that HDMI does not work on cm10. As for your battery issue, that has happened to me almost every time my battery has been fully discharged, so I take care to be sure that it doesn't happen. If possible, try charging the battery with an external charger. Then as, I stated in the beginning, research what you are doing BEFORE doing anything else. The best place to start is here:
http://forum.xda-developers.com/announcement.php?a=81
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Sorry, meant clockwork mod, not cyanogen. I haven't flashed any ROMs on this phone yet.
Do you think the battery issue arose as a result of rooting/installing clockwork mod?

No no..Many phones these days fail to charge when drained because they use software to detect the charger and then allow current to flow.. This is unlike the older nokia phones or current HTC phones.. what you can do is as suggested above.. use a 9V battery or something that ought to do it.

LG G3 - Fried battery and/or charging port?

Let me lay down the story first:
It all started when I tried out multiROM for the LG G3. I was running cm12 perfectly fine, unlocked and everything. Amazing battery life. But MultiROM barely worked, even though I followed the instructions exactly, I had many errors trying to get anything to boot properly. I got help with it, but ended up getting rid of multirom via internal storage (where it was) and flashing a normal, non modified TWRP 2.8.4.0. This is where stuff starts getting weird.
After getting rid of multiROM and flashing cm12 again from backup, I noticed my phone wouldn't take a charge at all. It was booted up and running at about 30% battery. My PC wouldnt do anything when I plugged it into my computer, too. I thought it was just Cyan being weird, so I rebooted into twrp and tried plugging in. No buzz, still wouldn't take a charge. For some reason, turning the phone off and plugging in the charger while it was off actually turned it on. So the charging port has to be working, the phones just being weird... but then I decided to smell the charging port. Smells like pure burning electronics. I rebooted the phone with the cable plugged in, and it boots up and charges. This is odd, because i can no longer plug the cable in while the phone is on, i have to reboot it with the cable in now in order to get it to charge. I tried flashing back to stock ROM, and same exact issue happens. Not only that, but the battery no longer holds a charge for more than a day on one full charge. It lasts about 3-4 hours now.
Please, xdaers, help a brotha out. I'm really pissed about whatever the hell is happening to my G3. It still works fine, I just have to reboot it with the cable in in order to get it to charge at all and the battery life sucks on top of that.
Note: One time after all this happened, the phone died fully. Plugging the charger in, the battery logo was flashing on and off. I tried multiple cables and chargers with the same problem. I pulled out the battery with the cable still in, and the battery logo actually stayed on the screen and once I put the battery back in, it charged again. THIS IS MAJORLY CONFUSING and hard to explain so I will clarify my issue if you are confused with my post.
Also, the phone likes to get really hot and die fast by itself even without the charger plugged in now.
thanks guys

Hi
Thanks for writing to us at XDA assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
http://forum.xda-developers.com/att-lg-g3
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
http://forum.xda-developers.com/att-lg-g3/help
Good luck!

So you flashtooled back to stock? And still persists? If so you next option is to buy both a battery and a charging port and do some trouble shooting.
2SHAYNEZ

King Ramen said:
Let me lay down the story first:
It all started when I tried out multiROM for the LG G3. I was running cm12 perfectly fine, unlocked and everything. Amazing battery life. But MultiROM barely worked, even though I followed the instructions exactly, I had many errors trying to get anything to boot properly. I got help with it, but ended up getting rid of multirom via internal storage (where it was) and flashing a normal, non modified TWRP 2.8.4.0. This is where stuff starts getting weird.
After getting rid of multiROM and flashing cm12 again from backup, I noticed my phone wouldn't take a charge at all. It was booted up and running at about 30% battery. My PC wouldnt do anything when I plugged it into my computer, too. I thought it was just Cyan being weird, so I rebooted into twrp and tried plugging in. No buzz, still wouldn't take a charge. For some reason, turning the phone off and plugging in the charger while it was off actually turned it on. So the charging port has to be working, the phones just being weird... but then I decided to smell the charging port. Smells like pure burning electronics. I rebooted the phone with the cable plugged in, and it boots up and charges. This is odd, because i can no longer plug the cable in while the phone is on, i have to reboot it with the cable in now in order to get it to charge. I tried flashing back to stock ROM, and same exact issue happens. Not only that, but the battery no longer holds a charge for more than a day on one full charge. It lasts about 3-4 hours now.
Please, xdaers, help a brotha out. I'm really pissed about whatever the hell is happening to my G3. It still works fine, I just have to reboot it with the cable in in order to get it to charge at all and the battery life sucks on top of that.
Note: One time after all this happened, the phone died fully. Plugging the charger in, the battery logo was flashing on and off. I tried multiple cables and chargers with the same problem. I pulled out the battery with the cable still in, and the battery logo actually stayed on the screen and once I put the battery back in, it charged again. THIS IS MAJORLY CONFUSING and hard to explain so I will clarify my issue if you are confused with my post.
Also, the phone likes to get really hot and die fast by itself even without the charger plugged in now.
thanks guys
Click to expand...
Click to collapse
Don't know about the charging port, but as far as battery life I'm getting the same thing, except mine lasts about 2 hours, I've decided I'm selling the phone while its still worth a bit of money, probably getting a Note 2 or Xperia Z2, I've been very unhappy with this phone, also my battery cover is falling apart and cracking,

SmokeyTech1 said:
Don't know about the charging port, but as far as battery life I'm getting the same thing, except mine lasts about 2 hours, I've decided I'm selling the phone while its still worth a bit of money, probably getting a Note 2 or Xperia Z2, I've been very unhappy with this phone, also my battery cover is falling apart and cracking,
Click to expand...
Click to collapse
Well I've had none of your problems. Note 2 or z2 is a downgrade. Have fun with that... Sucks your experience hasn't been a good one. Cheers
2SHAYNEZ

I get 13+ hours with 4 to 5 hours screen on time and 1to 2 hours of talk time. So I don't think your battery issue is normal for this phone. You have either a defective battery or phone or an app that is misbehaving.

I'm having the exact same problem with LG G3.
Can only charge when rebooted. And even then the charge indicator does not show charging.
I have to go into setting->battery where it shows 'charging'
I have tried new battery and cleaning port.
Anyone figure this out...?

My battery drained very fast before too after backed up to stock, but after I upgraded to 5.0, my phone can lives up to next morning!
Sent from my LG-D850 using XDA Free mobile app

OnePlus One Charging Issue (URGENT)

Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance

danieljh10 said:
Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance
Click to expand...
Click to collapse
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk

Elius2676 said:
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice, but sadly it's not the cable. Or the charger for that matter. The readings I get from the energy meter are too consistent. After plugging and unplugging several times the phone will eventually pull EXACTLY 3.8 watts. No more, no less, irregardless of battery percentage. As soon as the phone is turned off and plugged in, starts pulling anywhere from 7 - 12 watts, which is normal pull I expect.
Hence why I suspected a dodgy kernel, but no luck :'(

Hello
Hello, I had a not that much similar problem a month ago but i'm sharing and it might help (you never know). I was on a custom CM13 based rom and phone started overheating even when not in use, charging slow. When I let it charge overnight I would find it very hot and almost always stuck and 99%. Clean flashed different roms and the same continued to happen and it really got me worried!
Than I thought before ordering a new battery or charger lets try something really stock. I installed lastest OxygenOS and viola problem went away. (be careful and follow the steps you need to flash OxygenOS, it is NOT recommended you flash it via twrp). After that flashed twrp again and custom roms and havent had that problem again.
Hope it helps

Yeah, I would say your most probable culprit at this point might just be the OS. Try a clean flash and/or a different nightly or release. Try also a different Gapps package (you never know if it's not so much the OS, but maybe an interaction between OS and other software.
Sent from my A0001 using Tapatalk

Thanks for the advice, I've finally managed to free up an evening tonight so I'll try putting the phone back to stock. Hopefully it'll work! I'll post back to let you know if I've had any luck.

Put the phone back to stock Oxygen OS, and no luck. Going to use the Tamper Reset Script and try sending it back to Oneplus. Makes me sad that I couldn't sort it myself :crying: