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.

[ROOT] [Magisk] [Galaxy S6] - Magisk-root uninstalls automatically?

Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry

larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
Thank you
Larry
Click to expand...
Click to collapse
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk

CyberZeus1977 said:
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk
Click to expand...
Click to collapse
Tell me somthing about "stock kernel" and "EX Kernel" what is that and how can i install that? or change that?

I have the same problem, galaxy S6.

I noticed losing root randomly and fixed it by going install patch boot img then you flash the boot img in recovery. So far it's been a day no root loss
Lineage 14.1 for lg stylo 2 plus

Hi ! I have sale problem with my S8+ with custom rom and Custom kernel

Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
I hope I will be able to get some more usefull information for you soon (LogCat etc etc.). If any one has an answer or suggested options it would be good. I am particularly interested in getting the Busy Box feature to work with Root as I am working on an app for my job that needs both options (I work offshore and am trying to adapt a piece of Seismic QC software (unix based) to run on phones / tab's - Android).
I will sign up properly and start to follow the threads more closely.
Cheers... Andy
-Samsung S6 - Full Magisk Module (with recommended zeroflte TWRP).

AndyQVT said:
Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
Click to expand...
Click to collapse
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry
Click to expand...
Click to collapse
See above

Thanks to all for the help
Nye-uhls said:
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
See above
Click to expand...
Click to collapse
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy

AndyQVT said:
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy
Click to expand...
Click to collapse
Glad everything is good! Sometimes magisk will get messed up, so just updating or even reinstalling will fix things.
Just keep in mind, its very likely you'll have problems again down the road... Samsung phones do a lot of weird stuff under the hood, and eventually symlinks will get broken, files deleted etc... So when that does happen, the best you can do is uninstall, reflash, update, and watch your modules.

Today updated to 15.3 and install James DSP root losed...When open magisk ask for installation reboot to recovery twrp install latest zip reboot open magisk it close it self and root lost again ?! Any advice from @topjohnwu

Do you guys mind posting a resource that shows how to root the S6 using magisk? I'm very rusty, last time I dealt with rooting was 8 years ago. Any help is appreciated. Thanks

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.

help for rooted note 8

Hi guys. I need some help for my rooted galaxy note 8. I had rooted my phone a long ago and all was working good. All apps including banking apps were working fine with magisk hide. But few days ago i wanted to update my phone so i flashed stock rom with odin and updated my device. Earlier my bootloader version was 6 and now its updated to version 8. Then after updating i flashed latest twrp and rooted with magisk. I flashed magisk version 20.1 and magisk manager version was 7.4.0 . Then magisk update was available so i updated to magisk version 20.2 and magisk manager to version 7.5.0 . Now the problem starts. I am facing 3 issues.
1- my phone starts freezing and then reboots randomly. It happens quite frequently atleast 2-3 times in a day. Every time i clear cache partition from twrp but problem persists. I had checked ram also but ram useage is also fine. Please help me with this issue.
2- while searching for the solution of above problem i read somewhere that it might be because of safety net check. Earlier safetynet check was pass but now safety net check was fail. I flashed bypass safety net mod. But when my phone reboot a warning appears that your device has some internal problem. Contact the manufacturer. I pressed ok and phone starts. It seems to work normal but then i realised my device was not connecting to any wifi network. When i click on available wifi nothing happened. So i uninstalled the safety net bypass mod and then wifi start working again.
3- now final thing i want to know. If the above problem did not solve then i have to unroot my phone which i dont want. But if i had to then i dont want to flash stock rom. I want to unroot from magisk app itself. I had edited build.prop file for using samsung health app. So now if i unroot from magisk app will the changes made by me in build.prop file remain or it will revert back. Also will banking apps work or not....
I know its very lengthy post but please help

Wow...
70 views no comment..... it seems all the developers and tech people are enjoying winter break

Try going back to previous version of Magisk. I have Snapdragon N8 so I have supersu. But I did update my A20g with newest Magisk and had an issue. I know you have N8 but was just saying maybe could be new Magisk.
My SM-N950U Still Rooted Note 8

S10 bootloop, when restarting

Hey, everybody. First post. I need some serious help. I've been rooting and modding for years, but I don't know everything, so please don't assume that I do. Right, my Exynos G973F is rooted with Thunderstorm Kernel, and has TWRP installed. The phone functions perfectly and all of my apps pass root detection. However, if I restart the phone, it gets to the point where all my icons load and I can use the phone, then it suddenly goes back to the Samsung logo. The case used to be that if I left it long enough, it wouldn't continue to bootloop, but recently I'm having to restore TWRP images just to use my phone. I've done a factory reset, and tried to do the same thing with a custom kernel, but it will not pass safetynet. I've got Riru installed, LSExposed, safetynet patch 2.2.0 and Magisk Hide patch, with a different fingerprint set, and it absolutely won't pass cts. So, starting from scratch is not an option, because I've tried everything. How can I figure out what's making it bootloop? As I've said, the phone is perfect, other than this. It's really bizarre. Hope someone can help! Thanks in advance!