[MODULE] Play Integrity Fork (PIFork)

osm0sis · Sep 26, 2025

Play Integrity Fork (PIFork)

Play Integrity Fix (PIF), forked to be more futureproof and develop more methodically

General Information:

A Zygisk module to fix Play Integrity Android <13 verdicts, allowing custom Build fields and system props entries for advanced configuration. On Android 13+ ROMs it still helps to pass checks in Google Wallet and Google Messages RCS support.

I'm not going to duplicate too much information here, but I will introduce a few posts as part of the OPs, documenting current known working configurations or walkthroughs for initial setup that would be too difficult to maintain in the GitHub README, and hopefully making that information always easy to find and digest!

Please see (and read) the full Required Reading and Thread Rules sections below before posting, and if asking for help please post your full setup using PixelFlasher's PI Analysis Report feature.

My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!

Downloads:

Releases:

Releases · osm0sis/PlayIntegrityFork

Fix Play Integrity <A13 verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

Latest CI Builds:

Workflow runs · osm0sis/PlayIntegrityFork

Fix Play Integrity <A13 verdicts, allowing custom fields and props - Workflow runs · osm0sis/PlayIntegrityFork

github.com

(GitHub account required)

nightly.link | Repository osm0sis/PlayIntegrityFork | Workflow android.yml | Branch main | Artifact PlayIntegrityFork-CI_#559

nightly.link

(No account required)

Required Reading Before Posting:

PIF & TS FAQ:

PIF & TS FAQ

