Magisk General Support / Discussion

Search This thread

jons99

Senior Member
Nov 5, 2019
242
289
Thanks, no I used fastboot command , this is the PC name folder where I moved the image patched.
This step is mandatory, because I moved with the PC the image patched
View attachment 5521607
In need helps for this step, I should rename the magisk patched image?
View attachment 5521609
Where I unchecked Recovery mode option?
Thanks
no need to rename. open your platform tools folder in that folder open powershell type fastboot boot and drag and drop the boot img file then press enter.
tho this will only boot that img if you want to flash it you need to write fastboot flash boot then drag and drop
 
  • Like
Reactions: An68

zxxz0x0

Member
Jan 24, 2022
19
1
That is the point: I think you installed the new app without first uninstalling the old app.

There is no "hidden root". "Hide Magisk app" does not hide root. It hides the Magisk app.
The bank application does not work again in V23 when it is impossible to create "Hide The Magisk App" whether Magisk Hide is hiding the banking application. Another error I met at V24 is not possible to denylist Google Play Service when installing Modul SafetyNet-Fix. That makes me unable to pass Safety Net and use the bank application.
 

zgfg

Senior Member
Oct 10, 2016
7,346
4,744
The bank application does not work again in V23 when it is impossible to create "Hide The Magisk App" whether Magisk Hide is hiding the banking application. Another error I met at V24 is not possible to denylist Google Play Service when installing Modul SafetyNet-Fix. That makes me unable to pass Safety Net and use the bank application.
If you don't need Magisk app on a daily basis, you can uninstall the app (not Magisk)

All modules, root grants, MagiskHide (since you are on v23) will continue to work

Only when you need, you install that same Magisk v23 app (keep the apk handy), you will install the app, grant a new root, manage modules, sonething and uninstall the app again
 
  • Like
Reactions: J.Michael

zxxz0x0

Member
Jan 24, 2022
19
1
If you don't need Magisk app on a daily basis, you can uninstall the app (not Magisk)

All modules, root grants, MagiskHide (since you are on v23) will continue to work

Only when you need, you install that same Magisk v23 app (keep the apk handy), you will install the app, grant a new root, manage modules, sonething and uninstall the app again
I need root to work but also need to hide root bank and game app. I tried to remove and reinstall Magisk many times even reinstall ROMs but encountered errors in V23 as above. It was 3am but I still hope to try to overcome tomorrow not affecting the job
 

zgfg

Senior Member
Oct 10, 2016
7,346
4,744
I need root to work but also need to hide root bank and game app. I tried to remove and reinstall Magisk many times even reinstall ROMs but encountered errors in V23 as above. It was 3am but I still hope to try to overcome tomorrow not affecting the job
I'm not talking about uninstalling Magisk

When Magisk app is uninstalled, then it is better hidden then if you just hide it - isn't it?

I wrote about uninstalling Magisk app - read my previoud post carefully again, and again, and again if needed

If you don't distinguish Magisk from, then why Magisk app separately describes the version of MAGISK installed, and bellow the version of MAGISK APP installed
 
  • Like
Reactions: J.Michael

zxxz0x0

Member
Jan 24, 2022
19
1
Sorry for my English is not good, can misunderstand what you say. I cannot removed and reset the application or Magisk because it takes a lot of time and those applications need to run parallel to each other
I'm not talking about uninstalling Magisk

When Magisk app is uninstalled, then it is better hidden then if you just hide it - isn't it?

I wrote about uninstalling Magisk app - read my previoud post carefully again, and again, and again if needed

If you don't distinguish Magisk from, then why Magisk app separately describes the version of MAGISK installed, and bellow the version of MAGISK APP installed
 

zgfg

Senior Member
Oct 10, 2016
7,346
4,744
Sorry for my English is not good, can misunderstand what you say. I cannot removed and reset the application or Magisk because it takes a lot of time and those applications need to run parallel to each other
Phone Settings, Apps, find Magisk app and Uninstall it there

Just that, DO NOT DO anything else
 

Attachments

  • IMG_20220128_210323.jpg
    IMG_20220128_210323.jpg
    252.8 KB · Views: 56
  • Like
Reactions: J.Michael

zgfg

