Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
Hi,

does somebody knows, how the german health insurance app "TK" does detect root?

My configuration:
LOS 19.1
Magisk 24.3 (app hidden),
Zygisk, Shamiko 0.5.1(115),
MagiskHidePropConfig is set,
Safetynet is passed! CTS is passed.
No TWRP folder.

What am I missing?

samhhmobil
IMG_20220710_024836.jpg

detecting root. Thanks
TK-App 4.9.0
Xiaomi Redmi Note 8T, stock MIUI, Android 10.
Magisk 25101, Zygisk, USNF, Shamiko.
Magisk App hidden
TK in denylist:
IMG_20220710_030109.jpg


CTS profile match (SafetyNet) pass.
Play Protect Device is certified

Your TK in denylist?
Cleared app data since?

🙂 PW
 
Last edited:
  • Like
Reactions: J.Michael

samhhmobil

Senior Member
May 25, 2017
440
225
Hamburg

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,050
34,161
Halifax
GT-i9250
Google Nexus 4
If anyone wants to try, or is able to downgrade the Magisk App from current Canary or Debug to Stable, or to upgrade this to a CI build w/o restoring unpatched images (removing root), please report... I'll reward you with some happy faces... 😁 PW

You should still be able to install CI builds using Canary Debug, per https://github.com/topjohnwu/Magisk#signing-and-distribution

If that's not the case anymore then that's clearly a regression from the intended behavior as described by topjohnwu.
 
  • Like
Reactions: ipdev and pndwal

samhhmobil

Senior Member
May 25, 2017
440
225
Hamburg
Oh.. can't test then... Momo detector result may give you some clues...

Assume TK is in denylist... PW
Yes, I know, you can't test it. You need at first successful login with insurance-ID, password, security code (sent via snail-mail), and password again, and after this successful login it detects root and stops working.

Momo 4.3.1 shows:
Device is running a custom ROM.
Found Zygisk.
Bootloader unlocked.

Nothing else...

Google Play shows: Device is certified.

YASNAC passes both,
Basic integrity and CTS profile match.

SafetyNet-Test passed.

But...

"S-Check" (Security Check, by HCE Compliance Experts, PlayStore) detects root... (see screenshot)

Any idea more?

Maybe, it detects TitaniumBackup and/or AFwall+ and/or AdAway?

Thanks a lot,
samhhmobil
 

Attachments

  • Screenshot_20220709-203657_S Check.png
    Screenshot_20220709-203657_S Check.png
    160.5 KB · Views: 51
  • Like
Reactions: pndwal

martyfender

Senior Member
Mar 9, 2017
3,272
1,750
Indianapolis, IN
Yes, I know, you can't test it. You need at first successful login with insurance-ID, password, security code (sent via snail-mail), and password again, and after this successful login it detects root and stops working.

Momo 4.3.1 shows:
Device is running a custom ROM.
Found Zygisk.
Bootloader unlocked.

Nothing else...

Google Play shows: Device is certified.

YASNAC passes both,
Basic integrity and CTS profile match.

SafetyNet-Test passed.

But...

"S-Check" (Security Check, by HCE Compliance Experts, PlayStore) detects root... (see screenshot)

Any idea more?

Maybe, it detects TitaniumBackup and/or AFwall+ and/or AdAway?

Thanks a lot,
samhhmobil
You can try zygisk-lsposed with hide my applist and enhance mode for hidemyapplist and the app added to select effective apps. However, if the app is detecting zygisk, this may not work.
Another option is to use the @huskydg build with zygisk turned off and magiskhide turned on. you may also need riru and other riru modules such as riru momohider and others.

This is a quote from @huskydg github documentation:

Zygisk is easily detected​


Unfortunately, due to the nature of Zygisk, it leaves very obvious traces. Riru has RiruHide to hide itself from scanning in memory, however Zygisk not. Moreover, DenyList is not the hiding feature for zygisk because it can’t hide the existence of zygisk.


There are known apps have been reported that detect zygisk (deny to run if zygisk is enabled) such as Livin’ by Madiri, Itsme, InstaPay, … Even the third-party module Shamiko (v0.5.1) cannot hide zygisk from these mentioned apps above. If you use one of these, the only way to bypass root detection is to use MagiskHide only and DO NOT enable zygisk.
 
Last edited:
  • Like
Reactions: pndwal

dohanin

Senior Member
Mar 26, 2011
231
128
Sony Xperia X Compact
Xiaomi Mi Pad 4
"S-Check" (Security Check, by HCE Compliance Experts, PlayStore) detects root... (see screenshot)