PIF FAQ Abbreviations DG = DroidGuard (GMS process for SafetyNet/

xdaforums.com

This and TS thread OPs:

[MODULE] Play Integrity Fork (PIFork)

Play Integrity Fork (PIFork) Play Integrity Fix (PIF), forked to be more futureproof and develop more methodically General Information: A Zygisk module to fix Play Integrity Android

xdaforums.com

Tricky Store - Bootloader & Keybox Spoofing

IMPORTANT: I'm not the dev. of this module or have any affiliated with the dev. So a Big Thanks to the devs (5ec1cff & aviraxp) of this great module. All the credits for the images and apps and modules, go to the original devs. (I only share...

xdaforums.com

PIFork README:

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity <A13 verdicts, allowing custom fields and props

Fix Play Integrity <A13 verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

Tricky Store or TEESimulator README:

GitHub - 5ec1cff/TrickyStore

Contribute to 5ec1cff/TrickyStore development by creating an account on GitHub.

github.com

GitHub - JingMatrix/TEESimulator: Software simulation for Android hardware-backed key pairs with key attestation

Software simulation for Android hardware-backed key pairs with key attestation - JingMatrix/TEESimulator

github.com

Thread Rules:

This thread will be strictly moderated and any posts not following the rules may be removed!
- No posts asking about or duplicating anything covered in the Required Reading listed above.
- Don't quote an entire OP contents when replying/asking questions.
- People should always check both keybox and print before posting that one of them (or the module) has stopped working.
- Posts about non-PI app issues once PI is working are not allowed.
- No unnecessarily long repeat explanations when linking to a previous post will suffice, especially on technical topics/documentation.
- No heated arguing, or rehashing of grievances, kindly take it to PM.
- Posts promoting other Play Integrity Fix (PIF) forks are not allowed.

Source Code and Credits:

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity <A13 verdicts, allowing custom fields and props

Fix Play Integrity <A13 verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

Archival Credit Links:

Forked from chiteroman's Play Integrity Fix (PIF):

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

web.archive.org

(Archive.org backup since chiteroman removed it from GitHub)

🔧 [MODULE] Play Integrity Fix

PLAY INTEGRITY FIX I've decided to discontinue the PIF project. Google is increasingly putting up more obstacles, and I no longer have as much time to dedicate to this as I used to. It's been a very interesting journey, and I've learned a lot...

xdaforums.com

(Former thread)

osm0sis · Sep 26, 2025

Latest Working Solutions:

Useful Combinations:

Pixel Beta/Canary print passing <A13 PI STRONG in PIFork with an unrevoked keybox in a TS module. (Passes <A13 PI STRONG, A13+ PI STRONG, Wallet, RCS.)
Private print passing <A13 PI STRONG in PIFork with an unrevoked keybox in TrickyStore for Wallet also allows working RCS (if not banned for RCS), but since these prints' *.security_patch are >11 months old and required to match TrickyStore system= in security_patch.txt this can only achieve A13+ PI DEVICE. (Passes <A13 PI STRONG, A13+ PI DEVICE, Wallet, RCS.)
Private print passing <A13 PI STRONG in PIFork with an unrevoked keybox in TEESimulator for Wallet also allows working RCS (if not banned for RCS), and with TEESimulator system= matching *.security_patch or omitted for only GMS in security_patch.txt since >11 months old can still pass A13+ PI STRONG. (Passes <A13 PI STRONG, A13+ PI STRONG, Wallet, RCS.)
Private print passing <A13 PI DEVICE in PIFork for Wallet also allows working RCS (if not banned for RCS), and works with any keybox status in a TS module. (Passes <A13 PI DEVICE, A13+ PI per keybox/security_patch, Wallet, RCS.)

Known A13+ PI Strong Flaws:

~~Unexpired revoked/shadowbanned keybox in TS with spoofProvider=1 in PIFork, but without a private print also passing <A13 PI DEVICE in PIFork Wallet will not work.~~ Patched Nov. 11/25.
~~spoofVendingFinger=[Pixel Beta/Canary FINGERPRINT value] in PIFork, but without a private print also passing <A13 PI DEVICE in PIFork Wallet will not work.~~ Patched Nov. 21/25.

Known Issues From Recent PI Changes:

Starting Dec. 12/25, A13+ Devices on the Google Play System Update for November 2025 and later are no longer able to use spoofVendingSdk=1 to check the <A13 PI verdict, and attempts may have no effect (sdkVersion unchanged in the PI response) and/or instead result in only passing A13+ PI BASIC or an A13+ PI FAIL depending on device setup/conditions.

PI Monitored Properties:

When setting verboseLogs=100 in your custom.pif.prop the PIF logcat will show every Build field your ROM supports, as well as everything DroidGuard is checking in system properties on your ROM setup. The current list of checked properties I've seen of interest are as follows:

Code:

build.version.extensions.ad_services
build.version.extensions.b
build.version.extensions.c
build.version.extensions.r
build.version.extensions.s
build.version.extensions.t
build.version.extensions.u
build.version.extensions.v
init.svc.adbd
persist.graphics.egl
persist.sys.gameprops.enabled
persist.sys.knox.userinfo
persist.sys.oplus.region
persist.sys.pif
persist.sys.pihooks_DEBUG
persist.sys.pihooks_mainline_BRAND
persist.sys.pihooks_mainline_DEVICE
persist.sys.pihooks_mainline_FINGERPRINT
persist.sys.pihooks_mainline_MANUFACTURER
persist.sys.pihooks_mainline_MODEL
persist.sys.pihooks_mainline_PRODUCT
persist.sys.pihooks.disable.gms_key_attestation_block
persist.sys.pihooks.disable.gms_props
persist.sys.pihooks.first_api_level
persist.sys.pihooks.security_patch
persist.sys.pixelprops.all
persist.sys.pixelprops.games
persist.sys.pixelprops.gapps
persist.sys.pixelprops.gms
persist.sys.pixelprops.gphotos
persist.sys.pixelprops.pi
persist.sys.pp.gms
persist.sys.pp.photos
persist.sys.pp.tensor
persist.sys.timezone
persist.sys.usb.config
ro.board.api_level
ro.board.first_api_level
ro.boot.flash.locked
ro.boot.hardware.revision
ro.boot.vbmeta.digest
ro.boot.vbmeta.device_state
ro.boot.verifiedbootstate
ro.build.characteristics
ro.build.id
ro.build.release_type
ro.build.stock_fingerprint
ro.build.type
ro.build.version.oplus.api
ro.build.version.oplus.sub_api
ro.build.version.oplusrom
ro.build.version.oplusrom.confidential
ro.build.version.ota
ro.build.version.sdk
ro.build.version.security_patch
ro.config.tima
ro.config.timaversion
ro.debuggable
ro.gfx.driver.0
ro.gfx.driver.1
ro.hardware.egl
ro.oplus.image.my_stock.type
ro.product.device
ro.product.first_api_level
ro.product.mod_device
ro.product.vndk.version
ro.secure
ro.separate.soft
ro.superior.device
ro.treble.enabled
ro.vendor.api_level
ro.vendor.build.version.sdk
ro.vendor.oplus.market.enname
ro.vendor.oplus.market.name
ro.vendor.oplus.regionmark
ro.version.confidential
ro.vndk.version
ro.zygote
sys.boot_completed
sys.eliteprops.games
sys.eliteprops.pif
sys.usb.config
sys.usb.state

Of course a lot of the list doesn't seem to be currently enforced, and the ones that are we handle globally or in the custom.pif.prop, but just be aware that more could at some point and this is how you can check them.

osm0sis · Sep 26, 2025

PI Verdicts:

Notes: These are with TS and PIFork default/recommended settings. Other combinations are possible with altered TS target.txt and security_patch.txt where com.google.android.gms is <A13 PI and com.android.vending is A13+ PI, and using PIFork Advanced Settings. The PI internal CRLs and Shadowbanned/Soft-banned lists (<A13 PI and A13+ PI each have both) can also be out of sync with eachother and Google's public CRL, which then leads to varied results. TEE broken devices (teeBroken=true in tee_status in TS) may also have some differing results (generally FAIL instead of BASIC) in some cases.

Revoked Keybox + Strong Beta/Private Print Config (spoofProvider=0):
<A13 PI BASIC / A13+ PI FAIL / KA REVOKED

AOSP Keybox + Strong Beta/Private Print Config (spoofProvider=0):
<A13 PI BASIC / A13+ PI FAIL / KA AOSP

Shadowbanned Keybox + Strong Beta/Private Print Config (spoofProvider=0):
<A13 PI DEVICE / A13+ PI DEVICE / KA HARDWARE

Unrevoked Keybox + Strong Beta/Private Print Config (spoofProvider=0) + ROM *.security_patch/os_patch_level >11 months old:
<A13 PI STRONG / A13+ PI DEVICE / KA HARDWARE

Unrevoked Keybox + Strong Beta/Private Print Config (spoofProvider=0) + ROM *.security_patch/os_patch_level <12 months old:
<A13 PI STRONG / A13+ PI STRONG / KA HARDWARE

Revoked Keybox + Device Private Print Config (spoofProvider=1):
<A13 PI DEVICE / A13+ PI FAIL / KA REVOKED

AOSP Keybox + Device Private Print Config (spoofProvider=1):
<A13 PI DEVICE / A13+ PI FAIL / KA AOSP

Shadowbanned Keybox + Device Private Print Config (spoofProvider=1):
<A13 PI DEVICE / A13+ PI DEVICE / KA HARDWARE

Unrevoked Keybox + Device Private Print Config (spoofProvider=1) + ROM *.security_patch/os_patch_level >11 months old:
<A13 PI DEVICE / A13+ PI DEVICE / KA HARDWARE

Unrevoked Keybox + Device Private Print Config (spoofProvider=1) + ROM *.security_patch/os_patch_level <12 months old:
<A13 PI DEVICE / A13+ PI STRONG / KA HARDWARE

No Keybox or com.android.vending removed from TS target.txt:
A13+ PI BASIC

Broken/Bad Private or Beta Print Config:
<A13 PI BASIC and/or A13+ PI BASIC (due to separate/different allowed print lists)

Banned/Misconfigured Private or Expired Beta Print Config:
<A13 PI BASIC and/or A13+ PI BASIC (due to separate/different banned print lists)

Sideloaded PI API Checker app (to fix, reinstall from Play Store):
<A13 PI DEVICE with BASIC FAIL and/or A13+ PI DEVICE with BASIC FAIL

osm0sis · Sep 26, 2025

Important Links:

Information:

osm0sis - PIF & TS FAQ - Thread
osm0sis - PI Changes Timeline - Post
osm0sis - Banned Kernel Strings List - Post
osm0sis - RCS Fingerprint Ban Summary - Post
osm0sis - Private Fingerprint How-To Guide - Post
badabing2003 - UI Workflow Guide - Post
simplepinoi177 - Complete Noobs' Guide - Thread (Discontinued)
Vision - Apps & Games Needing PI List - Thread
V0latyle - Play Integrity API FAQ - Thread (Discontinued)
Vagelis1608 - Google CRL Changelog - Link

Scripts:

osm0sis - gen_pif_custom.sh - Post
osm0sis - migrate.sh - Link
osm0sis - autopif.sh - Post (Discontinued)
osm0sis - autopif4.sh - Link
TheFreeman193 - pickaprint.sh - Thread (Discontinued)
zgfg - pif-test-json-file.sh - Post
HippoMan - install-random-fp.sh - Thread
badabing2003 - kr_patch.sh - Post
TheFreeman193 - kr_offset.sh - Post
Vagelis1608 - settings.sh - Link

Tools:

1nikolas - Play Integrity API Checker App - Link
Vision - Key Attestation Fork App - Link
badabing2003 - PixelFlasher - Thread
Lord Sithek - Tasker PIF Testing Helper - Thread (Discontinued)
CZ.Kostra - Tasker/APK FP XEU Checker - Post (Discontinued)
CZ.Kostra - Tasker/APK FP BETA Checker - Post
CZ.Kostra - Tasker/APK spoofVendingSdk QSTile - Post

osm0sis · Sep 29, 2025

HippoMan · Nov 19, 2025

Thank you (!!!) for doing all of the work to create this thread!

osm0sis · Nov 19, 2025

HippoMan said:
Thank you (!!!) for doing all of the work to create this thread!

Only took a couple months of developing it in secrecy!

inkitiane · Nov 19, 2025

Nice, about time we got a new thread.

Fishawy · Nov 19, 2025

Finally

Thanks a ton!

simplepinoi177 · Nov 19, 2025

osm0sis said:
Only took a couple months of developing it in secrecy!

HippoMan said:
Thank you (!!!) for doing all of the work to create this thread!

Fishawy said:
Finally
Thanks a ton!

HERE HERE!

inkitiane said:
Nice, about time we got a new thread.

And with an SRD that is more active, present, and hopefully/probably with more scrutiny on the goings on in this/his-own thread

Lord Sithek · Nov 19, 2025

Excellent decision! It will be much less cluttered now

osm0sis said:
Lord Sithek - Tasker PIF Testing Helper - Thread

Actually I stopped working on this long time ago, when you came up with Pix Beta prints

but... if anyone feels it's still useful, I may reconsider

osm0sis · Nov 19, 2025

Lord Sithek said:
Excellent decision! It will be much less cluttered now

Actually I stopped working on this long time ago, when you came up with Pix Beta prints but... if anyone feels it's still useful, I may reconsider

As shown in the working combos in the OP, the private prints still very much have their place if people are willing to put in the work, so I think anything that facilitates bulk processing and testing of them is still of use. PixelFlasher and @zgfg's linked script from that same post can certainly be the main methods though if you like; I'll mark yours as Discontinued for now.

Vision · Nov 19, 2025

Finally!!!

Perfect organization!!!

kornball · Nov 19, 2025

Thanks so much! Really appreciate all your continued efforts for the community

Wolfcity · Nov 19, 2025

Just great!
It was about time, thank you very much for your efforts until now and in the future.

flyoffacliff · Nov 20, 2025

Thank you, it's great to see all the information finally in one place like this.

I started building a wiki site for all the play integrity stuff last year, but I never finished it. It was taking so much time and I got discouraged thinking no one would use it.

I don't use this anymore but I still like to pop in every few months to see how things are going, and every time it seems more complicated with new tools, settings, and exceptions to the rules. This is a big step forward.

I saw the rules said no discussion of related projects and forks. I just like to see what else is out there and the pros and cons. Is there a better thread for that?

osm0sis · Nov 20, 2025

flyoffacliff said:
Thank you, it's great to see all the information finally in one place like this.

I started building a wiki site for all the play integrity stuff last year, but I never finished it. It was taking so much time and I got discouraged thinking no one would use it.

I don't use this anymore but I still like to pop in every few months to see how things are going, and every time it seems more complicated with new tools, settings, and exceptions to the rules. This is a big step forward.

I saw the rules said no discussion of related projects and forks. I just like to see what else is out there and the pros and cons. Is there a better thread for that?

To be clear it says no promotion of other PIF forks, not that they can't be discussed at all; this allows for "cool fix X got added to fork Y, are you considering the same?" or "fork W did feature X like Y instead of yours' Z, how come?" type open, good faith conversation.

aorifan · Nov 20, 2025

osm0sis said:
PI Verdicts:

Notes: These are with TS and PIFork default/recommended settings. Other combinations are possible with altered TS target.txt where com.google.android.gms is <A13 PI and com.android.vending is A13+ PI, and using PIFork Advanced Settings. The PI internal CRLs and Shadowbanned/Soft-banned lists (<A13 PI and A13+ PI each have both) can also be out of sync with eachother and Google's public CRL, which then leads to varied results.

Revoked Keybox + Strong Beta/Private Print Config (spoofProvider=0):
<A13 PI BASIC / A13+ PI FAIL / KA REVOKED
View attachment 6287913 View attachment 6287912 View attachment 6287911

AOSP Keybox + Strong Beta/Private Print Config (spoofProvider=0):
<A13 PI BASIC / A13+ PI FAIL / KA AOSP
View attachment 6287913 View attachment 6287912 View attachment 6287907

Shadowbanned Keybox + Strong Beta/Private Print Config (spoofProvider=0):
<A13 PI DEVICE / A13+ PI DEVICE / KA HARDWARE
View attachment 6287914 View attachment 6287914 View attachment 6287909

Unrevoked Keybox + Strong Beta/Private Print Config (spoofProvider=0) + ROM *.security_patch/os_patch_level >11 months old:
<A13 PI STRONG / A13+ PI DEVICE / KA HARDWARE
View attachment 6287915 View attachment 6287914 View attachment 6287909

Unrevoked Keybox + Strong Beta/Private Print Config (spoofProvider=0) + ROM *.security_patch/os_patch_level <12 months old:
<A13 PI STRONG / A13+ PI STRONG / KA HARDWARE
View attachment 6287915 View attachment 6287915 View attachment 6287909

Revoked Keybox + Device Private Print Config (spoofProvider=1):
<A13 PI DEVICE / A13+ PI STRONG / KA REVOKED (Unexpired Keybox = A13+ PI Strong Flaw)
View attachment 6287914 View attachment 6287915 View attachment 6287911
<A13 PI DEVICE / A13+ PI FAIL / KA REVOKED (Expired Keybox = A13+ Expected Result)
View attachment 6287914 View attachment 6287912 View attachment 6287911

AOSP Keybox + Device Private Print Config (spoofProvider=1):
<A13 PI DEVICE / A13+ PI FAIL / KA AOSP
View attachment 6287914 View attachment 6287912 View attachment 6287907

Shadowbanned Keybox + Device Private Print Config (spoofProvider=1):
<A13 PI DEVICE / A13+ PI STRONG / KA HARDWARE (A13+ PI Strong Flaw)
View attachment 6287914 View attachment 6287915 View attachment 6287909
<A13 PI DEVICE / A13+ PI DEVICE / KA HARDWARE (A13+ Expected Result)
View attachment 6287914 View attachment 6287914 View attachment 6287909

Unrevoked Keybox + Device Private Print Config (spoofProvider=1) + ROM *.security_patch/os_patch_level >11 months old:
<A13 PI DEVICE / A13+ PI DEVICE / KA HARDWARE
View attachment 6287914 View attachment 6287914 View attachment 6287909

Unrevoked Keybox + Device Private Print Config (spoofProvider=1) + ROM *.security_patch/os_patch_level <12 months old:
<A13 PI DEVICE / A13+ PI STRONG / KA HARDWARE
View attachment 6287914 View attachment 6287915 View attachment 6287909

No Keybox or com.android.vending removed from TS target.txt:
A13+ PI BASIC
View attachment 6287913

Broken/Bad/Misconfigured/Banned Private or Expired Beta Print Config:
<A13 PI BASIC and/or A13+ PI BASIC (due to separate/different banned print lists)
View attachment 6287913

Amazing test combos! Great job, man.
However, even though you've tried so many combinations, mine is not in them.

Vagelis1608 · Nov 20, 2025

aorifan said:
Amazing test combos! Great job, man.
However, even though you've tried so many combinations, mine is not in them.

It's probably your FP
Use the Action button in PIFork to pull a new one.
If that doesn't fix it, try setting spoofVendingFinger=1 as well

aorifan · Nov 20, 2025

Vagelis1608 said:
It's probably your FP
Use the Action button in PIFork to pull a new one.
If that doesn't fix it, try setting spoofVendingFinger=1 as well

Thanks for the heads up. I think I forgot to spoof the TB/PIA Checker app in TS, so the security patch dates do not match. That explains why the apps are all working, but not the checker apps, for they are not on the list.

[MODULE] Play Integrity Fork (PIFork)

Senior Recognized Developer / Contributor

Senior Recognized Developer / Contributor

Senior Recognized Developer / Contributor

Senior Recognized Developer / Contributor

Senior Recognized Developer / Contributor

Senior Member

Senior Recognized Developer / Contributor

Senior Member

Senior Member

Forum Moderator

Senior Member

Senior Recognized Developer / Contributor

Forum Moderator / Recognized Translator

Senior Member

Recognized Contributor

Senior Member

Senior Recognized Developer / Contributor

Senior Member

Forum Moderator / Recognized Dev / Hacker Hunter

Senior Member

Similar threads

Top Liked Posts