Magisk General Support / Discussion

Search This thread

Macmoc16

Senior Member
Oct 30, 2016
270
40
when I flasho magisk 15.1, on my oneplus one with linage 15.1 it goes into bootloop. During the installation it seems to be all right, a part of this:
! Installed root system detected, mount rw :(

Despite having worked a wipe system and checking with root checker, and it fails. I do not know what to do, I do not understand what is the error even trying a flash unistall magisk, the device does not share the same saying that magisk is not installed. Sorry if I was wrong but I did not know where to write it and I did not find anything about it. Thanks in advance to those who friend me :)
 

Josey Wales

Senior Member
Jul 29, 2013
399
85
South Florida
Latest MM v5.5.2 and Magisk v15.1 update will NOT open MM at all. . . "Magisk Manager has stopped working" error.

I cannot open MM, no log generated. . . I tried flashing MM uninstaller in TWRP but failed WTF, first time for everything?!

Galaxy Note 5
Stock rooted 7.0


Sent from my SM-N920T using Tapatalk
 
Last edited:

NiTrOwow

Senior Member
Jul 20, 2010
203
57
Almost the same thing happened to me, went to update to 15.1 and SafetyNet failed and it said it was actually uninstalled, but rebooting my phone it went back to normal. Even Chase Pay works now.

I have updated my post. My problem with SafetyNet dissapeared after doing ;

  1. Go to Magisk Manager
  2. Hit Uninstall > "Complete uninstall"
  3. Reboot 2 times (first reboot crashed or was canceled?!)
  4. Install v15.0 by TWRP
  5. Open Magisk Manager again after installing v15.0
  6. Update from Magisk Manager to v15.1
  7. Reboot
  8. Now SafetyNet passes.

I assume that something went wrong on the updating process from v15.0 to v15.1.
Not sure what happened but it works now.
 

Floodland

Senior Member
Aug 29, 2011
644
387
Buenos Aires
A question to understand a little better: what triggers /data encryption even it was clean, without encryption and working fine? I know magisk write to /data, but the partition is not encrypted at that point (if installed from recovery at least), but when Android boots. I know there must be a reason, but I see it unnecessary, risky and harmful...
 

Simone98RC

Senior Member
Jun 21, 2013
400
158
25
Reggio Calabria
simonealecci.it
Magisk v15.1 has damaged dm-verity

Just tonight I've upgraded to Magisk v15.1.
Premise: I own a Oneplus 3 with OxygenOS OB28.

The SafetyNet check failed, so I tried to both reinstall OxygenOS OB28 with Magisk itself.
The result for a long while was an unbootable device with the dm-verity warning at every boot (even in recovery mode).

Until I decided, as partial workaround, to reinstall Magisk v15.0 and v15.1 in that order, then wipe cache and reboot.
The dm-verity screen is still shown, but device now boot properly.
@topjohnwu please note that, according to recovery output, only Magisk v15.0 recognizes properly dm-verity and try to patch fstab.

Probably (I've no free time to try), by reinstalling only Magisk v15.0, the dm-verity screen might disappear.
The dm-verity error persists even by reinstalling firmware, even by installing Magisk v15.0, even by upgrading to Magisk v15.2.
It means I've to lock and unlock bootloader, to fix them... but I prefer to think there's an easier solution.
 
Last edited:
  • Like
Reactions: Anova's Origin

jhill110

Senior Member
Oct 12, 2012
1,919
1,372
Santa Barbara
Samsung Galaxy Tab S8
Ok! Update to 15.1 from 14.0 worked!
Updated through MM 5.5.2 and my Galaxy Tab s2 stock rooted Nougat is working as it should now.
I spent a lot of time trying to get 15.0 going with no luck so this is great!

Thanks @topjohnwu for the work you and your testers have done. :cowboy::cowboy::cowboy:
 
Last edited:

Vinnom

Senior Member
Jun 21, 2012
1,705
1,143
Campinas
Xiaomi Poco F1
when I flasho magisk 15.1, on my oneplus one with linage 15.1 it goes into bootloop. During the installation it seems to be all right, a part of this:
! Installed root system detected, mount rw :(

Despite having worked a wipe system and checking with root checker, and it fails. I do not know what to do, I do not understand what is the error even trying a flash unistall magisk, the device does not share the same saying that magisk is not installed. Sorry if I was wrong but I did not know where to write it and I did not find anything about it. Thanks in advance to those who friend me :)
Google for osmose unSu. Flash it before flashing magisk.

This probably occur because you didn't clear LOS built-in su.

HUAWEI NOVA user since 12/2016 =)
---Current ROM: AospExtended
---Kernel:stock
MOTO X user since 03/2015 =)
---Current ROM: Tesla N
---Kernel: Tesla N stock
NEXUS 4 user 2013-2015 =/

