yashsingh1/xdaforums huggingface dataset:
[Magisk] badabing2003:
If the Xiaomi.eu print is failing for you, don't go hunting for prints, figure out what is wrong with your setup.

Uninstall module, reboot

Install osm0sis fork v4

reboot

follow the guide and test with Xiaomi.eu print, it should pass.

You didn't say what device you're testing on.
[Magisk] theofylaktos:
i wish happy holidays to everyone! Quick question, is there any solution for the Google Wallet to work again after the recent security updates? For Google Pixel 7 pro.
[Magisk] chrbur:
Stupid question, can't I read the fingerprint data from a non-rooted device and import it into the rooted device? How can I read the Informationen?
[Magisk] QoOdrink3r:
Any chance to get it too? :)
[Magisk] eugenwollekneul:
My device is a Poco F3 with crDroid 9.12

this is the console output of PF

===== PIFS Random Profile/Fingerprint Picker =====

Copyright (C) MIT License 2023 Nicholas Bissell (TheFreeman193)

Downloading profile/fingerprint repo from GitHub...

Traceback (most recent call last):

File "urllib/request.py", line 1348, in do_open

File "http/client.py", line 1294, in request

File "http/client.py", line 1340, in _send_request

File "http/client.py", line 1289, in endheaders

File "http/client.py", line 1048, in _send_output

File "http/client.py", line 986, in send

File "http/client.py", line 1466, in connect

File "ssl.py", line 517, in wrap_socket

File "ssl.py", line 1108, in _create

File "ssl.py", line 1383, in do_handshake

ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "pif_manager.py", line 529, in onFreemanPif

File "runtime.py", line 2422, in get_freeman_pif

File "urllib/request.py", line 216, in urlopen

File "urllib/request.py", line 519, in open

File "urllib/request.py", line 536, in _open

File "urllib/request.py", line 496, in _call_chain

File "urllib/request.py", line 1391, in https_open

File "urllib/request.py", line 1351, in do_open

urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)>

And if i request the xiaomi pif there are only 7 lines, the line with FIRST_API_LEVEL is missing, dont know if its relevant.

what could be wrong in my phone setup?
[Magisk] vettean:
I am aware of the post, but there was no vendor build.prop on the tablet so I used the only 2 .prop files on the device.
[Magisk] chuppito:
I want to test it, mine doesn't work
[Magisk] xSnowLeopardx:
People starting to ask for a FP in here... this is not what I expected. Call it Christmas spirit but we should teach a man how to catch a fish, yada yada.
[Magisk] rocketda7331:
Wrong time on phone or some firewall/vpn/dns issue is my first guess
[Magisk] niyas90:
Does this new fingerprint situation affect the older devices. (before 2019)

Sent from Redmi Note 5 using ReLabs
[Magisk] Wolfcity:
If you're using the

gen_pif_custom.sh

script by @osm0sis you can paste an empty dummy file in the folder called vendor-build.prop together with the original build prop.

Script will be working that way.
[Magisk] badabing2003:
If you use PixelFlasher, there is a option under Device Menu to read the fingerprint data from your device.

You can even dump the entire properties set as json if you wanted to.

For the first problem, for whatever reasons your computer is not liking the ssl certificate.

What OS are you running?

You can download the file manually and unpack it yourself, PF will find it and won't try to download.

Here's how you do it.

Download this file: https://codeload.github.com/TheFreeman193/PIFS/zip/refs/heads/mainOpen

In PixelFlasher, under Help Menu, click on Open PixelFlasher Working Directory

Extract JSON directory (not the parent) from the zip file, which happens to be under PIFS-main into PixelFlasher's working directory

Rename JSON directory to TheFreeman193_JSON

If you navigate to TheFreeman193_JSON directory you should only see

View attachment 6047655

As for Xiaomi.eu rpint not working

Try adding the following and see if it makes it work.

I don't know why they haven't included it it.

Next version of PixelFlasher, will allow you to reprocess a json file and fill in the blanks (depending on the version of the module installed) for the missing fields.
[Magisk] vettean:
Just wondering on this Christmas day, how many noobs like me have given up trying to get a FP to work on their rooted phone. After trying for the better part of a day, I give up. I have rooted my phones since 2015, and will keep my current OP 8 Pro rooted for the time being even though I can no longer get it pass Device Integrity. My banking apps still work and no longer being able to Google Pay is not that big a deal. I do feel bad about having to throw in the towel, though.
[Magisk] noooooo:
I've got 4 working FP, but even if google play store shows meets device integrity, google wallet displaysthe device does not satisfy the safety criteria. Am I doing something wrong? device pixel 2 xl on android 11 and PIF 14.8
[Magisk] V0latyle:
To be clear, you are meeting both BASIC and DEVICE, correct?

