yashsingh1/xdaforums huggingface dataset:
[Magisk] simplepinoi177:
As mentioned previously, any member is free to make any kind of thread as long as it follows the Forum Rules (properly placed, no profanity, appropriate, that kind of thing).

Also, any OP of every one of the threads they create dictates what is off-topic and how off-topic material gets handled and/or is able to report any posts they wish to take action against. Apparently, days long past had Recognized Developers be able to do & moderate their own threads under certain circumstances.

But my own personal thought on it is that maintaining such a thread will be a very involved undertaking as it is such an active, ever-developing, and fast paced subject (at least for the time being), to keep on top of all the new and current things and info will be such an undertaking. So any member 😉 should consider that when considering creating such a thread.

But I'm for providing support and/or my guide in any such way; whatever is most being of most help!

Yeah...sorry mine isn't as nice as a proper FAQ...there's just so much information to get through, and in my attempt to make it not so Android-technical speak doesn't help it stay short either...😅
[Magisk] majorfigjam:
This is going to sound harsh, so sorry in advance.

I assume you understand the concept of rooting, else you wouldn't be here.

Do you also understand the concept of using a fingerprint from another device, in a json file that is read by a magisk module, to allow your rooted or non stock phone to achieve "device integrity"?

If yes, then read the guides, find a fingerprint that works, and use it.

If no, then either read the guides carefully until you do understand.

OR, simply revert your phone to stock, lock the bootloader, and you will no longer be troubled by lack of device integrity. You may even get something like this!View attachment 6048851
[Magisk] tom1807:
Wanna take bets how long it takes until a new topic is also cluttered with the same questions, answers, "how long the PIF already works", etc.?

Then there is not only one topic to monitor, but also the same questions will show up in both.

If a new Topic, then I would suggest one which is solely for the PlayIntegrityFork.

Or a FAQ which is locked, but as long it is not pinned, it would vanish on Page2, 3 and so on.

Just my two cents.

Cheers

Tom
[Magisk] miho171:
Find a working fingerprint, no PIF module has in it, try and check what level of integrity meets, you need device for gpay
[Magisk] majorfigjam:
Thanks for the update.

For those who are linux users, the shell script can be run without modification to update jsons on the pc, which may make it easier if you have more than a handful of them to update.
[Magisk] osm0sis:
The new migrate.sh script? I may have thought about that beforehand, yes! 🤓
[Magisk] HippoMan:
In this hypothetical new thread, we could all agree that whenever such a post shows up, we just copy and paste a standard, boilerplate response that we come up with ahead of time ... perhaps something like this:

In order to keep this thread uncluttered with a large quantity of redundant questions and irrelevant discussions, we ask you to please read everything that has been posted and linked in the OP. You will be very likely to find your answer there.

OP: https://xdaforums.com/path/to/the/OP/of/that/thread
[Magisk] HippoMan:
And PS: I highly doubt that Chiteroman would be willing to take the time to modify the OP of this current thread to contain as much info as we're talking about, and also more attention-getting admonishment to read that OP before posting. But if we create a new thread with one of us being the thread creator, we could actually get the OP written the way we want.
[Magisk] trevtdogg:
here's my attempt at a noob friendly initial intro / background reading for an OP or FAQ:

-------------------------------

all play integrity fix methods use a fingerprint from another android device for spoofing. this tricks google into thinking your device is an older device that can't do hardware attestation, and uses the spoofed data from the fingerprint to get device integrity passing.

older versions of some play integrity fix modules included a shared 'fingerprint' that all people used by default without knowing. google recently found ways of blocking the use of these mass shared fingerprints, and often very quickly. this is why constant new updates were coming out - it was just replacing the latest 'burned' mass shared fingerprint with a fresh one (that would also soon be burned in a few days).

to slow this cycle of burning fingerprints down, the community in general are moving towards no longer using mass shared fingerprints at all. if people all use their own fingerprints that they find themselves instead, then less people will be using the same fingerprint and it's hoped that google is far less likely to burn those fingerprints, or at least at a rate nowhere near as fast just yet.

so to keep using play integrity fix modules, it's time for all users to do a little homework and find a working custom fingerprint that you can use for yourself. it is best practice not to share this fingerprint with anyone else, and definitely not to share it publicly, as we don't completely know how google are identifying fingerprints to burn just yet. it could be based on raw numbers of users, how publicly shared it is, or a combination of both.

---------------------------
[Magisk] HippoMan:
I like this intro to an OP which then also lists the various resources that are available for managing fingerprints and for learning the details of how to do so.
[Magisk] simplepinoi177:
Honestly, I see where you're coming from. I tried to create a thread (with my guide) that would welcome those type of repetitive questions as a safe space/place for noobs and even requested the experts here to merely/simply direct them "noobs" and repetitive inquiries there (also to not clutter this thread with it, if possible) -- but it looks like everyone likes to congregate in this "main" thread where all the experts frequent more than an off-shoot thread that might be better/more-willing/less-strict & conforming/straight-to-topic....

so there is also that....
[Magisk] HippoMan:
We could agree to simply respond to such inquiries with something like ...

Please read the OP of the following thread, and after doing so, please post in that thread, instead:

https://xdaforums.com/t/how-to-sear...scussion-for-complete-noobs-from-one.4645816/
[Magisk] badabing2003:
You would use that special Magisk only if safe mode or other methods didn't work for you.

Your device is in a situation where if you boot to stock boot.img, it works, but if you boot rooted boot.img, it bootloops, because one or more of the modules it loads is causing a problem.

Basically what is so special about that Magisk? It's that it gives you root access (which is needed if you want to disable modules) without enabling (actually loading) modules.

It's a Magisk without loading modules.

You use it to disable or uninstall the bad modules and then load back normal Magisk.

If anyone wants to discuss this further please take it up to DM or another thread (more appropriate to Magisk threads)
[Magisk] TheRomRooster:
should i build them from scratch so the new fields get filled with correct data or can i just migrate them?
[Magisk] majorfigjam:
Just migrate them. It's worked perfectly in Linux on the ones I've converted.

The migrate script takes a custom.pif.json in the same folder, backs it up, and writes a fully populated new version.
[Magisk] TheRomRooster:
perfect, thx, glad it works on linux or else this would have taken a decade and a half to migrate em all
[Magisk] majorfigjam:
It only does one at a time, so there's a bit of renaming involved, but otherwise easy,

I did about 15 in 10 minutes
[Magisk] TheRomRooster:
im already thankful that the normal pif builder works on linux, that increased my throughput by so so much
[Magisk] TheRomRooster:
i have a good substructure in my PIF organisation so i really only need to CD, i have ./PIF/CODENAME_OF_DEVICE/custom.pif.json
[Magisk] rseiler:
And all modern Windows users have easy access to Linux, too, though it's easy to forget about: WSL (Windows Subsystem for Linux). The script works great with it (I have Ubuntu on WSL).
[Magisk] osm0sis:
No need to cd even, since migrate.sh accepts a path/to/custom.pif.json as an optional argument and will backup and write to that location instead of the script's directory. 😁

Nothing a little for `find` loop on your command line couldn't handle. 👍
[Magisk] gpvecchi:
I found a working fingerprint using Play Integrity Fix Next, thank you. By the way, I can't understand the difference between this version and OG one, apart from the APK.
[Magisk] TheRomRooster:
You the GOAT, migrating all 13 PIFs literally took me under 2 minutes
[Magisk] kdsgn3:
Update on my situation with boot issue:

Turns out while the "Pixel is starting..." error message is running, adb commands work just fine. Even scrcpy works as you can see.

View attachment 6048867

So....I have tried everything to get past this to the home screen short of wiping all data (including booting into Safe Mode, removing Magisk modules, re-flashing from the both the OTA and factory images, etc.) (PixelFlasher is amazing btw, I wish I knew about it before), but to no avail. I always end up stuck at this screen. So, PIF may not be the problem after all...

Unfortunately, through this process I lost root when slots changed, so, no backups with adb for me anymore since my screen is inaccessible to re-root.

Now, the problem actually might stem from when I was screwing around too much with system apps in Titanium Backup before that first reboot. Any that I messed with there were related to play services or google play. What system app might have gotten me stuck at this screen? Would there even be a way to clear data and reinstall a system app of this sort without root?

Another weird thing that might have caused this was when I was checking apps in DenyList, the screen blanked out for a second when I checked "System UI" Maybe doing that corrupted the UI somehow?

