yashsingh1/xdaforums huggingface dataset:
[Magisk] Umgak:
This module only spoofs values to the DroidGuard app responsible for Play Integrity API, so using older OS versions will not cause any issues - Play Store will still see your device as A13/14. This is one of the main benefits of this solution over older solutions such as MagiskHide Props Config, which would cause you to be unable to download certain apps as those solutions would spoof for the entire device.

EDIT: Depending on device, an Android 12 fingerprint may be from a device too new for the module to work. Most working prints (in my experience) are from the 7.1-10 range.
[Magisk] ruiisaactan:
i see, so the reason why magisk hide props config causes problems is because it completely swaps the fingerprint info right?
[Magisk] Umgak:
Exactly - MHPC would change the fingerprint globally, while PlayIntegrityFix and forks instead hook the function for getting a certificate and ONLY swap the print out when detecting DroidGuard is the one asking. All other functionality is left as-is - to the point that even the Play Integrity API testers will report your actual device fingerprint, even though DroidGuard received spoofed data.
[Magisk] DAsshh:
so wait.. finger prints dont work? rooted? or why is this thread so confusin..

PIF? am i supposed to save that from my device prior to rooting? what i miss..

🥴🥴🥴
[Magisk] matfcb:
8.5 not working on Xiaomi Mi 9 Pro 5G, not going past Miui logo. I will install 8.4 now.

EDIT. Not going past Miui logo on 8.4 too :/
[Magisk] chiteroman:
Stock or custom rom? Displax mod works?
[Magisk] matfcb:
Xiaomi.eu. 8.4 was fine, but I updated to 8.5 and now it can't get past Miui logo on any version (8.5, 8.4). I delete it will install Displax mod, but I remember I couldn't get Integrity passed on newest version.

EDIT. Displax can't go past Miui logo too. Why is it happening? Should I disable all modules in Magisk before installing any of this fixes?

EDIt 2. 8.5 works, I disabled all modules but Viper4android and it installed and works.
[Magisk] Bladius:
What causes LP to stop verifying from being tested after it is launched?
[Magisk] mcreuter83:
With MagistHideprops working too.
[Magisk] chiteroman:
Oh, seems like verify methods didn't hook well or there are more verify methods in your Android build. I'm working in a better solution.
[Magisk] amk316:
FYI

before enabling the module

View attachment 6008591

after enabling the module

View attachment 6008593
[Magisk] chiteroman:
It happens with Displax module?
[Magisk] amk316:
Yes
[Magisk] dmenezes:
Howdy everyone, and thanks @chiteroman for the module.

Just installed v8.6 on my phone (Xiaomi Lisa running official LineageOS 20 plus Magisk 26.4 with Displax's v2.4.0-MOD_2.0, which was refusing to pass MEETS_STRONG_INTEGRITY), and nothing changed:

View attachment 6008677

I still have Displax's module installed, just disabled it; do I need to remove it to use @chiteroman's?

View attachment 6008681

TIA!

EDIT: if there's anything I can do to help fix this (logs, etc) please let me know and I will provide.
[Magisk] chiteroman:
Google patched Strong pass few months ago. You won't pass Strong with Displax's module neither mine.

As long as my module is active you will not be able to use safetynet-fix because they are incompatible, you can remove it if you want.

I made it deactivated because there were people who installed both modules at the same time and that gave problems, also in case mine didn't work for you or just in case someone wanted to try it and go back to Displax's one.
[Magisk] chiteroman:
Maybe due resetprop utility.
[Magisk] dmenezes:
:-( that really sucks... here's my motivation for that:

View attachment 6008737

Effing bank app, of course... :-(

I'm still backscrolling through this thread and just found your post here: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix-updated-fork.4607985/post-89010993

I'm here rooting (pun intented) for you! I really hope you find a way around this latest Google's effing-ness before long, I don't want to run anything but LOS in my phone :)
[Magisk] chiteroman:
Forget about passing the Strong verdict again, the moment someone finds a similar bug and makes it public, Google will fix it in no time. If any app needs Strong you will have to lock the bootloader, you have no choice.
[Magisk] dmenezes:
Sure thing, I disabled Displax's myself before installing yours, will keep it that way so I can switch between them (making sure to keeping only one of them enabled at all times) and help testing.
[Magisk] dmenezes:
Such is the way of any "arms race" situation like that. I wonder if it really depends on finding a bug, tho -- speaking from the depths of all my Android internals ignorance, why not just replace the part of Google's code that does it, in a worst-case situation, patching over it in memory if necessary? As magisk and your module run as root, that should be as easy as writing to /dev/mem. Of course, the problem is determining the addresses to be overwritten and what to overwrite them with, but it should not be impossible (again, speaking from the depths of my Android ignorance, but I do know a thing or two about the underlying Linux). OFC I know talk is easy and doing not so easy, but....

Noted. But in my previous phone (Also a Xiaomi but of the Curtana persuasion, running LOS 18.1) I had no problem for over 3 years... so I'm not sure at which intervals Google is able to do its thing again (every major AOSP upgrade? Every monthly patch? both? neither?)

Also, a few questions about that, if you don't mind.

1) Locking the bootloader again can only be done using Xiaomi's effing MIUnlock, right?

2) Would MIUnlock even allow me to lock the bootloader with the device running LOS instead of MIUI?

3) And the moment I lock it again, I won't be able to update LOS until I unlock the boot once more, correct?

