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

Magisk General Support / Discussion

Search This thread

culiacanazo

Senior Member
I have a galaxy s7e full stock when I install twrp on to phone and enter it to flash magisk do I need to wipe before hand? And what is a custom kernel and do I need one? Sorry for the noob
Too much of a device to be noobing around, I'd say... Take my word for it: get yourself a cheaper device and come back and mess with it

Sent from my SM-G900T using XDA Labs
 

klark1kent

Senior Member
I have an LGV10 running Eliminator's custom rom on Tmobile... I've found that no matter what I do I cannot remove SuperSU completely. I've tried from supersu app and also used the Unsu zip from Osmosis. I never flash the boot.img when I'm directed to do so in TWRP because I was under the impression they were referring to the boot.img provided in the rom that was already installing supersu during TWRP install. So my question is this, am I wrong in thinking the boot has anything to do with the custom rom obtaining su. Should I install the boot.img from the install zip for the custom rom or install the boot.img for stock in order to full remove Supersu and successfully use PHH superuser... I'm asking here because I've been unable to flash Magish 10.2 and my error is typically at the su portion of the flash in TWRP. I'm thinking if I just flash the boot.img and get rid of supersu altogether, i'd be able to successfully flash 10.2 and use PHH su. Thanks!
 

teddy0209

Senior Member
Feb 5, 2011
2,318
690
I have an LGV10 running Eliminator's custom rom on Tmobile... I've found that no matter what I do I cannot remove SuperSU completely. I've tried from supersu app and also used the Unsu zip from Osmosis. I never flash the boot.img when I'm directed to do so in TWRP because I was under the impression they were referring to the boot.img provided in the rom that was already installing supersu during TWRP install. So my question is this, am I wrong in thinking the boot has anything to do with the custom rom obtaining su. Should I install the boot.img from the install zip for the custom rom or install the boot.img for stock in order to full remove Supersu and successfully use PHH superuser... I'm asking here because I've been unable to flash Magish 10.2 and my error is typically at the su portion of the flash in TWRP. I'm thinking if I just flash the boot.img and get rid of supersu altogether, i'd be able to successfully flash 10.2 and use PHH su. Thanks!
I'm not sure if the rooting is related to the boot.img in your device, but you could try, as long as the rom is stock based. It would be better to ask from your rom dev about properly removing root.

Sent from my HTC One M9 using Tapatalk
 
  • Like
Reactions: klark1kent

klark1kent

Senior Member
I'm not sure if the rooting is related to the boot.img in your device, but you could try, as long as the rom is stock based. It would be better to ask from your rom dev about properly removing root.

Sent from my HTC One M9 using Tapatalk

If you only knew how difficult that thread is to navigate, magisk topics have been asked before but, I really can't put that thread into words other than saying that mods have been on it on several occasions. To his credit, he is performing great work. But it's lets just say an interesting thread.

What's weird is I found myself in a boot loop trying to work this out, and ended up pulling out of it... but in doing so needed to do magisk uninstaller and unsu zip. Well when I got the phone working again I had to use supersu, after I rebooted and everything I went into Magish and v10.2 installed first try... everything is working fine but I'm using chainfires tool and really don't get how/why the 10.2 upgrade would go through on supersu and not PHH. I'll prob uninstall supersu at some point and go back to PHH as I believe several modules require it but strange situation.
 

yochananmarqos

Recognized Contributor
I have an LGV10 running Eliminator's custom rom on Tmobile... I've found that no matter what I do I cannot remove SuperSU completely. I've tried from supersu app and also used the Unsu zip from Osmosis. I never flash the boot.img when I'm directed to do so in TWRP because I was under the impression they were referring to the boot.img provided in the rom that was already installing supersu during TWRP install. So my question is this, am I wrong in thinking the boot has anything to do with the custom rom obtaining su. Should I install the boot.img from the install zip for the custom rom or install the boot.img for stock in order to full remove Supersu and successfully use PHH superuser... I'm asking here because I've been unable to flash Magish 10.2 and my error is typically at the su portion of the flash in TWRP. I'm thinking if I just flash the boot.img and get rid of supersu altogether, i'd be able to successfully flash 10.2 and use PHH su. Thanks!
After you unroot via SuperSU, flash the boot.img from your ROM ZIP then install Magisk. If that doesn't work then it's a ROM issue.

Sent from my Nexus 5X using XDA Labs
 
  • Like
Reactions: klark1kent

seb5049

