yashsingh1/xdaforums huggingface dataset:
[Magisk] xcl1pse:
Didgeridoohan MHPC using resetprop utility to spoof your props value into your desire value. This technique prevent some newer phone which is using hadware backed attestation to force using basic attestation and safetynet can be bypass. But theres one caviat. Since your props value spoof into another phone is globally, some app prevent to work (like if I'm using samsung device and spoof into pixel devices, my galaxy store, galaxy themes and app from samsung, I can't use that anymore until I reset MHPC config).

To prevent that, kdrag0n tinkering and he found solution that only spoof play store to using other props bypass hadware attestation. He need to code to inject some props into play store process and Universal Safetynet Fix (USNF) born. From initial release, he using riru to inject props into play store but since riru deprecated and replace with zygisk, the newer one using zygisk to inject.

Displax notice on kdrag0n module that some time if the phone is standby, the module doesn't spoof that props and failed basic test. If the phone trigger attestation test like reopen and test safetynet again, the module will spoof that props again and pass basic test. So Displax forked that safetynet and doing some investigation and safetynet (USNF) mod by displax born. On safetynet mod v1.3, the spoof principle is same, spoof all play store process into another props. But this raising some issue like samsung devices using wifi calling.

So chiteroman fix this by only spoofing droidguard (com.google.android.gms.unstable) into another props also bypass safetynet (will replace into Play Integrity) and Play Integrity Fix by chiteroman release. Also notice that chiteroman love experimenting with this kind so this module can update in twice a week. When kdrag0n and displax no longer maintained safetynet fix, only chiteroman that give you fix for play integrity.

The HuskyDG one block droidguard detection to use key attestation using SELinux (no need riru or zygisk to work) + hiding sensitive props from Custom ROM user (mostly from Lineage) since he want to prevent using any of like zygisk module because only Alpha used native bridge zygisk injection based and you need shamiko to work perfectly and he dont like closed source module + LD_PRELOAD on OG magisk is terrible. Because of that, he fork magisk and name it magisk delta and replace zygisk API to use PoC native bridge injection by 5ec1cff on magisk 25.2. If you using magisk delta sometime you will notice theres 5ec1cff on the credit page since he using that and he dont want any complain from user about zygisk and combined them using shamiko. And his module also fail on some devices so he dropped that module. Well apparently theres sensitive props v4 but I can't find that, maybe in their telegram group, so I count that he dropped the module

Since Didgeridoohan, kdrag0n, Displax and HuskyDG are no longer maintained, you only use PIF from chiteroman. Because hes (chiteroman) madman (pun intended), theres one module by osm0sis forked btw, but you need your custom spoof. Information of that you can search in this thread.
[Magisk] uschipower:
ok, thanks

so i uninstalled universal safetynetfix, reboot, installed chiteroman's Fix Play Integrity (and SafetyNet) v14.2, reboot

as I read, this fix is a 1-click-solution: install, reboot, ready

Now, i used these Tester:

SafetyNet Device Check – Apps bei Google Play

Geräteprüfung gegen Googles SafetyNet Attestation API

play.google.com

Play Integrity API Checker - Apps on Google Play

Get info about your Device Integrity through the Play Intergrity API

play.google.com

SafetyNet | Integrity Checker – Apps bei Google Play

SafetyNet | Integrität ist eine Möglichkeit, den Zustand und die Umgebung von Gerät und App zu überprüfen.

play.google.com

YASNAC - SafetyNet Checker – Apps bei Google Play

Noch ein SafetyNet-Bescheinigungsprüfer

play.google.com

the first 3, still says that device do not pass.

the 4rd one always crashed on all devices.

what do i have to to?
[Magisk] woody4165:
Hi all and thanks to @chiteroman for his great work

I've just installed this module on Magisk 26.4 (the only module I have activated) on a Redmi Note 10 Pro with PixelOS Android 13

The app Play integrity API checker have green check on MEET_DEVICE_INTEGRITY and MEET_BASIC_INTEGRITY, but red check on MEET_STRONG_INTEGRITY

If I go on Play Store information panel I get that the device is not certified

And Google Wallet give me warning message

What can I check?