4) And to unlock the bootloader would force me to go through Xiaomi's 168 hour wait and jump through all its hoops all over again, or not?

Thanks again for all your help and patience.
[Magisk] zgfg:
AFAIK, you can relock Bootloader manually from Fastboot

You can relock only if you first flash the full official firmware. Then relock BL (you need Factory reset when switching ROMs and then relocking BL will also trigger Factory reset)

Otherwise, if BL is relocked with your custom ROM, you can immediately start looking for a paid EDL support (or you will need to find Prog eMMC firehose files for your chipset)

That's generally (not Xiaomi specific and not Qualcomm chipsets specific) - before relocking BL, you must return back to the official ROM, Recovery, Boot

Maybe on MTK phones you could relock BL by staying on custom ROMs, IDK - but otherwise you call for hard brick

Ofc, not talking about ancient KitKat or Lollipop phones

Btw, it's very simple. It will lock the Bootloader (as you asked) but after that it will bootloop to Fastboot (since locked BL requires a ROM digitally signed by the vendor).

But since you already locked BL, you will not be able to flash anything to get out of the bootloop.

And due to bootloop, you cannot boot to System to enable Developer options and OEM unlock (they were disabled by Factory reset) to be able to unlock BL again
[Magisk] chiteroman:
Understand how it works a hardware attestation and a certificate:

Android Keystore system | App quality | Android Developers

developer.android.com

Verify hardware-backed key pairs with Key Attestation | App quality | Android Developers

A tool for verifying security properties of hardware-backed key pairs.

developer.android.com

No, you can use fastboot oem lock and the bootloader will be locked again. But you must install first stock ROM.

Google allows OEM to lock bootloader with custom ROM installed, but the custom ROM must have signed all images. Not all devices have this feature, don't lock bootloader with custom ROM if you are not sure if your device has this feature.

If the public key is the same you can update via OTA, locked or unlocked bootloader doesn't matter here.

No, only the first time you must wait 168 hours, then you can lock and relock all times you want.
[Magisk] Lord Sithek:
So actually by searching for a new exploit, you work for Google helping them to patch their bugs 😂
[Magisk] RockerAlex:
Does this module work with Shamiko and Google Play on DenyList? Seems like Displax doesn't ... I need to hide root so that apps like PUBG will download
[Magisk] majorfigjam:
Potted version:

Google now checks that your device has "device integrity" before certain functions eg wallet will work as intended.

A boot unlocked rooted device is inherently insecure, so you need to use a magisk module to make Google think it has "device integrity"

To use the module, you need "a fingerprint" file, from a donor device old enough that it can make Google believe it has "device integrity", and which Google has not otherwise "banned". Your current device is almost certainly not a suitable donor, else it would already pass the test.

Go to the most liked post in this thread to find out how to get a "fingerprint" file. You will find references here to tools to make finding the "fingerprint" simpler.

Install it and carry on as before, until Google ban that print.

Sorry if you're confused, but given you must have worked out how to root your phone, this bit is relatively easy.

And if your phone is not rooted yet, then you're not having issues with wallet,so don't worry about this thread
[Magisk] gpvecchi:
Guys, what's the terminal command to restart GMS?

Thank you!
[Magisk] Umgak:
su -c killall com.google.android.gms.unstable

