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

Magisk General Support / Discussion

Search This thread

Goncalo29

Senior Member
May 10, 2014
95
24
I'm facing a little problem. I can't hide the Magisk Manager by changing its name. So some apps detect I have rooted my phone (eg Mcdonald's), even if I hide them with MagiskHide.

I'm using the last version (20.4)
 

razrielsch

Member
Aug 11, 2013
23
3
boot loop after magisk 21.0 was installed via twrp

Hi,
i installed the new 21.0 version via TWRP but now my S5 mini stucks in a boot loop.
Is that know and know someone a way to step out of this ?

looks like the vol+ home pwr button doesnt step into TWRP

razri
 

wbercha

Senior Member
Aug 25, 2013
79
8
Xiaomi Poco X3 Pro
Guys, i am unable to install one of my banking app, i have hidden magisk and everything and when i go to google play store it says this app is not compatible with this device anymore. Please help because i have been searching a lot fot it and still no luck.
 

pote2639

Senior Member
Jan 3, 2012
209
27
Goddamnit, can you for once just focus on stability and not some silly UI change? After since I upgraded my manager to the new ones I can't open my old hide magisk manager anymore.
 
Last edited:

BillAdama

Member
Feb 11, 2014
17
1
Hi
I'm having some troubles rooting my Pixel 4a. I unlocked it and I flashed the rooted boot image with success (I think) but Magisk Manager at "Installed" says N/A.
I already tried with flashing the stock image and restarting from scratch, locking and unlocking again the bootloader and also using Magisk Canary.
What can I do? Can you please help me? I used the boot image found here.
Is there a way to check if the boot image is really rooted?
 

dope77

Senior Member
Aug 8, 2018
310
68
Unable to use banking apps
Root detected?
Help
Using Migisk 21

Did you enable magisk hide from the settings?
Did you hide root from the banking app?
Also try repackaging the manager, sometimes it help hide root detection

---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------

Hi
I'm having some troubles rooting my Pixel 4a. I unlocked it and I flashed the rooted boot image with success (I think) but Magisk Manager at "Installed" says N/A.
I already tried with flashing the stock image and restarting from scratch, locking and unlocking again the bootloader and also using Magisk Canary.
What can I do? Can you please help me? I used the boot image found here.
Is there a way to check if the boot image is really rooted?


Not sure about your case, but on some devices (like mine) magisk would partially work or would be completely blocked due to some security in the kernel. You might have to flash a custom kernel to be able to root your device.
 

pndwal

Senior Member
Goddamnit, can you for once just focus on stability and not some silly UI change? After since I upgraded my manager to the new ones I can't open my old hide magisk manager anymore.
Actually, compatibility, hiding etc are pretty much what John does concentrate on.

Viktor (@diareuse) did / does the UI overhaul / maintenance for a number of not-silly reasons.

Moreover, this UI is no (recent) change for many users here as it's been around since January in Canary builds (although it's only recently hit Public Stable/Beta).
Most of the time however, other aspects of Magisk Manager development felt like a chore: I would rather spend time and effort on improving Magisk’s compatibility, more hiding capabilities, and more features, but not on struggling to create even the simplest UI element in the app that took me way too much time...

This is when diareuse approached me, willing to help redesigning the app, but most importantly, with source code!

New Magisk Manager Maintainer

Diareuse works as a full time Android app developer, and his skill really shows: I learned tons of new stuffs ever since his involvement in development back in last April. The first thing we agreed on doing is first rewrite and modernize the mess of code that was Magisk Manager...

Despite the initial skirmishes, diareuse is surprisingly determined and passionate to continue. We stroke a balance to collaborate, and his familiarity with the unusual nature of Magisk Manager made further development much smoother, so together we agreed on letting him do what he initially wanted: a full redesign, starting late September last year.

This redesign branch is now officially merged into master and pushed to canary for beta testing. Mixed feedback was received, but no worries for those critical of the new UI, we’ll definitely continue to work on improvements as this design is nowhere near final yet! However, a full revert will never happen. Diareuse and I do this by volunteer in our free time, and we do not have the capacity of maintaining 2 completely different UI design.

