Database Develop

The best way to calibrate batterystats.bin

Marvel, Zeus and another "G" key Recovery Roms
1. Shutdown the phone
2. Plug it on the charger
3. Wait until charged
4. Start the Phone and go directly into recovery with the G key.
5. Advanced - Mound SD Card
6. Advanced - Wipe Battery Stats
7. Reboot the Phone
8. Disconnect the charger when you're input on the pin.
9. Ready

use simply "battery calibration", download it from market

Dragusdrake said:
use simply "battery calibration", download it from market
Click to expand...
Click to collapse
that's not the best method.
The file is created when you start the Phone.

There's no battery calibration. Do you research.

dflt said:
There's no battery calibration. Do you research.
Click to expand...
Click to collapse
Exactly.
The "wipe battery stats" only deletes the file that contains the data about what used how much of the battery. The phone doesn't contain any "calibration" data related to battery, it's just an urban myth, deleting that file won't affect your battery in any way, only what's listed in the "Settings->About phone->Battery use" dialog.
For more info look at the following thread : https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT (or better yet read the XDA thread related to the issue : http://forum.xda-developers.com/showthread.php?t=1460553 )

[Q] REQ : PIT for 8.9 32G || Battery fake voltage and percentage

Dear Friends
i have galaxy tab 8.9 inch 32Gb
i need to downgrade from 4.0.4 to 3.2 because of battery problem
i did to 3.2 but still the same
now i need to flash 3.1
but
my device is 32gb should i use the same PIT.file labled P7300_P7310_p5_0614.pit or what
if i used former one it will not decreast the internal SD from 32 to 16 g
where i can get 32g pit file
thanks

For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app

lrcquest said:
For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app
Click to expand...
Click to collapse
Nothing usefull from that

Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium

lrcquest said:
Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did but the battery voltage show 0.004V
i think there is a problem my be fixed with full rom

Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium

lrcquest said:
Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did inside android
many program show this results as shown
Have u charged with phone off?
yes i did many times after i discovered this matter
Have u tried to take volt measurement in adb after charging?
yes correct measurement of voltage appear in 50% appear 3881

The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium

lrcquest said:
The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )

somaare said:
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )
Click to expand...
Click to collapse
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.

lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks i will try again today

lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks alot
i did that using my current installation just need to mount system to work on recovery mod
i downgrade to 3.1 using 5 files and update to 3.2
and i did the previous instruction and the battery now is very good and no fake percentage
But still fake voltage even using adb
see the attachment
i think my be some fail in files measure voltage
today morining to disconnect battery for 10 minute but the same problem
any program for the battery show voltage in MVor 0.00? V

U can use battery monitor widget. Always good measurements & worth timeline also.
The second voltage from the s2 might be divided by 1000 to get the right value.
Sent from my GT-N7000 using xda premium

Update 1.17.4.0.1234 bugs

Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.

phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?

souravipc53 said:
phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?
Click to expand...
Click to collapse
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.

reddevilx said:
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
On the asus forums a number of users said the latest 1234 update made the overheating and battery much worse.

reddevilx said:
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.

souravipc53 said:
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.
Click to expand...
Click to collapse
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers

heywheelie said:
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers
Click to expand...
Click to collapse
Tried this method. Doesnt work. Better use cyanogen mod and TWRP

Or try this:
1.0 [Preparation of your PC]
Download the ADB Tool HERE.
Click on the setup executable and type in "Y" for all the entries. (for the prompt on driver installation, simply click "Next", "Install", followed by "Finish").
1.1
Download the ASUS Software Update HERE.
Once completed, move the update file to C:\adb (where C: is the root drive where the ADB Tool was installed at).
2.0 [Preparation of Device]
Turn off your phone.
Press the "Volume Down" button followed by the "Power" button.
Keep holding the two buttons until the recovery screen appears, then release both AT THE SAME TIME.
Plug your phone into the PC.
On your phone, press the "Volume Down" button to select the option "apply update from adb".
Then, press the "Power" button once to select.
3.0 [Flashing]
Open the command prompt (Windows Key + R, type in "CMD" and enter).
Type in cd C:\adb (take note).
Then, type in adb sideload "downloaded file name".zip
4.0 [Finish]
Upon completion, make sure that the option "reboot system now" is selected on your phone.
Then, press the "Power" button once.

Is anyone using this update that is not experiencing any problems especially battery and heating?

No feedback anyone?
Sent from my GT-S7582 using Tapatalk

Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763

heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
I downgraded to V1.16 due to bugs and lag on v1.1.7.40.1234
Posted using a calculator and delayed by AT&T.
---------- Post added at 01:31 PM ---------- Previous post was at 01:29 PM ----------
shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
Mine keeps on overheating and it lags very bad. I downgraded mine to v1.16.
Posted using a calculator and delayed by AT&T.

shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
UPDATE: I don't know if it was caused by the update or not but I was on a call and the flashlight came on and Firefox and Settings opened.

