yashsingh1/xdaforums huggingface dataset:
[Magisk] dimak2103:
Then maybe it's something else. No idea. I have OnePlus 9 Pro, OxygenOS 13. Same thing on OnePlus 5 with DerpFest A13
[Magisk] stefaca:
I populated pif.json from build.prop file from my phone. But still nothing :D
[Magisk] GN-z11:
You have to populate that with a FP from a device that's not yet burned by Google.
[Magisk] trevtdogg:
you will most likely have to try many different devices until you find one that works. see the thread i linked earlier for you as a good start.
[Magisk] sawdoctor:
If you populated with the build prop from your own phone you haven't read the post you were linked properly. People on here will gladly help you but you also need to read a little yourself. It might seem a little overwhelming but honestly it's easier than rooting your phone
[Magisk] Vision:
like sawdoctor say, you must write in the fields the fingeprint you found from a old not from your new phone or other new
[Magisk] Cakelicious:
I'm in your shoes -- understand very little of the tech stuff.

Try this fork: https://github.com/daboynb/PlayIntegrityNEXT

He made a version+apk that basically finds and edits in a fingerprint for you, very simple instructions.
[Magisk] osm0sis:
The .sh files in the module directory.
[Magisk] stefaca:
I have tried. Populated pif.json with data from https://dumps.tadiphone.dev/dumps/r....0.4.0.RKHEUXM-release-keys/vendor/build.prop

Still nothing :D

Nevermind. I'm maybe not the one who is capable to this one.
[Magisk] osm0sis:
Try lowering API to 25, and put it in quotes.
[Magisk] dimak2103:
Thanks, I'll try to remove one function at a time and check if it works
[Magisk] osm0sis:
Start by just renaming the files to .off and that'll test if it's something in there causing the detection.
[Magisk] Vision:
The strange in the field "FIRST_API_LEVEL": the quotes not exist in v14.9

View attachment 6048268
[Magisk] klemi71:
Did you read PM?
[Magisk] osm0sis:
Technically correct json, but might be safer to be consistent since sometimes PIF has handled them all as strings 🤷‍♂️
[Magisk] ruiisaactan:
hey i just generated a custom pif file using your script for my pixel 5 on a version of android 13, it is rooted with magisk and im trying to use the module on the same version of android where i got the build.props from. currently i am only able to get basic using the play integrity api checker. device integrity still not working

{
"MANUFACTURER": "Google",
"MODEL": "Pixel 5",
"FINGERPRINT": "google/redfin/redfin:13/TQ2A.230305.008.C1/9619669:user/release-keys",
"BRAND": "google",
"PRODUCT": "redfin",
"DEVICE": "redfin",
"RELEASE": "13",
"ID": "TQ2A.230305.008.C1",
"INCREMENTAL": "9619669",
"TYPE": "user",
"TAGS": "release-keys",
"SECURITY_PATCH": "2023-03-05",
"DEVICE_INITIAL_SDK_INT": "30"
}

View attachment 6048272
[Magisk] Vision:
Oh and can confused with this different in "FIRST_API_LEVEL": , and pass only BASIC
[Magisk] Vision:
You must write in the fields the fingeprint you found from a old not from your new phone or other new
[Magisk] ruiisaactan:
so if i used this android 13 pif file on android 14 for my pixel 5 then it should work?
[Magisk] CZ.Kostra:
That would be very simple. 😁
[Magisk] osm0sis:
Are you using my fork? You need to to support the correct naming like ID and DEVICE_INITIAL_SDK_INT. Then try lowering DEVICE_INITIAL_SDK_INT to 25.
[Magisk] Vision:
Not newer device , old fingerprint from Android 6,7,8 and maybe 9 in some case
[Magisk] ruiisaactan:
yes i am using your fork, i used the gen_pif_custom.sh from your earlier post to generate this custom pif i uploaded in my orignal post
[Magisk] osm0sis:
Perfect. Any change with lowering to 25? There's a chance it'll work.
[Magisk] Vision:
Only with this change can pass? because he say use Android 13 FP

View attachment 6048290
[Magisk] ruiisaactan:
ill try this soon, i tried some stuff and wiped my device to install android 14 so need to install that specific version of android 13 again
[Magisk] Wolfcity:
As said the FP has to be from a device running android 7, 8, 8.1 maybe 9.

