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

MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0

Search This thread


Senior Member
Oct 24, 2012


New member
Jan 8, 2016
Hi All, I have searched the net but cant seem to find a solution to fixing the safetynet check and pass the checks on my A95x F3 Air and my Tanix Tx6 box. please can someone please point me in the right direction. Thanks in advance


Senior Member
Aug 12, 2004
after install test version 2.0 on latest dub5 samsung s20 i can get safetynet to work and all my banks app to use fingerprint safety but Google pay says card unconfigured as on screenshot. Will it work on Google pay as can't check easy now?


  • Screenshot_20210221-171934_Google Play services.jpg
    Screenshot_20210221-171934_Google Play services.jpg
    358.3 KB · Views: 152
Last edited:
  • Like
Reactions: Bec07


Senior Member
Nov 2, 2012
Moto G4 Play
If you flash the factory / full ota package, yes. Otherwise if you would like to take the OTA I am currently doing it in the following way:
- flashing back the original kernel
- taking the update ota
- rebooting
- patching the new kernel with Magisk
- flashing the patched kernel
Hi, I followed your tip keeping the patched stock kernel and noticed that the freezing continues even with the only Magisk hide enabled without extensions or apps hide or systemless host, and as second attempt, even with the only systemless host enabled with all the other things at default (no extension modules, no hide at all), so dunno't but it can be some Magisk bug because keeping just Magisk with nothing other and all settings to default it worked 2 days without freezes.


Feb 1, 2011
I have a Samsung SM-T510 2019 10 inch tablet with Android 9. I have TWRP and Magisk installed w/ MagiskHide Props Config and Universal SafetyNetFix 2.0.0-test enabled and setup.

Still failing with Attestation failed, basicIntegrity (pass) ctsProfile (fail) w/ evalType HARDWARE.
Last edited:


Jun 20, 2018
In case anyone has a Pixel 4a, with Android 11 still installed, the 1.1.1 ZIP will pass SafetyNet both in Magisk as well as the "older" version of Google Pay (Google Pay, not Gpay) after it is flashed via Magisk Manager. For reference, I am using the latest Magisk Canary as of time of this post.
  • Like
Reactions: jcp2


Mar 5, 2014
Hi All . . .
I am running a Amlogic X96Air Box with Slimrom-Android 9

Can someone plz guide me on installing Magisk for Safety Net Pass on Uncertified Google Play Store "Uncertified Device"

Firstly i installed the App Manager to access if "ramdisk" is available . . it says "No"
I then uninstalled it . . then tried to go the route to flash the zip (v22) thru TWRP . . after reboot nothing showed up in all apps (no Magisk) . . not sure if I'm doing it correctly !!! . . . However, I then reset the box and also reinstalled the rom to have a clean installation.

Any guidance on installing Magisk for Safety Net Pass on Play Store to have a certified device would be greatly appreciated, if this is at all possible
Thanks :)


New member
Feb 26, 2021
I had to do an account to thank you so much.
Finally i passed safetynet at mine Xiaomi mi 10 lite 5g.

Thank you sososo much. Finally i am able to install MCDonalds app and use GpAy


Jan 17, 2017
Unluckily it doesn't work for me, but maybe it's normal.

Device: Asus Zenfone Max Pro M1
OS: LineageOS 16.0-20210112-microG-X00TD (basically it's lineageOS with microG)
DroidguardHelper installed, however I cannot hide it in magisk hide. If I try, next time I check in Magisk Hide it's always not hidden.

I have Magisk Manager hidden and magisk hide active on all my banking apps and safety net checker apps.

Before installing safety net fix, banking apps and fingerprints on them would work. But it would fail attestation, and I suppose that's the reason why apps like Pokemon go wouldn't work.

I installed safety net fix 1.1.1 but attestation sfill failed. But fingerprints didn't work anymore on banking apps.

I installed safety fix 2.0 test 2 and now fingerprints work again, however attestation still fails.

I haven't found much about how to fix basic integrity, however I suspect it might be related to the ROM I'm using and/or microG.

Does anyone know why this happens and if there's any way to fix it?

Thanks in advance


  • AttestationFailed.png
    43.6 KB · Views: 11
Last edited:


New member
Feb 27, 2021
Hi all, tried safetynet fix 1.1.1 in Magisk 22.0. Now safetynet test is passed, but Google pay still doesn't work (your device doesn't meet....).

My phone is Xiaomi mi 10TPro with MIUI 12.1.2.

Any idea ?

Thank you in advance !
Last edited:


Recognized Contributor
Apr 20, 2012
Google Pixel 3a
Does anyone know why this happens and if there's any way to fix it?

Thanks in advance

You're failing basic integrity. This module is only to bypass hardware attestation. I would suggest checking to see what is making you fail basic integrity. A good guess would be your device fingerprint. MagiskHideProps is a good module to use a certified fingerprint.


Jan 17, 2017
You're failing basic integrity. This module is only to bypass hardware attestation. I would suggest checking to see what is making you fail basic integrity. A good guess would be your device fingerprint. MagiskHideProps is a good module to use a certified fingerprint.

Thanks for the tip. Unluckily I already have tried to change my fingerprint with the latest certified fingerprint for my device and it didn't work.

I don't have xposed. I tried to disable all magisk modules that I have (aurora services, systemizer), still didn't work.

I have quite a few apps that need root (Adaway, warden, and others) but I don't think they could cause problem, right?

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    i don't understand which is why i ask
    can explain it like...erm....i'm 5?
    Hardware attestation can't be fooled, but kdrag0n figured out how to make it fall back to basic, which can be fooled. That's what this module does.
    Wasn't aware of any Updates. Would be nice to get an Updated Thread Title from time to time...
    Pull request is beyond me ATM, so I submitted as an issue... 😜 PW
    Login to GitHub, go to README, press edit, it'll do the rest for you pretty much.
    I flashed this Magisk module on my OnePlus 5T running on Android 10 with Oxygen OS. I'm still not able to pass safetynet check. What should I do?
    OnePlus 5T and 6T are old enough that they do not need this module.
    They do not have the hardware to support hardware attestation

    Make sure MagiskHide is running.
    If it is on, toggle it off and on to restart it.

    Since you are running stock OxygenOS, MagiskHide is enough to pass SafetyNet.

    If you still have problems, it would be better to ask in the Magisk General Support / Discussion - xdaThread - Link

    Cheers. :cowboy:

    I double checked on my 5T running OOS 10.0.1 ;)
    GitHub link from OP:
    Android versions 7–12 are supported, including OEM skins such as Samsung One UI and MIUI. This is a Riru module, so Riru must be installed in order for it to work.

    Latest release
    kdrag0n released this 18 days ago

    Fixed under-display fingerprint on OnePlus devices (@osm0sis)

    kdrag0n released this 20 days ago

    Fixed new SafetyNet CTS profile failures as of September 2, 2021
    Added MagiskHide features that will be removed in future versions of Magisk

    kdrag0n released this 27 days ago

    Added support for heavy OEM skins (One UI, MIUI, etc.)
    Added support for Android 12 Beta 4 and future versions
    Android 12: Fixed face unlock on Pixel 4 series
    Added support for Android 7.0 and 7.1
    Rewritten as a Riru module



    kdrag0n released this on 14 Jan

    Added support for Android 8.0, 8.1, 9, and 10
    Increased chances of passing SafetyNet on older devices

    👍 PW
  • 217
    Universal SafetyNet Fix
    Magisk module​

    This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. The only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.

    Passing basic attestation is mostly out-of-scope for this module; this module is meant to defy hardware attestation, as well as reported "basic" attestation that actually uses hardware under-the-hood. Nonetheless, it features a few basic attempts at helping pass basic attestation on some devices, especially older devices and devices running stock ROMs.

    No device-specific features (such as the new Pixel-exclusive Google Assistant design or screen-off voice match) will be lost with this fix.

    Android versions 8–11 are supported. Heavy OEM skins are not officially supported, but they may work depending on your luck and the particular ROM in question. Please do not report problems on such ROMs.

    How does it work?
    The way this workaround works is relatively low-level. An in-depth explanation, as well as source code and ROM changes, can be found on GitHub.

    Ideally, this workaround should be incorporated in ROMs instead of overriding part of the ROM in a Magisk module. The ROM changes for it are linked above for ROM developers to use.

    Downloads and changelogs can be found on GitHub. The topmost release is the latest.

    Telegram group
    Source code

    If this helped you, please consider donating to support development: recurring donation for sustainable support or buy me a coffee. Thank you for your support!
    ok so there is a solution

    get the magisk module riru

    after you get riru get LSPosed

    after you get LSPosed get xprivacylua (in the LSPosed app)

    select play services in the xprivacylua settings IN the LSPosed app

    AND in the xprivacylua app itself after you've restarted.

    clear play service data

    check safetynet in magisk - enjoy?

    I would reboot between each step just to be safe but I know it's necessary to load the xprivacylua module

    s/o to saitama_96 for discovering it or so I'm led to believe
    I managed to fix the 3rd party app fingerprint issue on my Samsung w/ Android 10 (commented on this Github issue too). Basically the AOSP keystore is not fully compatible with the Samsung one so I decided to binary patch the one on my phone and ended up with this module. Now both fingerprint and SafetyNet works.
    - This disables key attestation for every app, idk if it breaks anything, nothing broke so far
    - Only change is the replaced system_sdk29/bin/keystore with the Samsung one (8 bytes modified)
    - Only works on Android 10
    - Might or might not work for you, use at your own risk.
    v2.1.0 is officially released and open sourced now, so everyone can stop being ****ing babies. 😏👍

    Anyone who installs Riru, deserves everything that happens to them.

    Anyone who pays a clown for broken amateur hour nonsense, also deserves everything that happens to them.

    This project has dramatically veered into a wall, and the torrent of mockery that is sure to follow, is well deserved.
    You're way off, and have cited no proof!

    I'll mention what we know - with no citations either as these will no doubt be lost on you also. - It may help those facing issues however.

    This fix seems to be working well on all but some custom ROMs like Pixel Experience etc. that already manipulate props in custom utils; these will apparently need fixing by their devs internally, and @Displax has already supplied a needed commit on GitHub. This and other issues may in part be why official LineageOS and many other custom OS's don't manipulate / spoof etc as a matter of policy... And who knows?, dev may also find an external solution for this yet!

    Other custom ROM users should find this works fine, but will likely need to set a certified fingerprint in MagiskHide Props Config module in addition.

    Riru's inject into zygote ability allows USNF to be more powerful, eg to target only Google Play Services with changed props to trigger the needed fallback to basic attestation, and not make the change global, which is causing many issues for users of other fixes that change model props etc, such as loss of device / OEM specific functionality (Galaxy Store, backup solutions, camera functions etc etc).

    In any case, it seems Riru is just a stop-gap solution and that this dev will move to John's new Zygisk asap or practical.

    The dev, @kdrag0n has clearly invested much time and effort in these S/N fixes. Most have been using them for a good while for free and would be pretty much up the creek without a paddle w/o them. No-one made him supply them as Magisk modules for all either; They were originally developed for his Proton ROMs...

    The new 'early releases' for his Patreon supporters will clearly generate only token recompense for his effort, and have so far become public and free in short order in any case.

    If you took the time to check facts, you would discover that these fixes are not only the best of the bunch, but are professionally coded and avoid the issues of most if not all others. A boon for the modding community.

    @kdrag0n deserves accolades and thanks from any modders worth their salt... He has mine.

    Sorry if this seems like a torrent of retorts, but I think they are well deserved... and I ain't mocking...

    It would be big of you to take back your .......... words. PW