willcall said:
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
Click to expand...
Click to collapse
Thanks. I wonder if the overheating and battery life problems only affects the Z00LD?

heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
Judging by the fact that a new update has not been released for quite some time now, the next update *should and hopefully, be marshmallow.
Sent from my ASUS_Z00LD using XDA-Developers mobile app

heywheelie said:
Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.
Click to expand...
Click to collapse
No issues on my ze550kl, no heating issue, no major bugs on 1.17.40.1234. But it becomes warm when I don't close any game and tap home button but that's normal.
1.17.40.1234 came with Wi-Fi and carrier network improvements. I guess people from certain region might be facing heating issue due to changes in modem. I am from India. No issues for me

I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.

dominati said:
I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.
Click to expand...
Click to collapse
Try using the auto-start manager and making sure the flashlight app does not start automatically then reboot the phone. High standby usage can sometimes be caused by a faulty microsd card. If you have one, try unmounting and then remountiing it and see if that helps. If it doesn't try reformatting it.

BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!

Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1

Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423

For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!

Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423

After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?

Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?

Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates

szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?

Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible

Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.

hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch

Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!

riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?

LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.

pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?

LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.

mediafire link is dead (twrp) - please, reupload it!

Thanks so much for this, it worked perfectly! So great to have my watch back!

Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.

Root for Android 9 Pie 50.2.A.0.352 out?

Sony rolled out Android Pie 9 50.2.A.0.352 for Xperia XA2 Ultra 2 days ago. I was wondering if I proceed with the update from my rooted Oreo, will I have any working Root for Android 9 for my phone?:silly:

Only a few regions has gotten Pie so far. Makes it hard to work on getting root when most of us are still waiting.
Edit: XA2 Ultra H3223 USA just got Pie today.

Looking for this one too hoping on of this days root method will come out ..
anyone tried using magisk ? the root method last time in Oreo ? want to try it out but i'm afraid my phone will get bricked

danger
qhuinzy_09 said:
Looking for this one too hoping on of this days root method will come out ..
anyone tried using magisk ? the root method last time in Oreo ? want to try it out but i'm afraid my phone will get bricked
Click to expand...
Click to collapse
You're rightly afraid. Steer clerar of magisk. Wait for a proper rooting method, or perhaps don't root at all.
This update is already a danger (see the previous brick wave), I would wait until things calm down.
XA2 Ultra owner, not updating. Staying on Android 8 for a good while.st

ish4d0w777 said:
You're rightly afraid. Steer clerar of magisk. Wait for a proper rooting method, or perhaps don't root at all.
This update is already a danger (see the previous brick wave), I would wait until things calm down.
XA2 Ultra owner, not updating. Staying on Android 8 for a good while.st
Click to expand...
Click to collapse
yeah mate Heard the brick update in russia just waiting for the proper Root method hope it will come out soon..
But the pie update is Really Good ! over all 9/10 and also noticed the battery is far longer now :good::good:

yes guys sony xa 2 ultra root in original rom normal the steps is the same of classic all time in all others rom idk if i make a deference but me use this step 1. run adb in my pc and write fastboot boot twrp-3.2.3-1-discovery.img step2. in twrp first install addonsu-16.0-arm64-signed.zip this file take of line age os 16 idk if this make the deference but me install first this file , so step 3. install magisk and reboot phone no install twrp in phone just restart and phone work very well in original rom pie9 H4213_Customized GR_1313-7447_50.2.A.0.352_R1B i hope help good luck to root your xa 2 ultra

malamas said:
yes guys sony xa 2 ultra root in original rom normal the steps is the same of classic all time in all others rom idk if i make a deference but me use this step 1. run adb in my pc and write fastboot boot twrp-3.2.3-1-discovery.img step2. in twrp first install addonsu-16.0-arm64-signed.zip this file take of line age os 16 idk if this make the deference but me install first this file , so step 3. install magisk and reboot phone no install twrp in phone just restart and phone work very well in original rom pie9 H4213_Customized GR_1313-7447_50.2.A.0.352_R1B i hope help good luck to root your xa 2 ultra
Click to expand...
Click to collapse
Strange! I was thinking exactly the same process would've been as you've mentioned but then I intended to wait for some expert reviews or suggestions. So you are saying that you did the root exactly the way Android 8 Oreo was rooted as in the process you mentioned? So how far has it been with Android 9 with Root access with you ?

root
noob_coder said:
Strange! I was thinking exactly the same process would've been as you've mentioned but then I intended to wait for some expert reviews or suggestions. So you are saying that you did the root exactly the way Android 8 Oreo was rooted as in the process you mentioned? So how far has it been with Android 9 with Root access with you ?
Click to expand...
Click to collapse
im not sure if understand you exacly your question but my phone work super fast and very stable just follow my steps and you done 100% safe
im try post some photos in my phone to see is real

