-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 18.7 busted it again #560
Comments
Not sure what you're running into. With v18.7, using TrickyStore and a valid kb file, I'm now back to Strong on the PI "New Response". |
Tricky Store never worked for me. KB files are hard to get and both are NOT part of the PlayIntegrityFix flavor. If you rely 2/3 on other apps, it's nothing to discuss about here. |
Did you set spoofVendingSdk to 1, as stated in the PIF readme? I just tested on my phone. -I changed PIF spoofVendingSDK to 1. |
@markfm62 Just did that and while I'm finally getting both Device Integrity and Basic Integrity, my Google Play Store started crashing again. |
Then PIF is working as documented, doing what it can. Please see the "A word on passing Strong Integrity" on the main PIF GitHub page, particularly the italic section just above "Acknowledgments". As of right now, to reach Device the "New Response (A13+)" PI checks need either a TrickyStore/valid-kb or spoofing that the device is < Android13 (what PIF can do). |
Google Pixel 7
Android 15, February Patch
Magisk 28102
On version 18.6, everything worked.
Since updating to 18.7
Edit: A fresh install (18.7) seems to have fixed it. Do not update from 18.6 to 18.7.
Edit 2: The latest version - once working properly - will still not pass the new Device Integrity

It's questionable whether this update is useful at all or not.
The text was updated successfully, but these errors were encountered: