• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Magisk General Support / Discussion

Search This thread

zgfg

Senior Member
Oct 10, 2016
6,054
3,552
So far so good

However, I cannot be happy that Zygisk cannot be hidden (it acts like a time bomb)
 

Attachments

  • 1.jpg
    1.jpg
    159.6 KB · Views: 74
  • 5.jpg
    5.jpg
    237.4 KB · Views: 73
  • 2.jpg
    2.jpg
    187.1 KB · Views: 68
  • 6.jpg
    6.jpg
    63.5 KB · Views: 67
  • 3.jpg
    3.jpg
    227 KB · Views: 64
  • 4.jpg
    4.jpg
    209.3 KB · Views: 72

mikwii2000

Member
Nov 1, 2015
16
5
Venice
Hi everyone, and thanks the developers for this great app. I need help because I can't hide the magisk app, the option isn't available/clickable in the Magisk settings as I show in the screenshot. I'm running an Android 11-based AOSP custom rom (Derpfest).
Thanks to anyone that can help ;)
Screenshot_20210923-220134479 (1).jpg
 

73sydney

Senior Member
Jul 21, 2018
1,989
1,772
Sydney
Google Pixel 2 XL
Come on mate... That's not what it's about. It's the page after page of off-topic social media/Telegram style posting, that clutters the thread so much that discussions about actual Magisk stuff gets even harder to find (in this impossible to search mammoth of a thread), that is the problem.

I'll keep an eye on things (since I pretty much live in the Magisk forum anyway) and let you guys know if it starts getting out of hand.

Nice try at satire though... It baited me hook line and sinker. :ROFLMAO:

Answered in private, cheers
 

zgfg

Senior Member
Oct 10, 2016
6,054
3,552
Can you elaborate as to why you need to hide Zygisk?
Any banking app etc can exploit that way to detect root in the future (not saying that there were not other ways to do it, but now it will be one more way, and the source code how to do that is also publicly available)
 
Last edited:
  • Like
Reactions: rodken

J.Michael

Recognized Contributor
Jan 20, 2018
913
797
Samsung Galaxy Tab A series
Now I'm thinking, is any way to disable recovery while holding the combo key so the combo key work only for the magisk too boot?
If you mean, make the bootloader have no interest in booting recovery, that wouldn't help you. Magisk hijacked recovery, Magisk *needs* the bootloader to load "recovery", which is now really Magisk. Once Magisk gets control, Magisk chooses whether to keep control or to turn control over to the original "recovery".

If you mean, make Magisk *always* keep control when booted as part of recovery, in theory it would be trivial: just change the "if" test. I keep hearing that Magisk is open source, so all you need to do is checkout a copy and make the change.

In practice, I don't like my odds. I don't know your background, so I can't guess your chances. Rotsa ruck!
 

ipdev

Recognized Contributor
Feb 14, 2016
1,608
1
2,153
Google Nexus 10
Nexus 7 (2013)
Hi everyone, and thanks the developers for this great app. I need help because I can't hide the magisk app, the option isn't available/clickable in the Magisk settings as I show in the screenshot. I'm running an Android 11-based AOSP custom rom (Derpfest).
Thanks to anyone that can help ;)
View attachment 5417127
Requires the Update Channel to be accessible.
(You have to be online to hide the Magisk app. 😞)

The update channel has to be set to the Magisk app version you want to install.
Using vvb2060's alpha builds, it will be pointing the the version released to github.
vvb2060 [magisk_files] - GitHub - alpha - Link

From the screenshot, it appears you set the Update Channel to Custom Channel.
The Custom Channel is not set so no online version can be found.

Cheers. :cowboy:
 

pndwal

Senior Member
How is this version working for you?
(Alpha is for mavericks only! 😬 )

As already mentioned, it's fine at present w/ caveats mentioned re. ease of Zygisk detection which vvb2060 has stated is impossible to hide, at least at present.

