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

Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
Which of the things doesn't match the others?
To my great delight, I discovered a ROM for Samsung S5e (kminilte) with Android 9. Runs great - just can't get Magisk to work. Have tried alpha, Hitman's and JohnWu's new releases. Neither with TWRP nor with the direct patch of the boot.img (and flash via download mode) I get further - the flashing stops with every method when repacking the bootimage, without anything being flashed/patched. Do I have to mount anything manually or so? Honestly, I do not get through meanwhile - is there somewhere a working guide, which system requirements, which flash method and which other requirements should be given? Here in the thread I have bravely read along - as far as I know, I have also tried all the instructions, but no Magisk was installed. I do not need SNP, only ROOT and Hiding Root and the ExSD card module. I'm not sure, but I had the impression that Zygisk (first two alpha versions up to ...31 I could still completely flash via TWRP) brings my device into bootloop /freezing. Should we users (who do not have their own dev skills) rather wait until there is any beta or use an old Magisk classic or have I overlooked / not understood something essential?
Yup - you need to read / follow official Installation Instruction linked from Magisk home page; pay special attention to Samsung section... 😁 PW
 
  • Like
Reactions: J.Michael

m0han

Senior Member
Apr 30, 2012
4,478
1,629

Attachments

  • Screenshot_20211027-180206_Magisk_Detector.png
    Screenshot_20211027-180206_Magisk_Detector.png
    124 KB · Views: 76
  • Screenshot_20211027-180037_MiXplorer.png
    Screenshot_20211027-180037_MiXplorer.png
    94.9 KB · Views: 77
  • Screenshot_20211027-180236_Magisk_Detector.png
    Screenshot_20211027-180236_Magisk_Detector.png
    119.3 KB · Views: 75
  • Like
Reactions: zgfg

pndwal

Senior Member
Latest Canary Magisk

Magisk (ea75a09f) (23011)

• Make Zygisk survive zygote restarts
• Fix crashes when Magisk environment was not properly setup. This will fix the crashes experienced after installing Magisk with patching boot images.

Diffs to v23.0

• [General] MagiskHide is removed from Magisk
• [General] Support 64-bit only systems
• [General] Support Android 12
• [Zygisk] Introduce new feature: Zygisk
• [Zygisk] Introduce DenyList feature to revert Magisk features in user selected processes
• [MagiskBoot] Support patching 32-bit kernel zImages
• [MagiskBoot] Support boot image header v4
• [MagiskInit] Support /proc/bootconfig for loading boot configurations
• [MagiskInit] Better support for some Meizu devices
• [MagiskInit] Better support for some Oppo/Realme devices
• [MagiskSU] Use isolated devpts if the kernel supports it
• [resetprop] Deleted properties are now wiped from memory instead of just unlinking
• [App] Build a single APK for all ABIs

[App] Switch to use standard bottom navigation bar

[App] Downloading modules within the Magisk app is removed

👍 PW
 

pndwal

Senior Member
got it. many thanks. had to run setenforce 1 to get the 3rd screenshot.
Nb. There may be issues with isolated as per GitHub page for module. - it is deprecated and replaced by setns (need isolated + setns). Without Zygisk you should be able enable all options. In Alpha with Zygisk + Riru co-existing, only isolated & initrc work. PW
 

rodken

Senior Member
Jan 11, 2010
641
185
Google Pixel XL
OnePlus 8
new alpha is out and working fineView attachment 5442539
Changelog:

- Fixed magiskd may crash
- Support Zygote restart
- Fixed CWD process across namespace in isolated namespace mode
- Improve deny list loading
- Use Traditional Search list in deny list
According to your screenshot, you might want to toggle your 'Update Channel' so that the current version matches the latest.

There is a newer alpha version released as of this writing?
 

Attachments

  • Screenshot_20211027-092842.jpg
    Screenshot_20211027-092842.jpg
    379.7 KB · Views: 60
Last edited:

zgfg

Senior Member
Oct 10, 2016
6,063
3,564
Nb. There may be issues with isolated as per GitHub page for module. - it is deprecated and replaced by setns (need isolated + setns). Without Zygisk you should be able enable all options. In Alpha with Zygisk + Riru co-existing, only isolated & initrc work. PW
With or without setns I have no difference. For me only isolated works (hiding su from the path)

