yashsingh1/xdaforums huggingface dataset:
[Magisk] awtompson:
v15.9.8 not working for me. I deleted pif.json. Removed the module and tried PI Fork & ran autopif.sh. Still failing device. I'm on a Pixel 7 Pro. I guess I'll try disabling all the other moduels.
[Magisk] pershoot:
7a (lynx):

osm0sis's v8 (from GH) and using custom.pif.json confirmed working ok (DEVICE pass)

I did have issue with chiteroman's 15.9.8 (from GH) and using a working pif.json (the in-built in the module should work fine on-device (as per other posters), but I did not test). 15.9.7 confirmed working ok (DEVICE pass).
[Magisk] awtompson:
Got it working on 2nd try. Not sure what I did wrong. I removed lsposed. Maybe that was it.
[Magisk] pershoot:
I do have lsposed installed as well; no perceived issues, thus far.
[Magisk] TheRomRooster:
Wallet not working on latest osm0sis fork with todays xiaomi eu print, passing device integrity though, already tried deleting play services data and wallet data but still failing, anyone else?
[Magisk] generalculprit:
wget was successful today. So I'm back in the game again. Let's see how long it lasts this time.

Thanks everyone. 🙂
[Magisk] fbirraque:
Working smoothly for me on Poco F3 (alioth)
[Magisk] Hikari no Tenshi:
Steps that helping me to make Google Wallet work again:

1. Check that device passing integrity check;

2. Turn on Flight mode;

3. Clear cache and data of Google Wallet and Google Play services;

4. Reboot device;

5. Turn off Flight mode;

6. Add cards to Google Wallet.
[Magisk] zgfg:
Maybe the server was overloaded yesterday with downloads - all Xiaomi.eu users plus the PIF users

Similarly PIC and SPIC were overkoaded for testing Play Integrity
[Magisk] osm0sis:
There is a FAQ, y'all. Most of the last 2 pages would have been handled by it. It's linked in the OP. Everyone please go read it and direct others to.
[Magisk] Grunwalski:
Hello, I just can't get it to work.

I've spent the last 2 hours trying out several modules and versions.

Maybe someone can give me a step-by-step guide:

Smartphone: Poco X6 Pro 5G HyperOS 1.0.7.0UNLEUXM

Security patch: 2024-02-01

KernelSU LKM 11682

YASNAC: Basic integrity: Pass CTS profile match: Fail

Integrity API Checker: MEETS_DEVICE_INTEGRITY: Fail MEETS_BASIC_INTEGRITY: Pass

What I have tried so far: KSU + Zygisk + Shamiko (Reddit Post) Not working

PIF (v15.9.8) or PIF (v15.9.7) Not working

PIF (v15.9.8) + PlayIntegrityNEXT (aka PlayCurl):

"Open the FP Downloader app and grant the necessary permissions. Alternatively, if you've chosen the Termux method, run the 'fp' command."

