Database Info

[Completed] I root my honor u19 .when I install super su it ask to install binary su but fail to

I root my honor u 19 today. When I install super su app it ask to update su binary by normal mode or cw recovery mode but when I clik on normal mode it say that there is an error to install su binary and cw recovery mode also don't work. I install some other apps that need root permissions they also doesn't work properly.
When I try to access and edit something in the device folder it also doesn't work.I install root checker it says that your device is rooted. What does this means. Please give me solution so that i can have full access to my device please help me..

XDA Visitor said:
I root my honor u 19 today. When I install super su app it ask to update su binary by normal mode or cw recovery mode but when I clik on normal mode it say that there is an error to install su binary and cw recovery mode also don't work. I install some other apps that need root permissions they also doesn't work properly.
When I try to access and edit something in the device folder it also doesn't work.I install root checker it says that your device is rooted. What does this means. Please give me solution so that i can have full access to my device please help me..
Click to expand...
Click to collapse
Hello, and welcome to XDA. One idea would be to download it and flash it manually instead of using an app. You will find plenty of support for doing this here: http://forum.xda-developers.com/showthread.php?t=1538053. Scroll down to "CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu" and then you can download and flash. But the best thing is to read the whole original post so you have a better idea of what you're doing and where to look for help.
Good luck!

[GUIDE] [How To] Install Xposed in Yuphoria

