Develop Bugs

[x Force] Installing Magisk Root & Universal Systemless Interface

Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased

JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.

sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.

For this procedure is necesary unlock the bootloader?

Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.

Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.

Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.

Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!

And how are we gonna unlock the bootloader?
Is there a way to do that?

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.

Refurb replacement problems and questions

My original Pixel XL died completely with a hard brick, no power, no lights, nothing. The refurbished replacement arrived yesterday. It booted up in 7.1.2 and had an update notice to Oreo 8. I did that and was on OPR6 with another update notice to the September security patch. Even with my T-Mobile SIM installed, it installed OPR1 for Project Fi and Canada instead of OPR3. Is that normal?
None of my Play Store apps downloaded and installed. Is that normal or is it because I couldn't sync with my dead phone? Unfortunately all of my recent backups had been to the local SD card, so that is a lesson learned for next time.
I unlocked the bootloader and fastboot flashed OPR3 with no problems, but now my Play Store says it's uncertified. I tried clearing the Play Store data and rebooting, plus several other tips I found online, but nothing fixed it. Is that because of the unlocked bootloader and not being rooted? Rather than doing a factory reset and starting over, if I root with SuperSU and run suhide, will the Play Store be certified again?

Anyone?

It changed back to certified for me. I'm rooted with SuperSU and suhide. I cleared Playstore data, I blocked Playstore, Pay, etc. app's in suhide, then I hid SuperSU and suhide icons, Safetynet passed, and rebooted.

galaxys said:
It changed back to certified for me. I'm rooted with SuperSU and suhide. I cleared Playstore data, I blocked Playstore, Pay, etc. app's in suhide, then I hid SuperSU and suhide icons, Safetynet passed, and rebooted.
Click to expand...
Click to collapse
Thanks! I rooted with SuperSU, installed suhide, blocked Play Store, cleared Play Store data and then rebooting fixed it. I have seen that others have had to hide the SuperSU and suhide icons but I didn't have to on either my old phone or this replacement.

JimSmith94 said:
Thanks! I rooted with SuperSU, installed suhide, blocked Play Store, cleared Play Store data and then rebooting fixed it. I have seen that others have had to hide the SuperSU and suhide icons but I didn't have to on either my old phone or this replacement.
Click to expand...
Click to collapse
Did you require TWRP to root or is there a way to directly flash SuperSU and suhide from fastboot?

Zwitterion said:
Did you require TWRP to root or is there a way to directly flash SuperSU and suhide from fastboot?
Click to expand...
Click to collapse
I don't know if there's a way to root without TWRP. I used the bootable one for Oreo with:
fastboot boot twrp-3-1-pixel-bootable-mod.img

JimSmith94 said:
I don't know if there's a way to root without TWRP. I used the bootable one for Oreo with:
fastboot boot twrp-3-1-pixel-bootable-mod.img
Click to expand...
Click to collapse
Could you kindly provide a link to the Oreo compatible TWRP? Also what SuperSu zip did you use?
Thanks so much!!

Zwitterion said:
Could you kindly provide a link to the Oreo compatible TWRP? Also what SuperSu zip did you use?
Thanks so much!!
Click to expand...
Click to collapse
You really should be searching and reading for yourself before you try any of this, but here is the TWRP thread with download link: https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
I always use the newest SuperSU and suhide, which at the moment are SR4-SuperSU-v2.82-SR4-20170918204844.zip and UPDATE-suhide-v1.08-20170815171034.zip. I'll let you Google those yourself.

JimSmith94 said:
You really should be searching and reading for yourself before you try any of this, but here is the TWRP thread with download link: https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
I always use the newest SuperSU and suhide, which at the moment are SR4-SuperSU-v2.82-SR4-20170918204844.zip and UPDATE-suhide-v1.08-20170815171034.zip. I'll let you Google those yourself.
Click to expand...
Click to collapse
Thanks!

JimSmith94 said:
You really should be searching and reading for yourself before you try any of this, but here is the TWRP thread with download link: https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
I always use the newest SuperSU and suhide, which at the moment are SR4-SuperSU-v2.82-SR4-20170918204844.zip and UPDATE-suhide-v1.08-20170815171034.zip. I'll let you Google those yourself.
Click to expand...
Click to collapse
Did you let the phone boot once between application of SuperSu and Suhide?

Zwitterion said:
Did you let the phone boot once between application of SuperSu and Suhide?
Click to expand...
Click to collapse
Haven't you read the threads about all of this? The instructions say to boot in between so that's what I did.

JimSmith94 said:
Haven't you read the threads about all of this? The instructions say to boot in between so that's what I did.
Click to expand...
Click to collapse
I have, including the line where Chainfire notes that it may be beneficial to not boot between flashing of these packages depending on how TWRP behaves, which is why I asked you.

Switch to Magisk from supersu

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.