Diareuse is officially the main maintainer of Magisk Manager. I will continue to work on the core functionality code, but everything you can visually see in the app is and will be written by him in the foreseeable future...
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post83637567

Nb. Custom mods like TWRP are languishing (this is still incompatible with devices shipping Android 10 w/ no accross-the-model-range solution in sight), whereas Magisk, which is still pretty much a 2 man operation, still gets fixes constantly, is adapted to a plethora of new Android architectures as they emerge, and is compatible with every Android OS since... way way back:
John Wu
Sept 13

Managed to get in-app theme switching in Magisk Manager work on Android 4.2 LOL. The app is finally 100% functional on all supported API levels!
I reckon it's pretty good value for our money, even if we have to fight with inevitable problems if we take updates... Otherwise, 'if it ain't broke, don't fix it' I guess.

More Magisk history:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post83707709 PW
 
Last edited:

73sydney

Senior Member
Jul 21, 2018
1,848
1,602
Sydney
Google Pixel 2 XL
Actually, compatibility, hiding etc are pretty much what John does concentrate on.

Viktor (@diareuse) does / did the UI overhaul and maintenance for a number of not-silly reasons.

Moreover, this UI is no (recent) change for many users here as it's been around since January in Canary builds (although it's only recently hit Public Stable/Beta).

https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post83637567

Nb. Custom mods like TWRP are languishing (this is still incompatible with devices shipping Android 10 w/ no accross-the-model-range solution in sight), whereas Magisk, which still pretty much a 2 man operation, still gets fixes constantly, is adapted to a plethora of new Android architectures as they emerge, and is compatible with every Android OS since... way way back:

I reckon it's pretty good value for our money, even if we have to fight with inevitable problems if we update... Otherwise, 'if it ain't broke, don't fix it' I guess. PW

Are you in here, again, not causing grief but actually being helpful?

Its beginning to be a pattern with you :)
 

JudgeDread11

Senior Member
Aug 17, 2014
881
500
Ao Nang, Krabi
Goddamnit, can you for once just focus on stability and not some silly UI change? After since I upgraded my manager to the new ones I can't open my old hide magisk manager anymore.
Without showing respect not many will be willing to help you.
The 'new' UI had been available and tested for many months in the canary branch.
Problems you are experiencing are most likely specific to your device/setup.
So instead of cursing, being respectful and giving information about your setup and steps taken would more likely get you some help.

Everybody else, please provide more information.
Device, Android version, Magisk version, stable or canary, steps taken.
And even then logs might be needed to analyze your issue.
 

zgfg

Senior Member
Oct 10, 2016
5,721
3,174
Goddamnit, can you for once just focus on stability and not some silly UI change? After since I upgraded my manager to the new ones I can't open my old hide magisk manager anymore.
If you have a problem with Manager after upgrade (did not really understand what was your problem), follow what's been suggested to others similarly: uninstall Manager (not Magisk) and install from the apk again.
Not sure about 8.0.2 but for Canary it worked
 

BillAdama

Member
Feb 11, 2014
17
1
Did you enable magisk hide from the settings?
Did you hide root from the banking app?
Also try repackaging the manager, sometimes it help hide root detection

---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------




Not sure about your case, but on some devices (like mine) magisk would partially work or would be completely blocked due to some security in the kernel. You might have to flash a custom kernel to be able to root your device.

I followed the guide here on xda and it doesn't say to flash a custom kernel. I'm not sure if I made something wrong have I got any way to check? Like dumping the boot image from the phone and checking it with md5\sha256?
 

FOREST37

Member
Nov 30, 2014
21
0
I followed the guide here on xda and it doesn't say to flash a custom kernel. I'm not sure if I made something wrong have I got any way to check? Like dumping the boot image from the phone and checking it with md5\sha256?

Forgive me asking the obvious = but have you actually tried using a file explorer to access System root to see if you can view restricted files - that would show whether you were rooted or not wouldnt it?
 

BillAdama

