Related
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)
Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:
uutsav said:
Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:
Click to expand...
Click to collapse
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]
tropicanapure said:
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]
Click to expand...
Click to collapse
And you passed safety net
uutsav said:
And you passed safety net
Click to expand...
Click to collapse
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.
tropicanapure said:
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.
Click to expand...
Click to collapse
I tried flashing unsu and it asked me to flash the stock boot image in TWRP.... Any ideas mate..
I am sorry to keep bugging.... But I am lost
Look for boot.img in the ROM zip and flash it.
I was just about to say that myself. See
https://forum.xda-developers.com/showpost.php?p=63615067
Like the previous post said, you need a pristine boot.img and your ROM zip is the ideal place to find it.
Dirty flash your Beta27 again and it should be clean, THEN reboot and then install Magisk
Now i flashed beta 28, flashed recovery and flashed magisk again... While I was able to flash it... But getting safety net error....
My life is finished...
If you were able to install magisk then you should take this to the official magisk support thread. You are more like to get a better variety of suggestions there.
Just saying.
Hey,
I've created a small magisk module, with that you can use the Argument Reality function inside the Google Camera.
It works on AOSP 8.0 Beta and Stable, maybe it also works on nougat.
When you want to test it on other devices than the Mi A1, please don't forget to make a backup even if bootloop and such things are very unlikely.
Wehen you have a device where it also works you are allowed to create a thread, only condition link me and very important Arnova8G2 because without his work it would not be possible.
Installation instructions:
The modules can easily flashed inside the Magisk Manager or with TWRP.
To get it fully working you have to flash both modules
Downloads:
All in one version:
https://forum.xda-developers.com/mi...re-modded-google-camera-t3720269/post75090632
ARcore Basic files:
https://drive.google.com/folderview?id=1C3pylJpeK9bc93L56v1JWrjJNXnNbU06
ARcore Basic files V2:
https://drive.google.com/file/d/16YyJN1PTDMZ5WPQ_F2VFZuyTJlAOmAyi/view?usp=sharing
Apps Module:
https://drive.google.com/file/d/12t5jRzlEM0tz1mkyKqjwu0RS8yZ37IeY/view?usp=sharing
Apps Module V2:
https://drive.google.com/file/d/19rtu2nUAcH2WKCBbGbm2F75uXsfwKXt4/view?usp=sharing
Do not thank me, just thank him @Arnova8G2
Thanks for your contribution! Will try as soon as I get the oreo beta working on my phone.
Unable to flash via magisk
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
fosco_ said:
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
Click to expand...
Click to collapse
My storage is also encrypted and it works.
AnnePunk said:
My storage is also encrypted and it works.
Click to expand...
Click to collapse
What version of Magisk and Magisk Manager?
fosco_ said:
What version of Magisk and Magisk Manager?
Click to expand...
Click to collapse
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
AnnePunk said:
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
Click to expand...
Click to collapse
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
Had the same bug, reinstall magisk with the Magisk Manager, reboot and try again.
I can flash other zip.. But these two can't be flashed on magisk
Rakibboss said:
I can flash other zip.. But these two can't be flashed on magisk
Click to expand...
Click to collapse
Hmm for me it works
Whatever, i managed to do it via this method
https://forum.xda-developers.com/redmi-note-3/themes/mod-updated-6-11-17-google-camera-hdr-t3701190
Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
"I can flash other zip.. But these two can't be flashed on magisk"
You must create an folder "magiskmanager" on internal sd card...then it works
I will try for Android Nougat. Thank you
It doesn't work on nougat .i tried
Hello, install without problems, but I would like to know which Gcam application exactly should I I must use, Thanks.
anyone got it working ?
jeneb11 said:
anyone got it working ?
Click to expand...
Click to collapse
Not working on Redmi Note 4 stock global miui9 with camera2 api enabled. Tried with both magisk, and TWRP, AR Stickers stoped.
how can you install magisk on oreo? when i booted to the twrp, it asks for my pattern and when i draw the pattern, it says pattern failed. so please tell me how can you install magisk on oreo
jigs4wkiller said:
Hmm for me it works
Click to expand...
Click to collapse
Which magisk version??
I tired all arm64 custom roms for moto z play, some arm, tried mixing with all kernels and magisk/without magisk.
And i can't pass safetynet on all these configurations
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
But I have passed with magisk
Artim_96 said:
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
Click to expand...
Click to collapse
But on my old phone, i was using custom roms (not certificed), and SN was passing.
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
With ROM you using?
dawidrejowski said:
With ROM you using?
Click to expand...
Click to collapse
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
dawidrejowski said:
But on my old phone, i was using custom roms (not certificed), and SN was passing.
Click to expand...
Click to collapse
How old of a phone? My last phone (HTC One M8) passed on custom ROMs because it didn't seem to report the bootloader was unlocked. But I have safety net passing on custom ROMs on my Z play thanks to magisk and universal safteynet fix beta 5.
mijing said:
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
Click to expand...
Click to collapse
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
KrisM22 said:
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
Click to expand...
Click to collapse
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
mijing said:
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
Click to expand...
Click to collapse
That is a very old one - could you please attach it to your post for a few minutes? TIA!
KrisM22 said:
That is a very old one - could you please attach it to your post for a few minutes? TIA!
Click to expand...
Click to collapse
Yes it is too old but till now it is usefull as you can see
mijing said:
Yes it is too old but till now it is usefull as you can see
Click to expand...
Click to collapse
I found it up on
https://androidfilehost.com/?fid=673368273298984533
is that it?
I'll go try it on AOSP 8.1 Alberto97
Yes,It Is. but I dont Know about AOSP Is it will work or not
mijing said:
Yes,It Is. but I dont Know about AOSP Is it will work or not
Click to expand...
Click to collapse
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
KrisM22 said:
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
Click to expand...
Click to collapse
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English? )
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
Edit: Never mind I saw what Rom you were running.
mijing said:
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English )
Click to expand...
Click to collapse
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Im glad you have fix your problem
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Check for Bluetooth and wifi if they are working correctly. I flashed the fix on AOSP and my Bluetooth crashed, needed to restore backup.
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.