“Ah Sh*t, Here We Go Again”. Well, it seems this conundrum is never going to end. Initially, it all started with the SafetyNet check which was then depreciated for the Play Integrity API and now we have an even more strict addition to this check- the New A13+ Play Integrity Check. So what exactly is this check all about and more importantly, how can you pass it? Let’s find out.
Table of Contents
What’s Play Integrity Check?
In simpler terms, the Play Integrity Check consists of three tests- Device, Basic, and Strong. If you unlock the bootloader, root your device, and/or flash a custom ROM then you are bound to fail these tests. So what’s the issue with that? Well, most of the banking and payment apps require you to pass at least the first and second tests [with that said, a few apps have even started asking for the Strong one].
To pass the Device and Basic test, you need to root your device and flash a couple of modules including the all-important Play Integrity Test. And if you are looking to pass the String test as well, then you’ll need an unrevoked keybox XML file as well [which we tend to provide to everyone via this guide!]. So what’s changing now? Let’s find out!
What’s the New A13+ Play Integrity Check
Play Integrity verdicts – that is, the MEETS_..._INTEGRITY labels – are changing for all devices running Android 13 or higher versions. The developers have been given a time frame of until May 2025 to implement this new verdict or else Google will automatically implement it across all the apps. The biggest change that you all going to notice once this new check is enforced is with the Device test.
The Meets_Device_Integrity will now require a locked bootloader signed by a certificate chain that points back to Google’s Hardware Attestation root CA key. 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. Here’s the changelog from Google’s Play Integrity site:
| What | What’s changing | Estimated impact* | Which devices |
|---|---|---|---|
| Device verdict response: meets-device-integrity | Required to have a hardware-backed, positive verified boot verdict | Minimal impact because Play Integrity API already uses hardware-backed security signals on Android 13 or later devices (~0.4%) | Android 13 and later |
| App integrity response: App recognition verdict | No change | Minimal impact, this will mirror the change in the device verdict (~0.4%) | Android 13 and later |
| Account details response: Play license verdict | Requesting app must be installed or updated by Google Play | Minor decrease in licensed responses (~2.5%) | Android 11 and later (this change will roll out gradually) |
How to Pass the New Android 13+ Play Integrity Check
To pass the new Android 13+ Play Integrity check, you will need to flash the Shamiko Module, LSPosed Framework, Play Integrity, Zygisk Assistant, and Tricky Store, and use an unrevoked keybox XML file, which will now [from May 2025] be required even to pass the Device Test as well, apart from the usual Strong Test. So you may refer to our detailed guide on this subject to pass this test right away:
So on that note, we round off this guide. 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.
