Database Info

Systemless root info

There seems to be a lot of issues regarding the systemless root method. Here is some help/basic info.
Prerequisite:
1. Bootloader must be unlocked
2. Must have TWRP recovery installed
How to systemless root:
1. Download SuperSU v2.61 or SuperSU v2.62-3. Both work, I use the v2.62-3.
2. Flash either in TWRP recovery. Reboot to system. You now have systemless root.
Problems/Fixes:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
2. One of your favorite root apps doesn't see that your rooted? Do THIS.

I update super su from the playstore without issues.

kadopt said:
I update super su from the playstore without issues.
Click to expand...
Click to collapse
Could you explain your process? I tried updating from the 2.61 and had issues.

gokart2 said:
Could you explain your process? I tried updating from the 2.61 and had issues.
Click to expand...
Click to collapse
Well, to get root (systemless) you flash super su 2.62-3 with twrp, then go to playstore and update super su app, open Super su and a pop up will indicate that your binaries need updating, press OK and wait until it's complete, then just reboot your device.

Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:

gokart2 said:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
Click to expand...
Click to collapse
Where can one find this magical "How to systemless root" list of safe-to-flash systemless SuperSU?
And I assume only the BETA versions are systemless? I have tried flashing the latest STABLE v2.76 and it just stuck on boot.
The SuperSU v2.62-3 that you mentioned does work but just want to find the latest version to flash.

jason2678 said:
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
Click to expand...
Click to collapse
Adding the single line text file to /data worked for me to root stock 1575 18-4 with the latest Supersu 2.76 stable.

Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
The systemless file contains the following:
SYSTEMLESS=true
BINDSYSTEMXBIN=false
Click to expand...
Click to collapse
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.

Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
Click to expand...
Click to collapse
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.

csrow said:
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
Click to expand...
Click to collapse
Yeah I'm hoping this will make it easier for those who are flashing SuperSU and ending up with an un-bootable phone due to the installer defaulting to system root in newer versions.
I've removed the permission script since I had no idea 2.76 now applies it. Thanks for the heads up!

Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
Click to expand...
Click to collapse
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:

Edvin73 said:
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Click to expand...
Click to collapse
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!

Spasticdroid said:
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Click to expand...
Click to collapse
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app

Ijspegel said:
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, I have updated the zip to fix this and it will now find and flash it.

Spasticdroid said:
Yes, I have updated the zip to fix this and it will now find and flash it.
Click to expand...
Click to collapse
Thank you for your work on this one, it is very helpfull!?
Sent from my XT1572 using XDA-Developers mobile app

Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
Thanks man, your script was the only thing that worked for me, but now wifi isn't working. what can I do?

Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
OMG THANK YOU
I had accidentally installed the wrong SU and i thought I would have to wipe my entire device after hours of trying different methods. Yours was the only one that worked and my phone booted back on. Thank you so much.

Taking a risk of sounding stupid, will your SystemLess Root work for Android 7.0 Nougat?

Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .

phillyguy /northeast said:
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
Click to expand...
Click to collapse
Didn't we fix this in another thread?!?!

Pokemon GO on Oneplus One custom ROM

Hey guys
Is there any method working with the newest version of Pokemon GO to allow Oneplus One custom ROM users to play this game? The Internet is full of methods, I've already tried some but didn't work. Do you have any working idea for now?
Thanks in advance

Check your inbox.
But for all the other folks.
1. Install suhide http://forum.xda-developers.com/apps/supersu/suhide-t3450396 (via recovery)
2. Install root switch apk https://www.asus.com/zentalk/tw/for...wNDk1fGJmMjhjZGZifDE0NzY0MDUzNjB8MHwxNzM1NDI=
3. Start the root switch app and toggle the first switch off (this will "disable" your root).
4. Play the game
5. If your ready playing and you wanna use root again just toggle the switch back on in the root switch app.

Just search for magisk
Sent from my A0001 using XDA-Developers mobile app

massivekind said:
Check your inbox.
But for all the other folks.
1. Install suhide http://forum.xda-developers.com/apps/supersu/suhide-t3450396 (via recovery)
2. Install root switch apk https://www.asus.com/zentalk/tw/for...wNDk1fGJmMjhjZGZifDE0NzY0MDUzNjB8MHwxNzM1NDI=
3. Start the root switch app and toggle the first switch off (this will "disable" your root).
4. Play the game
5. If your ready playing and you wanna use root again just toggle the switch back on in the root switch app.
Click to expand...
Click to collapse
Do I need SuperSU installed? I like built in root in CM14.1

