So the question, The new Magisk or SuperSU ?
Apart from Samsung Pay (Which doesn't work anyway) - Is there a reason why i should move to Magisk ditching the good old SuperSU ?
I personally prefer SuperSU since my time with HTC 8 till Samsung 8. Never have any major problems with it so far. But Magisk is actively being improved.
Related
I've been experiencing a weird issue since I installed DU on my 6p; a lot of apps crash when I try to open them until I use Magisk Hide on them. Not just user apps, I couldn't even connect to my JBL speakers via bluethoot until I hided root to my bluethoot-share system application. I can't get chrome (or anyhting related to it, like the in-app browser of Facebook) to work, and i've tried a lot of versions of Chrome and even Opera; the only thing I could get working it's Firefox. I can't even change my wallpaper (my launcher crashes).
On the other hand, apps that support root, like amaze file manager, work smoothly even without being granted root permission.
I'm a noob, so i have no idea what's causing the problem, but i'll try my best to give you my setup in case you can help me.
- I'm using official Dirty Unicorns ROM v11.3 (7.1.2) with the correspondent stock kernel (unicornblood)
- I'm rooted by chainfire's SuperSU v2.79
I don't know if the mods i've installed have anything to do, but i'll share them just in case
I installed these audio mods:
- Hi-Performance DAC Enabler:
- aptX™ HD Enabler
- AINUR Pandora
This other thermal mod: CTTmod
And I'm using Magisk v12.0
Thank you very much in advance
I don't think you can use Magisk and SuperSu at the same time because Magisk includes its own root app, PhilsSu. You are basically using two different root apps at the same time. You can try uninstalling SuperSu or Magisk but you might be better off doing a clean flash of DU, Gapps then either SuperSu or Magisk but not both.
jhs39 said:
I don't think you can use Magisk and SuperSu at the same time because Magisk includes its own root app, PhilsSu. You are basically using two different root apps at the same time. You can try uninstalling SuperSu or Magisk but you might be better off doing a clean flash of DU, Gapps then either SuperSu or Magisk but not both.
Click to expand...
Click to collapse
When I tried to install magisk without SuperSU it asked me to root my device first and aborted installation
I've never used Magisk but I thought PhilsSu was part of it. I suppose you can download PhilsSu separately and flash it before Magisk but I know that's the rooting app that works with Magisk, not SuperSu.
---------- Post added at 08:09 PM ---------- Previous post was at 08:02 PM ----------
Now that I think about it I'm pretty sure I read that you can uninstall SuperSu using the Play Store app then choose to root with PhilsSu within Magisk if you have both installed at the same time.
Magisk v12 is its own root solution. It doesn't use SuperSU & it doesn't use PHH superuser either. It's its own thing now. Magisk Hide does not hide SuperSU, only its own root. So if you're using Magisk Manager to hide apps while SuperSU is installed, it's literally doing nothing. Your root is not hidden and you should be able to confirm this using a root checker app. I guess it's possible that having both is causing your issues, but I follow the Magisk general support thread and never see issues that severe. I'd guess it's a stability issue on your ROM.
If you want to use Magisk Hide correctly, you need to get rid of SuperSU. Select the full unroot option from the settings. Hop on over to osm0sis thread here and grab and flash the unsu.zip he has over there. Then flash your ROMs boot.img again (unless it's rooted). That'll completely wipe SuperSU and let you use Magisk.
So basically (stock phone > unlock bootloader > install TWRP > flash Magisk v12) and now you're rooted. No SuperSU / anything else is involved. V12 literally roots you and you need to clean up SuperSU to use it properly.
RoyJ said:
Magisk v12 is its own root solution. It doesn't use SuperSU & it doesn't use PHH superuser either. It's its own thing now. Magisk Hide does not hide SuperSU, only its own root. So if you're using Magisk Manager to hide apps while SuperSU is installed, it's literally doing nothing. Your root is not hidden and you should be able to confirm this using a root checker app. I guess it's possible that having both is causing your issues, but I follow the Magisk general support thread and never see issues that severe. I'd guess it's a stability issue on your ROM.
If you want to use Magisk Hide correctly, you need to get rid of SuperSU. Select the full unroot option from the settings. Hop on over to osm0sis thread here and grab and flash the unsu.zip he has over there. Then flash your ROMs boot.img again (unless it's rooted). That'll completely wipe SuperSU and let you use Magisk.
So basically (stock phone > unlock bootloader > install TWRP > flash Magisk v12) and now you're rooted. No SuperSU / anything else is involved. V12 literally roots you and you need to clean up SuperSU to use it properly.
Click to expand...
Click to collapse
Thank you very much, that clarifies a lot for me and it did the trick, i clean flashed DU and rooted with Magisk v12, everything's perfect now:good:
Please, can someone help me to replace magisk without any bootloop, I just don't like this magisk thing and prefer good old supersu. Please, nearly all the nought rom for s4 has magisk and I really want su. I tried two to just to flash the zip, and i had to factory reset twice. Thank you . :crying::crying:
Uninstall Magisk, flash SuperSU zip. Done.
Pwnycorn said:
Uninstall Magisk, flash SuperSU zip. Done.
Click to expand...
Click to collapse
Thank you for the reply but how do i uninstall magisk
Nearly all the Android 7.x ROMs are using Magisk because of its ability to bypass SafetyNet for use with banking apps as well as Pokémon Go. Plus, SuperSU just recently had a botched rollout in that some devices bootlooped when it was installed, some devices lost root completely, and some were unable to update the hosts file using AdAway. Couple that with the new owners of SuperSU trying to slip analytics items into the app, not to mention excessive permissions for the bug reporting feature and you have a mess. So, while I have absolutely no idea what issues you're having with Magisk, you're doing far worse in my opinion going back to SuperSU and should instead use phh Superuser. It's as simple to use as SuperSU while not being saddled with SuperSU's excessive permissions and device problems.
With that said, if you really want to go back to SuperSU, dirty flash your custom ROM if using one (uninstalls Magisk), then install SuperSU and reboot.
Horridhenry said:
Thank you for the reply but how do i uninstall magisk
Click to expand...
Click to collapse
Have you looked in the Magisk thread? I'm pretty sure they have some uninstall instructions there.
Strephon Alkhalikoi said:
Nearly all the Android 7.x ROMs are using Magisk because of its ability to bypass SafetyNet for use with banking apps as well as Pokémon Go. Plus, SuperSU just recently had a botched rollout in that some devices bootlooped when it was installed, some devices lost root completely, and some were unable to update the hosts file using AdAway. Couple that with the new owners of SuperSU trying to slip analytics items into the app, not to mention excessive permissions for the bug reporting feature and you have a mess. So, while I have absolutely no idea what issues you're having with Magisk, you're doing far worse in my opinion going back to SuperSU and should instead use phh Superuser. It's as simple to use as SuperSU while not being saddled with SuperSU's excessive permissions and device problems.
With that said, if you really want to go back to SuperSU, dirty flash your custom ROM if using one (uninstalls Magisk), then install SuperSU and reboot.
Click to expand...
Click to collapse
If his ROM comes with Magisk "out-of-the-box", then dirty flashing won't do anything.
@Pwnycorn: LOL...I didn't think that one through, did I?
In any case, the bulk of my post was reasons why NOT to use SuperSU. Personally, there's nothing SuperSU can do that Magisk can't, and I don't miss SuperSU at all. In fact, I ditched SuperSU on MachineX ROM and successfully replaced it with Magisk. I replaced MicroG in that ROM as well, but I digress.
Strephon Alkhalikoi said:
@Pwnycorn: LOL...I didn't think that one through, did I?
In any case, the bulk of my post was reasons why NOT to use SuperSU. Personally, there's nothing SuperSU can do that Magisk can't, and I don't miss SuperSU at all. In fact, I ditched SuperSU on MachineX ROM and successfully replaced it with Magisk. I replaced MicroG in that ROM as well, but I digress.
Click to expand...
Click to collapse
fun fact!
galaxy S2 doesn't support Magisk(outdated boot image format),...i feel sorry for myself right now..LOL
Just like the topic says. I'm currently running Magisk 11.6 and was told not to install or upgrade to v 12 since it was buggy. Well it looks like v13 is available (13.1 actually). Is this safe to upgrade?
Rom: NATF 4.0 for H910 (AT&T) - Android v7.0
Sidenote: What is preventing SafetyNet from passing (CTS Profile mismatch) ? Is the due to the DirtyCow exploit? Debugging is disabled and Magisk hide is on.
is definitely safe if you have a US996 variant of the LGV20 as I'm using it on that... about to try it out on my H918 variant of the LGV20, but should be fine with since I went through all the betas fine
I flashed 13beta on my h918 without doing anything special and it works just fine
Well I took the advice and upgraded. It didn't go so smooth. The update feature within Magisk manager didn't work. First it didn't let the device reboot. I had to pull the battery since all the shutdown commands did nothing.
2nd time trying to upgrade, it rebooted this time and when I checked the manager again it said magisk wasn't even installed. So I manually got the zip and updated in recovery and then manually installed the latest apk for the manager and finally I'm up to date. All is well (aside from safetynet).
When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.
shadavis08 said:
When switching to Magisk 13.1 from anything lower you should use the magisk uninstaller before flashing the newer Magisk . Anything lower than Magisk 13 is not compatible with the newer v5 Magisk manager as far as I know.
Click to expand...
Click to collapse
I completely overlooked the uninstaller. I don't know how, I just did.
Updated to 13.2 and SafetyNet seems to pass now. Although I'm still "Uncertified" in the Play store.
Well goddamn, it must be working because I was able to get Google Wallet to work and Android Pay lets me add a card, although it says my card is not supported. I don't have a second card currently to test it. Maybe I need to enable it on the banks end. I'll call them tomorrow and ask.
Edit: Nope. It's my bank, not the card.
I am planning to eventually root the stock rom of SM-T580 to use AdAway and Greenify.
What sort of problems / side effects if any might I run into after rooting the stock rom?
Also I do not plan on using SuperSU as I will be using Magisk.
Some apps can not be installed anymore. (Netflix from playstore, super mario). Magisk does not prevent this. Use a browser with an ad blocker.
bert73 said:
Some apps can not be installed anymore. (Netflix from playstore, super mario). Magisk does not prevent this. Use a browser with an ad blocker.
Click to expand...
Click to collapse
Not even with Magisk hide enabled?
Not on my tab s2 with magisk.
Netflix working fine here with Magisk 13.0 and Stock Android N. But on my OnePlus One Netflix isn't available even with Magisk.
Shadowghoster said:
Netflix working fine here with Magisk 13.0 and Stock Android N. But on my OnePlus One Netflix isn't available even with Magisk.
Click to expand...
Click to collapse
When updating Magisk is it better to use the uninstaller zip and flash Magisk again or is using the built in updater fine?
You can't go wrong any way you use magisk. Mostly everything can be flashed directly from magisk. Remember magisk is root and has control. You won't have any problem updating magisk right from it's interface. The only time I've had a problem, has been from flashing a magisk module that doesn't support my device. Best regards.
I know there are many guide on this forum but I cannot get them working. Maybe someone might be able to help me.
I have trouble to root my one plus 5.
~4 Years ago when I received it I was able to gain root access by flashing SU, it was really easy.
But today I cannot find an install zip that isn't over 3 years old and all others don't work. I flashed them via TWRP 3.4.0.1 and they displayed a "success" message in the end, but it didn't work.
Before that I tried it via Magisk but that did nothing as well. It said it replaced my boot.img but my Magisk Manager claims neither Magisk nor the Manager is installed (not sure how that's even possible).
I'm on Pixel Extended Rom with Firmware 10.0.1
Thank you very much.
Solved it by myself. I had to use the newest Canary version of Magisk (21), not the stable Version (20).
So I had to manually download it.