FP Downloader App not working (App icon default, won't start)

I don't understand the alternative "fp command." What do I need to do? Is the custom FP still needed?

When do I have to delete Play Store Service Data? Is clearing cache enough?
[Magisk] osm0sis:
If you're passing DEVICE then the module is doing its job, sounds like Wallet/Pay or your bank has a cached server-side failure or red flag you'll have to clear with them.
[Magisk] G5-User7080:
I feel you, even after reading guides and posts, there are still things unclear to me, however I puzzled some things togethers, no one would confirm yet if I'm right with my assumptions since all I get is "read previous posts", but here goes.

The two "main" scripts, gen_pif_custom.sh and autopif.sh are for generating a custom pif.json from a build.prop file and for getting the latest xiaomi.eu print respectively.

To make your life easier, just use PixelFlasher, badabing added a pif manager which has a button to do what autopif.sh does, it can also read build.prop files, lets you edit the props before writing it into a custom pif.json on your device. So essentially what gen_pif_custom.sh does.

Though I got a slightly different output running gen_pif_custom manually, along with some extra fields.

And I think it just uses the build.prop file that's in the same directory, I thought it wanted both system build.prop and vendor build.prop but it seems to only use one of them. Also Vendor build.prop never worked for me, it would fail even basic.

You can run gen_pif_custom on any linux machine, doesn't have to be on your phone, but autopif is designed to run on device.

Just navigate to the directory you put the script in and do . ./gen_pif_custom.sh, optionally with options props and all or whatever they were (they're explained in the first lines of the script).

ADB shell works too, as well as a local terminal on your device of course (I use connectbot cause I don't like termux).

The scripts are not part of the module, at least not chiteroman's.

Run from anywhere I guess? Though I just made a new directory on /sdcard/

Outpuf file goes in /data/adb/

So just run mv ./custom.pif.json /data/adb/custom.pif.json if you're on osmosis' fork or mv ./custom.pif.json /data/adb/pif.json if you're using chiteroman's version.

I still don't know what's the difference between both aside of their custom pif naming.

The xiaomi.eu print is not ideal to use, as far as I learned, the folks behind it tend to find a new one quickly when it gets banned, but it also gets banned more frequently than custom ones.

To search for a custom one, follow osmosis how-to guide, aside that, just try out different phone's factory images as well as different versions of those.

Use a tool like MTK extractor to unpack the system.img and vendor.img files.

Get the build.prop from /system/build.prop from the extracted system.img (usually, otherwise use file search).

As well as /build.prop from the extracted vendor.img

Some OEM's pack their firmwares in custom file formats, just google for a tool to extract those, it's different for every OEM.
[Magisk] PandarianFury:
I have installed the latest version of Chiteroman 15.9.8. I get device integrity, but my banking app is no longer working. I am using Magisk 27000 and Zygisk with Denylist. Any ideas?
[Magisk] pershoot:
Try Shamiko (https://github.com/LSPosed/LSPosed.github.io/releases) and turn off Enforce DenyList.
[Magisk] osm0sis:
@badabing2003 has always had PixelFlasher up to date with my fork, just to answer your questions there.

And my gen_pif_custom.sh and migrate.sh scripts can be run anywhere (device or PC), but my autopif.sh is specifically designed to run completely on-device. 👍
[Magisk] linuxares:
I just used Pixelflasher and updated the new prints with your mod @osm0sis . Took less than 2mins to do that all and worked like a charm (honestly what took longest to download the update and find my cable)
[Magisk] G5-User7080:
corrected.

So PF will detect the specific PIF version and change filenames according to that, no configuration needed?

And aside of the custom pif filename as well as that chiteroman's version comes with xiaomi.eu print (or some other usually working one) by default, is there any functional difference between both versions?

Also (of course I remember my other question the moment I hit "post")... I know originally it was said that A9 and higher firmwares are less likely to work, but how is it now?

The only working prints I had were from A9, do A8 and below have any chances of working still or are they dead?

And then A9 - 13 can all work or so I read somewhere?

Oh and just to confirm, gen_custom_pif takes props from any build.props files in the same dir?

I initially understood it as both build.prop's from /system/ and /vendor/ need to be present, and it also said something like "it will prompt you for missing ones" or something.
[Magisk] PandarianFury:
I have tried this. The banking app doesnt detect root anymore, but it is infinitely loading. Sigh.

Nevermind. Got it working after a few reboots of everything. Thanks!
[Magisk] G5-User7080:
[unnecessary reply]
[Magisk] dlads:
15k+ posts... 😂 Not sure it matters anymore mate.. but yea you're right, all the info is deffo there.
[Magisk] zgfg:
All good in theory but be aware that chances that prints you generte by the gen script from a build prop files somewhere from a certain device and ROM will work are now in per mille. Hence you will need to test hundreds to eventually find a good one

Of course, it depends on which collection of build prop files you test. Any publicly available collection of the working build prop files would maje a low frouit for everbody and those prints would soon become banned

Hence first grab the availabke prints from XEU, by use of autopif script (or the same by using chiteroman's PIF nodule), to have your phone working and then invest time in fishing your provate prints

And for the fallback, you can again use autopif in the future when Clark got banned, XEU will publish the next for the masses
[Magisk] G5-User7080:
They've become that rare?

and I thought I was doing something wrong when it took me like 10 different roms to find a good print.

how do people have 20 working custom prints in store...

what is a "publicly available collection of the working build prop files"?

as in,.. tested props that pass?

I didn't even know such collections existed.

I just download a bunch of firmwares, extract their build.props and try them... is that the wrong way?

PrintS plural? I thought xeu was always just one print that was working, so xeu is a collection and the autopif script gets a random one from there for you, or how does it work?
[Magisk] zgfg:
From thousands I had tested over time, from whom few hundreds worked half a year ago, I have now (or still, depending from the point of view) 44 working in the range A9-A13

And yes, Chiterman builds in the same Moto Clark A6 prints 'published' by Xiaomi.eu
[Magisk] badabing2003:
One way is to do what you're doing, which is download a firmware, extract the necessary parts, build a pif.json and test,

Rinse and repeat.

Each manufuacturer firmware packing is different, so you'd need to adapt your extraction process.

Another method is to scrape various sites that have some dumps, (again each site is different)

Grab the necessary parts, build up the pif.json and test.

Rinse and repeat.

Tedious process unless you automate it, but it involves coding.

Xiaomi.eu at any given point embeds one single print, and all the autopif mechanisms extract from it, it is not a collection of prints, although they probably have a collection which was gathered trough the processes outlined above, and when one gets banned, they release a new apk with a new unbanned print in it.

And as you correctly pointed out, knowing what fields / props to use from which files (product. vendor, system ...) makes a big difference.
[Magisk] osm0sis:
Yeppers.

Several. Read my README, and follow the links in my Odds and Ends thread PIFork blurb for context.

5.0.1 to 13, but the vast majority are still ~8.

It takes the ones in the same directory named how it tells you to name them. Simply running it to see would explain.
[Magisk] zgfg:
Prints (plural) - yeah, it's actually one Fingerprint with the corresponding other props, for a single custom PIF JSON file.

Whan G would ban the current one, they will publish another, as long as supplies last

Once they burn all, they can switch off the lights - users of Xiaomi.eu custon ROMs (say, debloated and somewhat improved Xiaomi offficial ROMs) are accustomed to pass Play Integrity (most of them do not even know much about, they just expect to use Wallet, etc)

Collections - look at the attached screenshot, follow the links to GitLab, The Dumps = build.prop files from 'all' vendors (for many you have never heard of), 'all' devices and models, and 'all' their ROMs

You can download any of them but one file by one. Usually, per one ROM there will be single /system/build.prop with one or sometimes many /vendor/build.props and /product/build props

All are free, you can generate custom pif json files and test them, but very, very, very rare tests will pass Device Integrity

Moreover, where you have several /vendor/build.prop files you have dillema which one or which combination to try. And if 7 don't pass, you never know would maybe the 8th pass or not
[Magisk] matrix200200:
I have upgraded to latest CHiteroman's version and waited patiently for approximately 12 hours.

This morning Wallet app still shows "doesnt meet hardware requirements"

LOS 13.

Should I do the clear cache thing, or perhaps wait a bit longer?
[Magisk] Nergal di Cuthah:
Do you pass both basic and device? Cache I'd say clear away, data you may have to re-enter your cards.
[Magisk] matrix200200:
Can't say.

The checker has been throttled.

Yeah by data I meant clearing data of play services and re-entering the cards.
[Magisk] Nergal di Cuthah:
Enable developer settings in PLAYSTORE (not android settings) and use its less throttled checker.

Is your kernel on @osm0sis' banned list (as many los kernels are represented there).
[Magisk] matrix200200:
Thanks.

Yeah meets both device and basic.

So clear the cache and data?

Or perhaps wait a bit longer and make it sort itself out?

As to kernel, I am not sure, I checked the ban list, but at that time, though some strings appeared to be there, the wallet worked so I moved on.

You think it could be the kernel?
[Magisk] Nergal di Cuthah:
I mean it's common to take it 24 or more hours so, if your itching to do it clear data, if you pay alot with your phone, you can go the fast route and clear it.

Edit: that's my opinion, but I've never had to do it and I've never paid with my phone
[Magisk] matrix200200:
Just read somewhere else, that it could take up to 72 hours.

I guess I will wait for a bit more.
[Magisk] trevtdogg:
if you have device integrity, then no it's not the kernel.
[Magisk] zgfg:
Once I waited (I did post about here) ten days or so with no success

I cleared Wallet Cache right on the counter, reopened Wallet, it didn't complain anymore and I paid
[Magisk] matrix200200:
I tried clearing wallet cache (and data) to no avail.
[Magisk] badabing2003:
Have you tried adding a different card?

It could be that your bank (card issuer) had flagged you.
[Magisk] pndwal:
Also, does Wallet, 'Payment setup' show 'phone meets security requirements'? 🙂 PW
[Magisk] dlads:
This is what I usually do.

1. Open Magisk and remove the module, don't need to reboot yet.

2. Download the new one then install it, again don't reboot yet.

3. Open wallet and remove your card but not from Google, only your wallet.

4. Go to app info on wallet and force stop, clear data.

5. Confirm play store, wallet, play services are all blocked within deny list within magisk.

6. Reboot, allow the phone to fully turn on, then add your card back to wallet, if you get the white acceptance writing then you're back in.

This is what I've done every time it's failed and I've been fine.

Hope this helps 💪🏼
[Magisk] simplepinoi177:
clearing Google Play Services, Wallet, GPay, (for extra measure Google Framework, Play Protect, & Play Store) always got my wallet working after losing and re-gaining MEETS_DEVICE, without waiting the pre-requisite 72 hours (it took 3 days for me), downfall with this method being that you'd have to re-add every single credit card to Wallet...
[Magisk] matrix200200:
No.

simplepinoi177​

The readding is actually a bit problematic, I did get my card temporarily disabled for google pay for a few days, while trying to add it too many times.

I think, I will just wait till sunday and see then.
[Magisk] pndwal:
If not seeing 'phone meets security requirements', don't focus on card... Device security problem is the primary issue...

Did you clear Google Play Services (as well as Wallet app) data?... Please say device... 👍 PW
[Magisk] miho171:
I'm in the same situation, Xiaomi 12T Pro, updating PIF, meet Device Integrity, Play Store says Certified but Wallet doesn't meet the requirements.
[Magisk] pndwal:
Tried clearing Google Play Services as well as Wallet app data?...

Aside: Wallet used not to detect root, but it wouldn't hurt to add GPay/Wallet to denylist (even better, try with Shamiko hiding) just in case Google's added detection... Repeat data wipes after that...

🤠 PW
[Magisk] Wolfcity:
To add some information to "Niantic", the developer of "Ingress Prime" and 'Pokemon Go" who announced to use STRONG_INTEGRITY from May 27 on, I firstly got a warning in the game regarding to be aware of using rooted/jail broken devices (and for sure unlocked bl and custom roms) see attached screenshot in german and translation by Deepl below.

Would be interesting to see what consequences would follow....
[Magisk] lupastro82:
Yesterday, after latest pixel update, i lost device integrity (wallet warning about this and cannot work). Now I don't remember how to fix. Tried autopif but remain invalid 😅🤦

Ok, removed fork release and installed release from this topic (first post). Now again green. 😁
[Magisk] MaximeMNT:
Hello!

I don't understand why, but my device won't even pass the Basic Integrity.

I have a Xiaomi K30 Pro Zoom on last xiaomi.eu rom and I just installed the PIF module. I'm using the last Kitsune canary version.

Here all my modules:

iOS 17.4 iOS Emoji font by Keinta15

PIF v15.9.8

Systemless Hosts

Youtube Revanced

Zygisk LSPosed v1.9.2

zygisk-detach v1.15.0

uname -r: 4.19.157-perf-g8779875ad741

View attachment 6103860

What can I do? :(

Thanks!
[Magisk] zgfg:
PIF means PI Fix from chiteroman or PI Fork from Osm0sis?

With at least the version number, we could conclude

Asking, because the course to fix would be different

Also, with the same Kitsune, same modules, same ROM and kernel, theee days ago you were passing Basic and Device Integrity?
[Magisk] Wolfcity:
Uninstalled XiaomiEUModule_apk? You can't have both, Pif(fork) and the inbuilt APK.
[Magisk] MaximeMNT:
I did include the version number in the list haha, but PIF from chiteroman.

I just flashed last Kitsune, rom & PIF today. Before I was on another setup but my bank was blocking (but afaik, BASIC was passing without any problem).

I did uninstall the XiaomiEUModule **updates** but I think i misread the tutorial on xiaomi.eu. :/ My bad!

But now that I totally uninstalled the XiaomiEUModule, cleared the GMS cache & restarted, everything is working!

Thank you and have a nice day! :))
[Magisk] dlads:
I've never used Lsposed, used to use xposed.

Perhaps get rid of them all then try again, then add them bit by bit...
[Magisk] zgfg:
To the contrary, LSPosed is ok.

I'd be surprised if you could pass with the old xposed or edsposed

Reason: LSPosed is Zygisk based and Shamiko will hide it. But not for the ancient XPosed or EdXposed (whatever they were called)

Many of us (me incl.) use LSPosed with one or more LSPosed modules and of course pass PI. For banking and similar apps (but not for PI) it requires then an additional LSPosed module HMA (Hide My Apps) to hide all LSPosed modules, but with all this we're heading out of the topic here...

+ Only some LSposed modules cannot be hidden, like the notorious LP (its name is not welcome here) and will even cause PI to fail

Hence LSPosed per se is ok, only some of its modules/apps might be troublesome (almost all are ok)
[Magisk] Spartacus500:
New method check 🤔
[Magisk] zgfg:
Thannks, found the app
[Magisk] Spartacus500:
Try TOKEN AS SDK
[Magisk] zgfg:
Yeah but I'm ntrding to understand how can that be pra accomplished for ...
[Magisk] dlads:
I'm sure it is ok, not my kind of mod but if the person cannot get play integrity to work then the first thing I'd do if the other steps I wrote haven't work then I'd disable all modules in case one of them is the culprit..

Nothing to do with if I like Lsposed or not...
[Magisk] zgfg:
Generally yes but again, particularly LSPosed itself is not a culprit

Also, from his posts he was previously passing PI, seems also wirh LSPosed (and it modules), hence something else changed and affected
[Magisk] mike.s:
Wow. Another 10 pages and the only thing which has changed is the fingerprint.

It's not hard. Update your fingerprint, or upgrade to chiteroman's newest release. If you still have Wallet issues after, wait a few days. There are a several ways to find the latest xiaomi.eu fingerprint, all of which were documented before the current brouhaha, and have since been repeated. Simple, if you put even a little effort into it.

Methinks there are lots of people here who shouldn't be rooted, refuse to put any effort into it, and only are because they followed some boilerplate method.
[Magisk] simplepinoi177:
@matrix200200 , well, yeah, there's always the possibility that it's the card/bank that's the issue (this has happened to me multiple times since my Pixel 5 and USNF; it's quite a bit unnerving until/unless you try "verifying" another card and figure out it's a single bank). But I was more addressing the issue you describe below where it's the whole Wallet app (not just a single card added "too many times" "temporarily disabled) where, if you (or others) didn't wish to wait (as you state you're willing to "wait till sunday and see then"), then you could do the method I outlined to remove the "doesn't meet hardware requirements" and be able to tap-to-pay immediately, but the downside is the user would have to re-add the cards.
[Magisk] swieder711:
Running PIF 15.9.8 on Pixel Tablet with stock May update. I pass device and basic integrity. I also pass safetynet test. Yeah!

Play Store says my device is not certified. Tried manually registering Google Service Framework(GSF) ID. Says it is already registered.

Any suggestions to get device certified?
[Magisk] Vision:
Have you tried to delete the GMS and Google Play data and reboot?
[Magisk] swieder711:
Deleted Storage and Cache for Google Play Store and Play Services. No GMS because Pixel Tablet is just wifi. Rebooted. Still uncertified.
[Magisk] osm0sis:
Play Protect has its own APK now, clear its data too.
[Magisk] swieder711:
ReDeleted Storage and Cache for Google Play Store, Play Services and Play Protect apps. Rebooted.

Device is certified now. Whew.
[Magisk] CZ.Kostra:
FP XEU Checker v2.0 - added GUI for various settings
[Magisk] beeshyams:
M

Much appreciate 🙏
[Magisk] Vision:
Yeah, sorry not clarification, I meant Google Play Services, according to package name (com.google.android.gms), so GMS
[Magisk] szinyo1048:
Hello all!

i use DR Ketan Rom, U09 in my S24 Ultra

I all step is follow installing, than is run: Play Integrity Api Checker, and show me:

Device integrity: RED

Basic: OK, Green

Strong is RED

How to complete all to green?
[Magisk] CZ.Kostra:
Install stock ROM and lock bootloader. There is no other possibility.
[Magisk] ashish1989:
Really appreciate your efforts, great work
[Magisk] szinyo1048:
i want to use google pay, with root.. i want to hide magisk, and use all my bank app...

no stock rom, please help how to all green safetynet pass

(

i use DR Ketan Rom, U09 in my S24 Ultra

I all step is follow installing, than is run: Play Integrity Api Checker, and show me:

Device integrity: RED

Basic: OK, Green

Strong is RED)
[Magisk] CZ.Kostra:
Which PIF module do you use?

Do you have a valid fingerprint?

Isn't your kernel banned?

Does another Magist module conflict with PIF?

See to first post.
[Magisk] szinyo1048:
I USE Dr ketan Rom U09 - And all install is follow the instructions.

This say " Esential fix auto fix all safety net " than reboot, i have in phone:

Foxs Mum, and IntegrityChecker, Foxmum: -> Play integrity fix 15.9

and Safetynet sensitive props v3 and shamiko 1.0.1, and zygrisk 1.9.2

But only one green if i check,

how i check, why red, the device, and strong?
[Magisk] pndwal:
Well I think @chiteroman has one, but risky and requires a "a very particular set of skills"... I have another, but has it's own risks, especially since green paint can be messy... 😉 PW