Clear Play Services data

Clear Play Store data

Clear Wallet cache

Reboot and open Play Store again
[Magisk] Dragon Kumera:
So I think my pixel 8 pro running into this issue. The pif I been trying to get with pixel flasher have still been failing device integrity. Do I just run your export command?
[Magisk] noooooo:
This indeed worked! I was for sure clearing the wrong combination of data/cache of the apps. Many thanks
[Magisk] majorfigjam:
Use adb getprops to get the information from the non-root device, and copy paste it like you did for your working print.

Will it work to get 2/3? Maybe, but unlikely unless the donor is stock bootlocked Oreo or less.
[Magisk] Iridule:
@badabing2003 Compiled from source, got it working on Zorin 17. Thanks :D

View attachment 6047672
[Magisk] badabing2003:
You know you could have got it to work by just filling in this setting.

View attachment 6047675
[Magisk] majorfigjam:
Yes.
[Magisk] Iridule:
Interesting Didn't know that one. I am fairly new to linux been using it for about a year, Long story short I wanted to be able to decrypt ps3 hard drives and had to learn to compile linux kernel and I had never used the OS before, was a fun project. I noticed I did have to install libSDL2-2.0...where is the setting you mention above to delete bundled libs? Before when I tried to fun PF crashed soon after initial start. ?
[Magisk] Bladius:
14.8 banned, not work meets_device_integrity
[Magisk] HippoMan:
I already have something similar in Tasker, except it doesn't do the random pif.json selection.

I'll work on this Tasker suggestion in my not-very-ample spare time and then post it.

... and please, no need to put any cookies in the stockings by the fireplace.
[Magisk] majorfigjam:
14.8 can not be banned, there's no print to ban.

You'll need to find yourself a working print.
[Magisk] xSnowLeopardx:
What in the 2013 transitions is this
[Magisk] HippoMan:
One way to pass 3/3 green is to get a new, second Android device for Christmas with a stock ROM, and not to unlock its bootloader.
[Magisk] majorfigjam:
Bah humbug, although I also feel it's time to start rolling out RTFM more often.
[Magisk] HippoMan:
There is nothing to ban in 14.8, because it doesn't install any fingerprint. 14.8 is designed for everyone to find and install their own fingerprints.
[Magisk] badabing2003:
Some stuff are broken on 14.8

Switch versions and you should be fine (assuming that you have a working print)
[Magisk] osm0sis:
Regressions from the latest several rebases no doubt 🤦‍♂️
[Magisk] hackwerk:
As I described in this post I now have a new problem (see sig for actual versions):

I discovered I had to use Magisk Delta (& PIF) to not only pass all tests, but because Bybit (crypto app) did not work and apparently detected root (and shuts down), also needed to enable SuList (access) instead of MagiskHide list (block).

Bybit now works again, and all other apps are fine too (only enable apps that I need to have root), BUT:

Since SuList OR since a few versions of PIF ago, I do not anymore pass DEVICE INTEGRITY (STRONG INTEGRITY never worked) and do not pass CTS Profile match. Both checked fine before.

I could not care less, but now 1 app does not work; NEXT bank app from Krungthai Bank (Thailand)

Anyone?
[Magisk] miho171:
Got 9 prints in 5 minutes trying, backed up for future days
[Magisk] miho171:
Often the script check the same fp, but I found atleast 1 every 5 attempts
[Magisk] Iridule:
Evidently it's meant to mimic compiz. It's new to me too (First time I've used Zorin os)
[Magisk] majorfigjam:
Ok, easy question. Do you have a custom print, as required by latest PIF versions?

If not, find one. If yes, the maybe the Bank has tightened up its security.
[Magisk] nuttapolkung:
how to find a custom print?
[Magisk] Nergal di Cuthah:
🔧 [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

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] nuttapolkung:
Thank you
[Magisk] Nergal di Cuthah:
Fixed the third link while you typed
[Magisk] majorfigjam:
Bah humbug! You've created a login, asked for help - did you even try reading any of the previous posts?
[Magisk] dedalos91:
The 14.8 don't work for me any more.

if I can't search and if I want integrity to work on the phone without tricks (I don't have free time at the moment) then what should I do? I have to lock bootloader, remove root and remove custom recovery, will that be ok?
[Magisk] majorfigjam:
Yes, but in locking your bootloader after reverting to stock, you WILL wipe your device.
[Magisk] HippoMan:
Oh, you beat me to it!