With setns but without isolated - su is visible again in the path

Sticking with isolated - it worked to me with all flavours and Magisk versions (of course, without Zygisk and with Riru)
 

Attachments

  • IMG_20211027_152929.jpg
    IMG_20211027_152929.jpg
    290.1 KB · Views: 47
Last edited:

Makishima

Senior Member
Jun 3, 2013
258
42
Xiaomi Mi A3
Google Pixel 4a
I'm on the latest Magisk Canary released a few hours ago, I see people putting Google Play gms and so on on the denylist yet I can't see it listed. Do you do it via terminal? And if so, how? Or are you using a different version of Magisk?
 

Eng.Raman

Senior Member
Apr 13, 2014
409
464
Khanaqin
I'm on the latest Magisk Canary released a few hours ago, I see people putting Google Play gms and so on on the denylist yet I can't see it listed. Do you do it via terminal? And if so, how? Or are you using a different version of Magisk?
Magisk → Settings → Configure DenyList → Search icon → Show system apps → Search for gms in Filter by name.
 

Makishima

Senior Member
Jun 3, 2013
258
42
Xiaomi Mi A3
Google Pixel 4a
Magisk → Settings → Configure DenyList → Search icon → Show system apps → Search for gms in Filter by name.
Oh... I had already done that but I thought it found nothing. Turns out Play Services was hidden right beneath the search bar. Okay, so I 'deny' gms and gms.unstable right? Also, is it okay to hide the Magisk app with the latest update? Because it kept crashing half an hour ago and had to uninstall and reflash.
 
  • Like
Reactions: Eng.Raman

zaczatowany

Senior Member
Jun 25, 2010
91
15
Sorry, I dont understand what is that - it shows that you have Manager and Magisk, some old version v22.1?!

What do you really want to install, Stable 23000 or latest Canary 23010, or else?

Please, if you are really wanting to experiment with the latest Canary, be aware that you might have problems with SafetyNet, banking aps, etc - is it really neccessary for you and did you folloew and understand (to further apply what would you need) all changes brought by Zygisk, DenyList, etc
Sorry, my english not so good to do homework and understand all the posts.... I just want to install Magisk v23 and recover root in my phone. But some crazy things do with my phone. I tried many times to install Magisk-23.zip in TWRP but Magisk Manager still doesn't see any magisk installed or old version 22.1. I have no option to uninstall this... what i have to do? please...
 

Qnorsten

Senior Member
Mar 14, 2012
192
86
Do anyone know what can trigger ART parameters are abnormal in momo?
I have one app that seem to detect root no matter what I do, so I temporarily moved over to magisk alpha to try and use old magisk hide, Riru and Riru-momohider. To try and make momo don't detect root and see if that fixed the app, before I start decompiling the app to figure out what sort of root detection it does.

Update: the cause for art parameters are abnormal, was lsposed. Disabled lsposed and now momo are happy. Didn't fix my other app though, so back to drawing board I guess.

Screenshot_20211027-161357.jpg
 
Last edited:

Eng.Raman

