Benefits of using Magisk vs SuperSU? Reason I am asking is when I originally rooted my G5 I watched a tut given to me by a friend that I trust and SuperSU was recommended, but the more I read and learn it appears that Magisk may be the better alernative, as for one it is Open Source.
I had an issue when updating from LineagOS 05282017 to 06282017 and having the newest version of SuperSU on the phone - no WiFi, as soon as I placed SuperSU 2.79 back on (instead of 2.82) all worked well, but I am wondering if I may be using the wrong tool in SuperSU instead of Magisk.
So what says the hive - SuperSU or Magisk?
Bob
Related
Good Morning,
I installed Magisk in order to use Android Pay. Sadly it didn't work for me, but it's not that important. So I want to uninstall Magisk and install a normal version of SuperSU.
OnePlus 3
Official Cyanogenmod 13
Magisk
Phh's Superuser
Thanks
Closed, just couldn't find the Uninstaller zip.
I have problems with greenify an magisk su.
Instant deep doze after screen off doesn't work. With supersu it works without any problems.
With magisk my phone will only sleep in light doze mode.
Su is granted!
Anyone else?
If you're having this problem, it's more likely that you're either using an outdated version of Magisk, or your ROM doesn't support Greenify. I'm using the latest beta of Greenify and the latest version of Magisk and I'm not having any problems. If you are coming from SuperSU and you didn't do a clean wipe of your device, with a fresh install of whatever ROM you're using, it's likely that SuperSU is messing with Magisk at the same time.
Would suggest anyone updating Magisk read the Magisk support thread first, as many are having problems with Magisk v13.1/.2.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
clouds5 said:
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
Click to expand...
Click to collapse
See the last few pages of WTF thread. 17.0 boot loops. 17.1 fixes boot loops, but best to uninstall 16 Magisk in TWRP before installing 17.1. Run the uninstaller.
However, there's problems with Magisk Hide on 17.x right now. It crashes for a lot of people.
Thx, I'll stick with 16.0 for the moment. No issues with it and I'm not missing anything so...
17.0 made my stock rom bootloop.
17.1 works fine for me.
It probably makes no difference how you install it, but I used the patch boot image option then flashed the patched boot.img using fastboot.
use dd to get an image of your currently working boot partition
patch that boot.img with magisk manager to 17.1 and copy to PC
use fastboot to flash that patched_boot.img and then reboot (or fastboot boot TWRP.img then reboot from there to be extra safe)
I'm on 21B and that works for me. I have not tried a different way so I can't confirm/deny any other method yet
Sent from my LGE V30 using XDA Labs
21a here i just clean flashed with 17.1 ._.
I'm getting issues with 17.1 and magisk hide.. Is there any fixes? Thanks in advance
So just want to make sure.. can I run the magisk Uninstaller by flashing the zip in TWRP and the flashing 17.1 in TWRP to reinstall magisk?
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
silver311 said:
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
Click to expand...
Click to collapse
This worked for me as well.
1. Uninstall Magisk 16 in TWRP using the latest MagiskUninstaller.
2. Flash Magisk 17.1
3. Boot up and un-install MagiskManager 5.9.1
4. Install MagiskManager 5.8.3.
As expected, the SafetyNet check doesn't work but some of the modules I use are being updated to the new template which prevents them from running on Magisk 16.0.
Anyone know how to get rid of the pop-up to update MagiskManager every time the app is opened?
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
trekminal said:
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
Click to expand...
Click to collapse
Yes, discussed over in WTF thread.
https://forum.xda-developers.com/showpost.php?p=77687418&postcount=1798
Thanks.
I updated to MagiskManager 6.0 but it shows me the option to update to Magisk 17.1, not the 17.2
I will wait some days until 17.2 will be available through the main app.
Any else have magisk manager crashing when using selecting #magisk hide from the magisk manager menu?
running 20d us998
with magisk 17.1
magisk manager 6 (although 5.9.1 did the same thing)
and root checker remover
someone on the magisk support thread recommended deleting the hidelist file which didn't really do anything. Problem is still occuring even with the new hidelist.
What happened to SuperSu? I remember rooting every phone with it when I was a kid.All I hear is about Magisk nowadays.I love Magisk for the things I can do with it but what happened to SuperSu?
Why the development was stopped?
@RyanCr7
IMHO you should ask this question to developer of SuperSU.
BTW: With Android 10 things have dramatically changed.
In android 11, the devs of Magisk baked in the features of superSU, so having superSu now is redundant.
jasonlarawan said:
In android 11, the devs of Magisk baked in the features of superSU, so having superSu now is redundant.
Click to expand...
Click to collapse
So you mean magisk now has *true* rooting ?
In contrast to the outdated SuperSu what installed the SU ( AKA root ) in Android's system-space Magisk simply installs the SU in Android's user-space.
Hi guys, will Twrp be available for this device so I can root it with Supersu, instead of Magisk, couldn’t get Viper4Android and Adaway run properly with Magisk.
Yes, TWRP will be available, I tried making it for now with a dump but failed, waiting the real sources.
Also, use magisk lol, supersu is ancient and doesn't work. It's impossible that magisk didn't worked with those apps
I think it didn’t work cause of systemless root
TroyCas99 said:
I think it didn’t work cause of systemless root
Click to expand...
Click to collapse
Well no idea, all that I know is that Adaway and 99% Viper is working fine with Magisk.