How to Pass Google Verification

What is Google Three-Level Verification

Google Three-Level Verification typically refers to the device integrity checking mechanism in Google's Play Integrity API, used to verify the integrity of Android devices to ensure the security of both the device and its applications.

The Play Integrity API evaluates whether a device meets three levels of integrity requirements: Basic Integrity, Device Integrity, and Strong Integrity.

1. Basic Integrity
   The most fundamental level of integrity check, based on software verification, ensuring the device runs an untampered Android system with no obvious signs of system compromise.

2. Device Integrity
   A stricter check than Basic Integrity, verifying whether the device is Google-certified and running certified Android firmware.

3. Strong Integrity
   The highest level of integrity check, relying on hardware-backed verification (e.g., Trusted Execution Environment, TEE), ensuring the device runs an untampered official Android system.

Why is Google Verification Necessary?

Most overseas applications use Google's detection methods to verify devices, which reduces development costs for countermeasures and enhances application security. By passing Google’s three-level verification, users can normally use most applications that rely solely on Google’s detection mechanisms.

How to Check the Current Google Verification Status

You can test the status by installing apps such as Play Integrity API Check or TB Checker.

These apps can be searched and installed directly from the platform’s app store. If you encounter crashes, it may be due to an outdated version of the detection app; downloading and installing from Google Play should resolve the issue.

By default, cloud devices pass Basic Integrity (except for Android 15, which requires keybox.xml to pass verification), as shown in the images below:

What is keybox.xml

The keybox.xml is a file containing device key information, typically associated with the Android device's Trusted Execution Environment (TEE). It stores cryptographic keys (attestation keys) and other metadata used to prove the device’s identity and integrity. It is primarily used to support Strong Integrity checks.

Google servers verify the keys and certificates in the keybox.xml to confirm whether the device is unrooted, has a locked bootloader, and is running certified Android firmware.

How to Obtain keybox.xml

There are multiple channels to obtain keybox.xml, and the validity of the file varies depending on the source. For instance, publicly available keybox.xml files may have a short validity period due to widespread testing, potentially becoming invalid within days or weeks.

1. For simple self-testing: You can extract it from open-source projects, such as TrickyStore. After flashing it onto a real device, you can extract the keybox.xml file from the path /data/adb/tricky_store/keybox.xml for use. Alternatively.
   you can download files provided by certain websites or modules, such as root.zip.
2. For large-scale use: Purchase channels can be found on Telegram.
3. For stable and large-scale use: Collaborate with phone manufacturers, as their keybox.xml files are more stable and long-lasting.

How to Pass Google Verification

Currently, passing the three-level verification requires the use of a keybox.xml certificate file. This certificate needs to be uploaded to the /data/misc/google directory. After rebooting the cloud device, the verification can be achieved.
Alternatively, you can upload the file to the specified location using ADB commands:

adb connect xx.xx.xx.xx
adb push '~/tools/android/google/keybox.xml'  /data/misc/google/

After rebooting the cloud device, check again to see the results, as shown below: