Database Develop

Magisk vs SuperSU

I haven't seen a thead posted about this so I figured I'd get some input from people that have used both or either of the 2 root options.
What do you prefer and why? What are the pros and cons?
I know SuperSU is very well known and I'm familiar with it from the Galaxy S phones. Magisk is fairly new, but from what I heard it works well with Nougat and the other nice thing is that magisk can be toggled.
I'm not sure if there is any benefit to that or not, but I'd like to hear some feedback.

I'm interested to know more about this as well, but this is what I read about it.
Yes, Magisk can be toggled, so you can use Android Pay when you need it and then get back to being rooted.
However, for some reason, my AdAway adblocker just wouldn't work with Magisk+phhSU. No idea why. Everything else root worked well. When I had to clean flash the official Nougat, I decided to stick to good'ol SuperSU. I don't need the toggle function and everything worked great since.

So I've used both and can say this. Magisk works on both SuperSU and phhSU, although the later offers a different functionality. The toggle feature is an older feature of Magisk as they now have a hide feature baked in. This is the same as SUHide for SuperSU. I have yet to get SUHide working on the 3t, but I have it working on a few other phones. SuperSU+SUHide is great if you only want to run Root on your phone and hide systemless root from applications without having to really toggle Root. From my experience (YMMV), toggling root breaks things more than hiding. The only reason I have found to run Magisk is if you want to run Xposed as well. Xposed works with SuperSU, but Magisk does a pretty good job of UI integration with some of the pieces.

DarqAnshin said:
So I've used both and can say this. Magisk works on both SuperSU and phhSU, although the later offers a different functionality. The toggle feature is an older feature of Magisk as they now have a hide feature baked in. This is the same as SUHide for SuperSU. I have yet to get SUHide working on the 3t, but I have it working on a few other phones. SuperSU+SUHide is great if you only want to run Root on your phone and hide systemless root from applications without having to really toggle Root. From my experience (YMMV), toggling root breaks things more than hiding. The only reason I have found to run Magisk is if you want to run Xposed as well. Xposed works with SuperSU, but Magisk does a pretty good job of UI integration with some of the pieces.
Click to expand...
Click to collapse
Awesome, thanks for the input! That's definitely helpful. So you would recommend going with magisk? Would you say magisk works equally as well on all versions of OOS? 3.5.* and the new 4.*+ (nougat) version?

m0d hipp¥ said:
Awesome, thanks for the input! That's definitely helpful. So you would recommend going with magisk? Would you say magisk works equally as well on all versions of OOS? 3.5.* and the new 4.*+ (nougat) version?
Click to expand...
Click to collapse
Keep in mind, your mileage may very and these are only my opinions. With that said I will say this:
I've only had my OnePlus 3t for about 3 weeks, so I only really used it on the latest version of OOS 3.5. It seems to work fine on 4.*, however, it did take me a few extra steps and sideload.
I honestly would go with SuperSU / SUhide if I could get it to work on 3T correctly like it does on my other devices. Right now I have this weird forever and a day boot time with SUHide.
Magisk works almost as well in my experience and on the devices I do run xposed on runs even better in my opinion. The new Magisk doesn't turn root off but does mask root from certain apps such as android pay. The interface, in my opinion, has gotten better over the iterations. Magisk also does allow you to flash from the direct input, which depending on your skill can help out greatly.
I would say this. If you require
Xposed
UI
live updates of actual software similar to TWRP's new loader
ability to flash from app
Use Magisk
If you like simplicity and raw power go with SuperSU. I did try the SUHide Gui but found Magisk's version much easier and reliable.

Thanks again! That's super helpful!

Guys, Im running Tugapower and I cannot root the rom. Any of you know how to fix it? I run the zip file to root and I start to phone and looks that works but after couple of minuts is not rooted anymore. Anyone else?

Has anybody used the the latest version of superuser with oos 4.0?
That's the SR2 2.79 version. The one before turned off sims and a reflash of 4.0 sorted out.
And the info on Magisk has been informative. Thanks!

As someone who has used phhSu and SuperSU (I've also paid for SuperSU Pro) I find either do the job and that SuperSU is good for getting a ROM going while I prefer to then re-root with phhSU after I have my ROM set up for daily use, although the only annoying thing with phhSU is that TB detects the su binary as being a non-SuperSU one so it pops up an extra warning.
Either is fine, just pick the one you like better I guess.

How did you guys flash a systemless root without triggering DM-Verity?
From my understanding, we flash superSU after flashing TWRP and allowing modifications, because superSU disables/bypasses DM-Verity
Am I missing something here?

Freyelis said:
How did you guys flash a systemless root without triggering DM-Verity?
From my understanding, we flash superSU after flashing TWRP and allowing modifications, because superSU disables/bypasses DM-Verity
Am I missing something here?
Click to expand...
Click to collapse
With SuperSU 2.79 you don't need no-verity patch.

m0d hipp¥ said:
I haven't seen a thead posted about this so I figured I'd get some input from people that have used both or either of the 2 root options.
What do you prefer and why? What are the pros and cons?
I know SuperSU is very well known and I'm familiar with it from the Galaxy S phones. Magisk is fairly new, but from what I heard it works well with Nougat and the other nice thing is that magisk can be toggled.
I'm not sure if there is any benefit to that or not, but I'd like to hear some feedback.
Click to expand...
Click to collapse
Actually Magisk doesn't give root but the modded version of Phh's Superuser does.
One of the main difference is that Phh's Superuser (and Magisk) are open source. Once Chainfire will leave his SuperSU project you will have to fully trust CCMT.

LineageOS Help

Hi XDA!
I need some help with lineageos on here. I'm a pretty seasoned flashaholic and generally know what I'm doing however this is stumping me.
Anytime I install lineageos + magisk, I have no root. All flashing goes to plan, however when I open magisk manager I get one of 2 things:
Either, I'm rooted with magisk installed, or I'm not rooted with magisk installed.
It seems to depend on which root app gains root first - for example, if magisk says I'm rooted (e.g it'd the first app to gain root) then any other app I open afterwards will tell me I'm not rooted, including root checkers. If I open a root checker first, it will say I'm rooted but then magisk will say after that I'm not, but magisk is installed, and all root apps from then on will fail. I'm really not sure what the problem is, and I have done clean installs, dirty flashes etc. All I have enabled is magisk hide and its busybox toggle. I've tried turning off it's busybox but no luck.
It gets worse if I enable developer options, Even if I don't touch any root settings in there (I like to disable Bluetooth absolute volume). If I do this, I loose root completely, but it still says magisk is installed. I'm not using SuperSU as I want to pass safetynet, and there are no su files from lineageos in /system/bin or xbin.
Obviously doesn't happen with OOS and all works fine.
Firmware is correct for LOS etc
If anyone can help I would appreciate it
Norman

Bump anyone?

Do you have Magisk built-in busybox enabled? If so, try disabling it. From the Magisk release thread:
FAQ:
Q: I am losing root randomly!
A: In some custom roms (known: LineageOS), enabling the Magisk busybox will make root unstable
If you experience root loss issue, disable busybox in MagiskManager
Click to expand...
Click to collapse

Didgeridoohan said:
Do you have Magisk built-in busybox enabled? If so, try disabling it. From the Magisk release thread:
Click to expand...
Click to collapse
Thanks for the answer, but you didn't read all i put. It happens with or without busybox enabled. It happens more when i have developer options enabled so i can disable absolute bluetooth volume.
Norman

manor7777 said:
Thanks for the answer, but you didn't read all i put. It happens with or without busybox enabled. It happens more when i have developer options enabled so i can disable absolute bluetooth volume.
Norman
Click to expand...
Click to collapse
Oh crap... I did miss that part... Sorry about that. Gonna blame a long week and tired eyes.
No idea then, other than it being a LineageOS issue (I really dislike that ROM).

Didgeridoohan said:
Oh crap... I did miss that part... Sorry about that. Gonna blame a long week and tired eyes.
No idea then, other than it being a LineageOS issue (I really dislike that ROM).
Click to expand...
Click to collapse
I preferred CM but its discontinued and replaced by LOS. I use tidal for music and whilst OOS Is good, its buffer city for tidal lostless and I can't get aptx on OOS.. I'm working on it now I'll report Here if I fix it

Advanteges of Magisk?

I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer

akash.galaxy07 said:
I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer
Click to expand...
Click to collapse
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know

manor7777 said:
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know
Click to expand...
Click to collapse
Thanks bro, and, is it stable too? I mean, are there any risks involved?

akash.galaxy07 said:
Thanks bro, and, is it stable too? I mean, are there any risks involved?
Click to expand...
Click to collapse
There are risks with any kind of root on your phone, as an app developer, you should know that.
You could get a virus that takes advantage of root to encrypt all of your files.
Again, you should know this if you are an app developer, there is a difference between creating a single app, and developing applications as a whole!
Magisk is very stable though, more so on OxygenOS but it will be pretty stable with LineageOS too! I have had no problems whatsoever! I have been using android pay and all my root apps without my phone ever crashing! And if you are careful, you won't get a virus (root will not cause a virus, user stupidity gets virus') - enjoy

I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.

Didgeridoohan said:
I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.
Click to expand...
Click to collapse
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.

vipivj said:
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.
Click to expand...
Click to collapse
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.

Didgeridoohan said:
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.
Click to expand...
Click to collapse
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?

vipivj said:
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?
Click to expand...
Click to collapse
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.

MagiskHide
You can use apps like Android Pay or Snapchat on a rooted device

Didgeridoohan said:
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.
Click to expand...
Click to collapse
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?

vipivj said:
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?
Click to expand...
Click to collapse
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...

Didgeridoohan said:
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...
Click to expand...
Click to collapse
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along ?

vipivj said:
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along
Click to expand...
Click to collapse
Ah... Ok. Those kind of issues are easy to work around and the next version of Tasker will have official MagiskSU support.

Use Magisk Manager
I also used Magisk Manager in my old device at it worked fine and as magisk allow you to root Android without effecting on system files I could also install root unsupported apps as well. So i think Magisk is the best solution for you.
link deleted by Moderator due to untrustworthy site will be a help full site to gather more info about magisk from one place.

Topjohnwu has strictly stated that any website which spreads Magisk is not official and cannot be trusted. The only official place is the XDA Thread. If you see any Member promoting an external site related to Magisk, please report the post.

Magisk viper bootloop on beta 12

Has anyone gotten Viper4Android to work on OB12? I've tried SpasilliumNexus' version and the ones in the Magisk repo. They all flash without error, but my 3T fails to boot. Any tips would be appreciated.

Edit: fixt. Thanks @Stephen.

HampTheToker said:
Edit: fixt. Thanks @Stephen.
Click to expand...
Click to collapse
Please post the solution, for the benefit of others that may have a similar question/problem.

redpoint73 said:
Please post the solution, for the benefit of others that may have a similar question/problem.
Click to expand...
Click to collapse
Whoops. I meant thanks for moving my post. I originally posted in the themes apps and mods subforum by mistake. Stephen bumped it over for me pretty quick.
I still can't install viper. It fails to boot and uninstalling Magisk to get it to boot trips dm-verity and it still fails to boot. I imagine getting kicked in the a** on a pirate ship feels much the same. I'm getting tired of restoring backups.
I've seen others report success on OB12...I'm not just one of them even after a clean flash and wiped internal.

Works for me. Used the version with the latest magisk template. Viper 2.3.4.0 Super high quality. It apparently doesn't play well with bluspark kernel