Kernel Adiutor Interactive profile: INTERACTIVE
Kernel Adiutor Intelliactive profile: INTELLIACTIVE
Kernel Adiutor Intellimm profile: INTELLIMM
Kernel Adiutor Smartmax profile: SMARTMAX
 

jackieku

Senior Member
Aug 20, 2012
72
37
v15.1: magiskinit: Segmentation fault

I noticed that sepolicy injection tool was moved from magisk to magiskinit after updated from v14 to v15.1.
However, when I attempt to execute magiskinit command in a root shell it always crashes immediately, with any arguments that I think it should accept.

I tried,
Code:
# /data/magisk/magiskinit
# /data/magisk/magiskinit --help
# /data/magisk/magiskinit magiskpolicy --live 'allow kernel system_block_device blk_file read'
# /data/magisk/magiskinit supolicy --live 'allow kernel system_block_device blk_file read'

This is the log of the crash:
Code:
--------- beginning of kernel
12-29 11:40:47.322     0     0 I magiskinit[5874]: unhandled level 2 translation fault (11) at 0x00000018, esr 0x92000006
12-29 11:40:47.322     0     0 F         : pgd = ffffffc01dc7b000
12-29 11:40:47.322     0     0 F         : [00000018] *pgd=00000000b127c003, *pmd=0000000000000000
12-29 11:40:47.322     0     0 W         : CPU: 1 PID: 5874 Comm: magiskinit Tainted: G        W    3.10.103-g5e329b33dbe #1
12-29 11:40:47.322     0     0 W task    : ffffffc02a2eeb80 ti: ffffffc028084000 task.ti: ffffffc028084000
12-29 11:40:47.322     0     0 W         : PC is at 0x455808
12-29 11:40:47.322     0     0 W         : LR is at 0x45369c
12-29 11:40:47.322     0     0 W pc      : [<0000000000455808>] lr : [<000000000045369c>] pstate: 60000000
12-29 11:40:47.322     0     0 W sp      : 0000007fca7426f0
12-29 11:40:47.322     0     0 W         : x29: 0000007fca7426f0 x28: 0000000000000004
12-29 11:40:47.322     0     0 W         : x27: 0000000000000003 x26: 00000000ffffffff
12-29 11:40:47.322     0     0 W         : x25: 0000007fca7427f8 x24: 00000000004cd000
12-29 11:40:47.322     0     0 W         : x23: 000000000048e858 x22: 0000000000000000
12-29 11:40:47.322     0     0 W         : x21: 00000000004934d8 x20: 0000000000000000
12-29 11:40:47.322     0     0 W         : x19: 0000000000000018 x18: 00000000004f3e08
12-29 11:40:47.322     0     0 W         : x17: 0000000000000000 x16: 00000000004f3000
12-29 11:40:47.322     0     0 W         : x15: ffffffffffffffff x14: 00000000004f3000
12-29 11:40:47.322     0     0 W         : x13: ffffffffffffffff x12: 0000000000000023
12-29 11:40:47.322     0     0 W         : x11: 0000000000000003 x10: 0101010101010101
12-29 11:40:47.322     0     0 W         : x9 : 7f7f7f7f7f7f7f7f x8 : 0000000000000050
12-29 11:40:47.322     0     0 W         : x7 : 6163686e71636d60 x6 : 12050d0230000a0b
12-29 11:40:47.322     0     0 W         : x5 : 0b0a0030020d0512 x4 : 0000000000000000
12-29 11:40:47.322     0     0 W         : x3 : f35a6d9a85b1755d x2 : 0000000000000000
12-29 11:40:47.322     0     0 W         : x1 : 00000000004f0d60 x0 : 0000000000000018