Senior Member
Nov 28, 2015
66
9
Remove old root, install MagiskSU... You might need to reinstall Magisk and in that case MagiskSU will be installed automatically if you've removed the previous root method. Otherwise it's just a matter of flashing the Magisk superuser module.
So I uninstalled Magisk, flashed my stock boot image, then installed it again to get the correct phh superuser. However, my problem still remains.
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,017
13,698
Gothenburg
Google Nexus 4
Nexus 6
So I uninstalled Magisk, flashed my stock boot image, then installed it again to get the correct phh superuser. However, my problem still remains.

Logs (Magisk log and recovery log from the installation are usually quite useful) and a screenshot of the status page from the Manager can be helpful as well.
 
  • Like
Reactions: seb5049

seb5049

Senior Member
Nov 28, 2015
66
9
Logs (Magisk log and recovery log from the installation are usually quite useful) and a screenshot of the status page from the Manager can be helpful as well.
Attached are the Magisk log and status screen screenshot.
 

Attachments

  • magisk_error_20170205_095933.log
    7.6 KB · Views: 8
  • Screenshot_20170205-095757.png
    Screenshot_20170205-095757.png
    51.3 KB · Views: 488
Last edited:

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,017
13,698
Gothenburg
Google Nexus 4
Nexus 6
Attached are the Magisk log and status screen screenshot.

Everything looks good.

Your original problem was that ticking the boxes for Hide wouldn't stick, right? That's been fixed now, I assume, and now you just want to pass SafetyNet.

Does Hide work otherwise, as in: can you hide root from an app not using SafetyNet. A root checker, for example. If that works, you'll just have to go through the usual suspects that trigger SN. Here are some tips:
https://forum.xda-developers.com/showpost.php?p=70426733&postcount=7120
 
  • Like
Reactions: seb5049

seb5049

Senior Member
Nov 28, 2015
66
9
Everything looks good.

Your original problem was that ticking the boxes for Hide wouldn't stick, right? That's been fixed now, I assume, and now you just want to pass SafetyNet.

Does Hide work otherwise, as in: can you hide root from an app not using SafetyNet. A root checker, for example. If that works, you'll just have to go through the usual suspects that trigger SN. Here are some tips:
https://forum.xda-developers.com/showpost.php?p=70426733&postcount=7120

Unfortunately, the ticking boxes problem is still there. I'm not really interested in bypassing Safetynet - I just want to be able to play games like Fire Emblem Heroes which block you out after a while if you're rooted.
 

Ikzy

Senior Member
Apr 3, 2016
57
23
Xperia X Compact (F5321) on Nougat 7.0 with Genesis Kernel 1.03
When I power off my device it will not boot up again. Reboots do work and a volume up + power reset will boot up just fine.
Unfortunately there is no last_magisk.log probably because the power off won't finish. I checked regular magisk.log with no errors.

Any other logs I can provide to troubleshoot this, or any fixes?
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,017
13,698
Gothenburg
Google Nexus 4
Nexus 6
Unfortunately, the ticking boxes problem is still there. I'm not really interested in bypassing Safetynet - I just want to be able to play games like Fire Emblem Heroes which block you out after a while if you're rooted.

Ok. You've got some other issue then. I never caught what device and ROM you're using.
 
  • Like
Reactions: seb5049

speakeasy1

Senior Member
Dec 18, 2008
247
26
IIRC Nitrogen comes with superuser built-in. Did you remove that before installing Magisk? If not that's a good place to start. I even believe they provide you with an unsu script.



Remove old root, install MagiskSU... You might need to reinstall Magisk and in that case MagiskSU will be installed automatically if you've removed the previous root method. Otherwise it's just a matter of flashing the Magisk superuser module.



Your boot image isn't compatible.

I seem to recall you need to "bump" LG devices. Have you done that? Of course, my memory might have failed me like it usually does...
I have did not unroot. Clean I stall. It just stopped working. I am trying to pass to see if pogo will work again. Are there any steps that may help

Sent from my Nexus 6P using XDA-Developers Legacy app
 

sscsps

Senior Member
Nov 17, 2013
618
186
delhi
I have a Xiaomi Mi4. Latest Global Stable. Installed Magisk Manager. Saftey Net check passed (other ones are red of course). Flashed TWRP, rebooted and checked again. Test still passed.

Booted into TWRP and flashed that Magisk-10.2.zip, Rebooted and SafteyNet Failed.

