yashsingh1/xdaforums huggingface dataset:
[Magisk] konstantinos_general:
Unfortunately it will not pass MEETS_DEVICE_INTEGRITY on leaOS, it worked ok with 15.9.8 until yesterday, today removed the old module, checked for any old pif.json on /data/adb, rebooted, installed the new one 15.9.9 rebooted again but no luck at all.

If anyone needs any information (props or whatever) from my phone I can share whatever it needs. Thanks.
[Magisk] dmenezes:
Perhaps this kind of info should be pinned to the top of the thread or put in a FAQ or something... no one has the time to "read back a few pages", or at least I don't, and certainly not for "just out of curiosity" info like this.

Thanks. So about 69 weeks (68 now, I presume), ie about 1 year and 4 months.

I *really* hope we can get a more definitive solution to escape Goggle's Play Integrity hell before then...
[Magisk] 4sz0m:
Works on Pixel Experience. And using @osm0sis fork. Simply changed the FP to sailfish.
[Magisk] xantrk:
Working with osmosis fork on Pixel 6 Pro as well. Thanks!
[Magisk] mike.s:
So, instead, you selfishly add more cruft to the thread. Whatever.
[Magisk] notanSU:
not sure if this is helpful to you @chiteroman but id like to mention that I updated to your latest module and the fix does indeed meet device integrity.

I am using lineage os 20 with Magisk
[Magisk] notanSU:
And thank you!!
[Magisk] 에어 론 리:
i'm using your sources, but didn't update them, just update pif and it's workin on prev sources ver.

Thank You and guys for your work!
[Magisk] soa008:
Not passing BUT i got RCS back working !!
[Magisk] anova93:
Tried both this and osm0sis's fork version, but for some reason after multiple tries and reboots and using the play store integrity checker it keeps saying my poco F3 is stuck on Pixel 5 redfin.
[Magisk] bombadier:
pixel 7a using Osmosis's fork, just ran autopif.sh and created the new fp, copied it over and am passing again cheers.
[Magisk] sawdoctor:
Less than 69
[Magisk] sawdoctor:
Could Google have just added more banned kernel strings to their banned list?

Would explain why stock ROM and only some custom rom passes?
[Magisk] niko26:
v15.9.9 working fine on Pixel Pro 7. Thanks @chiteroman
[Magisk] mugendon:
Pasted the contents of pif.json from the sources into pif manager from pixel flasher, clicked update pif.json but still basic. Did you do anything else?
[Magisk] ziomek3120:
After updating pif.json from github, Play integrity fix works fine on version 15.9.7. Paranoid Android, Xiaomi 13 Pro (nuwa). pif.json can be replaced with Termux using the sudo nano /data/adb/pif.json command. You must first install the tsu package using the pkg install tsu command
[Magisk] wilsonhlacerda:
BASIC + DEVICE passing here. Official PIF on official LOS 20 but its kernel is set to a custom name.
[Magisk] EAZY BLACK:
kernel name mokee+

passes only basic

los 16.0 android 9

microg with play store
[Magisk] 에어 론 리:
mmm, mb my rom based on stock, but very deep modded? that's why? dunno
[Magisk] ziomek3120:
Tutorial how to set custom name?
[Magisk] immortalwon:
use a hex editor on the boot.img and edit the name of the kernel, carefully. Make backups as well as I am not responsible for bricked device.

Also has anyone figured out why it's not passing on custom roms such as evolution x?
[Magisk] zgfg:
Little more, ~75 are still ok

Over 75% that were ok last week are gone yesterday together with Clark
[Magisk] oopps24:
PLAY integry Next not more working. What can i do?
[Magisk] wilsonhlacerda:
Use this script:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89323635

In a nut shell:

save the script on mobile, any folder.

open a terminal and go to that same folder.

run it with a "sh scriptname parameters".

"sh scriptname" will show you all parameters you can use, or read the link above for main ones.

It can automatically extract boot, patch with desired name and flash for you. But if you want to be on very safe side you can:

get your clean boot image file (from ROM).

run script only patching file (read output to be sure no errors).

get this file and patch with your Magisk Manager app.

get this new file and boot mobile from fastboot without flashing (fastboot boot file).

if everything goes fine then you can flash the file (fastboot flash boot file / or TWRP).

For more info on banned Kernel names, read this:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] purgy:
Exact same story here.

Here's hoping we get a longer reprieve than last time lol
[Magisk] dknight178:
has anyone encountered an issue wherein, after killing com.google.android.gms.unstable and replacing the pif.json, it initially passes device integrity, but after rebooting, it then fails even basic integrity? Have encountered this twice today.
[Magisk] dlads:
15.9.9 worked.

