2025 may patch

[apppeter1]

https://www.reddit.com/r/PoGoAndroidSpoofing/comments/1ikqi3x/2025_strong_integrity_end_of_rooted_devices_end/
This say there will be a patch in 2025 may. Is there a solution?

[DanGLES3]

https://www.reddit.com/r/PoGoAndroidSpoofing/comments/1ikqi3x/2025_strong_integrity_end_of_rooted_devices_end/ This say there will be a patch in 2025 may. Is there a solution?

The solution is the same as it always been, though now Tricky Store and a valid/private keybox will be mandatory

Play Integrity Fix alone won't get around the new checks as the old device integrity (that just relied on fingerprints) will no longer work

TL;DR New checks

New Basic Integrity = Old Device Integrity

New Device Integrity = Old Strong Integrity

New Strong Integrity = Old Strong but requires the device to have an updated security patch

[apppeter1]

If I need to buy a tickystore key box, can you tell me where to buy it?

[DanGLES3]

If I need to buy a tickystore key box, can you tell me where to buy it?

You shouldn't buy keyboxes. Most people that are selling these are not trustworthy and will likely scam you completely or give you a stitched up keybox that won't last

Even if the keybox that they sell you is legitimate, there is no guarantee that they won't sell the same keybox to other people, thus killing it faster

[apppeter1]

What is my problem? I have to install more module? I have valid keybox

[DanGLES3]

What is my problem? I have to install more module? I have valid keybox

On the new A13 checks you also need an updated security patch, the latest version of Tricky Store can spoof that, just follow the guide

https://github.com/5ec1cff/TrickyStore#customize-security-patch-level-121

[apppeter1]

Is it impossible to pass both at the same time?

[apppeter1]

It's like this right now

[icewyvrn]

how did you fixed it?

[markfm62]

Is there a writeup anywhere on how to extract/process a keybox from a beta build?

For example, starting from cheetah_beta-bp11.241210.004-factory-430bc869.zip, which .img/folder_path/file has the necessary information that needs to be pulled, with data then used in a TS .xml file?

Thanks!

[HarriBuh]

@apppeter1 How did you fix it ?

[kam821]

Is there a writeup anywhere on how to extract/process a keybox from a beta build?

For example, starting from cheetah_beta-bp11.241210.004-factory-430bc869.zip, which .img/folder_path/file has the necessary information that needs to be pulled, with data then used in a TS .xml file?

Thanks!

No, you can't take the keybox out of the beta build because it's not there.
It's stored inside trusted environment part of the device and was installed there by the manufacturer during the production process and no, you can't take it out.

[markfm62]

No, you can't take the keybox out of the beta build because it's not there. It's stored inside trusted environment part of the device and was installed there by the manufacturer during the production process and no, you can't take it out.

Thank you for clarifying. I'd run across multiple references to "AOSP sw keybox", had misunderstood that, thought that there might have been something buried in the Beta builds.

[kam821]

No, you can't take the keybox out of the beta build because it's not there. It's stored inside trusted environment part of the device and was installed there by the manufacturer during the production process and no, you can't take it out.

Thank you for clarifying. I'd run across multiple references to "AOSP sw keybox", had misunderstood that, thought that there might have been something buried in the Beta builds.

AOSP software attestation keybox is well-known and publicly available.
You can find it e.g. in the Tricky Store module zip as TS uses it by default.
However, this keybox does not provide STRONG attestation result (even legacy) and in combination with the current version of the PlayIntegrityFork - results in the lack of the BASIC A13+ attestation result if com.android.vending is added to the TS target.txt list.