Magisk General Support / Discussion

Search This thread

kugamu

Member
Sep 27, 2022
9
7
Who can tell me how to fix these errors?
 

Attachments

  • 1664297509941.png
    1664297509941.png
    185.8 KB · Views: 76
  • 1664297544936.png
    1664297544936.png
    205.1 KB · Views: 74
  • 1664297611639.png
    1664297611639.png
    245.7 KB · Views: 74

zgfg

Senior Member
Oct 10, 2016
7,943
5,483
Who can tell me how to fix these errors?
All those apps must be in DenyList

For Oprek use additionally Hide My Applist (LSPosed module) to hide Magisk app and all LSPosed modules (HMA itself including)- there have been guides here how to setup.
See the screenshot.
Same works for TB Checker

From Momo you will probably never fully hide root - somebody else could give you some hints

Root Beer is pretty much deprecated.
But if it only detects BusyBox - make sure you use BB module, not a rooted BB app
 

Attachments

  • Screenshot_2022-09-27-19-26-57-515_com.godevelopers.OprekCek.jpg
    Screenshot_2022-09-27-19-26-57-515_com.godevelopers.OprekCek.jpg
    295.2 KB · Views: 42
Last edited:

73sydney

Senior Member
Who can tell me how to fix these errors?

@zgfg has covered this before

and using search terms Hide My Applist or HMA would have gotten you here with a little clicking


you can get a 100% pass on all but Momo (we tend to ignore it, if not call it pointless or worse here) but doing as suggested - create a blacklist with root and lsposed/xposed modules, and then apply it to any "detector" apps. also important is to force stop, then clear data on those detector apps before testing again each time as they can cache previous results....failure to do this last step can send you in hours of circular disappointment :)
 

73sydney

Senior Member
@m0han

Heres one that had me scratching my head, and i know @m0han mentioned it before

I noticed i was getting a red on Oprek for custom recovery files, and im like "but i haz no TWRP folder on my internal memory!"

Tonigth i figured it out with a bit of basic detective work....

at adb shell on pc, because daddy likes his 32" Odyssey G7 over a 6.5" phone screen:

y2s:/data # find / -iname "TWRP" 2> /dev/null

/mnt/runtime/full/emulated/TWRP
/mnt/runtime/write/emulated/TWRP
/mnt/runtime/read/emulated/TWRP
/mnt/runtime/default/emulated/TWRP
/mnt/pass_through/0/emulated/TWRP
/data/media/TWRP
/dev/lS2qb/.magisk/mirror/data/media/TWRP

how is it ive never looked in here before?

delete the /data/media/TWRP folder and all is goodness again in Oprek...

Anyways the lesson:

To avoid:

1) if you are in TWRP, and you flash the magisk.apk as a zip, before you reboot, go to file manager and delete the TWRP folder there

OR

2) navigate to /data/media with a file manager in booted system and delete TWRP there

Afterwards doing:

y2s:/data # find / -iname "TWRP" 2> /dev/null

will return a big fat blank.....as i suspect magisk wont have mounted/mirrored it...

seems a bit obvious now...you know...with hindsight....
 
Last edited:
  • Like
Reactions: ipdev and m0han

kugamu

Member
Sep 27, 2022
9
7
All those apps must be in DenyList

For Oprek use additionally Hide My Applist (LSPosed module) to hide Magisk app and all LSPosed modules (HMA itself including)- there have been guides here how to setup.
See the screenshot.
Same works for TB Checker

From Momo you will probably never fully hide root - somebody else could give you some hints

Root Beer is pretty much deprecated.
But if it only detects BusyBox - make sure you use BB module, not a rooted BB app
When I install the BusyBox-ndk-master module I get an error
 

Attachments

  • 1664308296705.png
    1664308296705.png
    125.2 KB · Views: 41

kugamu

Member
Sep 27, 2022
9
7
All those apps must be in DenyList

For Oprek use additionally Hide My Applist (LSPosed module) to hide Magisk app and all LSPosed modules (HMA itself including)- there have been guides here how to setup.
See the screenshot.
Same works for TB Checker

From Momo you will probably never fully hide root - somebody else could give you some hints

Root Beer is pretty much deprecated.
But if it only detects BusyBox - make sure you use BB module, not a rooted BB app
I did everything as you said, but these errors are still there
 