Easy-Peasy Interactive root
_/easy[+EASY-PEASY+]easy\_
ii-I/n/T_e r-A-c t_I\v\E-ee​ i have conjured up a simple tool for rooting the xa2 ultra. nothing special, all you do is download the zip, extract it, and run the .bat file, and follow along in the cmd prompt window. its interactive so you will have to select a few options while in recovery. its really easy. bootloader must be unlocked. make sure to read the read me files, and also follow along with the command prompt.
hope someone tries it out. i would like some opinions. im not new to computers, but im new to scripting.
any feedback would be appreciated. go to the ftp site listed below and download Also stock android 9.0 is included, its seperate from the tool. extract the zip open folder and double click newflasher.exe its all set up. just select no on the 2 options that come up before the flashing, put your device in flashmode
ftp://
192.161.
227.
73

v1nd1cta_d3b3llat0tlr said:
_/easy[+EASY-PEASY+]easy\_
ii-I/n/T_e r-A-c t_I\v\E-ee​ i have conjured up a simple tool for rooting the xa2 ultra. nothing special, all you do is download the zip, extract it, and run the .bat file, and follow along in the cmd prompt window. its interactive so you will have to select a few options while in recovery. its really easy. bootloader must be unlocked. make sure to read the read me files, and also follow along with the command prompt.
hope someone tries it out. i would like some opinions. im not new to computers, but im new to scripting.
any feedback would be appreciated. go to the ftp site listed below and download Also stock android 9.0 is included, its seperate from the tool. extract the zip open folder and double click newflasher.exe its all set up. just select no on the 2 options that come up before the flashing, put your device in flashmode
ftp://
192.161.
227.
73
Click to expand...
Click to collapse
strange that when I unzip a 1.8GB or so zip it just ends up with 2 small files (bat and readme) (even tried pulling the constituent files out from the zip independently). Also the batch file won't run due to windows security (understand running .bat is always risky no matter how good one's intentions might be)

mac231us said:
strange that when I unzip a 1.8GB or so zip it just ends up with 2 small files (bat and readme) (even tried pulling the constituent files out from the zip independently). Also the batch file won't run due to windows security (understand running .bat is always risky no matter how good one's intentions might be)
Click to expand...
Click to collapse
hey, thanks man, im new to this so i really apprecite it. i unzipped the 1.8gb zip, left it for download, and also left the unzipped folder and unhid everything. i left a NOTE to do explain a little better, not much, but its a little more than i am now. i changed permissions on my end, so it should be ok. as long as everything stays together in the same directory, for example the desktop,...... it doent have to be that folder, but it cant be in any other folder either, as long its all on the desktop, its good. i figure you already know that, but it makes me feel better to let you know. the .bat extracts 3 other .zip, one .zip is a usb driver and it installs it also. you can hit no, cmd will read access denied, but in this script its not considered an error, so it will continue. it will also connect to adb automatically and push 2 files, .img, .zip, to the device. if there is a problem with adb connecting, it will give notice, prompt, and when hit enter it will kill adb server and exit cmd. if everything is ok,it will boot the recovery .img automatically, given you press enter to give it permission. once in recovery it prompts instructions for the user, and a new instruction will show after every enter. well, i guess i did explain it better than i did in that NOTE.
hope i dont sound to retarded and noobish, and i hope you give it another go.
again thank you, much appreciated
.

v1nd1cta
noticed your bat file has the zip file in system32 directory
the bat file does not work due to the paths I am guessing. Why would the zip want to be in system 32 windows directory?

any update? a safe way to root in android 9?

v1nd1cta_d3b3llat0tlr said:
hey, thanks man, im new to this so i really apprecite it. i unzipped the 1.8gb zip, left it for download, and also left the unzipped folder and unhid everything. i left a NOTE to do explain a little better, not much, but its a little more than i am now. i changed permissions on my end, so it should be ok. as long as everything stays together in the same directory, for example the desktop,...... it doent have to be that folder, but it cant be in any other folder either, as long its all on the desktop, its good. i figure you already know that, but it makes me feel better to let you know. the .bat extracts 3 other .zip, one .zip is a usb driver and it installs it also. you can hit no, cmd will read access denied, but in this script its not considered an error, so it will continue. it will also connect to adb automatically and push 2 files, .img, .zip, to the device. if there is a problem with adb connecting, it will give notice, prompt, and when hit enter it will kill adb server and exit cmd. if everything is ok,it will boot the recovery .img automatically, given you press enter to give it permission. once in recovery it prompts instructions for the user, and a new instruction will show after every enter. well, i guess i did explain it better than i did in that NOTE.
hope i dont sound to retarded and noobish, and i hope you give it another go.
again thank you, much appreciated
.
Click to expand...
Click to collapse
ftp not working btw

There only seems to be Magisk root for up to 50.1.A.13.83 (Oreo)... Which is a massive pain because there have been tons of updates since, including Android Pie. I check this site loads and still nothing towards rooting for Pie.

So, not sure if this helps, but magisk seems to install fine in pie, but so far I'm having a ton of issues regarding freezes and reboots. Will search for a kernal fix, anyone have a clue to this? Just thought I'd inset my 2¢ into this and see if anyone has any insight to this. Thanks guys you do great work ?