Thanks
[Magisk] xcl1pse:
Only Play Integrity API Checker is right. You can also using TB Checker, SPIC or Play integrity test on developer option play store. If your module fail check the log. Also what's your setup?
[Magisk] titomax82:
Because after spending 2 days trying to make my custom pif.json with failure, I'm searching for another solution
[Magisk] xcl1pse:
Is not that hard honestly with osm0sis giude and badabing tool. You can also using PIF 14.2 until the fp banned and chiteroman will release a new module ☠️
[Magisk] titomax82:
As said, I tried a lot and failed the same.... Shame on me
[Magisk] xSnowLeopardx:
Have 19 FPs right now. It's really easy, indeed. All the info is in this thread, especially OP.
[Magisk] borygo77:
I have

Make it public so we can test! 😊 TiA!
[Magisk] majorfigjam:
Or you could use the one I pm'd to you just now, which should give you a hint as to what to search for, to develop variations of your own in future.
[Magisk] wyt18:
Am on Samsung S20 stock rooted, installed PIF 14.0 and since then keep getting a recurring message of CPU overload and a need for a system reset. Anyone else seeing this as well?

Didn't happen when I was on the old kdragon solutions ...
[Magisk] beeshyams:
I

I am not very savvy but you need to spoof

A good starting place to read about it is @osmosis fork readme, come back here and read highly liked posts.. You will have to go back at least 30 odd pages
[Magisk] zgfg:
Without going to details, Google frequently updates on their side

By a rule of thumb, anything older than few weeks will not be enough (it will pass only Basic but not Device and so)

Also, you must not mix several of them, one will mess to another

Therefore, stick to the newest/recently released. And see yourself where the crowd is (here), or has moved from the other out-dated threads and methods. Read also the last/latest farewell posts there by users who complained that it didn't work anymore and we're advised to move here
[Magisk] GabbyWC:
As we await chiteroman's answers to these questions, the XDA post of his at https://xdaforums.com/t/spoof-locked-bootloader-bypass-tee-check.4586251/post-88563847 contains a statement that could answer your last question. "STRONG requires a locked bootloader o spoof certificates which is difficult." I think that he meant to say "or" before the word spoof and that the spoofed certificate is what his module provides based on the description.
[Magisk] Fishawy:
Generally, rooted means no STRONG integrity, but he did it before (by exploiting some Google loophole), hence the question.

I guess we'll wait for him to come back on those queries.
[Magisk] xcl1pse:
Difficult means here is to get trusty cert. Since his get one, is not really difficult anymore, just some phone with TEE broken, maybe this upcoming module will not work on that devices. But will see
[Magisk] xSnowLeopardx:
+ today will be 7 days for the main FP I am using to still work.
[Magisk] badabing2003:
PixelFlasher update Release:

Dec 09, 2023 v6.3.2.1 release

Add VNDK_VERSION to pif print

Bug fix: add the missing comma in the generated pif.json.
[Magisk] Oswald Boelcke:
Sir, I'm happy with whatever the decision is and am ready to move @Lord Sithek's thread into the Magisk forum. My suggestion is to leave the decision to Lord Sithek. Lord, please let me know what you prefer. Thanks for your cooperation.

Regards

Oswald Boelcke
[Magisk] xSnowLeopardx:
20th FP after 5-10 minutes of trying (not searching) from one of the sources I have.

It's, again, that easy.
[Magisk] lallolu:
5th attempt, still haven't got a working fingerprint :unsure:
[Magisk] Lord Sithek:
Oh well... Difficult decision 😅 Taking into account that it's a Tasker tool, I think the thread can stay on Tasker forum. However, it would be nice to have somewhere a list of tools available for "mining" prints, including @osm0sis script and @badabing2003 Pixel Flasher. Is there something like pinned post on a thread?
[Magisk] xSnowLeopardx:
Describe the method + tools you're using. To see what bottlenecks you.
[Magisk] zgfg:
Bootloader Spoofer will not help for Play Integrity, definitely not to spoof Strong Integrity

Besides to hide that BL is unlocked for Key Attestation app, there is not much use of. Unless you find some banking app where it may help you with (but sophisticated banking apps use various detection methods and they will still find the other ways to recognize that your phone was modded)
[Magisk] badabing2003:
I think it is up to @chiteroman to add a section in OP. That is always OP's choice.