Attachments

  • 1664309076672.png
    1664309076672.png
    204.4 KB · Views: 43

kugamu

Member
Sep 27, 2022
9
7
@zgfg has covered this before

and using search terms Hide My Applist or HMA would have gotten you here with a little clicking


you can get a 100% pass on all but Momo (we tend to ignore it, if not call it pointless or worse here) but doing as suggested - create a blacklist with root and lsposed/xposed modules, and then apply it to any "detector" apps. also important is to force stop, then clear data on those detector apps before testing again each time as they can cache previous results....failure to do this last step can send you in hours of circular disappointment :)
I am from Ukraine and do not know English well, so I communicate through an interpreter and it makes it a lot harder to find information
 

73sydney

Senior Member
I am from Ukraine and do not know English well, so I communicate through an interpreter and it makes it a lot harder to find information

I understand completely, i have to use Firefox Addon to translate some russian android sites all the time, so something like this may make things easier, you can use it to translate an entire page or from a highlighted section of text via the right click menu


And without getting too political (actually impossible not to) as a former infantry soldier, know theres plenty of us here in Australia would come to help if we could. The Ukrainian people have really shown their courage and determination, and may there be peace for you soon.
 
Last edited:

kugamu

Member
Sep 27, 2022
9
7
I understand completely, i have to use Firefox Addon to translate some russian android sites all the time, so something like this may make things easier, you can use it to translate an entire page or from a highlighted section of text via right click


And without getting too political (actually impossible not to) as a former infantry soldier, know theres plenty of us here in Australia would come to help if we could. The Ukrainian people have really shown their courage and determination, and may there be peace for you soon.
Thank you for your help and thank you for your kind words.
 

73sydney

Senior Member
When I install the BusyBox-ndk-master module I get an error

if you see -master at the end of a file that means its a zip of the master code of a github repository and NOT the correct magisk module zip file, and its contents arent arranged correctly, leading to the error you see

Usually you would get the correct file from the Releases page on a repository, but there hasnt even been that on that repo as his module was distributed via the magisk repository and via the Magisk Manager. that system has been ended - though replaced with a standalone app here (install the apk from under Assets):


Once installed, you can search for magisk modules to install and maintain them using this app

For now, to speed things up, im attaching the correct file to this post
 

Attachments

  • Busybox_for_Android_NDK-1.34.1(13412) (Magisk Module).zip
    9.4 MB · Views: 17
Last edited:
  • Like
Reactions: ipdev and pndwal

kugamu

Member
Sep 27, 2022
9
7
if you see -master at the end of a file that means its a zip of the master code of a github repository and NOT the correct magisk module zip file, and its contents arent arranged correctly, leading to the error you see

Usually you would get the correct file from the Releases page on a repository, but there hasnt even been that on that repo as his module was distributed via the magisk repository and via the Magisk Manager. that system has been ended - though replaced with a standalone app here (install the apk from under Assets):


Once installed, you can search for magisk modules to install and maintain them using this app

For now, to speed things up, im attaching the correct file to this post
I had this apk file installed and the busybox module from it also gave me an error, but the module you sent me worked
Thank you so much!
 
  • Like
Reactions: 73sydney

kugamu

Member
Sep 27, 2022
9
7
But unfortunately the error remained even after installing the module
 

Attachments

  • 1664311773089.png
    1664311773089.png
    198.7 KB · Views: 51
  • 1664311781315.png
    1664311781315.png
    191.9 KB · Views: 52

73sydney

Senior Member
But unfortunately the error remained even after installing the module

Okay you only need one Busybox module, so disable (or uninstall) one of them

Also you should install this module (if you havent already)


and (almost certainly/usually) disable MagiskHide Props Config unless theres a specific reason you need it enabled

Also i havent tested Deny List Unmount in a while, but Shamiko is an alternative (disable Enforce Deny List in Magisk -> Settings if you try this - making sure to disable DenyList Unmount first)


and make sure you reboot after making any such changes

theres a lot of modules for basic root hiding that do similar things (sometimes in different ways), but you cant have them all installed or active at once....so you have to pick 1 or the other


you should probably also follow this thread, as its newer than the (legacy) magisk thread we're currently in, plus it also will have links to all the modules and latest info in the opening few posts:

 

