Hi,
I've been using Oxygen 2.0.3 for some time and I remember my battery has autonomy from 100 to 0%. The phone was shutting down at 1 or 0%, every single time.
So once I decided to backup and wipe battstats file. Since than my phone is shutting down at 9-10%. I've changed two Oxygen versions, full wipes etc etc. Nothing.
Tried with restoring old batterystats.bin file but the system overwrites it every time. Tried calibration - no changes.
Is it possible to restore old .bin file somehow? Could I take someone else's 'more precise' .bin and put it in my system?
Did you try to wipe the battery stats again in the recovery?
Sure, every time.
I've done calibration last day, deleted stats from recovery and now I'm waiting for the phone to shut down. At this moment it's on 9%...
Edit: Hm, 4% and still has 3640mA. Usually it shows 35xx mA at 9% and AFAIK that's the lowest point for li-ion batteries.
Edit2: Turned off at 1%. That's all what I wanted, but I'm not sure what have I done exactly to make batstats reading more accurate...
Related
Lately, my Desire has been locking (freezing) on the boot screen, just before it starts into the OS (not going black, just not going further). It then requires a battery pull, as power button doesn't work. I have an SLCD, GMA Desire, with LeeDroid 2.1a (A2SD). It's all been working fine until recently, so I'm not sure what changed. I wiped the Dalvik cache recently, and did uninstall some programs, but not system apps (some sys apps were deleted a while ago, but I didn't notice any problems following that). I would really like to try to avoid having to wipe/factory reset/reinstall LD; as I have a lot of hours invested in the configuration of this device.
Does any of this sound familiar?!
Cyanoid said:
Lately, my Desire has been locking (freezing) on the boot screen, just before it starts into the OS (not going black, just not going further). It then requires a battery pull, as power button doesn't work. I have an SLCD, GMA Desire, with LeeDroid 2.1a (A2SD). It's all been working fine until recently, so I'm not sure what changed. I wiped the Dalvik cache recently, and did uninstall some programs, but not system apps (some sys apps were deleted a while ago, but I didn't notice any problems following that). I would really like to try to avoid having to wipe/factory reset/reinstall LD; as I have a lot of hours invested in the configuration of this device.
Does any of this sound familiar?!
Click to expand...
Click to collapse
i guess that the only answer is to install new rom
try to backup as much as you can with titanium backup
and install a new rom
Hi, I've installed CM7 and it's loading perfectly fine on the 1st boot-up, with the set-ups and stuff.
However I noted several time that if the batt were to go flat (because I forgot to charge) or if I were to reboot the phone, the 2nd boot-up will not load up at all.
I've tried this several times (even to the extent of letting it boot-up and wait until the battery is flat) but it still doesn't boot up.
Any idea if it's a bug or something went wrong?
I've wiped everything before installing the ROM, so wasn't too sure what's the problem.
Thanks in advance for any advice.
Did you try to process it once more, with FULL wipe + Delvick cache wipe and EVERYTHING? Formatting the SDCard, partitioning it... and everything.
***IT HAPPENED A SECOND TIME. THIS TIME I WAS ABLE TO FIX IT BY CLEARING CACHE/DALVIK CACHE AND FLASHING A NEWER VERSION OF THE THE SAME ROM***
Hi guys,
I recently bought a Desire and loaded LeeDroid on a week later. Everything's been fine, until today, when I shut-down my phone and went to turn it back on, and it froze at the Telstra (telco who I bought it from) splash screen.
Here's what I did:
- Power + Vol- + trackball, which resulted in it restarting and freezing at the same point (15 minutes wait)
- Pulled battery and booted into recovery
- NAND Backup using AmonRA
- Restored original (pre-LeeDroid) NAND backup, and rebooted, which resulted in phone freezing at the same point
- Shut down, removed SD Card, wiped using AmonRA, restored original (pre-LeeDroid) NAND backup, which enabled it to boot properly
- Restarted and flashed Leedroid Rom from ZIP, which worked fine.
- Restored today's NAND backup, which of course brought everything back to square one.
Can anyone tell me if it's possible to access any of the contacts/SMS/etc? I was planning to back-up tonight as I'd put a whole heap of stuff in today, so of course this arvo was when it had to die. That and there's some stuff I'd really like to have that I'm not sure the relevant apps have stored on the SD.
And how can I ensure a clean restore? Run Telstra's RUU, then install LeeDroid as per instructions?
(EDIT) I notice that the NAND backups consist of a bunch of .img files. I imagine that data.img might have what I'm looking for in it. I've tried searching for a way to explore the contents, but I'm still trying to get unyaffs running...
Reflash or wipe cache and dalvik cache and reflash.
Sent from CM7
So you're suggesting I do the following?
- Restore freezing NAND backup
- Wipe Cache + Dalvik Cache
- Reflash LeeDroid from zip
Are the contacts all google contacts? If so you can recover those that way.
When you signed in for the first time after flashing the rom, while linking your google account, did you check "backup this phone to google servers"? If so, that should restore things if you wipe all and reflash the rom.
I used this option for the first time, and my wallpaper, shortcuts, alarm settings and SMS all restored after 5 minutes or so.
Unfortunately not. I didn't make the same mistake this time though >_>
Even so, I'm still hoping I might be able to pull some of the stuff out of the NAND backup.
Do you know if it's possible to fake/bypass the md5? If I can swap the data.img from the busted backup to a working one (the one before I put all my contacts in etc) then I should be able to access something.
Unfortunately that brings up an error, and I imagine the checksum is what's doing it.
Does it just delete the batterystats.bin file or something else?
I was under the impression that it wipes the battery history/statistics and calibration level, however I'm not 100% sure about the later.
In the last few days, my N7100 (which I gave to wife) has gone twice in bootloop by itself while idling.
Every time TWRP showed that the phone was unable to mount /efs.
By restoring the efs partition from a nandroid backup I could restart it again both times.
The double failure of /efs at less than a week distance makes me think there's something very wrong in the phone.
After first efs restore I did a factory reset and installed only 2-3 fundamental apps, so I don't think it's the fault of a rogue program.
Do you think my device is at the end of its life cycle? Is there anything I could do to fix it?
Thanks.
'SHAME'sung...?
Only God Can Forgives!?