Senior Member
Apr 13, 2014
409
464
Khanaqin
With setns but without isolated - su is visible again in the path
setns works only when the config isolated is enabled ( i.e: It can't be configured without isolated ), referring to the momohider github page.

Sticking with isolated - it worked to me with all flavours and Magisk versions (of course, without Zygisk and with Riru)
All the 4 configs worked for me in both magisk custom and alpha but i only need ( isolated+setns+initrc ).
 

zgfg

Senior Member
Oct 10, 2016
6,063
3,564
setns works only when the config isolated is enabled ( i.e: It can't be configured without isolated ), referring to the momohider github page.


All the 4 configs worked for me in both magisk custom and alpha but i only need ( isolated+setns+initrc ).
With isolated I kill su and obtain as on the screenshot

What additional do you get with setns?

Please be aware that init rc modifications detection or not is not reliable
 

Attachments

  • IMG_20211027_152929.jpg
    IMG_20211027_152929.jpg
    290.1 KB · Views: 37

zgfg

Senior Member
Oct 10, 2016
6,063
3,564
setns works only when the config isolated is enabled ( i.e: It can't be configured without isolated ), referring to the momohider github page.


All the 4 configs worked for me in both magisk custom and alpha but i only need ( isolated+setns+initrc ).
For me the filling was (already on two occasions, with varios Magisk versions) that the phone becomes less fluid with setns
 

abagm

Member
Jun 22, 2018
6
0
Yup - you need to read / follow official Installation Instruction linked from Magisk home page; pay special attention to Samsung section... 😁 PW
Thank you for your quick answer! I Just -mmmh - I am not on stock, I am running a Custom Rom; to flash all AP files means being forced to flash all the other stock rom files - as far as I understand the installation guide. Are you sure? I tried different apk and different zip - only the old magisk23 apk did finiish (direct method and patching img), no other apk did manage that. Maybe the attached logs are clearer than me to show the difference. I can get Magisk classic, AND i would like to understand WHY it fails to run everything POST-magisk classic
 

Attachments

  • magisk_install_log_2021-10-27T18:35:17Z.log
    2.1 KB · Views: 3
  • magisk_install_log_2021-10-27T18:18:41Z.log
    1.7 KB · Views: 1
Last edited:

Top Liked Posts

  • 16
    I've been following the thread for a long time now, and I think some users are still confused regarding the differences between the different variants of Magisk that are available for use. I'm going to try and summarize them here, which should be helpful for everyone:

    Magisk Variant​
    Stable​
    Canary​
    Alpha​
    Custom​
    Release​
    Official​
    Official​
    Unofficial​
    Unofficial​
    Maintainer​
    topjohnwu​
    topjohnwu​
    vvb2060​
    TheHitMan7​
    Zygisk​
    No​
    Yes​
    Yes​
    Yes​
    DenyList​
    No​
    Yes​
    Yes​
    No​
    MagiskHide​
    Yes​
    No​
    Yes*​
    Yes​
    Modules Repo​
    Yes​
    No​
    No​
    Yes​

    *If you turn off Zygisk in Alpha, then DenyList will act like MagiskHide. So essentially, you can have Zygisk On + DenyList or Zygisk Off + DenyList running as MagiskHide.

    In case I've gotten something wrong, or can add more information, please let me know. :) Cheers!
    5
    I've been following the thread for a long time now, and I think some users are still confused regarding the differences between the different variants of Magisk that are available for use. I'm going to try and summarize them here, which should be helpful for everyone:

    Magisk Variant​
    Stable​
    Canary​
    Alpha​
    Custom​
    Release​
    Official​
    Official​
    Unofficial​
    Unofficial​
    Maintainer​
    topjohnwu​
    topjohnwu​
    vvb2060​
    TheHitMan7​
    Zygisk​
    No​
    Yes​
    Yes​
    Yes​
    DenyList​
    No​
    Yes​
    Yes​
    No​
    MagiskHide​
    Yes​
    No​
    Yes*​
    Yes​
    Modules Repo​
    Yes​
    No​
    No​
    Yes​

    *If you turn off Zygisk in Alpha, then DenyList will act like MagiskHide. So essentially, you can have Zygisk On + DenyList or Zygisk Off + DenyList running as MagiskHide.

    In case I've gotten something wrong, or can add more information, please let me know. :) Cheers!
    Kudos to you for doing this. This thread has become very fragmented with all the different versions of Magisk being discussed in this one thread. I can't imagine being a new user (or even an experienced one) and coming in here and trying to figure out what is what, what does what, etc., especially given the OP can't be revised unless John does it. Even trying to figure out what version someone is talking about in a given post can be difficult at times I would imagine. I'm sure this table will be very helpful to many. 👍
    4
    I've been following the thread for a long time now, and I think some users are still confused regarding the differences between the different variants of Magisk that are available for use. I'm going to try and summarize them here, which should be helpful for everyone:

    Magisk Variant​
    Stable​
    Canary​
    Alpha​
    Custom​
    Release​
    Official​
    Official​
    Unofficial​
    Unofficial​
    Maintainer​
    topjohnwu​
    topjohnwu​
    vvb2060​
    TheHitMan7​
    Zygisk​
    No​
    Yes​
    Yes​
    Yes​
    DenyList​
    No​
    Yes​
    Yes​
    Yes^​
    MagiskHide​
    Yes​
    No​
    Yes*​
    Yes​
    Modules Repo​
    Yes​
    No​
    No​
    Yes​

    * If you turn off Zygisk in Alpha, then DenyList will act like MagiskHide. So essentially, you can have Zygisk On + DenyList or Zygisk Off + DenyList running as MagiskHide.
    ^ DenyList depends on Zygisk being enabled. So if you turn off Zygisk in Custom, DenyList will also stop working.

    In case I've gotten something wrong, or can add more information, please let me know. :) Cheers!
    AFAIK, there is no DenyList in Custom. Only MagiskHide without or with Zygisk
    3
    AFAIK, there is no DenyList in Custom. Only MagiskHide without or with Zygisk
    Thanks! Post updated. (y)
    3
    is it about the same magisk?
    What does that mean?

    What is or not the same Magisk - sorry be precise, cannot guess what you think or not?!

    Canary channel is (and always was) official prereleases from TJW, creator and maintainer of Magisk (Stable).
    Big changes are already rolling in Canary, hence it is not (functionally) the same as the old Stable.
    There are already tons of posts here in the thread about what is new in the Canary and how to use - there are also posts with ChangeLogs - please read, be familiar, this is not TG channel and please don't expect that somebody will waste the time to repeat all the same things to every newcomer

    There are also two spun-offs, Magisk Alpha and Magisk Custom - they are based on the new Canary but with some differences (making them more or less similsr to the old Magisk Stable).
    Again, please go back, find and read the posts about, tons of ink was already spent on, several users posted questions, answers, opinions, links to their Github pages and TG channels for download, discussion about, etc
  • 16
    I've been following the thread for a long time now, and I think some users are still confused regarding the differences between the different variants of Magisk that are available for use. I'm going to try and summarize them here, which should be helpful for everyone:

    Magisk Variant​
    Stable​
    Canary​
    Alpha​
    Custom​
    Release​
    Official​
    Official​
    Unofficial​
    Unofficial​
    Maintainer​
    topjohnwu​
    topjohnwu​
    vvb2060​
    TheHitMan7​
    Zygisk​
    No​
    Yes​
    Yes​
    Yes​
    DenyList​
    No​
    Yes​
    Yes​
    No​
    MagiskHide​
    Yes​
    No​
    Yes*​
    Yes​
    Modules Repo​
    Yes​
    No​
    No​
    Yes​

    *If you turn off Zygisk in Alpha, then DenyList will act like MagiskHide. So essentially, you can have Zygisk On + DenyList or Zygisk Off + DenyList running as MagiskHide.

    In case I've gotten something wrong, or can add more information, please let me know. :) Cheers!
    14
    For those who use Alpha or new Canary and miss the old Modules Repo:

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

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

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

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

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

    ---

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

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

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

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

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

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


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

    Hope it helps more than confuse. 🙃

    Cheers. :cowboy:
    12
    Hi all. :D

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

    Seemed to be appropriate to mention here.

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

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

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

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

    Cheers all. :cowboy:
    10
    Gents, as grateful I am for all above substantial contributions I hope you allow me to express my "wonder"... As you all know off-topic posts (unless violating forum rules) are only removed on request of the threadowner, I'm just surprised that extremely experienced and knowledgable XDA users allow this thread to deviate from its subject.
    Just as an idea for similar "occasions" in future, hadn't it been better to simply point somebody to the well known subject matter related ad blocker threads? Okay, unexperienced members should certainly question themselves why they post off-topic in a thread. After the initial serious problems with the in-XDA-search, I meanwhile must say it's working excellent for me.

    And by the way: I've removed the link to paid applications as not being accepted on XDA. Please don't mind.

    Regards
    Oswald Boelcke
    Senior Moderator
  • 1069
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    156
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    The Flash
    Forum Moderator

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

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

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

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

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