Should do the trick.

EDIT: Switched from sudo to su -c as ADB does not natively support sudo command (that's from Termux).
[Magisk] dimak2103:
Which version are you using? 26404?
[Magisk] awarexda:
Using now a custom fp with success but I face an issue: some apps don't get updated on playstore... It shows that they can be "also installed" on my already installed device...

Rings any bell to anyone?
[Magisk] majorfigjam:
Not specifically with Playstore, but I can't validate my phone for RCS chat (may be a carrier issue) , and in My Devices, Google thinks it's a Pixel XL not a Pixel 6 Pro.
[Magisk] xcl1pse:
Update again, your 3 version older. I assume latest kitsune release is R65894F03-kitsune
[Magisk] sawdoctor:
Osmosis fork won't work on android 14 beta because it's using shadow hook but seeing as osmosis has the pixel 8pro himself running android 14 stock I'm certain it works on stock.

I'm still using PIF 14 with a custom fingerprint on the pixel fold with qpr2 beta
[Magisk] awarexda:
So in essence, in order to update I must remove pif.json temporarily?
[Magisk] sawdoctor:
I have a similar issue where my phone thinks it's a realme x2 pro (but rcs works). Nothing i do changes it unfortunately. Speaking with osmosis he said it will be a leftover from using one of chiteromans safety net fix mods that used the x2 pro fingerprint and the only way to fix it is to wipe play services data which is a pia
[Magisk] majorfigjam:
Sorry, I don't know. It's probably worth a go, if you desperately need to update an app. It's easy enough to reinstall the json, clear caches, and restore "Device Integrity".

That would also test if you have some other issue that maybe stopping you update.
[Magisk] dimak2103:
Lol, it works))) Thanks) But I doesn't find anything about resetprop fixed in Magisk Delta changelog. Maybe you know exactly what the fix is called?
[Magisk] RichyRicho:
Same here. My Xiaomi mi note 10 pro identifies as a pixel 2 😂
[Magisk] RichyRicho:
How does one wipe play services data? Is that on the server side or the phone?
[Magisk] majorfigjam:
Phone, /settings / apps / google play services, then force stop and wipe cache. No need to wipe all data, as it may delete wallet data too
[Magisk] sawdoctor:
Just bear in mind you'll have to set up all your Google accounts watches and anything else
[Magisk] xcl1pse:
.View attachment 6048542
[Magisk] jrotaetxe:
Hello all.

@osm0sis and @chiteroman , a question:

Is there a reason why a custom pif extracted from the same build.prop can pass with PIF(14.5) 2/3 and fails miserably with PlayIntegrity fork (V4)(0/3)?

Mi10T A12 stock fw.

And a big thank you for your effort (toghether with other making tools and scripts and trying to help).
[Magisk] shoey63:
Rename pif.json to custom.pif.json and move it from /data/adb to /data/adb/modules/playintegrityfix

Force stop Google play services, or reboot and check again.
[Magisk] sethieplayz:
Hello all,

I was wondering if the average banking app which includes NFC payments within it would work without PIF? I would test myself but I've broken my phone, and am waiting for my new Pixel 6 Pro to arrive. I'm tossing up whether I should continue rooting, as there are many features I will miss without.

Finding a PIF is not my issue, but in terms of longevity I would prefer to not have to worry. I'm talking about the Australian Commbank app specifically.

Thanks in advanced
[Magisk] jrotaetxe:
Hi, Shoey

Sure I positiioned the (slightly different) files in their proper locations and with proper names. custom.pif.json in /data/adb/modules/playintegrityfix in the case of osm0sis' module and as pif.json in /data/adb in case of chiteroman's module.

The source info for both is the same build.prop

Thank you very much for your kindness, but neither the name nor the localisation explains the different behavior.

Regards
[Magisk] ruiisaactan:
hey i just got another pif from my old android device, i tested before on the old device if the device passed both basic and device integrity and it did. but after installing the custom pif onto my pixel 5 android 14 with magisk 26.4.

the device i got the pif from is the s7 edge on 8.0.0. anyone got any tips on getting the fingerprint to work?
[Magisk] majorfigjam:
Almost certainly it will be in the file syntax, if the details are valid. You say they are slightly different files, presumably not just in the name. Make sure your spaces, commas and nulls are correct for Osm0sis.
[Magisk] jrotaetxe:
The

