Develop Bugs

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"

Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.

For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.

Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:

neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?

Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.

That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.

Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.

neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.

Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.

I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.

Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)

[App] [SafetyNet Passer] Pass SafetyNet after 2017-07-17 on Magisk V13

Hello XDA,
As we are all aware that once again Google broke SafetyNet Passing as they have extended their property scanning | Original Article here
The temporary fix was originally mentioned on this thread by @[email protected]
However you had to do the terminal commands after every reboot, thus Me and a few friends took this idea and created an app that does the same for you in the background and thus an easy temporary fix.
All you have to do is to install the apk as usual, grant it supersu permission and click to fix :laugh:
GitHub: https://github.com/Agusyc/SafetyNetPasser | Credits @Agusyc15
Download APK
Made a Quick Video Here
Tested Working on Oneplus 5 & Pixel XL | Magisk V13.2
Development Credits: @Agusyc15 & @unknownblkman
Magisk Credits as always @topjohnwu
Original Fix & ADB Commands: @[email protected]
PS: This is a temporary fix, I am sure @topjohnwu is aware of this situation and an official fix should be out soon :fingers-crossed:
Never Settle :highfive:

Reserved

You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol

Interceptor777 said:
You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol
Click to expand...
Click to collapse
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?

Bewildered Wolf said:
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?
Click to expand...
Click to collapse
Resurrection Remix with Spectrum kernel app, running lightning kernel LOS version which supports it.
The symbol on the quick settings is a quick profile switcher for spectrum, this is what it looks like on balanced profile.
Also, theme is also called spectrum on the play store.

Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.

GitHub along with the Updated apk now uploaded on the OP | Credits @Agusyc15

hachamacha said:
Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.
Click to expand...
Click to collapse
Please try the new apk uploaded on the OP :fingers-crossed:

Funk Wizard said:
Please try the new apk uploaded on the OP :fingers-crossed:
Click to expand...
Click to collapse
Just tried it and it works fine as did your first. Thanks!

@Funk Wizard you can also purpose the recovery flash solution (by noahajac) available from Github : here
Personaly i prefer flash the fix by this way instead of install a apk/service for fix SafetyNet each boot

Magisk 13.2 has been released and fixes the SafetyNet test failing.
Magisk 13.2
I can confirm that it's working for me.

Magisk 13.3 already available, and everything is fixed

Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?

13.3 fixed for me

Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.

Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.

crumble6 said:
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.
Click to expand...
Click to collapse
That didn't work for me unfortunately.
ArkAngel06 said:
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.
Click to expand...
Click to collapse
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Thanks guys!

Binary Assault said:
That didn't work for me unfortunately.
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Click to expand...
Click to collapse
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.

crumble6 said:
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.
Click to expand...
Click to collapse
Ya, I just discovered this. I actually noticed a few things,
My original issue was caused by a module I installed
It seems anything I flash via TWRP makes Magisk manager fail.
Most modules I installed in TWRP that fails, will properly install within Magisk manager.
For me, the culprit was doze for Google play services. Even installing it via Magisk manager froze Magisk manager.
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.

Binary Assault said:
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.
Click to expand...
Click to collapse
Just delete the module folder from /magisk and reboot. You will need root access for this but from what I've found, root access still works even though Magisk Manager is not responding.

Where can i find a version of busybox that will work?

i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.

equlizer said:
i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.
Click to expand...
Click to collapse
Use the Magisk Module Busy Box for Android NDK. Works great.

felosisman said:
Use the Magisk Module Busy Box for Android NDK. Works great.
Click to expand...
Click to collapse
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?

equlizer said:
Where do i find it? thx
Click to expand...
Click to collapse
Open Magisk Manager, go-to Downloads, find and download "BusyBox for Android NDK 1.27.2", reboot and profit.

Noob question but what is BusyBox and what's it's purpose

mackentosh said:
Noob question but what is BusyBox and what's it's purpose
Click to expand...
Click to collapse
Busybox allows programs to perform actions on your phone using Linux commands. So some apps require it to run some commands and wont work without it.

equlizer said:
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?
Click to expand...
Click to collapse
You shouldn't be getting that error anymore if you're using the latest Magisk release. He released version 15.0(1500) a couple days ago, but that was actually fixed in the last beta 14.6.
You would have to reflash your Kernel boot and dtbo and repatch though with the new version. I just used the Magisk Uninstaller script in TWRP, flashed the latest zip of flash Kernel then latest Magisk in TWRP and all good.

Flashfire Alternative

