Database Users

Magisk v11.6 compatible with Droid Turbo Stock ROM

I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Pics or it didn't happen

And last, but certainly not least...

So I can root without unlocking the bootloader using sunshine?

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.

Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.

Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.

Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.

TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.

Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.

More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU

y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.

TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?

y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.

It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^

Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).

.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.

I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.

Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?

Get Snapchat to work With Root?

Hi guys! I cant log in or make a new acct on Snapchat with my g4 plus rooted on stock N, is there a workaround?
Thanks

You can't make new account with root enabled! Try hide root or Magisk and try creating again
Sent from my Moto G4 Plus using Tapatalk

lexie90 said:
Hi guys! I cant log in or make a new acct on Snapchat with my g4 plus rooted on stock N, is there a workaround?
Thanks
Click to expand...
Click to collapse
Here's a fairly easy way to solve this:
- Unroot your phone
- Install Snapchat and login
- Root
- Install Titanium backup
- Backup Snapchat
- Go to your Internal Storage>Titanium Backup, and copy the gzip files from there to an SDCard or back it up to the cloud.
Now, if you ever flash another custom ROM all you have to do is install Titanium Backup and restore A bit complicated, but it's a 1-time issue and works pretty well.
Oh, and btw, Magisk works fine, so try that instead of SuperSU.

So I can root with magisk instead of super SU? I Tried phh and got stuck on bootlooping!
I Tried unrooting with super SU and didnt work Will try to flash the stock back to do that

1. Flash Magisk from recovery.
2. Install Magisk Manager from the play store.
3. In settings (Magisk Manager), enable Magisk Hide.
4. Go your merry way.
This is what I did. I'm using the likes of Snapchat, Pokémon Go and Mario Run.
And yes, you can log into Snapchat.

​
baunthiyal said:
1. Flash Magisk from recovery.
2. Install Magisk Manager from the play store.
3. In settings (Magisk Manager), enable Magisk Hide.
4. Go your merry way.
This is what I did. I'm using the likes of Snapchat, Pokémon Go and Mario Run.
And yes, you can log into Snapchat.
Click to expand...
Click to collapse
Didnt work for me, got an error because IM not rooted with magisk SU

negusp said:
Here's a fairly easy way to solve this:
- Unroot your phone
- Install Snapchat and login
- Root
- Install Titanium backup
- Backup Snapchat
- Go to your Internal Storage>Titanium Backup, and copy the gzip files from there to an SDCard or back it up to the cloud.
Now, if you ever flash another custom ROM all you have to do is install Titanium Backup and restore A bit complicated, but it's a 1-time issue and works pretty well.
Oh, and btw, Magisk works fine, so try that instead of SuperSU.
Click to expand...
Click to collapse
thank you! it worked amazingly.
do you have the magisk link throgh? so i can avoid future trouble lol

lexie90 said:
thank you! it worked amazingly.
do you have the magisk link throgh? so i can avoid future trouble lol
Click to expand...
Click to collapse
The latest Magisk zip is here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You need to flash it in TWRP. I recommend completely unrooting from SuperSU or phh.
Also, stock kernel is incompatible with Magisk. Flash ElementalX or Vegito if you wish to use Magisk.
So, in this order:
-Unroot
-Flash Kernel (EX or Vegito)
-Flash Magisk (will automatically install MagiskSU)
-Wipe ART/dalvik cache
-Boot
-Install Magisk Manager, presto, ur done

A lot of apps (and system settings) won't work unless I hide root