Any idea more?

Maybe, it detects TitaniumBackup and/or AFwall+ and/or AdAway?

Thanks a lot,
samhhmo

My setup is similar to yours (big difference is that I'm using Stock rom) and I passed S-Check.

Stock A12
Magisk 24.3 (app hidden and disabled),
Zygisk, Shamiko 0.5.0(110), USNF
 

Attachments

  • 2022-07-10 08_01_02-Screenshot_20220710-075137975.png ‎- Photos.png
    2022-07-10 08_01_02-Screenshot_20220710-075137975.png ‎- Photos.png
    51 KB · Views: 62
  • 2022-07-10 08_00_51-Screenshot_20220710-075119604.png ‎- Photos.png
    2022-07-10 08_00_51-Screenshot_20220710-075119604.png ‎- Photos.png
    40.5 KB · Views: 64
  • Like
Reactions: pndwal

pndwal

Senior Member
Further, I've found I can no longer even install a [later] CI App... from Actions runs with 25101 Magisk binary installed! ☹️ ... I'm guessing this is due to app signature checks.
You should still be able to install CI builds using Canary Debug, per https://github.com/topjohnwu/Magisk#signing-and-distribution
Many thanks!... I missed the May 24 update to main page (readme.md)...
https://github.com/topjohnwu/Magisk/commit/edb76503d36f05a757fa4e652a2dfbbb471695ad?diff=split

This confirms app signing is the issue here...
If that's not the case anymore then that's clearly a regression from the intended behavior as described by topjohnwu.
No regression... can confirm installing Debug build (Magisk binaries flashed) allows CI signed builds to install...

In fact, it fixes this issue too:
... seems we can no longer 'downgrade' the App to a version earlier than running Magisk daemon in 25100+...
Force app version not lower than daemon
vvb2060 authored and topjohnwu committed 22 days ago

So with Magisk 25101 [Canary] loaded, there is no way I can downgrade the App to Stable 25100 (despite the binary being in sync), or run any earlier app (Including old Manager app) on my device. ☹️
While this remains true, installing Debug build (Magisk binaries flashed) allows downgrading to any earlier App build...

Clearly Debug binary bypasses both app signing and daemon version checks. 🙂 (Does this mean that certain commits are skipped in builds w/ debug flag, or are they just bypassed somehow?)

Of course, changing app through the Magisk App, or with it installed, will fail in both these cases... System app version and signature checks will still prevent downgrading and updating to builds signed with different keys. This means users must uninstall the Magisk App and manually install downgrade, CI or unofficial distribution builds.

... I'll reward you with some happy faces... 😁 PW
... Your due sir; really appreciate it!:

☺️
🌞😁
😂😃😄
😊🥳😹😺🙋
🙂🙃😛🤠😜😝
😷😀🤪😀😃😄😁😆
😅😂🤣😉😍🤩🥰😋😊😇
🌝😻🙉💇👩‍✈️👸👶👱👴🏻👩‍🦰🧑🐸

... For a good 🥚, 😜

----------------------------------------------​

Unrelated: I do see that this anomaly remains:

Hiding the Magisk app (and restoring it) often fails with a message saying 'root is lost; you need to reinstall Magisk', 'request superuser permission for Magisk app' etc...

Actually the issue is that the previous App is not successfully uninstalled, and two conflicting apps are left installed...

The workaround is to ignore the various messages completely... Close everything, and if you were taking Hide the Magisk app, simply uninstall the full app manually; if you were taking Restore the Magisk app, simply uninstall the obfuscated (stub) app manually...

🤠 🐣 PW
 
Last edited:

IronStorm84

Member
Jan 28, 2014
17
2
hi all,

i have a problem to reinstall magisk.
iam runnning a galaxy s9 with soldiers rom with android 9 (y i know very old but working)
twrp is installed. magisk was installed. for one app i uninstalled magisk once. now i have the problem when iam install the 25er version that i have no options like su or modules because app says magisk is not installed.
i dont want to wipe everthing. install magisk v25 with twrp was succesfull (via renamed zip) but the app told me that magisk is not installed.
how to reinstall the app to hide some apps from magisk without losing data or wipe it?
 

nu11ptr

Member
Oct 11, 2021
7
7
Redmi Note 9
hi all,

i have a problem to reinstall magisk.
iam runnning a galaxy s9 with soldiers rom with android 9 (y i know very old but working)
twrp is installed. magisk was installed. for one app i uninstalled magisk once. now i have the problem when iam install the 25er version that i have no options like su or modules because app says magisk is not installed.
i dont want to wipe everthing. install magisk v25 with twrp was succesfull (via renamed zip) but the app told me that magisk is not installed.
how to reinstall the app to hide some apps from magisk without losing data or wipe it?
Um, Didn't quite follow you.
So the app said "magisk is not installed". It probably means, the app tried to execute "su" binary but cannot find it. Check if the "su" binary exists.
Sorry for my English.
 
  • Like
Reactions: ipdev and pndwal

zgfg

Senior Member
Oct 10, 2016
7,811
5,223
hi all,

i have a problem to reinstall magisk.
iam runnning a galaxy s9 with soldiers rom with android 9 (y i know very old but working)
twrp is installed. magisk was installed. for one app i uninstalled magisk once. now i have the problem when iam install the 25er version that i have no options like su or modules because app says magisk is not installed.
i dont want to wipe everthing. install magisk v25 with twrp was succesfull (via renamed zip) but the app told me that magisk is not installed.
how to reinstall the app to hide some apps from magisk without losing data or wipe it?
As said, try with su from Terminal. And/or even better, check what version of Magisk you have with the command:
magisk -c

Most likely, Magisk is there but your new Magisk app does not find it.
If you did Hide Magisk app/mngr with your old Magisk app/mngr, you had to unhide THAT OLD Magisk app before upgrading

That's the common mistake many do, resultimg with the problem like yours

Check as above, we'll see then
 
  • Like
Reactions: J.Michael and ipdev

73sydney

Senior Member
HCE Compliance Experts

My setup is similar to yours (big difference is that I'm using Stock rom) and I passed S-Check.

Stock A12
Magisk 24.3 (app hidden and disabled),
Zygisk, Shamiko 0.5.0(110), USNF


Worth pointing out the actual app name is Security Check - Device compliance for payments


I mention this only because when i searched for S-Check, all i got was an Australian Hospitals app for meth users to track their meth addiction :)

fwiw, i dont have a meth problem, and * my device doesnt pass root detection


*quite possibly due to the fact im spoofing just the manufacturer prop of my S20+ 5G as Google to get Samsung Health working

life is like a box of ponkles
 
Last edited:
  • Haha
Reactions: ipdev and pndwal

zgfg

Senior Member
Oct 10, 2016
7,811
5,223
Worth pointing out the actual app name is Security Check - Device compliance for payments


I mention this only because when i searched for S-Check, all i got was an Australian Hospitals app for meth users to track their meth addiction :)