Just removed the card.

Cleared wallet data.

Removed module.

Rebooted

Installed 15.9.9

Rebooted.

Readded card

Seems to be ok.
[Magisk] wilsonhlacerda:
Read my comment just above for a very fail safe approach.
[Magisk] dmenezes:
oh crap... :-( so what was it they did this time, a mass bananaing, or just tightened some rule that ended up bananaing those many devices?

I guess nobody really knows, but if I'm wrong, please set me straight.

But anyway, if the PIG banishes every week 75% of what's left, we will be in a logarithmic spiral that, according to my calculations, will get us down to zero FPs in less than 16 weeks... 😵‍💫
[Magisk] Flr Power:
V15.9.9 not working on Poco X3 pro with Derpfest ROM...
[Magisk] wadams1:
edit: figured it out. thanks!
[Magisk] SoulsAssassins:
tried autopif.sh + killgms.sh didn't pass device on osmosis fork any idea ?

i have no xiaomi eu no playcurl etc
[Magisk] adilrenzu:
V15.9.9 Working on poco F5 hyperos 1.0.7.0
[Magisk] dlads:
Do this.

Just removed the card.

Cleared wallet data.

Removed module.

Rebooted

Installed 15.9.9

Rebooted.

Readded card
[Magisk] pershoot:
You would need to copy it in place after autopif runs (this assumes you are using v8 and run autopif elsewhere). /data/adb/modules/playintegrityfix/custom.pif.json ... Then, killgms.
[Magisk] Spartacus500:
For me also works new version 👍😘
[Magisk] Flr Power:
I don't even pass device integrity so I don't bother with wallet yet.
[Magisk] SOCOM-HERO:
Working again using PIFork and Playcurl. Huge thanks.
[Magisk] fkrrr:
which pifork?
[Magisk] SOCOM-HERO:
osm0sis version
[Magisk] mattburga1984:
BASIC and DEVICE passing but Wallet says my device doesn't meet security requirements.

Pixel 7 Pro, stock rom, stock kernel.

I have PlayIntegrityFix 15.9.9, no playcurl.

Any ideas how to fix?
[Magisk] wilsonhlacerda:
Disable Play Protect inside Play Store. Google uses it to flag apps they don't trust.

A new public fingerprint is available within the PIF updated a few hours ago.

To avoid conflicts:

uninstall PIF

uninstall Playcurl

Reboot

Delete /data/adb/pif.json if it exists

install newest PIF from its official Github releases

Reboot

Do exactly all that exactly in that order. Test Play Integrity certification. Should get BASIC + DEVICE.

If it fails:

Disable/uninstall all other modules, let only PIF

Reboot

Test Play Integrity certification. Must get BASIC + DEVICE.

If it fails then there are some conflicts with your own custom ROM (it probably has some fingerprint mechanism baked in, check with custom ROM developer).

Or your Kernel name is banned. Read about that and solution here:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] MikeZh:
Just wait. Or clear google services data & add your cards again
[Magisk] casouzaj:
Weird! Few days ago, when the Moto Clark FP got banned, autopif.sh insisted in downloading it again. Today, it switched to Google Sailfish, and, after a reboot, device integrity is back to work for me.
[Magisk] wilsonhlacerda:
Wait till it refresh cache. Or force that cleaning data of related apps. Read pages back for details/which apps.
[Magisk] immortalwon:
What android OS are you on?
[Magisk] fkrrr:
Not working for me
[Magisk] casouzaj:
LineageOS 21 on a Sony Xperia 1 II. KerrnelSU, PlayIntegrityFork CI #223 (Sailfish FP), Shamiko V1.0.1 and Zygisk maphide. Contactless payments are working here too.
[Magisk] Flr Power:
It seems nothing works 😕 I think it is related to my Derpfest ROM latest...
[Magisk] zoisa:
Same on crDroid 9.15
[Magisk] RAZINARES:
not working for me either on EvolutionX 9.0

did it get banned already or something else?

Sent from Pixel 7a using ReLabs
[Magisk] linuxares:
Used Pixel Flasher and got the new key. @osm0sis would it be possible to somehow encrypt the key so it's obfuscated? I guess not with Droid guard need to see it in clear text?
[Magisk] frank93:
false alarm (from my side at least) before, sorry: i used your zip and manually extracted the fingerprint, copypasted it into pixelflasher and saved it - that’s when it didn’t work (and i posted before), using osmosis’ fork module.

ran autopif.sh then a bit later, which returned the same (sailfish) print, and then all of a sudden .. everything back to "normal". i guess there was an issue with the formatting?, i didn’t really pay attention to the minor details in json-syntax-"needs" between the modules.

