OK so I bought a phone off craigslist as a replacement for my gf, really unstable running the stock 2.3 firmware, did a factory reset, seemed to be stable afterwards but the battery meter constantly reads 100%, so I flashed it to 2.3 stock with ODIN, problem was still present, put clockwork mod on it, wiped battery stats, still was there. Installed a PAC MAN rom, still there, flashed back to stock 4.1 firmware, problem still present, and finally put the dirty unicorn ROM on it and its still stuck.
So I found a post saying to charge up all the way, delete the batterystats.bin file reboot in recovery wipe cache partition and davlik cache, power off and keep plugged in, disconnect charger reconnect and leave powered off but charging, then turn on, did that and leaving on till it powers itself off and its still stuck at 100%
Oddly when the phone is turned off upon first showing it does display the correct battery for about 15 seconds and then reverts to 100%
What is going on here, how do I fix this
rodimus_prime said:
OK so I bought a phone off craigslist as a replacement for my gf, really unstable running the stock 2.3 firmware, did a factory reset, seemed to be stable afterwards but the battery meter constantly reads 100%, so I flashed it to 2.3 stock with ODIN, problem was still present, put clockwork mod on it, wiped battery stats, still was there. Installed a PAC MAN rom, still there, flashed back to stock 4.1 firmware, problem still present, and finally put the dirty unicorn ROM on it and its still stuck.
So I found a post saying to charge up all the way, delete the batterystats.bin file reboot in recovery wipe cache partition and davlik cache, power off and keep plugged in, disconnect charger reconnect and leave powered off but charging, then turn on, did that and leaving on till it powers itself off and its still stuck at 100%
Oddly when the phone is turned off upon first showing it does display the correct battery for about 15 seconds and then reverts to 100%
What is going on here, how do I fix this
Click to expand...
Click to collapse
u would need to try an oem battery and cable to see if it corrects the issue, if not then its probably the charging port, reading this post might help http://forum.xda-developers.com/showthread.php?t=2493751
An OEM battery really isnt a possiblity as no places sell it locally (sure I can order it online but this is a time sensitive project) and I really dont want to dump any further money into this project if its not going to work
Related
Why is battery use not resetting itself, it says 7days on battery... shouldnt it reset to zero everytime recharged?
You haven't said if your phone is rooted or not. If you are rooted, boot into recovery and you can wipe the battery stats there. I belive some custom roms have it built in so that after the first 100% charge the battery stats are wiped automatically.
If you post more info about your phone you'll get better answers.
unrooted and stock, and now it has reset after another charge....
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
bweN diorD said:
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
Click to expand...
Click to collapse
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
In all likelihood, this is not a LiquidSmooth issue. I would suggest a clean install as the previous posters suggested. The latest stable version of LS is now at v2.10 for Android 4.3
LS 2.10 must be installed as follows, according to the devs:
New Flashing Instructions
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format /system
Install ROM, NOT GAPPS YET!!
Reboot system, first boot may take a few minutes, don't panic ;-D
Setup your phones settings, anything that isn't Google related
or let your phone sit for 5 minutes
reboot back into recovery
wipe cache and dalvik
then flash gapps
reboot and enjoy
Click to expand...
Click to collapse
For the xt926, the download page for LS 2.10 is here: http://d-h.st/users/jsnweitzel/?fld_id=15202#files
gapps 8/13 or newer are supposed to be used with this ROM. dl from here: http://d-h.st/users/jsnweitzel/?fld_id=21058#files
The official ROM page is over at G+ https://plus.google.com/u/0/communities/117452480298315341829, if you have any additional questions.
Give it a whirl, and let us know what happens. Good luck.
SELind01 said:
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
Click to expand...
Click to collapse
you are wiping very well, i was just confirming you wipe everything possible short of the external sd.
the wipe im talking about in twrp is wiped when you wipe "data", the one where you have to type "yes" before it will wipe. in cwm, in the formatting section (i forget what its called), there is an option that specifically says "data-media /internal sd" or something close to that.
as for the latest recoveries, here is a tool by Tucstwo that i have been updating lately http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
also, twrp 2.5 doesnt have all the selinux bugs worked out, you need 2.6.3.0, which is in the above utility.
Update:
ok somehow i managed to get my phone rooted/s-off on hboot 2.15 , TWRP 2.6.3 and made backup of ROM, everything in a few misn it allowed me to work it on fastboot, but the problem is sometimes i turn it on on Bootloader when i connect the USB cable it freezes/reboot/turnoff/works (random) , now when i manage to get into recovery, sometimes it works wiping but sometimes it just freezes and reboot, also the battery says 66%, all of the sudden is 99% then back to 66%, so i been thinking is never been a software issue, cause i wiped the rom and just boon into recovery and still do it, but its more like a hardware issue......anyone have the closest idea what i can do/try to try and fix it.
now that i got my phone working from not doing anything at all , its been working fine for a couple of days but right now screen was off when i went to check it was off , connected to charger no light so i did this :
Connected it to wall charger.
Press power + volume down
Orange LED went on
Let it sit for 5 mins
Turn it on
It turns on and battery is at around 70%
Could it be battery is bad and phone is missreading it or could it be something else ?
please anyone with any ideas, im so tired already ill try anything.
cubanito08 said:
Update:
ok somehow i managed to get my phone rooted/s-off on hboot 2.15 , TWRP 2.6.3 and made backup of ROM, everything in a few misn it allowed me to work it on fastboot, but the problem is sometimes i turn it on on Bootloader when i connect the USB cable it freezes/reboot/turnoff/works (random) , now when i manage to get into recovery, sometimes it works wiping but sometimes it just freezes and reboot, also the battery says 66%, all of the sudden is 99% then back to 66%, so i been thinking is never been a software issue, cause i wiped the rom and just boon into recovery and still do it, but its more like a hardware issue......anyone have the closest idea what i can do/try to try and fix it.
Click to expand...
Click to collapse
This happened to me as well I wiped the whole device meaning SD and rom then this stopped happening
mmm ill try that havent wipe SD yet but i dont see if that could be the problem but doesnt hurt trying but its just hard to even stay on the recovery long enough to wipe.
didnt work, wipe it all , reinstalled RUU stock , unlocked and rerooted again , super CID, still does that crap i think maybe hardware issue
phone is been for more than a week at a local repair center and i dont think they can even figure it out, they said may be software issue but i know for a fact isnt, it had stock rom, i wiped it out, everything, reinstall using RUU, still same problem.
Dunno what happened, but couple days ago my phone powered off due to dead battery, and when I charged it up and turned it back on it didn't ever get passed the blue cyanogenmod logo. I was running a CM13 nightly from a few months ago. Couldn't power off. Tried holding volume buttons with power and could make it reboot but never boot. Eventually let the battery run flat, charged it up, then start into twrp, cleared cache and davlik cache. No change booting, let it run to flat again. This time I tried flashing the latest cm13 nightly in twrp, but still no change booting.
I don' t have any backup and would like to get my phone working again with the least amount of loss, but dunno any troubleshooting steps. Anything I could try before wiping data?
How long did you let it sit at the boot logo? Sometimes the first boot can take an exceedingly long time; a fsck process running I believe was the holdup typically.
Without a backup, there's not a lot else you can do if you don't want to wipe data.
arrrghhh said:
How long did you let it sit at the boot logo? Sometimes the first boot can take an exceedingly long time; a fsck process running I believe was the holdup typically.
Without a backup, there's not a lot else you can do if you don't want to wipe data.
Click to expand...
Click to collapse
I let it run til the battery was flat from full charge. Hours and hours. In fact don't know any other way to turn it off when it won't boot anyway.
So I wiped data 20 mins ago, and hasn't booted yet. I'll let it run flat then try wiping and flashing rom again. If that doesn't work, I guess that means I have to wipe system too, then flash cm and gapps, and finally be back up.
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Jvers said:
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Click to expand...
Click to collapse
OK so what you've done is correct flashing stock (which includes stock kernal). You have to make sure the stock ROM is correct for your device and region or it will not start.
It's not unusual to have to flash it twice with Odin.
Next up you don't need to wait for batt to die to restart. Press volume down+home+power and keep them pressed until phone restarts. Should now be in download mode, reflash correct ROM with Odin. TWRP is wiped off the phone when you flash a stock ROM.
If it doesn't go through the boot up/freezes/ does nothing etc. You need to "wipe cache" then reboot from the recovery menu.
Press and hold volume down+home+power. As soon as the screen goes black move your finger to volume up (it may take more than one attempt). Once your in recovery menu use volume up and down to move through options and power to execute. Wipe cache then reboot and allow the phone to go through all the reboot stuff. It can take a few minutes just leave it alone. It will also reboot a couple of times.
If it does nothing after 15 minutes then start again and repeat the process.
Thanks for reply.
The Phone was off for a day and after charging for 1h it still does not react to any command. Vol down + home + power does nothing. Same with vol up.
Is there a way to force a boot? Even if the PC does not recognize a device on usb?
I Tried the commands 30 secs each, plugged in and off. Also usb port is not broke since the phone is getting temperature after a while charging..