nagi_007pk said:
Works for me. Used the version with the latest magisk template. Viper 2.3.4.0 Super high quality. It apparently doesn't play well with bluspark kernel
Click to expand...
Click to collapse
I'm on Franco's kernel r25. Never had issues using viper previously.

HampTheToker said:
Whoops. I meant thanks for moving my post. I originally posted in the themes apps and mods subforum by mistake. Stephen bumped it over for me pretty quick.
I still can't install viper. It fails to boot and uninstalling Magisk to get it to boot trips dm-verity and it still fails to boot. I imagine getting kicked in the a** on a pirate ship feels much the same. I'm getting tired of restoring backups.
I've seen others report success on OB12...I'm not just one of them even after a clean flash and wiped internal.
Click to expand...
Click to collapse
I would suggest for you to avoid using the magisk based viper 4 android files since it mess up the boot sequence on 13 above.
I follow this steps instead and was able to successfully install viper4android without the boot issue.
Also if you experience the driver abnormal status I would suggest that you grab the SELinux changer and set it to permissive first thing after the device boot.

I never did successfully get v4a to boot, Magisk or otherwise. Magisk 13.5 is right around the corner. Ahrion just announced a partnership with Zackptg5 to improve his audmodlib and multiple different submodules for it. Hopefully, that'll work out.

SuperSU no more & FlashFire (potentially) no more. Moving on...

@topjohnwu
I'm sure you've read the google+ message or the post on the front page in regards to Chainfire stopping development on all current root-related apps. This includes thus SuperSU (which was sold to CCMT a long time ago and they did absolutely nothing with) and FlashFire (which i use to flash an OTA and keep root intact.
Now with that in mind, magisk is pretty much the only root solution now and i'm starting to look into it. I've already installed the manager and will flash the stock rom at a later point. First a question.
What would be the proper way to flash an OTA (on my 6P, for as long as it will get them) and keep magisk root intact? (i know my way around ADB a bit and twrp, usually i ADB BOOT the latter, not install it). Has anyone tried the latest magisk with flashfire on a 6?
I'll appreciate your input.
Regards,
Ch3vr0n

I'm also interested in getting OTAs installed while preserving root and magisk, on my Pixel XL. I can't get it working properly using the suggested method from @topjohnwu

May i suggest you make your own topic then? It will do neither of us any good of replies to our issue get lost in replies to the other

I did already.
I just showed that I am interested in a proper solution as well. I have not asked specifically about my issue, but wanted to tell you that the "official" way (which is well documented) doesn't work for some users (it's not only me).

yeah but you have a completely different device. So what's not working for you, isn't even relevant in case. Thanks for the interest though

and a quick bump.

Ch3vr0n said:
Has anyone tried the latest magisk with flashfire on a 6?
Click to expand...
Click to collapse
Hopefully you're aware that you can no longer even purchase FlashFire on the Google Play Store, so it's not a solution going forward...

Who said that was a problem. I've been using pro since day 1. Pro users don't have the time issue and it works just fine.
Sent from my Nexus 6P with Tapatalk

OTA installation tips (from the official Magisk docs):
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
I know that A/B device users have been reporting negative results with the documented method, but fortunately it's not applicable in this case.
Have seen a bunch of reports of Flashfire not working properly with later release of Magisk, but can't confirm since I've never used it.
That leaves the last described method. Should always work, but by then I usually feel it's a lot easier to just use fastboot to flash the latest factory image...

I have some phones with Magisk, and are not A/B devices. Magisk gets lost after the OTA, I just reflash it, reinstall the 4 Magisk modules I use, and open each app that requires root so I can grant root access to them again. Of course, add to Hide the banking and other apps that need it. Not too much trouble for me, even if I usually receive weekly OTAs. Wish I could save the Superuser and module settings of Magisk before flashing, then I can just restore it.