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

Magisk General Support / Discussion

Search This thread

tjluvu

Member
Jun 7, 2014
21
7
i have wierd problem.... i am able to pass safety net ..... pokemongo works fine ..... even magisk hide works well on some apps like titanium , terminal emulator ... but there are some apps which still detect root even after selecting them in the magisk hide app list.... any thought about what might be the problem ... i am on a lineageos based rom.... which had cm root before i flashed magisk..... currently i am using phh superuser installed by magisk automatically ......
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,994
13,599
Gothenburg
Google Nexus 4
Nexus 6
somebody help me with this problem i cant flash magisk im using arkROM1 gt-i9500 please

You probably won't get much help unless you give details, lots of details.

And logs, lots of logs...

Edit: And please don't cross post. It's annoying and easily leads to confusion. @tjluvu I'm looking at you as well.
 
Last edited:

Captain_Throwback

Recognized Developer
i have wierd problem.... i am able to pass safety net ..... pokemongo works fine ..... even magisk hide works well on some apps like titanium , terminal emulator ... but there are some apps which still detect root even after selecting them in the magisk hide app list.... any thought about what might be the problem ... i am on a lineageos based rom.... which had cm root before i flashed magisk..... currently i am using phh superuser installed by magisk automatically ......
They could be detecting the Superuser app. Or any number of things. It's all speculation without any logs ;).
 

gk1984