kugamu

Member
Sep 27, 2022
9
7
I did everything as you said, but the errors are still the same
 

Attachments

  • 1664319733591.png
    1664319733591.png
    198.8 KB · Views: 43
  • 1664319765725.png
    1664319765725.png
    194 KB · Views: 42

pndwal

Senior Member
When I install the BusyBox-ndk-master module I get an error
FYI (& others):

Authors official releases are here:
https://forum.xda-developers.com/t/...tiple-devices-platforms.2239421/post-40409356

He (@osm0sis) has myriad useful tools, scripts, flashable zips...

For Busybox NDK, scroll to 3rd section, Flashable Installer Zips, and find Busybox Installer...

I did everything as you said, but the errors are still the same
Do you have Shamiko?... PW
 

73sydney

Senior Member

regularmen

Member
Feb 7, 2018
23
2
Hi guys, I have trouble setting up Password screen lock after using Swipe screen lock for a while. It's just doesn't work, when I set it up nothing happens, even it stays Swipe on it's settings. I'm running at Android 9 using Magisk 23 before but tried updating (and with no module at all) to Magisk 25 and it still doesn't work.

Ye had same issue on my old device. Flashing magisk would break lockscreen and if u set lockscreen it would stay say Swipe. You'll get bootloop if you reboot your device too.

Is there by any chance that you have a Samsung J-series device?

It's not Samsung, It's a Nokia 5. no bootloop safe to say but It seems that you know something about this?

edit : I want to add, It used to be working. I used Password screen lock before using Swipe screen lock, in Magisk 23.
 

dope77

Senior Member
Aug 8, 2018
354
93
It's not Samsung, It's a Nokia 5. no bootloop safe to say but It seems that you know something about this?

edit : I want to add, It used to be working. I used Password screen lock before using Swipe screen lock, in Magisk 23.
How did this issue start? Did it happen after upgrading magisk? Or you've updated your rom?
 
  • Like
Reactions: J.Michael