Good job!
[Magisk] DougMG:
If you do not want to use PIF to pass integrity checks then yes you will need to flash the stock ROM for your device and lock the bootloader. Locking the bootloader will reset your device back to factory settings and wipe all user data in the process.
[Magisk] dedalos91:
I have not other option. I understand that there won't be a newer version after 14.8 and I don't have my own pif (although I know the process)
[Magisk] HippoMan:
This is great! Thank you!

I was already writing something similar, and I finished it now, so I'll post it as well.

I wrote a script which can be run from within the device or via ADB, and it will install a random print. And I also wrote a simple Tasker profile which will fire off this script at boot time.

In case you want a script that is callable outside of Tasker to install a random fingerprint, you could use my code to get that script.

I'm not trying to compete with you, @CZ.Kostra, as your Tasker profile is excellent. I just want to supply my version also, in case someone wants to use Tasker *and* also use a stand-alone script ... or in case someone wants the stand-alone script by itself.

https://xdaforums.com/t/script-for-randomly-installing-custom-device-fingerprints.4647408/
[Magisk] simplepinoi177:
Plus, to be kept in mind, because of loss of root, any backup method used (outside of Google backup; which is severely limited) won't be able to restore 3rd party (non-Google Store installed) apps nor any apps' data or settings -- as you'd need a root backup and restore option and root access to restore all that stuff too!
[Magisk] YMatrix:
Hello!

So version 14.8 isn't working for me (only getting basic with my FP)

Went back to 14.5 and it's working (basic and device)

I'm guessing it has to do with my custom FP using api 25

My question is about a long talked bug on samsung devices causing wifi calling to not work. I am having this problem - is there any fix for it?
[Magisk] badabing2003:
If you need a print, truly need one, and don't have one, then see this thread.

🎣 Pif Game Theory 🎣

Cooperate or Defect? This is an experiment to test if cooperation truly works (I personally believe that it does, but let's put it to test) What does this have anything to do with PIF? Well, I'm glad that you asked. In the spirits of holiday...

xdaforums.com
[Magisk] Vision:
Yeah, i know that, but unfortunately I don't have the resources (💸) lol 😂
[Magisk] HippoMan:
Well, maybe Santa will give you a nice Christmas present! :)
[Magisk] fkofilee:
Anybody know if LG has been backlisted in anyway?
[Magisk] Vision:
I wish that (i wish you the same), the only i have is my old phone and not have Strong (Stock without root and pass 2/3)😂 and from 2024 i read many apps use Strong
[Magisk] Nergal di Cuthah:
I doubt it highly, where ever you heard that I'd take it with a grain of salt.
[Magisk] HippoMan:
If I ever find myself in a situation where I can no longer avoid using an Android or iOS device for contactless payments instead of plastic cards, I'll get Santa to gift me a smart watch whose bootloader I will keep locked, which I can use as a wallet.

I'll go for the cheapest one I can find with the fewest features, because all I'll use it for will be telling time and making those unavoidable contactless payments.
[Magisk] HippoMan:
Over time, I think more and more apps will indeed start requiring STRONG, but I think that will happen gradually, not suddenly in 2024, and I also think that there will still be plenty of apps who don't require it.
[Magisk] Nergal di Cuthah:
And when it does, xda will find a way to break right through.
[Magisk] Vision:
Yeah understand your point, all the government say no more cash and after say no more plastic cards, only via smartphone, don't they know many people don't know how to use all this technology? But they don't care unfortunately
[Magisk] HippoMan:
Is there a 14.9 PIF release now? I saw a mention of 14.9 in the TG group a few minutes ago.

Or maybe that was just a typo ... ???
[Magisk] Vision:
I think is a typo, because i check not see anything, and one say he test the 14.8, 14.8 fix and 14.9, what 14.8 fix?

View attachment 6047752
[Magisk] sawdoctor:
There's a test release on telegram for people having issues with 14.8. I'm guessing people are referring to that as 14.9
[Magisk] linuxares:
Actually... I never tested that print. I should test it.

