Hello everyone, long time reader, first time poster (with a real query).
Actually last Friday my cappy started to show 100% of the battery after being for some time in use, so I reboot it trying to solve the issue.
After the boot, the cell shows the Initially Battery screen for 2 seconds with the battery without charge then turns off. Tried several times and also using a second battery with full charge and same problem persisted.
10 minutes later without having a battery inside the phone, it boots but when I rebooted the problem arises again.
This weekend I installed Illuminance 3.01, after that I have installed CM9 (very nice ROM) and the battery problem still is happening. I am able to use the phone but I donĀ“t know for how much more.
Any suggestion?
Thanks,
Martin
have you tried to wipe battery stats in recovery ?
Felixcm88 said:
have you tried to wipe battery stats in recovery ?
Click to expand...
Click to collapse
Yesterday night I did a wipe battery stats and the problem still is there.
It starts with the loop and the only way I can start the phone is plugging it then it shows the actual charge of the battery and after that I can boot.
It must be something "deeper" than the rom...
Anybody?
Thanks
Somebody can help?
I am having the exact same issue, stock froyo 2.2 rooted 5 months ago. I'm trying everything before updating to 2.3, I'll let you know if I find a fix, please do the same.
Searching google is not working this time, it's been 3 days...
Things I've tried:
1- From recovery, boot phone. Problem persists after phone is turned off.
2- Boot from revovery, then reset to factory settings, after rese, same issue.
3- Wipe cache from recovery. Problem still there.
4- Wipe cache+user data from recovery. Same thing.
5- repeating 1-4 without SD card or SIM card.
- Wipe battery data... nothing...
- Unrooting, same issue, rooted again.
- Run root fixes with Titanium backup. Same...
- Removing battery for hours, while charging it externally, replace battery, same issue.
All to no success. Things yet to try:
- Update to 2.3 using kies
- Update to beta 2.3.5 using odin
- Update to custom rom, maybe try 3 or 4 different...
- Cry, then save and buy a new phone, use cappy as shiny paperweight...
Please let me know if you could fix it...
I'm not sure what you mean when you say "initial battery screen."
But if I am to understand the rest, your problem is:
initial boot - runs fine, but battery stays at 100% no matter how long it runs.
reboot - phone now says the battery is suddenly dead, and shuts-off.
further reboots - same
You can't get the phone to fully boot till the battery is left out for a while and the phone is fully de-energized.
You have tried a different battery and it behaves the same.
- - - - - -
Have you tried using a known "good" battery? (a new one or one from someone who's phone works fine)
Also, what happens if you plug in the USB while the phone is off? (after the inital boot, when it is stuck in the "dead battery loop.")
Still dead after installing update and 2 custom roms...
Yes I tried a good battery from another cappy, if I plug in the cable it does the same, instead of normally booting, it displays an empty battery and goes off.
I am able to make it work but only entering the restore mode, so I cannot for example be on a trip and reset the phone for whatever reason...
have you tried using a different kernel?
Sent from my SGH-I897 using XDA App
sorry, but how can I try a different kernel? do i need to change the rom?
Nah, kernels can be flashed independent of ROMs just look through development for topics that have "[Kernel]" as the fist word in their title.
If you have gone and loaded two custom ROMs and it still persist then it's not a kernel issue. As the kernel is always changed along with the ROM.
That said, I can only think of two other possibilities: one being dirt or such making a short in the contacts of the usb (does it sometimes think it is plugged in when it's not), two something in the circuitry for the battery randomly went bad.
Try cleaning the socket for the usb. If that does not fix then assume the worst
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
Ok, here's the thing, I left it without the battery for 24 hrs, then it was worst. The phone would not turn on at all. However, after that I tried putting the battery in while holding the power button, it worked!!! it's better than having to connect to the computer, but still, I don't want to have to do this every time... flashing roms now to try again.
We're getting somewhere now...
DaNaRkI could be right about it being a circuitry problem (which would suck). With that in mind, have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
When you flashed the roms, are you doing complete wipes? (wiping the cache/dalvik/data)? It might be worth it to go one step beyond that and format all the partitions and then reflash. I think if you do that, you could basically rule out any software problems.
Be sure to back up your data!
P.S. When you do all this wiping and formating and reflashing, boot up and check to see if the problem is still there before you put your data back on jic there is some weird corruption in your data which is causing this.
ok.
have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
yes I have, they're perfect
When you flashed the roms, are you doing complete wipes?
many times, actually
I have yet to format all partitions, how can I do that?
Thanks!!
and yes, all my data is well backed up in my PC and cloud...
---------- Post added at 12:31 AM ---------- Previous post was at 12:09 AM ----------
this is rather odd, just tried to factory reset again, then restarted using the battery method, then... turned it off, and now it boots normally!!!
Thanks for your help !!!
I have the same problem. What exactly did you do? I use a custom rom, and I flashed stock gingerbread 2.3.4.
Formatting the partitions won't do anything, since the phone won't even turn on sometimes. So when exactly did this problem start happening? Was it after a particular flash or other incident?
I was on previously on stock GB rom and kernal (unrooted) and then used Kies to upgrade to ICS. Then followed the various guides on XDA to get root. Everything was fine for a few months except that the responsiveness on the note was laggy probably because when i used Kies to upgrade to ICS it was a no wipe and so everything i had installed on GB moved over to ICS.
Anyway, I read up on the brick bug and followed the guide here (http://forum.xda-developers.com/showthread.php?t=1857556) to use odin to flash kernal to HydraCore. Then rebooted into CWM, wiped data and cache and then installed Rocketrom v12. Reintalled all the apps from google play. Then used titanium backup to restore the data only of various apps (the only system app restored was internet (bookmarks)). Rebooted phone and everything was still fine. Then after booting up and was running a few apps (eg whatsapp) to make sure the data had been restored. Then noticed the screen started to flicker....then after about 30 seconds the screen went blank. And now no response, cannot get into recovery, download mode and not recognise when i plug it into computer. Is this the infamous brick bug??? Or something else??? My battery was on about 40% so i guess its not out of battery....could it be that the battery has died (i am not using the original samsung battery).....pls help!!!!
the screen flickers and the phone goes off is a classic sign of battery drained to 0.. charge again while the phone is off and try to reboot again. i guess u should be ok
nokiamodeln91 said:
the screen flickers and the phone goes off is a classic sign of battery drained to 0.. charge again while the phone is off and try to reboot again. i guess u should be ok
Click to expand...
Click to collapse
Thanks for ur tip. It turned out that the battery died flat out....bought a new battery and my note is back alive again! I was so worried it was bricked! Thanks again!!!
cool..
Did you try charging the phone whilst off?
Hey everyone:
HTC One M7 (AT&T variant). Unlocked bootloader & s-off. TWRP 2.7.0.0. HBoot 1.44.
I had Maximus 30.00 ROM on my phone up until last night. Then I downloaded Whats app plus on a questionable site application; it looked like it was taking forever to finish; so I went ahead and restarted the phone. That was a bad mistake.
The phone started boot looping. I tried in vane to reinstall the same ROM and then whatever ROM. It turned out the /data/ partition was corrupted. So I reformatted it with mkfs4 thanks to these instructions. Then I was able to install Maximus 40.00 and got the phone unbricked (yay). But I found two problems:
1) The phone battery wouldn't charge past 77%... nor did it seem to discharge.
2) The phone battery wouldn't charge when I first turned the phone off. The amber LED light would just hold constant.
I tried running that ROM with elementx kernel with no results. So I installed the latest version of this ROM (Android Revolution 71.0) with a full wipe of everything. /data/system/cache/dalvik cache etc. Still had both problems.
Then I tried installing ElementX kernel (with the fast charging option checked) with this ROM which led to the second problem going away. However the first problem still exists. I also tried clearing battery stats with no effect. Also tried doing a fastboot erase cache with no effect.
I'm not sure if the battery is really at 77%; but I have turned off the phone and am watching it charge with the same charger I've always had that charged it to 100% before... but its been going for 15-20 minutes without going up one percentage.
Any idea how I can try to get rid of this quite annoying problem? Thanks very much in advance! I would be happy to provide any additional information you might need.
Hello, this is my first post here and ofcourse I have a problem...
So yesterday I was rooting my Xperia Z, unlocked the debug mode and was able to access the recovery mode a few times. So I flashed my device to 4.2 version with a computer then I copied the 4.2.2 .tft file and the Kernel into my phones internal memory, turned my phone off, turned it on again, turned on the recovery mode, did the "Wipe data/Factory reset", wiped the catche partition, wiped the Dalvik cache, formated the system, formated the data and the cache. So then I went to install the prerooted ROM but my phoned seemed not to find it in the internam memory so I selected to reboot my device and since then it is acting all weird...
So the phone then tried to reboot but freezed at the Sony logo, the battery was about 89% and the phone started heating like it was working on its max, the phones battery died after about 2 or 3 hours, so ofcourse I tried connecting it to my PC to try to charge it but it just started to boot loop, I could hear the computer making a notification sound that the device is connected and after a few seconts it just disconnects. It seems that the phone isnt charging at all because after leaving the phone to charge for the whole night with a regular charger the phones LED was still red and was giving me 3 blinks when I tried to turn the device on. I think that if I could to access the recovery mode again I would be able to fix everything from there on my own...
Any help to fix this problem is welcome, I can provide more information about the problem if there are some questions
P.S. I already tried to remove the microSIM and microSD cards
flash the ftf file you have using flashtool
Richy99 said:
flash the ftf file you have using flashtool
Click to expand...
Click to collapse
I noticed a really weird thing. It looks like it might be both technical and software problem. So earlyer I had the rooted 4.4.2 version but it started to bootloop when I turned on the camera, the device turned off when it was at about 60% battery. So I though to hell with this version and wiped everything again, installed the 4.4 version with flashtool but then the bootlooping started again, it went no further than the Sony logo, after about 2 hours of trying to get the damn thing on I took my fathers Galaxy S4 charger and pluged it into my phone, for my surprise the phone started charging and was displaying that battery icon in the middle of the screen, so now its about at 30% battery and trying to turn it on wont work, almost gets to the main screen and then instantly turns off. Ill try to charge it to about 80% battery and then try to turn it on. I suspect that the device thinks its battery is empty when it is actually at about 60%
FerretXing said:
I noticed a really weird thing. It looks like it might be both technical and software problem. So earlyer I had the rooted 4.4.2 version but it started to bootloop when I turned on the camera, the device turned off when it was at about 60% battery. So I though to hell with this version and wiped everything again, installed the 4.4 version with flashtool but then the bootlooping started again, it went no further than the Sony logo, after about 2 hours of trying to get the damn thing on I took my fathers Galaxy S4 charger and pluged it into my phone, for my surprise the phone started charging and was displaying that battery icon in the middle of the screen, so now its about at 30% battery and trying to turn it on wont work, almost gets to the main screen and then instantly turns off. Ill try to charge it to about 80% battery and then try to turn it on. I suspect that the device thinks its battery is empty when it is actually at about 60%
Click to expand...
Click to collapse
Try flashing 4.3 Stock rom from flashtool
androidtweaker1 said:
Try flashing 4.3 Stock rom from flashtool
Click to expand...
Click to collapse
Still boot looping, when I flashed it into 4.3 and it started up for the first time i got the message "process system isnt responding"
Hello,
I have a problem, when my battery is discharged i cant run my phone again, phone stops on booloop.
I do factory reset and phone worked for 2 days and again bootloop.
When battery is on low stage (3-5%) phone crashes.
I using this rom
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-4-4-4-t3026347
When i install rom again with full wipe everything working fine.
Sory for my English.