yashsingh1/xdaforums huggingface dataset:
[Magisk] Vision:
I read most users say have 20-50 FP and if Google block 1 used other, but the unlucky is if Google block it many and a user have these what a bad luck then, for that i have only 5 (2 donations, thanks again, and found 3 myself) :ROFLMAO:
[Magisk] changhuapeng:
Thanks for your kind words!

This is just a side project that I'd tinkered in Tasker, early this month, when Xiaomi.eu implemented their module apk. I was simply nudged by @osm0sis' post to clean up, package and then release the project, so some credit goes to him too. :LOL:

Announcing this app on XDA is enough for me. I'm still looking forward to more people finding their own fingerprints so I'm not trying too hard to push for the uptake of this app.
[Magisk] woody4165:
Thanks!

where can I find a (or the) script to test build.prop ?

I'm still learning about this since this is new for me, but reading all the messages, also in silence, I'm understanding more.
[Magisk] zgfg:
Module removes GMS for good reasons - how/why answered hundredth times here

Test that prints with YASNAC and if it shows CTS Eval type Hardware backed, them FORGET about using that prints (from your own phone). Mine from Internet instead
[Magisk] zgfg:
Like ten days ago I posted my script here with description how to use -.the post is burned now under a pile

It's for Terminal emulator or easier, to be started by Execute from MiXPlorer (MiXPlore must have the root granted)

You just start it from the given folder and it crowds and tests all JSON file it finds. And it lowers FIRST_API_LEVEL if there is a chance to make it pass. It deletes JSON files that do not pass, leaves the ones that pass and saves the results to the list file

There is also another thread named like Instructions for noobs, it has only a dozen of pages, it can be easier found there

After the XMas I will update the script and post again
[Magisk] Dragon Kumera:
So where is the one module solution? I am willing to try to get the fix just have no idea how.
[Magisk] HippoMan:
My earler crDroid ROMs didn't have that problem. It seems phone-model-specific.
[Magisk] majorfigjam:
It's posts like this one which make the rest of us wonder why we bother to try to share information, and even share jsons privately.
[Magisk] xSnowLeopardx:
Yeah. Mine had it + others for the same phone had it for the 9.x versions.
[Magisk] robbins:
Is there anything else that can affect only getting MEETS_BASIC_INTEGRITY and not DEVICE_INTEGRITY other than the fingerprint / props set by this module?

Because I'm not sure if I'm just getting super unlucky or what, but I've gone through upwards of 100 fingerprints (from that one script that picks ones at random) and they all are only BASIC_INTEGRITY.

If it matters, my device is a OnePlus 7 Pro on a custom build of AOSPA (signed with test keys).

OnePlus7Pro:/sdcard/prints # ls -l /data/adb/oldpifs/ | wc -l
141

140 fingerprints actually.
[Magisk] chrbur:
I think there must be another solution besides testing fingerprints? 😬
[Magisk] xSnowLeopardx:
No. Start looking again. Don't give up.
[Magisk] majorfigjam:
Well you could go back to stock and relock your phone, or carry a second device (maybe a watch) to do some of the things you can't do without a working fingerprint, but other than that you're stuck with looking for a working print.

Perhaps Santa Claus will pm you a workng print?
[Magisk] badabing2003:
Update Release:

Dec 23, 2023 v6.4.1.0 release

Added Get xiaomi.eu pif, use it only if you don't manage to find working print, strongly recommended not to rely on it.

Support for caching of xiaomi.eu pif to avoid unnecessary downloads and processing.

All done in Python, hence no dependency on apktool or Java.

Support for @osm0sis native props.

Minor UI improvements.
[Magisk] Dragon Kumera:
Sorry. Re edited my post for clarification. Willing to help and do what is needed. Just no idea where to start.
[Magisk] okij:
Awesome ...

... video editing. 😂

(Just kidding! 🙃 Congrats!)
[Magisk] majorfigjam:
That's hardly clearer.

But as it's nearly Christmas, I suggest you start by reading the top liked post in this thread.

