yashsingh1/xdaforums huggingface dataset:
[Magisk] Vision:
Oh understand, i ask because with Notepad++ is one large space in v14.6 when delete in front, in v14 is 2 small space
[Magisk] osm0sis:
Yes... One could indeed call a tab "one large space"... 🤔🤣
[Magisk] zgfg:
Interesting

He has PIF.sh script on GitHub that first fetches (curl and grep) a link for the latest XiaomiEUModule.apk from Xiaomi.eu SourceFourge.Net

The script then downloads (wget) the apk, extracts by apkool and by grep and sed cuts out the prints being hardcoded in the latest XiaomiEUModule

The script then creates the PIF JSON and saves to GitHub

---

On the user side, user installs an app together with his PI Next module

By use of tasker, that app looks to his GitHub link and downloads and installs the latest PIF JSON file that his script had created there

---

So in short, he 'steals' the prints from the latest XiaomiEUmodule injector app, creates the PIF JSON with that same prints on his Github address - his app from the phone checks, downloads and 'installs' that latest PIF JSON for the local use

Hence he doesn't burn additional or his own FPs, but piggybacks to the latest prints being used by Xiaomi.eu
[Magisk] Vision:
Yeah, i remember some time have mess up with this big large space in one module in past, not make again the same mistake :ROFLMAO:
[Magisk] immortalwon:
That's actually a smart way of transferring the blame to someone else, lol! But he stated on the telegram channel that people should seek out their own prints again due to many forks of his mod.
[Magisk] ionut310:
For everybody that may struggle with pixel flasher this is how i do it. You can test them on the fly without flashing a module in magisk or rebooting.
[Magisk] simplepinoi177:
that's a different kind of message...

it's one thing if you are getting "didn't meet security requirements" or simply puts up a random "unknown" or unclearly stated error, because that means it's DEVICE_INTEGRITY...

i used to have a lot of issues with Wallet as well, both in the case of rooting, and when it's not. yours sounds like the latter.

with all the "checking" and re-adding, most likely your bank is throwing a fit/red-flag. most likely you need to call the bank, tell them you're trying to add to Wallet/Tap-to-Pay, and they need to do something in their end or re-authorize or something. usually this is the case, only one case i found a member simply wasn't able to al add his card while can add it to another device -- still seems to be ended up on his bank's end, but couldn't be 100% sure.

hope this helps and this leads to get it working...!
[Magisk] tfhavel:
As this seems to be the place to ask Play Integrity Fix questions:

Right now I can't verify my identity on payments.google.com (to delete an old card I need to re-add to Wallet, though that's not my question here). If I try this via a browser on my Ubuntu laptop, my phone does not display the verification request, so I can't do it there (even when BT-paired with the phone). When I connect via a browser on my phone and ask it to verify using "This Device", however, it says my phone has no passkeys on it (which is of course wrong!).

My question is: Has Google really so badly screwed up the roll-out of its new passkey based authentication system, or is my inability to verify my identity due somehow to the fact that I've rooted my phone? FYI: I've installed PIF 14.6, which doesn't allow me to pass STRONG_INTEGRITY though it passes the others. And it's a Pixel4a running the latest Android 13 (rooted via Magisk).
[Magisk] woody4165:
Hi all

