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)

root with Magisk on Oreo.

I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.

DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers

jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).

DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?

humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct

I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?

the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol

j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.

Check out this post, it works like a charm.

Ressurection Remix boots to bootloader when Magisk is installed.

Hello,
This one is a funny one, as on my OnePlus 2 rooting was easy but ever since I got my OnePlus 5T I've always had issues, rooting it in the first place was troublesome but managed to get Magisk running with OOS and I have decided to migrate to Resurrection Remix (What I used to run on OnePlus2) when I format my data and flash RR and gapps it runs perfectly fine, but when I flash Magisk it states it has successfully changed the boot.img and when I restart the system it ends up going to the bootloader, I can then run the Magisk uninstaller and my RR will run normally again.
Magisk definitely seems to be the issue but I don't know why, I have gone back to stock firmware and locked my bootloader and tried again from stock and still, after installing the latest RR with Magisk after the first initialisation I get no errors it just doesn't boot.
Has anyone got any idea of what I could do wrong, I have found myself following guides online with no luck. As no one seems to have an issue similar.
An advice?

As far as I know.magisk should be flashed only after booting into system and completing the initial setup

Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486

rakuyo said:
As far as I know.magisk should be flashed only after booting into system and completing the initial setup
Click to expand...
Click to collapse
I do install it after the intial set up and it still doesn't load :/

nicorvienne said:
Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486
Click to expand...
Click to collapse
Thanks this was my solution, just needed to flash a custom kernel.

NarcoticNoble said:
Thanks this was my solution, just needed to flash a custom kernel.
Click to expand...
Click to collapse
You are welcome!

Magisk needs to be installed after every reboot?

I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?

boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
Flash magisk v18.1 and it will work fine. Don't update Magisk. Some roms have this bug.

boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
If you reboot it should reappear (it does for me).
I don't know what's the root cause, I'll just wait patiently for a fix. Unfortunately I don't have time to troubleshoot or provide logs to whoever to help the investigation.
PS: in your description be more accurate "latest version of xyz" means nothing. Specify exactly which version. Especially there is stable and beta!

Question Magisk Update doesn't run very well :(

Hello guys.
Unfortunately the today Magsik Update doesn't run very well on my Device. I did update to the available slot then reboot but the bootsplash now runs since 1H without being able to land on OOS. I'm on 11.2.5.5.LE15 BA + Omega Kernel latest build
Fastboot mode doesn't report any bootloader version nor baseband version.
What's the best way to repair that ? What was the mistake I did to prevent further error while I'm updating magisk or the Kernel ?

Ty @avid_droid but that's what I tried first. It leads me to the exact same type of Boot where nothing happens for 30 minutes excepts the bootsplash logo animation.
I did try to boot from the vanilla boot.img ... but that sent me directly to crashdump mode.
I then boot one last time to magisk_boot.img and .... it worked.
For some reasons everything was wiped on the device even if I never wipe anything from fastboot but no matter ... I'm now back in OOs and try to set it up completly

It's not Magisk, I updated to version 23 with no issues at all.
Also flashed the new Omega kernel afterward, no issues with that either, Magisk was still retained.
I would see if you can get into recovery, if you can then do a system reset and see if the phone will let you set it up again.

For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^

Fre$h said:
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Click to expand...
Click to collapse
I did it the other way round, updated Magisk app, then Magisk itself, rebooted the phone. Installed the latest kernel using EX Kernel manager, it noted that Magisk was there so re-applied it on the new kernel, then rebooted and it was fine after that.
I'm not using any Magisk modules though, not going to risk that until we have a good recovery.

avid_droid said:
Same here. I keep magisk modules to a minimum. I am however playing with substratum and we know how that usually ends up haha. Giving it a go. Trying to remember the signal icons I used to use
Click to expand...
Click to collapse
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either

djsubterrain said:
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
Click to expand...
Click to collapse
Liv dark works now on op9pro OS11.. I'm using several different themes from livDark now

All I need to do here just hit "install"?
Ive never done it before so I just don't want to screw up.

First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update

Fre$h said:
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Click to expand...
Click to collapse
Thx bro...all good

This is particularly here we miss TWRP to flash magisk uninstaller properly. I like the way we can temporary boot from rooted boot.img but the disadventage is that we need a computer just near us to do that.
Hope everything is now fixed