The custom.pif.json has been automatically generated using osm0sis' script, so syntax shoud not be the issue, but will check twice later
[Magisk] CZ.Kostra:
Try to compare the logs from PIFix and PIFork. Termux: logcat | grep 'PIF'

(do not publish logs)
[Magisk] BunnyPig1:
It depends on your bank.

My banking app works without PIF, doesn't even need basic integrity. The only thing I need to do is to make sure the banking app is in the deny list within Magisk.

But then there are banks that are almost impossible to hide root from. So it varies a lot between different apps.
[Magisk] Vision:
The old device still can pass, but the Fingerprint can be block it by Google (the block FP not affects the real device) and from old device need the build.prop and with this info write in the pif.json between quotation marks
[Magisk] chiteroman:
Amazing new root solution, in my opinion better than Magisk.

GitHub - bmax121/KernelPatch: Patching and hooking the Linux kernel with only a stripped Linux kernel image.

Patching and hooking the Linux kernel with only a stripped Linux kernel image. - bmax121/KernelPatch

github.com

GitHub - bmax121/APatch: The patching of Android kernel and Android system

The patching of Android kernel and Android system. Contribute to bmax121/APatch development by creating an account on GitHub.

github.com

Also, DroidGuard doesn't detect patched boot.img if you are using this 😯

View attachment 6048616