Also Pixel 7 Pro is my device.
[Magisk] jabennett:
Ugh, this is probably the single biggest thing that keeps me rooting my phones after all these years. The fact that Google implemented a thoroughly effective method for backing up apps and data years ago, but still hasn't made it universal/mandatory for app developers, makes it somehow even *more* irritating.
[Magisk] linuxares:
Seems like I fail with both osmosis and the original module with the xiaomi.eu.

I gonna test the module I used before testing again.

EDIT: Yeah, Play Integrity Next works. I guess something isn't working well for me with the newer versions?
[Magisk] sawdoctor:
Not running android 14 beta are you?
[Magisk] linuxares:
Nope, plain old latest stable from December for Pixel 7 Pro.

EDIT 1.4.9-TEST works. But I seem not be able to find a working print with PIFS (maybe it takes forever?)
[Magisk] mike.s:
Are they going to give everyone a free smartphone to replace the plastic cards they got for free?
[Magisk] eugenwollekneul:
I am running Garuda Linux (Arch based)

The link you posted ends in a 404 error.

For the Xiaomi print you have written: "try adding the following and see if it makes it work." but I don't see the following.
[Magisk] dosbuddy:
See module.prop of the latest TG version:

version=v14.9-TEST
[Magisk] badabing2003:
I'm sorry, which link are you referring to?

I make too many posts to remember them all.

As for xiaomi prints, they haven't included FIRST_API_LEVEL try adding that with value of 25.
[Magisk] FrogMaster-:
I'd just like to extend my thanks to @osm0sis @badabing2003 and @V0latyle. I read through all the valuable information you've all left in your posts and had a fairly easy time finding numerous functional PIFs to allow Google Wallet to work.

I much appreciate the wealth of information you've all shared and the tools you've developed. Really big thank you.
[Magisk] osm0sis:
Exactly, @badabing2003 has it right.

NEXT uses a FIRST_API_LEVEL of "null", which is crazy and bad, and I'm surprised it works there: https://github.com/daboynb/autojson/blob/main/pif.json#L9

Change that to something proper like 25 and it'll pass on mine (until it gets banned), I'm sure.

Edit: Yep, tested and confirmed working. 😉
[Magisk] Umgak:
Gotta love their commit history of -.- and Empty-Commit every 5 minutes as well. Super useful.
[Magisk] REM_8:
Has anyone managed to pass basic & CTS on a GP7P? if so can you please publish a tutorial or steps taken? thanks
[Magisk] cosy6ay:
is the 14.6 pif, compatible with osmosis v4?

unable to get it working on v4 fork.
[Magisk] osm0sis:
Isn't the 14.6 PIF print banned?

If you're talking about a custom one, then yes it should work, unless you're on the Android 14 QPR2 Betas, since ShadowHook is broken on those, and I'm giving ShadowHook a chance to fix it before jumping ship since QPR2 isn't out until March.

shadowhook_hook_sym_name of __system_property_read_callback broken on Android 14 QPR2 Betas · Issue #53 · bytedance/android-inline-hook

ShadowHook Version 1.0.8 Android OS Version 14.0 QPR2 Android ABIs armeabi-v7a, arm64-v8a Device Manufacturers and Models Google Pixel Fold, and others Describe the Bug The following code is workin...

github.com

If you're on stable Android 14 and certain whatever print you're referring to still works on 14.6 then I can say with some certainty it's just some level of user error/learning curve, so feel free to PM me and I'll see if I can help you figure it out.
[Magisk] cosy6ay:
i am on qpr2 hence it not working.

thanks for your advice.
[Magisk] majorfigjam:
It's the same as any other device, unless you have QPR2 beta. There are various tutorials here, maybe start with the "most liked" post.
[Magisk] TheRomRooster:
Yes, osm0sis play integrity fix v4 + private PIF gives basic and CTS on cheetah
[Magisk] tom1807:
To my knowledge, LG hasn't been used in any of the Xiaomi.eu files, so there is a chance that LG is not banned.

However, you could test them.

Cheers

Tom
[Magisk] tom1807:
He is probably referring to this link:

Cheers

Tom
[Magisk] sawdoctor:
Just use the version from the aur
[Magisk] sawdoctor:
I'm on qpr2 and been running v14 with a custom fingerprint for over 3 weeks no issues. Tbh with all the changes i think v14 itself is the safest on QPR2 beta
[Magisk] eugenwollekneul:
Thx I will give a try.

Btw I managed the problem with the link, had to remove the word "Open" at the end.
[Magisk] Vision:
We wish for that, but i don't think they care about us, just they woke up one day and make ridiculous laws, at our expense 🤣
[Magisk] Vision:
@HippoMan

