thefreeman193 / pifs Goto Github PK

(Original title: None of these fingerprints work anymore)

I used this beautiful tool together with Chiteroman's fix and at some stage it worked fine, but after the working fingerprint was banned... I tried A LOT of times to find a fingerprint that passed both Basic and Device, (I tried for hours) but none of them seem to work anymore, I tell you this just for information purposes, I can't help much... Are there other known solutions? Or are you planning something? Thank you anyway

Of all of the verdicts listed here : https://developer.android.com/google/play/integrity/verdicts

Does it pass all of them? or only some of them?

Thanks.

Running A14 on Google Pixel 7A.
Should I see the label 'device integrity' or is it only shown when it meets the device integrity?

I've tried to use the 2 options, making sure the pif.json was there and well written, but when I try to test my Play Integrity, in Play Store or in a third app party, both are not detecting my new device fingerprint. Instead, they're detecting the original one.

I'm using chiteroman module and the ABI list was always correct.

hi
i followed your instructions carefully and i got this warnings
also there was no pif selected
could you please tell me at least the way on how to do it correctly cuz i swear i am not sure if i did something wrong since i followed the instructions

Device : POCO F3
ROM : CRDroid (Android 14)
Root : KSU

After running pickaprint.sh with the osm0sis fork of Play Integrity Fix, any sort of method to check Play Integrity returns "API ERROR -17"

After reinstalling osm0sis on its own and not using pickaprint.sh, it works fine. After running the script once again it breaks.

As someone who is a bit weary of running scripts from the internet I opted to use option 2 and do this process manually but I run the chiteroman PIF and I couldn't figure out why no matter what fingerprint I used my play services kept crashing and integrity checks gave me "NO_INTEGRITY." Even worse than just basic. Eventually after checking the bug tracker I realized the files are in the wrong format and after extracting the bit of sed from your script I got this working with the first fingerprint I tried after previously going through about 10 of them. I spent quite a bit of time trying to track this down and for the future person doing it manually it'd be great if the conversion process was documented. Thanks for this collection!

Won't this repository make it trivial for google to ban every fingerprint in it. They can just download it and ban everything.
The only way we have any chance of using spoofed fingerprints longterm is if people learn how to find them on their own.
The main thing this repository will accomplish is burning a whole bunch of fingerprints all at once.

Checking new PIF only works with reboot, not just killing the process!

I've been trying to use your script to find a valid print on my device, and none worked.

adb logcat showed PIF/Java: Couldn't parse JSON from Zygisk whenever I tried a new one, so I started looking at the pif file, and it contained a dangling comma, which is not valid json.

…
  "FIRST_API_LEVEL": "25",
}

I tried fixing it, but between the very limited sed in busybox and my own ineptitude, I found it very hard to strip that dangling comma.

Here's a very crude fix, but I know you get the gist and will find a more elegant solution.

The "fp downloader" application can only be used after the initial restart after installing the Magisk module, after the next restart of the "fp downloader" application, it repeatedly crashes after starting the application. However, calling the "fp" command in the terminal still works. Is there a similar experience?

Run the script in termux
Root with magisk
The script worked about two weeks ago

===== PIFS Random Profile/Fingerprint Picker =====
 (Buy me a coffee: https://ko-fi.com/nickbissell)
============== v3 - collection v1.3 ==============

    Using busybox '/data/adb/magisk/busybox'

Looking for installed PIF module...
    PIF module found but not recognized! Will use /data/adb/pif.json

Detecting device ABI list...
    Will use profile/fingerprint with ABI list 'arm64-v8a,armeabi-v7a,armeabi'

Picking a random profile/fingerprint...
    Found excluded profile 'Meizu_meizu_PRO6Plus_PRO6Plus_7.0.0_NRD90M_m96.Flyme_7.0.1533805452_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'nubia_NX619J-EEA_NX619J-EEA_9_PKQ1.180929.001_eng.nubia.20190929.101618_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'Coolpad_C103_C1-INDIA_C103_6.0.1_ZIXOSOP5801803011S_0001832_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'samsung_greatltexx_greatlte_9_PPR1.180610.011_N950FXXU5ZSAB_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'asus_WW_Z01H_ASUS_Z01H_1_7.1.1_NMF26F_WW_user_71.60.139.30_20180306_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'Xiaomi_oxygen_oxygen_7.1.1_NMF26F_V11.0.2.0.NDDCNXM_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'ZTE_ZTE_WARP8_warp8_7.1.1_NMF26V_20181018.111136_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'Huawei_PLK_hi3635_6.0_MRA58K_jenkins12300945_user_test-keys.json'. Moving to '/data/adb/pifs/failed'
    Found excluded profile 'GiONEE_F103_GiONEE_GBL7319_5.0_LRX21M_1446213931_user_release-keys.json'. Moving to '/data/adb/pifs/failed'
ERROR: Exhausted 10 attempts to pick a profile not in the failed list. Are all profiles excluded?

(original title: Brilliant, but...)

...what's stopping Google from finding these fingerprints, and just mass-blocking them? Also, surely people using devices with a stock ROM and a genuine fingerprint are going to get blocked too, right? Especially if they have an older phone.
(Like, when I first got my Xiaomi phone, my one was already blocked on latest MIUI)