13 and 14 is far too new.
[Magisk] ruiisaactan:
im not sure about this as i tried magisk hide prop module that is discontinued using the android 12 fingerprint and this works to fix basic and device integrity on my pixel 5 on android 14
[Magisk] Vision:
I write exactly the same but :(

View attachment 6048300
[Magisk] CZ.Kostra:
Downgrade DEVICE_INITIAL_SDK_INT will cause rating type: BASIC. It may/may not work.
[Magisk] Vision:
I think now not work because Google make huge update since magisk hide prop module, but maybe @osm0sis know about that
[Magisk] ruiisaactan:
just tried the pif file with api level of 25 on both android 13 and 14 and it doesnt work, only has basic attestation no device integrity
[Magisk] Vision:
Anyone if have a extra working FP, can give one in ruiisaactan to see if evenctually work?
[Magisk] ruiisaactan:
do you know what are the changes that google made?
[Magisk] Vision:
Unfortunately no, just only hear, maybe @osm0sis know, but you must try a Old fingerprint from a Android 6,7,8 and 9 in some case and write it in the pif.json
[Magisk] CZ.Kostra:
I have a working FP from A12.

It is about the age of the mined equipment.
[Magisk] Vision:
Really, now i'm little confused 🤪 i thought we can't use from newer devices, because of hardware. Now the best answer we can take is from @osm0sis

View attachment 6048308
[Magisk] Umgak:
Could be a device with broken TEE, or one which received particularly long term support from the manufacturer and still released pre-TEE requirements. Without knowing the print (do not post the print) it's hard to say.
[Magisk] dimak2103:
I found what the problem is, it works without these commented out lines. What could be the reason? Without these lines, Play Integrity and Safety Net will not pass the test. Or should I find the lines that affect, taking into account the fact that those in the screenshot will not be commented out?

upd.: Also it works without lines from screenshot 2 an uncommented from 1, but Play Integrity and Safety Net will not pass.

upd2.: It doesn't work if everything in service.sh is uncommented and all other files are commented out. It turns out that the root of the problem is that the application can see that the fingerprint has been changed since I believe that the functions in screenshot 1 and 2 break the module. Is this even possible? What can I do?))
[Magisk] CZ.Kostra:
The manufacturer may have released a new ROM on an older device. Then FP can work.
[Magisk] Vision:
I read about broken TEE, the second first time hear, interesting

Edit: So with little word if the manufacturer support old devices without harware, with new ROM like Android 12, we can take this Fingeprint and add it as spoof
[Magisk] Vision:
Yeah maybe, first time hear, because always have short life the old devices (and how old talk about) for support new ROM

Edit: So with little word if the manufacturer support old devices without harware, with new ROM like Android 12, we can take this Fingeprint and add it as spoof
[Magisk] fragtion:
I'm running Magisk Alpha (built in Zygisk) with MinMicroG-NoGoolag-2.12.0-20230729205908.zip

I get continuous " microG Services Core keeps stopping" when PlayIntegrityFix 1.9 module is enabled. the microG utility app also fails to launch

I tried to clear data for microG services core

Is there a known incompatibility with MicroG?
[Magisk] nonstopzx0x:
I'm having problems with my s23 ultra, tried version 1.6, 1.8, 1.9, removed service framework update, chplay, but didn't pass the test, almost uninstalled chplay
[Magisk] Wolfcity:
I've seen that (that's why I wrote "as said") but I had the infallible feeling that the concerned user hasn't understood the point. Sorry for repeating your post but sometimes twice is better. 😉

There are a lot of repeating questions coming in here....
[Magisk] Vision:
You have right, for that i write in the end 'but' with face confused :ROFLMAO:
[Magisk] Wolfcity:
I'm not sure if PIF works without GPS or the other way round is able to work with microG.