dasti555 said:
Do I need SuperSU installed? I like built in root in CM14.1
Click to expand...
Click to collapse
In the topic of suhide you can find the following
Requirements
- SuperSU v2.78 SR1 or newer (link)
- SuperSU installed in systemless mode
- Android 6.0 or newer
- TWRP (3.0.2 or newer, with access to /data - link!) or FlashFire (link)
So yes, you need supersu.

massivekind said:
In the topic of suhide you can find the following
Requirements
- SuperSU v2.78 SR1 or newer (link)
- SuperSU installed in systemless mode
- Android 6.0 or newer
- TWRP (3.0.2 or newer, with access to /data - link!) or FlashFire (link)
So yes, you need supersu.
Click to expand...
Click to collapse
- SuperSU installed in systemless mode
This mean normally flashed SuperSU.zip or I need to do something more?
Because I just flashed SuperSU SR4.zip and after that I wanted suhide0.55.zip and I can't "error 1 - check if you have atleast SR1 installed"
Can it be because of some kind of "november update"?

dasti555 said:
- SuperSU installed in systemless mode
This mean normally flashed SuperSU.zip or I need to do something more?
Because I just flashed SuperSU SR4.zip and after that I wanted suhide0.55.zip and I can't "error 1 - check if you have atleast SR1 installed"
Can it be because of some kind of "november update"?
Click to expand...
Click to collapse
You can just flash the zip

massivekind said:
You can just flash the zip
Click to expand...
Click to collapse
Too bad because I can't :/

Can't install busybox on 32.3.A.0.378, patched stock kernel and phh's superuser.

Hi!
Today I have updated my E6653 from 32.2.A.5.11 (with Chainfire's SuperSU) to the newest version 32.3.A.0.378 (with phh's superuser) using the "Customized NOBA" package, downloaded via XPeriFirm.
Everything seems to work fine and I have root access. I can create new files in "/system/xbin" by using the RootExplorer, but I cannot install busyboy (pro).
Every time I try to install it to "/system/bin" or "/system/xbin" it fails, telling me I have to chose another location. And if I try to install it to "/su/bin" it tells me that systemless root is not installed.
What I did to upgrade my phone:
1) Downloaded 32.3.A.0.378 via XPeriFirm
2) Removed build.xml and created a new bundle
3) Extracted the kernel and patched it by using "rootkernel v5.23"
3a) Disabled: RIC and dm-verity
3b) No superuser, no busybox
4) Flashed the custom bundle (wiped everything, except user data)
5) Flashed patched kernel
6) Installed phh's Superuser app.
Everything worked as expected.
But after I was not able to install BusyBox I rebuild the kernel and this time I installed superuser.zip to it.
3b) phh's superuser with unmodified config.txt => installed permissive
But the BusyBox installer is still not working.
How can I install BusyBox on my system?
Thank you very much!

Ikarisan said:
Hi!
Today I have updated my E6653 from 32.2.A.5.11 (with Chainfire's SuperSU) to the newest version 32.3.A.0.378 (with phh's superuser) using the "Customized NOBA" package, downloaded via XPeriFirm.
Everything seems to work fine and I have root access. I can create new files in "/system/xbin" by using the RootExplorer, but I cannot install busyboy (pro).
Every time I try to install it to "/system/bin" or "/system/xbin" it fails, telling me I have to chose another location. And if I try to install it to "/su/bin" it tells me that systemless root is not installed.
What I did to upgrade my phone:
1) Downloaded 32.3.A.0.378 via XPeriFirm
2) Removed build.xml and created a new bundle
3) Extracted the kernel and patched it by using "rootkernel v5.23"
3a) Disabled: RIC and dm-verity
3b) No superuser, no busybox
4) Flashed the custom bundle (wiped everything, except user data)
5) Flashed patched kernel
6) Installed phh's Superuser app.
Everything worked as expected.
But after I was not able to install BusyBox I rebuild the kernel and this time I installed superuser.zip to it.
3b) phh's superuser with unmodified config.txt => installed permissive
But the BusyBox installer is still not working.
How can I install BusyBox on my system?
Thank you very much!
Click to expand...
Click to collapse
Try with supersu, that way you can tell the source of the problem.

Hi!
A few seconds ago I managed the installation by using the custom installation path "/vendor/bin".
This is the location where the su binary is installed, too.
L33Tgod said:
Try with supersu, that way you can tell the source of the problem.
Click to expand...
Click to collapse

Ikarisan said:
Hi!
A few seconds ago I managed the installation by using the custom installation path "/vendor/bin".
This is the location where the su binary is installed, too.
Click to expand...
Click to collapse
Install via rootkernel..

Help!!!!