IMHO, it's good to mention relevant tools in this thread that people can use to ease their way, however I strongly think that questions about the usage of the tools or bugs related to the tools should be kept in their own threads to keep the main thread's discussions noise free.
[Magisk] Lord Sithek:
Yes, I agree fully. So @chiteroman please consider adding a list of relevant tools for fingerprints testing in the OP
[Magisk] uschipower:
Because google deprecated safetynet, does this also mean that no app can use this method to check - does every app in google play need to use "PlayIntegrity"?

what is the correct way to reset?

Because all of my devices are older and are not maintained by manufacturer any more, I have to use custom rom or treble image.

My devices:

Samsung SM-T550: LOS 18 custom rom from retiredtab

Lenovo TB-X505F: LOS 20 Treble GSI from AndyYan with GAPPS

Lenovo TB-X605L: LOS 20 Treble GSI from AndyYan with GAPPS

on all devices: Magisk Delta 26.4

you think of this?
[Magisk] Oswald Boelcke:
If you like we can leave the thread in "Tasker" but I can create a permanent redirect in "Magisk"?
[Magisk] Spartacus500:
14.2
[Magisk] beeshyams:
Last Point - yes
[Magisk] xcl1pse:
Theres reset menu after enter props on terminal, I forget whats name since I no longer use that anymore... also if using pif is failed, you can check the log: su -c logcat | grep PIF. And why not updating magisk delta to latest?
[Magisk] zgfg:
Please take some time to search/read, you will find answers for your current and future questions

Some apps do not check anything, therefore not Play Integrity. Sophisticated banking and similar apps use various detection methods, NOT ONLY Play Integrity, hence by spoofing PI they may still force-close, popup warning/error or whatever they prefer

New apps cannot be published to Playstore if they implement deprecated SN instead of PI. By the end of next year Google will remove the old SN API/support from Play Services

But who cares about SN - if you pass PI Basic and Device, you will definitely also pass the old SN with CTS Basic (not Hardware)

Google's own Wallet (GPay in US and Singapore) fully relies on Play Integrity, and they don't do other detections like banking apps do

Simply test do you pass Basic and Device Integrity and if not, install, test again, learn about, search for your own spoofs, etc

Or if you don't use Wallet/GPay and you don't have problems with other apps that detect your modded phone, then why to bother with PI
[Magisk] Lord Sithek:
Sure, would be nice. Thank you! 😊
[Magisk] Oswald Boelcke:
Accomplished.
[Magisk] devilsshadow:
still rocking the 1st key I found on my 1st try based on roughly interpreting @osm0sis original helper post. I have not bothered to "mine" more keys as the chance of them becoming broken by the time I need them becomes higher with each passing day that I'm still on my 1st key. For people hoarding keys, I understand the dopamine hit, I get that it gives you a feeling of superiority, knowing that you're better than the poors that cant find a key. I'd urge you to keep those feelings in check. If you're good enough to find a working key quick, stick to that, dont hoard. If you must hoard, consider sharing your keys privately with others, at your own discretion. Hoarding for hoarding's sake isn't healthy behavior.

As someone else said in this thread, it's probably healthier to just look into getting a pay-enabled smart watch. And if the PIF cat&mouse game comes to an end in google's favor (it will), it'd rather keep my root (that I like having for other stuff) and have a device (the watch) that bypasses the ratrace and just works. Besides, a watch is helpful for other stuff as well, it helps you look at your device less! Had a 1st gen android smart watch and it was slow as heck, but i loved it and used it until the battery died. I even rooted/custom rom'd the watch at some point for the memes, once I no longer needed it for payments.
[Magisk] HippoMan:
That is a false assumption about the motives of most, if not all of those people. I'm sure that someone who has one or more extra fingerprints would be willing to privately share with you, if you don't approach them with such a condescending false accusation when you ask.
[Magisk] BrimoFan123:
My success ratio is almost 10%

Checked 38 build.prop files and this number gave me 4 working fingerprints.

With mentioned by others tools like PixelFlasher procedure is quite fast.

Keep mining... eventually you will succeed.
[Magisk] HippoMan:
I agree with that approach. This fingerprint-based solution is intrinsically doomed.

