Yes, you read that write! Using a nifty workaround [or a loophole from Google’s end], you can now pass the Strong Integrity test even using a revoked/banned keybox XML file. One of the biggest issues with these keybox files is that they tend to get revoked within a week. Then I had to be on my toes, searching for a new unrevoked file, and sharing it with you.
While that’s fine, what isn’t is the fact that many people have started selling these files, and the users who are in utter desperation to pass the Strong test are left with no choice but to buy those files. Well, not anymore! Both my misery [searching for files] as well as the users [who were purchasing these files] are now finally coming to an end.
However, it goes without saying that this honeymoon period isn’t going to last long. Once Google finds out about it, it will patch it at the earliest. But until that happens, let’s extract maximum benefits out of it. Follow along.
Table of Contents
How to Pass Strong Integrity Using Revoked/Banned Keybox XML File
Before starting, please take a complete device backup. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device, and data by performing the below steps. [Credits: XDA Senior Member zgfg].
METHOD 1: Shorter One [Recommended]
- First off, uninstall Play Integrity Fix/Fork module that you have installed.
- Then, flash the Play Integrity Fix Inject Manual module onto your device.
- Now restart your device. Then install KSUWebUI and give it the SU access.
- Now launch it and select Play Integrity Fix [Inject]. Then tap on Advanced.
- Finally, enable the toggle next to Spoof Provider and check out the results.
METHOD 2: Lengthy One
- First off, get a banned/revoked keybox file from here. [See NOTE below].
- Then, uninstall the Tricky Store and Play Integrity Fix/Fork module.
- Now, launch a root-supported file manager app like Solid File Manager.
- Then head over to data/adb and delete the folder of tricky_store.
- Now, launch Magisk and flash the Tricky Store and Play Integrity Fork CI modules.
- As opposed to Play Integrity Fix, the Play Integrity Fork doesn’t automatically give us a fingerprint file [pif.json], so let’s manually invoke it from the module.
- For that, download and install wget2 [Credits: XDA Senior Recognized Developer / Contributor: osm0sis]
- Then install Termux, launch it, and execute the following commands:
su //you'll get a SU request, hit Grant cd /data/adb/modules/playintegrityfix //to change the directory to the module's sh autopif2.sh --preview // this will give you the fingerprint file
- Now launch Solid File Manager and head to the below location:
data/adb/modules/PlayIntegrityFix
- Open the custom.pif.json file, add the following values at the end, and save it.
// Advanced Properties "spoofBuild": "1", "spoofProps": "1", "spoofProvider": "1", "spoofSignature": "0", "spoofVendingSdk": "0", "verboseLogs": "0"
- Then go to the below location and create a blank security_patch.txt file:
data/adb/tricky_store
- In the same location, open the target.txt file.
- Then add the first two values and comment the third one via hash, as shown [you may leave the other values as it is]
android com.android.vending #com.google.android.gms
- Finally, hit Save. Now launch Play Integrity API Checker and check out the result. Three greens are all yours!
So on that note, we round off the guide on how you can pass the Strong Integrity test using a Revoked/Banned Keybox XML file. 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. And yes, before going, do check the all-important note regarding the keybox given below. [Credits for Method 2: XDA Senior Member zgfg].
An Important Note About Keybox
While the keybox can be banned or revoked, it should not be expired. To verify it, install Key Attestation from GitHub and check out the “not-after” date in the third paragraph [in our case, it is 16th April 2028]. Theoretically, if Google doesn’t find out this loophole, then we can use these keybox till 5-6 more years [I have a bunch of revoked keybox whose expiry date is 2030].
Moreover, you can also see in the very same paragraph, you can see that: revoked: Certificate revocation status is REVOKED, reason is KEY_COMPROMISE. This all but proves that we are using a revoked keybox XML file, and using that, we are passing the Strong Integrity test.
