Database Users

Magisk on s7 & s7 edge

Hi Everyone, l have a question about this Magisk Mod and its directed to s7 & s7 edge users. If anyone is using this Mod, may you please tell us how you got it to work, coz l have tried and failed many times. Your help would be kindly appreciated..
King Addies

Root and install xposed.

I have used a stock rom, as it says on the magisk thread and followed all the instuctions and still failed.. lm not really botherd about using the mod anymore, but l made this thread so all the other people who are in my situation can get help or a tutorial on how to install it on s7 & s7 edge. Coz l could not really get much help from the official thread.
King Addies

I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.

Mr. Orange 645 said:
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Click to expand...
Click to collapse
Thanx for your input on this issue mate, hope the info you have provided helps all those that want to use this Mod on their s7 or s7 edge phones..
King Addies

One more step, sorry. You have to also install Phh's SU app from the Google Play store.

Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies

Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.

I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Galactus said:
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
Click to expand...
Click to collapse

kevinwu128 said:
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Click to expand...
Click to collapse
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.

Galactus said:
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Click to expand...
Click to collapse
Maybe I did have it working then, the only thing I tested it with Pokemon go and it didn't work.. so I just assumed it wasn't working, so I reverted all changes. I spent way too much time than I had hoped
Cheers Buddy

Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.

Devilover said:
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Click to expand...
Click to collapse
Magisk is pointless right now. Simply having an unlocked bootloader causes SafetyNet to fail. The latest version of magisk also removed the checkbox to turn root on and off. To use Snapchat YOU MUST login before any modifications. Make a titanium backup of Snapchat logged in, then you can restore it whenever you want.

silverrum said:
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Click to expand...
Click to collapse
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/

PoTBrain• said:
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
Click to expand...
Click to collapse
What part of S7/S7Edge do you fail to understand?

Or, boot into TWRP, format data to unencrypt then flash latest magisk and reboot. Once booted, open magisk manager hit menu button and open settings, check magisk hide. Exit settings, open menu and open magisk hide, there you can check any app you want to hide from root. done.

American locked bootloader hide root issues

hope i am not violating any forum rules here, as i know how strict they can be. I am not a noob in this area, ive rooted and flashed all my phones since my droid x on. I miss my s-off HTC so bad. I did 5 minutes of research and thought all Galaxy S7s were bootloader/recovery unlockable...only to find out the american versions arent after im stuck with s Sprint SM-G930P. I was able to root and install xposed with the engineer boot.img and odin. Since TWRP or recovery isnt an option I have tried for months to systemless root this thing to hide root and pass safetynet. Ive tried flashfire to flash SU systemless 2.78SR5 and root switch and am on android 6.0.1 PE1 firmware following guides here: https://forum.xda-developers.com/sprint-galaxy-s7/how-to/sm-g930p-root-t3410604 but after factory reseting and trying Rootswitch (will hide exposed but not root with flashfire installing it since bootloader lock doesnt allow TWRP) I piddled with magisk but I am not on the Equinox unlockable s7 and am just at a loss here. Any one out there know of a way to hide root with this version of S7? Im out of ideas and any help here is appreciated. When i flashfire Supersu i get the locked out modified boot img error, but selecting AP and flashing the engineer boot img will get me back up rooted but root switch is a no go. I can use buildprop/rootzwitch to set selinux permissive sstatus but still fail. I refuse to let samsung not let me root my phone properly. I ser xposed modules like snorlax being updated so there seems to be a way to use xposed modules in PoGo while hiding root/xpised but every guide i see leads to TWRP instructions. Can i adb/terminal install magisk/rootswitch? and stiil use modules? (Cart before the horse question seeing as right now i cant bypass safetynet.) HELP!!

Have you made any more progress with this by chance?

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?

Any OREO rom that doesn't trigger SafetyNet?

What the title says basically...
I don't like having my phone rooted and would rather not bother with Magisk.

You could install magisk and deactivate root. Then you're not able to give out or decline root access to apps.