Hey everyone, i got a new j6+ (sm-j610f) running 8.1 oreo. I rooted it via magisk patched boot.img method , also removed all the bloatware. I want ro install xposed framework but this device doesn't have a compatible twrp/cwm recovery yet, i tried using flashfire but it's not working. I'm not sure if the app isn't compatible with oreo or magisk, i granted it superuser permission but it's stuck on acquiring root access. Is there a fix for this problem, if not is there an alternative for flashfire?!

dope77 said:
Hey everyone, i got a new j6+ (sm-j610f) running 8.1 oreo. I rooted it via magisk patched boot.img method , also removed all the bloatware. I want ro install xposed framework but this device doesn't have a compatible twrp/cwm recovery yet, i tried using flashfire but it's not working. I'm not sure if the app isn't compatible with oreo or magisk, i granted it superuser permission but it's stuck on acquiring root access. Is there a fix for this problem, if not is there an alternative for flashfire?!
Click to expand...
Click to collapse
Magisk already has Xposed support. No need to install the framework separately.
Just type Xposed in the download section and install the SDK 27 version.

ashyx said:
Magisk already has Xposed support. No need to install the framework separately.
Just type Xposed in the download section and install the SDK 27 version.
Click to expand...
Click to collapse
I tried this, no success

dope77 said:
I tried this, no success
Click to expand...
Click to collapse
Are you sure you have the latest version of Magisk installed?
Also save and post the log after install.

ashyx said:
Are you sure you have the latest version of Magisk installed?
Also save and post the log after install.
Click to expand...
Click to collapse
Magisk manager says that i have the latest version

dope77 said:
Magisk manager says that i have the latest version
Click to expand...
Click to collapse
update-binary[102]: /sbin/.core/mirror/bin/magisk: not found
Have you got stuff hidden?

ashyx said:
update-binary[102]: /sbin/.core/mirror/bin/magisk: not found
Have you got stuff hidden?
Click to expand...
Click to collapse
Look, here's how i got this phone rooted, downloaded magisk manager, patched the boot.img and flashed through odin, restored phone to factory settings bcz i was stuck with integrity verification failed and there was no way to flash dm verify disabler since there is no custom recoveries for j6+ yet. After that phone booted and magisk was installed. Haven't touched any settings nor hidden any things, and there's this message i keep getting whenever i open magisk. Each time i open magisk it popups, even if i press yes it will appear the next time open magisk.

This is the log i get after installing the additional setup
- Detecting target image
- Target image: /dev/block/mmcblk0p23
- Device platform: armeabi-v7a
- Existing zip found
- Extracting files
Killed
Killed
Killed
- Unpacking boot image
Killed
Killed
Killed
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
Killed
! Unable to repack boot image!
! Installation failed

This commonly happens whe u don't have the latest MAGISK installed NOT MAGISK MANAGER.

Anyone get Viper4Android to Work on Q?

Before I go back to 9.0.0, i figured i would ask....
Anyone get Viper4Android to install properly on Q?
I tried the latest Viper Magisk Module v1.4.2 i think... Magisk completed the installation but after reboot, Viper is requiring Drivers to be installed. So i install the Drivers, which took longer then normal, reboot and BAM! Viper needs to install Drivers on your device.
So Q doesnt seem to wanna play well with the Viper drivers.
And i tried installing Busybox for ****s and giggles and install fails in Magisk....
Thanks in advance for any assistance and/or **** head comments,
T

HACK3DANDR0ID said:
Before I go back to 9.0.0, i figured i would ask....
Anyone get Viper4Android to install properly on Q?
I tried the latest Viper Magisk Module v1.4.2 i think... Magisk completed the installation but after reboot, Viper is requiring Drivers to be installed. So i install the Drivers, which took longer then normal, reboot and BAM! Viper needs to install Drivers on your device.
So Q doesnt seem to wanna play well with the Viper drivers.
And i tried installing Busybox for ****s and giggles and install fails in Magisk....
Thanks in advance for any assistance and/or **** head comments,
T
Click to expand...
Click to collapse
Try using this viper apk, it generates a magisk module when you reboot the phone. In the latest update post, OP says:
The compatibility mode switch has been added back. This seems to be mandatory for car mode and some android q builds.
Click to expand...
Click to collapse
Worth a try

TENN3R said:
Try using this viper apk, it generates a magisk module when you reboot the phone. In the latest update post, OP says:
Worth a try
Click to expand...
Click to collapse
Yea thanks for trying but no go. The apk did install the Magisk Module, Drivers took 2-3 times but finally took. Driver Status is all NOs and Unsupported Sometime soon i'm sure...