Magisk v11.6 compatible with Droid Turbo Stock ROM

[TheSt33v]

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

 

[TheSt33v]

Pics or it didn't happen

 

[TheSt33v]

And last, but certainly not least...

 

[Sparksys]

So I can root without unlocking the bootloader using sunshine?

 

[zys52712]

So I can root without unlocking the bootloader using sunshine?

No.

 

[ChazzMatt]

So I can root without unlocking the bootloader using sunshine?

No. Sunshine unlocks your bootloader, so you can then root.

 

[pgzerwer]

So I can root without unlocking the bootloader using sunshine?

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.

 

[Tokogon]

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

 

[TheSt33v]

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

MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.

 

[Tokogon]

MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.

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.

 

[TheSt33v]

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.

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.

 

[y8s]

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

 

[TheSt33v]

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

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.

 

[y8s]

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.

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?

 

[TheSt33v]

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?

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.

 

[Einheit-101]

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^^

 

[TheSt33v]

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

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).

 

[Einheit-101]

.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.

 

[y8s]

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.

 

[TheSt33v]

.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.

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?