JD. A said:
You could install magisk and deactivate root. Then you're not able to give out or decline root access to apps.
Click to expand...
Click to collapse
But why does all the Oreo rom fail SafetyNet?
I don't want yo use Magisk because I don't want to have to update every time SafetyNet is updated and Magisk fails.
I thought LinageOS would be out for this phone by now. They seem to be the only ones that are keen on keeping in SafetyNet friendly.
Back to Nougat for now I suppose.

mottokeki said:
But why does all the Oreo rom fail SafetyNet?
I don't want yo use Magisk because I don't want to have to update every time SafetyNet is updated and Magisk fails.
I thought LinageOS would be out for this phone by now. They seem to be the only ones that are keen on keeping in SafetyNet friendly.
Back to Nougat for now I suppose.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but safetynet checks if your bootloader is unlocked. If it's unlocked you fail the safetynet check. There's a workaround in custom kernels that disables that check or returns it false, makes saftynet thinks that bootloader is locked.
LOS is out 7.1.2. We just have to wait for Oreo. If you wanna try a oreo rom either install magisk or a custom kernel and that should fix safetynet for you.

safetynet question - cts profile false

I was running stock 7.1.1 and everything was fine. Then i decided to try LOS 15.1, with magisk 17.4 but encountered an issue with safetynet cts profile false that prevented me from using android pay. I then proceeded to flash B35 EDL, and then do the sd upgrage to Oreo B20, but i still have the same issue with failing cts profile.
AI'm no longer rooted, running stock but still fail safetynet. Any one have any ideas what I can try next? at this point i just want cts profile to pass on the current oreo b20 stock.
Thanks!

It could be that SafetyNet detects that you have an unlocked bootloader, but there are ways to hide that (custom kernel, Magisk, etc). Do you have Xposed installed? That's an automatic SN fail. You haven't changed system partition in any way at all? It's also possible that Google hasn't yet approved B20 despite it being official rather than beta. There could be other factors too. SN looks at lots of things, many of which Google won't talk about.

You need to install magisk hide props and then in a terminal
"Su"
Grant superuser
Then
"Props"
And follow the on-screen instructions. Stupid that Google pay has a problem with rooted phones as it's painfully simple to get around it
You can find magisk hide props in the "download" section of magisk manager

Check the settings in the Google play store, Device not certified can be an issue when you change Roms.
The link between the device and Google has been broken, hence the device not certified.
There is an app Device ID that can add the certification back to its original state.
Hope this helps

Turned out to be it was because of the unlocked bootloader.
funny story... i locked the bootloader without having oem unlock enabled . Got bricked, couldn't boot into EDL... so i had to take it apart and ground the test point to put it into EDL.

xavoc said:
Turned out to be it was because of the unlocked bootloader.
funny story... i locked the bootloader without having oem unlock enabled . Got bricked, couldn't boot into EDL... so i had to take it apart and ground the test point to put it into EDL.
Click to expand...
Click to collapse
There's a tool for that now; you may not have had to open it: https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

TPMJB said:
You need to install magisk hide props and then in a terminal
"Su"
Grant superuser
Then
"Props"
And follow the on-screen instructions. Stupid that Google pay has a problem with rooted phones as it's painfully simple to get around it
You can find magisk hide props in the "download" section of magisk manager
Click to expand...
Click to collapse
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.

xavoc said:
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
Click to expand...
Click to collapse
try this thread https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809/page2
Update to Magisk v17 and then try the above solution

xavoc said:
Im trying out Magisk 16.7 (I saw some posts that said 17 causes bootloops) and MM 6.0.1. I don't see hide props in downloads? What can I do to pass safetynet? Thanks
I'm now running twrp with Oreo B20 stock.
Click to expand...
Click to collapse
"Magisk hide props config" is literally what it is called. If you can't find it, you're doing it wrong.
If all else fails, google then install manually.

Had to upgrade to magisk 17 to see the hide prop module download. Still couldn't pass safetynet with Oreo B20. Switched to LOS 15.1 and now everything works.