[WIP] Finding Solution for 0% Battery

Status
Not open for further replies.
Search This thread
By:
Advanced…
Alejandrissimo

Alejandrissimo

Senior Member
Jan 12, 2011
778
625
unlock-bootloader.com
Hello again people :D

Ok we know there are a ton of phones with 0% battery issue after downgrade from 2.3.4 and root

Apparently is not software related problem since I already try to:

Flash a lot of different firmwares - Doesn't work
Fix the bootloader - Doesn't work
Repair trim area (working trim area from another phone and restore security backups) - Doesn't work

So now the dev of setool is search for a solution for whis annoying problem.

Update 1

Anyone with an Arc with this problem who wants to try a full trim area repair please contact me.

This process is simple:

1. First we need to backup your security units from original Trim Area.
2. Format trim area and write a backup from another working phone.
3. Restore your original security backup.

Please anyone with an Arc 0% battery issue send me a pm.

+++++++++++++++++++++++++++++++++++++++++++++++++

Please all users with this problem who want to help to this:

1. Download the rar attached.

2. Unpack it and double click to execute.bat

This file just is a command "adb shell dmesg > log_output.txt"

3. Post that log_output.txt file , don't forget to say the model of the phone :D

For now this can help to identify the problem. Only post logs with 0% battery problem please :D

Thanks in advance
 

Attachments

  • adb.rar
    506.8 KB · Views: 2,844
Last edited:
  • Like
Reactions: ST4YSTR0NG, zainthesnipe, dugzino and 3 others
V

visarya

Senior Member
Mar 30, 2010
59
16
New Delhi
here is the attached output file
one of the suspects that someone pointed at is
[ 5.085205] Please check boot accessing charger (want 0x50, got 0xac) ***
 

Attachments

  • log_output.txt
    35.2 KB · Views: 777
I

icet925

Senior Member
Sep 14, 2009
207
9
Using Xperia Arc version 2.3.2 build 181
no root..

Hope this can help
 

Attachments

  • log_output.txt
    35 KB · Views: 243
kbadone

kbadone

Senior Member
Dec 13, 2008
384
59
United States
I tried turning on my phone(plugged in charger) and enabled USB debugging. but when I doubled click on execute.bat I get an empty log_output file!:confused:
 
D

Deleted member 4234466

Guest
kbadone said:
I tried turning on my phone(plugged in charger) and enabled USB debugging. but when I doubled click on execute.bat I get an empty log_output file!:confused:
Click to expand...
Click to collapse

Same here, I fixed it by opening execute.bat and changing adb to adb.exe. Hope that helps.

Here is my log.
 

Attachments

  • log_output.txt
    45.6 KB · Views: 92
Last edited by a moderator:
Alejandrissimo

Alejandrissimo

Senior Member
Jan 12, 2011
778
625
unlock-bootloader.com
Crahzee said:
Same here, I fixed it by opening execute.bat and changing adb to adb.exe. Hope that helps.

Here is my log.
Click to expand...
Click to collapse

Update 1

Anyone with an Arc with this problem who wants to try a full trim area repair please contact me.

This process is simple:

1. First we need to backup your security units from original Trim Area.
2. Format trim area and write a backup from another working phone.
3. Restore your original security backup.

Please anyone with an Arc 0% battery issue send me a pm.
 
  • Like
Reactions: MTechRD and phamhonghainb
D

Deleted member 4234466

Guest
kbadone said:
Thats all I got, not sure what I am doing wrong!


* daemon not running. starting it now *
* daemon started successfully *
Click to expand...
Click to collapse

Don't worry about that now, go help Alejandrissimo! Hopefully we can find a solution with this new method.
 
Last edited by a moderator:
V

visarya

Senior Member
Mar 30, 2010
59
16
New Delhi
Alejandrissimo said:
Update 1

Anyone with an Arc with this problem who wants to try a full trim area repair please contact me.

This process is simple:

1. First we need to backup your security units from original Trim Area.
2. Format trim area and write a backup from another working phone.
3. Restore your original security backup.

Please anyone with an Arc 0% battery issue send me a pm.
Click to expand...
Click to collapse


looks like someone already tried it.
http://support.setool.net/showthrea...wngrade-and-root&p=68959&viewfull=1#post68959


I am not sure how to do it , but i dont mind following the instructions
 
Status
Not open for further replies.

Similar threads

zohaib0001
Xperia T ICS Rom V7.8.6 For 2011 Xperia, Based on (4.0.4) [ 4th-Feb-2015 ]
Replies
4K
Views
833K
stealthware
stealthware
DooMLoRD
[ROOT] Rooting Toolkit for Xperia 2011 ICS [FW:.562]{LOCKED & UNLOCKED BOOTLOADERS}
Replies
298
Views
1M
P
psychoplasm02
S
[ROM][AOKP][JB][RC]KXP for ARC/ARC S[Build 5]
Replies
3K
Views
526K
smokerman
smokerman
IdeosDev
  • Locked
