This media is not supported in your browser
VIEW IN TELEGRAM
I'm testing 630 pif😂
for now, no luck
Forwarded from Pray Integrity Fix 🙏 (Marcos)
v15.9.9 released!
https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v15.9.9
https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v15.9.9
The Best Years Of Our Lives
1. Connect your phone to pc, make sure to have usb debugging enabled and then run the following in cmd
adb shell
pm uninstall —user 0 com.goolag.pif
(via adb needed because for some reason on jimgsey you can't run pm command on termux, even with su)
2. Then have zygisk enabled (magisk)/latest zygisknext module installed (ksu/apatch), install both PIF and playcurl modules
4. After reboot, run su -c fp in termux and it'll now automatically download a new fp
5. Finally, clear playstore data, reboot, profit
adb shell
pm uninstall —user 0 com.goolag.pif
2. Then have zygisk enabled (magisk)/latest zygisknext module installed (ksu/apatch), install both PIF and playcurl modules
4. After reboot, run su -c fp in termux and it'll now automatically download a new fp
5. Finally, clear playstore data, reboot, profit
Do this guide ^ ignore the part where it says to (install playcurl and do su -c fp)
Only PIF module is sufficient
Only PIF module is sufficient
The Best Years Of Our Lives
ap_policy.zip
^ Flash this module if you can't use pm command on termux, even with su
Forwarded from Pray Integrity Fix 🙏 (Marcos)
By the way, it seems that a certain Google employee is back from vacation.... The other fp didn't even last a week.
We are back to the dark days...
We are back to the dark days...
Forwarded from Pray Integrity Fix 🙏 (Marcos)
Seems like there are users failing Device verdict.
I want to know your setups.
DroidGuard can detect Magisk, KernelSU (legacy) and KernelSU GKI patched images, so maybe this fp (sailfish) is "banned" for them. Also you can post in XDA
I want to know your setups.
DroidGuard can detect Magisk, KernelSU (legacy) and KernelSU GKI patched images, so maybe this fp (sailfish) is "banned" for them. Also you can post in XDA
Anonymous Poll
60%
Magisk
15%
KernelSU (legacy) (non GKI kernels)
12%
KernelSU GKI
6%
KernelSU LKM
6%
APatch
Forwarded from Pray Integrity Fix 🙏 (Marcos)
Can someone read module logs (adb logcat -s PIF) and post in XDA?
Maybe Google implemented "image fingerprint":
https://github.com/chiteroman/PlayIntegrityFix/issues/236#issuecomment-1917752630
Maybe only pass on stock roms and not custom?
Google, what are you doing 😡
Maybe Google implemented "image fingerprint":
https://github.com/chiteroman/PlayIntegrityFix/issues/236#issuecomment-1917752630
Maybe only pass on stock roms and not custom?
Google, what are you doing 😡
Forwarded from Evolution X (Official) (Joey)
chiteroman's module didn't help pass device integrity in the latest Evo 9.0 that was released nor did the updated pif.apk. We've made a few changes to be tested tonight and hopefully this mitigates the issue for the time being.
In any case, a pif apk update may no longer work for all current evo builds and might require a ROM update for everyone.
In any case, a pif apk update may no longer work for all current evo builds and might require a ROM update for everyone.
Forwarded from vbajs
Google is playing fucking 5d chess with us
The Best Years Of Our Lives
HyperOS Global 1.0.3.0 A14
Gonna flash this now, cya
May not cook new Matrixx OS, even if it did get updated to fix integrity issues
May not cook new Matrixx OS, even if it did get updated to fix integrity issues
The Best Years Of Our Lives
Gonna flash this now, cya May not cook new Matrixx OS, even if it did get updated to fix integrity issues
And now I'm passing device integrity on it with ksu and pif 1.5.9.9
Looks like chiteroman's suspicions about image fingerprint is correct
"openela" uname string is banned
https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89524461
Avoid using Strix for the meantime
https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89524461
Avoid using Strix for the meantime
XDA Forums
🔧 [MODULE] Play Integrity Fix (SafetyNet fix)
PLAY INTEGRITY FIX
This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation.
You will need root and Zygisk, so you must choose ONE of this three setups:
-...
This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation.
You will need root and Zygisk, so you must choose ONE of this three setups:
-...
Hmm the thing that's suspected to be causing AOSP ROMs to not pass is because signature spoofing that had been introduced by PE's PixelPropsUtil since A14
It also explains why <=A13 AOSP is passing
It also explains why <=A13 AOSP is passing
The Best Years Of Our Lives
Hmm the thing that's suspected to be causing AOSP ROMs to not pass is because signature spoofing that had been introduced by PE's PixelPropsUtil since A14 It also explains why <=A13 AOSP is passing
And also some A14 AOSP ROMs that do not spoof signature like le new official Lineage 21
So known types of ROMs that pass device with latest PIF:-
* MIUI/HyperOS ROMs
* <= A13 AOSP ROMs
* Some A14 ROMs that do not spoof signature like Lineage
* MIUI/HyperOS ROMs
* <= A13 AOSP ROMs
* Some A14 ROMs that do not spoof signature like Lineage