either way, sailfish is working for now (pixel 7a, osmosis fork). <3
[Magisk] zgfg:
You mean prints?

DroidGuard does not read from the json file - module (it's binary code) reads from JSON and injects the prints to DroidGuard

PIF (Chiteroman) used to have (eg, previous version) prints hard-coded into the module, without JSON file

But as long as the modules are open-source on GitHub, one can find the prints even if they are hard-coded to the native C code for the Zygisk injector

Besides, G could start sorting out directly on the server which prints are misused for spoofing - DroidGuard sends everything it has collected or what was injected to DG), and based on that G server delivers the final verdict what is passing and not
[Magisk] Victor27587:
Crdroid 10.5 not working either
[Magisk] ohap:
15.9.7 pif 10.1 playcurl and wait 10 mins or so.
[Magisk] generalculprit:
+1

Big thanks to everyone involved!

Let's see how long it lasts, especially when xiaomi.eu is using that print like we were using theirs. 😉
[Magisk] wilsonhlacerda:
Fingerprint is always plain text. At the end it can be seen at least on Android logs.

Besides that if it is an open source module/app that deliver it, it can be read/unencrypted from sources.

The only way to try not exposing it would be towards a closed source module/app - thus not trustful - and not generating any Android log. And this would be effective only for users, but not Google itself (that will always obviously receive the fingerprint when checking).

Besides that the fingerprint is indirectly presented (device name) in Google's Find My Device/device list to any user. That is why you see there your device as an weird one (Motorola and others if you have been using PIF lately).
[Magisk] Victor27587:
Where can I get the 10.1 playcurl?
[Magisk] birdr:
This is very helpful - but unfortunately seems not to work if you are rooted via KSU. since it fails on missing magisk busybox module. Are there any other methods to rename your kernel without resorting to a hex editor...
[Magisk] wilsonhlacerda:
Maybe you can add to KSU the busybox module (by @osm0sis ), and be enough.

Then follow instructions.
[Magisk] DVBMan:
No. Sailfish print not working on Poco X3 NFC with crDroid 9.14. Tested PlayIntegrityFix and PlayIntegrityFork. No success.
[Magisk] carlese:
PIF not working seems to affect custom Roms, some devs like @joeyhuab are looking into the issue, let's hope something comes up..
[Magisk] buzzywuzzy:
as in one should downgrade to pif 15.9.7 and playcurl 10.1 to get it to pass Device Integrity?
[Magisk] Victor27587:
I downloaded the pif version but I don't know where to get the 10.1 playcurl. Let me know if you find it please.
[Magisk] changhuapeng:
Try replacing the parts of the script that has:

/data/adb/magisk/busybox and /data/adb/magisk/magiskboot

with:

/data/adb/ksu/bin/busybox and /data/adb/ksu/bin/magiskboot
[Magisk] birdr:
Yes, this made the script run. Thank you!

Unfortunately on running I get "No offsets with UTS format found for '4.14.344-Bool-X' " so the reason i am not passing device integrity may not be the kernel...
[Magisk] sawdoctor:
If you read through the last couple of pages I'm pretty sure no one has it working on cdroid, pretty much every custom rom is failing so Google are probably adding extra checks like when some kernels were banned. Give it time and the community will find what the extra checks are
[Magisk] osm0sis:
If we knew that for certain we'd have it working. We've tried spoofing almost a full device's Build class fields and matching properties, but it made no difference. The one we can't spoof without things breaking (hung boot) is SDK, so maybe that's the ultimate check for what's real, or could be other things, for example Pixel VPN works fine on unrooted/locked devices, but only works on unlocked/rooted devices if you are also paying for Google One, even with anything imaginably related on Shamiko's list, so clearly they've got a bootloader/root check we haven't found/worked around yet.

I'll check that one, show me the full `uname -r` ?

What ROM? They all seem ROM related, specifically crDroid and EvoX so far. `uname -r` ?

@joeyhuab, any changes to the way /system_ext/app/PifPrebuilt works lately? crDroid is just direct framework-level spoof IIRC, so that's different but you're both affected, so yeah could also just be more kernel or prop checks. I know they've been looking at (though not enforcing previously) persist.sys.pif, persist.sys.pixelprops.games and ro.superior.device for example. crDroid was previously on the kernel string ban list but not EvoX, do you still have something identifiable in your `uname -r` ? I've got EvoX and crDroid on a couple of test devices in my drawer, I'll see if I can reproduce the issue.

Is that the actual `uname -r` for your device? I'll check it.
[Magisk] birdr:
Thanks. 'uname -r' gives