View attachment 6047313
[Magisk] Dragon Kumera:
thx!
[Magisk] makeyourself:
@TheFreeman193 Can't seem to pass Play Integrity using your PIF Props Collection script. The script seems to run OK, it downloads the collection and it populates my [custom.]pif.json file. I can also see from logcat that PIF is using the print from your collection. However I always fail Device Integrity. Have tried many times with different random prints and with both chiteroman PIF 14.8 and also the osm0sis fork v4. Am a bit confused as to what's wrong! The default print from PIF 14.6 works OK if I install that, but obviously it will very likely stop working soon.
[Magisk] purgy:
Try the FP that's included in the xiaomi mod, and see if that works for you. If that too is 1/3 you have a different issue.
[Magisk] simplepinoi177:
PIF Manager in the tool below is probably the easiest/most-straightforward

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com
[Magisk] TheFreeman193:
Are you using a recent device like a Pixel 7? There appears to be an issue with a handful of newer devices (all Pixels so far) that only support the arm64-v8a ABI where they don't pass with arm64-v8a profiles/fingerprints. If you think this applies to you, you could try forcing my script to use a different set of profiles with the following in a root shell:

export FORCEABI="arm64-v8a,armeabi-v7a,armeabi"

Those with newer Google devices have told me arm64-v8a,armeabi-v7a,armeabi profiles have worked for them.
[Magisk] Bonoboo:
2 All who use

GPay Checker

(monitors Google Pay availability)

Updated to v1.1, sqlite3 binary now unnecessary, delete that Magisk-module.

Important action for app users: launch it after update and grant files access permission.

Without it app won't work, that's Tasker requirement.

Download: APK / Tasker
[Magisk] mike.s:
If it's too much for you, there's a zero module solution. Unroot and go back to a factory image.
[Magisk] Dragon Kumera:
I have been root for years. Rooted my pixel 8 pro day 1 of getting it a few weeks ago. Was solid and fine. 0 issues. Now I find out we have to get our own finger prints. I have no idea how to go about that. Hoping that auto.sh file someone posted here helps.
[Magisk] makeyourself:
OK so I ran the export command and the 3rd print I tried after that worked. Thank you! But make of that what you will lol, not totally sure if it was the export command or just chance that I found a print that works! My device is an Xiaomi Poco X5 Pro (arm64-v8a).
[Magisk] TheFreeman193:
You should be able to tell based on whether the profile/fingerprint was from the arm64-v8a,armeabi-v7a,armeabi directory. It seems plausible this was the issue and would mean it isn't just Google arm64-v8a-only devices needing this tweak. Interesting...

For reference, if the JSON files from another directory are working for you, you can make the $FORCEABI variable persistent in a terminal emulator like Termux:

echo 'export FORCEABI="arm64-v8a,armeabi-v7a,armeabi"' > /data/data/com.termux/files/home/.bashrc
[Magisk] dmenezes:
Thanks for finally coming around to that, @chiteroman! While we still have unburned working fingerprints, that is! 👍👍👍

Now if only the Xiaomi.EU devs did the same...
[Magisk] dmenezes:
You can't be serious -- you must just be messing with us... AGAIN... 🫨😵‍💫😵
[Magisk] dmenezes:
That's not how it works. The card has an internal private key that never sees the light of day, and is used internally by the card to sign a nonce sent by the bank. The bank can then check if it was truly the card that signed it because it has its public key.

MTM (actually, MITM) does not work because the nonce is random for each transaction, so there's nothing to replay.
[Magisk] dmenezes:
Thanks for the detailed write-up. Actually I just bookmarked it in case I ever need to look for another print (the first I ever found exactly 21 days today is still working great -- knock on wood).
[Magisk] dmenezes:
Only if he has been a good kid. Which I guess he hasn't, asking other people for fingerprints and all... 😆😁🤣
[Magisk] majorfigjam:
That's harsh, and who am I to judge? I wonder if he (or she) checked their PM yet?
[Magisk] makeyourself:
Thanks again. I've managed to find 3 working ones now, all whilst $FORCABI was set so all from the arm64-v8a,armeabi-v7a,armeabi directory. Can't be sure but it does seem that this may be needed on my device.
[Magisk] crayoneater:
So the fingerprint MUST be from an older device with FIRST_API_LEVEL below 34? And anything newer can only pass basic integrity?

I see that's interesting, thank you for the explanation.
[Magisk] majorfigjam:
For real? Just read the basic guide in this thread, and you will get all the information you need!

It pretty much has to be a device of Oreo or maybe Pie vintage, which means Play Integrity will fall back to requiring only Device Integrity. From my experience, your best bet is an Oreo 8.0.0 rom and build.prop.

View attachment 6047371
[Magisk] simplepinoi177:
If you review the guidelines the experts have been following that was figured out by osm0sis shown in the 2nd part of the post below (which is the most liked post in this whole 7k+ post thread)...

