yashsingh1/xdaforums huggingface dataset:
[Magisk] osm0sis:
I also literally pointed him to chit's version of it...

PlayIntegrityFix/module/pif.json at main · chiteroman/PlayIntegrityFix

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

github.com
[Magisk] Vision:
I send it before, but Android 8 and older no need the json file to spoof

EDIT: I'm sorry @zgfg, i write wrong, @osm0sis informed me
[Magisk] osm0sis:
No, his would, because he's not on stock ROM, and his custom ROM didn't keep the stock values.
[Magisk] Vision:
Oh yeah, sorry i forgot that part, for that need it to spoof the value of json file to DroidGuard right ?
[Magisk] neonblind:
Classic Xposed always triggered CTS safetynet on every android version it was released. It's well documentated since years and the only way is to uninstall it and delete every trace left (XposedBridge.jar etc.)
[Magisk] neonblind:
OK guys, first of all i want to say i appreciate the work of every developer and good soul in this thread, helping to bypass this sh**y google stuff.

I tested 3 devices:

a) Sony X Compact with stock android 8.0 (shipped android 6)

b) Lenovo Tab with stock android 8.1 (shipped android 7)

c) Lenovo Tab wit stock android 10 (shipped with android 9 or maybe 10 and never got a major update)

at one point, all bypass device intergrity. a) 2-3 months ago (last time i checked), b) until yesterday c) still bypass

a) never make it work with the motorola print

b) until yesterday it worked with the print (magisk delta 26.1, PIF fork)

c) classic magisk 26.1 , shamiko 0.73, PIF fork with the well known print

as for a) and b) on both devices play store is certified, i even see and can instal netflix, YASNAC passes both basic and CTS with basic evaluation, play integrity only basic.

i think i'm sitting in the same boat like this gentleman: https://github.com/chiteroman/PlayIntegrityFix/issues/280

or the user in this thread who passed device intergrity with an android 10 rom but did not with an android 9 rom on the same device.

There has to be something google did with the latest GSM/ play service whatsoever updates, no module/solution cant fix anymore for some devices with android 8.0, 8.1. and 9. I will provide every log possible to help and is there anybody who still bypass device integrity with this android versions and can share the configuration?

best regards.
[Magisk] osm0sis:
The Magisk module Xposed he's using does have the potential to be hidden using MagiskHide or DenyList, however. 👍
[Magisk] Vision:
The irony is if have custom ROM and still can't pass, all this features is useless.
[Magisk] neonblind:
If you are speaking about the official systemless xposed modul from topjohnwu himself he said its always detectable: https://xdaforums.com/t/2019-5-1-ma...eta3-sdk-21-27.3388268/page-210#post-73691464
[Magisk] osm0sis:
Ah thanks for that! Well there's the definitive answer for @ashish1989 then.
[Magisk] Vision:
We discussion about that before and he say have this

GitHub - HuskyDG/magisk-xposed: Legacy Systemless Xposed Framework by topjohnwu

Legacy Systemless Xposed Framework by topjohnwu. Contribute to HuskyDG/magisk-xposed development by creating an account on GitHub.

github.com

View attachment 6085264
[Magisk] Vision:
This mean

GitHub - HuskyDG/magisk-xposed: Legacy Systemless Xposed Framework by topjohnwu

Legacy Systemless Xposed Framework by topjohnwu. Contribute to HuskyDG/magisk-xposed development by creating an account on GitHub.

github.com

View attachment 6085266
[Magisk] Vision:
What about this in older devices can pass ?

GitHub - canyie/Dreamland: A third-party Xposed framework implementation which supports Android 5.0~14.

A third-party Xposed framework implementation which supports Android 5.0~14. - canyie/Dreamland

github.com
[Magisk] Vision:
I think we figured it out, in older devices, the old Xposed fails to pass with all the PIFs and the old safetynet, especially if you have a custom ROM
[Magisk] neonblind:
yes, these are topjohnwu xposed moduls. i'm a fan of compact phones and since sony decided to stop making compact ones, i'm sitting on a bunch of old stuff, using every systemless xposed module api 21 till 26. i never pass safetynet nor PI with it and well, you can trust topjohnwu, when he said, you always fail safetynet. on 8.1 lsposed should be installed because you can pass device integrity with it. as for riru, i dont know, never using it.
[Magisk] Vision:
Yeah i know, i had it many of those in my old Sony and riru (had it before the zygist appeared for the first time) as i remember working good in my old 7.1.1 when have it
[Magisk] osm0sis:
Guess "xposed" should be added to the PIF module's detected conflicting mods script.