As for me, I'm looking for more of a cheap, "dumb" smart-watch with NFC capabilities, which I will mostly use for finding out what time it is. I would only rarely use it for contactless payments.

Some of the cheapest, simplest versions I've seen are set up to use Samsung Pay, but I don't know how prevalent that payment service is in the U.S. Unless I find out that it's as widespread as Google Pay and Apple Pay, I'll probably just get a slightly more expensive watch which handles one or both of those services.
[Magisk] lallolu:
I am using gen_pif_custom with build.prop and vendor build.prop, which has successfully generated custom.pif.json. I replaced the content of /data/adb/pif.json with the content of the generated custom.pif.json. But I am still not passing "play inegrity". I cleared data on google play services and wallet. Am I doing something wrong or I just need to continue searching?

I have tried mbiphone_s10, Ace_AS0618, mblu_10 and 2 others I don't recall.
[Magisk] xSnowLeopardx:
Ah, you're doing the fork's method? Fair fair. I have never seen those codenames while searching, though.

My tip: type "android dumps" and dig.

Something should work for ya. I have 20 right now, but finding the next one is very easy. Your method and source should be optimal. Continue the search.
[Magisk] bigd4ve:
Just to double-check, if you're using DEV v1 then that file path should be correct. If you're using the fork, the file path and file name are different.

You may want to try changing the FIRST_API_LEVEL for your chosen prints and/or removing the BUILD_ID and VNDK lines because some have reported success without those.
[Magisk] lallolu:
Thanks. I am using https://github.com/chiteroman/PlayIntegrityFix/releases/tag/DEV-v1, which I assume is not the fork. And I actually, just used the custom pif.json which was generated with custome_pif_gen script and the version I have does not populate BUILD_ID and VNDK. So, I didn't have those fields in /data/adb/pif.json. Maybe I should try including them.
[Magisk] evildog1:
The fingerprint must be from Oreo roms right?
[Magisk] wfred:
🤔 For me it names the correct phone, but shows an image of the device I'm spoofing
[Magisk] xSnowLeopardx:
It can be lower and higher as well. I don't know the exact min. and max. unfortunately.
[Magisk] evildog1:
Oh ok. I've tried 3 fingerprints from underrated phones I know, none worked so far. I'll keep trying
[Magisk] xSnowLeopardx:
Tip: some of mine aren't underrated at all. Although, I have one as well with a brand I have never, ever heard of.
[Magisk] wfred:
AFAIK Samsung Pay on a Galaxy watch requires Samsung Wallet on a Samsung phone.

You can use Google wallet on a Samsung watch, but I don't know if watch G wallet requires phone G wallet to pass PI
[Magisk] Wolfcity:
Maybe I'm a bit late to the party but opinion counts,doesn't it?

Stay with the. json format. There has been a lot of back and forth so why change it again?

I'm able to use the script by @osm0sis to find working prints and the people using Pixelflasher seem to have no problem with the json format also.

So stay with it.
[Magisk] bigd4ve:
I guess you could try adding them because maybe they are useful for the version of the module you are on.

Personally, I would continue with your current method but try more prints as it sounds like you are doing things right and just haven't found a working one yet.

For me, I found one after about 6 tries. If it's taking you a lot of tries with no success, review everything to make sure your setup is right and maybe change the way you are choosing devices/prints. It's pretty random after all.

As a sanity check, you could also grab the known working print from v14.2 and use that to double-check things are working for your environment. Good luck with the search!
[Magisk] bigd4ve:
Same here, well spotted! I didn't notice the image of the device when I checked earlier.
[Magisk] HippoMan:
Thank you.

So, unless/until I get more info, I'll just investigate non-Samsung watches.
[Magisk] flawless911:
It's been exactly 7 days since I made this post.. I'm still using the props I found that day, I haven't "mined" for more props, still using v14 of @chiteroman module and will continue to do so as long as it still works.. When it comes to mods and bypasses, I strongly believe in "if it ain't broke, don't update it" (sometimes I refuse to update Magisk for months because of this, unless absolutely necessary)