[ROM][Arc/S][JB][4.2.1][WIP]Unofficial CyanogenMod 10.1 Alpha Build {3}
Replies
316
Views
175K
Sorin90
Sorin90
C
The Complete Comprehensive List of System Apps for Xperia Arc (Updated)
Replies
147
Views
480K
feco86
feco86

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 9
    Bin4ry
    Bin4ry
    Okay.

    So I think that following happened:

    Downgrade and gingerbreak caused a firmware damage of fuelgauge. I saw some logs showing me that bq2xxxx device is not even showing up in /sys/class/power_blablabla

    So device cannot start. BUT to upgrade the firmware of the device it is neccesary that it is present. Also you always see the i2c xfer errors. that's another indicator that the device is not up, OR that the device is not up in a recognized mode.
    I have to do a little research about the chip and the hardwarelayout where it is embedded. I HOPE that i am able to find a solution for this. I think that it has to be possible to set the bq fuelgauge device to firmware download mode.
    Please give me a little time for that. I will come back to you, even if i only have bad news.

    Regards
    View
    8
    V
    visarya
    good news , it looks like it is a kernal related issue , i created a new ftf using kernel from docomo ftf and it can be applied as a patch after installing any 2.3.2 firmware. however you will be stuck with 1% battery issue.
    this is just a temp fix till we get a real fix for the issue
    View
    6
    Alejandrissimo
    Alejandrissimo
    Hello again people :D

    Ok we know there are a ton of phones with 0% battery issue after downgrade from 2.3.4 and root

    Apparently is not software related problem since I already try to:

    Flash a lot of different firmwares - Doesn't work
    Fix the bootloader - Doesn't work
    Repair trim area (working trim area from another phone and restore security backups) - Doesn't work

    So now the dev of setool is search for a solution for whis annoying problem.

    Update 1

    Anyone with an Arc with this problem who wants to try a full trim area repair please contact me.

    This process is simple:

    1. First we need to backup your security units from original Trim Area.
    2. Format trim area and write a backup from another working phone.
    3. Restore your original security backup.

    Please anyone with an Arc 0% battery issue send me a pm.

    +++++++++++++++++++++++++++++++++++++++++++++++++

    Please all users with this problem who want to help to this:

    1. Download the rar attached.

    2. Unpack it and double click to execute.bat

    This file just is a command "adb shell dmesg > log_output.txt"

    3. Post that log_output.txt file , don't forget to say the model of the phone :D

    For now this can help to identify the problem. Only post logs with 0% battery problem please :D

    Thanks in advance
    View
    5
    Bin4ry
    Bin4ry
    Well let me jump in here:
    I read up some informations, maybe you can help me work it out.

    From what i know the problem occours:

    - On downgrade to a "too" old version
    - Intention of downgrade was to use gingerbreak
    - Problem does NOT happen when you downgrade step by step in versions

    What i know:
    - TI Fuelgauge firmware got a firmware-update around the problematic firmware you are downgrading to.

    Assumption:
    Firmware 181 had included the firmware upgrade of TI fuelgauge. When skippinmg 184 firmware in downgrade process you are running into a firmwareupgrade which fails.
    As result you will end up with a ****ed up firmware!

    Similar problem we had on X10 some time ago, but on X10 it was camera firmware which got upgraded.

    Ok. Here is the plan:
    Because i am busy in fixing hdmi i have no time to crossflash all firmware versions or extract it. Just too busy sorry.
    But you can help me.

    Please dump me the filesystem (exclude apps!) from 184 and 181 firmware! I think we can find some informations inside which helps to repair the firmware of the fuelgauge ;)

    Regards
    View
    5
    F
    FiDra
    Hi guys,

    These are some information I think it will help:

    - I flashed this firmware: http://www.mediafire.com/?68r93ddskychhoa
    (This is a Docomo firmware which has been modified, so you can flash it to an un-Docomo Arc)
    - Flashed successfully. Info:
    +++ Android: 2.3.2
    +++ PIN: 1%
    (PIN shown 1% but you can use it as normal. The phone does not shut down any more.)
    +++ Charging: Yes, as normal. But always said 1%.

    - Then, I flashed the Custom KERNEL of DoomLord and Blend:
    +++ PIN: 0% --> Phone shut down.

    - Then, I re-flashed the Stock KERNEL from Docomo's firmware:
    +++ PIN: 1% --> Phone DOES NOT shut down. And you can use it as normal.

    ----- Another tests -----
    - Flashed Docomo - then UK firmware build 181 --> No help. PIN 0%, phone shut down.
    - Flashed Docomo - then Global 2.3.4 build 283 --> PIN 0%, phone shut down.
    - Flashed Docomo - then UK firmware build 181 - then Global 2.3.4 build 283 --> PIN 0%, phone shut down.
    - Flashed Docomo - Installed custom ROM Blend@ARC --> PIN 0%, phone shut down.

    That's all what I've tested on my Arc.

    Through all my tests, I think this issue is some kind related to the kernel of the 2.3.4.

    Now I'm using the modified Docomo's firmware and the phone runs fine (PIN said 1%).
    This is a temporary solution until the permanent solution is out.

    Hope this help!
    View

New posts