Edit: Or we could just file it under https://github.com/osm0sis/PlayIntegrityFork/blob/main/README.md#failing-basic-verdict 🤷‍♂️
[Magisk] Vision:
and with this way can spoof it with inside functions PIF, and no trigger with Xposed and the Integrity can pass ?
[Magisk] neonblind:
ehmmm, when is release day? :) can't download without account, as you say. is there some kind of selection screen when installing on android <10?
[Magisk] Vision:
I think detect auto when you use older version and install only scripts-only mode

Here the latest with the scripts-only
[Magisk] neonblind:
Oh i understand, it uses script mode only with old magisk version without zygisk and not with new magisk and disabled zygisk option, right?
[Magisk] Vision:
And with the new Magisk and with zygisk, because still the old devices support, just different only disabled some functions of zygisk in PIF because not need it in older, i think
[Magisk] neonblind:
hmm, did not work for me. do i have to manually add "/data/adb/modules/playintegrityfix/scripts-only-mode" or is the api call missing in customize.sh?
[Magisk] Vision:
If the install not work you can, like you say, manually add all the files here "/data/adb/modules/playintegrityfix/

i don't know if anything else change beside the scripts-only-mode for that i say this
[Magisk] CZ.Kostra:
Installing (updating) the module is governed by the existence of the 'scripts-only-mode' file in the '/data/adb/modules/playintegrityfix/' directory of the installed module. If you want to use only scripts, you must create this file before updating.
[Magisk] polarisito:
Is there no way to bypass this yet?
[Magisk] pndwal:
Ah, missed that it's a custom ROM. I think I saw 2019 security patch date?...

So it could simply be that ROM uses a security patch level (date) not aligned with fingerprint used which became critical after March 2018...

You could try Scripts-only mode PIFork again + old MagiskHide Props Configuration module and use menu to select a fingerprint... This will globally spoof both the fingerprint and correct corresponding security patch date... May be best to use a print from same OEM since spoof is globally applied...

That (using a security patch date matched with fingerprint) was all that was all that was needed for passing device integrity verdicts on official LOS etc before USNF/PIF began spoofing pre-2018 prints...

Test with Xposed module etc disabled of course...

👀 PW
[Magisk] khusika:
There are couple answers about that in post #10,355 and #10,450
[Magisk] me_droid:
Haha, yes, I had a little stash of FP's I found in December, was using just one of them til this week when it failed. Now the whole stash has 0% success. Using PlayIntegrityNext til I can hunt down some more.
[Magisk] osm0sis:
Tap still worked for me a minute ago, but I'm sure it's not long for this world. I avoid opening the actual Wallet app in an attempt to prolong things when I know it's failing, though it could just be placebo.
[Magisk] boualemdz:
Ça ne sert à rien, il vaut mieux verrouiller le bootloader
[Magisk] MightySashiman:
merci pour cette belle contribution.
[Magisk] boualemdz:
people want to make an effort to bypass the strong verdicts and now the devices the Google developers are too strong for us unfortunately
[Magisk] boualemdz:
V11
[Magisk] iruiz2:
On 9.8 here. Doesn't pass, same as everyone else.
[Magisk] pndwal:
Does anyone with a custom ROM integrating device integrity fix/spoofing have MEETS_DEVICE_INTEGRITY?... If not with Magisk installed, possible with Zygisk disabled?... Or unrooted?

👍 PW
[Magisk] sawdoctor:
I'm on 9.9 on pixel fold and have just checked and I'm now failing device too. Everything still seems to work and no idea what issues this will cause. No idea when it happened so must be something Google changed
[Magisk] MightySashiman:
actually a good question. I don't unfortunately have another similar era / exact same phone as the rooted one I currently have on hand (a oneplus 6T running LOS 20 nightly). It'd be interesting to know if this is google silently introducing a new anti-anti-tampering detection method or if they just decided to dictate devices older than a certain threshold are now obsolete security-wise and want users to upgrade for that sweet $$$ (coincidence with the pixel 8/8pro line up release?)
[Magisk] alfian89:
What modules do you use and what version of Android do you have?
[Magisk] shoey63:
Those days are long gone. Google patched everything.

At the moment I'm only passing basic integrity
[Magisk] alfian89:
can you tell him? chances are it still works on my device. because I'm still on Android 9.
[Magisk] osm0sis:
This module requires Zygisk, so no real way to test this idea that I can see, since any custom ROM will by nature also fail Device... except maybe unrooted, completely unmodded, bootloader unlocked stock ROM? That should only fail Strong IIRC.
[Magisk] pndwal:
ROMs integrating SNF or other device integrity fixes can pass DEVICE_INTEGRITY w/o Magisk/root... If rooted just need to add Droidguard (unstable) GMS process to denylist... No module or Zygisk needed... 👀👍

...Eg. @kdrag0n's USNF was a derivative of his SafetyNet passing Proton ROMs originally... It had SNF... Then he made a Universal SNF module for all...

🤠 PW
[Magisk] chiteroman:
Today at Google someone woke up in a bad mood...
[Magisk] chiteroman:
View attachment 6030390

Maybe Google banned marlin and walleye like they did with angler.

I will try to bypass it but I can't promise you anything...
[Magisk] osm0sis:
Any way to expose what's getting spoofed in the Zygisk part as user settable in a .prop in the module directory or something? That way it would be possible to experiment without a full recompile.
[Magisk] zgfg:
On my Xiaomi.eu 14 I didn't need PIF nor SNF and was always passing Basic and Device

However, Device Integrity has just gone today😡

(Device is still Certified in Playstore but for how long)

Old SafetyNet of course still passes but with Basic CTS (as usual)
[Magisk] osm0sis:
Switching to latest upstream official Magisk CI build with Native Bridge Zygisk merged has no effect on the failing Device verdict either; tested on my OnePlus 9 Pro on Lineage (former daily driver) which previously worked.
[Magisk] MrLumin:
I thought it was just on my device's end. I tried many things to try passing the DEVICE_INTEGRITY verdict but to no avail. And it turns out why.
[Magisk] Spartacus500:
Since yesterday, Samsung S7 9.0 Pie Play integrity devices ❌ 🤷
[Magisk] zgfg:
Griffin still works for you?
[Magisk] bombadier:
On the subject of kernel blacklisting, I just updated to a March beta of Sultan's kernel for the Pixel7a,

uname -r

5.10.213-Sultan

PIF still works but I thought this string would result in a ban?
[Magisk] pndwal:
Using PIF with JSON, or Scripts-only mode? PW
[Magisk] ashish1989:
I think I should use this as the older one has already specified will not pass safetynet

Will definitely try it now, but first I should install huskyDG xposed and latest @osm0sis script
[Magisk] ashish1989:
I am sorry, I misread it, I am not using this, installing this now. But the problem is modified xposed can not be downloaded, its deleted I think

Edit - Found it on github
[Magisk] pndwal:
Dreamland (with Pine hooking) may be better if you know what you're doing... 👀 PW
[Magisk] ashish1989:
I just installed @huskydg xposed in magisk and latest CI 205 @osm0sis script. Will then install dreamland one if integrity fails
[Magisk] ashish1989:
Used PIFork and same OEM fingerprint using old MHPC, cleared play services and play store data and rebooted, still can't pass integrity

I think I should try Dreamland now
[Magisk] neonblind:
i and other users have the same problem.

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

we need to find a solution for android 8-9. for me scripts-only mode also do not work for these devices.
[Magisk] sawdoctor:
We may have to face the fact that there is no solution. Even for devices above android 9 as soon as Google either ban the last few prints or block the mismatch then that's it no solution apart from locking bootloader and unroot
[Magisk] osm0sis:
Most custom kernels have started using a patch to alter the uname call kernel-side if it sees GMS is the requestor.

🔧 [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] osm0sis:
If scripts-only-mode doesn't work then normal mode should still. Feel free to add more fields or properties to your json, and do verboseLogs 100 on my fork to see if they're checking anything new on older ROMs. You're on stock ROMs, but were you also on stock kernel? Did you follow the troubleshooting instructions and remove other possibly conflicting modules? Enforce DenyList disabled? Latest Magisk Canary? Latest Shamiko installed (where possible)?
[Magisk] Vision:
Yeah, as i remember this have it in my old Sony 7.1.1 but all Stock, i tell yesterday about Dreamland, i read work to pass if original xposed can't
[Magisk] Vision:
Yeah, give it a try
[Magisk] ashish1989:
Dreamland not working with my required module. I think I have to pass now and accept the fate that no banking app would ever work on my A7 device
[Magisk] Vision:
Unfortunately, but i remember say about you have another device with Android 9? If yes

Relocked BL and all stock in Android 7, and have banks apps there
[Magisk] ashish1989:
Yes I have another Samsung device with A9, but its rooted and only passes basic integrity
[Magisk] Vision:
Wait, and your Samsung can't pass? Or still talking for Android 7 ?
[Magisk] Spartacus500:
V15.9 by chiteroman it worked all the time until yesterday 🤷
[Magisk] CZ.Kostra:
This suggests that PIG has done something for older versions of android(?).
[Magisk] Oplaom:
Does anybody have a fork of this that supports riru?
[Magisk] CZ.Kostra:
Minor improvements and bug fixes Here.
[Magisk] osm0sis:
Known Banned Kernel List updated: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89308909

Found specifically -CAF (but NOT -caf) is banned; unclear if it's a new ban or was banned before and just not found yet.
[Magisk] Vision:
For new devices or older ?
[Magisk] Vision:
Theoretically, if change the name of folder zygisk to lib and inside for what arm we need add the folder etc. arm64-v8a, and chance is to libsafetynetfix like old riru support ? :unsure:
[Magisk] osm0sis:
You should definitely be able to get a PIF module working on your A9 device.

We have a Android 13 Xiaomi device that's started failing with the griffin print but others still work on it...

So seems more likely a normal print ban or DroidGuard update to ban it that's being A-B tested or is in a staged rollout. 🫤
[Magisk] osm0sis:
That's not how programs work. Zygisk APIs are Zygisk APIs.
[Magisk] Oplaom:
New devices
[Magisk] wfred:
Has anyone tried the fingerprint and props from this Xiaomi device? 🤔
[Magisk] Oplaom:
So is there no hope for porting this module to riru?
[Magisk] osm0sis:
USNF used to have a Riru version, so I wouldn't say "no hope", but Riru is deprecated, so it's probably more like "no interest". As we saw yesterday, Riru is on the Play Integrity file checks, so probably wouldn't pass anymore anyway.

🔧 [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] Vision:
Oh yes, because i have done this in the old safetynet module zygisk and change to work with riru, or i do something else I don't remember 😂🤣
[Magisk] Vision:
Maybe if mod classes.dex to v2.4.0-MOD, and change the FP to make it work it ? @osm0sis know better
[Magisk] Oplaom:
Kinda saddening bcuz zygisk is getting detected in some apps I use
[Magisk] Vision:
Yeah, i use Kitsune Mask, have the old magiskhide and a mod zygisk version, and for that you need shamiko
[Magisk] osm0sis:
Zygisk is much easier to hide than Riru. Just pray they continue to develop Shamiko.
[Magisk] 18Orioon:
Hi, I have just installed microg and id like to know if there is anyway to pasa safetynet.
[Magisk] Oplaom:
Maybe this will help you:

Peace in microG user group

Guide on How to Pass SafetyNet/PlayIntegrity/CTS on MicroG. Requirements : 1. Root, Magisk or KernelSU is preferred but you can try other root solutions too. 2. PlayIntegrityFix. 3. PlayIntergrityNext. 4. Zygisk Enabled : Magisk : you can go to Magisk Manager setting and enable "Zygisk" toggle...

t.me
[Magisk] 18Orioon:
It didn't but thank you anyway. I do not have Google services I only have microg and when play integrity fix is active microg crashes thus making every Google dependent app unusable.
[Magisk] zgfg:
The 'guide' that the guy gave you above has actually nothing specific to MicroG. Just a standard guide how to setup PlayIntegrity by using playcurl to obtain the custom json file..However, that does not solve your problem when you only have MicroG and bo GApps/Play Integrity services

Good that you have confirmed
[Magisk] ashish1989:
Is playintegrity_next not working as I can not pass device_integrity in my A9 device after trying many times
[Magisk] 18Orioon:
then is there any way I can pass play integrity?
[Magisk] shoey63:
@Vision

Please consider using the multi-quote function when responding to many posts in this thread.

Your constant replies to individual posts are bordering on spam.

Edit. It will also reduce notifications for those who have subscribed.
[Magisk] Oplaom:
The people in the microg telegram group will help you
[Magisk] neonblind:
for my a8.0 /8.1 devices: both stock rom, stock kernel, freshly flashed, no other modules, shamiko only 8.1. nothing worked. will try latest canary and provide logs. maybe you see something.

from your readme: "Add a "verboseLogs" entry with a value of "0", "1", "2", "3" or "100" to your custom.pif.json to enable higher logging levels; "100" will dump all Build fields, and all the system properties that DroidGuard is checking."

what exactly do i have to add? "verboseLogs": "100" at the end of custom.pif?
[Magisk] neonblind:
that aren't good news. do we know, if there is another working print public?
[Magisk] Vision:
Oh yeah, sorry my bad, from now i do this.

Thanks.
[Magisk] Vision:
if not pass is something else, because this module do one thing, downloads a working fingerprint.

So if not pass with the current Xiaomi.Eu, neither pass with this
[Magisk] neonblind:
Got it running. Android 8.0 griffin print failed device integrity.
[Magisk] zgfg:
Anywhere, but last field must not end with comma, hence it's easier to add to the top, like in the attachment
[Magisk] zgfg:
It fails for me too, since today morning. All my 'private' prints work fine though

A13, Canary 27002, PI Fork v8 - nothing changed compared to the last days when Griffin worked

That's why I asked in the morning here did Griffin still work, but nobody responded

Seems it's specific to some devices/setup
[Magisk] Vision:
Oh not see it, just now test it Xiaomi A11 MIUI 12.5, pass 2/3

EDIT: Kistune Mask latest stable and PIF V8
[Magisk] CZ.Kostra:
Griffin works for me on MIUI14 (A13) Xiaomi.eu ROM.

I am using PIFork v8 in Canary 27002.
[Magisk] neonblind:
so do you mean, a private print works for your A14 device where the griffin print got burned? you only change custom.pif with private print and nothing more?
[Magisk] zgfg:
A13 actually. Yes, just changed the JSON with the other phone/ROM prints inside
[Magisk] aliantonio:
I'm passing device and basic integrity but RCS just started getting blocked again. v15.9.6 of play integrity fix was working up until about 20 mins ago.
[Magisk] ki4mor:
Yup same here, just got off a plane and thought it was something to do with my network settings. Tried a few things before ending up here, no luck.
[Magisk] neonblind:
thanks. your answer is the final piece for my conclusion, that griffin is on its last legs. all the user using griffin but dont pass device integrity especially on older android version (myself included), dont need to change magisk or modules. there configuration works. what they need and maybe all of us sooner or later is a working print.
[Magisk] Redn2000:
I just had the same thing happen to me. Tried the update to 15.9.6 but no luck. This is also after using the guide to generate my own fingerprint from my own device last month.
[Magisk] fma388:
Just a question:

Is there a way to prevent WearOS devices from resetting when the GMS app data and cache are cleared?

I'd like to be able to keep testing fingerprints, but it's annoying to reconfigure my watch every time o_O

Thanks !
[Magisk] woodpecs:
Same here as well. Sooo tired of the Google BS. I switched from signal because of them dropping SMS support and ended up with RCS, got contacts to switch since it was already on some of their phones and have been dealing with RCS issues every couple of months. The last few has been from blocking rooted devices. Might have to finally live the unrooted life because I am tired and the constant battling against restrictions
[Magisk] majorfigjam:
You don't need to clear GMS data, you only need to stop and clear Play Services cache between tests. That way you preserve Wear OS settings.

FWIW, Griffin and other custom fingerprint still working on my Pixel 6pro, A14, March Play Services
[Magisk] Link2811:
Same, RCS just died again, and I'm still passing device integrity.
[Magisk] osm0sis:
Have you RCS issues guys tried adding the GApps with their own root checks to the DenyList for Shamiko to help with? Meet, Messages and Phone are all known to have some (Mishaal reported on it at one point). I've never once had an RCS issue, even when my phone was failing Play Integrity. 🤔
[Magisk] pndwal:
RiruHide took advantage of @canyie's native bridge loading (specifically it's anonymous memory and repairable environment) so had some advantage over Zygisk for hiding, but with recent refactoring Zygisk has abandoned LD_PRELOAD and uses native bridge too. Also, Zygisk always self-unloads (avoiding detection) unlike Riru, so Riru has no advantage anymore and Zygisk is now actually better for hiding purposes AFAICS.

But that came before Magisk 24.0 (Zygisk), and @kdrag0n said that he wouldn't produce Riru versions once 24.x (public) builds were available.

In DroidGuard? Mmm. But it's been there for years however.

🤠 PW
[Magisk] Link2811:
Yes, but still the same
[Magisk] osm0sis:
Presumably it won't start working immediately. Might need to reboot and wait a few hours, or even clear app data for the apps and/or Carrier Services.
[Magisk] Link2811:
Edit.
[Magisk] Link2811:
Okay I will try that, wait a bit and report back.

Message was on the list since always but never added phone and meet apps.
[Magisk] osm0sis:
You need to do it directly after a reboot. Those are only partial logs.

Hmm, well that's the only one that should matter for RCS, so not sure. 🤷‍♂️