4.14.344-Bool-X-

When I look in KernelSU it shows the same, albeit there is a flag after the X- (though I'm not sure this is relevant...)
[Magisk] ohap:
I would guess GitHub . But if not there you have to ask the dev as I can't host it it's his file
[Magisk] ohap:
I keep hearing the new one works tho 15.9.9 but I'm not going to try it as I updated to 15.9.8 last time and it only lasted a few days lol . Which I assume 15.9.9 will only last a few days also
[Magisk] joeyhuab:
Our last changes (on the latest source) included adding RELEASE and INCREMENTAL values and re-arranging the arrays to match the values used in chiteroman's module.

Pif: Support RELEASE & INCREMENTAL · Evolution-XYZ/packages_apps_Pif@91c6805

Match array order with https://github.com/chiteroman/PlayIntegrityFix Signed-off-by: AnierinB <anierin@evolution-x.org>

github.com

PixelPropsUtils: spoofBuildGms: Support RELEASE & INCREMENTAL · Evolution-XYZ/frameworks_base@e66e450

Remove useless logging. Stop enforcing DEVICE_INITIAL_SDK_INT value range. Match array order with https://github.com/chiteroman/PlayIntegrityFix Signed-off-by: AnierinB <anierin@evolution-x.org...

github.com

I also made some changes to AndroidKeyStoreApi file to match the one in PIF module as well.

PixelPropsUtils: Clean up and update · Evolution-XYZ/frameworks_base@1ebdfc6

Co-authored-by: chiteroman <98092901+chiteroman@users.noreply.github.com>

github.com

Let me know what else can be done. I've tested these changes on my POCO F5 and unfortunately, it still only passes basic. I use a GKI kernel and KernelSU and the only kernel string included is `gki`.
[Magisk] osm0sis:
To be fair, my module has remained much more stable, so I'd encourage you to look at my fork of the code instead. Did you try removing the pixelprops persist props?

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] bdr127:
To add to the complication of all of this.....

