Google SafetyNet attestation workarounds for Magisk
Go to file
Danny Lin 73c8587a80 Dynamically patch build fingerprint in GMS process
"AndroidCAStore" always seems to be used early in the attestation
process, before the fingerprint is checked.

Dynamic patching avoids problems with device detection and functionality
that can be caused by permanently spoofing another device.

Closes #207, closes #224, closes #222, closes #220, closes #218, closes #212, closes #211, closes #210, closes #204, closes #203, closes #201, closes #196, closes #188, closes #171, closes #170
2023-01-06 11:59:50 -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 service: Set shipping level to 32 for devices >=33 2023-01-01 04:50:49 -08:00
zygisk Update log tags 2022-12-06 20:26:20 -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 changelog: Label footer 2022-06-27 03:30:47 -07:00
LICENSE Remove Riru implementation 2021-10-30 18:33:29 -07:00
README.md readme: Update Android version compatibility 2022-06-27 03:04:34 -07:00
update.json version: 2.3.1 2022-06-27 02:58:11 -07:00

Universal SafetyNet Fix

Magisk module to work around Google's SafetyNet attestation.

This module works around hardware attestation and recent updates to SafetyNet 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 with this module, use MagiskHide Props Config to spoof a certified device profile. 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 Beta 3 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 v23 and older.

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.