fwiw, i dont have a meth problem, and * my device doesnt pass root detection

*quite possibly due to the fact im spoofing just the manufacturer prop of my S20+ 5G as Google to get Samsung Health working

life is like a box on ponkles
Stock MIUI, I put S-Check to DenyList (using Shamiko).and enabled hiding in HMA but still root detection error 107/204/606
 

Attachments

  • Screenshot_2022-07-10-17-41-58-139_com.hce.compliance.checker.jpg
    Screenshot_2022-07-10-17-41-58-139_com.hce.compliance.checker.jpg
    424.1 KB · Views: 26
Last edited:

huskydg

Senior Member
Feb 17, 2021
242
246
An old Chinese story called The Man who Sold Spears (momo) and Shields (shamiko).

In the state of Chu lived a man who sold shields and spears.
"My shields are strong," he boasted, "that nothing can pierce them. My spears are so sharp that there is nothing they cannot pierce."
"What if one of your spears strikes one of your shields?" someone asked him.
The man had no answer to that.🤣
 

pndwal

Senior Member
Stock MIUI, I put S-Check to DenyList and enabled hiding in HMA but still root detection error 107/204/245
Did same yesterday... (Nearly signed up on meth program too.😜 ... By accident I mean...)
IMG_20220710_105744.jpg

If you touch failed result you get error codes... No ideas of meaning, but may be worth comparing...
after your "mental masturbation" to crappy comparison apps (momo, magisk detector, ...), you'll want to say "well anyway I just expect my banking app to work fine"
Modding is just a fun diversion / 'sport' for some... Some take it too seriously...

For the players, at least Momo is current; Magisk detector is deprecated... PW
 
  • Like
  • Love
Reactions: ipdev and 73sydney

zgfg

Senior Member
Oct 10, 2016
7,811
5,223
Did same yesterday... (Nearly signed up on meth program too.😜 ... By accident I mean...)
View attachment 5656455
If you touch failed result you get error codes... No ideas of meaning, but may be worth comparing...

Modding is just a fun diversion / 'sport' for some... Some take it too seriously...

For the players, at least Momo is current; Magisk detector is deprecated... PW
Error codes do have meaning

First, I forgot to Save in HMA, hence effectively I didn't have it enabled in HMA and error was 107/204/245

Then I configured again in HMA and saved (and edited my post), with HMA error is now 107/204/606

I tested and have the same errors on Mi 9T (Xiaomi.eu but also A11), also Canary 25101, Shamiko - however, on Mi 9T I don't need/run USNF

Btw, I disabled now S-Check in DenyList and error code changed - it's now 107/204/251
 
Last edited:
  • Like
Reactions: 73sydney and pndwal

pndwal

Senior Member
An old Chinese story called The Man who Sold Spears (momo) and Shields (shamiko).

In the state of Chu lived a man who sold shields and spears.
"My shields are strong," he boasted, "that nothing can pierce them. My spears are so sharp that there is nothing they cannot pierce."
"What if one of your spears strikes one of your shields?" someone asked him.
The man had no answer to that.🤣
There was an old man from Chu
who said "I sell shields that are true
And I test them with spears
that I sharpen with tears!
- such is my devotion to you."​

Still, a bat and ball (sport) analogy may be more apt since it's just a game to me.

... And some balls will always hit the wicket.

Those intent on winning a (serious) battle are already doomed.

Some spears will always make their mark...

👍 PW
 
Last edited:

Top Liked Posts

  • 3
    My noob question is if I update the ROM I lose data, right ?
    Not unless you wipe or format data = clean flash... Dirty flash to keep data...

    If flashing Sammy binaries w/ Odin, CSC will wipe data for clean installation, HOME_CSC won't wipe data, ie. Installation will be 'dirty'...

    🙂 PW
    2
    Hello Everyone. I have an old S8+ using android 8.0 with Renovate Ice . Magisk was working fine, dont recall the version but it was old . Trying to update to version 25.2 but nothing happens. Got stuck on 25.1 and besides that I cant get Magisk properly installed, zigdysk N/A . Which steps should I take ? I dont recall if I need to format data again, but I did not want to lose all the data inside the phone.
    Please say what you mean by 'got stuck'... Are you using .zip installer in twrp, or in-app patching and fastboot flash?... When does "nothing happen"?...

    Re. no Zygisk, you may need to update to a ROM with kernel version 3.19+:
    https://github.com/topjohnwu/Magisk/issues/5395

    🙂 PW
    2
    I realized the attachment did not work. This time the file is zipped.

    Before I recorded the bootloop (with the patched imaged) I was using the original boot image to boot into safe mode. But as you explained this does not have an effect on the modules as magisk itself is missing.

    I thought TWRP was working when I tested is a few weeks ago, but right now TWRP is stuck at the splash screen, so I cannot test it :( probably this is because of Android 13

    My solution was to modify magisk itself. I removed the module loading part, compiled magisk and patched the boot image again. This was I was able to boot and remove all modules and then again patch the original boot image with the "real" magisk. See here for more detail https://github.com/topjohnwu/Magisk/issues/6301#issuecomment-1265164036.

    Thank you all for your help.

    EDIT: I have attached the binary if anybody has the same issue. But you can and should always compile it yourself.
  • 7
    Can someone either provide actual proof that zygisk/shamiko etc does anything to GPS (i havent had a single issue and i use it daily) or i dunno, maybe stop spreading FUD because of personal gripes you have against people on other platforms that dont take part here, and therefore wont get any of the swipes youre taking at them here that only further add to the aforementioned FUD.

    We've all had our moments with those folk and its fine to mention the odd bit of spice you may come across when trying to submit an issue on github (ive done this myself), but to then to continually poison magisk proper/shamiko because of that person/persons taking part is not helping anyone. Thats a personal gripe, and shouldnt colour the entire magisk (proper) project/shamiko. What we dont need is spice here....

    Please, you know who you are...

    I think we've all had enough, now
    5
    Installing on Samsung S7 (SM-G930F) with /e/OS?
    Okay folks, thought I'd post up the procedure:
    1. Follow these instructions until you get to 7th bullet point here;
    2. Stop. Some points to mention on the way:
      1. Note my progress above from 'Preliminaries' until point 5, adb pull /sdcard/Download/magisk_patched_[random_strings].img works just fine;
      2. Ignore my rambling queries up to point 5;
    3. Install heimdall;
    4. Boot device into 'Download' mode without USB cable connected, then once in 'Download' mode insert USB cable (this seemed important as I ran into quite a lot of ERROR: Protocol initialisation failed! type errors which seemed possibly cable/ hardware related);
    5. Bash:
      $ heimdall detect
      Device detected
      $ heimdall print-pit --no-reboot > print-pit.txt
    6. From print-pit.txt discover:
      ...
      --- Entry #10 ---
      Binary Type: 0 (AP)
      Device Type: 8 (Unknown)
      Identifier: 5
      Attributes: 5 (Read/Write)
      Update Attributes: 1 (FOTA)
      Partition Block Size/Offset: 10240
      Partition Block Count: 10240
      File Offset (Obsolete): 0
      File Size (Obsolete): 0
      Partition Name: BOOT
      Flash Filename: boot.img
      FOTA Filename:
      ...
    7. Reboot into 'Download' mode (this rebooting also seemed to help prevent the above errors);
    8. Bash:
      $ heimdall detect
      Device detected
      $
    9. Then, instead of fastboot flash boot /path/to/magisk_patched.img at the 7th bullet point here
      Do:

      Bash:
      $ heimdall flash --BOOT magisk_patched-25200_UjUVt.img
      Heimdall v1.4.2
      
      Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
      http://www.glassechidna.com.au/
      
      This software is provided free of charge. Copying and redistribution is
      encouraged.
      
      If you appreciate this software and you would like to support future
      development please consider donating:
      http://www.glassechidna.com.au/donate/
      
      Initialising connection...
      Detecting device...
      Claiming interface...
      Setting up interface...
      
      Initialising protocol...
      Protocol initialisation successful.
      
      Beginning session...
      
      Some devices may take up to 2 minutes to respond.
      Please be patient!
      
      Session begun.
      
      Downloading device's PIT file...
      PIT file download successful.
      
      Uploading BOOT
      100%
      BOOT upload successful
      
      Ending session...
      Rebooting device...
      Releasing device interface...
      
      $
    10. At which, the device reboots and:
      Screenshot_20220927-133842_Magisk.png
    11. Happiness :)
    5
    I'm using the systemless debloater module to degoogle and debloat a device (and several other magisk modules to assist in that endeavor). I'd really like to be able to do a factory reset to clear the device of any data/artifacts from the debloated apps, but of course a factory reset wipes out magisk modules, so I'm in a catch 22.
    You can do some cleaning like this:

    - Wipe (from TWRP or by root explorer like MiXPlorer)
    /data/dalwik-cache
    /data/system/package_cache

    -In MiXPlorer, go to three dots, Tools and clean by App Remnants

    -Install SD Maid:
    And clean by CorpsFinder option
    5
    How does PixelFlasher invoke boot_patch.sh?
    Does it invoke it as an "executable", creating a new process? Or does it "source" it, so changes to the environment will survive?

    Does PixelFlasher create an environment variable named "SHA1"?

    My copy of boot_patch.sh has a compound statement that tests whether SHA1 has a non-zero length value before setting it to the sha1 of the boot image. If the environment variable is already set, it will not be overwritten. I don't know why.
    I wouldn't source. The script is supposed to be called as an executable

    Eg, my following code is rather primitive but it dumps the active Boot partition (it supports A/B and non-A/B devices), then it patches by invoking the boot_patch.sh script, finally it dumps back to the Boot partition and automatically reboots

    Ie, it updates me the Magisk and it also leaves me the patched-boot img in the Download folder

    Code:
    #!/system/bin/sh
    
    # Boot partition
    AB=$(getprop ro.boot.slot_suffix)
    BOOT_PART=/dev/block/bootdevice/by-name/boot"$AB"
    
    # Boot and patched boot images
    DOWNLOAD=/sdcard/Download/
    BOOT_IMG="$DOWNLOAD"boot.img
    PATCHED_BOOT_IMG="$DOWNLOAD"patched-boot.img
    
    # Magisk path
    MAGISK_PATH=/data/adb/magisk/
    
    # Disk-dump boot image to Download folder
    dd if="$BOOT_PART" of="$BOOT_IMG"
    
    # Patch the boot image and move to Download folder
    "$MAGISK_PATH"boot_patch.sh "$BOOT_IMG"
    mv "$MAGISK_PATH"new-boot.img "$PATCHED_BOOT_IMG"
    
    # Flash the patched boot image
    dd if="$PATCHED_BOOT_IMG" of="$BOOT_PART"
    
    # Reboot
    reboot
  • 1085
    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