Senior Member
Oct 10, 2016
7,346
4,744
I can distinguish Magisk and Magisk Manager. Uninstalling Magisk Manger can hide root?
You complained that for Magisk v23 you cannot do "Hide Magisk app", didn't you

I'm telling you that instead of "Hide Magisk app" you uninstall Magisk app

Magisk app = Magisk manager - it is not Magisk

Of course, before you uninstall Magisk app (call it Magisk Manager if you like), fully setup your Magisk v23 - all modules, root grants, MagiskHide
 
  • Like
Reactions: J.Michael

zxxz0x0

Member
Jan 24, 2022
19
1
You complained that for Magisk v23 you cannot do "Hide Magisk app", didn't you

I'm telling you that instead of "Hide Magisk app" you uninstall Magisk app

Magisk app = Magisk manager - it is not Magisk

Of course, before you uninstall Magisk app (call it Magisk Manager if you like), fully setup your Magisk v23 - all modules, root grants, MagiskHide
Safetynet pass , magisk hide on , magisk app delete , bank app still detected
 

zgfg

Senior Member
Oct 10, 2016
7,346
4,744
Safetynet pass , magisk hide on , magisk app delete , bank app still detected
Then it's something else, banking apps get smarter and smarter to detect or guess about rooting

But believe me, if it detects now, it would also detect if you kept Magisk app installefd but just did "Hide Magisk app".
Bcs, the app is NOW UNINSTALLED, not just HIDDEN (some banking apps detect even hudden Magisk app)

It's not about finding Magisk app

Go to Magisk Github, read Wiki, there is a section with tricks how banking apps may detect 'root' and hints how you try to beat them:
 
Last edited:
  • Like
Reactions: J.Michael

zxxz0x0

Member
Jan 24, 2022
19
1
Then it's something else, banking apps get smarter and smarter to detect or guess about rooting

But believe me, if it detects now, it would also detect if you kept Magisk app installefd but just did "Hide Magisk app".
Bcs, the app is NOW UNINSTALLED, not just HIDDEN (some banking apps detect even hudden Magisk app)

It's not about finding Magisk app

Go to Magisk Github, read Wiki, there is a section with tricks how banking apps may detect 'root' and hints how you try to beat them:
I tried on the V24 with Zygisk Denylist + USNF as you guide another post or follow Youtube. Yasnac Pass SafetyNet But Other App (Safynet Test) Failed with Error (Cant Access Google Play Service). Banking still doesn't work. I do not use a lot of bank applications because I have many devices but I'm frequently used to check Magisk Hide operations. Before V24 officially released everything to operate normally. I am not specializing in phone so only focus on V23 version research . Thank you for guiding new users like me
 

Mr Wolf

Senior Member
Aug 1, 2011
69
5
Hi, I have a Xiaomi Redmi 5 Plus with Resurrection Remix OS RR-O-v6.2.1-20181003-vince-Final.
I've just updated to Magisk 24.1 from 23.0 and now, when I boot the phone, I get this message from the Trust Platform:
This build has been signed with public keys

I've never seen this message before. I've googled a bit, but I can't understand well what it means and why it has appeared only know, and, most of all, if it can be safely ignored.
 

silver2004