🔧 [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

Or, as I made an attempt to explain in plainer terms...
[Magisk] crayoneater:
Thanks for the help!
[Magisk] vettean:
I have an old rooted tablet running Oreo that passes Play Integrity without any modules, so I presumed that using its FP on my OnePlus 8 Pro phone would enable it to pass. Searching for prop files, the only ones on the device were build.prop and default.prop. So I tried to process then with PixelFlasher and nothing happened. Any suggestions as to how I might get a working FP off the tablet.
[Magisk] majorfigjam:
IF it is a valid print for your phone, and that's a big if, try manually editing a template file with the details in your build.prop and saving it (named appropriately) wherever your module requires. Use notepad++ or similar. The two forks may use different locations.

Then manually stop and delete caches from playstore and play services.

If it works, great. If not then you have more work to do.
[Magisk] Iridule:
@badabing2003 will PF work on linux mint?
[Magisk] crayoneater:
I've extracted several images from devices that shipped with Android 8, ran gen_pif_custom.sh on their build.prop files, copied it to /data/adb/pif.json, killed com.google.android.gms, and then ran YASNAC, but it keeps on failing because it's doing HARDWARE_BACKED evaluation. I verified that FIRST_API_LEVEL is a small number (20-something) so I don't understand why it keeps on doing HARDWARE_BACKED instead of BASIC. Does anyone have pointers on getting it to do BASIC?
[Magisk] beeshyams:
Maybe it's the cache of YASNAC? clear cache and data and try
[Magisk] badabing2003:
Update Release:

Dec 23, 2023 v6.4.2.0

New feature: Label and save your working pifs into your favorites and load them quickly from a combo box.

Added Get TheFreeman193 Random Pif, credit to @TheFreeman193 for the print supplies and the original logic of randomization based on device architecture.

Other minor improvements.

Guide updated to reflect the changes.
[Magisk] badabing2003:
It should, try the Ubuntu builds

report back if there are issues.

Try testing the Xiaomi pif or TheFreeman193 Random pif buttons and testing those, the xiaomi pif should pass, if it does not, there's something wrong on your device.

Uninstall module, install @osm0sis Fork v4 reboot, and try again.
[Magisk] Iridule:
I get multiple errors mainly ...

(PixelFlasher_Ubuntu_20_04:15441): Gtk-WARNING **: 00:45:32.326: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Mint-Y/legacy/16/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Mint-Y/legacy/16/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Aborted (core dumped)
[Magisk] HippoMan:
Hmm ... because of differences between various flavors of Linux, I'm wondering if it would be worthwhile to release a flatpak version of PF for the Linux world.

I'll look into this in my spare time.
[Magisk] Iridule:
I was going to try to emulate with wine or bottles, but still not working.
[Magisk] chrbur:
I suspect I'm doing something wrong? Any visible mistakes?
[Magisk] majorfigjam:
Yes, you haven't checked your PM to see if Santa Claus gave you a present.
[Magisk] beeshyams:
Looks fine to me

Have you checked the integrity after this using the apps (TB checker, Play Integrity checker or SPIC) or Play Store test?

If it doesn't pass

./pickaprint.sh

Repeat and rinse till you get a working FP
[Magisk] beeshyams:
Santa, I have my own stash but good to see :)
[Magisk] simplepinoi177:
From the most voted post (so I would think it would be hard to miss) with osm0sis' guidelines that the experts follow and refer to....
[Magisk] crayoneater:
ugh I installed the PIF module incorrectly 🤦‍♀️ reinstalled it and now it's using BASIC evaluation. Still don't have DEVICE integrity but at least I am getting BASIC integrity.
[Magisk] Bonoboo:
2 All who use

GPay Checker

(monitors Google Pay availability)

Quick update, v1.2: deleting temporary file for the sake of cleanliness and security.

Reminder: delete Magisk-module with sqlite3 and grant files access permission for app.

Download: APK / Tasker
[Magisk] TheRomRooster:
it would be nice to have a module that rotates all you PIFs on reboot (for the people who use multiple) so its more stealthy and the PIFs get hit less often
[Magisk] xdatin1:
Where to put my own pif.json?

System/data/adb or System/data/adb/modules/playinegrityfix?