Hi,i updated my Htc A9 device from Marshmallow stock rom to Nougat official rom.
My Device Info:
***UNLOCKED***
S-OFF
CID BS_US001
MID 2PQ912000
Os 2.18.617.10​​I decided to root my device but i have problem on that!!!
Step 1- installed twrp 3.1.1-0 by fastboot mode
Step 2-installed Magisk Manager and download magisk v 12.0 zip file from magisk manager.
Step 3-Reboot to twrp recovery and select (Swipe To Allow Modifictions),then i flashed Magisk v 12.zip file from install menu and after that reboot device.(recovery log)
Step 4-Run Magisk Manager and see this Status:
installed magisk ver 12.0 --->Iatest version magisk installed and Properly rooted--->8:MAGISKSU
(tpjohnwu)Pic 1.
Superuser show on Magisk manager menu(Pic 2) and apps send request for permission to #superuser(Pic 3).
On the surface everything is OK but i have problem,for example i installed Link2SD app to use that for uninstall system apps and freez apps but does not work properly & show error msg(Pic 4).
I would be honored if you tell me what is my problem,thanks...

Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?

eavandijk83 said:
Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?
Click to expand...
Click to collapse
I can't install busy box,when o clicked on install button,busy box closed!!!!

cowboy_ea said:
I can't install busy box,when o clicked on install button,busy box closed!!!!
Click to expand...
Click to collapse
I think you'll be better off if you install the latest LOS ROM (20170530) and flash SuperSU. I don't know about Magisk, but I've never experienced problems with SuperSU. Once rooted, install busybox from the playstore and install into "system/xbin/"
In SuperSU make sure you override LOS root settings since it's set to off by default. By the way, you can turn on LOS root settings manualy. That way you don't need Magisk or SuperSU at all. Settings can be unlocked by tapping the build number several times in settings-->Device status. A menu will be unlocked called Developers options. Within that menu you'll find the root settings.
Good luck

[ROOT] and TWRP with squashfs 3.1.1 for Lg urbane 2nd

Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]

zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele

mminfor said:
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
Click to expand...
Click to collapse
you can check root trough adb
connect the watch and type this:
"adb shell"
"su"
you must have installed busybox on rails on the watch, you can try only booting the recovery with this command "fastboot boot twrp-3.1.1.0.img"

zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
I can confirm that you are correct that the TWRP does flash correctly and that the normal reboot to recovery works properly and I thank you for that, but the SU does not flash properly I get error 2 which indicates it does not work for the device (through searching) google, I forgot what that error was, I tested through the only app I see on wear that allows root and works, Advanced Settings and anytime I change the processor settings and exit the app, the same standard non-root settings appear again. Indicating that root was un-successful. I will see what I can do for the SU zip, becuase it appears to be related to the updater binary, the updater scirpt is usually more straigt forward, but sometimes harder to figure out. I will try to do what I can in this regard, but power might go out (Harvey) and circumstances might becom unfavorable throught this weekend.

try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M

zbask said:
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
Click to expand...
Click to collapse
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor

Working.
mminfor said:
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Click to expand...
Click to collapse
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.

physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
This solution seems to work.
Here's the check
thanks

zbask said:
Steps
Unlock bootloader
...
Click to expand...
Click to collapse
How exactly do you unlock the bootloader?

madsc13n41s4 said:
How exactly do you unlock the bootloader?
Click to expand...
Click to collapse
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
- adb reboot bootloader
- fastboot oem unlock
enjoy!

Is there any way we can pass SafetyNet for Android Pay using SuperSU?

???
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?

Grumps said:
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Click to expand...
Click to collapse
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.

Drakosha said:
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Click to expand...
Click to collapse
Isnt APN settings configured after you install a sim card from the provider? Surely it must then be stored somewhere else?

Did anyone succeed ?

what is about squashfs? is there anyway, to make /system/ writeable?

sebj84 said:
what is about squashfs? is there anyway, to make /system/ writeable?
Click to expand...
Click to collapse
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later

SQUASHFS is read only by default.
sebj84 said:
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
Click to expand...
Click to collapse
You won't be able to do anything within the /system/ partition while it is mounted. I can't answer the question as to why specifically, because I am not as knowledgeable of it, but here is the wiki SQUASHFS info. and another one that gives more information as to the uses SQUASHFS HOWTO.. If I am correct in order to make any changes to the system one would have to have a backup or original system image unsquash the image make any changes from that then re-squash the image and flash it in custom recovery. I have already unsquashed the image of the original image from the newest update myself and have it on my laptop, but I have not been able to go much further (busy). There are workarounds to the system not being able to write, but those are mostly for other versions of the filesystem and on different devices along with it not being totally writable.

Ok. I see now.
Thanks for the link. I will check those infos first.

physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
I changed my phone and I have on LG Urban 2 started the Wear Recovery procedure.
after restart, it will start only on TWRP. what can I do??
Thanks in advance
mminfor