Senior Member
Feb 10, 2017
92
18
Cool, LG v35 on LineageOS 18.1, Ramdisk (Yes)
update 23.0 -> 24.1 went without any problems :)
Both app&Magisk
I will miss the repo though :(
 
  • Like
Reactions: zgfg

Top Liked Posts

  • 1
    Please those of you who have Magisk v25, test the following:

    - open Terminal

    - do not execute su
    (do not go as root/superuser)

    - test:
    which su

    Since you did not request (and were not granted root privileges), you must not be able to see su in the path

    But with Magisk v25 it returns:
    system/bin/su

    and that makes it trivial.for an app to detect that the phone is rooted

    See the screenshot
    Wasn't it always this way? How else would the shell find `su` when you try to run it?
    What if you add `terminal` to your deny list?
    1
    Wasn't it always this way? How else would the shell find `su` when you try to run it?
    What if you add `terminal` to your deny list?
    See the screnshots from Momo

    And Momo is in DenyList
    1
    On RN8T w/ A10 MIUI stock & 25101, which su gives /sbin/su, but my Momo isn't showing 'Found executable su in the path'...

    For me it's 'init.rc is modified' and 'Found zygisk' that have returned...

    View attachment 5647419
    PW
    You should use which -a su to see all the directories in your path containing su, not just the first one.
    1
    Test with Magisk v25.1:

    - open Terminal

    - do not execute su
    (do not go as root/superuser)

    - test:
    which su

    With Magisk Canary 25101 it returns for me:
    system/bin/su
    @zgfg @pndwal

    How does hiding root work?
    When target app on hidelist / denylist is opened, Magisk will immediately unmount Magisk tmpfs mountpoint, dummy skeleton tmpfs and magisk created mount bind so there are no /sbin/su or /system/bin/su (Android 11+) in target apps.

    See the source code:
    Denylist unmount: zygisk/deny/revert.cpp
    MagiskHide: magiskhide/hide_policy.cpp

    Momo is abusing isolated process and app zygote process to bypass MagiskHide and detect Magisk. And the fact that not all banking apps use isolated process or app zygote.
    1
    You should use which -a su to see all the directories in your path containing su, not just the first one.
    ... Just did what @zgfg did for his comparison... However w/ -a, same result:
    IMG_20220628_114406.jpg

    PW
  • 10
    Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

    Magisk (bf04fa13) (24314)​

    • [App] Fix language switch
    • [MagiskSU] Handle system_server restarts to prevent UID reuse abuse

    Diffs to v24.3​

    • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
    • [MagiskInit] Introduce new sepolicy injection mechanism
    • [MagiskInit] Support Oculus Go
    • [MagiskInit] Support Android 13 GKIs (Pixel 6)
    • [MagiskBoot] Fix vbmeta extraction implementation
    • [App] [MagiskSU] Properly support apps using shared UID
    • [MagiskSU] Fix a possible crash in magiskd
    • [MagiskSU] Prune unused UIDs as soon as possible to prevent UID reuse attacks
    • [MagiskSU] Verify and enforce the installed Magisk app's certificate to match the distributor's signature
    • [MagiskSU] Handle system_server restarts to prevent UID reuse abuse
    • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
    • [DenyList] Fix DenyList on shared UID apps
    • [BusyBox] Add workaround for devices running old kernels
    https://github.com/topjohnwu/magisk-files/blob/4cc20a9dfb66ddd96b88499c0f4fffeee357afe8/notes.md

    👍 PW
    9
    Latest Official TJW Beta (release) Magisk build:

    Magisk

    2022.6.7 Magisk v25.0​

    Another major release! A lot of the changes aren’t visible at the surface, but v25 is actually a really substantial upgrade!

    MagiskInit Rewrite​

    A significant portion of magiskinit (the critical software that runs before your device boots up) is completely rewritten from scratch. Ever since Android introduced Project Treble in Android 8.0, Magisk has been constantly fighting against the increasingly complex partitioning and early mount setups of all kinds of devices, sometimes with weird OEM specific implementations. It got to a point that magiskinit had become so complicated that few people (including myself!) were aware of every detail, and maintaining this piece of software like this was clearly not sustainable. After many months of planning (yes, this whole re-architecture has been in my head for a long time) and some help from external contributors, a whole new sepolicy injection mechanism is introduced into Magisk, solving the “SELinux Problem” once and for all.

    Since this is a full paradigm shift on how Magisk hot-patch the device at boot, several behaviors that many developers implicitly relied on might not exist. For example, Magisk no longer patches fstabs in most scenarios, which means AVB will remain intact; some custom kernels rely on AVB being stripped out for them by Magisk.

    MagiskSU Security Enhancements​

    The superuser functionality of Magisk has not seen much changes ever since its introduction. v25 focuses on making root permission management more accurate and secure:

    • Add a whole new package tracking system to ensure malicious UID reuse attack cannot be performed
    • Properly support and implement the UX in the Magisk app for packages using sharedUserId
    • Enforce root manager APK signature verification to combat the rampant unofficial Magisk app “mods”
    Many might not realize, but using a trusted, unmodified Magisk app is really important. Magisk’s root daemon treats the Magisk app differently and gives it blanket root access without any restrictions. A modded Magisk app can potentially backdoor your device.

    And in case some of you are about to put on your tin foil hats, this is not designed to “vendor lock-in”; the goal is to make sure your root management app comes from the same developer of the underlying root implementation. Magisk’s build system allows custom distributors to use its own signing keys, and in addition, I am also providing official debug builds which skips any signature verification for development.

    Full Changelog: here

    Magisk Changelog​

    v25.0​

    • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
    • [MagiskInit] Introduce new sepolicy injection mechanism
    • [MagiskInit] Support Oculus Go
    • [MagiskInit] Support Android 13 GKIs (Pixel 6)
    • [MagiskBoot] Fix vbmeta extraction implementation
    • [App] Fix stub app on older Android versions
    • [App] [MagiskSU] Properly support apps using sharedUserId
    • [MagiskSU] Fix a possible crash in magiskd
    • [MagiskSU] Prune unused UIDs as soon as system_server restarts to prevent UID reuse attacks
    • [MagiskSU] Verify and enforce the installed Magisk app’s certificate to match the distributor’s signature
    • [MagiskSU] [Zygisk] Proper package management and detection
    • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
    • [Zygisk] Fix Zygisk’s self code unloading implementation
    • [DenyList] Fix DenyList on shared UID apps
    • [BusyBox] Add workaround for devices running old kernels
    https://topjohnwu.github.io/Magisk/releases/25000.html

    🎉🎉 👍 PW
    7
    Latest Official TJW public Stable (release) Magisk build:

    Magisk

    Magisk Changelog​

    v25.1​

    • [MagiskBoot] Fix ramdisk backup being incorrectly skipped
    • [MagiskBoot] Add new feature to detect unsupported dtb and abort during installation
    • [Zygisk] Change binary hijack paths
    • [App] Fix incorrect recovery mode detection and installation
    • [MagiskInit] Fix config not properly exported in legacy SAR devices
    • [General] Enforce the Magisk app to always match or be newer than magiskd

    Release Notes:
    https://topjohnwu.github.io/Magisk/releases/25100.html

    For remaining diffs to public Stable 24.3, see Changelog for public Beta 25.0:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86993241

    🎉🎉 👍 PW
    6
    Thank you @zgfg and @ipdev . I have a fully working and automated script to both update my phone and patch & flash the magisk boot.img file. The only thing thats missing is the autoreboot after sideload but i guess TWRP has to implement this feature.

    The script can both be used as standalone or class to modify it for custom stuff. Ill continue to work on the repo and make everything neat, as well as working on windows and linux binarys & a gui for people that have no idea how to use scripts.

    Thank you guys for your help, this will save so much time for me and maybe even other people (at least i hope it will be used). :)

    Here it is on github
    6
    Latest Official TJW Canary (release) & Debug (debug) Magisk builds:

    Magisk (34b2f525) (24316)​

    • [App] Fix stub app on older Android versions

    Diffs to v24.3​

    • [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
    • [MagiskInit] Introduce new sepolicy injection mechanism
    • [MagiskInit] Support Oculus Go
    • [MagiskInit] Support Android 13 GKIs (Pixel 6)
    • [MagiskBoot] Fix vbmeta extraction implementation
    • [App] [MagiskSU] Properly support apps using shared UID
    • [App] Fix stub app on older Android versions
    • [MagiskSU] Fix a possible crash in magiskd
    • [MagiskSU] Prune unused UIDs as soon as possible to prevent UID reuse attacks
    • [MagiskSU] Verify and enforce the installed Magisk app's certificate to match the distributor's signature
    • [MagiskSU] Handle system_server restarts to prevent UID reuse abuse
    • [MagiskSU] [Zygisk] Proper package management and detection
    • [Zygisk] Fix function hooking on devices running Android 12 with old kernels
    • [Zygisk] Fix Zygisk's self code unloading implementation
    • [DenyList] Fix DenyList on shared UID apps
    • [BusyBox] Add workaround for devices running old kernels
    https://github.com/topjohnwu/magisk-files/blob/b4869a2d900721c508c974e5288edf29aee25e01/notes.md

    👍 PW
  • 1080
    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