Member
Feb 11, 2014
17
1
Forgive me asking the obvious = but have you actually tried using a file explorer to access System root to see if you can view restricted files - that would show whether you were rooted or not wouldnt it?

Don't worry, I tried and I cannot access anything, I see only the folder structure under /system, no files or anything. Also X-plore it's not prompting for root access nor Root checker.
 

zgfg

Senior Member
Oct 10, 2016
5,721
3,174
Don't worry, I tried and I cannot access anything, I see only the folder structure under /system, no files or anything. Also X-plore it's not prompting for root access nor Root checker.
Delete explorer from MM Superuser - long tap and Revoke
For explorer, in Settings/Apps, Clear Data, and then try to open /system again

Btw, you can try with MiXPlorer
 

FOREST37

Member
Nov 30, 2014
21
0
I cannot even open the section for enabling Superuser in MM, it says that Magisk it's not installed.
I tried cleaning the Cache for MM but the situation is the same.

I'm not familiar with the Pixel - but is it a dual partition phone? Do you need to fastboot using a patched boot image and then install magisk using a patched boot image via the manager once the phone has rebooted? That's what I had to do with my Mi A2 Lite and when i do OTA updates I have to select reinstall to inactive slot post OTA reboot to retain root status.
 

BillAdama

Member
Feb 11, 2014
17
1
I'm not familiar with the Pixel - but is it a dual partition phone? Do you need to fastboot using a patched boot image and then install magisk using a patched boot image via the manager once the phone has rebooted? That's what I had to do with my Mi A2 Lite and when i do OTA updates I have to select reinstall to inactive slot post OTA reboot to retain root status.

Yes, it's an A/B device. You have to unlock it, flash the rooted boot image and then install Magisk Manager. Now I'm running on slot B, if I switch to slot A it doesn't boot.
 