View attachment 6047911
[Magisk] castaway1:
hello community im on Oneplus 5T derpfest ROM latest A14 latest magisk,shamiko 7.5.0 amd PIF 14.9 but still can't pass MEET DEVICE INTEGRITY what do you suggest me to do? i clean data for wallet, play services rebooted reinstalled modules etc.

i had it working several times foe several daya but it Google keep banning my fingerprint propably.

will this ever end or im forced to use stock ROM and lock bootloader to get Google wallet to working ?

thanks everybody involved
[Magisk] Vision:
Yeah, because Is not about rooted phone, with force Strong effect older phone like my old phone is from 2015 stock not root and pass 2/3, if Google or other force to use Strong, losing customer because many people still have phones as primary from 2015 with android 7
[Magisk] Vision:
Probably block it or is not right your FP, and unfortunatly if not someone found a solution, google block it all in the end and we must use stock ROM and lock bootloader to get Google wallet to working or other thing
[Magisk] Bladius:
14.9 still not work on Redmi Note 10
[Magisk] safelock1:
hello, I have 14.9 and realme 8 (lineageos 20) and actually not work good.

I testes change pif.json any other and if I test integrity via google play-> developer then resolve me information: Realme 8 not OPPO, XIAOMI etc to write in pif.json.

How to run good pif.json on realme 8 and lineageos?

I change /data/adb/pif.json (on phone via adb shell->su) and reboot phone
[Magisk] Vision:
This module only spoof the Fingerprint you add in specific process and not global, this mean all other app and test show your real phone and not the Fingerprint you add to pass
[Magisk] safelock1:
How to check if the pif.json file has been loaded correctly? Any command from the adb console?
[Magisk] acwcanada:
You mean Google change something in their Android 14? Anyway, thanks and hope you fix it out.
[Magisk] chiteroman:
This is the problem:

Behavior changes: Apps targeting Android 14 or higher | Android Developers

Learn about changes in Android 14 that will affect apps when they target Android 14 or higher.

developer.android.com
[Magisk] acwcanada:
Do I need to also install Shamiko?
[Magisk] chiteroman:
No.
[Magisk] Stillhard:
While I know this is not for me to test, but i gave it a go with the result failed in Strong ;) in my device
[Magisk] acwcanada:
Finally it passed all 3 including strong integrity! However I have to reboot a couple of times as in first reboot module shown that Zygisk is not loaded due to incompatibility, see attached picture for what I have seen.

In 3rd reboot the incompatibility error is gone.
[Magisk] chiteroman:
Strange... At least, it works xD
[Magisk] chiteroman:
Which one did you try ?
[Magisk] Stillhard:
This one
[Magisk] chiteroman:
Updated module (again).

- Fixed A14 compatibility due to restrictions of non read only .dex files: link

- Updated .dex file to latest @Displax did: link

- Removed useless native code.

You don't need Shamiko neither have GMS in deny list (module will remove it in system start).

If you don't pass Strong using this @ me and provide logs ^^
[Magisk] Stillhard:
Tried this, still failed to Strong

Edited:

But the one from the fist post saved the day (y)
[Magisk] chiteroman:
Yep, your device must spoof first_api_level to 33 to pass Strong, if you try latest release, sure it will pass.
[Magisk] Stillhard:
This must be in bold :LOL:
[Magisk] chiteroman:
Also, the Strong variant of safetynet-fix works for you? Because it does the same, it removes that property:

View attachment 5960647

Very strange...
[Magisk] Stillhard:
No, only the one i mentioned here that works
[Magisk] chiteroman:
View attachment 5960655

It sets to 33 :O
[Magisk] Stillhard:
Yes :D

@andy242 stated that too in here
[Magisk] psychoela:
Any riru version or without zygisk mode?
[Magisk] supermansaga:
Per Google support website at

Increase your online security with VPN by Google One - Android - Google One Help

If you want more protection from hackers and online monitoring, you can make your connection more secure with a virtual private network (VPN) by Google One. Turn on VPN by Google One in the Google One

support.google.com

The following are the main culprits when Google one VPN doesn't work. Obviously there are now posts claiming rooted would still work, but one can't have LSPosed modules and another say LSPosed modules are ok, except may be certain ones would break it

Your device is rooted or isn’t up to date with security updates.

Your bootloader is unlocked.

You run a beta or other unofficial version of Android.