Pass SafetyNet on Rooted Android 12/13

So, you’ve successfully rooted your Android 12 or Android 13 device, unlocking a world of endless possibilities and customization! However, with great power comes great responsibility—in this case, the challenge of passing the dreaded SafetyNet Test. Google’s SafetyNet API is specifically designed to detect modifications on your device and may restrict access to certain apps, like banking and streaming services if the test fails. But fear not! In this comprehensive guide, we will walk you through two highly effective methods to effortlessly breeze through the SafetyNet Test on your rooted Android 12 or 13 devices. By doing so, you’ll be able to explore a vast world of possibilities while ensuring your apps remain intact and fully accessible. So, let’s get started on this exciting journey!

What is SafetyNet on Android?

SafetyNet is Google’s watchful eye that safeguards the security and integrity of Android devices. When you root your device, it triggers a safety flag, prompting the SafetyNet Test. This test checks whether your device has been tampered with or modified in any way, and it’s a prerequisite for accessing certain apps that require a secure and unmodified environment.

Consequences of Failing the SafetyNet Test

Failing the SafetyNet Test can put a damper on your rooting adventure. Banking apps might refuse to cooperate, and streaming services could slam their doors shut, leaving you in the dark. Even games like Pokemon Go might throw a fit and refuse to play nicely.

Understanding Basic Integrity and CTS Profile Tests

Before we dive into the methods, let’s understand the two critical components of the SafetyNet Test:

• Basic Integrity Test: This checks the basic security of your device, including its bootloader status, system integrity, and official firmware usage.
• ctsProfile Test: The Compatibility Test Suite (CTS) profile ensures your device complies with Google’s compatibility standards and can work seamlessly with Google Play Services.

To pass the SafetyNet Test successfully, both the basic integrity and CTS profile tests must yield positive results.

How to Pass SafetyNet on Rooted Android 12/13

Below, we present two proven methods to successfully tackle the SafetyNet Test on your rooted Android 12/13 device:

Method 1: Pass SafetyNet using Magisk Hide Props Config [OLD]

This method employs the nifty Magisk Hide Props Config module to trick the system into thinking your device has basic authentication, making it easier to bypass robust hardware-based authentication.

Step 1: Install MagiskHide Props Configuration

• First, download the MagiskHide Props Config module from GitHub or XDA and install it through the Magisk App.
• Now, give your device a quick reboot to implement the changes.

Step 2: Force Basic Attestation

• Install a terminal emulator app like Termux on your device.
• Grant Superuser access and fire up the MagiskHide Props Configuration with the “su -c props” command.
• Choose option 2 to force BASIC key authentication.
• Select an appropriate value from the device list, such as the Nexus 6P or Pixel 3A.
• Reboot your device once again to activate the changes.

Step 3: Install the Riru Module

• Obtain the Riru module from GitHub and install it via the Magisk app.
• Give your device another reboot.

Step 4: Flash SafetyNet Fix

• Download the corresponding SafetyNet Fix module for your Android version.
  • Android 12: Universal SafetyNet Fix Magisk Module
  • Android 13: Modified SafetyNet Fix Module
• Install the module via the Magisk app.
• It’s time for yet another reboot.

Step 5: Enforce the Deny List and Enable Zygisk

• Navigate to the Magisk settings and enable both Zygisk and Enforce Deny List.
• You know the drill—reboot your device.

Step 6: Configure the DenyList

• Tap on “Configure DenyList” under Magisk Settings.
• Optionally, you can hide the root from specific user apps.
• Checkmark Google Play Protect Services, Google Play Services, Google Play Store, and any other apps you’d like.
• You guessed it—another restart is in order.

Step 7: Hide the Magisk App

• Still, under the Magisk settings, select “Hide the Magisk App.”
• Give it a quirky name and press OK.
• Why not? Add a home screen shortcut too for that extra convenience.

Step 8: Delete the Play Service and Play Store Data

• Head to Settings > Apps > See All Apps.
• Clear all data from the Google Play Service, Google Play Store, and Google Play Protect Service.

Step 9: Check SafetyNet Results

• Since the latest Magisk update removed the option to check SafetyNet, use a third-party app like YASNAC.
• Run the SafetyNet Attestation in YASNAC and revel in your “pass” results for both the basic integrity and CTS profile sections.

Method 2: Pass SafetyNet without Magisk Hide Props Configuration [NEW]

This new method is sleek and eliminates the need for Magisk Hide Props Config, thanks to the ingenious Universal SafetyNet Fix Module.

Step 1: Hide the Magisk App

• In the Magisk settings, enable “Allow apps from this source.”
• Rebrand the Magisk App with a random name, and, hey, why not add a home screen shortcut?

Step 2: Enable Systemless Hosts

• Go back to the Magisk settings and enable “Systemless hosts.”

Step 3: Enable Zygisk

• One more time, enable Zygisk in the Magisk settings and give your device the customary reboot.

Step 4: Flash the Universal SafetyNet Fix Module

• Download the fresh Universal SafetyNet Fix module.
  • SafetyNet-fix-v2.3.1.zip
  • SafetyNet Fix module v2.3.1-MOD_3.0 [NEW]
• Install the module through the Magisk app.
• Yes, you guessed it—another reboot is required.

Step 5: Configure the Denylist

• Enforce the Denylist through the Magisk settings and tap on “Configure Denylist.”
• Checkmark Google Play Service, Google Play Store, Google Service Framework, and any other apps of your choosing.
• Not again—you know the drill; restart your device (mandatory this time).

Step 6: Delete data.

• Erase the app data of Google Play Service, Google Play Store, Google Play Protect Service, and any other apps from which you’ve hidden a root.
• Restart your device one more time (don’t worry, we’re almost there).

Step 7: Check SafetyNet Results

• Use YASNAC or a similar app to check SafetyNet results. Smile as both the basic integrity and CTS profile sections proudly display “pass.”

Update for Android 13

For Android 13 devices, select Pixel 3 as the device and Android 10 as the OS in Step 2.

Conclusion

Rooting your Android device can be an exciting journey, but it comes with its own set of challenges. Thanks to these two effective methods, you can now embrace the freedom of root access while keeping your essential apps intact. Always remember to proceed with caution and follow the steps diligently to avoid any potential issues.

Frequently Asked Questions (FAQs).