yashsingh1/xdaforums huggingface dataset:
[Magisk] GuyWithRootedPhone:
just a reminder, you cannot add new cards to GPay. I don't know what's going on but just letting you know.
[Magisk] Nergal di Cuthah:
Why not, it seemed to let me do so
[Magisk] GuyWithRootedPhone:
everytime I try to add one it says there's a problem adding my card.
[Magisk] mihalis1983:
I tried disabling all magisk modules, lsposed, adaway, cleaned store and services data, still not passing...
[Magisk] texasaggie1:
Worked for me. OnePlus 11 pro running Lineage OS
[Magisk] ipdev:
¯\_(ツ)_/¯

Just did a little test on mine.

It was clean flashed (stock MiUi) not to long ago when I was testing Magisk builds.

I did not worry about Certification or PlayIntegrity at the time, so I had to wipe cache and date from PlayStore to get it to pass.

View attachment 6017093

View attachment 6017085 View attachment 6017087

View attachment 6017089 View attachment 6017091

Stock MiUi seems to pass with just the PIFix v8.8 module on Poco F1.

Did you try clearing cache and data of the PlayStore app?

Cheers. :cowboy:
[Magisk] pershoot:
I'm trying 8.8 and will report back. To sanitize, I removed and disabled safetynet-fix, rebooted, then installed PIF8.8 and rebooted. Checked Integrity, YASNAC and Wallet's Tap to Pay setup; all seems ok, thus far.
[Magisk] chiteroman:
Updated OP and release a new version! v8.8

I recommend using this version because it has a lot of improvements in native code, specifically in Zygisk part, now if your device doesn't need to spoof first_api_level the native library will be detached from unstable process (less memory usage).

If it doesn't work you can provide logs using this command: adb shell "logcat | grep 'SNFix'"
[Magisk] chiteroman:
If you fail BASIC verdict something is wrong in your setup, DroidGuard is detecting injection or root.
[Magisk] WhoIsJohnGalt1979:
8.8 works fine for me.
[Magisk] spida_singh:
Works all OK here (DEVICE and BASIC pass)

LineageOS 20

Pixel 6

Magisk Alpha
[Magisk] pndwal:
This member has unevaluated results which always leads to no deviceRecognitionVerdict at all in deviceIntegrity response... Not really a BASICINTEGRITY failure or Droidguard detection... Indicates something different is wrong with setup... PW
[Magisk] zgfg:
Official v8.8 does not work for me on Xiaomi.eu 12.5

However, v8 7 does work

The same was also confirmed by @eXtremeDevil:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-89082963

Log says that hook is disabled and 'not needed for my ROM':

10-04 20:53:21.103 9861 9861 D SNFix/Zygisk: first_api_level: 28
10-04 20:53:21.141 9861 9861 D SNFix/Zygisk: Your device has first_api_level property and its value is lower than 33, hook disabled
...
10-04 20:53:21.147 9861 9861 I SNFix/Java: xiaomi.eu custom ROM already spoof props, you don't need this module with this ROM (if it's updated)

However, I do need PIFix (v8 7) because without I cannot pass