I've been experiencing a weird issue since I installed DU on my 6p; a lot of apps crash when I try to open them until I use Magisk Hide on them. Not just user apps, I couldn't even connect to my JBL speakers via bluethoot until I hided root to my bluethoot-share system application. I can't get chrome (or anyhting related to it, like the in-app browser of Facebook) to work, and i've tried a lot of versions of Chrome and even Opera; the only thing I could get working it's Firefox. I can't even change my wallpaper (my launcher crashes).
On the other hand, apps that support root, like amaze file manager, work smoothly even without being granted root permission.
I'm a noob, so i have no idea what's causing the problem, but i'll try my best to give you my setup in case you can help me.
- I'm using official Dirty Unicorns ROM v11.3 (7.1.2) with the correspondent stock kernel (unicornblood)
- I'm rooted by chainfire's SuperSU v2.79
I don't know if the mods i've installed have anything to do, but i'll share them just in case
I installed these audio mods:
- Hi-Performance DAC Enabler:
- aptX™ HD Enabler
- AINUR Pandora
This other thermal mod: CTTmod
And I'm using Magisk v12.0
Thank you very much in advance

I don't think you can use Magisk and SuperSu at the same time because Magisk includes its own root app, PhilsSu. You are basically using two different root apps at the same time. You can try uninstalling SuperSu or Magisk but you might be better off doing a clean flash of DU, Gapps then either SuperSu or Magisk but not both.

jhs39 said:
I don't think you can use Magisk and SuperSu at the same time because Magisk includes its own root app, PhilsSu. You are basically using two different root apps at the same time. You can try uninstalling SuperSu or Magisk but you might be better off doing a clean flash of DU, Gapps then either SuperSu or Magisk but not both.
Click to expand...
Click to collapse
When I tried to install magisk without SuperSU it asked me to root my device first and aborted installation

I've never used Magisk but I thought PhilsSu was part of it. I suppose you can download PhilsSu separately and flash it before Magisk but I know that's the rooting app that works with Magisk, not SuperSu.
---------- Post added at 08:09 PM ---------- Previous post was at 08:02 PM ----------
Now that I think about it I'm pretty sure I read that you can uninstall SuperSu using the Play Store app then choose to root with PhilsSu within Magisk if you have both installed at the same time.