Top Liked Posts

  • 10
    MOD ACTION:

    Enough is enough. Despite my deleting some off topic posts yesterday, the spam continues. Thread cleaned. Please check your PM inbox and avoid off topic posts.
    3
    This is based on John's repo.
    I am not sure if vvb2060's alpha build require Zygisk active for enabling DenyList.
    AFAICS it does, at least for now.

    I believe ptrace was used previously for this; new Magisk needs Zygisk; I don't think we'll have an option in future since all ptrace code is gone... unless it comes back. vvb2060 OP note re. this here:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85643797

    ... 'n please don't team up on me; my Android reflexes are abominably slow and I might just go sulk in the carpark... Marvin.
    3
    Need quick help with the installation instructions https://topjohnwu.github.io/Magisk/install.html

    Under "Patching Images" it says I need the boot.img (cause my OP 5T has RAM disk), but where can I download it?

    Thanks in advance

    Edit: I'm running lineage OS with microG
    From the LOS install zip file.
    Unzip that file, you should find a boot.img in there. That's what Magisk needs.
    If you have a boot.img.br file, just uncompress it first with brotli.
    2
    For those running vvb2060's alpha builds.

    You should be able to install any of the alpha builds over each other.
    The versionName is changing GitShortHead-alpha.
    The versionCode is remaining 23001.

    The versionCode is what triggers the upgrade/downgrade install.
    PackageManager only see that you are re-installing version 23001. ;)

    With that being said, you might run into a problem with magisk.db that was generated by an older/newer build.
    There was a very recent commit about this. (Currently the last commit on John's repo.)​
    Magisk - GitHub - commit - f7c0e40
    Also the last commit in vvb2060's repo currently.


    You might have an issues repacking a Magisk boot image.
    For testing purposes you should always use your ROM's stock boot image.
    Yes testing the updating logic is important but, you need a base line to compare.​
    A clean install may fail when an update succeeds and vice versa.

    Cheers all. :cowboy:
    Good to know, thx

    Hopefully, if I make a copy of /data/adb/magisk.db before trying the next Alpha, I will be able to restore the database if I would have to go back to b6298f86-alpha
    1
    Hi,

    Does snapchat work with the Magisk and corresponding modules for hiding? I've been out of rooting scene for long, so I don't know. The last time snapchat was able to detect it.

    Thanks.
  • 44
    OK. AIO solution. Modded "Universal SafetyNet Fix" module. Just added "model" props.
    17
    So, new layer of HARDWARE detection is here.
    SafetyNet failed on devices, where must bee HARDWARE detection. GMS no longer check system response of evaluation type, and force check HW. USNF doesn't work in this cause.
    Hm, funny things happening. I was thinking this is upgrade of HW attestation, but it is DOWNGRADE actually. 😄

    Remember my old first simple digging into HW?
    It`s..... working again.

    Looks like a temporary solution or just "combo" of old and new methods from Google.
    This explains the fact that dirty hack with Xposed-s working now.

    So, this current environment may be temporary or preparation for something BIGGER.

    In conclusion: in this time to passing SafetyNet you need just my old "hardware_off" module from link above or "MagiskHidePropsConf" with any "BASIC" print with model simulation and kdrag0n-s "Universal SafetyNet Fix".

    No ***-posed-s need!
    16
    Few Headsups:

    1) There are reports that Danny's (@kdrag0n) new early release Universal SafetyNet Fix 2.0.0 (combines AOSP Keystore and shim Keystore solutions) is restoring ctsProfile for some. It just may work for all, but not enough reports as yet. Also, it requires a payment at this stage:
    https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-85581909

    https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-904209677

    2) There are reports that simply using MagiskHide Props Config module to 'delete' ro.product.model prop fixes ctsProfile on custom ROMs where other methods have failed. Eg:
    https://github.com/kdrag0n/safetynet-fix/issues/78#issuecomment-912885628

    3) New MagiskHide Props Config module 6.0.0 just released with all the sensitive prop values that MagiskHide changed up to and including Magisk v23 set by default, "Force BASIC key attestation" re-enabled (for Googles latest changes), and various other fixes.
    https://forum.xda-developers.com/t/...p-edits-and-more-v6-0-0.3789228/post-85581939

    I have to agree that this module's name does suddenly seem very apt, and as always, it proves elegant in its versatility. 😛👍

    4) Another elegant solution that some may have relegated to a bygone era seems to be coming back in fashion to!

    Those with Google Pay problems persisting after fixing ctsProfile are reporting in GPay threads, here and elsewhere, that GPay-SQLite-Fix + SQLite binary modules from stylemessiah (a connoisseur at least in digital fashion ... or perhaps just lucky, our @73sydney, - original solution from @BostonDan ) is fixing these for them once again. 😜 Eg:
    https://github.com/kdrag0n/safetynet-fix/issues/78#issuecomment-912798412

    WOT 😉 to read if interested:
    https://forum.xda-developers.com/t/...s-of-gms-17-1-22-on-pie.3929950/post-79643248

    🤠 PW
    15
    ro.product.model was enough for my OP8T, but I didn't like how Google Play Services started referring to my device as "OnePlus BASIC" with the "hardware off" module, so I knocked together this module really quickly to just append _SN to the real model name. WFM. 🤘
    14
    Removed the @Displax safety net mod fix and applied the latest USNF 2.1.0 from @kdrag0n.

    Attestation is passed and device is compliant in company portal too with my original device name 1+8 Pro and not Pixel.

    This is done over the latest Alpha Magisk.

    Update: My In-display fingerprint hardware is not working anymore, I think the fix is already committed. Hopefully it will be resolved in the next version.
    Yep, I have sent a Pull Request with the fix like an hour after v2.1.0 was released. 🤠

    See my post here in the official USNF thread for getting it working in the meantime until it's merged and a new release is made: https://forum.xda-developers.com/t/...tynet-fix-1-1-0.4217823/page-59#post-85631613

    Also may be worth everyone reading my comments at the end of that post about people doubting the sponsored testing closed-then-open development.

    And then here on this GitHub issue about how it's not meant to replace MagiskHide so you can't just turn Hide off: https://github.com/kdrag0n/safetynet-fix/issues/91#issuecomment-919264624
  • 1062
    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