I use my Pixel 6 on Google Fi (Google's wireless service; T-Mobile MVNO). Starting at around the time of the Clark print ban yesterday, I stopped being able to receive phone calls. When I used a landline to try calling myself, there wasn't even a ring.... just voicemail. Everyone's calls were going straight to voicemail.

I had disabled RCS in Messages settings, but I'm not quite sure about regular SMS text messages.... I was still able to send and receive most, but there were a couple people that said I didn't respond to a text message (that I obviously didn't receive.) So it seems perhaps it was intermittent or spotty?

After trying a simple reboot of the phone, when I got back into the OS, I got a notification that "Google Fi not fully activated." When I tapped it and then selected my account, it attempted to activate but then said "Your SIM card can't be read." (FWIW, I use the e-SIM.) Meanwhile, I got a pop up message that the Messages app crashed ("Messages has stopped [Wait for app/Close]). During all of this time, I had a good 5G connection that I was able to use successfully (manually disabled wifi to test).

After a couple regular reboots that just resulted in the same issues, I rebooted into Safe Mode. No notifications about not being activated or Messages crashing (although I realize now that I forgot to test a phone call from a landline). I booted back into the normal system and now there were no activation notifications or Messages crashing, but I still apparently couldn't receive phone calls. My wife successfully texted me, so I guess that at least worked somewhat.

It wasn't until I updated PIFork with the new print this morning that I could receive phone calls again. And it was literally like flipping a switch -- tested immediately before the new print, call from landline goes directly to voicemail with no ring; tested immediately after the new print, call from landline rings my phone normally.

If Google is not only messing with the ability for certain apps to function, but they're really also messing with my cell service and being to receive phone calls...... then that's crazy and messed up.
[Magisk] Nergal di Cuthah:
Ok, i read everything posted last night/today

Missed how people are getting sailfish print on Osm0sis fork. I assume not getting it via xiaomi.eu in pixel flasher.
[Magisk] kornball:
Use his autopif.sh to generate the sailfish json and then copy the new custom.pif.json into the proper directory
[Magisk] Nergal di Cuthah:
Thanks, to note i tried xiaomi button in pf and got sailfish, so they updated theirs too
[Magisk] D€INOS:
This works to get Wallet not complaining on the device requirements
[Magisk] zgfg:
If it is All-IP, then it doesn't matter WiFi or 5G.

And All-IP can really include telephony, not just messaging/RCS

Hence not only RCS, but you got calls affected to
[Magisk] wilsonhlacerda:
So it seems you are in US. Think about if you were in a dangerous situation and needed to call 911 during those days, besides all other potential loss because calls/messages were not available to you. Google/authorities may be informed about that.
[Magisk] ThePrinceofBirds:
v15.9.9 worked for me on stock pixel 7. RCS is back and working. Wallet hasn't popped an error but I haven't tried to use it yet.
[Magisk] aimless0079:
That caught me out. On Poco F3 Lineage 21, used banking app this morning to check wages, about 7pm GMT I went in shop to get milk and couldn't pay as wallet freaked. Updated, rebooted and working again. Found it hilarious I couldn't even buy milk, lucky it wasn't a big shop. Don't like carrying bank cards.
[Magisk] immortalwon:
I hope someone finds a way around this new droidguard check soon for us custom rom users >.>
[Magisk] casouzaj:
Not all custom ROMs, neither all devices are in this basket! My Xperia 1 II runs LineageOS 21 (A14), and it passes the device integrity test with the Sailfish FP.
[Magisk] Eula13:
can't seem to pass device with the new public print with pifork on lineage os gsi (magisk), tried having only pif installed to no avail
[Magisk] ionut310:
Who's running the show at Google?

These are grounds for a lawsuit.

Google DOES NOT OWN the phone.

Google can not restrict the basic functionality of a phone: calling and text messaging.

This can be extremely dangerous in an emergency.
[Magisk] 4sz0m:
Once your bootloader is unlocked, I guess they're legally out of the picture.
[Magisk] papasso:
Hi @osm0sis, I tried running autopif.sh in Termux, but it exits with the error "need root permission". I think the problem lies in the third line:

if [ "$USER" != "root" -o "$(whoami 2>/dev/null)" != "root" ]; then

In Termux, the $USER variable is not set, so the entire condition is met after the first check. I think the operator should be "-a", not "-o".
[Magisk] joeyhuab:
Currently making a build for now with pixelprops mentions replaced. Temporary of course. Will provide an update if successful.
[Magisk] FIERA03:
Unlocking Bootloader means leaving the device's warranty (e.g., not accepting repairs if the device is broken and cannot be fixed ourself), but that is no reason at all to enable artificially interfere with basic Phone and SMS functionality.

ionut310 is right, the situation is life-threatening depending on the circumstances. If there is an explicit basis, users are likely to prevail in court.
[Magisk] Lobod:
@osm0sis Tried modules and pixel pif on multiple devices. 2 devices with openela kernels can't pass, and 2 devices with different kernels passed.
[Magisk] _VictoR_:
@chiteroman Hello! You asked in telegram about non-working configurations. I know one for sure: it's impossible to pass device integrity when I enforce denylist in Zygisk Next in KernelSU. Everything was working before couple of PIF versions. I needed that option, because shamiko isn't enough for me (I tested), but I had to disable it for device integrity.
[Magisk] stanley321:
I could have never guessed sailfish has a working print, I have the real phone sitting in front of me all the time :ROFLMAO:
[Magisk] 4sz0m:
Depends, but you'd need the best lawyers. Blocking incoming calls and messages would hardly be considered life-threatening anyways. Have not read, but I'm sure their LoL and ToS fully protect their asses in most jurisdictions.
[Magisk] osm0sis:
No... You just need to run it as root. You type su first to get to a root prompt... 🙄

People out here trying to edit my scripts before following the instructions the script gives them. 🤦‍♂️

`uname -r` output on the non-working ones?
[Magisk] Lobod:
4.14.340-openela-perf-g7642b51d0c32-dirty

and

4.14.344-openela-VantomKernel
[Magisk] papasso:
OK, I ran 'sudo su -', just like on linux. 'su' did the job, thanks ;)

But I think my remark on the contidion is valid. After logging in with 'sudo su -' the environment is very minimal, but 'whoami' returns 'root', so the script should run.
[Magisk] osm0sis:
Sounds like -openela is now banned, but I'll check later to confirm. 👍
[Magisk] EfthimisVl:
Am I doing something wrong? Currently on the latest osm0sis fork, using autopif.sh to generate custom json and then move it into playintegrityfix folder but I'm not getting meets_device. Any ideas? I'm on PixelOS on 11 Lite 5G NE.
[Magisk] osm0sis:
Might be another affected ROM along with EvoX and crDroid.
[Magisk] osm0sis:
You just type su and you'll have a proper root prompt from your root solution.
[Magisk] Vision:
You mean, we write the keybox in keybox.java and the info of our device in Android.java in the section say about this ? And can pass ?
[Magisk] joeyhuab:
Possible this is banned too?
[Magisk] papasso:
4.14.343-openela-perf-g13a75317e4f4

It's working for me (vayu/LineageOS 20).
[Magisk] Vision:
Useful Info.

View attachment 6105885View attachment 6105886