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

Magisk General Support / Discussion

Search This thread

zgfg

Senior Member
Oct 10, 2016
6,080
3,580
You don't understand... I install Magisk from zip file by TWRP but Magisk Manager show me so i have no magisk installed. I tried install different versions of Magisk but Magisk Manager doesn't see any of it.
Classic. First thing, go to Apps drawer or Settings/Apps and look for your old Magisk mngr/app and uninstall that old one

If you previously did Hide Magisk app (mngr in the old case) to rename Magisk app/mngr (and to obfuscate it by renaming the package), then upon updating Magisk the new Magisk app cannot see Magisk app
 
  • Like
Reactions: J.Michael

pulpf

Member
Aug 25, 2011
21
3
OnePlus 7T
hello i think i read everything but it doesn't work
safetynet is failed.
the riru modules must all be installed? where are they found? i have a oneplus 7t
Oxygen os 1103.1
Screenshot_20211027-093852.jpg
 

zgfg

Senior Member
Oct 10, 2016
6,080
3,580
hello i think i read everything but it doesn't work
safetynet is failed.
the riru modules must all be installed? where are they found? i have a oneplus 7t
Oxygen os 1103.1View attachment 5442503
Generally, Riru cannot help you for SafetyNet. If you properly enabled Zygisk rebooted, Configured DenyList (GMS and GMS unstable), rebooted, you should pass SN.
If not, then you would need USNF and/or MHPC

As mentioned several times here, Riru is broken with Zygisk. And in your Canary, you need Zygisk for DenyList (hence for SN).
Therefore, if you really want Riru, you would need to switch to Alpha or Custom (many posts here how/where/what, etc) and use them as: Zygisk No, MagiskHide Yes (not the new DenyList)

And to avoid troubles when switching the Magisk flavour, better completely uninstall Magisk before you go
 

pndwal

Senior Member
With the latest update, I have a failure to connect mobile wifi, any solution ?.

my device redmi note 7. android 10, ROM stock.

I am attaching catlog, I hope you can see the error. thank you all for your time and effort, greetings.
Meaning Magisk Update, or Rom?

These symptoms are often an indication of mismatched boot image...

Did you take an OTA update and restore previously patched boot image, or perhaps updated Magisk but patched a boot image extracted from a ROM prior to an OTA update or other ROM entirely?... PW
 

pndwal

Senior Member
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
Pretty funny Dev asks "what's new?", then user provides translation (above) of Dev's Changelog as answer...

I doubt that's what Dev meant by "I also want to know!" (Translated) 🤪 PW
 
  • Like
Reactions: jons99

zaczatowany

Senior Member
Jun 25, 2010
91
15
Classic. First thing, go to Apps drawer or Settings/Apps and look for your old Magisk mngr/app and uninstall that old one

If you previously did Hide Magisk app (mngr in the old case) to rename Magisk app/mngr (and to obfuscate it by renaming the package), then upon updating Magisk the new Magisk app cannot see Magisk app
Now Magisk Manager show Magisk version but... my buttons on bottom disappeared. And Magisk Manager show me a strange version number to update. And i can't to update Magisk to v23. After i install zip file from TWRP MM still show me v22.1
 

Attachments

  • Screenshot_20211027-123026.jpg
    Screenshot_20211027-123026.jpg
    290.8 KB · Views: 61

zgfg

Senior Member
Oct 10, 2016
6,080
3,580
Now Magisk Manager show Magisk version but... my buttons on bottom disappeared. And Magisk Manager show me a strange version number to update. And i can't to update Magisk to v23. After i install zip file from TWRP MM still show me v22.1
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
 
  • Like
Reactions: J.Michael

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
I just want to instal stable 23 version. And i download zip file, install this zip file by TWRP but MM still show me old version 22.1. And i can't install any modules because the module, log, etc, buttons from bottom of the screen disappeared.

I have no buttons on bottom, just look at the SS. Root Checker shows my phone is no rooted...
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
6,080
3,580
I just want to instal stable 23 version. And i download zip file, install this zip file by TWRP but MM still show me old version 22.1. And i can't install any modules because the module, log, etc, buttons from bottom of the screen disappeared.