Also this thread has been more entertaining than Netflix these past few days, and to think I started down this road because I couldn't find Netflix on my Playstore anymore 😂😂😂
[Magisk] HippoMan:
They should put a reality show on Netflix called something like "Magisk PIF".
[Magisk] sga999:
Is Netflix always being allowed on your device now? Using 14.2 or DEV-V1, I pass Basic and Device Integrity, and my device shows certified. But Netflix access is peculiar. It will show as installable at one time, and hours later, without any changes to PIF module, it is no longer installable. I know that sounds unlikely, but it has happened many times. Does anyone know what Play Store is checking when it decides "This app won't work for your device"?
[Magisk] niko26:
Speaking of Netflix - what's the reason why Netflix can't be updated or even installed anymore?

Mind... Gpay works currently, and the device (Pixel 7 Pro) passes the first two level of integrity in Playstore (basic and device integrity).
[Magisk] HippoMan:
Netflix is probably wayyyyyy overreacting to security issues like is done by many banks and some apps like Uber-rider. These apps do their own "security" checking on the device that goes beyond simple Googlefrinchian play integrity checking.
[Magisk] niko26:
OK, I get that the app doesn't want to start *like the Dreame Home app. But in this case the Playstore shows that Netflix can't be installed / updated. How does that work? How does the play store know about the restrictions for the apps?
[Magisk] samuelpoc:
Hello, I'm using a Lineageos 20 and when I installed the module without any custom prop it didn't work, so I put a pif.json (I took it directly from the stock rom with the help of the guide indicated in the post) and then I installed the module with the custom prop and it still did the same thing (it didn't pass safetynet or play integrity) can anyone help me?
[Magisk] HippoMan:
Oh, that I don't know.

It could be that app developers now can somehow flag their apps in such a way that the Play Store doesn't show them as being installable on a modded device.

But that's just a wild guess.

UPDATE: I just checked on my modded/rooted A13 device running with a PIF-installed spoof fingerprint, and I see Netflix offered in the Play Store.
[Magisk] HippoMan:
Hmm ... is it possible that a spoof using the fingerprint of an ancient or "rare" device that Netflix doesn't supprt might fool the PlayStore into thinking that the Netflix app is not installable on that device?
[Magisk] majorfigjam:
Please confirm exactly what you have done. What device? Which module (Osm0sis, 14.2, 14 etc)? Is your custom prop a recommended version like Oreo 8.0? Or are you trying to use the stock rom which may be too new? Did you clear Play Store and Play Services cache?

If you follow the guides, and have a working print, then it will work.
[Magisk] zgfg:
I have Netflix all the time installed and I use it, and I upgrade the Netflix in Playatore with no issues, like the other 'normal' apps
[Magisk] Nergal di Cuthah:
Same. just with pif 14.2, i can download netflix and updates (just updated netflix a few days ago on pif 14.2)
[Magisk] hassanhassan:
finally sat down and figured this out. spent the last two hours going through every build.prop I could find and i'm getting fails. I need a break

edit: can't even spell anymore....
[Magisk] wugga3:
Being able to open Netflix in the play store is one way I can verify that PIF is working.... So the saga continues!

Can't download/update without working PIF
[Magisk] samuelpoc:
the device is a moto g10 (capri) I used the dev-v1 version of chiteman (I think this is the one used to load custom props) the impression I used was the stock rom of the capri which comes from the factory with Android 11, I used the stock last
[Magisk] ReQuiereZ:
Hey guys , Im a new here... I'v got nothing phone 2

I wanted to root my phone , and I saw that I need to use play integrity fix to make google wallet work ... but when I continue to read I saw that I need to customize values in pif.json.

Its necessary ?

play integrity fix is not enough?
[Magisk] sga999:
I'm replying to my own post, because I don't know who saw it. There are other posts about Netflix, but no one agreed with mine. I'm wondering if anyone else has seen the same thing that I do where Netflix is available in the Play Store, but hours later, it is not. No changes have been made regarding the pif module or anything else in the meantime.

@HippoMan offered a possible idea above, but he did not say he had had the problem. I'm trying to learn if I am the only one!
[Magisk] De_Haos:
No i am back on stock L1 and huge difference between L3 and L1.
[Magisk] chiteroman:
In what way? This module only serves to obtain a certified device so that certain applications can be used. If you are referring to the Widevine L1 it will depend on the OEM implementation. For example, my device (POCO X3 Pro) with open bootloader still retains L1.