yashsingh1/xdaforums huggingface dataset:
[Magisk] GN-z11:
Not KernelSU, I'm 100% sure. I am passing in mine. Perhaps KernelSU then checking if there are specific modules. But also that is a very low chance. I know this because I have KernelSU on my device but no modules at all.View attachment 6060072
[Magisk] zoisa:
So i read the last pages.

I have xiaomi, custom rom, and custom kernel, i use AutoPif Next and dont work, i tried some FP manually from repository, dont work, so the problem is the custom kernel and not the FP?
[Magisk] sir_bazz:
Maybe.

Updated LOS today on my RN9P and ran into problems on the default kernel. Cutting a long story short, all up and running again on a custom kernel, (older versions of the same custom kernel that I had at hand were met with different issues).
[Magisk] sawdoctor:
No one is certain what is actually going on but it does appear changing your kernel can fix the issue. For example on the pixel 7 no one is passing any fingerprint with sultan kernel but other kernels are passing.

The strange thing is the kernel hasn't updated its something on Google server side that has changed
[Magisk] zoisa:
Ok i will try and i will post the result. Thx.

Edit: it doesnt work for me change kernel. :(
[Magisk] Gilg@mesh:
I just noticed my device failed today too...one from december.
[Magisk] sawdoctor:
What ROM/kernel are you on?
[Magisk] Gilg@mesh:
Evolution X, Sultan kernel, but been using @osm0sis fork.
[Magisk] 666biker:
Hello guys, is my understanding from reading of last pages, that currently there is no solution to pass safety net check? CTS profile match fails on my OnePlus 3T with LineageOS 18 and root Magisk. I noticed it today when GOOGLE Pay does not work in the shop (pay by mobile - NFC), it was working 2-3 days ago. Or I missed some workaround solution for CTS profile match pass again? Thank you in advanced.
[Magisk] sawdoctor:
From what I've read on telegram no one is passing integrity with sultan kernel. Try swapping kernel and report back if you can
[Magisk] Gilg@mesh:
I've been using Sultan kernel for a while and it's been passing fine, but it's no big deal my bank have pay app that can be used no problems after hiding with Magisk.
[Magisk] kocsogfax:
I have tested 5 custom pif, pifs from android 6.0, 6.1, 7.0, 7.1:

Xiaomi 13 pro, with xioami.eu Linux 5.15.74-android13, all of my custom pif NOT pass basic and device. Google play version: 39.3.33-29, updated: 2024/01/24

Xiaomi 11 ultra, with xiaomi.eu Linux 5.4.210-qgki all of my custom pif PASS basic, device, Google play version: 39.3.34-29, updated: 2024/01/25

Xiaomi mi 9, with xiaomi.eu Linux 4.14.180-perf, all of my custom pif PASS basic, device, Google play vesion: 39.3.33-29, updated: 2024/01/20
[Magisk] sawdoctor:
It's not sultan kernel that's changed it's something Google side that's affecting some kernels. All i can tell you is it's worked for a lot of people
[Magisk] osm0sis:
It's not about GMS version, DroidGuard gets downloaded into GMS app data independently, and can update any time, plus that doesn't necessarily even mean anything, because a lot of DroidGuard is server-side.

If you keep looking for more prints you'll find one that works on your other device again, as long as you didn't change anything else on it recently. I was able to get my failing device working again by doing a print from 8.0.0 instead of the previous 8.1.0 for example.
[Magisk] changhuapeng:
My private PIF of almost 2 months was "banned" yesterday. I went through my private stash of PIFs and found many of my private prints, extracted from dumps and ROMs included, are not passing device as well now.

My phone is flashed with a custom ROM and custom KernelSU kernel (linux ver 4.14) so I'm not too sure if I'm one of those people that were affected by the custom kernel issue. I have also tried switching from KernelSU to APatch but that doesn't help at all.

However, I managed to find a couple of PIFs that still works despite not switching away from my custom KernelSU kernel. I don't know if this matters but a thing that I notice about these PIFs that still works for me are that most of them do not have SECURITY_PATCH in its prop.

Edit: I'm using PIFork v7, by the way.
[Magisk] osm0sis:
For the kernel issue people I don't think any print works until they switch to an older kernel. So you're in the newly banned print rollout boat with me.
[Magisk] changhuapeng:
If that's the case then I can say a good chunk of my prints which are extracted from ROMs and not available in public dumps, are dead now. o_O
[Magisk] osm0sis:
Are they all old Android versions? It seems like they are "raising the floor" on us by banning a lot of those currently.
[Magisk] osm0sis:
@Fishawy can you PM me a full log from Fork v7 at boot up on the broken kernel and "VERBOSE_LOGS": "100" enabled? I want to be certain there isn't a new property check that's involved somehow.
[Magisk] nicoco19:
Hello everyone,

Having problems downloading the official apps from the Google Play Store since my Samsung Galaxy S23 ULTRA is rooted on Android 14, I used the Play Integrity Fix_V15.1 and the latest APK app from Yasnac to pass the SafetyNet.

When I launch the Yasnac application this is what I get as a result:

Basic Integrity: Pass

CTS profile match: successful

Assessment type: BASIC

Timestamp: January 26, 2024 at 4:45:34 p.m.

When I launch the Google Play Store application, I go to the settings then on the About tab and this is what I have: Google Play Store version: 39.3.33-29 (o) (PR) 599690833 and unable to update it even if it offers me an update from the Google Play Store.

The most worrying thing is when I click on Play Protect Certification: it tells me that the device is not verified.

How do I know if the installation of Play Integrity Fix and Yasnac worked when on the one hand it tells me that my device is not certified???

Previously, when I was using Play Integrity Fix_V9.8 and before upgrading to Play Integrity Fix_V15.1, in my Google Play Store certification it was clear to me that my device was indeed verified.

Can you help me please.

Good day.

Nicoco19
[Magisk] changhuapeng:
Most "banned" prints are old Android versions but a few that are still working are of even older Android versions. If you would like, I can PM you a few of the prints for testing?
[Magisk] osm0sis:
Nah, I've got plenty. Yeah I found some Android 5 ones still working myself. But a lot of the banned were Android 5 and 6.
[Magisk] tom1807:
Google Play Store version is not important,

I think you maybe should look in to the Google Play Services version and when it was updated.

I can imagine, that there is a correlation between Custom Kernels and GPS.

FYI

After reading all these posts about "banned" FPs, I checked my 20 FPs, ranging from Android 7 to Android 10 and API Level 24 and API Level 30 and all passed.

Went back to my "original" FP from mid of December after that.

But I am on a stock kernel.

Cheers

Tom
[Magisk] Lagartixo:
Look for a custom PIF. I tested a dozen until find one that worked.
[Magisk] linuxares:
Dozen, sometimes it takes like 100s
[Magisk] giacomowrc:
I can't pass device integrity with arter kernel r9 + kitsune magisk and Osm0sis v7 module.

On stock kernel is fine.

I've nothing phone 2 stock ROM 2.5.2 A14.
[Magisk] Nergal di Cuthah:
1) yasnac is outdated switch to play integrity checker (or the one built into playstore developer mode)