I have no buttons on bottom, just look at the SS.
It has been discussed here many times, with the new Magisk there is no more Modules repo in the app. You must download all your modules manually (link for Repo was also given previously here)

There is also no more SafetyNet checker n the app. And there is no more MagiskHide but DenyList where you must know how to manually enable GMS to pass SN (all was also described more than once here).
Please be prepare for that, if you didn't follow all discussions here, do the homework and get ready to go along by yourself with all those news and changes

If you still want to install that new Magisk Canary, take Uninstall Magisk to uninstall your old v22.1

Since you have troubles with flashing through TWRP, use the method as recommend on MagisknGithub: install Canary 23010 apk, patch the image and flash it through Fastboot (instructions are on Github and it was also discussed here numerous times)
 

m0han

Senior Member
Apr 30, 2012
4,484
1,630
... tested also MagiskCustom... with Zygisk No and MagiskHide Yes. Modules:
- Riru
- Riru-LSPosed (GravityBox-R)
- Riru-Momohider
i refer to screenshot 5.jpg in your post above. i have almost the same setup as you. yet, magisk detector reports that 'su file exists in path'. how can i resolve this? i have just installed Momo hider module. any further configuration required? i'm running the latest magisk alpha.
 

Attachments

  • Screenshot_20211027-165446_Magisk.png
    Screenshot_20211027-165446_Magisk.png
    142.1 KB · Views: 83
  • Screenshot_20211027-165502_Magisk.png
    Screenshot_20211027-165502_Magisk.png
    170.7 KB · Views: 85
  • Screenshot_20211027-165510_Magisk.png
    Screenshot_20211027-165510_Magisk.png
    196.8 KB · Views: 80
  • Screenshot_20211027-165526_Magisk.png
    Screenshot_20211027-165526_Magisk.png
    208.8 KB · Views: 74
  • Screenshot_20211027-165626_RootBeer_Sample.png
    Screenshot_20211027-165626_RootBeer_Sample.png
    148.7 KB · Views: 66
  • Screenshot_20211027-165546_Magisk.png
    Screenshot_20211027-165546_Magisk.png
    193.8 KB · Views: 60
  • Screenshot_20211027-165552_Magisk.png
    Screenshot_20211027-165552_Magisk.png
    169 KB · Views: 57
  • Screenshot_20211027-165609_YASNAC.png
    Screenshot_20211027-165609_YASNAC.png
    148.7 KB · Views: 60
  • Screenshot_20211027-165658_Magisk_Detector.png
    Screenshot_20211027-165658_Magisk_Detector.png
    134.8 KB · Views: 81
  • Like
Reactions: duttyend

pndwal

Senior Member
I just want to instal stable 23 version. And i download zip file, install this zip file by TWRP but MM still show me old version 22.1. And i can't install any modules because the module, log, etc, buttons from bottom of the screen disappeared.

I have no buttons on bottom, just look at the SS. Root Checker shows my phone is no rooted...
Screenshot showing Magisk not installed, so no bottom menu...

