yashsingh1/xdaforums huggingface dataset:
[Magisk] novicecoder0:
Yes, Selinux is enforcing. Encryption enabled.

Yes official LOS
[Magisk] chiteroman:
If Basic veredict is failing, DroidGuard is detecting something wrong in your ROM, maybe injection into GMS process. Try to uninstall all Magisk modules except mine and try again.
[Magisk] novicecoder0:
I did and restarted. For a moment the API checker was saying something about not able to get token from google and then reverted to show fails. Attaching the screenshot.

Thanks
[Magisk] pndwal:
Ah... That explains passing S/N on YASNAC... On PIAPIChecker, that's not really failing verdict; Unevaluated indicates network or other issues including 'trustworthyness'...

Try disable Addaway, VPNs, firewalls etc if you have em to test...

Also, 'Unevaluated' responses can mean mean:

So there's likely abnormal issues with your device causing it not to be trusted; Unevaluated accountDetails and/or appIntegrity apparently results in empty deviceIntegrity result; no deviceRecognitionVerdict is called so you're not getting either Hardware or Basic Evaluation for PI API, just a failed response...

I've had LSPosed modules that cause this, eg early versions of @chiteroman's BootloaderSpoofer XPosed module did this on some devices incl. mine... Nb. current version doesn't do that for my device now... So you may want to try with selected Magisk and XPosed modules disabled...

Some have needed to install full stock ROM to restore device trust for these verdict labels if they messed with system... PW
[Magisk] osm0sis:
If it's properly already in the example.pif.json format then it won't need to be migrated. Something's missing/incorrect in the way you filled it out for sure.

What you do is take your pif.json that worked with chiteroman's, simply rename it to custom.pif.json and put it in /data/adb/modules/playintegrityfix then reinstall my Fork v5 zip over top in Magisk and you should see it migrate your file automatically.
[Magisk] thf1973:
Are you by any chance using a newer Pixel device (Pixel 7 or 8)? Then this could be your problem:

🔧 [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] V0latyle:
What would this have to do with Pixels?
[Magisk] thf1973:
Quote from @TheFreeman193:
[Magisk] sawdoctor:
The issue is with the A14 beta firmware rather than pixels but apart from custom ROMs only pixels have A14 beta firmware (QPR 2 is the problem)
[Magisk] mkcs:
Wow, it fills out the empty fields automatically and works now! Without it I wouldn't realize the "INCREMENTAL" is wrong based on the build.prop I copied on the web

cd /data/adb/modules/playintegrityfix; sh /data/adb/modules/playintegrityfix/migrate.sh; exit &>/dev/null

custom.pif.json migration script

by osm0sis @ xda-developers

- Parsing fields ...

- Simple entry SECURITY_PATCH found, changing to SECURITY_PATCH field and "*.security_patch" property ...

- Deprecated entry FIRST_API_LEVEL found, changing to DEVICE_INITIAL_SDK_INT field and "*api_level" property ...

- Missing default fields found, deriving from FINGERPRINT ...

- Renaming old file to custom.pif.json.bak ...

- Writing fields and properties to updated custom.pif.json ...
[Magisk] molitar:
Help is there a recent guide on how to properly setup Magisk with Play Integrity Fix because it fails daily and I have to keep updating this module in Magisk. It seems I should not when I am using stock ROM and my own fingerprints.

OnePlus 6T

Stock OS OxygenOS 11.1.2.2

Magisk Standard 26.4

Modules Installed

Play Integrity Fix v15.1

Process Monitor Tool v2.3

Shamiko v0.7.5

System Hostless 1.0

Zygisk - LSPosed v1.9.2
[Magisk] majorfigjam:
On the right, most liked post.
[Magisk] droidman1992:
I'm using daboynb/PlayIntegrityNEXT, with the gms.apk to get the fingerprint automatically and it's working. Is there any disadvantage in doing it this way as I can't be bothered to constantly look for fingerprints and mess with pifs?
[Magisk] akaloith:
ok 15.1 solved the problems (for as far as it goes)

meanwhile i installed PlayIntegrityNEXT & gms.apk and also worked

but reverted to 15.1

please keep it that way :P
[Magisk] HippoMan:
I want to test a large group of FP files by running *solely* on my Android device ... because I can't afford to tie up my desktop machine for a long period of time running PixelFlasher.

I already have a way to automatedly run through a directory on my device that's filled with FP json files and install each one, but I haven't been able to come up with a way to automatedly check for DEVICE integrity after each iteration, except by means of "uiautomator"-based or "Tasker/AutoInput"-based screen scraping.

Does anyone know of a way to query the phone for DEVICE integrity via a script and then capture this integrity level for logging purposes, without any such screen scraping?

If so, I could run my tests via an extended session on my extra phone, without typing up my desktop computer.

Thank you in advance for any suggestions.
[Magisk] Lord Sithek:
Something peculiar is going on... I installed an update of my system (Xiaomi Mi Note 10, ArrowOS, A13) and I noticed that I can't pass DEVICE anymore with my custom fp I've been using long time (BASIC still passing). I updated PIFork to v5, used migration script, but nothing. I rolled back to the previous build, even done a clean flash and still can't pass DEVICE 😦 Moreover, I use the same fingerprint on my other device and it's still passing DEVICE. I can't really imagine what could go wrong, I don't remember doing anything which could possibly break my setup. Sooooo... 🤷‍♂️
[Magisk] badabing2003:
What is the downside of using uiautomator?

It works and it's automatic
[Magisk] majorfigjam:
I literally gave you a working print for Osm0sis fork.

You're going to have to use it sometime as the print in 15.1 is going to be banned sooner or later, and in any event sooner than the one I gave you.
[Magisk] HippoMan:
I have found that these screen-scraping-based testing procedures to be subject to race conditions, and they also can be fouled up by external events that generate things like notification popups, toasts, etc.

I'm trying to avoid those kinds of problems, if possible.
[Magisk] badabing2003:
I'm not aware of any other method, and none of these application support CLI commands as far as I know.
[Magisk] HippoMan:
Yes, that's been what I have found, as well. I was just hoping that someone might have found a cli-based way to do this.

Oh well ... (sigh)
[Magisk] akaloith:
I understand that the 15.1 fingerprint will be sooner or later banned

I dont understand the rest

if you can help me add me on telegram

edit: now i saw the pms, now i have to learn what to do with it...

===================

Moderator edit: Telegram links deleted. -BIGWORM
[Magisk] iruiz2:
I'm running PIF 14.0 with own fingerprint. 26 days and counting.

Find a fingerprint and relax, people...
[Magisk] osm0sis:
It's dead, Jim! On to the next print.
[Magisk] Lord Sithek:
No way. My second device still passing
[Magisk] xSnowLeopardx:
Almost a month of me using my first found FP.

Hey Google - I dare you to ban this one. Bet you can't. :cool:
[Magisk] osm0sis:
Same print? Also on Fork v4 or v5?

Does ArrowOS use their own spoof of some kind? What's your second device running?

Check the logcat?
[Magisk] vMAC:
So yes I have P8P that I am using. Anything special I need to do or just keep trying fp until I get one that passes?
[Magisk] sawdoctor:
If you are on the beta firmware then unfortunately osmosis fork probably won't work. I think chiteromans latest should work on beta firmware but I'm still using PIF 14 with a custom fingerprint. AFAIK the only problematic firmware/phone is the QPR2 beta
[Magisk] Dragon Kumera:
pif v15.1 is working fantastic for me on my p8p.
[Magisk] vMAC:
Not on a Beta firmware. Just the December release for the p8p
[Magisk] shadowillusion:
Sorry a bit out of topic, but do you mind to also include most properties from service.sh / post-fs-data.sh as spoofable variables inside the json? @osm0sis @chiteroman