And I cannot update the ROM since MIUI 12.x is end-of-line (I have the latest Xiaomi.eu Stable from Dec 2021 and otherwise the ROM still works fine - however, that's not my daily driver)
[Magisk] chiteroman:
As they do everything so strangely and everything is so private it is impossible to make a universal solution for these ROMs, also this module is intended for stock ROMs (original made by OEMs, or pure AOSP as LineageOS). The best thing is that if you use a custom ROM that the devs are responsible for making the corresponding "hacks" to pass PI/SN.

Or use other different module versions, what a headache...

On top of that the logs show that your device came by default with Android 9 (api level 28) but still Google asks for a hardware attestation...

If they did things as standard and implemented the hooks in the framework.jar you could modify it yourself and problem solved.

I honestly already pass xiaomi.eu, their ROMs are very strange and do nothing but give problems xD.

(You can't see my annoyance 😂)
[Magisk] ljani:
Many thanks for the module!

I'm using it on klte with microG, and v8.7 works fine and makes basic integrity and CTS pass. Klte ships with API level 19.

However, v8.8 hangs with SafetyNet calls. Eg. YASNAC just keep spinning. Looking at microG's attestation logs, it shows the response as null. Looking at changes, maybe the hook should be always ran?

Here's everything I get from logcat for SNFix with v8.8:

10-04 23:11:25.965 3004 3004 D SNFix/Zygisk: first_api_level: 19
[Magisk] zgfg:
Did you look into the v8.7 log - IMO, it would tell you that hook is disabled and that you don't need the module (since your first API level is so old)

So check that and test then without either v8.7 and v8 8 - if you pass CTS Basic in YASNAC, that's it and you would not need to use the module

Btw, YASNAC and SafetyNet are deprecated. Better test with Play Integrity API Checker where you need to pass Device and Basic Integrity (not Strong) - but that should be practically the same as passing CTS Basic attestation type in SafetyNet
[Magisk] Muzine:
Earlier today I saw some people asking questions about the new 8.9 version and those comments are gone.

Version 9.0 is up on GitHub releases and all the previous versions have been removed!

What is happening?!
[Magisk] direwolf1:
I've got similar questions. The release notes for the module indicate that version 9.0 is now an addon for the safetynet-fix module, and that you should install both, but it's not totally clear. The release notes and GitHub page both refer you to the OP for this thread, but it doesn't seem to have been updated yet. I couldn't find anything in the thread for the safetynet-fix thread, either. I'm waiting to update until new instructions from @chiteroman are posted.
[Magisk] zgfg:
Not sure what are you asking but:

- v9.0 is released today

- developer has a habit to delete previous versions but that is of course his right (he wants to avoid supporting the old versions)

- XDA made a backup/snapshot yesterday evening and moved that to the new platform, moving was finished today afternoon (rel to CET time)

- there was a popup on XDA in the meantime, noting that Forum is moving and that all posts from the between will be lost
[Magisk] blinoff82:
Same question. What do you mean by two modules? Which module exactly should we use with version 9.0?

UPD: Got it. Main module by Displax + Plaintegrity fix v.9.0
[Magisk] ljani:
To be honest, that's what I thought, but I couldn't pass SafetyNet without Magisk, with Magisk, or with Magisk+Displax' module. What finally clicked was v8.7 of this module.

Here's a logcat from v8.7, it doesn't tell me much though:

10-05 22:08:20.106 1390 1390 D SNFix/Zygisk: Dex file size: 5540
10-05 22:08:20.106 1390 1390 D SNFix/Zygisk: getSystemClassLoader
10-05 22:08:20.106 1390 1390 D SNFix/Zygisk: InMemoryDexClassLoader
10-05 22:08:20.109 1390 1390 D SNFix/Zygisk: loadClass
10-05 22:08:20.110 1390 1390 D SNFix/Zygisk: init
10-05 22:08:20.117 1390 1390 I SNFix/Java: Spoof new device props
10-05 22:08:20.123 1390 1390 D SNFix/Zygisk: clean
10-05 22:08:20.123 1390 1390 D SNFix/Zygisk: Got __system_property_read_callback handle at 0xae3bd38d
10-05 22:08:20.344 1390 1390 I SNFix/Java: Spoof new device props
10-05 22:08:20.807 1390 1408 I SNFix/Java: Spoof new device props
10-05 22:08:21.136 1390 1408 I SNFix/Java: Spoof new device props
10-05 22:08:21.431 1390 1406 I SNFix/Java: Spoof new device props
10-05 22:08:21.636 1390 1406 I SNFix/Java: Spoof new device props
10-05 22:08:21.701 1390 1406 I SNFix/Java: Spoof new device props
10-05 22:08:21.813 1390 1406 I SNFix/Java: DroidGuard detected
10-05 22:08:22.112 1390 1406 I SNFix/Java: Spoof new device props
10-05 22:08:22.121 1390 1406 I SNFix/Java: Spoof new device props
10-05 22:08:22.123 1390 1406 I SNFix/Java: DroidGuard detected
10-05 22:08:23.264 1390 1432 I SNFix/Java: Spoof new device props
10-05 22:08:23.271 1390 1432 I SNFix/Java: Spoof new device props
10-05 22:08:23.297 1390 1432 I SNFix/Java: Spoof new device props
10-05 22:08:23.324 1390 1432 I SNFix/Java: DroidGuard detected
10-05 22:08:23.637 1390 1432 I SNFix/Java: Spoof new device props
10-05 22:08:23.643 1390 1432 I SNFix/Java: Spoof new device props
10-05 22:08:23.648 1390 1432 I SNFix/Java: DroidGuard detected

Thanks for the heads up for YASNAC though.
[Magisk] KAPABLE-K:
I upgraded my Pixel 7 to Android 14 last night and the Google play store showed device not certify with Displax module then I came across this one and after removing Displax and installing 8.8 it worked then it was updated to 9 but I was having issues with a google play system update that kept failing I was playing around with wiping the cache and data for the play system and play store then all of a sudden the google play store shows not certify again and nothing seems to fix it even with Displax + 9.9 anyone has any idea?

I'm using the canary build for Magisk
[Magisk] zgfg:
You need to capture the logcat during the time you're running Play Integrity (or the old SaferNet) testing

Besides, developer has released the latest (he says maybe the least - but don't worry yet😁) v9 0 - you may try. See also his post above about using v9.0

But if v8.7 works for you (while v8 8, v8.9 and v9.0 do not) keep it for yourself and enjoy using it
[Magisk] HippoMan:
That's why I put the word "banned" in quotes.

When discussing this subject, I decided a month or two ago to usually use a much more appropriate spelling of the word:

banana-ed
[Magisk] casouzaj:
I apologize beforehand. If it's not too much to ask, could you, guys and gals, who are posting the results of lengthy getprop commands, put them inside codes?
[Magisk] Umgak:
Just added a card with no issues.

In your tap to pay setup menu, does it show a check next to "your phone meets security requirements"?
[Magisk] makeyourself:
I added one a few hours ago without issue. If you're passing Device level PI and wallet app says you meet security requirements then it's probably nothing to do with PI. Just one card you can't add or multiple ones? I had it once where after I cleared Play Services Data without removing the cards first, it wouldn't let me readd one particular card until I had waited for a few days.
[Magisk] trevtdogg:
what exactly is the problem with just continuing to use the working acer FP instead?

that's all the goal is: find any random FP that passes device, then happy days, set and forget.
[Magisk] trevtdogg:
first step would be to find out for certain if the problem is with the print or something else in your setup.

try the current public working fingerprints first to check if your setup still works well enough to pass device.

PINext is using the current Xiaomi print and no one has complained that it stopped working yet. I think PIF 14.6 is back to working as well? someone can correct me if I'm wrong.

If those public prints work, and your custom print no longer works, then it's time to find a new custom print.
[Magisk] ace2nutzer:
A few weeks ago it was required to update the module every 2 - 3 days and to reboot the phone. It was annoying, but for now seems to be fine.

Other reason was for learning purpose. And of course for the hope that the stock FP for this device would work "longer".

Yeah ... still didn't managed .. but I'll keep testing props.
[Magisk] badabing2003:
If you're interested, check this

@HipKat is waiting to help :)
[Magisk] majorfigjam:
I'd send you a DM with a few helpful hints to using Osm0sis fork, but it seems I can't do that ...
[Magisk] ace2nutzer:
Yes I'll for sure if all my tests will FAIL... lol

Thank you. If I need it, I'll PM you, then you can reply to my PM. ;)
[Magisk] Umgak:
Wait - are you trying to spoof your device's fingerprint with your device's fingerprint? That's never going to work. The whole point of this module is to lie to Google about what your device is and what its capabilities are, so it doesn't think you're being shifty when you ask it to please use the old deprecated method of key attestation. If you ask it for basic (aka software-backed) attestation, and then tell it you're a new phone that they know should be capable of hardware-backed, you'll fail PI.
[Magisk] xcl1pse:
Goolag wake up after long holiday and choose violence. Now the included fp in latest PIF can rest in peace
[Magisk] blu.italia:
Back to basic with latest pif version 15.1 😕
[Magisk] majorfigjam:
Oh dear, how sad, never mind ..... time to get a custom print.

My early December one is still alive
[Magisk] Fishawy:
Back from annual leave 🤷🏻‍♂️

When people on this thread highlighted the risk and started encouraging the others to get their own prints, they were criticised (here) and trolled (Telegram).

Chilling with my private print from mid-November.
[Magisk] chiteroman:
Rip v14.6 and v15.1 fingerprint
[Magisk] sawdoctor:
In all fairness it lasted a hell of a lot longer than anyone expected. Guess the PIG is back from his vacation
[Magisk] TheRomRooster:
Get ready for the influx of people asking why Android Pay doesnt work anymore
[Magisk] supernovac:
do you found a new pif for yourself? it works?
[Magisk] HipKat:
I've got you covered if you need help. I can have set up pretty quickly. You can get me here in DM, TG or Discord if you want
[Magisk] MrSteelX:
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

That makes it so easy to find a working print. It only took me 10 minutes of my time and found 5 working prints.
[Magisk] ykjae:
I'm still passing device with 15.1 fingerprint. Oneplus 8t.
[Magisk] Vision:
Interesting, because the FP included inside, Google has blocked it

View attachment 6055799
[Magisk] V0latyle:
Were you using a custom print, or the included print?
[Magisk] xSnowLeopardx:
1 month and 13 days -> still on v14.4 with still a working FP.

The good life.
[Magisk] pranciskus2:
Pixel 7 stopped working today, my card was removed and can't add it 15.1
[Magisk] Umgak:
The shipped fingerprint with v15.1 is restricted. You will have to find another - the module will not be providing more. Many tutorials have been shared for how to find them in the past, like osm0sis' How to create and use a custom.pif.json which will help you find an eligible build.prop, osm0sis' gen_pif_custom.sh which will turn that build.prop into a pif json, and badabing2003's UI workflow for editing pif.json via PixelFlasher. Unfortunately nobody in this thread is likely to publicly post fingerprints, as it's likely to result in them quickly also becoming restricted. You will most likely have to find your own.
[Magisk] HipKat:
Correct Chiteroman is uploading 15.2, if not yet, soon
[Magisk] sawdoctor:
I'm still on v14 and custom fingerprint from 2nd December, no need to update if it still works
[Magisk] V0latyle:
#IfItAintBrokeDontFixIt
[Magisk] xSnowLeopardx:
#ifitaintfixedbreakit

That's, at least, how I approached rooting 10 years ago :cool:
[Magisk] V0latyle:
>have working phone

>root it

>noproblem.jpg

>get everything working with root

>life'sgood.jpg

>let's just try this new alpha build mod...

>everything's broken

>can't seem to get it fixed again

>have to factory reset and start over

>sad.jpg
[Magisk] xSnowLeopardx:
Man, I did not come on XDA today to see you write about my life :cry:
[Magisk] sawdoctor:
The saddest thing is that is 💯 correct for pretty much all of us.

My philosophy is the best way to learn is by breaking something then trying to fix it
[Magisk] badabing2003:
Works well on a test phone, but definitely not on a daily driver.
[Magisk] Nergal di Cuthah:
You're not really a beta tester unless it's on your daily driver :cool:
[Magisk] Rakib191223:
How is it rooted device
[Magisk] Rakib191223:
How??
[Magisk] V0latyle:
This was a short lived exploit with Google side print bugs that have since been patched. Not possible to pass Strong with ANY other configuration than locked bootloader on OEM firmware.

It's a joke.

Please, do some reading, especially my FAQ here:

[INFO] Play Integrity API - replacement for SafetyNet

THIS IS NOT A SUPPORT THREAD. For questions and support regarding how to fix your Play Integrity verdicts, see the Play Integrity Fix thread. ⚠️BEFORE YOU ASK A QUESTION, READ THIS POST AND THE FAQ!⚠️ ****Update 12/11/23**** Google has been...

xdaforums.com
[Magisk] Nergal di Cuthah:
It's a joke, notice all the extra tests (super dooper strong etc)
[Magisk] Rakib191223:
can i make play integrity module for myself, Is there was any tutorial about this topic?
[Magisk] V0latyle:
Why?

No offense, but it doesn't sound like you are at all familiar with this topic. There's no need to "make" a module for yourself. Use an existing module, whether it's the one linked in this thread, or @osm0sis Play Integrity Fork.

As far as finding a valid print to use, you can easily do this with PIFS.

And yes, there are multiple tutorials on how to do this.
[Magisk] Rakib191223:
I want to make one only for myself, by that i can use it longer then others.
[Magisk] V0latyle:
We haven't been "making" these prints.

Many have explained this multiple times before. The way this fix works is by spoofing props of existing devices. You can't "make your own" print because you have to spoof vaid props for CTS certified devices. You can find your own print, and there are multiple tutorials on how to do this, but it is easier to just use PIFS to pick one.
[Magisk] Rakib191223:
Where can i found authentic pifs which is good
[Magisk] Nergal di Cuthah:
Follow the tutorial you have to do the legwork of finding. Or use the freeman script to pull until you pass.
[Magisk] Fishawy:
The struggle is real. 🤦🏻‍♂️

Well, at least I moved away from daily flashing. That's progress, no? 🥴
[Magisk] V0latyle:
Yeah, same here.

I remember flashing nightly CyanogenMod builds on my Motorola A855...
[Magisk] Bitrey:
Please excuse me for my stupid question but I'm new to this, can I use a print of another device (Galaxy M32) since mine (Galaxy M31) is not listed or would it break things? Thanks
[Magisk] majorfigjam:
Please read the tutorials referenced above.

You need to find a working print, which is not from your existing device. The tutorials tell you what type of device print to look for.
[Magisk] Bitrey:
Yep, that would have been smart. Finally got Wallet working, thanks for urging me to use my neurons
[Magisk] Yusef Kifah:
I eventually did have to update PIF to 15.1 with one of my custom FPs. Don't think the older version (14.8) broke my integrity but Nearby Share stopped working, chrome didn't load pages, etc. Reboots / WiFi resets didn't work. Checking integrity with play store didn't work either..

Flashing latest PIF and slotting one of my saved FPs with Pixel Flasher did the job. Not sure why that happened but all is still good. Same FP for almost a month now.
[Magisk] V0latyle:
When you exercise the ones you have, you grow new ones too.
[Magisk] zhengsmall:
I am using chiteroman's pif + ksu. I tried nearly 100 times without luck on my S23U A13. I guess there must be sth not working properly. Once thing I noticed I always get same info on google play developer integrity checking even I used the script to pick different fp after I type n(no). Is that normal?
[Magisk] Umgak:
Yes. The integrity checker will show your real fingerprint, because the integrity checker itself isn't actually being given any false data. However, when DroidGuard (the module responsible for Play Integrity) attempts to read the same data, it is given faked values by PIF.
[Magisk] gj4560:
Hi everyone,

Today I tried to pay in store with Google Wallet but got the "phone doesn't meet security requirements" error, so I changed over to Play Integrity Fork (from PIF 15.1) and set a new fingerprint with PIFS, and verified that it is passing basic and device integrity using the Play store integrity checker. Later on when I tried to pay again I was still unable to pay with Google Wallet, getting the same error and now I'm not sure what to do next. Is Google Wallet now requiring strong integrity or something? When I check the pay contactless setup page, I still have the error showing there. All help is appreciated, thanks.
[Magisk] osm0sis:
Welcome to my fork, and congrats on finding a working print!

If you read the README...

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
[Magisk] theCroh:
When I update the contents of /data/adb/pif.json, should it reflect instantly to the results of the Play Integrity test? I.E. can I update the file with a fingerprint, test Play Integrity, update the file with a fingerprint, test Play Integrity... and so on until I find a working print?

Also, is there a recommended Play Integrity testing app or do they all do the same thing?
[Magisk] majorfigjam:
Probably best to stop and clear caches (not data) of Google Play Store and Play Services - in airplane mode for safety.

Test with Developer Options in Play Store - Settings- General - Developer Options (have to tap 5 times on Play Store version first to access this).

Or use the pixelflasher tool.
[Magisk] simplepinoi177:
Yeah....when I found my working FP, this happened to me...

you'll have to clear data on Play Services, Wallet, Gpay, Google Framework (for good measure), but unfortunately this'll mean you'll have to re-add the cards back into Wallet...but at least afterwards it'll be up and running...!
[Magisk] Umgak:
Run the following command in termux or ADB shell when changing the json file:

su -c killall com.google.android.gms.unstable

That will make sure that it updates immediately.
[Magisk] zhengsmall:
Seems that ksu + chiteroman's pif + PIFS(custom fp) never worked on my S23U A13 device, no idea of :unsure: what was wrong with my setup. I only got basic integrity passed, the device integrity always fails after google banned the default fp with v15.1. I also tried the play integrity Next module, but without luck. Finally, I got it working by switching to osm0sis's pif module (with PIFS to find working fp, good on the very 1st trial 😂).
[Magisk] gj4560:
Ah yes, I missed this part 😅 my bad but thank you! After following these steps, Wallet appears to be happy and it says my phone now meets security requirements. Will have to test it next time I need to pay for something. Thank you so much for all of your hard work, it is greatly appreciated 😃
[Magisk] simplepinoi177:
I kinda feel bad for daboynb.....there seems to be so much kanging happening with PINext on Telegram....I've come across like 3 or 4 clones of it (curl script, apk, module; the works!) They just packaging it together sometimes, or individually, but renaming it and publishing it in the channel and/or not calling it NEXT....

GitHub - daboynb/PlayIntegrityNEXT

Contribute to daboynb/PlayIntegrityNEXT development by creating an account on GitHub.

github.com
[Magisk] niko26:
Trying to use PIFS for the first time. After half an hour struggling with chmod and finding out that +x does not work on the sdcard partition, I am now not sure if I am doing things the right way.

Whenever a new fingerprint is being tried it, it fails, and the weird thing is... That Google Play Check shows the same information:

"

Labels: [MEETS_BASIC_INTEGRITY]

Build fingerprint: google/cheetah/cheetah:14/ UQ1A.240105.004/11206848:user/release-keys

Brand: google

Device: cheetah

Model: Pixel 7 Pro

Testid:xxx"

Shouldn't it show the information and brand of the fingerprint with the PIFS script is trying to add?
[Magisk] badabing2003:
no, spoofing is on for Droidguard
[Magisk] shoey63:
Like @badabing2003 says, not seeing the spoofed fingerprint is normal.

And yes, you need to a partition where you can change file permissions

I use /data/adb

Also,

Some devices, Pixel 7/8 for example, need the PIF directory changed to arm64-v8a,armeabi-v7a,armeabi by entering this code into the terminal as per the github readme.

export FORCEABI="arm64-v8a,armeabi-v7a,armeabi"
[Magisk] niko26:
I thought the process which does the checking for Google Play Store uses Droidguard?

The results which I have quoted come from the Google Play Store app/dialogue.
[Magisk] niko26:
Ah, yes, I am on a Pixel 7 Pro. Is this necessary for PIFS? Do I run this before invoking PIFS?