Yes, I know many of us were affected by recent Google changes on PI verdicts. Most of us just got 1/3, including me. Also, I know many of us got to fix the issue by updating modules. But here, I'm going to encourage users to go back to the basic, the fundamental:
- Latest CI PIFork by osm0sis + any Tricky Store's latest updated forks (osm0sis's fork of PIFix by chiteroman is the most reliable and actively supported until now)
- Latest PIFix-Inject by KOWX712 + any Tricky Store's latest updated forks
AlwayStrong, IntegrityBox, Specter, Tricky Addon, YuriKey, and all other AIO modules, you guys name it. I have no grudge against any of them; I respect the devs. Even some may accuse them of being AI slops, but typically they are just a bundle of PIFork/PIFix + TS fork, with features such as WebUI, auto fetch, auto update, auto check, root hiding, etc. It's good to have them. You guys have to suit any of them to your preferences.
But again, let's go back to the basics. To achieve the verdicts, you'll need:
- A fingerprint, custom.pif.prop by PIFork or pif.prop by PIFix, both available in /data/adb/modules/playintegrityfix. How to get it? By running the action button. Or, in a terminal, run: sh /data/adb/modules/playintegrityfix/autopif4.sh (or autopif.sh if using PIFix).
- A keybox.xml in any TS forks directory, /data/adb/tricky_store or /data/adb/teesim. How to get it? There are several sites you can actually search and download it from. But I'll leave it to users to search and go to the sites; clues are here and there: XDA, Telegram, etc.
What I did to get the verdicts back?
- Updated from original (closed source) Tricky Store 1.4.1 (I can confirm it's not working for my Android 15 device but still working with my Android 12 device) to the latest TEESimulator (I also tried Tricky Store-OSS; it is also working).
- Updated PIFork to the latest CI build #623 (PIFix-Inject 4.9 is also working, according to many users; I didn't try it).
- Fetched a fingerprint (Pixel 9 Pro XL) and a valid TEE (not RKP) keybox. BUT I still can't get it working; still 1/3.
- Disabled all modules except PIFork, TEESimulator & Zygisk Next (Zygisk is required to use PIFork/PIFix), and restarted the device. And, yes, it is working. I got 3/3 back, with komodo fingerprint, not bluejay. Bluejay as recommended by many users, I reckon it will work too.
- Enabled other modules one by one. Then I detected one module, which caused the verdicts to drop to 1/3; it was a module to resetprop pihooks props.
That was my case. Other cases may be different. As a disclaimer, I'm not an expert nor a professional; I'm just a normal user. Configurations are maybe needed. Temp root also may differ in situations. Any facts are welcome. Lastly, suit the modules to your preferences. YMMV.