Top Liked Posts

  • 1
    Good day everyone i have a problem in disabling my dm-verity using magisk, im trying to disable the dm-verity of my phone using magisk and after i flashed it i always ended up in bootloop it will only boot if the forcencryption option is enabled any solution how to solve this? Im still amatuer.


    Device name: Oppo A71 CPH1717
    Color Os: 3.1.0
    Android version: 7.1.1
    Magisk installed: Magisk 25.2 latest
    Bootloader unlocked
    When disabling forced encryption, you usually have to delete data or factory reset so a new, unencrypted data partition is created. At least that is what I had to do when I used it on older, Android 6 devices I used to have.
    1
    thank you for answering me sir, how am i going to factory data reset if im not able to boot up should i use stock recovery or twrp recovery?
    Yes, you can use the stock or twrp recovery to do the factory reset.
  • 8
    New Shamiko-v0.6(126)

    With this new Shamiko, Momo does no more detect Zygisk and Zygote (official latest Magisk Canary 25205, Zygisk enabled, DenyList configured and not enforced, Shamiko v0.6 in default black-list mode)
    7
    S-Check:

    Root detection, as on the screenshot

    I can pass with Delta but cannot with TJW Canary

    Delta:
    latest, Zygisk, MagiskHide, no Shamiko, App Data Isolation, HMA

    Canary:
    latest, Zygisk, DenyList, Shamiko, App Data Isolation, HMA, even with Magisk app uninstalled

    I have tested thoroughly on my two Xiaomi phones, one with A11 and the other with A12.
    Tested on both phones with Canary and with Delta - and I have the same results on both phones

    Not to mention that I fully pass Oprek, Ruru, TB-Checker, SafetyNet/Play Integrity
    Yup, Native bridge loading based on Maru Magisk fork implementation of Riru's loading method seems to have much merit...

    Nb. Original author says it's an experiment however, still not perfectly implemented and may be issues w/ some modules... Also Shamiko hiding with probably not work properly with this... Long read here for those interested:
    https://github.com/5ec1cff/my-notes/blob/master/maru.md

    For others, I put more here too:
    https://forum.xda-developers.com/t/...third-party-magisk-fork.4460555/post-87729841

    🙂 PW
    Worth pointing out that @zgfg asked me to test that on Magisk Canary (official) earlier but ive broken something it seems with my uber Samsung debloat and cant get S-check to even open anymore :)

    Anyone else care to chime in with Magisk Canary (official)
    I had that issue a while back, I do not remember what I did to fix it. :unsure:
    I just setup my Pixel 5a (it did not like updating from July to November 🙄) so clean flash. 😛

    No issues with Security Check. 🙂

    Pixel 6 - Stock Google 12L (July 2022).
    Pixel 5a - Stock Google 13 (November 2022).

    Magisk debug (snapshot)
    - Personal build from the official branch, so it includes the commits since the last canary/debug release.
    Magisk - [GitHub] - Building and Development

    USNF - Not the one that includes Displax's changes.
    - Personal test build that includes some other (mostly prop) changes.
    Fork - [GitHub] - commits
    One of these days I will have to pull Displax's Zygisk changes. 🙃

    MHPC
    - Set fingerprint back to stock Pixel 12.
    Pixel 6 is using the Pixel 6 12 print, 5a is using the 5a 12 print.

    Shamiko and LSPosed modules.

    HMA (Beta v3.0.5 r373)
    Two templates.
    Magisk
    - Settings (renamed Magisk app).
    - Hide My Applist.

    PlayStore
    - YouTube
    - YouTube Music​

    AdAway running in VPN (non-root) mode. ;)

    Cheers. :cowboy:
    7
    Just Curious
    Which command did you use to flash the patched_magisk...img with?
    1. fastboot flash init_boot magisk_patched...img
      or
    2. fastboot boot init_boot magisk_patched...img
    I think they both will work. :)
    Personally, unless booting an image is not an option..

    I always test boot the Magisk patched image using fastboot boot NameOfFile.img instead of flashing it.
    If it boots, Magisk will be active and I then use the Direct install option to make it permanent.
    If it does not boot, then no harm since the stock boot image is still installed. 🙃

    Cheers. :cowboy:
    6
    Personally, unless booting an image is not an option..

    I always test boot the Magisk patched image using fastboot boot NameOfFile.img instead of flashing it.
    If it boots, Magisk will be active and I then use the Direct install option to make it permanent.
    If it does not boot, then no harm since the stock boot image is still installed. 🙃

    Cheers. :cowboy:
    Some have said it's a waste of time to test by booting first, then direct installing because you can just flash the stock image back if it doesn't work.
    This maybe true, but directly flashing the patched image does NOT give Magisk the chance to back up the stock boot image, whereas booting then installing does.
    This makes it easier to take an OTA update on devices that require everything to be pure stock before proceeding by using Magisk's restore images function.
    6
    Hello everyone!

    Thank you for the very active thread i finally managed to figure out what i did wrong (yet again).

    I rarely tinker with the device, and when i am forced to, then i forget about A/B partitions, and wipe boot.img.

    I was hoping there is now another way for keeping TWRP and Magisk. Aside from embedding twrp image in stock boot, and than patching from magisk manager?

    Thank you.

    Also if someone more knowledgeable could help (even though it is slightly Offtopic), do i patch boot img with firmware boot img, or boot img from the custom rom i was using?

    Because that rom was then for testing (even though i kept it), and i can't figure out the version.
    I suspect when i run adb shell getprop "ro.product.version" it will probably fail, because i did a number on that device trying to fix it without understanding A/B partitions.
    Only if you don't have Recovery partition, then you patch TWRP to Boot (and afterwards the Magisk)

    (It's not necessarily specific to A/B devices - there are A/B devices that do have separated Boot and Recovery partitions, and in that case TWRP goes to Recovery partition, Magisk to Boot)

    But when you update Magisk, you can just take Direct Install (update)

    ---

    And of course, you must patch the boot.img corresponding to your current ROM. Usually, you can find it in the ROM zip file

    If you use some stock boot.img instead, then you risk the bootloop (of course, if boot img from your custom ROM coincides with the stock boot img then it doesn't matter, but usually it won't be the case - or you will not know

    That does not depend on Magisk - if the boot.img is wrong and you flash it (with or without Magisk) it will cause the bootloop (in the 'better' case, it may boot but you might have troubles later because of eg the wrong Kernel).
    Hence make sure to always use (for patching) the correct boot img
  • 1089
    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