It's looking more and more like I may have to just completely wipe, which would suck because I would lose a lot of 2FA keys and other things that I never backed up (like a moron).
[Magisk] simplepinoi177:
I'm with either way....and as much as I'd love the engagement of my own thread, I'd feel better that your original-idea thread receives the credit and engagement since it would originate from there than being a simple signpost towards mine in such circumstance...
[Magisk] majorfigjam:
Yes, but I was lazy when I was creating them weeks back - i just tacked the device onto end of the name, so mine were custom.pif.json-att1, -verizon2 etc. I should have known better.

Which all makes me realise that it's now four weeks since we started the custom print game, and my first one is still usable.
[Magisk] TheRomRooster:
im really REALLY surprised that mine isnt banned yet cause its from a phone that was talked about A LOT back when it launched but now fell into obscurity
[Magisk] sawdoctor:
Is there no way to make all new members be given a welcome message saying if you have joined because of PIF read these posts first please? I know I'm over simplyfing but they could be given a link to the posts in the welcome message
[Magisk] simplepinoi177:
I imagine that would be most helpful (for these cases/instances, or in some general sense), but only the site admin can do that. I believe it was done when the site migrated a few months back (to announce the migration and that new posts weren't going to be migrating within the 18-24 something hours).

But as much as we're getting a whole lot new traffic (particularly from Telegram) from very green & new members, I doubt unless it's something a lot more major, it wouldn't be implemented and set up like that -- the age-old practice has been announcements like that be in the OP (whether newbies read it ever at all or not) and most likely would be left to that tradition.
[Magisk] changhuapeng:
I have updated my Extract Xiaomi.eu PIF Tasker app and project to work with @osm0sis's newly updated Play Integrity Fork v5.

You can find the updated apk and project files here: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-389#post-89234476
[Magisk] theofylaktos:
please can you paste a link?
[Magisk] tom1807:
Scroll up in this topic, on the right side is the most thanked post and right below the 2nd most liked post.

Both are good starting links.

Cheers

Tom
[Magisk] xSnowLeopardx:
Even though we can read everything important on the right side: if you're an XDA user like I am, you know you always start with the opening post/thread starting post/OP/however you want to call it hehe.

Still think that post should have links to guides/great tips as well. My 2 cents.
[Magisk] xSnowLeopardx:
So, @chiteroman ... why did you add a FP in the newest version again?
[Magisk] mike.s:
...and/or simply start reading 10-20 pages from the end to catch up on the latest developments. There's not much that isn't covered, again and again, every 10-20 pages.

It's discussed in this thread.
[Magisk] Vision:
I wake up and suddenly so many new version again :geek:🧐
[Magisk] sawdoctor:
He just added the one from 14.6, he's not added a new one and states in release notes he won't so cut him a little slack
[Magisk] pelia0:
Ok guys, I can't get it, my device is old af with android oreo (z2 force), so if I'm not wrong, hardware attestation is not available and there is no point to play with it so I can just copy my own build.prop info into pif.json?

actually I don't even see pif.json in /data/adb/, only pif.json.old and after installing last version my gpay worx
[Magisk] xSnowLeopardx:
Nothing about my comment you quoted just now stated that I asked why he added a new FP. Re adding an old one is still not something I'd have done.

I did not really attack him so why would I cut him a little slack? I have openly thanked him a lot in this thread, because he helped me + lots of people with having a 2/3 situation when we had 0/3 & 1/3. Was just curious why he did add one back after saying everyone should find a FP themselves -- nothing more and nothing less.

So, yeah. (Oh, and don't think I am attacking you now, merely explaining myself.)
[Magisk] miho171:
I just saw the 15.1 update release notes, will the module reinject 14.6 fp over my own working? Or just let you pass the verdicts with the one provided in the 14.6 version?
[Magisk] blue whale:
yeah the apps can't even be installed if the device is ''not secure'', I could thanks to Aurora. and then I get the message that root prevents them from working...

While my S5 has the official non-rooted samsung ROM, and the official ROM is also on my laptop, can't I retrieve it's profile before I install Lineage 18.1 ? SamFirm_Reborn says he official ROM is :

OS=Marshmallow(Android 6.0.1)

ReleaseDate=20210227121445

I guess I am interested in this part of the tutorial:

samsung ROM is formatted like this, first it's a single file .tar.md5,

View attachment 6048981

and system.img.ext4 contains

View attachment 6048982

I can't find the ''vendor build.prop''. the vendor folder only contains:

View attachment 6048991

so I just unzip build.prop and create a profile with this ?
[Magisk] mike.s:
I just don't get it. Someone has a working setup and a new version comes out. Then they want to know what's needed to change to the new version.

Big hint: if it's working, don't f with it by changing anything. There's nothing to gain.
[Magisk] xcl1pse:
Because that fps is already used in PIF 14.6 but force to use it again with additional field so it pass device again...
[Magisk] xSnowLeopardx:
Still chilling with v14.4 - no worries.
[Magisk] miho171:
Since the pif situation is evolving daily (with google banning fp and devs trying to keep integrity) I think it is a wise thing to keep an eye to the update button of the module, and when it's on, just read the notes of the release.
[Magisk] Gysper:
Updated PIF to 15.1 and passes now. Can also setup wallet without any issues.

Sidenote: I did attempt the previous fix by finding my own fingerprint but as a noob-novice, I don't think I have the time/energy to go and find fingerprints. I'm not complaining but if Google is putting down the hammer on this and you need a fully working phone with NFC/Wallet, I'd probably stick with stock until then. But I applaud the dev and community here for finding some unique workarounds.
[Magisk] sawdoctor:
I wasn't saying you were attacking him I was just pointing out he's not started to share fingerprints again that's all. I don't agree with the way he went through fingerprints but i also know he was the only one coping flak for it when all the custom ROM devs were doing it as well
[Magisk] Vision:
@chiteroman why in v15.1 add it new field "FORCE_BASIC_ATTESTATION": true ?

View attachment 6049004
[Magisk] osm0sis:
Yeah, he lasted, what, like 1 week? Guess he wanted 100% completion on all his used prints being banned. 🤣
[Magisk] vMAC:
So if I am no longer passing Device Integrity, do I assume that is an issue with a FP? Or am I having something else that is triggering that?

I pass Basic Integrity.
[Magisk] xSnowLeopardx:
FP. If you failed at basic, then it was something different (corrupt build.prop or wrong FP format). Device -> Google banned it.
[Magisk] Ginosius:
Same here.

I reverted to stock Oxygen OS 12 for this reason.

But I feel kinda stupid for running an older OS which doesn't get updates any longer (and can probably be exploited) just because I'm too lazy to carry my physical bank card with me lol.
[Magisk] dmenezes:
Google should feel even more stupid (and be ashamed) of forcing us to jump through these hoops, when the 'official alternative' is reverting to Stock, which as you pointed out, is almost always less up-to-date than our modded ROMs, and therefore less secure.

And the bigger irony is, the whole point of PIF is supposedly to somehow 'guarantee' security... yeah, right.
[Magisk] Ginosius:
Not only that, Google made it near impossible for banks to use NFC directly without resorting to Google Pay.
[Magisk] dmenezes:
Yeah, but that at least makes 'sense' (from a greed standpoint) because with Google Pay, Google get its cut.

Forcing us to jump through hoops to keep DEVICE_INTEGRITY, as far as I can see, doesn't serve even that purpose...
[Magisk] Ageete:
I was trying to find a FP by my own but pasting the json in data/adb. With 15.1 it's all good, but I can no longer see the file in that folder because it's in data/adb/modules/playintegrityfix instead. Was I testing the file in the wrong place?
[Magisk] sawdoctor:
It's sad isn't it. I have an app called sumup which i can take card payments with via NFC but i don't have a single app apart from Google wallet that can make payments
[Magisk] mkcs:
I tried the fork version by osm0sis, however, the fingerprint didn't work while it works on chiteroman version
[Magisk] osm0sis:
Did you migrate it to the new format? Or are you on Android 14 QPR2 Beta?
[Magisk] thf1973:
Did the fingerprint migrate successfully during the module installation?
[Magisk] molitar:
I'm confused I am using my own fingerprints but it seems I still have to update this module daily. Is there something else I need to do after installing so I don't have to do daily updates?

Stock Oneplus 6T ROM
[Magisk] vMAC:
Interesting because I am using the @osm0sis fork and the script from TheFreeman and I've gone through about 15-20 FPs and can't get Device to pass. I must be doing something wrong.
[Magisk] mkcs:
Not on any QPR. I added new information in example.pif.json and renamed it to custom.pif.json followed by the migration script. I'm thinking if there's incorrect information in the build.prop I found on the web due to additional parameters. Or maybe the migration is failed?

# cd /data/adb/modules/playintegrityfix; sh /data/adb/modules/playintegrityfix/migrate.sh; exit &>/dev/null

custom.pif.json migration script

by osm0sis @ xda-developers

! No migration required
[Magisk] xSnowLeopardx:
Continue the FP hunt, then
[Magisk] chiteroman:
Should work with Displax's module and mine, you must select main and unstable process.
[Magisk] RockerAlex:
What happens if you select them all?
[Magisk] chiteroman:
Will be useless because GMS only check root in main and unstable process.
[Magisk] vajenc:
Have you tried using Shamiko in combination with denylist (*DO NOT* turn on denylist enforcement). For the more detailed instructions on how to set it up, just check the link.

It works with all my banking apps. Maybe it is worth a try, but it all depends on the banking app in question.

Fingers crossed

P. S. If your banking app is specifically asking for a locked bootloader, then this will not make a difference
[Magisk] Essentrix:
Funny mate. 🤣
[Magisk] pndwal:
Do you mean Google Play Store or Play Services?... Nb. Play Store doesn't check for root; it polls Play Services or Play Protect Service if exists separately for a cached PI verdict to set Play Protect certification status and registered requirements individual apps to be available in Store...

Also, all Zygisk based device integrity fix modules hide root from GMS (Google Play Services Droidguard and main processes, com.google.android.gms.unstable and com.google.android.gms) themselves (inbuilt hiding), so no need for you to add to denylist... Nb. Shamiko won't break the fix modules but Denylist will if active...

All you need to do manually is add PUBG to denylist and check you have PI deviceIntegrity and Play Protect "Device is certified"...

🤠 PW
[Magisk] chiteroman:
MEETS_DEVICES_INTEGRITY unchecked · Issue #4 · chiteroman/PlayIntegrityFix

Hi, in 9.4 I pass the device integrity check but not anymore in 9.7.1. I am on Oneplus 8T OxygenOS 13.1

github.com

Due to the changes that each OEM makes to their Android system it is impossible for me to give a universal version for all devices. In this issue I have uploaded a new version that probably solves the error to the user but will not work correctly in other devices. What a headache 😢
[Magisk] ipdev:
To promote some optimism.

View attachment 6010165

Keep up the good fight. 👍

Cheers. :cowboy:
[Magisk] ykjae:
I've found personally that 8.4 gives me fewer problems. The original never gave me problems either, but I like to keep updating. The displax module also shows fewer problems, especially the version before Mod 2.0 (I can't remember the number).I've got a Pixel 6 Pro, which seems to always malfunction in some way however.
[Magisk] J0nhy:
What's that bank?
[Magisk] chiteroman:
MEETS_DEVICES_INTEGRITY unchecked · Issue #4 · chiteroman/PlayIntegrityFix

Hi, in 9.4 I pass the device integrity check but not anymore in 9.7.1. I am on Oneplus 8T OxygenOS 13.1

github.com

As I expected this version works, but I'm very sure if someone try this version on very recent device shipped with Android 13 wouldn't work and 100% wi-fi calling would break. The cause is the STL built in Zygisk lib...

The "best" solution is uploading two modules (one with c++_static STL and the other without STL) and users should try both and check which works better in their device. But this wouldn't be a "universal" fix...

The truly best solution is modifying framework.jar of the ROM and implement by yourself the fix.
[Magisk] chiteroman:
Some Android builds aren't very friendly with Zygisk and the c++_static STL :(
[Magisk] amk316:
how can i modify framework.jar?

is there steps to do so?
[Magisk] novicecoder0:
I am unable to use GPay(google) or PhonePe.

I have lineageOS 20 nightly build, android 13 on OnePlus 7t

I am able to pass YSNAC but not even a single of Play Integrity API checker.

Even google play store isn't showing certification for my device. But I guess that's because I can't Pass PI API checker.

Root check works fine.

I am using Magisk Delta right now, after PhonePe and GPay suddenly stopped working yesterday. A lot of other apps that don't let you work with rooted device is working fine.

Even if not able to work apps, I would like to know how to pass the Integrity test.

Plz help
[Magisk] pndwal:
Is ROM official LOS?... selinux enforcing? PW
[Magisk] novicecoder0:
Yes, Selinux is enforcing. Encryption enabled.

Yes official LOS ROM