I'm trying to use a build.prop found in some MIUI dump, but I haven't succeded un til now (I've tested around 10) using the guide from @badabing2003

How can I revert back to the pif included in PIF 14.6?

Now I have two pif.json one in /data/adb and one in /data/adb/modules/playintegrityfix

Should I remove this last one?

I've already tried to remove from Magisk, reboot and reinstall it, but still getting no DEVICE_INTEGRITY

Thanks
[Magisk] simplepinoi177:
this may have been answered/addressed already, but...

I'm guessing this may not be the best latest version of Pixel Flasher...
[Magisk] xXHenlolXx:
Hey @igormm. I was able to fix BB by using Magisk Delta instead of the default. But now I have another app that I need some help with hahaha.

https://play.google.com/store/apps/details?id=br.com.mobile.ticket Can you guys test this app? I'm using Magisk Delta + Shamiko + HMA + Play Integrity Fix (passing basic) and can successfully hide from my bank, Netflix and Google Pay, but this app just won't work.

It prints this message:

View attachment 6046927
[Magisk] badabing2003:
The newer version of PF does not make prints pass, if the print is bad, the print is bad, the tool just makes it easier for you to hunt and test and manipulate the prints.

Say what?

The guides have been updated here and here
[Magisk] sawdoctor:
Anyone having issues? I'm using my own print had zero issues. Play store says device is certified but failing all 3 checks now on every app
[Magisk] Vision:
Yeah delete the /data/adb/pif.json, because if remove from inside magisk the /data/adb/pif.json still remain must delete manually (in v14 i don't know about v14.6)
[Magisk] woody4165:
Thanks

I've tried to copy the /data/adb/modules/playintegrityfix to /data/adb/pif.json then rebooted and it worked

I will try also to remove from /data/adb
[Magisk] Vision:
Good. The default Fingerprint is the /data/adb/modules/playintegrityfix/pif.json and auto go to /data/adb/, if you want to test new Fingerprint, just send and replace the /data/adb/pif.json

Edit: For quick test (if you have already installed this module) if FP working, send the new pif.json file to /data/adb and replaced the exist, go to setting/apps, found the Google Play Services and click force close (no need close the internet etc.) (i try it this with Total Commander) after do the test if pass 2/3
[Magisk] simplepinoi177:
crap... my apologies @badabing2003!

my computer is on the fritz and I'm using mobile, and it autocorrected from "latest" to "best"...!!! i trust all what you implement in your wonderful program is "best"; therefore all versions is "best"...

I've since edited & corrected my post...

sorry for reviving an off-topic subject, but since the mistake happened here...
[Magisk] simplepinoi177:
some other users are having this happening to them... but if you go back a version or two, the same print works...

seems to be something with 14.6; probably how he injected the capability to have two .json's, one custom or one default...

I'll see if i can edit in his response to it...
[Magisk] badabing2003:
Thank you for the clarification, I've been bitten quite often with the auto-corrector, and times people probably were wondering what the heck I was talking about see how far from the intended meaning they were at times.
[Magisk] sawdoctor:
I'm still running v14 with a custom fingerprint, if the print was banned wouldn't I still pass device?
[Magisk] simplepinoi177:
yea... just edited in my post... sorry on Mobile so it's difficult and takes longer...

but, for whatever reason, it's happening to the other users as well where it's not about it being banned/burned, but something bugs out and glitches in the code that shows all 3 to fail, even if the fingerprint isn't burned yet... it seems the fingerprint or it's application didn't stay intact..
[Magisk] Vision:
You mean basic ? or Play store device certified ?
[Magisk] xSnowLeopardx:
Update

Still passing both integrities, still being able to pay with GWallet, still using the same FP which I found 20 days ago, still on v14.4.
[Magisk] sawdoctor:
Everything was failing apart from play store device certified. Strangely rebooting fixed it, I'm back to device and basic after a reboot. Hope Google aren't doing anything at thier end
[Magisk] simplepinoi177:
usually we say for shorthand "device" for MEETS_DEVICE_INTEGRITY and "certified" for "play store device is certified".... at least that's how i take it
[Magisk] CZ.Kostra:
Own FP+Play Integrity Fork v4 and all good (PI 2/3).
[Magisk] HippoMan:
I wonder if this might be related to the particular integrity-checking app that they might be using ... ???
[Magisk] simplepinoi177:
me too... but just for 14 days instead of your 20.

but I'm beginning to be of the impression that, after seeing how some others are having theirs suddenly banned but have been using theirs for not as long as mine (*knocks on wood*), the only difference i can guess is that i took mine from an extracted ROM i downloaded vs. a repo which most likely means they were using a fingerprint on a device that wasn't necessarily a smartphone...! but, then again, with my bad luck, watch mine get banned in the next day or two (*knocks on wood again*) -- and mine doesn't prove much of anything, in the end...
[Magisk] HippoMan:
Isn't it the case that the latest @chiteroman release installs a different pif.json upon every reboot?

Or am I misunderstanding something?
[Magisk] simplepinoi177:
some have said, instead of checking through the app or play store -- play integrity API check specifically -- they just see if Netflix (i know Turo for sure is another one) shows up in results or not. i know it seems obvious, but anything to keep Google from possibly being alerted simply by the amount of requests a device (spoofed) makes...
[Magisk] xSnowLeopardx:
If you have a good amount of backup FPs, then all is good. I don't mind seeing my 1st banned soon, then I can finally use another one lolol.
[Magisk] simplepinoi177:
i think that's PlayIntegrityFixNEXT or something like that (can't remember the name exactly [maybe PIFNEXT], but read back a page or two and he speaks to that being how his (or the dev's) module works)...
[Magisk] bakaekze:
your print is no good, find another one
[Magisk] HippoMan:
Oh, yes!

Does anyone know of an automated way to check whether any given app is available in the Play Store?

If I can do this, and if this Netflix test for DEVICE integrity is indeed valid, I could then write a script to fully automate this integrity checking process, and the script could be run either via adb or on the device itself.
[Magisk] Vision:
Me to i have some strange with v14. New FP just now clean Google Play & GMS data and cache reboot, pass 2/3, Play store says device is certified but the Netflix and some else say it is not compatible

Me to i have some strange with v14. New FP just now clean Google Play & GMS data and cache reboot, pass 2/3, Play store says device is certified but the Netflix and some else say it is not compatible
[Magisk] Vision:
Oh yeah, sorry i confused with something else :ROFLMAO:
[Magisk] Vision:
Εxcept Netflix, now some games need DEVICE integrity, like this: https://play.google.com/store/apps/details?id=games.dali.adventure.reborn&hl=en_US
[Magisk] simplepinoi177:
hmmmm that's peculiar... usually clearing data of play services/gms and rebooting does it...! I've tested enough where it literally says that one minute, then suddenly says compatible the next minute!

maybe clear Play Store data as well...?

that, or you're receiving a cached result on passing the 2/3...
[Magisk] Vision:
Yeah i know for that is strange, i have do it this lot of times and always works, i have clear Play Store data. You mean like temporary and show pass 2/3 but not permanet? but Play Store say device is certified
[Magisk] simplepinoi177:
I'm just spitballing (about the possible cache/temporary passing 2/3), but sometimes i clear data on the checkers, just in case.

and sorry for not assuming your cleared data on Play store; you only stated "Play", i didn't really to presume whether that was the Store or other services

Play Store showing certified or not certified has always been very delayed for me. in the early days of Dispax MOD or even MHPC, i would do everything i could to update Play Store (uninstalling updates, then updating the app), just to get it to say certified, so i could download Netflix or whatever, and sometimes it would still take hours/days. so i don't trust that to show very current; but maybe times have changed since I've really looked at it...
[Magisk] Vision:
Yeah undarstand, is fresh install the Play Integrity API Checker, after check always i deleted the checker from my phone :ROFLMAO:

Yesterday the Google Play Services have a updated, maybe something with that
[Magisk] miss:
Thanks, I thought that's what but I couldn't find how to do it.
[Magisk] bakaekze:
Wow, didn't know that I could speak Spanish
[Magisk] Vision:
@simplepinoi177 Just now check again and the Netflix he did me the honor to appear (after 2 hours) :ROFLMAO::ROFLMAO::ROFLMAO:
[Magisk] woody4165:
Both BASIC and DEVICE are ok after copying pif.json from /data/adb/modules/playintegrityfix to /data/adb and a reboot

Should I do also force close of GPS ?

I don't have Total commander, but I have Solid Explorer or X-plore and don't know how to do a force close from there
[Magisk] Vision:
Sorry for misunderstanding, i mean i try it with total commander the replace of pif.json, not force close a app, for force close like normal in settings/apps find your app and click force close
[Magisk] chiteroman:
Release v16.5 · chiteroman/PlayIntegrityFix

Update hook framework: Dobby Fix Device not passing in few devices Improve code Reduce Zygisk libs size

github.com
[Magisk] woody4165:
Ah, ok

Force close is greyed out in Play Service for me
[Magisk] Bonoboo:
I'm using custom fingerprint (BTW 22 days). Right after update can't pass integrity, rebooted - too. Reverted to 14.6 - all fine.
[Magisk] Vision:
Maybe because this line have remove from v14.7 and your FP from 14.6 have includes this inside

"FIRST_API_LEVEL": "",

"SECURITY_PATCH": "",

"VNDK_VERSION": ,

"BUILD_ID":
[Magisk] Vision:
Good, but why Always spoof api_level props to 23 ? Mine FP had (before block it) work with 28 and 29

and why remove the SECURITY_PATCH ? no need it anymore ?
[Magisk] Bonoboo:
Yes, I have "FIRST_API_LEVEL" and "SECURITY_PATCH".

If we all should remove these parameters (why just not ignore them in code?) I guess chiteroman had to mention this important info.
[Magisk] HippoMan:
Thank you!

Given that so many people in the TG group use PIF and will have to learn how to download and install their own fingerprints, it would be helpful if the following link is pinned to the TG group's discussion:

https://xdaforums.com/t/how-to-sear...scussion-for-complete-noobs-from-one.4645816/
[Magisk] Vision:
Yeah maybe is bug and @chiteroman he not noticed
[Magisk] affedov:
Hi, I used Play Integrity and updated it today. And it doesn’t work for me at all, it constantly writes that there is Root Rights, as I understand, the developer did something, and now there is no fingerprint there, but I’m stupid and don’t know how to add it, what should I do?
[Magisk] Claus….:
Good decision! I am also working my ass off just to mine 1, but it pays off.
[Magisk] tom1807:
This should be useful for you,

Cheers

Tom
[Magisk] sawdoctor:
I'm still using v14 so no that doesn't affect me. Maybe just a Google gremlin? Rebooting fixed it anyway
[Magisk] sawdoctor:
My fingerprint is fine, a banned print still passes device. I was falling all 3 so it was a different gremlin
[Magisk] xSnowLeopardx:
Not really needed to go to 14.7 if a) someone is on 14.4 and b) everything (for now) works, right?
[Magisk] Vision:
Yeah, the same

View attachment 6046964
[Magisk] affedov:
So what should we do now? I CANNOT live without using Google Pay, how can I fix it?
[Magisk] affedov:
Maybe there are other applications besides Google Pay?
[Magisk] V0latyle:
Find a working fingerprint, you can use this

For NFC payment? Maybe your bank has an app but they most likely have their own root detection
[Magisk] zgfg:
I have found very rare ones among Xiaomi dumps.

It seems for two reasons:

- Generally, their fingerprints require Strong attestation, hence they are not suitable (you need FPs that allow weaker, Device Integrity, ie CTS Eval Type BASIC, not HARDWARE_BACKED)

- Mostly the same build.props (and the already made PIF.json files) circulate around.

But it seems that somebody stripped of build.prop from /product instead of from /system and for many A11 and higher ROMs you have often like:

"FINGERPRINT": "qti/missi/missi:12/SKQ1.211006.001/V13.0.6.0.SKOMIXM:user/release-keys"

But that cannot be from the certified ROM - qti, meaning Qualcomm Technology, Inc is not the phone manufacturer and missi is not the model (this particular FP, together with many others, corresponding to various MIUI 12/A11, MIUI 13/A12 and MIUI 14/A13 builds) was among Xiaomi Lisa prints

Since I have the same phone I looked myself and I found that that qti Lisa FP can be found in the build prop from /product, whereas the FP from /system does have correct manufacturer xaomi, model lisa, etc

Hence, those qti FPs fail even Basic Integrity.

While the correct ones (if you find them) require CTS Eval type HARDWARE_BACKED attestation (so on TEE), hence STRONG attestation in PI jargon, where you cannot spoof

If you are not testing by an automatic script, you will waste a lot of time to find an useful FP from Xiaomi. Better invest your time in testing FPs from the other vendors, their build props and FPs seems to be properly collected and sometimes, against the odds, even for FIRST_API_LEVEL 30 (and ery, very rare even for 31) they still allow CTS Eval Type BASIC (meaning that somehow they were exempt from Strong attestation on TEE, maybe due to some issues in their TEE design and implementation or who knows)
[Magisk] majorfigjam:
Depending on your location, you could use a smart watch for Google Pay.

Otherwise follow the instructions for Osmosis fork, look in your PM, and maybe Santa Claus will leave you a present.
[Magisk] vamteusz:
I used this but I get the message

and nothing further happens. What should I do to make it work?
[Magisk] majorfigjam:
Follow the instructions closely, don't take shortcuts, and it will work.
[Magisk] majorfigjam:
I know I offended some by responding RTFM earlier, but seriously, R'ing the FM is the best way for those still struggling.
[Magisk] zgfg:
Yesterday I had a close call. I was automatically testing hundredths of FPs (and I found almost 60 valid custom PIF JSON files) but probably my Wallet updated the PI attestation at the bad moment (when the previous cached attestation expired and when I was testing PIF JSON that was not passing)

While I was entering the store I shortly tested PI to make sure that I finished the previous testing (my script for automated testing had to do that) by putting back the valid PIF JSON.

And it was, it passed Device Integrity

But when I tried to pay contactless by the phone, Wallet complained that the phone is not secure

I asked to let me try paying again, and then it passed (Wallet must have been retested then and it passed with again the valid PIF JSON). After that I successfully payed in another store and on the gas station
[Magisk] purgy:
Read this https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-177#post-89189572

Then if you have a PC read this https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-179#post-89189970

Or if phone only, https://xdaforums.com/t/pif-testing-helper-tasker-profile-for-testing-fingerprints.4644827/
[Magisk] casouzaj:
My wife's Xperia XZ2, running LineageOS 20, started failing Device Integrity with PIF 14.7. I turned to daboynb's Play Integrity Next solution, and Device Integrity is back. Just my 2 cents.
[Magisk] maxwellfire:
One thing that I'm wondering about. I have an old Nexus 5, Nexus 6p, and a Pixel 2XL. I believe that all of these devices had fingerprints that worked at some point before they were banned. There were some earlier messages in the thread that indicate that these fingerprints should still work on my devices if I was running stock. But that they don't work anymore with a custom ROM. Is there anything that I can do to try and help determine how play integrity is figuring out that my device is running a custom ROM? I can flash whatever on the 5 and 6p to compare stock vs lineageos vs etc. Is it merely that they're banning the fallback to software authentication on devices that should have working hardware backed authentication (As in, requiring either strong integrity or basic integrity, and disabling just device integrity as an option)?
[Magisk] chiteroman:
v14.8 released to fix issues of v14.7

Release v16.5 · chiteroman/PlayIntegrityFix

Update hook framework: Dobby Fix Device not passing in few devices Improve code Reduce Zygisk libs size

github.com
[Magisk] wugga3:
Wouldn't the script be better directed at the play store play integrity under developer options... Of course I could be wrong (and I reserve the right to be wrong). Thanks
[Magisk] simplepinoi177:
It seems that Play Integrity Next is simply continuing what PIF/chiteroman/main-branch was doing and is pulling from the xiaomi.eu ROMs; so additional 2 cents is to be sure to keep up with any new versions (I don't believe he updates versions like chiteroman did, it might be automatically fetched when you reboot I believe seeing) and/or be on top of how the module updates fingerprints...
[Magisk] simplepinoi177:
I feel the same as you..which is why I dedicated 2 and a half days to figuring this all out (from a completely utterly hopelessly noob level of understanding). So, you might want to check out my guide below if you feel the same and/or want to read up/relate on the experience

How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)

It seems Google has banned more than 95% of custom fingerprints, so this thread/guide has kind been laid to the wayside. But it's still a great resource to understanding the foundations of fingerprints and all that... This is for any/all utterly...

xdaforums.com

and this tool that will check frequently and alert you when Wallet will fail...

GPay Checker: monitor of Google Pay availability

Google Play Protect now triggers onto app (that's honor for me), but here nothing criminal. You can safely skip warning. There is non-zero theoretical possibility, that using this app increases risk of banning your personal fingerprint. There...

xdaforums.com
[Magisk] xcl1pse:
Now it's working 😀
[Magisk] zgfg:
PIF 14.7 and 14.8 install empty JSON

{
"PRODUCT": "",
"DEVICE": "",
"MANUFACTURER": "",
"BRAND": "",
"MODEL": "",
"FINGERPRINT": "",
"FIRST_API_LEVEL": 21
}

. User/you are required to mine your own one and to give it to PIF v14.7

Otherwise, with PIF 14.7 alone, you will NEVER pass - that has already been announced here by developer, it's written in his PIF Github Readme and in his TG channel
[Magisk] shoey63:
For users looking for a simple approach to find a new fingerprint, try this method. (Thanks to @TheFreeman193 for his great tool)

I recommend @osm0sis's fork https://github.com/osm0sis/PlayIntegrityFork/releases/tag/v4

- Install termux

- enter su

- then

mkdir pif && cd pif

- then, as per The GitHub readme, enter

/data/data/com.termux/files/usr/bin/curl "https://raw.githubusercontent.com/TheFreeman193/PIFS/main/pickaprint.sh" | sh

- Test for device integrity

- No good? Go back to termux and enter

./pickaprint.sh

and test again.

- repeat until you pass DEVICE _INTEGRITY.

- then either clear Google Play Services data and re-add cards etc. or just wait a few hours until wallet works again.

Edit:

To start a new session, open Termux, enter su

Then enter cd pif

then ./pickaprint.sh and test.

If you don't pass DEVICE_INTEGRITY, go back to Termux and enter ./pickaprint.sh again until you get a working print.
[Magisk] vamteusz:
I read the readme and tried everything but it doesn't work :( I still have some errors (?) such as "unexpected operator" and "expecting primary"...

View attachment 6046991
[Magisk] osm0sis:
Oh wow, 2 full rewrites in one day! That might be a new record for you! 😆

Hmm, thinking more about this ...

@TheFreeman193 + @chiteroman, how would you like to screw over this fork by doing all the Xiaomi.eu print extraction on-device instead of relying on some dude to update their git repo? I can dex the latest apktool for us if we want to make it function similar to ./pickaprint.sh... 🤠