What did I do wrong? Will Unmagisk repair my keys? How can I root my device without breaking possible future apps...?

Did you found the solution? I had a similar issue with my LeTV Le1S Eco, I fixed it with these steps:
1. Full unroot from SuperSU(if you have it)
2. Reboot to system
3. Reboot to recovery
4. Flash magisk uninstaller
5. Flash magisk installer
6. Reboot to system
7. Install phh's superuser from play store
8. Reboot to system (now phh's superuser should takeover)

and that's it, safetynet passes now!
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,017
13,698
Gothenburg
Google Nexus 4
Nexus 6
I have did not unroot. Clean I stall. It just stopped working. I am trying to pass to see if pogo will work again. Are there any steps that may help

Sent from my Nexus 6P using XDA-Developers Legacy app

-Uninstall Magisk
-Use the unsu zip from the Nitrogen thread
-Install Magisk
-Activate Magisk Hide
-Reboot

If it doesn't work, your system has something triggering SafetyNet. Here are some tips:
https://forum.xda-developers.com/showpost.php?p=70426733&postcount=7120
 

Top Liked Posts

  • 3
    I'm not noticing any problems either. Was just making a PSA for anybody who does use Riru that it's not going to work anymore, and it's not a bug -- it was intentionally disabled. People are freaking out in the alpha Telegram over the "bug," and I wanted to head that off over here
    Yup, looks like w/ a0fe78a7-alpha (maverick 😜) users needing any Riru solutions are out of luck.

    I'm guessing many of these modules will move to Zygisk base in due course.

    Those using needing USNF 2.x for September Google server end change can move back to 1.2.0 and older fixes changing model props. MagiskHide Props Config module Force Basic attestation option with similar late 'device selected from list' matching OEM configured is probably the best of these option. PW

    Screenshot_2021-09-25-09-21-04-544_com.topjohnwu.magisk.png
    Screenshot_2021-09-25-09-25-37-464_com.topjohnwu.magisk.jpg
    2
    For me everything ok (I don't use and need riru): root, SN, V4A, WebView, you name it
    I'm not noticing any problems either. Was just making a PSA for anybody who does use Riru that it's not going to work anymore, and it's not a bug -- it was intentionally disabled. People are freaking out in the alpha Telegram over the "bug," and I wanted to head that off over here
    2
    Interestingly, I had such issues with 0ab31ab0-alpha with Riru enabled, but issue is gone for me in 61783ffc-alpha...

    You could try disabling Riru & USNF 2.x, rebooting, checking Zygisk status / settings, then enabling again; I needed this initially - actually uninstalled USNF, disabled Riru and rebooted before installing again... No issue since on RN8T.

    Of course this may be a per device issue.

    John and vvb2060 are still busy with implementation of Zygisk; this may help in next builds:
    https://github.com/topjohnwu/Magisk/pull/4720
    ... merged with Commits on Sep 24, 2021:
    https://github.com/vvb2060/Magisk/commits/app_zygote
    ... there'll be more too. PW
    I have tried w/o any modules
    Toggled the zygisk button to enable, reboot, zygisk = No, but the button in settings stayed as toggled on, checked the logs, no trace of zygisk

    Tried toggled on and added denylist, reboot, zygisk = No, checked the logs, still no trace of zygisk, but the denylist ran and active.

    Reverting to 0ab31ab0-alpha, boom!!! zygisk = Yes, checked the logs, zygisk xhook was there.

    Tried all alpha before 0ab31ab0-alpha too (with zygisk in it), all the same result with zygisk xhook ran.

    ...running weirdly? or it is weird that they are running?
    It was weird they were running but with no zygisk
    1
    He showed us a screenshot of TWRP running.
    Does he have to tell TWRP to protect itself?
    I guess if he already booted to recovery using key combo such ROM patching is not working / occurring.

    There may be a number of issues:

    Enabling 'Keep system read only' prevents such patching. (I guess there may be additional issues w/ modern shared-blocks filesystem too.)

    ROM may also have harder verified-image-protection to defeat. Some who found twrp fails to patch simply flashed Magisk which also prevents overwriting recovery. (Likely won't help here.)

    I suspect he may also simply have booted using 'fastboot boot twrp.img'. PW
    1
    tried the new alpha and it broke riru which broke lsposed and safetynet not recommended at least if you want to use riru I went back to previous one for now
    That's because they toggled a switch to stop Riru from working with Zygisk in the latest build. Apparently it causes issues
  • 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
  • 1064
    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