Edit: [Seems you may have a previous manager /app installed causing conflict (can't see Magisk/root). Have you searched settings / apps for that as previously described?]

Actually, seems TWRP might be the issue, and ruined previous root... (This is a common problem and reason John depreciated Custom Recovery installation method...)

If you can restore previous old root (backups?) you should be able to update from app using Direct Install...

With existing old root ensure Magisk App is restored first (not hidden), then uninstall the Magisk App, download the late version (APK) you want, install app, update within app (direct install)...

If you can't restore you should do as @zgfg advised above. PW
 
Last edited:
  • Like
Reactions: J.Michael

zgfg

Senior Member
Oct 10, 2016
6,080
3,580
i refer to screenshot 5.jpg in your post above. i have almost the same setup as you. yet, magisk detector reports that 'su file exists in path'. how can i resolve this? i have just installed Momo hider module. any further configuration required? i'm running the latest magisk alpha.
To hide su from the path, you need isolated option. On the Momohider Github page you have instructions
 
  • Like
Reactions: J.Michael and m0han

lokopol

Senior Member
Jul 16, 2013
463
1,264
¿Significa actualización de Magisk o Rom?

Estos síntomas suelen ser un indicio de que la imagen de inicio no coincide ...

¿Tomó una actualización de OTA y restauró la imagen de arranque previamente parcheada, o quizás actualizó Magisk pero parcheó una imagen de arranque extraída de una ROM antes de una actualización de OTA u otra ROM por completo? ... PW

Meaning Magisk Update, or Rom?

These symptoms are often an indication of mismatched boot image...

Did you take an OTA update and restore previously patched boot image, or perhaps updated Magisk but patched a boot image extracted from a ROM prior to an OTA update or other ROM entirely?... PW
thanks for answering. no, my stock ROM worked fine, it was with the magisk update when the wifi connection stopped working.
 
  • Like
Reactions: J.Michael

Dwightsch

Member
May 9, 2020
7
4
Okay @topjohnwu you're probably sick of the "sell out" stuff and just flaming over the changes in magisk in this new direction you're taking this great project since your employment at Google. I totally agree with you. I think devs and apps and... Should have the option to "opt out" of any modification. but riddle me this, when I have some banking app, some other system app or whatever and that has nothing to do with the modifications I have using root, should they force me to unroot my phone? It's their choice that I shouldn't mess with their app but is it theirs to demand I either choose banking or modifications to other parts of my phone? My point being, if it's at all possible, consider adding Deny list functionality for system apps because currently it doesn't work on any and Hide options for apps that force you to either choose magisk or their app, regardless of what you're modifying. You can factor out any app or service that Google runs but a "choice" for users to bypass detection and modification for apps and services that insist you don't root android and enforce that whether by themselves or using Google services, would be great and probably in sprit of your current decisions.
Other than that, cheers and thanks.
I hope you stay strong and healthy.
 
Last edited:

abagm

Member
Jun 22, 2018
6
0
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?
 

Top Liked Posts

  • 3
    Anyone seen Happy Momo before?

    Hiding Zygisk may be possible! 😀 ...

    View attachment 5472595

    Translated:
    "The environment is normal, no changes to the environment have been found"

    Seems Shamico may be the answer, but early days... (according to this user / dev: nu11ptr)

    I know nothing about anime, Manga, demon-girl characters etc, and this may or may not be relavent:


    https://machikado-mazoku.fandom.com/wiki/Momo_Chiyoda

    Anyway, looks like a genuine POC FWIW.

    🤪 😝 PW 😋

    ... So we now have proper hide-for-Zygisk test released to public!

    It's Shamiko-v0.1.1-40-debug.zip

    Translated;
    LSPosed:

    Shamiko Preview

    Simple hide based on zygisk.

    Configure inheritance denylist. After installing Shamiko, configure denylist and close denylist, Shamiko will automatically take over and hide.

    Theory supports Android 8.1+, but only tested on 11

    You need to use the version of magisk after this pr: https://github.com/topjohnwu/Magisk/pull/5010

    So need to wait for that PR to be merged, or build Magisk from
    https://github.com/LSPosed/Magisk/tree/xhookclear
    to try. PW
    1
    Gotta be impressed with some of John's observations / mathematical mind (which we all apparently have... somewhere...).
    John Wu, Dec 3

    US: 12022021
    Asia: 20211202
    EU: 02122021

    Only for today, EU is wrong

    Me, I didn't initially see it... Took the word 'palindrome' to kick-start my math's brain... 🤪

    Bit late, but Happy No-Palindrome Day Europe!

    Sorry if OT, but this has gotta be relavent to Magisk development... no? PW
  • 34
    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​
    Project Link
    Zygisk
    No​
    Yes​
    Yes​
    Yes​
    DenyList
    No​
    Yes​
    Yes​
    No​
    MagiskHide
    Yes​
    No​
    Yes*​
    Yes​
    Modules Repo
    Yes​
    No​
    No​
    Yes​
    Download Link

    *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
  • 1070
    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