Because some bank apps (example https://play.google.com/store/apps/details?id=com.muamalatdin ) is detecting whether these properties is modified or not.

Example in rooted xiaomi, we need to set:

with correct fingerprint in order to pass safetynet. But the bank app will not pass. If i uninstall PIF module, these properties is unmodified and bank apps will launch. But PlayIntegrity will not pass. A bit of dilemma currently.
[Magisk] GabbyWC:
This could be unrelated to PIF but does anyone else's Android phone randomly restart or is this just happening to me? The affected phone is a Xiaomi Redmi Note 9 Pro (joyeuse) which is running the Pixel Experience Plus v12.1 custom ROM along with Magisk v26.4 and osm0sis' PIF Fork v5. Maybe my device is experiencing a hardware failure because the SIM 1 slot stopped detecting my SIM card for no apparent reason but the SIM 2 slot still works. In the next few days, I'll do a clean install of the Evolution X custom ROM (which is based on Android 14) to see if that provides better stability. If the random restarts continue to happen, then I may end up buying a new Android phone sooner than expected. I'd like to wait for the upcoming Poco F6 Pro but that's not likely to launch until a few months from now so perhaps my next phone will be a Google Pixel 8.
[Magisk] Umgak:
Should be unrelated, PIF doesn't change anything related to SIM or radio. Could be another magisk module, hardware failure, ROM issue, incompatible firmware... but it's extremely unlikely to be PIF.
[Magisk] GabbyWC:
I suspect that a hardware failure is the source of the problems. The only other Magisk modules that I've updated in recent weeks are ReVanced Extended and Shamiko. Since Pixel Experience still does not have custom ROM releases based on Android 14, I'll soon find out how Evolution X compares.
[Magisk] livinx:
I am following this thread, and also occasionally updating the magisk module.

Its a cat and mouse game, often im at the store "your device doesnt work" and I have to pull out my card again. Not a big issue, but would be nice to have a permanent fix.

Im reading something all the time about using your own fingerprints?

Im not sure, but has someone made a simple to follow guide?

Is there any way to have a more permanent solution at this moment, or do we have to continue cat and mouse?

Thanks guys for helping me out.

Im a casual XDA noob, and not as deep into everything as you guys seem to be.
[Magisk] majorfigjam:
Read the most liked print on the right side of your computer screen, or by scrolling down on your phone.

Find a print,install the Osm0sis fork, and you'll have a more lasting solution. Not permanent, as google can kill it at any time, but the best we have for now.
[Magisk] titomax82:
I'm really sorry if this can be a stupid question, but how do you know if a device has been released with android 7 nougat and upgraded at least to android 8 oreo? There are thousands of devices! Suppose I search randomly on the web and the I identify a device to test, in the famous dumps' site well known here, i can't find the name found on internet, but strange codenames. Maybe I found a good device to test and it's not in that dumps' repository... useless search or, maybe again, I found a good device to test but I think it's not in the repository beacuse it has another name.

There is something obvious to winning fingerprints' haunters that is not obviuos to other people like me that continue losing.
[Magisk] GabbyWC:
GSM Arena lets you search for devices and when you access such a page, you can scroll down and see which operating system version it launched with. You can find out which codenames are for which devices through web searches.
[Magisk] majorfigjam:
Well you could use gsmarena to find release details.

If you know the maker and the code name, google will usually turn up the model.

Eg Moto + Potter = Moto G5 Plus.

Search a brand and oreo and 8.0 will get you a good start.
[Magisk] mielletseed:
In my opinion is that the big advantage of @osm0sis 's fork that you can set any property. Read the description at github and just try to set your properties in the custom.pif.json
[Magisk] simplepinoi177:
There's been 4 new pages since last night (6PM PST), so if what I'm addressing has already been addressed, I'll edit this post later after I read through all the new posts...I just want to get to it while it's fresh in my memory...

So, in the end, confirming those two work with Magisk and PIFork....

So I imagine you'll be able to if you get both of those (Magisk and PIFork or PIF) set up right...

Yeah...osm0sis goes more into it in the 3rd section of his post...
[Magisk] livinx:
I would like to share a small success I had, and I found the process to be noob friendly enough.

Finding custom fingerprints etc and making them work with files, was too complicated for me.

What I found was this:

GitHub - TheFreeman193/PIFS: A collection of build properties for the PIF module

A collection of build properties for the PIF module - TheFreeman193/PIFS

github.com

Process seems easy, just install Osmosis Fork in magisk:

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

Then run fingerprint fix in Termux:

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

Repeat the last step until you have attestation.

I use this appstore app:

SPIC - Play Integrity Checker - Apps on Google Play

demonstrates the usage of the Play Integrity and SafetyNet Attestation API

play.google.com

Took me about 20 repeats in Termux until I had the needed result.

I found on reddit this explanation:

thefreeman193

I have discussed this with the module creators. I have concluded that uploading a curated list of working fingerprints is too risky. This collection is simply a distillation of publicly accessible build properties which would be no less difficult to scrape if Google engineers were interested. Only fingerprints/profiles that are being used by tens of thousands of people are getting blocked from software attestation. If Google wanted to enforce hardware attestation for all those device profiles, they could and would do so easily with or without this collection.

Sorry if this is old news to anyone!

Im just sharing my experience. I found this process to be easy enough to repeat.
[Magisk] HippoMan:
Cat and mouse continues.

And if anything permanent comes along, I fear it will be a permanent loss for us mice.

Once app developers jump onto the "strong integrity" bandwagon, and once the Googlefrinchians start requiring strong integrity for tap-and-pay, we'll be screwed.

Our only hope is that this "world of strong integrity" will take a long time to fully come into fruition.
[Magisk] livinx:
I think the script i posted should at least improve to get working fingerprints fast.

The community is again coming to the rescue with people like osmosis and freeman.

Im not sure about the strong integrity. I have phones that never had strong integrity even right out of the box from manufacturer. Especially all chinese mid level brands like redmi or so. Maybe just me, but I always run check of phone before rooting and flashing custom rom and found it interesting.
[Magisk] simplepinoi177:
I'm sure it's working fantasticly....for the very temporary short amount of time before it will be inevitably be banned...

You should check out the tool below -- if you're as paranoid as I am about unexpectedly being caught unawares trying to tap & pay at a store and suddenly not being able to out of nowhere...It's not that "permanent fix", but at the very least it might give you a heads up -- I can't confirm if it works or not as my custom fingerprint is still passing, but I see the toast every time my screen unlocks so it looks promising!

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

When I first started out finding my own custom fingerprint -- this was way before any of the automated scripts or methods available now; the only way was manually searching for fingerprints -- I felt like you did! I found that all the devices I really felt had good potential wasn't found at that dumps site...so I had to go and learn/gain-experience on the fly and figured out a few things...which I go through in Section 1.1.2 of a thread of my writeup of my experience finding my own (below)...that might be applicable to what you are inquiring on...

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
[Magisk] osm0sis:
chiteroman has gone back and forth on including them in the actual code a few times, presumably because when not spoofing them globally it will fail in other apps.

I believe there are Magisk forks with an updated resetprop that improve the situation with global properties somewhat.

Very true about my fork however! Instead of needing a new build, you can just add any properties you want to spoof to only DroidGuard to your custom.pif.json and remove them from the .sh files. 🤘

And for the truly lazy who don't appear to mind having their print banned repeatedly, there's the "PlayIntegrityNEXT method" of stealing the latest Xiaomi.eu print, with the last autopif.sh script I shared: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89233630

Of course I do think putting a bit of time into finding a more unique random print with TheFreeman193's pickaprint.sh script is a better solution with more longevity, and I think finding your own very unique print manually will have an even better result.

Really nobody has an excuse not to have a (currently, at least) working print anymore. 😉👍
[Magisk] titomax82:
Directly oreo? Not a device released with nougat and then upgraded to oreo?

After I find a nougat device, how do I know if it has been upgraded to oreo at least?
[Magisk] GabbyWC:
The manufacturer (or a third party web site) may provide factory ROM downloads and indicate which Android versions those files are associated with. This is the case with a popular Chinese electronics company that has been mentioned in this thread. If you need a clue as to that company's name, "X" marks the spot. The article here is useful in explaining how long different companies typically support their phones with software updates.
[Magisk] trevtdogg:
i found it faster and easier to instead just look for build.prop files, and then focus on testing those that have a native API level somewhere between 23-28.

it's going to be trial and error either way, but at least that way you can do the full trial instantly without further work or research, and then see what levels the fingerprint passes.
[Magisk] MartinShoob:
Hi, I'm having this problem with the fix: For some reason, for about 20 seconds after launching I pass device integrity, however after that I'm back to no integrity... I've tried disabling magisk modules, which seems to be the main reason for not passing even basic integrity, however I can't get it to work... any ideas?
[Magisk] trevtdogg:
what "fix" are you using? as in which module, and which version of which module?

are you using a built in fingerprint, or are you using your own custom fingerprint you found yourself separately?

what do you mean by "after launching" - do you mean after a reboot? or after launching what?

how are you checking for device integrity?
[Magisk] Nekromantik:
I tried your script but I think it only works for official magisk as it cant find mine as I am on kitsune magisk. Might need to change the script on my phone to point it to correct binary.
[Magisk] osm0sis:
What binary? What are your telling me? Log?
[Magisk] Lord Sithek:
Sorry for the delay, I had a super busy day today (rhyme not intended😅).

Excactly the same print, on both devices PIFork v5. Different results.

Well I know that Arrow used to provide it's own spoof, however it was never interfering with PIF when installed. My second device is Samsung Galaxy Tab S5e with crDroid A13.

Logcat shows this: (sensitive info removed)

C:\Windows\System32>adb shell "logcat | grep 'PIF'"
12-29 15:29:20.418 19800 19800 D PIF/Native: Read from file descriptor file 'classes.dex' -> 8128 bytes
12-29 15:29:20.418 19800 19800 D PIF/Native: Read from file descriptor file 'pif.json' -> 569 bytes
12-29 15:29:20.477 19800 19800 D PIF/Native: JSON contains 16 keys!
12-29 15:29:20.478 19800 19800 D PIF/Native: Found '__system_property_read_callback' handle at 0xb400007c100e7a40
12-29 15:29:20.478 19800 19800 D PIF/Native: get system classloader
12-29 15:29:20.478 19800 19800 D PIF/Native: create class loader
12-29 15:29:20.480 19800 19800 D PIF/Native: load class
12-29 15:29:20.480 19800 19800 D PIF/Native: read json
12-29 15:29:20.482 19800 19800 D PIF/Native: call init
12-29 15:29:20.484 19800 19800 D PIF/Java: Spoof KeyStoreSpi and Provider done!
12-29 15:29:20.485 19800 19800 D PIF/Java: [DEVICE]: tucana -> ***
12-29 15:29:20.485 19800 19800 D PIF/Java: [SECURITY_PATCH]: 2023-12-05 -> ***
12-29 15:29:20.486 19800 19800 D PIF/Java: [MODEL]: Mi Note 10 -> ***
12-29 15:29:20.486 19800 19800 D PIF/Java: [RELEASE]: 13 -> 7.1.1
12-29 15:29:20.486 19800 19800 D PIF/Java: [MANUFACTURER]: Xiaomi -> ***
12-29 15:29:20.486 19800 19800 D PIF/Java: [BRAND]: Xiaomi -> ***
12-29 15:29:20.486 19800 19800 D PIF/Java: [FINGERPRINT]: Xiaomi/arrow_tucana/tucana:13/TQ3A.230901.001/adams12251711:userdebug/release-keys -> **
12-29 15:29:20.486 19800 19800 D PIF/Java: [PRODUCT]: arrow_tucana -> ***
12-29 15:29:20.486 19800 19800 D PIF/Java: [DEVICE_INITIAL_SDK_INT]: 28 -> 25
12-29 15:29:20.486 19800 19800 D PIF/Java: [ID]: TQ3A.230901.001 -> ***
12-29 15:29:20.487 19800 19800 D PIF/Java: [INCREMENTAL]: eng.adams.20231225.131043 -> *** PIF/Native: [sys.usb.state]: mtp,adb -> mtp
12-29 15:29:20.983 19800 19847 D PIF/Native: [sys.usb.state]: mtp,adb -> mtp
[Magisk] Nekromantik:
Sorry not magisk here is output
[Magisk] andrewff2:
I have an old asus zenphone3 but it's using a custom rom.. should i flash the original rom (Marshmallow or Nougat) in place then try to test the fingerprint? Trying to understand @simplepinoi177 tutorial.. to maybe generate my own fingerprint
[Magisk] badabing2003:
Update Release:

Dec 29, 2023 v6.5.1.1

Support for PlayIntegrityFix 15.1 added keys.

Improved auto-fill (from device) missing fields.

Dec 29, 2023 v6.5.1.0

Added Bulk Reprocess json file(s) (detects module flavor / version and outputs compatible format, similar to previously included Reprocess Pif feature which only applied to the Active Pif).

Get donor device's Pif print, now outputs @osm0sis v5 fork format print (needless to say, donor device must be connected).

Adding to Pif favorites now auto-fills the label with device brand and device model.

Other minor improvements.
[Magisk] MartinShoob:
I'm using the pif fork by osm0sis

I have a custom fingerprint

Yes I mean after a reboot

I am using the SPIC app for checking, but others have shown the same result