yashsingh1/xdaforums huggingface dataset:
[Magisk] halfbytecode:
You can create an empty file named disable in /data/adb/{module_name}/ folder to disable a specific module, from within TWRP. Else you can backup the module folder before deleting.
[Magisk] sga999:
Your post mentions Chit's way of logging, but I don't know what his parameter name is. I guess I can try verboseLogs, but it sounds like you are saying his is different. Maybe it's just Debug without any number?

🔧 [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

EDIT: Oh, I see "DEBUG": false in the default file, so I assume I can just change that to true.
[Magisk] sga999:
EDIT: It took more than a minute to start displaying. But maybe it's okay.
[Magisk] Mitezuss:
Is

dnt work for me too

only pass Device with beta fp on rom with testkey

maybe will be better get the hex signature code from a file/config like others values
[Magisk] Zytrel:
Could you please give more info about your config (device, rom, magisk/modules, etc.), maybe we can nail down common issues.

Regards,

Zy.
[Magisk] fbirraque:
Play Integrity Fix v16.8 available on GitHub.

(*) Just sharing, I didn't test it.

Release v16.8 · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] osm0sis:
Got someone to pretty much confirm the new signature spoofing code is the cause of the bootloops: https://github.com/chiteroman/PlayIntegrityFix/issues/380#issuecomment-2242882415

That only undoes the script updates that chit wrongly blamed for the bootloop, where it's almost certainly the signature spoof code.
[Magisk] Zytrel:
@osm0sis The bootloop issue is not really related, but just fyi, I did the sailfish tests with my private key build with your PIFork as I wasn't sure if Chit's version would always try to spoof, even if the build had releasekeys. ;)
[Magisk] tazlooney89:
I updated the module to its latest version, but now the phone is in bootloop, it is a moto g7 plus with pixelexperience android 13 rom, any solution without having to do a factory reset.
[Magisk] Vision:
If you have Recovery (TWRP etc) you can deleted from there and phone boot normal again.
[Magisk] SchmilK:
Well I had RCS for about an hour today....then it got blacklisted.
[Magisk] Pixel86:
No issues here on PIF 16.6.
[Magisk] casouzaj:
Neither here. Xperia 1 II, running LineageOS 21 with KSU, keeps exchanging RCS messages with an older Moto G4 Play, running LineageOS 18.1 with Kitsune Mask. It was fine with v16.7 and keeps so with v16.8.
[Magisk] pndwal:
But all of this occurred after Google added hardware key backed attestation (HKA) for integrity verdicts!... The original essential method never changed!