I use chiteroman v14.8...
[Magisk] majorfigjam:
It would be nice if the weather would be nice for Christmas, but we can't always get what we want
[Magisk] simplepinoi177:
I have to admit, I am a bit amused & entertained at all the "pif 14.6 worked, but 14.8 won't" in Telegram channel (totally clueless about no more embedded print)....😅🤣
[Magisk] TheRomRooster:
cause people are just too lazy to read or look for a private PIF. Its really not that f ing difficult, just annoying
[Magisk] simplepinoi177:
If Freeman is able to do it pulling from repos on the web, I'm sure someone that's just as good or better in that type of coding could write such a thing but instead of repos from the web, just one's own personal repo in a folder somewhere on the device...
[Magisk] majorfigjam:
Really? How hard can it be to stick all the files in your repo in the folder, and just rename them from time to time manually.

Except when testing PIFs I rarely reboot my phone.

Perhaps someone might ask Santa Claus for a Tasker option?
[Magisk] sawdoctor:
Have you noticed the post count going through the roof? How many people don't even read the release notes to know why it doesn't work
[Magisk] simplepinoi177:
It's funny because it's literally

pinned!

Full explanation and everything. But, if anything, it's causing more traffic towards here for those desperate now looking up "custom fingerprints" and such....😅

It's interesting seeing all these "new members" posting here and the usual other places, making me grin knowing where they're coming from....
[Magisk] majorfigjam:
Scary though. They have seemingly managed to root a phone, install magisk modules etc, but some of them don't even know how to copy a file when you give it to them gift-wrapped and tied up with tinsel.
[Magisk] vamteusz:
View attachment 6047572

i tried more than 200 times and no results
[Magisk] simonirwin:
However, even with your own fp, 14.8 still fails where 14.6 works if your pif has redundant entries. Eg

"SECURITY_PATCH": "xx"

"FIRST_API_LEVEL": "nn",

"BUILD_ID": "xxxc",

"VNDK_VERSION": ""
[Magisk] shoey63:
I agree. You would think it should be a piece of cake. How are they even unlocking their bootloaders? What with installing drivers, correct platform-tools, entering fastboot and getting the PC to recognise it and typing the appropriate unlock command in a terminal/PowerShell.

Maybe they have tech savvy friends or family doing it for them.
[Magisk] shoey63:
That's far too many. Maybe @TheFreeman193 has a suggestion?
[Magisk] sawdoctor:
Still on v14 with custom fingerprint. Don't see why so many people feel the need to update when something works. Unfortunately i can't switch to osmosis fork yet as it's not compatible with A14 beta
[Magisk] CZ.Kostra:
A simple task for Tasker. It will randomly exchange FP from your collection.
[Magisk] Fishawy:
All I want for Christmas is MEETS_DEVICE_INTEGRITY.
[Magisk] Vision:
One user in friday have this problem, and i tell maybe is bug

View attachment 6047587

View attachment 6047588
[Magisk] badabing2003:
After a large system update (manjaro), do not work now. · Issue #111 · badabing2005/PixelFlasher

Like from object, with manjaro. After latest (large) system update, pixel flasher do not work. Tried both ubuntu release + aur release, system and manual platform tool packages, but still not work....

github.com
[Magisk] TheRomRooster:
Santa says "Will you be a good boy and not share the allusive PIF with anyone else?"
[Magisk] TheFreeman193:
Even with the increased usage and a handful of the previously working profiles now blocked, you shouldn't need more than ~20 attempts to find one that passes.

As a side note, the profiles in this collection include extra properties to utilise all features of the @osm0sis fork. There are some changes in the latest @chiteroman PIF module which might conflict with these additional values - you can try switching to the fork or installing v14.6 in this case.

If you can't pass with any profiles using the advice in the above paragraph, DM me your device/android build/PIF module version and we can troubleshoot.
[Magisk] TheRomRooster:
At some point, you will get routine and learn the patterns of what devices are likely to pass compared to others, my first 2 PIFs took me about 100 attempts to find, the last 3 i got within 20ish
[Magisk] iakoboss7:
can i have a present also santa? at some point playintegrityfixnext will stop also i guess >.<
[Magisk] TheRomRooster:
Will you promise not to share it with anyone else?
[Magisk] flawless911:
It's Beautiful really 🥹
[Magisk] TheRomRooster:
Welp, let's do it differently:

Since it's Christmas, I wanna give someone a little gift so the first person to quote reply this post below, will receive a working PIF.