This is a Nexus 9 LTE that is running RR nougat ROM.
I need to inject a policy to get swap on loopback device working, please help!
 
Last edited:

Vinnom

Senior Member
Jun 21, 2012
1,705
1,143
Campinas
Xiaomi Poco F1
Magisk Manager Version: 5.5.1(82)
Magisk Version: 15.0
Device: Huawei Nova
Rom: LOS 14.1

Hi! When I try to install a module, I get the following:
Code:
- Copying zip to temp directory
- Installing Module(any module).zip
- Mounting /system, /vendor, /data, /cache
! Magisk is not activated!
Failed!
! Installation failed

The behaviour above can be verified in install_logs attached.
I installed Magisk through recovery, after using the addon to unsu LOS (which has its own su). The installation was pretty ok. I had just clear flashed the ROM.

I captured a logcat too, probably it will be needed.
Just as complementary information, this occured with magisk 14.0 too, as I also tried (I clea flashed ROM so I could have a clean environment to flash 15v).

PS: I split it the logcat in beginning_of_system, beginning of crash and logcat_magisk_module_install. Size reasons. I don't know if everything will be needed, but it better to send a full logcat.

EDIT:
I forgot to mention that flashing module through recovery gave me a similar output (something like that magisk is needed and not found)
After updating to:
Magisk Manager Version : 5.5.2
Magisk Version: 15.1

This still occurs

HUAWEI NOVA user since 12/2016 =)
---Current ROM: AospExtended
---Kernel:stock
MOTO X user since 03/2015 =)
---Current ROM: Tesla N
---Kernel: Tesla N stock
NEXUS 4 user 2013-2015 =/

Kernel Adiutor Interactive profile: INTERACTIVE
Kernel Adiutor Intelliactive profile: INTELLIACTIVE
Kernel Adiutor Intellimm profile: INTELLIMM
Kernel Adiutor Smartmax profile: SMARTMAX
 

OreoCupcakes

Member
Nov 16, 2017
11
1
After updating to 15.1 my phone lost forced-encryption even though I had the box checked to keep it. Now my phone automatically decrypts on boot into recovery and brings me straight to the lock screen.
Device: OnePlus 3T (OOS 4.5.1)
 

SeishiNui18

Member
Apr 19, 2016
25
5
Updated to Magisk Manager 5.5.2, tried to update from v14 to v15.1 through it shows success but after reboot still stays with v14. I tried:

Complete uninstall, run latest uninstaller through TWRP then restored stock boot.img. Reboot back to TWRP to patch v14 again, reboot to system and installed MM 5.5.2 directly. Check SafetyNet and all good. Update through MM to v15.1 is successful but after reboot still stays with v14. Flashed v15.1 in TWRP and no bootloop plus SafetyNet passes.
 

Sir Backe

Senior Member
Apr 14, 2012
171
31
If by code you mean "Contract number", I can get to it just fine.