Also, prop/field spoofing was not needed because of the move to HKA; it became necessary (as an addition) much later, and only when Google began 'enforcing' HARDWARE_BACKED evaluationType per device (read 'began blacklisting devices for passing BASIC-only evaluated S/N ctsProfileMatch, now PI DEVICE_INTEGRITY, verdicts).

Spoiler content hidden.

I'm not familiar with pixelproputils or pputils, but any normal integrity fix method must employ a hardware key attestation 'block' (just like the original did) in addition to currently needed prop/field spoofs...

Beyond normal, we could find another 'decietful' Google loophole/vulnerability (like the walleye fingerprint that allowed their broken first generation Pixel 2's to pass STRONG using basic attestation measurements for many years) and exploit it (temporary!), or spoof valid (leaked) A8+ keys/certificates (again, likely to be temporary at best)...

Yes... No solution can fully anticipate Google moves...

Yup... That's why I mentioned:

And yup... ROM solutions with no USNF/PIF conflicts have existed for a long time (even before @chiteroman's PIF) as I mentioned.

🤠 PW
[Magisk] Mitezuss:
@osm0sis

hi, are there any guide to compile the PlayIntegrityFix from source (github) ?
[Magisk] Nergal di Cuthah:
Osm0sis is pifork not pifix. They have no compile info for it probably
[Magisk] Radulfr:
Updated pif and now my FP downloader was removed by it for being incompatible?PPlay integrity next by daboynb is there an alternative this is compatible?
[Magisk] Vision:
Just reinstalled playcurl, after updating PIF
[Magisk] osm0sis:
Seems more likely now that it's a recent prop change. Narrowed it down to sys.oem_unlock_allowed or doing all the ro.*.build.tags and ro.*.build.type ones I think.
[Magisk] Sheist!:
With playcurl removed as incompatible, surprised it still passes device and Play certified. Holding off on reinstalling the playcurl module for now. No reboots here.
[Magisk] Radulfr:
I was keeping everything updated on a pretty regular basis checking for updates in magisk every other day and I haven't run into any issues at all. I'm on op12 with OOS 14

Just reinstalled playcurl after updating pif and so far still no issues
[Magisk] CZ.Kostra:
PIFix v16.6+ modules contain FP with which RCS works. 'Playcurl' would download FP which is banned for RCS.
[Magisk] DIXES:
Test results report:

One of my old phones, the Asus Zenfone 3 running stock Android 8.0, can finally pass MEETS_DEVICE_INTEGRITY again using PIF v16.6. Previously, it couldn’t with PIF v16.5.
[Magisk] x_berzerker:
i humbly ask for help mates:

got 16.7 but:

-no meet device integrity yet.

-gmail, keep, and some other google stuff keeps instacrashing.
[Magisk] sawdoctor:
What device, which rom, which modules do you have installed and have you any logs? The information you can share the better chance one of us can help fix your issue
[Magisk] xcl1pse:
11-15 13:42:56.643 16292 16292 D PIF/Native: Starting to hook...
11-15 13:42:56.643 16292 16292 D PIF/Native: Got __system_property_read_callback handle and hooked it at 0x72857a56fc
11-15 13:42:56.643 16292 16292 D PIF/Native: get system classloader
11-15 13:42:56.643 16292 16292 D PIF/Native: create buffer
11-15 13:42:56.644 16292 16292 D PIF/Native: create class loader
11-15 13:42:56.645 16292 16292 D PIF/Native: load class
11-15 13:42:56.646 16292 16292 D PIF/Native: call init
11-15 13:42:56.647 16292 16292 D PIF/Java: Field 'PRODUCT' value is now 'WW_Phone'
11-15 13:42:56.647 16292 16292 D PIF/Java: Field 'DEVICE' value is now 'ASUS_X00HD_4'
11-15 13:42:56.647 16292 16292 D PIF/Java: Field 'MANUFACTURER' value is now 'Asus'
11-15 13:42:56.647 16292 16292 D PIF/Java: Field 'BRAND' value is now 'Asus'
11-15 13:42:56.647 16292 16292 D PIF/Java: Field 'MODEL' value is now 'ASUS_X00HD'
11-15 13:42:56.647 16292 16292 D PIF/Java: Field 'FINGERPRINT' value is now 'asus/WW_Phone/ASUS_X00HD_4:7.1.1/NMF26F/14.2016.1801.372-20180119:user/release-keys'
11-15 13:42:56.648 16292 16292 D PIF/Java: Spoof KeyStoreSpi and Provider done!
[Magisk] stathis95194:
Reporting for 12.4 on xiaomi.eu on Mi 13 Pro. PI passes Basic Integrity but not Device Integrity. GW doesn't register cards
[Magisk] pulpf:
Hi here is my answer to the test, any idea?

I deleted safety net and installed play integrity fix v13.3.

Tel oneplus7 t android 12

Magisk 26401

ThView attachment 6033059anks
[Magisk] nil?:
View attachment 6033060

(from the first post of this thread)
[Magisk] zgfg:
Idea about what? It fully works per your screenshot
[Magisk] nil?:
This is not a thing I'm asking about. I encounter "Zygisk module not loaded due to incompatibility" and I'm looking for something that explain what's wrong with my setup, specifically logs of Magisk module loading, where thay can be grepped by 'playintegrityfix'.
[Magisk] zgfg:
Have you inspected the module's own log lines from logcat - exactly from the module's Zygisk native code?

su -c logcat | grep PIF

In your log it's only about Magisk processing the scripts
[Magisk] nil?:
Of course, I have no logs with the word PIF in logcat because module isn't running. I'm trying to understand where it breaks and this is the reason why I'm asking about logs of Magisk processing the scripts from devices where it works.

I tried uninstall/reinstall Magisk, tried Magisk Delta, as a result currently on the same Magisk version as yesterday (26400) now I can't run not only PIF but LSPosed too.
[Magisk] xcl1pse:
What's your setup? Module you're using? Anyway if you're having an issue with zygisk, upload your dmesg log. Connect your phone to pc/laptop, type command

adb shell su -c dmesg > dmesg.log

Reproduce the issue, then upload dmesg.log in github issues.
[Magisk] nil?:
Looks like I just found the problem, my Magisk installation is full of zeros...

for file in /data/adb/magisk/*; do echo $file; xxd $file | head -3; done
/data/adb/magisk/addon.d.sh
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................
/data/adb/magisk/boot_patch.sh
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................
/data/adb/magisk/busybox
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................

and so on

But I installed Magisk several times this night, including complete uninstall and then patching kernel + installing via the app. WTF this mean?
[Magisk] nil?:
Pfff, yes, it fixed now. Idk how. Since I keep an eye on these files during Magisk reinstall they're not nullified. And I have the subject module working, finally, after 15h of suffer.

P.S. Thank you all for rooting for me. And of course many thanks to the author of this module, it solved the issue.
[Magisk] Mohamedkam000:
Hi. I can't pass CTS, logcat shows nothing related to 'PIF'. Any help, please?

- I'm decrypted.

- Galaxy S20+.
[Magisk] xcl1pse:
Your zygisknext module seems doesn't loaded. Can you try older releases?

Releases · Dr-TSNG/ZygiskNext

Standalone implementation of Zygisk. Contribute to Dr-TSNG/ZygiskNext development by creating an account on GitHub.

github.com
[Magisk] pulpf:
Ok I thought all crosses had to be green
[Magisk] Shubhuuuuu:
Same problem with me

Due to device integrity failing my netflix shows error (-93)

but after installing this module my play store shows that device is certified.

can anyone explain me what's happening, my device is showing certified but the device integrity is failing

Btw if you guys are wondering strong integrity always fails
[Magisk] xSnowLeopardx:
Problems

- Google Wallet was working for some days, but right now, it says my device doesn't meet the security requirements.

- Currently can't install/update/open Revolut (Play Store tells me my device is not compatible with this version).

Installed

PIF:

- tried the newest 12.4 but that one doesn't work and gives me random org.codeaurora.ims.imsapp crashes.

- 12.3 not working for me.

Magisk: 24601 canary

- Magisk Bootloop Protector

- PIF -> well currently on 12.3 again since the crash from above was annoying me

- Shamiko 0.7.4.

- Systemless Hosts

Enforce Denylist is toggled off and is configured with the apps to be hidden.

Google Play-services is not toggled at all, since I don't know if this is needed.

Cleared data+cache of Google Wallet and Play Store between removal of PIF and LSPosed.

Not of GPS and GSF since I got a gms / notification problem because of this and will never do that again lol.

Had LSPosed but with that installed I did not even meet basic or CTS.

Removed LSPosed and met these.

What I want

1) Wallet to work again properly

+

2) Revolut to be opened/installed.

bonus: LSPosed to work as well, but that's a low priority compared to 1 + 2.
[Magisk] Paz9:
Anyone know what's happened?

View attachment 6033483
[Magisk] chenw191:
I also encountered a similar problem, my play integrity check result is random. Have you solved this problem now?
[Magisk] marcopit-92:
This is my setup. You might try check the app in deny list as I did. I have TJW Magisk and everything works correctly. Also I have LSPOSED.
[Magisk] RMD08:
There's someone in the magisk group "he passed strong integrity". but he kept it a secret. does anyone know how? he took the test on November 15th
[Magisk] xcl1pse:
Maybe his rom included this one?

https://github.com/chenxiaolong/avbroot
[Magisk] luqman98:
Yesterday I remember both of my phones did pass "MEETS_DEVICE_INTEGRITY" with PIF 12.3 but today that is not longer the case even with PIF 12.4. Google patched it again?

Xiaomi Redmi Note 11S 5G (picture below):

Stock MIUI 14.0.4.0 TGLEUXM

Magisk Delta 26301

Xiaomi Redmi 7A:

crDroid 9.10 Mi439 latest official build

Magisk Alpha 26401

Shamiko v0.7.4 (189)

And yes, searching for Netflix on Play Store on both devices shows "This app won't work for your device"
[Magisk] zandatsu06:
View attachment 6033564

I checked earlier mine is passing MEETS_DEVICE_INTEGRITY

Now is not passing anymore because i noticed the play store is not certified anymore...I guess google patched it again

I'm using PIF 12.2
[Magisk] liyafe1997:
Me too, today 12.3 and 12.4 both doesn't work, yesterday still able to pass it...

View attachment 6033567
[Magisk] spida_singh:
same here, its either a temp error or Google has ammended something.
[Magisk] Wolfcity:
And the same here too.

TJW Magisk 26.3

PIF 1.23
[Magisk] makeyourself:
And me, it worked fine about 2 hours ago, now it's failing Device Integrity. Fun game this is Google...
[Magisk] oOEDGUYOo:
The same has happened to me
[Magisk] Clasimodo:
Same here
[Magisk] FIERA03:
I think we should refrain from writing props for Device spoofing, as Google is definitely looking here, as well as YouTube's anti-ad blocker.
[Magisk] Samuel Holland:
Wow, nice, I guess I'm late to the party. 🎉👍
[Magisk] immortalwon:
It has been patched again. PIF no longer works 11/16/2023. Failing meets device integrity.
[Magisk] osm0sis:
Well, on to the next fingerprint I suppose!

@chiteroman, any possibility of exposing the spoofed values to userspace (in a prop file somewhere perhaps) so that they can be changed for experimentation without needing a full recompile? This way everyone could find and set their own unique working ones which would be good basically indefinitely.

It might also be smart to establish a pool of sets of working values that get randomly used within the module, so that Google doesn't see 1 million people with the same device all of a sudden spamming their servers with integrity checks, thus keeping it less obvious what the modules are using.
[Magisk] chiteroman:
Even if it does that, in the end, Google is going to ban all fingerprints, it is a war that we already know that sooner or later Google will win. There's nothing to do. I don't know if I should continue maintaining the module, I'm going to try to fix it and make it read a .prop file but I can't promise anything.
[Magisk] EuK_V:
Can confirm, pif isn't working.
[Magisk] FIERA03:
I think there is no way to win over Google is to make it completely closed source like New Twifucker(Developing), and to give it even stronger encryption. But even if we could do that, I don't know if we could win.
[Magisk] chiteroman:
Furthermore, we could say that we have infiltrators here... They were very quick this time...
[Magisk] osm0sis:
They probably just starred your or USNF's repo on GitHub. 😛

No, but honestly having the Play Integrity API Checker app max out its tokens for a week with failures and then suddenly successes again all from the same device are pretty clear indicators of spoofing to read in the data.

I think Google is at least inviting us to be more clever about it. 😘
[Magisk] immortalwon:
Please remove all source codes and keep it closed for longer module sustainability.
[Magisk] osm0sis:
I think making it read a prop or from a pool is a good first step, which could allow the module to remain open source.

Then our working prop files can remain privately available here or Telegram, and/or the pool could be external to the app on a private server so Google would have to do a lot of work to scrape them all.
[Magisk] chiteroman:
Done :D
[Magisk] immortalwon:
Good idea, but may seem like a lot of work? Up to chiteroman
[Magisk] FIERA03:
I have been watching the uBlock Origin filter developer's Tweet and he too said that G is clearly taking aim at uBlock.

The reason they are able to keep fighting to stay open is because their resources (props for us) are not capped, unlike ours.
[Magisk] osm0sis:
I'd say just make the prop code then put the current prop in your .gitignore ...

That way the majority of the module is open, but the values we're using aren't (until the module gets downloaded and inspected anyway).
[Magisk] liyafe1997:
Even you can use some obfuscator for the code, making it harder to be inspected by Google.
[Magisk] immortalwon:
Agreed, in times of universal deceit and totalitarian power, you gotta use every trick in the book.
[Magisk] sawdoctor:
Has anyone looked at the new QPR beta 2? They've added "private space" and " quarantine " features/code. Maybe these could be used to isolate root from banking apps.
[Magisk] Eclipse1991:
So does the xiaomi.eu dev need to update the whole rom to make this fix work again ?
[Magisk] liyafe1997:
From the name of the features you mentioned, I guess it seems just like the muti-user mechanism, just like the Work Profile or switch users feature.
[Magisk] DineshValor:
Similar setup mine but didn't pass from past few days suddenly start failing.

Any update related "Device Integrity fix" ?
[Magisk] osm0sis:
We've just been discussing ideas for it, maybe read.
[Magisk] immortalwon:
I am just surprised people didn't see this coming. It's like watching a fast train on the train tracks and not avoiding it. Everything at this point needs to be closed source and encryption used.

Even the above mentioned may be futile, A.I (artificial intelligence) will be able to crack encryptions and anonymization techniques. But that doesn't mean we bend over backwards and let them win, at least in my book.
[Magisk] HippoMan:
Agreed. The Googlefrinchians seem to be approaching this with the same mind set and fervor that their ancestors the Golgafrinchians had when they decided to try to defoliate most of the world's forests in order to increase the value of the leaves that they were using for currency back then.

Lots of those Golgafrinchians were telephone sanitizers, and today's Googlefrinchians are following this tradition of their ancestors by working hard to sanitize our smartphones.
[Magisk] marcopit-92:
I just uninstalled YASNAC as I remember somebody said would trigger something.. now I don't remember clearly what but maybe that does the trick..

EDIT

mine also lost DEVICE INTEGRITY...
[Magisk] xcl1pse:
I'm guessing private space it'll be like samsung secure folder and quarantine mode like suspending the app since from the leak, the icon still appear in the launcher, just grayed out (pm suspand com.your.app). If that the case, secure folder will still see magisk su (I dont know about kernelsu since kernelsu at this point can't be installed on another user) and for quarantine, just freeze the magisk or use HMA
[Magisk] ai024:
I would politely suggest that good folks who aren't familiar with reading XDA threads, or choose not to, might want to avoid rooting their devices or sharing advice that is based on things they've heard here and there.
[Magisk] MrLumin:
Here we go again :cool:
[Magisk] HippoMan:
But if people do that, we won't get to be entertained by reading posts like the following example ...

I came to this thread now to report that [the module in question] doesn't work. Please fix it.
[Magisk] Qnorsten:
Stupid cat and mouse game. I am lucky I have an unmodifed samsung watch that I can use for contactless payments in the meantime.

I would love the implementation suggested by @osm0sis . That read the parameters from a prop file. Then you can keep the module open source. In worst case scenario you can just stop suplying props at all and just supply the code. Leave it up to the end user to test and find props that they want to use.

I really don't like the idea of closed source modules. I did use shamiko before out of necessity but it felt wrong. Now I have moved to DenylistUnmount as it is good enough for my needs. Luckily none of the bank apps over here care about root surprisingly so it is only needed for contactless payments.
[Magisk] kopap:
Funny part I can't pass play integrity but play store is certified .banking apps work fine
[Magisk] chiteroman:
Making the module closed source is the best chance we have now to avoid Google.

I know there are people who don't like this, myself included. But we have no choice...
[Magisk] liyafe1997:
The play store certified is a cache... If you clear play store's data then you can see it is not certified.
[Magisk] Qnorsten:
I know it can be for the best but I would like you to only do that if needed. Like if you make some major update to what you are patching and how the patches are applied. Making the module closed source won't protect much if it is only for the props.
[Magisk] HippoMan:
Unless the entire method for bypassing integrity checks is changed in the closed-source version, I think that the Googlefrinchians will still be able to defeat the software ... especially given that they (presumably) already have downloaded the source code for the current and recent versions.
[Magisk] trax69:
Removed the cache from services and play store and now it no longer works
[Magisk] osm0sis:
I'll speak a little more plainly... I've literally had conversations with now-Googlers (after they in turn were able to have closed talks with Google's Platform Security team) about how SafetyNet and PlayIntegrity aren't about stamping out the modding community, and the intention isn't to completely stop everyone forever, they're about giving off the appearance of same to the companies who care...

So therefore all they actually do is pick off the low-hanging fruit, like whenever we make things completely obvious, e.g. with all the clear data I already alluded to, pointing to a specific fingerprint for them to block. Using prop files to allow users to experiment, customize and find unique value sets, and provide a randomized/rotating pool of working value sets not stored in the source will probably raise the bar high enough that they'll leave us alone again for a long while. So I'll say it again... they're simply inviting us to be more clever about it. ;)
[Magisk] crok.bic:
Offtopic:

Some of you perhaps remember this website of LineageOS.

Just wondering why can't we simply register the GSF ID here and get at least the device integrity OK with an exemption? Perhaps with a message from Google telling us (and banking apps) that you registered your GSF ID by yourself and "you are on your own" and you are responsible for what you are doing on your device? :| It did work 5+ years ago..
[Magisk] HippoMan:
Sadly, I believe that most devs (including those who work for banks) will completely ignore this info.

And I also believe that the main reason for the Googlefrinchians not offering such a thing now is that they are catering to the banks and others who specifically want to force their security checks on all of us, irrespective of whether we want to take responsibility for our own security.
[Magisk] LucasBS1:
I'm not a programmer or anything, so forgive if the questions below are too noobish or already considered:

Could I just block internet access to Google framework, or the wallet (using AFWall) ?

Or even prevent any of these apps to updating themselves (UpdateLocker xposed module)

What if I roolback to a previous version of google play services ?

My rationale is simple: the wallet doesn't need internet at the moment of payment, right ? So it cannot confirm if the app is up to date.
[Magisk] user_hajime:
Sa

Same ahahaha