Senior Member
Jan 4, 2011
2,318
626
i have wierd problem.... i am able to pass safety net ..... pokemongo works fine ..... even magisk hide works well on some apps like titanium , terminal emulator ... but there are some apps which still detect root even after selecting them in the magisk hide app list.... any thought about what might be the problem ... i am on a lineageos based rom.... which had cm root before i flashed magisk..... currently i am using phh superuser installed by magisk automatically ......
As CaptainThrowback suggested, some apps simply detect superuser is installed. The AT&T U-verse app does for sure. I did some experimenting with that. Removing the app without unrooting made it not detect root (I don't recommend this) and installing superuser without rooting made it not work. This is how I figured it out. No solution though.
 

beta546

Senior Member
Jan 25, 2011
401
85
Blackpool
Hello, I've got everything working with root and xposed but I just can't pass the safetynet check, I don't really need to but the ocd in me can not stand to see that big red box saying failed.

I am uaing this ROM (I guess is the problem)
https://forum.xda-developers.com/le-max-2/development/madsurfers-21s-eui-5-9-rom-t3497125

It comes rooted but I did a full unroot in superSU and restored boot image.
Then flashed latest magisk in TWRP,
Then installed systemless xposed and phh superuser to manage permissions. Magisk works to hide root which I tried with root checker. But I'm guessing there is some other system modification in this ROM being detected by safetynet?

I've attached some screens and logs as well.
 

Attachments

  • Screenshot_2017-01-17-16-15-51.jpg
    Screenshot_2017-01-17-16-15-51.jpg
    148.8 KB · Views: 606
  • Screenshot_2017-01-17-16-15-40.jpg
    Screenshot_2017-01-17-16-15-40.jpg
    168.3 KB · Views: 604
  • last_magisk.log
    1.4 KB · Views: 6
  • magisk.log
    12.2 KB · Views: 6

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,994
13,599
Gothenburg
Google Nexus 4
Nexus 6
Hello, I've got everything working with root and xposed but I just can't pass the safetynet check, I don't really need to but the ocd in me can not stand to see that big red box saying failed.

I am uaing this ROM (I guess is the problem)
https://forum.xda-developers.com/le-max-2/development/madsurfers-21s-eui-5-9-rom-t3497125

It comes rooted but I did a full unroot in superSU and restored boot image.
Then flashed latest magisk in TWRP,
Then installed systemless xposed and phh superuser to manage permissions. Magisk works to hide root which I tried with root checker. But I'm guessing there is some other system modification in this ROM being detected by safetynet?

I've attached some screens and logs as well.

Magisk does NOT hide Xposed!
 

beta546

Senior Member
Jan 25, 2011
401
85
Blackpool
Magisk does NOT hide Xposed!

But what about all the guides around describing how to use android pay with root and xposed, using magisk? Was it only the older version of magisk that could do that? Or has safetynet been updated to circumvent it?

Also I don't pass saferynet without xposed installed (Probably should have mentioned that earlier)
 
Last edited:

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,994
13,599
Gothenburg
Google Nexus 4
Nexus 6
But what about all the guides around describing how to use android pay with root and xposed, using magisk? Was it only the older version of magisk that could do that? Or has safetynet been updated to circumvent it?

Magisk Hide have never been able to hide Xposed. I believe you can disable Xposed (and reboot) though to pass Safety Net, but I don't use it myself so I've never tried. I'd suggest you should read the Official announcement thread. Pretty much all you need to know in there. If you've got questions after that, search this thread. Most questions have already been asked and most of those have been answered (several times).

And by the way... Why so many apps on your hide list? Do all those really need to have root hidden? Youtube? Or where you just hiding stuff on random trying to make things work. For Safety Net nothing needs to be hidden on the list. It's just for apps that don't use SN to find root... Too many hidden apps might actually break your root in certain circumstances (again, read the Official announcement thread).
 
  • Like
Reactions: Captain_Throwback

beta546

Senior Member
Jan 25, 2011
401
85
Blackpool
Magisk Hide have never been able to hide Xposed. I believe you can disable Xposed (and reboot) though to pass Safety Net, but I don't use it myself so I've never tried. I'd suggest you should read the Official announcement thread. Pretty much all you need to know in there. If you've got questions after that, search this thread. Most questions have already been asked and most of those have been answered (several times).

And by the way... Why so many apps on your hide list? Do all those really need to have root hidden? Youtube? Or where you just hiding stuff on random trying to make things work. For Safety Net nothing needs to be hidden on the list. It's just for apps that don't use SN to find root... Too many hidden apps might actually break your root in certain circumstances (again, read the Official announcement thread).

Yeah I'm not sure as it won't even pass without xposed. Oh and I'd just hidden everything while messing about. I'd actually unticked everything before I copied them logs. So nothing is hidden now anyway. I guess I'll just leave it as is now seeing as it all works and I don't actually use any apps that use safety net. I've read all of the announcement thread and searched as much as I can but nothing I do will let me pass the check..I guess I'll give up and leave it. It's not affecting anything. I'll look into it again if I ever need one of these apps that detects modified systems.
Thanks anyway though
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,994
13,599
Gothenburg
Google Nexus 4
Nexus 6
Yeah I'm not sure as it won't even pass without xposed. Oh and I'd just hidden everything while messing about. I'd actually unticked everything before I copied them logs. So nothing is hidden now anyway. I guess I'll just leave it as is now seeing as it all works and I don't actually use any apps that use safety net. I've read all of the announcement thread and searched as much as I can but nothing I do will let me pass the check..I guess I'll give up and leave it. It's not affecting anything. I'll look into it again if I ever need one of these apps that detects modified systems.
Thanks anyway though

No worries. Several things may trigger SN. I wrote this a while back: https://forum.xda-developers.com/showpost.php?p=70426733&postcount=7120
 

Demax55

Member
Jan 17, 2017
10
0
I tried flashing this on my Honor 8 and it seems to work, boot, and pass safety net, the only issue is it seems to break the fingerprint reader. The Fingerprint ID menu gets removed from Settings. It can be found by searching, but will not let you add a Fingerprint to it, and also removes some of the other features tied into Fingerprint ID, such as swiping down to open notifications. The button itself still works as I can still set and use that. I then flashed stock boot.img back and everything was working again. I don't know if it's something such as a prop that is getting set that disables it based on security or if it's just in the way that it modifies the boot.img and is breaking something in Huawei's implementation. I grabbed two logcats, one before flashing magisk and one after. Unfortunately I don't know enough about where to look or what I'm looking for exactly to try and figure it out. If anyone could help out that would be greatly appreciated, if not, it's not a big deal as I have my HTC 10 with Magisk working quite nicely.


This happened to me! Yesterday I updated Magisk to v10.2 on my Honor 8 and the fingerprint stopped working. What should I do to fix it? I need root on my phone for so many things and I need to have fingerprint working, since it saves a lot of time. I can't just unroot it
 
Last edited:

duowing

Senior Member
Dec 14, 2010
537
106
Cleveland, OH
This happened to me! Yesterday I updated Magisk to v10.2 on my Honor 8 and the fingerprint stopped working. What should I do to fix it? I need root on my phone for so many things and I need to have fingerprint working, since it saves a lot of time. I can't just unroot it

I pulled the getprop log as suggested by Captain Throwback and didn't find anything different. I think it's something to do with the way Magisk is modifying the boot.img and probably related to the way Huawei codes. Even in the logcat it looks like everything initializes and then it just errors out. I just used the Charles app method to flash the latest N beta, so I'll unlock bootloader and try flashing Magisk on that to see if it works on N.
 

Demax55

Member
Jan 17, 2017
10
0
I pulled the getprop log as suggested by Captain Throwback and didn't find anything different. I think it's something to do with the way Magisk is modifying the boot.img and probably related to the way Huawei codes. Even in the logcat it looks like everything initializes and then it just errors out. I just used the Charles app method to flash the latest N beta, so I'll unlock bootloader and try flashing Magisk on that to see if it works on N.

This is incredibly annoying. I come back home just to sleep and I don't have to time to play around and see how to make it work again.

Could someone explain me how to unroot ( I have magisk v10.2 + phh superuser) so I can install magisk v9 that used to work? I have Honor 8 and Android 6. When unrooted I'll also update the phone ( Not to android 7)
 
Last edited:

andrew2432

Senior Member
This is incredibly annoying. I come back home just to sleep and I don't have to time to play around and see how to make it work again.

Could someone explain me how to unroot ( I have magisk v10.2 + phh superuser) so I can install magisk v9 that used to work? I have Honor 8 and Android 6. When unrooted I'll also update the phone ( Not to android 7)

Still flash the uninstaller? It locates your stock boot, used to, and installs it
 

Top Liked Posts

  • 3
    Hi from greece! I have a pioneer SDA8TAB android 9,followed the magisk steps for recovery method as the tablet doesn't have ram disk but it doesn't work, I can't try other method cause this device does not have custom recovery and I cant find a way, anyone can help? I have full system dump made from emmc easyjtag
    I have a Pixel 4A without a custom recovery. I use fastboot to install Magisk
    3
    Thanks! Yes it boot to recovery, tried few times but root not working, there is a forum but they don't know something, I also sent the the files to try, yes sda835a, in greece yes different name, is any other way? Any way to patch the system. Img may be? Or someone who can make twrp for this device?
    The point of Magisk is to *not* patch the system image.

    I think installing TWRP to use it to install Magisk is the wrong way to go. Finding a working TWRP is a whole other project.

    "few times" isn't nearly enough. The process is very fussy. You have to find just the right time to let go of the buttons so the (BIOS?) has committed to booting the recovery image, but the recovery image (hijacked by Magisk) has not yet tested to see if the buttons are being held down. Someone finally found a way to explain it to me, it involved identifying just which of the three to five "boot logos" was my signal to let go. I really meant it when I said try it a few dozen times. And, like I said, at some time, for some device, someone declared that it wouldn't work unless you had a cable plugged into the device.

    Make a point of shutting down to the completely powered off state before each trial.

    I don't know in what form you have the original boot image, but compare the sizes of the original and patched images. If the patched image is smaller, maybe it needs to be padded. Even if they are the same size, it could be that the Magisk app you are using discarded some signature string that was in the original. Somebody else will need to comment further.
    1
    Tried, no ramidisk and if I do the recovery it don't do anything
    You might be able to patch the boot image. Sometimes it works, even though the original boot image does not have a ramdisk.

    You will need to describe "don't do anything" in more detail. What do you see? When does it look different than the way it looks when booting the stock image?

    How can you have a "full system dump" if you are not rooted?

    Did you unlock the bootloader?
    1
    Thanks! Yes it boot to recovery, tried few times but root not working, there is a forum but they don't know something, I also sent the the files to try, yes sda835a, in greece yes different name, is any other way? Any way to patch the system. Img may be? Or someone who can make twrp for this device?
    I have NOT read all the posts. But to flash the boot image, I do NOT go into recovery, it is dlashede in fastboot. CAn you get into fastboot? and can your PC "see" the phone in fastboot mode?
    1
    Here is the stock imgs from my firmware, if anyone can help me to make it work I will be thankful and I will buy him a drink! Maybe Raki we have here in crete!
    As mentioned by @J.Michael, I think you have likely already succeeded in flashing root w/ Magisk in recovery ramdisk since it flashed without errors, and you don't get bootloop.

    Your difficulty appears to be booting to recovery mode system-with-Magisk on type III device using key combo.
    Type III: Late 2018 - 2019 devices that are A-only. The worst type of device to ever exist as far as Magisk is concerned.
    https://topjohnwu.github.io/Magisk/boot.html#piecing-things-together

    Nb. 'booting into recovery mode' is not referring booting into recovery, but system-with-Magisk mode achieved using recovery ramdisk, ie. booting into system via 'hijacked' recovery ramdisk since boot.img lacks ramdisk. This involves Magisk independently detecting recovery mode key combo + release of buttons within a specific time window in order to execute magiskinit. (A ramdisk is always required for systemless Magisk.)
    https://github.com/topjohnwu/Magisk/blob/master/docs/details.md#magisk-booting-process

    If the key combo only is detected ramdisk will boot to recovery.

    Instructions:
    https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

    As mentioned, key release timing is critical, and varies per device.

    Compounding the issue is the fact that John's hybrid Magisk key combo detection does not operate as expected / designed on many devices, and users may need to experiment to establish a working method that is sometimes at odds with John's instructions.

    As an example, safe mode is not always detected by Magisk resulting in modules remaining active even after safe-mode has been activated w/ Magisk installed on (some) Xiaomi devices. This can be very misleading to users. However, an altered key combo does work to both trigger safe mode and allow Magisk to detect Safe mode trigger.

    I opened an issue here Regarding this failure to detect key combo and critical timing 'sweet spot'.
    https://github.com/topjohnwu/Magisk/issues/4624

    So I recommend you keep trying to boot system w/ Magisk in recovery as you already seem to have (had) this installed correctly.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    This is done over the latest Alpha Magisk.

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

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

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

    And then here on this GitHub issue about how it's not meant to replace MagiskHide so you can't just turn Hide off: https://github.com/kdrag0n/safetynet-fix/issues/91#issuecomment-919264624
  • 1062
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    156
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    The Flash
    Forum Moderator

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

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

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

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

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