Magisk v15.0, Manager v5.5.1, the app added to the Hide list and the Manager hidden (there's an option for that in the Manager settings).

Hi Didgeridoohan,
Thanks really a lot for your efforts. Yes I meant contract code. I do not arrive there due to whatever reasons. The app recognizes root before. So at the moment I don't know what more I should ask. Since it works on your phone it must be a problem of mine. But where to search? What to do else? I don't know.
I also tried hiding the manager already before. It also didn't work.
Anyhow Tks really a lot, I appreciate your efforts. If you have any further idea what I could try, just let me know.
 
Mar 16, 2017
27
3
São Paulo
Hello everyone. Until version 14, the app worked perfectly for me, with no problem whatsoever, but in version 15 the "hide" function stopped working, with applications detecting root normally. I went back to version 14 and it worked again. I have now updated to version 15.1 and the problem persists, the "hide" not working. Has anything changed in this sense? What do I need to do to fix this? Appreciate.
 

ahse0w

Senior Member
Feb 14, 2012
220
36
I just came here to report v15 causing screen crashes on my nexus 5x on latest 8.1 (it becomes total a graphical hangup), but this right here makes me think that f.lux and magisk might not be playing nice together anymore. I've moved back to v14 and that fixes the issue as well.

I am on the Nexus 6P. Trying out the Qualcomm option rather than the composite option for color filtering.
Seems like i am not the only one.
 

Fild5x

Senior Member
Feb 2, 2016
1,191
192
During installation I see something like installation boot partition detected. Is that a big issue?
 

ahse0w

Senior Member
Feb 14, 2012
220
36
Damn! Having trouble with Magisk Manager 5.5.1, and toyed with the idea that Lux is, once more, causing issues. 15 installed OK under 542, updated to 551, crashes at opening the app.

Sent from my XT1254 using Tapatalk

Are you crashing at the opening of f.lux? My issue is with graphical hangups. Screen is working, but the actual graphics is screwed up.
Did you roll back to 542? Did it help?
 
Are you crashing at the opening of f.lux? My issue is with graphical hangups. Screen is working, but the actual graphics is screwed up.
Did you roll back to 542? Did it help?
Not exactly. Lux has been a conflict issue before, thought it was why 551 was crashing at opening. I did revert to 542 while the latest snafu played out. Turns out bad Magisk coding at fault, Lux was innocent. I'm fully updated now, although some minor coaxing was involved, nothing advanced.

Sent from my XT1254 using Tapatalk
 

nuxbag

Senior Member
Aug 19, 2009
520
49
Sliver Spring, MD
I have a Sprint Note 4 6.0.1 stock, I am not getting past the Sprint boot screen. With the new Masky 15.1 with the systemless modified xposed. It will boot without Xposed.

Sent from my SM-N910P using Tapatalk
 
Last edited:

SeishiNui18

Member
Apr 19, 2016
25
5
Hi Didgeridoohan,
Thanks really a lot for your efforts. Yes I meant contract code. I do not arrive there due to whatever reasons. The app recognizes root before. So at the moment I don't know what more I should ask. Since it works on your phone it must be a problem of mine. But where to search? What to do else? I don't know.
I also tried hiding the manager already before. It also didn't work.
Anyhow Tks really a lot, I appreciate your efforts. If you have any further idea what I could try, just let me know.

Try the new Manager 5.5.2 and Magisk v15.1, add the app on MagiskHide list then Settings and select to hide Manager which will repackage the Manager app. Tried your app and I can get to the contact number screen. I don't have xposed installed.
 

matuszp

Senior Member
Apr 14, 2014
135
25
Magisk v14 on stock LG G6.
I get notifications about new update but when I click on it nothing happens.
Same situation when I try to update directly from the app.
Nothing happens.
Any clue how to fix it?

Wysłane z mojego LG-H870 przy użyciu Tapatalka
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    I can't access superuser and modules they are both lockedView attachment 6081641
    Your phone isn't rooted! The top section of your screenshot shows Magisk "Installed N/A".
    Installing the Magisk app isn't enough to root your phone.
    4
    I have always have problems with magisk and bug reports think I have even failed with the debug version lol, although its closed I have added that the bug is not present with the debug version
    Just open another with "version code: 27002" somewhere in first post, explain you tested both but issue is with Canary only, not Debug... Supply logs from broken build and wait for further instructions from Devs... Template requires the version code (or bot closes) + logs (or Devs will often close with comment like "no log no fix")...👍 PW

    Edit: Someone opened proper issue following template just now:
    https://github.com/topjohnwu/Magisk/issues/7921

    Looks to me like this commit has issues:

    Always update stub APK when upgrade

    committed5 days ago
    4
    Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
    Not pushed yet... Looks like recent Android Gradle plugin upgrade just didn't build properly... Guess a new build may come once Upgrade AGP is reverted but may not happen till AGP upgrade is redone. 🤪 PW
    4
    Latest canary Update 27002 will not let me hide the Magisk app, get a failed toast, tried opening an issue but need to use the debug version,
    Installed the debug version and it works and hides the magisk app?
    4
    Not sure if the fix has been pushed yet but looking at GitHub it's been sorted
    Not pushed yet according to my magisk app.
    Luckily i don't hide or need to hide; this is a sad bug and i hope, for others' sake, it's pushed as soon as the developers can. But that's also why it's canary and not beta or release, it's why (or should be why) we use canary, to squash bugs before the rest experience them.
  • 1103
    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