But someone with more knowledge about it may correct me.
[Magisk] Nergal di Cuthah:
It's not the current android that matters it's the release os, what it had when it was first sold (example I'm on a Pixel 6 Pro on 14 (34) but if i used it as a fingerprint, I'd place 31 (android 12) (it will fail but example only),
[Magisk] Vision:
I don't know if it is relative, but has been discussed some similar with MicroG before one month

View attachment 6048350View attachment 6048351
[Magisk] Nergal di Cuthah:
Didn't Displax have to write a special version for microG near the end? I don't think, but may be wrong, that work continued into pif
[Magisk] Vision:
Yeah right

View attachment 6048352
[Magisk] majorfigjam:
I have this eerie feeling that I have woken up after Christmas and this forum has turned into telegram ....
[Magisk] Vision:
Yeah this is the point, i little confused from few answer for some users

View attachment 6048364View attachment 6048365View attachment 6048366View attachment 6048367
[Magisk] Vision:
Υou are not wrong, we discussed again about the right value in pif.json :ROFLMAO:
[Magisk] sawdoctor:
I can't believe it's the day after Christmas and people have forgotten how to use Google search
[Magisk] simplepinoi177:
direct from osm0sis
[Magisk] Vision:
My first FP had Android 9+ (FIRST_API 28) in pif.json and working pass 2/3 until Google block it :ROFLMAO:
[Magisk] Slim2none4u:
agreed...less useless chatter would be nice
[Magisk] fragtion:
Thanks you guys! I actually tried both PIF v1.9, and also safetynet-fix-v2.4.0-MOD_1.3-microG.zip already, and both of them are giving me the crashes for microG service core.... So I opened an issue @ PIF github (to try avoid creating a conversation thread here about it yeah. If there is a telegram chat for this I'd be most glad to shift this issue over to there)... So now hoping this can be figured out soon and that it isn't just my device xD

Right now it's not very urgent as I don't have any app that needs a safetynet pass, I just want my phone to be perfect. Some OCD you know...:D
[Magisk] Vision:
Sorry i violated the Rule 11
[Magisk] majorfigjam:
Are you indicating the print I gave you last week has been blocked? Maybe not as that one was definitely Oreo 8.0 with api 25.
[Magisk] Vision:
Before you gave me this (thanks again), i had one with Android 9+ (FIRST_API 28)
[Magisk] Vision:
For TG group for asking for help in chiteroman in GitHub in this module first page

Edit: Anyone who want ask help, chiteroman have a TG group and can found it, in GitHub in this module first page
[Magisk] majorfigjam:
For real? I recognize the words, but I have absolutely no clue what you're trying to say!
[Magisk] HippoMan:
FYI: it turns out that chiteroman himself hardly posts at all in that TG group. Generally, he only posts announcements of new software releases there.

That group contains more than 6,000 members and receives more than 1,000 messages every day. Even though there are people there who will try to be helpful, there also are lots of repetitious questions being asked, and there is lots of confusing information being posted there ... and also totally irrelevant stuff like cat pictures, etc.

And a lot of the useful information that people do repeatedly post in that TG group are simply references to these PIF-related threads here in XDA.

Just keep all that in mind if you decide to go to the TG group.
[Magisk] Vision:
Anyone who want ask help chiteroman have a TG group and can found it, in GitHub in this module first page
[Magisk] Marvin732:
Any way to uninstall the eu.xiaomi.module.inject

After installing the latest play integrity fix that thing is still there.

cant find a way to uninstall that app
[Magisk] Vision:
Yeah, you have right, thanks for advice 🙂
[Magisk] fbirraque:
Here
[Magisk] xSnowLeopardx:
24 days later -> still passing 2/3

Love this feeling. I can remember before Dec 2nd, I had no feeling that I could go and pay for something without having a risk of GWallet failing on me.
[Magisk] PedroCaseiro:
I didn't want to bump this but I'd really like some advice on how to get a fingerprint
[Magisk] trevtdogg:
Many people here don't have English as a first language. They are not allowed to post here in any other language due to forum rules. They are doing their best, maybe you can try a little harder to understand? And at least be polite if you can't.
[Magisk] sawdoctor:
Have a read of the thread HippoMan linked, try and take in as much as you can. Anything you are unsure about ask in that thread. If you are still struggling hit one of us up with a pm and we'll help with anything your struggling with.
[Magisk] shoey63:
He means that if you go to

https://github.com/chiteroman/PlayIntegrityFix

You will find a link to the Telegram support group.

Wasn't that hard to work out.
[Magisk] majorfigjam:
I fully recognise that many people don't have English as a first language, and I am careful to make allowances for that.

However, you must also recognise that posting an unconnected string of recognisably english words, with little or no context, does absolutely nothing to help other people with English as a first, second or other language gain useful information.

Sorry if I offended your evidently sensitive soul.
[Magisk] Vision:
Please don't start confrontation about English, and the 2 sides they are right, many people like me not have English first language, but when we write a post must be careful about the correct position and grammar of the words
[Magisk] GbnrVR:
Alright, so I am using the Fork by osm0sis, and I input all the props that are needed, and it doesn't work, I'm only passing Basic Integrity, not device integrity (and i'm not talking about strong integrity because the fork github has made it clear that it WILL not pass strong integrity). My device is Pixel 8 Pro, rooted with Magisk.
[Magisk] Nergal di Cuthah:
Probably a bad fingerprint, try another

Secondly could be that the gms.unstable didn't die after the fingerprint was filled in.

Is the donor rom a initial sdk of oreo?
[Magisk] GbnrVR:
where would I find another fingerprint though?
[Magisk] GbnrVR:
i got the info and props from the Android 14 build.prop of my phone.
[Magisk] xSnowLeopardx:
Start the FP hunt. We have given a lot of tips in this thread. What helped me was searching for Android 8 or 9 build dumps. Then looking for build.prop, yeeting it into PixelFlasher and then trial and error.
[Magisk] Nergal di Cuthah:
Well that definitly won't work, you're trying to trick something into thinking you aren't you.

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

These links should explain how
[Magisk] Vision:
You must write in the pif.json the fingerprint you found from a old not from your new phone or other new
[Magisk] Alpha_Geek1:
I had PIF v14.8 and it worked to pass MEETS_DEVICE_INTEGRITY. I have not put any values in /data/adb/pif.json. All the key values in this JSON file are empty strings except for FIRST_API_LEVEL which says 21.

When this stopped working for Play Integrity, I waited for 14.9, updated the module, rebooted.. no dice. My device is OnePlus 7 Pro. Build info has 'walleye' in the fingerprint. I did adb shell getprops on a fully sotck never-rooted OnePlus 7 Pro Sprint 5G (now being used on T-Mobile) and set my pif.json values from that. This caused SafetyNet to fail CTS, and still no Pley Integrity MEETS_DEVICE_INTEGRITY. I reverted/removed the values from pif.json, rebooted, and now SafetyNet passes again, but I have not regained DEVICE Play Integrity.

Questions:

Do I actually need custom fingerprint values in pif.json to make PIF work? It seemed to work without this until very recently. If I *do* need to have values in pif.json, do they need to match what the settings-->build info says about the device (the stuff mentioning 'walleye')? I have some old stock ROMs - they are .ops files, but nothing older than Android Oreo (9).

Happy to sit tight if this is not something I can do anything about myself.

Thank you!
[Magisk] Fishawy:
Yes, the DEV started removing the included fingerprints in recent releases. You're gonna have to find and use your own private fingerprint, and there is a couple of great guides being shared on almost every page here to help you.
[Magisk] Homeboy76:
< < Edit > >

Nevermind, I figured it out. 😁
[Magisk] ew:
Given the fact that the module no longer includes fingerprints, are there any functional differences between this module and the osm0sis fork? Are there any reasons to go one way or the other - and if so, what are the considerations at this time.

(I have a working pif file (and a few reserve ones).

Thank you in advance for any replies and/or information.
[Magisk] osm0sis:
Your app might be detecting the resetprop. There was an old version of PIF that used an alternate resetprop from @huskydg's Pull Requests which might work.

Very different, mine was forked after the PROPS v2.1 build, (just before chiteroman's 14.0 merge of the 2 branches and rewrite), so a particularly stable time, and then I've just worked to weed out bugs and expand features rather than rewrite things constantly.

See here:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] badabing2003:
New Release:

Dec 26, 2023 v6.5.0.0

Retry downloading with disabled SSL certificate verification if SSL error is encountered during TheFreeman193 pifs download. Print an alert to warn the user.

Added testing with YASNAC

Display a warning toast during Play Integrity test, when the Active Pif window content is not in sync with the device's pif.json.

Added Paste Down button to transfer the contents of Active Pif to Output Console (useful for reprocessing a pif.json.

Added Reprocess button to reprocess and produce pif.json compatible with the installed module version. Useful when different versions of modules require / depend on different fields / props. (Note: this is compatible with @osm0sis modules, @chiteroman modules change often and it's hard to keep up, I've done my best to keep compatibility with some of those versions).

Fill in missing build fields from fingerprint or vice versa.

Added an option to add missing fields with values from running phone (not the donor print)

Added an option to point to a directory full of json files and import them to favorites.

Added an option to disable UIAutomator (useful for devices that have a buggy UIAutomator). coords.json file can be manually created to run the automated tests. See #137

Did some code refactoring.
[Magisk] pndwal:
Google does not enforce hardware-backed verdict enforcement (server end) for all devices that are capable of the same, and first identified those slated for such by means of model prop(s)... Even when they began using fingerprint prop(s), this was not used for all hardware-backed verdict capable devices; for some they still only used model prop mismatches (ie. mismatches with expected values for your device)... Thereafter, more and more devices began to have hardware-backed verdict enforcement applied on the basis of prop

sets

which include fingerprint prop(s), and now a number of other props are evidently checked against the print prop, so the fingerprint prop has become key... Further, Google is evidently applying hardware-backed verdict enforcement (no longer making exceptions) to all Android 13 launch version devices so first API level and associated API level props will necessarily trigger hardware-backed verdict enforcement if set to 33+ and it's a safe bet that fingerprint + other associated props for these devices will also trigger to same...

Further, while there may still be devices extant where bypassing hardware-backed verdict enforcement can be achieved with model prop mismatches only, it's clear that for the vast majority (all?), fingerprint + associated props must now not match expected values for devices slated for such enforcement... So we're simply looking for prop sets not used by Google to identify devices slated for hardware-backed verdict enforcement to use for spoofing/bypassing such enforcement...

I put more details about how hardware-backed verdict enforcement and bypassing this is achieved (basics of how USNF and forks (inc. PIF) work) here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89167147

and more under 'a bit of history' here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89186994

👀 PW
[Magisk] niko26:
For some reason my older, outdated PIF version still works. How do I find out which info/fingerprint it currently uses and how can I export the info, in case I need to update to a new version? For example if I need to reapply/reinstall the module?
[Magisk] HippoMan:
If it's a @chiteroman PIF version, save this file: /data/adb/pif.json

If it's an @osm0sis PIF version, save this file: /data/adb/modules/playintegrityfix/custom.pif.json

If you're switching from the @chiteroman PIF version to the @osm0sis PIF version, save the first one and then rename it and install it as the second one ... and vice-versa.
[Magisk] eugenwollekneul:
Depends on which pif module you are using and which version.
[Magisk] BoomBucks:
This module has been unreliable with the Pixel 8 Pro, in my experience. Have been having to install updates almost daily, yet it's broken most of the time. Now even AdAway doesn't work, let alone streaming or financial services.
[Magisk] HippoMan:
Are you running Android 14, by any chance? One of its versions (I forget the exact acronym in that version name) is known to be problematic.
[Magisk] BoomBucks:
Yes, I'm on the latest stable releases of Android and Magisk.

Any way to fix this? @osm0sis fork is falling CTS, too.
[Magisk] majorfigjam:
If adaway is not working, that's a wider magisk issue. Maybe uninstall magisk, reboot and reinstall it. Make sure you allow systemless hosts. Then add the osmosis fork, and a custom pif (see PM) only, before adding any more modules. Also clear cache of playstore and play services before retesting.
[Magisk] HippoMan:
I don't know how to fix it, unfortunately.

If it turns out that you happen to be running on Android 14 "QPR2", I now remember that this is where the Android 14 issue that I mentioned is occurring. I don't understand all the details, but @osm0sis wrote the following recently, which *might* be related to your problem ...

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89237164

But if you're not running that QPR2 version, then I'm sorry, but I don't know what you might want to do.
[Magisk] osm0sis:
You have to supply your own custom.pif.json. Lots of resources here for finding one.
[Magisk] HippoMan:
Oh ... so I was on a totally wrong path with this. Please ignore my comments above.
[Magisk] BoomBucks:
Ok, thank you @osm0sis and @HippoMan. I'll do some more research later tonight and report back.
[Magisk] makeyourself:
The issue of resetprop detection has been fixed in Magisk Alpha, I'm currently using it succesfully.
[Magisk] ruiisaactan:
are there any downsides to using an android 12 fingerprint on a newer android version like 13 or 14. e.g. like missing features or apps unable to download