Requirements:
1. Rooted Yuphoria phone
2. Flashed with any custom recovery like TWRP or CWM (I haven't tried using CWM)
Steps:
1. Download Xposed Framework ZIP file from here: [OFFICIAL] Xposed for Lollipop/Marshmallow [Android 5.0/5.1/6.0]
(Click here for Unofficial Systemless Xposed)
For MiUI ROM, check this out: [UNOFFICIAL][5.0/5.1/6] Xposed for MIUI by SolarWarez
Important Note:
The First Yuphoria (YU5010) is arm64 architecture..
The later Yuphoria Pure Stock Android (YU5010A) is arm (32bit)
This thread is for Yu Yuphoria only. For other devices, Check build.prop's ro.product.cpu.abi to find whether arm/arm64/x86
Marshmallow (Android 6.0.x) or CM13 based ROMs are sdk23
Lollipop (Android 5.1.x) or CM12.1 based ROMs are sdk22
Lollipop (Android 5.0.x) or CM12 based ROMs are sdk21
Correspondingly, download the xposed-vXX-sdkYY-architecture.zip file..
(XX represents the current version, which is subject to change)
2. Place it in Internal Storage of phone and boot into custom recovery.
3. Now flash the zip file and reboot the phone..
(The device will take around 5 minutes to boot up since the dalvik cache is cleared during flashing)
4. Download and Install the app XposedInstaller.apk from: Xposed Installer Material Design
That's it!! Xposed Framework is Installed in your phone.
You can now start using your favorite Xposed modules (apps).
Note:
If you face bootloop, wait for 5-10mins to ensure it's a bootloop..
If yes, just flash the uninstaller.zip to remove Xposed..
Credits:
@rovo89 for the wonderful Xposed Framework
@vishal_android freak for TWRP
@DooMLoRD for CWM
Hit the Thanks button if it worked

Will try this... Tnx for sharing
Sent from my Yu Yuphoria
Read my thread EXTREME BATTERY BACKUP FOR YUPHORIA [GUIDE]

not working
GokulNC said:
Requirements:
1. Rooted Yuphoria phone
2. Flashed with any custom recovery like TWRP or CWM (I haven't tried using CWM)
Steps:
1. Download Xposed Framework ZIP file from here: Xposed for Lollipop [Android 5.0/5.1] (See attachments there)
Important Note:
For CM13 or any CM13 (6.0.x) based ROM, download the file named xposed-vXX-sdk23-arm64.zip from there
For COS 12.1 or any CM12.1 (5.1.x builds) based ROM, download the file named xposed-vXX-sdk22-arm64.zip from there
For COS 12 or any CM12 (5.0.x builds) based ROM, download the file named xposed-vXX-sdk21-arm64.zip from there
For pure Lollipop 5.1 (32bit), download the file named xposed-vXX-sdk22-arm.zip
(XX represents the current version, which is subject to change)
2. Place it in Internal Storage of phone and boot into custom recovery.
3. Now flash the zip file and reboot the phone..
(The device will take around 5 minutes to boot up since the dalvik cache is formatted during flashing)
4. Download and Install the app XposedInstaller_3.0_xxxxxX.apk from: Xposed for Lollipop
That's it!! Xposed Framework is Installed in your phone.
You can now start using your favorite Xposed modules (apps).
Credits:
@rovo89 for the wonderful Xposed Framework
@vishal_android freak for TWRP
@DooMLoRD for CWM
Hit the Thanks button if it worked
Click to expand...
Click to collapse

mdsaifalamansari said:
not working
Click to expand...
Click to collapse
What's not working??
This is for Yuphoria phone only.

yeah... i am using yuphoria only..when i updated to official cm12.1 OS and try to flash xposed zip via TWRP i got the error

mdsaifalamansari said:
yeah... i am using yuphoria only..when i updated to official cm12.1 OS and try to flash xposed zip via TWRP i got the error
Click to expand...
Click to collapse
What error?

error
GokulNC said:
What error?
Click to expand...
Click to collapse
cp :write error: n space left on the device
E: error executing updater binary in zip '/sdcard/xposed-v75-sdk22-arm64.zip'
---------- Post added at 06:53 AM ---------- Previous post was at 06:48 AM ----------
GokulNC said:
What error?
Click to expand...
Click to collapse
i have mailed you the error image on [email protected] hope you will find the solution soon....

mdsaifalamansari said:
cp :write error: n space left on the device
E: error executing updater binary in zip '/sdcard/xposed-v75-sdk22-arm64.zip
Click to expand...
Click to collapse
Is your phone rooted?
If yes, install Link2SD app..
Then uninstall any useless system app like 'Tags' or 'CM Bug Report' or 'Google Play Movies' using Link2SD so that you'll get some free space in system partition.
Then flash xposed now.

Hey bro. I deleted google play movies and google play books. After that i flashed the xposed.. It just perform very well on cm12.1 stock rom. Greenify is upto the extent.... But camera shows can't connect to camera app. Even i use third party camera app. It still shows the same thing. After that i flash cm12.1 camera and gallery app once again but not worked on yuphoria...
I'm long waiting for xposed for stock rom on yuphoria....

My yuphora get soft brick when i flashed framework
Sent from my YU5010 using XDA Free mobile app
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
So then i flashed cm12.1 firmare
Sent from my YU5010 using XDA Free mobile app

mayankbanga18 said:
Hey bro. I deleted google play movies and google play books. After that i flashed the xposed.. It just perform very well on cm12.1 stock rom. Greenify is upto the extent.... But camera shows can't connect to camera app. Even i use third party camera app. It still shows the same thing. After that i flash cm12.1 camera and gallery app once again but not worked on yuphoria...
I'm long waiting for xposed for stock rom on yuphoria....
Click to expand...
Click to collapse
I'm using stock COS12.1 and facing no issues.
Maybe an Xposed module that you installed is messing with the camera.
adityamishraa said:
My yuphora get soft brick when i flashed framework
Click to expand...
Click to collapse
Hey, that is NOT soft brick, if you think your phone is stuck in boot loop by flashing Xposed.
Wait for 10-15 mins so that you'll see something like 'Optimizing Apps'.
(This is because the xposed zip clears the dalvik cache)

Gokul bro....
Could u pls tell me which xposed framework you're using.
I was using xposed-76-sdk22-arm64.zip
Which leads to camera can't comnect

mayankbanga18 said:
Gokul bro....
Could u pls tell me which xposed framework you're using.
I was using xposed-76-sdk22-arm64.zip
Which leads to camera can't comnect
Click to expand...
Click to collapse
I'm now using xposed-v79-sdk22-arm64.zip on my COS12.1

GokulNC said:
I'm now using xposed-v79-sdk22-arm64.zip on my COS12.1
Click to expand...
Click to collapse
When trying, showing : error executing updater binary in zip '/sdcard/xposed-v75-sdk22-arm64.zip'

chan10 said:
When trying, showing : error executing updater binary in zip '/sdcard/xposed-v75-sdk22-arm64.zip'
Click to expand...
Click to collapse
bro i think u on cos 12.1 just download system app remover from play store and delete some system apps
and then u will be able to install

Can temp recovery can be used for xposed
Can use a temporary recovery of twrp for the usage of xposed. Is there any need of a permanent recovery for its functioning . Help me out . I know how to boot in temporary recovery using fastboot..

mukulmagotra98 said:
Can use a temporary recovery of twrp for the usage of xposed. Is there any need of a permanent recovery for its functioning . Help me out . I know how to boot in temporary recovery using fastboot..
Click to expand...
Click to collapse
Just flash TWRP using the app "Flashify" from Play Store

Recovery
Flashing by flashify will leads to permanent replacement of cyanogen recovery with TWRP due to which i will not be able to get updates . I have to reflash my cyanogen recovery once again to get updates

Thanks

Sir using of flashify completely removes ur stock recovery with the custom one .......
I am saying can we use a tempory recovery ( hotboot like ) to install xposed .... Is there is any need of a fixed custom recovery for its functioning....
Can this be done : Like use temporary twrp that vanishes on reboot to flash closed and use stock cyanogen recovery for its later functioning

[Q] Systemless SuperSU failed everytime (Binaries need to be updated)

Hello,
I have a problem and I will try to explain that precisely.
(I'm on Galaxy S6 G920F Stock Firmware)
I have tried to flash SuperSU in Systemless mode and I have followed this tutorial : http://forum.xda-developers.com/showpost.php?p=69412347&postcount=1215&branch_used=true
1st try :
Wiped all partitions and Flash Stock Firmware
Flash TWRP
SN Green response
Push Ramdisk and .supersu patch with ADB
In TWRP : Terminal : echo "SYSTEMLESS=true" > /data/.supersu
Flashed SuperSU SR2
Succeed with no error
And then... "Binaries need to be updated" in SuperSU app (even with reboot) and Root not working.
Then, I have tried with SR1 and SR3, not working too.
2nd try :
I have re-flashed the stock firmware (and wipe all partitions)
And tried again the same steps BUT NOW with Arter Kernel.
Not working too with SR1, SR2 and SR3.
I have missed something?
Thanks in advance!

Did you wipe data after install the SuperSU zip?

forumber2 said:
Did you wipe data after install the SuperSU zip?
Click to expand...
Click to collapse
I have a fresh install of the firmware, before installing the rom I have wipe data / system and all other
So no data left from my other rom

LucaXperia said:
I have a fresh install of the firmware, before installing the rom I have wipe data / system and all other
So no data left from my other rom
Click to expand...
Click to collapse
I mean did you wipe after install SuperSU zip, not before

forumber2 said:
I mean did you wipe after install SuperSU zip, not before
Click to expand...
Click to collapse
I have to wipe all my personal data after flashing SuperSU ?

LucaXperia said:
I have to wipe all my personal data after flashing SuperSU ?
Click to expand...
Click to collapse
You have to NOT wipe data after flashing SuperSU

forumber2 said:
You have to NOT wipe data after flashing SuperSU
Click to expand...
Click to collapse
Yeah, look at the first post, I updated it

I've had this same problem too. Here's what I did to resolve the problem
Code:
1. Clear all PHH SuperUser app data
2. Uninstall PHH SuperUser
3. Flash the latest version (r266 ATM)[URL="http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921"]HERE[/URL] phh super user binaries
4. Reboot and re-install PHH Superuser from market
5. Haven't had the issue since.
One thing I did notice was as long as you didn't need to request /new/ admin rights, things would still work. It was when you needed to grant a new app root access.

nolimit78 said:
I've had this same problem too. Here's what I did to resolve the problem
Code:
1. Clear all PHH SuperUser app data
2. Uninstall PHH SuperUser
3. Flash the latest version (r266 ATM)[URL="http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921"]HERE[/URL] phh super user binaries
4. Reboot and re-install PHH Superuser from market
5. Haven't had the issue since.
One thing I did notice was as long as you didn't need to request /new/ admin rights, things would still work. It was when you needed to grant a new app root access.
Click to expand...
Click to collapse
I would like to use SuperSU
And PHH seems to be not Systemless

LucaXperia said:
I would like to use SuperSU
And PHH seems to be not Systemless
Click to expand...
Click to collapse
PHH was specifically created to handle systemless.

[ROOT][L09/L19] Pre-rooted boot.img for P9 Nougat (b378)

This is now deprecated
See proper SuperSu root installation instruction by @hakaz here: https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Install stock b378 boot image (L09) here first: https://mega.nz/#!v1RGRSzD!7Z9oKmvEbZHG9UGwxh-iCR_tEw2qjVJ2tHkb1mFSTLk
Splitting this out into separate thread for better visibility. Note that if you are already on L09 B378 root, no need to update -
What is this?
Root on Nougat for the Huawei P9. It's a boot image, pre-rooted with PHH's SuperUser. Requires an unlocked bootloader.
Downloads:
B378
L09: https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
L19: https://mega.nz/#!blgUnDpD!OAiHXwXvUfJ36OZeNBFbVkBeEocnNc-irHHo5CxMjrA
Installation:
Root install method 1 (no TWRP)
Reboot phone into bootloader mode
Download boot.img to PC and fastboot flash with: "fastboot flash boot rooted_b378_boot.img"
Reboot phone back into system
Install phh's SuperUser app from Play Store
Install JRummy's Busybox Installer and install to /vendor/xbin
Root install method 2 (with TWRP)
Download boot.img to phone (Internal Downloads or External SD)
Use OldDroid's TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703/post71244945#post71244945
Reboot into TWRP
Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
Flash and reboot phone back into system
Install phh's SuperUser app from Play Store
Install JRummy's Busybox Installer and install to /vendor/xbin
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
No responsibility if this doesn't work/breaks your device/eats your cat etc. - make sure you backup your data and have a backup boot/recovery image handy
XDA:DevDB Information
Pre-rooted boot.img for P9 Nougat, Kernel for the Huawei P9
Contributors
Atarii, PHH, LastStandingDroid, OldDroid, Dkionline
Version Information
Status: Stable
Stable Release Date: 2017-03-17
Beta Release Date: 2017-01-20
Created 2017-03-17
Last Updated 2017-03-17

Update (17/03/2017):
* Added L19 pre-rooted boot.img

This is not systemless root yes? No OTA support?

askor said:
This is not systemless root yes? No OTA support?
Click to expand...
Click to collapse
Yes this is Systemless, OTA should be fine - I've manually flashed OTA via dload but not tested normal OTA upgrade

will this root method have any drawbacks compared to the standard method( installing twrp and then flasing super su) am i going to be able to do the same things that im able to do with any rooted device? thanks in advice

ricardo99831390 said:
will this root method have any drawbacks compared to the standard method( installing twrp and then flasing super su) am i going to be able to do the same things that im able to do with any rooted device? thanks in advice
Click to expand...
Click to collapse
SuperSu does not currently work on the P9 with Nougat, partially due to lack of loop mount support in the kernel. Kernel sources are needed to rectify this, so I encourage people to email Huawei asking for their Nougat kernel patches.
PHH is not perfect (some apps don't work fully) but it's the best we have right now

Atarii said:
SuperSu does not currently work on the P9 with Nougat, partially due to lack of loop mount support in the kernel. Kernel sources are needed to rectify this, so I encourage people to email Huawei asking for their Nougat kernel patches.
PHH is not perfect (some apps don't work fully) but it's the best we have right now
Click to expand...
Click to collapse
ohh okay thanks for the info and also the work, i guess im waiting till the fully working method is out.
I've heard that they will relase the source near this month or the next when they finsh updating every p9

Is it possible to use this prerooted boot.img for l19 honor 8?

No. It's for P9, Honor 8 isn't P9, right?

Atarii said:
Splitting this out into separate thread for better visibility. Note that if you are already on L09 B378 root, no need to update
What is this?
Root on Nougat for the Huawei P9. It's a boot image, pre-rooted with PHH's SuperUser. Requires an unlocked bootloader.
Installation:
Root install method 2 (with TWRP)
Download boot.img to phone (Internal Downloads or External SD)
Use OldDroid's TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703/post71244945#post71244945
Reboot into TWRP
Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
Flash and reboot phone back into system
Install phh's SuperUser app from Play Store
Install JRummy's Busybox Installer and install to /vendor/xbin
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
Click to expand...
Click to collapse
Thank you for the guide, everything worked as described. I've got my P9 with c432 b378, rooted and TWRP installed.
By testing so far, RootChecker, AdAway (v3.2), Titanium and Reboot (to boot into TWRP or fastboot) all work fine with this phh's SuperUser
PS: It's possible to install Chainfire's SuperSU instead, and Viper4Android works too, see e.g.
https://forum.xda-developers.com/showpost.php?p=71761747&postcount=167

Hi all, is that ok to flash on my current P9 L09C432B383 ?
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Thanks

twerg said:
Hi all, is that ok to flash on my current P9 L09C432B383 ?
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
flash this, V3 is the version i would suggest.

[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