Google SafetyNet attestation workarounds for Magisk
Go to file
Danny Lin cbb1681064 Revert "Revert Magisk update metadata"
This reverts commit 65bc7f072e.

The current implementation of dynamic fingerprint spoofing seems to work
well in practice, and I haven't received any issue reports so far. It
can be improved in a future release if necessary.
2023-01-09 09:49:29 -08:00
.github github: Fix typo in issue template 2022-06-27 02:36:19 -07:00
docs readme: Rewrite, split details for developers 2022-03-12 21:05:44 -08:00
java Dynamically patch build fingerprint in GMS process 2023-01-06 11:59:50 -08:00
magisk [NEXT RELEASE] Separate patchset 2023-01-06 12:01:21 -08:00
zygisk Update log tags 2022-12-06 20:26:20 -08:00
.gitattributes Create .gitattributes 2023-01-06 12:01:12 -08:00
.gitignore magisk: Add new module template 2021-10-30 17:51:53 -07:00
.gitmodules zygisk: Import Zygisk module template 2021-10-30 17:50:50 -07:00
build.sh java_module: Rename to java 2022-03-10 22:16:04 -08:00
CHANGELOG.md Revert "Revert Magisk update metadata" 2023-01-09 09:49:29 -08:00
LICENSE Remove Riru implementation 2021-10-30 18:33:29 -07:00
README.md version: 2.4.0 2023-01-06 11:59:56 -08:00
update.json Revert "Revert Magisk update metadata" 2023-01-09 09:49:29 -08:00

Universal SafetyNet Fix

Magisk module to work around Google's SafetyNet and Play Integrity attestation.

This module works around hardware attestation and updates to SafetyNet and Play Integrity CTS profile checks. You must already be able to pass basic CTS profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.

If you still have trouble passing SafetyNet or Play Integrity with this module, spoof the profile of a certified device by copying ro.product properties. MagiskHide Props Config is an easy way to do so on Magisk v23 and older. This is a common issue on old devices, custom ROMs, and stock ROMs without GMS certification (e.g. Chinese ROMs).

Android versions up to 13 are supported, including OEM skins such as Samsung One UI and MIUI.

Download

Download latest version

Install the downloaded module in Magisk Manager, then enable Zygisk in Magisk settings.

There is also a Riru version for Magisk 23 and older, but it is no longer updated. Please update to a current version of Magisk and use the Zygisk version.

How does it work?

See Details for details about how this module works.

ROM integration

Ideally, this workaround should be incorporated in custom ROMs instead of injecting code with a Magisk module. See the ProtonAOSP website for more information.

Support

If you found this module helpful, please consider supporting development with a recurring donation on Patreon for benefits such as exclusive behind-the-scenes development news, early access to updates, and priority support. Alternatively, you can also buy me a coffee. All support is appreciated.