Magisk v12 is its own root solution. It doesn't use SuperSU & it doesn't use PHH superuser either. It's its own thing now. Magisk Hide does not hide SuperSU, only its own root. So if you're using Magisk Manager to hide apps while SuperSU is installed, it's literally doing nothing. Your root is not hidden and you should be able to confirm this using a root checker app. I guess it's possible that having both is causing your issues, but I follow the Magisk general support thread and never see issues that severe. I'd guess it's a stability issue on your ROM.
If you want to use Magisk Hide correctly, you need to get rid of SuperSU. Select the full unroot option from the settings. Hop on over to osm0sis thread here and grab and flash the unsu.zip he has over there. Then flash your ROMs boot.img again (unless it's rooted). That'll completely wipe SuperSU and let you use Magisk.
So basically (stock phone > unlock bootloader > install TWRP > flash Magisk v12) and now you're rooted. No SuperSU / anything else is involved. V12 literally roots you and you need to clean up SuperSU to use it properly.

RoyJ said:
Magisk v12 is its own root solution. It doesn't use SuperSU & it doesn't use PHH superuser either. It's its own thing now. Magisk Hide does not hide SuperSU, only its own root. So if you're using Magisk Manager to hide apps while SuperSU is installed, it's literally doing nothing. Your root is not hidden and you should be able to confirm this using a root checker app. I guess it's possible that having both is causing your issues, but I follow the Magisk general support thread and never see issues that severe. I'd guess it's a stability issue on your ROM.
If you want to use Magisk Hide correctly, you need to get rid of SuperSU. Select the full unroot option from the settings. Hop on over to osm0sis thread here and grab and flash the unsu.zip he has over there. Then flash your ROMs boot.img again (unless it's rooted). That'll completely wipe SuperSU and let you use Magisk.
So basically (stock phone > unlock bootloader > install TWRP > flash Magisk v12) and now you're rooted. No SuperSU / anything else is involved. V12 literally roots you and you need to clean up SuperSU to use it properly.
Click to expand...
Click to collapse
Thank you very much, that clarifies a lot for me and it did the trick, i clean flashed DU and rooted with Magisk v12, everything's perfect now:good:

Switch to Magisk from Super SU

Hey guys,
I apologize in advance if this is somewhere on the forum (I coukdn't find anything on it.)
So last evening I decided to do the fllowing: unlock, install twrp, root and install a custom rom. I'm comeing from a Note 3 so just getting familar with everything for Nexus.
I completed the unlock, twrp install and root (supersu) with the nexus root toolkit and made a backup as well (not through twrp), and flashed the latest pure nexus rom (stock kernal).
I would like to switch over to magisk so I can get the benefits of using it. How would I go about doing so ?
Thanks !

rich6619 said:
Hey guys,
I apologize in advance if this is somewhere on the forum (I coukdn't find anything on it.)
So last evening I decided to do the fllowing: unlock, install twrp, root and install a custom rom. I'm comeing from a Note 3 so just getting familar with everything for Nexus.
I completed the unlock, twrp install and root (supersu) with the nexus root toolkit and made a backup as well (not through twrp), and flashed the latest pure nexus rom (stock kernal).
I would like to switch over to magisk so I can get the benefits of using it. How would I go about doing so ?
Thanks !
Click to expand...
Click to collapse
If you want magisk then dirty flash your rom to get rid of magisk. After that flash the magisk zip from recovery then reboot and go to play store to update app. Why do you want magisk btw? I used it but drooped it for supersu as it made the splash screen (boot logo that said Google) stay for a while making boot time take a long time.

Ok so if I did the following would I be in the clear:
Full Wipe
Flash rom
Gapps
Elementalx kernal (want to try this kernal)
Magisk 12.0
Reboot
Install magisk manager
I'd like to have magisk to hide root, for things like netflix.
Also would it make any sense to run unsu while flashing everything else ?

rich6619 said:
Ok so if I did the following would I be in the clear:
Full Wipe
Flash rom
Gapps
Elementalx kernal (want to try this kernal)
Magisk 12.0
Reboot
Install magisk manager
I'd like to have magisk to hide root, for things like netflix.
Also would it make any sense to run unsu while flashing everything else ?
Click to expand...
Click to collapse
No need to flash unsu. If Netflix is the only reason you are using magisk then you could just use apkmirror. Also, I heard that the app detects unlocked bootloaders. You should be good to wipe the rom and flash all the stuff you said.

I'll look into apkmirror. Forgot to mentioned I'd like to used android pay as well. Can apkmirror help with that ?

rich6619 said:
I'll look into apkmirror. Forgot to mentioned I'd like to used android pay as well. Can apkmirror help with that ?
Click to expand...
Click to collapse
If you want android pay then you need magisk and need to hide magisk from it aswell as using the hide root settings. You also need to pass the SafetyNet check if you want to use android pay.

Ok thanks. So I will do everything I mentioned in the list as well as set magisk to hide in magisk manager settings ?

rich6619 said:
Ok thanks. So I will do everything I mentioned in the list as well as set magisk to hide in magisk manager settings ?
Click to expand...
Click to collapse
Yes, make sure to run a SafetyNet check.

Will do. Thanks for all the help !

rich6619 said:
Will do. Thanks for all the help !
Click to expand...
Click to collapse
You're welcome, hopefully all goes well?.
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
rich6619 said:
Will do. Thanks for all the help !
Click to expand...
Click to collapse
Also, make sure to check out my thread for better idle drain by blocking wakelocks if you haven't already seen it. I've built a version for pure nexus.
https://forum.xda-developers.com/nexus-6p/general/taking-wakeblock-requests-t3583397

I will for sure check it out. Thanks again !

DEVILOPS 007 said:
You're welcome, hopefully all goes well.
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
Also, make sure to check out my thread for better idle drain by blocking wakelocks if you haven't already seen it. I've built a version for pure nexus.
https://forum.xda-developers.com/nexus-6p/general/taking-wakeblock-requests-t3583397
Click to expand...
Click to collapse
So just an update. Did the following :
flashed
Rom
Gapps
Magisk
ElementalX Kernal
Reboot
Installed Magisk Manager, enabled magisk hide and systemless host (for adaway) and rebooted. Safetynet passes in magisk manager. Went to play store, checked settings device certification and it's certified. Searched netflix, still not available. I'm guessing this has to do with the bootloader being unlocked ? Is there a way around this or will I have to just download the latest apk from apk mirror ?
Going to test the phone out for a few days to see what battery life is like with elementalx (I was averaging around 4.5 hrs ost with stock). If I don't get any better I will def test out your wakeblock.

I would like to hijack this thread a little bit as it is on the same topic as well with slight differences, sorry!
I got a stock 6P with unlocked bootloader and rooted with systemless SuperSU. Fiddled around with Magisk manager before, it will fail SafetyNet check.
How do I switch to phh superuser and using magisk? Will this pass SafetyNet check? The bootloader will still be unlocked....
My main intent is to be able to use Android Pay.

This thread is right up my alley. I just got a Nexus 6 ( XT1103 ) unlocked bootloader, rooted using a Windows toolkit (don't remember the name) and have twrp installed. I read about Magisk after trying to use Android pay without any luck. I would like to use Android pay and believe Magisk would let me be able to do so with still having use of root apps.
Is it possible to go from root to Magisk without loosing my data?

how to keep magisk from uninstalling during a reboot!!!!!!???!!!!!!
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM if also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know

[Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU)

Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system (Edit 8/28/17: DO NOT install TWRP, just boot to system)
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
UPDATE 10/2 The links for SuperSu and SuHide have been updated to the latest releases.

GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.

raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs

GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
GroovinChip said:
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?

raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
I've seen some folks report that they couldn't get Magisk to work. I can't confirm that right at this moment though. You can test and see if it'll work by just using the TWRP provided. Not sure if it's based off RC2 or RC1.

raazman said:
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?
Click to expand...
Click to collapse
It depends, are you able to boot to system? If not, like you're stuck in a bootloop, I'd suggest flashing completely back to stock. It would mean you'd lose your apps and data, but if you can't boot to system anyway then it doesn't really matter.
If you CAN boot to system, then I'd suggest just starting over and use SuperSu with SuHide. I doubt that any changes actually took place on your device since you didn't flash a custom kernel. But this is only if you can boot to system successfully.
Sent from my Google Pixel XL using XDA Labs

Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.

GroovinChip said:
3) Download SuperSu Config
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
Click to expand...
Click to collapse
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.

Mike02z said:
Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.
Click to expand...
Click to collapse
Great!
I haven't tested my debit card after adding yet either. Been home the whole time
Sent from my Google Pixel XL using XDA Labs

@GroovinChip Is your bootloader unlocked?

Kisakuku said:
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.
Click to expand...
Click to collapse
Ok, I'll edit the OP. I wasn't 100% sure, that's why I did it anyway.
Sent from my Google Pixel XL using XDA Labs

GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Rooted perfect however I cannot uninstall system apps, how come?

have you tried going into adb shell and type the su command?

I'm using the system app remover from playstore. It says failed to uninstall.

Root works. AndroidPay works with SUHide!
Thanks!

Ok after reflashing, everything works as intended. Thanks for the guide!

I can confirm this works with the Pixel XL.

Stupid question but I'm guessing bootloader must be unlocked first correct?

Denton.S said:
Stupid question but I'm guessing bootloader must be unlocked first correct?
Click to expand...
Click to collapse
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs

GroovinChip said:
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I was afraid you were going to say that. For one brief, glorious moment I thought I could get rid of adds without having to deal with this damn locked bootloader. My own mistake for getting the phone from EE direct. Thanks dude, much appreciated though