Related
Ok, So I got my S3 I believe October, anyways I rooted it and installed roms etc etc because I was a flashaholic, every rom I tried maps would get instant lock with a very accurate reading, but when it came to navigation and other stuff that use location all it will say was "Searching for location or w/e it says". It didn't really bother me, then I noticed that If I let my phone die all the way I would not be able to charge the phone or get very lucky pulling the battery out or pulling the plug and then rinse repeat and it would miraculously charge, didn't really bother me, because I work at raadioshack and I bought a external battery charger in case I did let it die, in which case I never did. But now today, lol, I installed a new rom(In no way was it the roms fault) It was goodness 8.0.1 port, installed lean kernel 1.8 and I did this with about 38% battery. Watched a couple shows on the phone so I could let it die and calibrate the battery, but at like 4% I bought a game and I wanted to play it more so I got my charger and charged it. Went to the kitchen for a few seconds heard a weird sound out of nowhere. Went to reach my phone and I smelled a burning smell, I was like WTF? My phone was hot as hell, really HOT. so I unplugged the charger and I installed notice that the charger was burnt, and then I smelled the charging port and it smells burnt also. I think that's it, the end for my S3, I mean as of now 2:30 am I am using my external charger to charge my battery but I think I'm going to have to call verizon up for a replacement and it's my first time doing this so I hope they give me a replacement, didn't really want to go this option. but wish me luck lol.
Edit 1: Lol I just realized my usb port isnt working anymore. Is there anyway I can go back to stock using adb or something
Watoy said:
Ok, So I got my S3 I believe October, anyways I rooted it and installed roms etc etc because I was a flashaholic, every rom I tried maps would get instant lock with a very accurate reading, but when it came to navigation and other stuff that use location all it will say was "Searching for location or w/e it says". It didn't really bother me, then I noticed that If I let my phone die all the way I would not be able to charge the phone or get very lucky pulling the battery out or pulling the plug and then rinse repeat and it would miraculously charge, didn't really bother me, because I work at raadioshack and I bought a external battery charger in case I did let it die, in which case I never did. But now today, lol, I installed a new rom(In no way was it the roms fault) It was goodness 8.0.1 port, installed lean kernel 1.8 and I did this with about 38% battery. Watched a couple shows on the phone so I could let it die and calibrate the battery, but at like 4% I bought a game and I wanted to play it more so I got my charger and charged it. Went to the kitchen for a few seconds heard a weird sound out of nowhere. Went to reach my phone and I smelled a burning smell, I was like WTF? My phone was hot as hell, really HOT. so I unplugged the charger and I installed notice that the charger was burnt, and then I smelled the charging port and it smells burnt also. I think that's it, the end for my S3, I mean as of now 2:30 am I am using my external charger to charge my battery but I think I'm going to have to call verizon up for a replacement and it's my first time doing this so I hope they give me a replacement, didn't really want to go this option. but wish me luck lol.
Edit 1: Lol I just realized my usb port isnt working anymore. Is there anyway I can go back to stock using adb or something
Click to expand...
Click to collapse
If you're rooted and unlocked, you can give mobile odin a try.
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
minirx7 said:
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
Click to expand...
Click to collapse
Never flash anything or make major changes to your phone with a low battery (below 70%).
I may be the member he was talking about. I had a thread on this. Only difference was my phone wouldn't charge at all. When I plugged it in when it was off it would boot loop the charge screen. It was rooted and I had some bloat frozen, but the issue started after I installed Sugarsync. I had the same configuration for a few days with no problems, and my battery was about 50 percent when I tried to charge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just trying to help. I freaked yesterday because no matter what i did, it wasnt charging. But once i fully powered off, it started chargin!!
scott14719 said:
Never flash anything or make major changes to your phone with a low battery (below 70%).
Click to expand...
Click to collapse
I just flashed a ROM with 56%. I like to live dangerously.
AdePower said:
I just flashed a ROM with 56%. I like to live dangerously.
Click to expand...
Click to collapse
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
scott14719 said:
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
Click to expand...
Click to collapse
I bricked a S2 like that. Flashed a rom adn the battery drained in the process, causing it not flash properly. phone was dead, no download mode or anything.
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
My phone is not charging sometimes and when it is, it charges at about 1% every 15 minutes. I've tried many known working chargers and cables so rule that out. I switched custom ROMs because of this issue. and a few days in it began to happen again. What are some things that could be causing this?
Im desperate! really, it's only phone for communication. My last resort is back to stock but I really like my setup now and battery is amazing. Please help lol
If the same thing happens with several known working chargers and cables, then likely you have a hardware issue with the phone itself.
(On my first Nexus 5, the charging port came slightly loose and would only charge with the cable at a very specific angle. Got it replaced when it was still under warranty)
To be absolutely sure it's not the rom or kernel or some strange mod, make a nandroid backup, copy it to pc, then go fully back to stock. See if it charges properly.
Try out apps like Ampere etc which display the charging rate. Your battery might be dead or as mentioned in the above post
Just spent a whole day doing all that stuff, It's def the phone :'( It's absolutely heartbreaking since I don't have money to fix it......... Uuuuughh...
charging was wonky, been checking it constantly
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: