yashsingh1/xdaforums huggingface dataset:
[Magisk] intel_core_i7:
So YouTube (in this case ReVanced) playback requires passing PI to work? Can anyone test this out?

I find this very hard to believe, because there are some comments saying it works flawlessly with failing PI DEVICE/SN CTS. I currently have no bootloader unlocked device on hand to check.

Post image just in case it got removed, but seemingly unlikely because it was verified by the head developer. Still I think it's because of something else, not because of PI.
[Magisk] fbirraque:
No worries the Revanced still working flawlessly
[Magisk] intel_core_i7:
Thanks. I don't know why the developers decided to spread false information, definitely not april fools given the uploaded date.
[Magisk] xSnowLeopardx:
V15.9.1 still treating me well :)
[Magisk] wfred:
Same here. The 8.0.1.3 update from last week. The update wouldn't open until I put BBC in the deny list
[Magisk] sawdoctor:
Weird no issues at all here, not added on the deny list
[Magisk] tom1807:
Interesting, yours is v.8.1.05995 bbc.mobile.news.uk, while me and @wfred use v.8.0.1.3 bbc.mobile.news.ww (worldwide).

Was not aware that there are 2 editions, so I assume, the worldwide app is only affected.

Cheers

Tom
[Magisk] wfred:
As @tom1807 said

The latest BBC will install, but when you try to open it you get the below message.

Add it to the Denylist and there are no issues

View attachment 6089088
[Magisk] Neisim:
Hey folks! I've been reading about this module for a while now, but I'm still having some doubts: does this module work by itself? I've seen this fork and what I've understood is that they are complementary (being PIF the main one). Is that correct? How should I proceed: should I go with PIF only? PIF + playcurl module?

I've tried to get answers to this questions before asking, but unfortunately I wasn't able to solve them. Thanks!
[Magisk] Vision:
Please read again carefully, and read and this excellent guide by @osm0sis is explain everything about 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] sawdoctor:
I switched to the beta version to see if that was the version affected (before your post) but had no issues with either stable or beta

(Sorry for the ot please feel free to pm me if you want to check anything else)
[Magisk] 2eno:
Hello,

thank you for everything you're doing for the scene!

I'm currently on the Pixel 8 Pro, running GarpheneOS (I know it's not officially supported from theirs side, still trying tho) with a self built patched kernel (kernel su).

I'm currently passing

BASIC_INTEGRITY

and wonder whether it's the kernel string or something else (probably GrapheneOS related). my

uname -r

return is:

5.15.148-android14-11-g147888816c8e-dirty

and (KSU comoatible modified)TheFreeman193's

kr_offset.sh

script returns:

...

Unpacking boot image 'boot.img'...

Looking for instances of '5.15.148-android14-11-g147888816c8e-dirty' in 'kernel'...
Checking match at offset 26208112... kr_offset.sh: 83: [: 2f6c69622f6669726d776172652f757064617465732f352e31352e3134382d616e64726f696431342d31312d673134373838383831366338652d64697274790064: unexpected operator
Partial match/not UTS
Checking match at offset 26728439... kr_offset.sh: 83: [: 352e31352e3134382d616e64726f696431342d31312d673134373838383831366338652d6469727479006e665f636f6e6e747261636b5f7463705f74696d656f75: unexpected operator
Partial match/not UTS
Checking match at offset 26838243... kr_offset.sh: 83: [: 2f6c69622f6669726d776172652f352e31352e3134382d616e64726f696431342d31312d673134373838383831366338652d646972747900496e76616c69642072: unexpected operator
Partial match/not UTS
Checking match at offset 27082496... kr_offset.sh: 83: [: 352e31352e3134382d616e64726f696431342d31312d673134373838383831366338652d646972747920534d5020707265656d7074206d6f645f756e6c6f616420: unexpected operator
Partial match/not UTS
Checking match at offset 29095192... kr_offset.sh: 83: [: 4c696e75782076657273696f6e20352e31352e3134382d616e64726f696431342d31312d673134373838383831366338652d646972747920286275696c642d7573: unexpected operator
Partial match/not UTS
Checking match at offset 40578274... kr_offset.sh: 83: [: 352e31352e3134382d616e64726f696431342d31312d673134373838383831366338652d6469727479000000000000000000000000000000000000000000000000: unexpected operator
Partial match/not UTS

No offsets with UTS format found for '5.15.148-android14-11-g147888816c8e-dirty'

Thank you for any help!
[Magisk] osm0sis:
There are no banned strings in that kernel. So that's not why you're failing DEVICE.
[Magisk] chiteroman:
Commit all the changes or cherry-pick this: https://github.com/chiteroman/kernel_vayu/commit/a10ff86a4a15f3968dbf2635934aba6f3b4cb66a
[Magisk] osm0sis:
I've checked dirty and Dirty before, they're not banned.

Edit: @Umgak also confirmed:

🔧 [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] jurluk:
After a long time I'm finally passing BASIC and DEVICE integrity 🤩
[Magisk] trevtdogg:
might be a silly question, but are you actually running a PIF module or some sort of fingerprint spoofer?
[Magisk] 2eno:
Well, I'm only passing BASIC, not DEVICE.

I'm running KernelSU, currently with chiteromans PIF and playcurl, but I already tried some different setups with osm0sis' PIF, shamiko and lots of different fingerprints, but even the Xiaomi.EU app project FP isn't working.

I think I'm passing BASIC even without any module tho. Just DEVICE doesn't seem to work.

It's probably something GrapheneOS related. PIF is only spoofing to com.google.android.gms.unstable if I got it right. GrapheneOS is using it's own sandboxed version of PlayServices with a compatibility layer called app.grapheneos.gmscompat .

I have hoped that it's only the kernel string, why I'm failing DEVICE. Now I doubt it will ever work, at least without modifying PIF or GrapheneOS on my own :/
[Magisk] xcl1pse:
So your running grapheneos with kernelsu? Can you send screenshots on kernelsu module page?
[Magisk] 2eno:
Sure:

View attachment 6089485View attachment 6089486

I just switched back to osm0sis' PIF ,hoping to get logs. Before

su -c logcat -d | grep PIF

didn't return anything. I'm going to try again now.
[Magisk] xcl1pse:
Can you open ZygiskNext webui and send screenshot? Just tap open beside uninstall button
[Magisk] 2eno:
View attachment 6089492

Should I enable "Enforce Denylist"? I think this option just came new with the last update.
[Magisk] xcl1pse:
I suspect earlier ZygiskNext isn't working for you since your using grapheneos. Graphene already modified zygote to fulfill their "security" feature, so zygisk isn't working, either on magisk or kernelsu, even "we" refuse to support them. But I don't have time to see graphene latest source if their modification is continue in latest android or not. The only option for graphene user is using kitsune magisk

Enforce denylist = unmount zygisk module on any app that don't explicitly specify their unmount. Don't activate it if you don't know your usage + enable that option with global unmount in kernelsu
[Magisk] 2eno:
Thank you for your help. For me it looks like zygisk is working... There was an update for Zygisk-Next only yesterday, that's why I used an older version before lol.

I tried with kitsune-mask two weeks ago, with no luck. But now that I'm again a bit deeper into everything, I might try again.

Why do you think Zygisk-Next will work on grapheneos with kitsune but not with magisk and kernelsu?
[Magisk] xcl1pse:
Ok I just see VoltageOS since it's has the same sandboxed gapps features like GrapheneOS but have pif prebuilt like EvoX and it cannot pass play integrity due to limitation. So yea you never pass play integrity with sandboxed gapps.

For kitsune question, I already tell that official magisk even contributor won't support Graphene (also applied in ZygiskNext) unless their implementation also applied in AOSP or contributor change their mind. Kitsune magisk have modified zygisk to support Graphene so it will work
[Magisk] 2eno:
Thank you for clarifying. I guess I will switch OS then. No need for working zygisk with kitsune if the only zygisk module I use is PIF which will still not work due to sandboxed PlayServices.

Might be off topic, but any suggestions on which supported ROM to use with Pixel 8 Pro?
[Magisk] xcl1pse:
stock always best for compatibility, using custom rom is based
[Magisk] Nergal di Cuthah:
That settles it, TJW rocks a griffin. Pour stock investment in Motorola
[Magisk] pndwal:
+ @2eno,

Re working PIF w/ Graphine

While the original Kitsune fix (which official Magisk doesn't/won't build), Zygisk: Support GrapheneOS Android 14, is still maintained, apparently Kitsune Zygisk is currently broken again in for late QPR2 based GrapheneOS Pixel builds so it still won't work yet due to Google changes (added a boolean ("Z") parameter "mount_sysprop_overrides" to forkAndSpecialize ("fas") and specializeAppProcess ("spec"))... The prior GOS patch needs modifying to accommodate QPR2 change... Official Magisk already builds a fix for this QPR2 change... This comment:

https://github.com/HuskyDG/magisk-files/issues/129#issuecomment-2007962590

The commenter has since made a Kitsune build that seems to be working however:

https://github.com/HuskyDG/magisk-files/issues/129#issuecomment-2008071465

and opened PR for official fix:

Zygist: Support GrapheneOS Android 14 QPR2

#5 opened 3 weeks ago by lbdroid

FWIW, Graphine Devs seem inclined to support Key Attestation by encouraging (and hoping (wishfully?) for) banks to support OS by whitelisting keys for B/L "verified" Yellow (Google just call Yellow "Selfsigned") state and their OS signing, but not to spoof for Google device integrity APIs which they view as a "very weak approach"... See this:

www.reddit.com/r/GrapheneOS/comments/zx9mwi/comment/j1znlq7/?utm_source=share&utm_medium=web2x&context=3

More here:

https://grapheneos.org/usage#banking-apps

Not spoofing natively is probably a good thing as far as PIF module use is concerned however.

🤠 PW
[Magisk] raph_dev:
Hello,

I need help, I didn't find the same problem in this long topic. Here is my situation:

I flashed my Fairphone 4 from /e/ to LineageOS for microG. I understand that we cannot relock the bootloader with this king of custom ROM, consequently one of my banking app (only on mobiles) fail to open with the message "Please install from GooglePlay".

So I:

- installed Magisk

- enabled Zygisk

- add my banking app into the DenyList

- installed the module: Play Integrity Fork v8 by @osm0sis & @chiteroman

- tried to generate and update the pif.json with the PIF manager of PixelFlasher

But I face a problem, the Play Integrity Check apps (all listed on the PixelFlasher) cannot do the verification. Not because the rate limit but I got this message: "Binding to the service in the Play Store has failed. This can be due to having an old Play Store version installed on the device."

I don't have the Google Play Store, but Aurora Store (the latest version, v4.4.3), I don't have the possibility to install Google Play Store.

What can I do? Should I need to try with ZygiskNext another kernel? Should I need to add another modules to Magisk (this is the only one)?

Thank in advance!
[Magisk] 2eno:
Can confirm that Zygisk is working with the modified Kitsune app. Still not passing DEVICE_INTEGRITY tho'.

As I said before: I think Zygisk was working with KSU on GOS too.

I'm not sure if DEVICE_INTEGRITY fails because of banned/wrong fingerprint, or as @xcl1pse said: because of sandboxed PlayServices.

When I have time, I will revert to stock and try to find a working fingerprint. Then maybe go back to GOS to assure its not the fingerprint causing the failing of DEVICE_INTEGRITY.
[Magisk] V0latyle:
Play Integrity is integrated into Google Play Services, so if you're using a cut down version like MicroG, it may not work properly.
[Magisk] raph_dev:
So what I should do? Is there an alternative to microG? Or should I go back to a LineageOS ROM without microG?
[Magisk] RAVINTER:
Hi, can anybody help? Im fighting with that maybe 11 hours and still not find solution. I can't pass CTS profile match, im trying this module, Universal safety net fix, universal safety net fix mod and nothing works. Im read this thread and im find that some custom roms banned, im trying find in HxD string Lineage or something like that and no results, im not good at this so maybe im missing something? Phone - Lenovo p2a42 Lineage OS 18.1 Android 11.
[Magisk] CZ.Kostra:
Run this command in the terminal: uname -r

Compare the result with this list of banned kernels:

🔧 [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] Ginosius:
Thx bro!

V12 saved the day!
[Magisk] zgfg:
Unfortunately, with this new nodule now failing all three and Yasnac fails too

Strange, logcat works fine but

logcat | grep SNFix

gives nothing

Xiaomi.eu MIUI 14.0.12, Magisk 26401

Without the nodule, Yasnac was Ok and Basic was green
[Magisk] Serinor:
Thank you for your quick response and overall hard work. As a token of gratitude I've made a donation. You saved the day! To everyone else reading this, please consider donating as well as it definitely helps support development.
[Magisk] watoan:
Hi everyone, I am new to here.

I have been using Magisk 26401 + USNF v2.4.0-MOD_2.0 (modded by Displax)

Until an hour ago, I found Google Pay not working when I tried to pay in store

then I noticed MEETS_DEVICE_INTEGRITY shows in red

I did searching and finally found "Play Integrity Fix", now I see the hope and I appreciate your work

so I have uninstalled the module USNF v2.4.0-MOD_2.0 manually, rebooted

then installed Play Integrity Fix v12, then reboot again

now I can see MEETS_DEVICE_INTEGRITY and MEETS_BASIC_INTEGRITY both in green

However, in Google Wallet it is still showing "Your phone doesn't meet security requirements"

I am wondering if any steps I missed? or any further action needed after I install Play Integrity Fix?

Please advise, many thanks!
[Magisk] pershoot:
This will take ~24 hours to clear.
[Magisk] Nergal di Cuthah:
Likely and sadly you need to clear wallet's data or maybe not see the poster ahead of me
[Magisk] pershoot:
Thank you. Looks good.

I needed to re-install PIxelXPERT (AOSPMods), thereafter as there appeared to be some issue (hanging lockscreen / home, etc. (I use double tap to wake / sleep)). I reinstalled all modules fresh (lsposed, shamiko, pixelxpert and this one) as a precautionary measure.
[Magisk] SuperMaximus:
@chiteroman

Thanks for the V12:

Integrity Checker shows MEETS_DEVICE_INTEGRITY & MEETS_BASIC_INTEGRITY ticks, however, YASNAC shows Basic Integrity - Fail & CTS profile Match Fail. Should we care?
[Magisk] chiteroman:
Xiaomi.eu roms have an unknown fix for me ("strange rom"), sorry but their developers must inbuild the fix into the rom, remove it or use the standard fix (modifying framework.jar).

Sorry but I can't do nothing :(
[Magisk] watoan:
Thanks for your reply @pershoot

Does it mean I can ignore that and use Google Pay as usual within the coming ~24 hours?

Thanks
[Magisk] chiteroman:
Clear data and cache of:

- Wallet

- Play Store

- GMS

- GSF

Reboot and voilà!
[Magisk] devilsshadow:
Found this by accident while looking for updated info on USNF since i recently updated to A14 and my wallet was borked in the process (rooted P6 with magisk). Only found out about this mod from a random reddit comment. Thanks @chiteroman for the awesome work! Looks like our rooted phones will still be able to use payment services for the foreseeable future!
[Magisk] zgfg:
Sorry, btw, didn't you have Xiaomi.eu yourself some time ago

Also, did you remove SNFix from the logcat now or that's specific to my ROM (previously, if I used your ROM, I always had SNFix in the logcat)

Edit: On my older Xiaomi.eu (MIUI 12.5) new module works fine and there is also no logcat SNFix so I guess it is disabled now
[Magisk] Catarsi:
I installed the module and uninstalled USNF. Before this YASNAC was passing but now it fails, along with the Play Integrity check.

My phone is a Mi10 with MIUI (Xiaomi.eu) 14.0.4.0 and Magist 26400.

Is there something extra I should be adding to the DenyList or... Can anyone give me a hand?
[Magisk] pershoot:
Google Pay (tap to pay) may not work, until that occurs. You can check back by tomorrow and it 'should' have flipped back to healthy status.
[Magisk] ZG_DEV:
Great module, it is the #1 in my magisk modules list !

Thanks for your great work!
[Magisk] devilsshadow:
What's GMS and GMA? Google messaging service? What about GMA? :ROFLMAO:
[Magisk] MrLumin:
GMS - Google Mobile Services (or just basically the Google Play Services app)
[Magisk] zgfg:
See the posts #1432 (me) and #1439 (devs answer) above
[Magisk] chiteroman:
Sorry, I thought it was GMA but it's GSF 😂. (com.google.android.gsf)
[Magisk] V0latyle:
Yes, use a GApps suite such as NikGapps, MindtheGapps, etc.

See https://wiki.lineageos.org/gapps/
[Magisk] RAVINTER:
Thanks for reply, i got this: uname -r 3.18.140-lineageos-ge9eebafea158
[Magisk] raph_dev:
Yes I see, but it not guaranteed me that the play integrity check would work for my banking app with an unlocked bootloader.
[Magisk] V0latyle:
The best you can do is work on passing DEVICE and go from there.

Or, if you need a guarantee that your banking app will work, reflash to stock and lock your bootloader.
[Magisk] zgfg:
But there is almost guarantee that if you don't pass Device i Integrity, that then your banking app would not work

See above the logical and mathematical difference between necessity and sufficiency.

Ie, IF above is not the matheIFF = If and only If

Or, in the IETF RFC (de-facto, funding specifications for the public Internet protocols) jargon, it SHALL read as You SHOULD first assure to pass Device Integrity
[Magisk] sga999:
I patched mine a couple of months ago, so it's vague in my memory, but I think I created it successfully for you. I changed it to l18eageos, not that you need to know that. In the future, you can search recent pages to find where there are scripts to help you.

But I did it another way which is also mentioned somewhere in this thread. I used Magiskboot unpack, HxD to search for and change the string, Magiskboot repack. I think this way is simpler for me, but the scripts are certainly helpful.
[Magisk] RAVINTER:
Thank you very much for your help. Yes i see something about scripts but being honest im not know how use them :/ Can you take screenshot of this string wchich you change? I want learn for future where this string is, so maybe then i can do it myself. Thanks :)
[Magisk] pndwal:
I believe microG users can achieve DEVICE_INTEGRITY though... May need to configure denylist to hide root from 'microG Services Core', enable 'Device Registration' and 'SafetyNet' in microG settings etc... and there's a 'FakeStore' option (I know nothing about 😉)... PW
[Magisk] sga999:
I hope it did actually work for you, but maybe you didn't try yet? Anyway, here's a screenshot from laptop where I did the HxD search and replace.
[Magisk] RAVINTER:
Thats what im think... Im use HxD on laptop with windows 7 and open in HxD Boot.img or unpack with CarlivImageKitchen and in Hxd i don"t even have this strings... Tommorow i will try on laptop with windows 11. But you help me, now im think i can do it myself, if you have revolut pm me with your @Revtag or number i send you 2$ for help.
[Magisk] chiteroman:
Unpack using magiskboot and open "kernel" in HxD. Then repack using same tool. You can get it from Magisk app, if you have Magisk installed it should be in PATH.
[Magisk] RAVINTER:
Yes im already know that, sga999 helped me understand this.
[Magisk] sga999:
You still didn't say whether it helped you to pass. I'm curious to know if it did work.

You're very welcome. But no need to send me anything. I was glad to help. But I do hope you will be able to do it yourself in the future.
[Magisk] pndwal:
Hi @nico2195x...

If you're still around, please can you say how you configured LOS/microG, and confirm that Play Integrity DEVICE_INTEGRITY was achieved?... For @raph_dev...

Aside: I assume USNF_mod module still worked for you (for UberDriver etc) because OP8T has broken keymaster implementation ("broken TEE") so doesn't need Zygisk spoofs anyway... Ta! 🙂 PW
[Magisk] ashish1989:
Guys in my J7 Prime with A9, I am using playintegrityfix by chiteroman and playcurl zip by daboynb. Is it compulsory to add gms and gms.unstable processes of play services in denylist. Because when I am enabling them they are disabled by fp_downloader and I have to enable them again manually.

Can not pass device_integrity too🥲🥲
[Magisk] raph_dev:
Yes, that's what I've done, now I'm on a pretty google phone 🤡

Yes, that's was my priority in the short term (my sentence was not logical ;)).

I found a good discussions here: https://github.com/kdrag0n/safetynet-fix/discussions/145

It motivate me to get out of (direct or indirect) Google apps, fully switch to open source apps and then go back to LineageOS without microG. For me, it will be the easiest way to fight against Google. 🤕

Anyway thank for your help and all great tools developped here!
[Magisk] RAVINTER:
Ok im now done everything, your modified boot.img + patched with Kitsune + Play Integrity Fix v15.9.7 👍👍😁
[Magisk] Partyzanin:
Had troubles with basic Magisk/Zygisk install, but after that everything works (LinageOS 21/Pixel 3 XL).
[Magisk] mkcs:
Are there any methods to pass device integrity after the mass ban wave in Feb? I cannot find any vaild fingerprints
[Magisk] bondik77:
https://raw.githubusercontent.com/daboynb/autojson/main/pif.json
[Magisk] Captain_Throwback:
Use the Xiaomi.eu print like almost everyone else.

(see previous post)
[Magisk] majorfigjam:
There are a small number of working prints. However, if the generic xiaomi print does not work for you, chances are you have a banned kernel or other conflicting modules.

Without more information about your set up, we will not be able to assist.
[Magisk] tom1807:
After 44 days the Xiaomi.eu print is still working. Did the guys find the holy grail fingerprint of fingerprints?

[Offtopic] Is it only me who checks every day whether the mobile still passes Device_integrity? 😆 [/offtopic]

Cheers

Tom
[Magisk] osm0sis:
I'd say they're not done messing with us yet, as the last 3 months has shown. We'll have to see what the end of April has in store for us...

Perhaps another RCS experiment at least... 😐
[Magisk] freeza:
Does both wallet and rcs still work with xiaomi.eu print?
[Magisk] MrSteelX:
So far yes.
[Magisk] majorfigjam:
Yes, but only if you have Device Integrity with that print.

If you don't have Device Integrity - for example due to banned kernel string or other conflicting modules - then both RCS and Wallet are likely to fail.
[Magisk] ashish1989:
Plz help me to pass device integrity on my A9 Samsung J7 Prime. Using official magisk 27.0 and official playintegrityfix module by chiteroman, playcurl zip by daboynb, shamiko and Zygisk Lsposed.

I don't know what I am doing wrong but can't pass device integrity, can pass only basic integrity.

Cleared play store and play services data many times, renamed magisk to different package name and running fp_downloader apk provides same result. Only basic integrity can pass.
[Magisk] NIKOST:
Is anyone else facing issue with setting up a new card with the latest version? I am getting errors when setting up a new credit card. And my pixel 7p passes device integrity. Any help appreciated
[Magisk] majorfigjam:
What does wallet report under the Pay Contactless Setup check?