2) you need a custom fingerprint for 15.1 i believe
[Magisk] osm0sis:
Did you let @arter97 know? If anyone can bisect and find the cause it's him.
[Magisk] giacomowrc:
Yes, of course. He said: "Please ask others for assistant on this. I personally haven't looked on device integrity as none of my apps care."

Anyway, I'm actually back to stock kernel.
[Magisk] Nergal di Cuthah:
Did switching back to stock help your issue (as it's helped some others)
[Magisk] 666biker:
you generate it randomly using PixelFlasher tool as well and just try integrity check after each generation?

btw, it depends which Play Integrity Fix is used? I am on latest 15.3.4

In PixelFlasher I haven't load any custom build.prop file or something, just connect phone, open PIF manager and press "Get TheFreeman random pif..." and paste, upate. integrity check.. correct way of trials?
[Magisk] giacomowrc:
On stock kernel I pass device + basic, no problems.

My configuration is kitsune magisk + Osm0sis v7 and custom pif of course.
[Magisk] linuxares:
Yes I used that back in November before finding my print (I think it was November?). But it was a bug back in the script back then so my phone only got certain prints.
[Magisk] chiteroman:
Why don't use Zygisk? Riru is depracated.
[Magisk] m0han:
https://xdaforums.com/t/module-play-integrity-fix.4607985/#post-88781523

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88782733

https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88784977

That device runs Riru, it doesn't have Shamiko and Zygisk is not enabled.
[Magisk] Captain_Throwback:
This version caused some odd side effects on my device. My lockscreen font became very tiny for some reason. Went back to the one from Post #39 and all is working properly again. Any idea what the problem could be?

UPDATE: I just tried the test version @Displax posted and it has the same problem. So perhaps the dex file is the issue?
[Magisk] chiteroman:
This is strange... Can you send logs?
[Magisk] chiteroman:
What happen if you check logcat ? This shouldn't be possible XD.
[Magisk] chiteroman:
Execute this command: adb shell "logcat | grep 'SNFix'"

And send me output.
[Magisk] Captain_Throwback:
See edit above

UPDATE: Previously I was able to go back and forth between versions and it restored the lockscreen/SystemUI. Now I've removed the module completely and it's still broken. Looks like I may need to factory reset :(

UPDATE 2: Rebooting the device into Safe Mode got the lock screen and SystemUI back to normal. However as soon as I install the latest version of this fix, it gets messed up again. Going back to the zip from Post #39 fixes it once again, so I guess I'll be sticking with that one for now.
[Magisk] psychoela:
Some app can still detect zygisk n freeze, tested with official mgisk, alpha n delta,so i don't have choice.

View attachment 5961177
[Magisk] shaunoleary:
Good morning,

I have just tried the module in the original post in this thread, and it worked like a charm for Google Wallet. I have a Google Pixel 3 with LineageOS 18.1. Great work, thank you so much for this module.
[Magisk] Captain_Throwback:
No Strong Integrity with this one, but lock screen and SystemUI are fine. Seems the Post #39 one is still the best one for now. I checked logcat for 'SNFix' but nothing reported there.

UPDATE: It seems even the Post #39 version is giving me the messed up lockscreen and SystemUI now. The only version that appears to work without an issue is the @Displax "STRONG" version with the mod to set first api level to 33. I believe that's essentially the same as what @Stillhard is using. I'm not sure why this is the only way my device can pass strong integrity without an issue, but that does appear to be the case.

If there's any other logs I can pull for you, please let me know.
[Magisk] beeshyams:
In Magisk 25.2 on Pixel 6a, Android 13, July update, I see this warning Though all tests including strong integrity passed

Any idea why? @chiteroman

Magisk logs are empty and it says that's weird but logs are saved and can't be attached so pasted below

Spoiler content hidden.
[Magisk] fillwithjoy1:
@beeshyams You need to enable Zygisk in the Magisk settings, and then reboot to fix.
[Magisk] fillwithjoy1:
yeah because you need to enable Zygisk. You need to migrate all your modules to Zygisk from Riru.
[Magisk] fillwithjoy1:
Does this module bypass strong_integrity, i.e. fake bootloader unlock status?
[Magisk] beeshyams:
Done that twice.. Still remains

Thanks for your help
[Magisk] Essentrix:
A52s 5G latest Android 13 using version in initial post - all 3 green!
[Magisk] pndwal:
Why not try latest Magisk?... So many fixes since 25.2, some Zygisk related... PW
[Magisk] beeshyams:
I use V4a and read that 26.x Magisk has problems with 64 bit V4A. Hence using 25.2... Surprisingly, strong integrity also passes so I am not sure if I should ignore it. Incidentally, get the same warning with Displax latest module. Your thoughts?

Thanks for being a help for all 🙏
[Magisk] mkcs:
After upgrading the module, those play integrity or safetynet checkers failed to check properly, although no banking apps could detect the status of root
[Magisk] pndwal:
Many thanks for efforts again!

Since OP is not clear, can we take it that this PIF is once again a full (standalone) fixed-USNF forked build with the shipping level fixes added?... No need for USNF + PIF (both) now?... PW
[Magisk] ykjae:
It's working fine for me as a stand alone module. Android 14 pixel 6 pro raven.

But so was every other version. What are the changes in 9.1?
[Magisk] m0han:
Going by the size, it doesn't seem to be the full thing. @chiteroman would know better.
[Magisk] lihaoking:
Where can I download the full version?
[Magisk] pndwal:
Yeah, but it still should be clear for users... See my reply above... Really, I'm hoping for more clarification for everyone in OP and in GitHub repo...

I'd actually considered size (I haven't properly looked at the code and am very amateurish at that), but the less than 25% increase could have been accounted for by • Updated to latest libcxx and • Strip native libraries (less size) changes... 🙃 PW
[Magisk] ZalRi:
someone still have version 9.0 Full ? share please
[Magisk] Bkblues:
You can download the historical version here
[Magisk] ZalRi:
don't have full version in that link
[Magisk] iruiz2:
Working here on a OnePlus 9 pro with OOS 13. I say with and without the module screenshots. No other safetynet modules installed here.

View attachment 6019050View attachment 6019051
[Magisk] chiteroman:
It has the fix included, so it's full version. It has less size because I'm not using C++ (except Dobby which require it).
[Magisk] pndwal:
So this:

View attachment 6019073

is the full version? 🤔 PW
[Magisk] ZalRi:
can u share Full version 9.0 ?,

9.1 Broke my CTS in Miui. i can't even check with YASNAC.

every time i open YASNAC or something that need CTS, i got Google Play Service Keeps stopping
[Magisk] chiteroman:
Provide logs
[Magisk] ZalRi:
Here
[Magisk] ValerioWasTaken:
Here are all the versions. Mod edit: TG link removed.

Badger50 Senior Moderator
[Magisk] amakuramio:
Works, device is seen as pixel 2, however I wonder if hackers who have a backup can clone and use it as google prompt (since same fingerprint) and gain access, I got hacked twice in 2023
[Magisk] UberNorse:
Working as a stand alone on P7P and a P7A with Magisk 26.3. Thank you!
[Magisk] pershoot:
@chiteroman 9.1 (https://github.com/chiteroman/PlayIntegrityFix/releases/download/v9.1/PlayIntegrityFix_v9.1.zip) seems ok, initially, thus far, on 7A (A14). Thank you.
[Magisk] 666biker:
I tried many random, but not lucky yet :( using now module 15.2, oneplus 3t, LineageOS 18.1
[Magisk] sga999:
I must be blind. In PixelFlasher, PIF Manager, after getting TheFreeman random PIF, I don't see exactly how to paste and update. (I have been using a very old PixelFlasher which had different actions under Magisk).
[Magisk] 666biker:
Use Custom Fingerprint/Build.Prop to Pass Play Integrity Test

This guide will show you two methods to create custom fingerprints using build.prop and pass the Play Integrity Test on rooted/custom ROM.

droidwin.com
[Magisk] Nergal di Cuthah:
I hope they keep that article up to date with our still evolving understanding and progress
[Magisk] 666biker:
who knows, at least I am not lucky guy according it :)
[Magisk] sga999:
Thank you! I could have missed it, but I don't think PixelFlasher documentation has as much info as this article. This was very informative.
[Magisk] weilunt0219:
Anybody else getting an issue where Wallet stops working after a little bit? Initially when I installed this module it just worked and I passed BASIC and DEVICE, along with wallet and Empower working without any issues.

However, recently it stopped working, with DEVICE no longer passing, but after following the thread and doing some digging, I used TheFreeman193's `pickaprint.sh` to get DEVICE and BASIC both passing, but not necessarily enabling me to use my apps as intended (Wallet or Empower).

Even when I pick a print that ends up working and allowing me to use Wallet for contact less pay or sign into Empower, it only works for maybe a few days before failing again (with DEVICE and BASIC still continuing to pass)
[Magisk] Umgak:
If it "just worked" for a while, you probably were using the built in 15.1/14.6 fingerprint. That one was restricted recently, which would be the first "recently stopped working."

A few days ago there was a second restriction-wave, and it's possible your new print also got hit by that.

As for why Wallet doesn't work and your Play Store probably isn't certified: these actually make a PI attestation check every few hours and cache the result, which is probably why after you got BASIC and DEVICE passing, you didn't have Wallet still. You can clear Wallet cache, Play Store cache and data, and Play Services cache and data to refresh the result immediately, but this will remove your cards and possibly cause a few other issues, like resetting update preferences in Play Store, unpairing WearOS devices, etc.
[Magisk] purgy:
Just confirming that switching back to stock from sultan kernel got me back to 2/3.

Pixel 7a, stock sept patch (A13).
[Magisk] purgy:
There was also an issue with 15.2 where it would stop working after a bit if I remember correctly.

↓↓↓↓ we need an eye roll reaction ↓↓↓↓
[Magisk] osm0sis:
To whoever Frankenstein'd my v4 and my v6 zips together on Telegram: anything you can do with v4 you can do on v5+ and do more, so that was pointless... 🙄
[Magisk] HippoMan:
Pointlessness and other confusion are endemic under TG ... while pointfulness and clarity are difficult to find there. :)

I hope that the TG Dr. Frankenstein is reading your message here.
[Magisk] simplepinoi177:
I dunno...the PIF Manager workflow/guide in the OP seems easy and simple enough to me (below)...

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com
[Magisk] purgy:
I have no idea if it's relevant, but sultan kernel does not require disabling dm verity etc, so I still had those enabled.

Am I wrong in thinking the other custom kernels that are still passing require dm verity / verification to be disabled?
[Magisk] HippoMan:
Agreed. And whether it's intentional or not, they also seem to be making it a bit more precarious to use non-stock kernels.
[Magisk] HippoMan:
MESSAGE NUMBER 10,000 on PAGE 500!

Let's have a party!
[Magisk] majorfigjam:
Yes, you're wrong. My P6pro Kirirasura doesn't need them disabled. On the other hand, it wasn't updated for the P6 series in January.
[Magisk] S1yRuleZ:
OnePlus 11 stock android14 (OOS14), rooted.

Kitsune Canary + Zygisk enabled + MagiskHide(SuList) + PIFork_v7 and like 50+ tries on PixelFlasher random pif generation and I still fail CTS check.

The strange thing is that I can see my original fingerprint on TB Checker and Momo, is that normal? I don't think so.

I'm losing my mind at this since I passed both basic and device integrity like 2 days ago with stock magisk 26.4 + PIF 15.1 and literally the first random TheFreeman193 pif.json I got. Yesterday I don't know what I did exactly that failed the check.

Any clues on what am I possibly doing wrong? Some stealthy google update ruined everything recently? Might be LSPosed or some other magisk module doing conflicts?
[Magisk] Fishawy:
Radioactive and Starlite do not require disabling verity or verification, and they both pass.
[Magisk] Nergal di Cuthah:
You think wrong. It should be your original fingerprint. Module only spoofs server facing droidguard.
[Magisk] majorfigjam:
You're likely not doing anything wrong, if that random pif was working as you think it was. Google has clearly changed something in their validation process, which is breaking some, but not all, custom roms and kernels.

Lots of clever people are trying to work out what that is right now, but no solution yet.
[Magisk] simplepinoi177:
That's why i'm holding my breath for the next version of @osm0sis ' PIFork....hoping that it's a sign a good number of things were figured out and maybe some of these FPs that are now failing might have gotten sorted and can once again pass
[Magisk] beeshyams:
A possibility is that Google is doing it in countries where wallet is available. This is just an observation and may need others to confirm

I am from India where we don't have wallet and Gpay works with Play Store certified (of course with basic integrity). I had my custom print running for a while and switched to Freeman's print and no problems for 7 weeks, since I am using it.
[Magisk] nicoco19:
Hello @tom1807 et @Nergal di Cuthah ,

If I understood correctly, it's a security issue when I start my Samsung Galaxy S23 ULTRA?

Currently I use the code from the SIM card and to unlock my phone it is a password, I have never configured the fingerprint.

If I do this, do you think it will solve my problem and I will have my device certified for the Google Play Store? How do I know if I'm blocked by the Google Play Store please? If this is the case, what should I do to fix it? Is there a tutorial or other applications to get my phone certified?

When I used the Play Integrity Fix_V9.8 everything worked fine, Yasnac put everything in PASS and in the Google Play Store settings my device was also certified.

Do you think I should go back and revert from Play Integrity Fix_V15.1 to Play Integrity Fix_V9.8 or did everything work fine?

Sorry, I admit I'm a little lost.

Thank you for your help

Nicoco19
[Magisk] majorfigjam:
No, I use wallet regularly, probably too regularly, and have not seen problems with it. I even use it on a Pixel, which is not officially supported in my country.

Nearly 2 months since I switched to Osm0sis, and while I occasionally swap them, I've never failed Device integrity on any of my previously working prints (yet).
[Magisk] majorfigjam:
I think you are muddling up fingerprints!

You may, or may not, use a physical fingerprint to unlock your device with a reader. That has no relevance to this thread, play integrity or anything related.

Your Samsung has a "software" fingerprint contained within its Properties, usually in a file called build.prop, which Google validates. If your bootloader is unlocked, and/or your device is rooted, you will not be certified unless you provide an alternative software fingerprint that will fool google into believing your Samsung has Device Integrity.

To find how to do this, start with the second most liked all time post in this thread, or one of the other guides scattered in the previous 500 pages or so.

Edit. As you added to your questions. The old versions of PIF supplied software fingerprints. Those fingerprints no longer work, so you need to find one that does.
[Magisk] 666biker:
just small question, if I update custom PIF file, should I see the print is really applied in the phone? e.g. somewhere under device system information? because when I am generating custom PIFs and e.g. use "DevCheck"app to show system information, fingerprint data are unchanged there. Or this Pixelflasher and PIF generator update that json file internally and basic system information still shows default fingerprint? thanks
[Magisk] majorfigjam:
No - the PIF file only spoofs for Droidguard, everything else sees your actual device.

To see what Droidguard sees, you need to check your logfile for PIF eg with adb shell "logcat | grep 'PIF'"
[Magisk] Septentri0n:
My print stopped working 2 day ago like a few people, flashed a stock kernel from custom but it didn't fix if for me so i went back to custom. What fixed it was going into magisk disabling the playintegrity module restarting, turning the module back on then restarting again and it's passing. Hope it helps