I changed back to USNF 2.1.1 & Riru (last build didn't like Riru for me), enabled LSPosed too, updated Magisk / rebooted and all seemed good; SafetyNet pass, stable etc.

On next reboot SafetyNet failed inexplicably however. --> disabled Riru and USNF, rebooted, Reinstalled USNF 2.1.1 for good measure, enabled Riru, rebooted...

--> SafetyNet passing, system stable, SafetyNet survives reboots even with LSPosed, webview fine, no further issues.

@vvb2060 seems to be restoring just enough of the revoked MagiskHide commits to allow SafetyNet pass ATM, and there do seem to be more mod traces being detected. I can't even seem to hide 'MagiskHide' (aka MagiskDeny) any longer. See screenshots.

I'm guessing others may need to supply modules (made more powerful by Zygisk at least) or other solutions for hiding these, and I don't assume even SafetyNet will pass without at least an updated USNF in future TJW builds. Hiding Zygisk itself may be a tall order...
Screenshot_2021-09-24-13-38-23-932_com.topjohnwu.magisk.jpg
Screenshot_2021-09-24-13-39-59-013_io.github.vvb2060.mahoshojo.png
Screenshot_2021-09-24-13-34-43-389_io.github.vvb2060.magiskdetector.jpg
Screenshot_2021-09-24-13-34-17-482_io.github.vvb2060.zygiskdetector.jpg
😜 PW
 
  • Like
Reactions: jons99 and BillGoss

mikwii2000

Member
Nov 1, 2015
16
5
Venice
Requires the Update Channel to be accessible.
(You have to be online to hide the Magisk app. 😞)

The update channel has to be set to the Magisk app version you want to install.
Using vvb2060's alpha builds, it will be pointing the the version released to github.​
vvb2060 [magisk_files] - GitHub - alpha - Link

From the screenshot, it appears you set the Update Channel to Custom Channel.
The Custom Channel is not set so no online version can be found.

Cheers. :cowboy:
Thank you for your time man, that solved my problem!
 
Mar 25, 2012
1,053
772
31
Crete,,,Heraklio
If you mean, make the bootloader have no interest in booting recovery, that wouldn't help you. Magisk hijacked recovery, Magisk *needs* the bootloader to load "recovery", which is now really Magisk. Once Magisk gets control, Magisk chooses whether to keep control or to turn control over to the original "recovery".

If you mean, make Magisk *always* keep control when booted as part of recovery, in theory it would be trivial: just change the "if" test. I keep hearing that Magisk is open source, so all you need to do is checkout a copy and make the change.

In practice, I don't like my odds. I don't know your background, so I can't guess your chances. Rotsa ruck!

News! Just created twrp, all night was working and now is ready, let's see now what I can do with magisk!
 

Attachments

  • DSC_0045.JPG
    DSC_0045.JPG
    3.3 MB · Views: 49

Stillhard

Senior Member
Sep 25, 2016
64
40
Tried newest alpha, zygisk = No, ramdisk = yes, denylist(s) active and running (weird)
Reverted to 0ab31ab0-alpha, zygisk = Yes...
For now i'm happy with 9bf835e8-alpha
 
Mar 25, 2012
1,053
772
31
Crete,,,Heraklio
So guys after tests I have to find out how I add squashfs support on twrp, cause I can't do much, what I saw is that when I rebooted to system magisk was not working like the first place, tried to boot to twrp and guess what, it booted to stock recovery, how? I didn't flash the stock recovery, I searched and I find out that when it booting to system everything I has flash goes back to stock, for this magisk don't work when I trying to boot with combo key, everything goes back to stock without flashing, so the patched recovery from magisk goes back to stock while booting, I will make more research!
 
  • Like
Reactions: J.Michael

pndwal

Senior Member
So guys after tests I have to find out how I add squashfs support on twrp, cause I can't do much, what I saw is that when I rebooted to system magisk was not working like the first place, tried to boot to twrp and guess what, it booted to stock recovery, how? I didn't flash the stock recovery, I searched and I find out that when it booting to system everything I has flash goes back to stock, for this magisk don't work when I trying to boot with combo key, everything goes back to stock without flashing, so the patched recovery from magisk goes back to stock while booting, I will make more research!
Behaviour is pretty standard w/ stock ROMs (eg MIUI):
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
https://twrp.me/xiaomi/xiaomimi9tpro.html

Nb. as mentioned, installing Magisk zip installer from TWRP will only succeed if bootloader contains 'boot' ramdisk support to allow basic ramdisk added by Magisk to be utilised... Of course you may be considering other custom recovery tricks. 😛 PW
 

pndwal

Senior Member
Tried newest alpha, zygisk = No, ramdisk = yes, denylist(s) active and running (weird)
Reverted to 0ab31ab0-alpha, zygisk = Yes...
For now i'm happy with 9bf835e8-alpha
Interestingly, I had such issues with 0ab31ab0-alpha with Riru enabled, but issue is gone for me in 61783ffc-alpha...

You could try disabling Riru & USNF 2.x, rebooting, checking Zygisk status / settings, then enabling again; I needed this initially - actually uninstalled USNF, disabled Riru and rebooted before installing again... No issue since on RN8T.

Of course this may be a per device issue.

John and vvb2060 are still busy with implementation of Zygisk; this may help in next builds:
https://github.com/topjohnwu/Magisk/pull/4720
... merged with Commits on Sep 24, 2021:
https://github.com/vvb2060/Magisk/commits/app_zygote
... there'll be more too. PW
 
  • Like
Reactions: ipdev and rodken

J.Michael

Recognized Contributor
Jan 20, 2018
913
797
Samsung Galaxy Tab A series
Behaviour is pretty standard w/ stock ROMs (eg MIUI):

https://twrp.me/xiaomi/xiaomimi9tpro.html
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
He showed us a screenshot of TWRP running.
Does he have to tell TWRP to protect itself?
 

J.Michael

Recognized Contributor
Jan 20, 2018
913
797
Samsung Galaxy Tab A series
So guys after tests I have to find out how I add squashfs support on twrp, cause I can't do much, what I saw is that when I rebooted to system magisk was not working like the first place, tried to boot to twrp and guess what, it booted to stock recovery, how? I didn't flash the stock recovery, I searched and I find out that when it booting to system everything I has flash goes back to stock, for this magisk don't work when I trying to boot with combo key, everything goes back to stock without flashing, so the patched recovery from magisk goes back to stock while booting, I will make more research!
Please put more space between thoughts. Maybe an occasional period or carriage return.

What happens if you
Code:
fastboot boot magisk-patched-recovery.img
?
 
  • Like
Reactions: digger16309

Top Liked Posts

  • 1
    I think you can still use patched AP method (but with canary release), vbmeta gets patched during this process as well, it's nothing to get confused about. I never used patched AP method tho, rooting with custom recovery is much easier/faster imo. And I feel more confident with TWRP instead of stock recovery.
    Here you have the guide:
    Thread '[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 Ultra (Exynos)' https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-s21-ultra-exynos.4240993/

    Cheers
    Thanks for the help, really appreciated.
    It works, got BUKG rooted (≧▽≦)
  • 14
    For those who use Alpha or new Canary and miss the old Modules Repo:

    Download and install their root app that will act like the old Modules tab with the integrated connection to the Repo

    Actually, two Repositories - the old 'official' one plus the alternative new Repo (the old/original TJW's Repo is closed for submission of any new modules - only the modules that were admitted previously could still be updated to the old 'official' Repo)
    13
    Great guide, thanks... I think I followed a similar guide from you a while back, but forgot full path requirement... Pinged you as I thought you'd come through! 👍

    I didn't say MagiskBoot was part of Magisk binary however... I clearly said 'magiskboot * binary * isn't working for me'. 😜 ...

    Thanks for the method. PW
    This one might be a bit more confusing. ;)

    Not sure I can operate Magiskboot before I flash it to the device. Once I flash Magisk, I have access to fastboot through recovery, and that's it.
    While catching up last night, I missed that you are not rooted. :oops:

    ---

    Without root, you need a directory with heightened permissions that you can access.

    You should be able to use the /data/local/tmp/ directory.

    Unzip the Magisk apk file and push the appropriate architecture to the device.
    Then set the permissions to be executable.

    Linux/Mac command line example.
    Make the appropriate changes if you use Windows.​
    • Unpack the lib directory from the Magisk apk file.
      unzip app-debug.apk lib*
    • Push the matching Magisk architecture to the device.
      adb push lib/YourDeviceArchitecture/* /data/local/tmp/
    • Push the boot image you want to modify to the device.
      adb push boot.img /data/local/tmp/
    • Set permissions.
      adb shell chmod 0755 /data/local/tmp/*.so
    • Enter adb shell and change directories.
      adb shell
      cd /data/local/tmp/
    • Run the commands using the ./ prefix.
      ./libmagiskboot.so

    Make the changes you want, exit the shell and pull the new-boot image to the computer.
    Reboot into bootloader and boot the new-boot image.

    Note:
    /data/local/tmp/ should be an empty directory.
    You should clear the directory after you are done using it. ;)


    Quick example just unpacking and repacking a boot image without root.
    Magiskboot Example - Pastebin - Link

    Hope it helps more than confuse. 🙃

    Cheers. :cowboy:
    12
    Hi all. :D

    I do not use twitter so, I am out of the loop at times. :confused:
    Links to a few tweets were noted in an issue on USNF github earlier today.

    Seemed to be appropriate to mention here.

    From John Wu.
    PSA: MagiskHide of Magisk v23.0 no longer passes SafetyNet, even with BASIC evalType. Tested on my Pixel 4 XL running stock Android 12 with vanilla Magisk v23.0.

    MagiskHide is *officially* dead. If you need any kind of root hiding, it's the perfect time to find alternatives.
    There are already plenty of "root hiding" modules out there that I'm aware of, some even utilizing the latest features of Magisk canary.

    I'm obligated to distance myself from any tamper detection circumvention, so I will not assist/promote any modules. Do your own research 🙃

    From osm0sis
    *Cough* @kdrag0n's Universal SafetyNet Fix (USNF) *Cough* 😘
    To be specific, Magisk Canary, Zygisk and DenyList enabled, and USNF v2.2.0+ is the way forward. 🤘

    Cheers all. :cowboy:
    12
    Is there any good reason to update to a canary or alpha build if stable 23.0 does everything you want from it - apart from curiosity to where Magisk is heading with zygisk?
    I'm surprised seeing so many people installing unstable builds and running into problems.
    There are way too many people that update just for the sake of updating...
    10

    Latest Magisk Canary:​

    Magisk (7e9d4512) (23014)​

    • Fix crashes when multiple Zygisk module is installed
    • Fix crashes in magiskboot under certain circumstances
    • Always unload Zygisk itself after post specialize
    • Add module suspension state in Magisk app (riru/zygisk modules)

    Diffs to v23.0​

    • [General] MagiskHide is removed from Magisk
    • [General] Support 64-bit only systems
    • [General] Support Android 12
    • [Zygisk] Introduce new feature: Zygisk
    • [Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes
    • [MagiskBoot] Support patching 32-bit kernel zImages
    • [MagiskBoot] Support boot image header v4
    • [MagiskBoot] Support patching out skip_initramfs from dtb bootargs
    • [MagiskInit] Support /proc/bootconfig for loading boot configurations
    • [MagiskInit] Better support for some Meizu devices
    • [MagiskInit] Better support for some Oppo/Realme devices
    • [MagiskInit] Support init.real on some Sony devices
    • [MagiskPolicy] Load *_compat_cil_file from system_ext
    • [MagiskSU] Use isolated devpts if the kernel supports it
    • [MagiskSU] Fix root shell if isolated mount namespace is set
    • [resetprop] Deleted properties are now wiped from memory instead of just unlinking
    • [App] Build a single APK for all ABIs
    • [App] Switch to use standard bottom navigation bar
    • [App] Downloading modules within the Magisk app is removed
    https://github.com/topjohnwu/magisk-files/blob/55bdc45955e7ba1fe4d296b6fc06f926ebc9ddd1/notes.md
    👍 PW
  • 1069
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    156
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    New Forum!
    As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
    **For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
    It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about :D

    The Pixel Phone
    Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things ;)

    Current Progress
    In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
    To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
    After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)

    Safety Net Disaster
    Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
    However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
    I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.

    Conclusion
    Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.

    Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!
    121
    Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.

    First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.

    -------------------------

    What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!

    Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).

    He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.

    It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
    @topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.

    tl;dr Towards @topjohnwu, I have:
    - expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
    - expressed surprise he is using SuperSU binaries in a competing superuser without permission
    - expressed surprise he is posting a modified LiveBoot without permission
    - informed him of issues with the modified SuperSU he has posted
    - let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser

    To be crystal clear:
    - I have not asked for an apology
    - I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
    - I have not made an issue of any of this anywhere, until this post
    - I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
    - I have not reported this thread to XDA moderators for copyright violations or otherwise

    While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.

    To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.

    I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake :)

    Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.
    76
    Thread temporarily closed so everyone sees this.

    The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.

    The Flash
    Forum Moderator

    EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.
    75
    Hello everyone!

    I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

    Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

    So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

    Google, how will a few systemless mods do any harm :p:p