In this guide, we will show you the steps to pass the Play Integrity Test in the New Android 13+ Checks. A lot is going on in custom development for the past few years. Initially, we were greeted with the SafetyNet fiasco which straightaway failed as soon as you rooted your device. As soon as we found a workaround for it, Google went a step ahead and introduced a more stringent mechanism in the form of Play Integrity.
This in turn consists of three tests- Device, Basic, and Strong. For the first few months, you just needed to pass the Device and Basic test, which in turn could be carried out by flashing a couple of modules. However, over the course of time, banking and payment become strict and some now require you to pass the Strong Test as well.
For the unaware, this requires you to get hold of an unrevoked keybox XML file, which not only is quite a tough job in itself but gets revoked within a few days as well. All in all, things are currently quite messy in the rooting domain. But the Silicon Valley giant doesn’t stop here and wants to make things even more complicated.
It has introduced even stricter rules for devices running Android 13 or higher versions, which now require some additional tweaks, apart from the usual steps that we earlier used to carry out. Even then, the success rate of this tweak is currently on the lower side. Still, let’s give this tweak a try and see if we are on the lucky side of the fence or not. Follow along.
Table of Contents
What are the New Android 13+ Play Integrity Checks
Before we proceed to pass this new test, let’s get acquainted with its technicalities and what is changing this time around. So without any further ado, let’s dive into it right away!
The first question that you might ask is “What changes are being made to the Play Integrity API verdicts on Android 13 or later devices?” Let’s find out, straight from the mouth of Google:
Play Integrity API will now require hardware-backed security signals for all integrity verdicts, namely: Device, Basic, and Strong. In simpler words, the Device Integrity will now also require an unrevoked keybox XML file to pass the Play Integrity Test, similar to how Strong Integrity currently works. To know more about this change, do check out this guide.
Next up, why is there a need to introduce this change in the first place?
After making changes to these integrity verdicts, Google has said that one might notice the following improvements on devices running Android 13 or later:
Reduction in device signals that need to be collected and evaluated to generate the default verdict on Google servers by ~90%. Optional signals will continue to require additional signals to be collected.
Improvement in verdict latency by up to 80% for worst-case standard requests and up to 80% for all classic requests to obtain the default verdict. Optional signals can increase the latency.
Consistent level of reliability and support for all Android form factors with key attestation including mobiles, tablets, foldables, TV, Auto, Wear OS, and ChromeOS.
A greater differentiation between each device label in the device recognition verdict:
meets-strong-integrity,meets-device-integrity, andmeets-basic-integrity.Moreover, there might also be a gradual improvement in performance once the new verdicts are made compulsory for all developers in May 2025
How to Pass Play Integrity in New Android 13+ Checks
- To begin with, carry out all the steps mentioned in this guide.
- This should make you pass the current/old Strong Integrity.
- Now, to pass the new test, download the Tricky Store add-on.
- Next up, flash the module via Magisk and restart your device.
- Go to Modules tab of Magisk > tap Actions next to Tricky Store.
- This will open the KsuWebUI. Hit Grant in the Magisk request.
- Then checkmark the following three apps > Hit Save > Restart.
Google Play Service Google Play Store Google Services Framework
- Then download and install the Play Integrity API Checker app.
- Now launch it, tap Check, and enable New Android 13+ Checks.
- The device should now pass all three tests [Device, Basic, Strong].
What is the Role of Tricky Store Add-On
Tricky Store add-on is an unofficial open-source app that allows you to configure the Tricky Store target.txt file. So instead of manually heading to the data/adb/tricky_store directory, opening the target.txt, and then typing the required app package name, you can simply checkmark the said app in KsuWebUI [which comes into action thanks to this add-on]. Apart from that, this module also allows you to fetch the latest unrevoked pif.json file and place it in the required directory [data/adb/pif.json]m thereby saving a considerable amount of time and effort.
That’s it. These were the steps to pass the Play Integrity Test in the New Android 13+ Checks. This is a developing story and will be updated on a regular basis. So do keep a tab on the same at frequent intervals. Moreover, if you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution as soon as possible.