Please be considerate: Don't post it publicly afterwards, don't intentionally burn it and don't participate if you already have working PIFs and backups. This is really just supposed to be a Christmas present from me to someone who is still looking for a working one, good luck, happy holidays
[Magisk] iakoboss7:
actually yes, but you know how trustworthy an internet promise generally is sadly :/ so i dont think anyone would believe me.
[Magisk] iakoboss7:
:D
[Magisk] TheRomRooster:
PIF was given out, merry Christmas everyone
[Magisk] eugenwollekneul:
FYI

I can run the Ubuntu 22_04 appimage on Garuda Linux which is based on Arch
[Magisk] mielletseed:
I want the pif-file please!
[Magisk] bsg411:
Is there a tutorial on how to do this fingerprint thing??
[Magisk] sawdoctor:
There's a working version in the aur as well maintained by one of the manjaro devs
[Magisk] GN-z11:
I'm feeling good today as well and it's Christmas. I am just an avid reader here. But first to reply as well to this reply will receive a FP that took me a while to find. Welcome!
[Magisk] makeyourself:
Here, here and here.

Also see here
[Magisk] mielletseed:
i want it
[Magisk] GN-z11:
I'll send it to you.

Edit : I sent it. Welcome.
[Magisk] Fishawy:
It's really refreshing to see that the Christmas spirit is strong in this thread.

Thank you to everyone who contributes to support the community.
[Magisk] eugenwollekneul:
Right now I testet your latest release.

Getting TheFreeman193 pif does not work getting pif data.

Getting the Xiaomi pif works but it doesn't pass device integrity.

If I load my own working build.prop fingerprint and update the custom.pif.json then I pass device integrity.

I am using the play integrity fork v4.
[Magisk] badabing2003:
I say you should check your setup.

I just retested xiaomi.eu pif and it is still working,

Just for kicks, I pulled a random TheFreeman193 pif and the first one right of the bat worked as well.

What is your device you're testing on?
[Magisk] bellamossa:
Hi everyone,

nice to meet you all. I hope I can find someone in this group willing to move me through my last upgrade of a firmware, which is causing me problems on Magisk 26.4 and Zygisk. Several fixes were unsuccessful. Maybe I didn't do it correctly, so here it is.

I'm Magisk 26.4 using Android 8.0 (not 8.1), it's the most recent OS supported by my Samsung A320FL (old since 2017 but small as I need and amazing, also with Zygisk, till few days ago).

However, Zygisk and all mods were also working flawlessly on my previous Oreo 8.0 firmware, with binary 2. Till then, no app was able to detect Magisk.

However I had the great idea to flash a more recent firmware, still Oreo 8.0, with binary 9 (and ofc I can't revert it back to binary 2 either). Again, Oreo 8.0 is the most recent firmware I can use. Nothing available in newer 8.1+ operating systems.

Of course, both Zygisk and deny list are enabled. But even though, with the binary 9, both Magisk 26.4 and Zygisk became powerless, including their most updated fixes like PIF and USN. Not even hiding Magisk with its internal feature helps. It still gets detected and I can't pay on Wallet or use any other banking app.

Maybe this info might be useful, the firmware security level of my current firmware binary 9 level is Nov2020.

So, as per now, no integrity, no bankning app working anymore. Of course, I can't buy a new phone. It's just my feeling it might depend on the binary. Maybe I don't apply the Zygisk mode or the fixes in the right order. however I would heartly welcome any suggestion.

Few regular anomalies I noticed, since I reinstalled Magisk 26.4 on firmware with binary 9, are that

When the phone reboots or just powers on, the screen switches off for half a minute. In that short time, it doesn't react to physical buttons either.

The phone connects to wi-fi about after about a minute, not immediately.

As soon as it connects to wifi, system notifications appear saying that Google Play Services has stopped working and since then just keeps stopping, never mind if I repeatedly clear cache, data and have the most recent version installed.

With lower versions of Magisk the phone are still passing SafetyNet check, but Magisk gets still detected.

When installing Magisk 26.4, I tried both installation via patched boot file and via internal upgrade from older versions. Nothing helped so far. I'm not sure it depends on binary, it's just my assumption, based on my previous attempts and observations (hopefully wrong).

If no way, I'll have to reflash the firmware with binary 9 and keep the phone unrooted. So, big thanks in advance, to whoever try to come with a working solution or with some new attempts, that I didn't try yet or list already here already.
[Magisk] Vision:
All I want for Christmas is Pass 3/3 and see all green like Christmas🎄Tree. Merry Christmas to all
[Magisk] linuxares:
Man I tried over an hour yesterday and failed over and over again. Just a bad luck of the draw I guess.