No Zygisk available :(
[Magisk] dmenezes:
So, similar to KernelSU? Or am I missing something?
[Magisk] eugenwollekneul:
What do u think compared to kernelSU
[Magisk] xcl1pse:
If the module implementation is like overlayfs, then theres no difference between this and kernelsu. Usefull for device that dont have kernel sauce
[Magisk] sawdoctor:
Might get zygisk once Apatch is officially released, can't see the Linux version needing it
[Magisk] Vision:
A big difference from KernelSu as i can see, is this support old kernel ? and KernelSu support but need patch manually and very knowledge
[Magisk] eugenwollekneul:
What I understood is, that you don't need to wait now till the manufacturer releases the sourcecode of the kernel and devs don't need to implement SU to the kernel.

That's a big thing.
[Magisk] Kopasz999:
Hi 😎

After last update (14.9) not working.

I can't pay with my phone.

Have somebody the same problem???
[Magisk] badabing2003:
I'd be curious if you reprocess the JSON in PixelFlasher with the latest osmosis fork and test, does it work?

It's your S7 rooted?
[Magisk] sawdoctor:
Unfortunately the Apatch is Only for arm64 reading it so probably won't support arm7a devices
[Magisk] manan001:
Tried on Oneplus 11 5g Android 14 but still no luck.
[Magisk] sawdoctor:
Zygisk next is 95% working, just reading it they have a working Daemon.

Thanks for the link, really interesting project and could well be the future
[Magisk] ruiisaactan:
was not rooted when i tested integrity, then i disconnected from internet and rooted it so i can extract the build.prop file. i was going to try extracting another build.prop but i accidentally tripped kg state prenormal on my galaxy note 8 and now its bricked, and i cant find the older version of the software because sammobile archived it.
[Magisk] Vision:
Yeah i read that, is a negative, i have arm64, bad for anyone have arm7a unfortunately
[Magisk] ruiisaactan:
i tried using total commander but it doesn't like it but ill try again thanks
[Magisk] jrotaetxe:
Will do
[Magisk] badabing2003:
I thought your old device got bricked.

If not, just connect it to PixelFlasher and go to device menu.

There are two options.

Get just pif.json or the entire props in JSON format.
[Magisk] osm0sis:
Should work unless it's relying on an empty field that 14.5 was filling in for you or something. Feel free to PM me and I'll see if I can figure out what's missing in your json.
[Magisk] ruiisaactan:
ah no my samsung s7 is alright, my note 8 is bricked so im going to reinstall the stock firmware, wanted to get custom pif for my pixel 5 so i dont need pixel flasher.
[Magisk] poulopoulosa:
I have been reading this thread (however I must have missed some replies). I have been trying many different fingerprints and so far I can't seem to get 2/3 of the device certification.

I know SafetyNet will soon go kaput but in there the CTS profile match is failed.

I was using Chiteroman's PIF then I dirty installed the osm0sis fork 💀. As I said I have been trying so many different FP but all of them are stuck at 1/3 could it be something really bad on my setup?

I am using:

Magisk​

Magisk Modules​

LPosed modules:​

- Magisk Canary

- Zygisk

- Enforce DenyList

- busybox

- Play integrity fork (v4).

- Systemless hosts

- Zygisk - LSPosed

- Hide my apps

- UpdateLocker (Because Google has been secretly updating my Vanced app to the newest version)

What am I doing wrong? Has anyone found a working FP via Pixel flasher's "TheFreeman193" random PIF?
[Magisk] akaloith:
help

I pass safetynet test with play integrity fix 14.9

but fail google pay

what can i do????
[Magisk] sawdoctor:
What device and android firmware are you using
[Magisk] badabing2003:
If you're willing to take this challenge,

🎣 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

I can work with you via DM to get you operational.
[Magisk] pulpf:
Hi, I had several payments declined today. I just installed version 14.9 of play integrity.

But here is the result of integrity checker.

Is this normal?

View attachment 6048706
[Magisk] V0latyle:
Please post in English or provide a translation.

You have to use a custom print with the latest release, as it does not include one. The resources needed to find a print are in the OP.

Also:

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

[MODULE] [DATA] Custom PIF.JSON files collection for Play Integrity Fix

A collection of pif.json profiles for the Play Integrity Fix module by @chiteroman or the fork by @osm0sis. TheFreeman193/PIFS on GitHub Detailed instructions are on the repository homepage but you can either copy a file manually or run the...

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
[Magisk] V0latyle:
Clear Google Play Services data

Clear Google Pay/Wallet cache

Clear Play Store cache

Reboot
[Magisk] 01046:
If i Clear Google Play Services data , my watch will disconnect

how to avoid it
[Magisk] badabing2003:
That is such a PITA, I don't understand the design decisions.

Not only the watch will disconnect, you'd have to set it up fresh.
[Magisk] 01046:
Ya, It seems there is no way to escape this

such a strange design, wearos(android wear) has been bothering me since its inception
[Magisk] Kopasz999:
I have thé same problem.
[Magisk] Kopasz999:
After last update not working.
[Magisk] akaloith:
done that

opened google wallet

try to add my card and still does not let me!!
[Magisk] V0latyle:
Did you try the same solution?

Have you checked your Play Integrity verdicts?

Does Wallet say your phone meets security requirements?
[Magisk] poulopoulosa:
Pixel 7pro - Lineage OS 20 (Android 13)
[Magisk] blue whale:
can somebody check if PostIdent works

POSTIDENT - Apps on Google Play

POSTIDENT for the convenient, simple and secure verification of your identity.

play.google.com

and WebID

My WebID - Apps on Google Play

Identify and sign quickly and easily online

play.google.com

I have a smasung s5 900f , can somebody confirm magisk and Play Integrity Fix work on it ?
[Magisk] V0latyle:
You can follow the guides I linked above to find and confirm your own custom print
[Magisk] BrimoFan123:
On Telegram I had a funny discussion with one guy who claims he have kernel su, no modules in Magisk installed and he is able to pay using Google Pay.

View attachment 6048728

:) :)
[Magisk] HippoMan:
Just out of curiosity, since I'm considering the possible purchase of a smartwatch ...

Is there any other brand of smartwatch which can be used for Google tap-and-pay, and which will not require a full reset when clearing play-services data? Or is this just a "feature" (ha ha!) of all Google-pay-enabled smartwatches?

Feel free to reply via PM if this is deemed to be OT.
[Magisk] simplepinoi177:
I don't know if this has been answered or addressed already, but there's been 4 new pages since 12 AM last night and I haven't gone through all of them yet, but....

@ruiisaactan , passing basic and device integrity on your original device (the source of another build.prop [what you seem to refer to as "pif]) is not a requirement. If it isn't rooted and/or has a locked bootloader, it is very likely to pass basic, device, and strong more than your rooted pixel 5.
[Magisk] V0latyle:
Actually, if a device's profile doesn't pass in native configuration (stock firmware, locked bootloader), the print is not likely to be usable for PIF. This is important because there are some devices out there whose OEM keys were revoked by Google, so the prints are all but worthless.

If it does pass on the original device but you're having trouble using the print on your new one, make sure you're spoofing the FIRST_API_LEVEL as well. If the original API level doesn't work, try using different ones from API 21 through 27.