yashsingh1/xdaforums huggingface dataset:
[Magisk] GabbyWC:
For now, at least, I'll stick with the PI Fork v7 "no custom.pif.json method" which passes both basic and device integrity on my device. I look forward to osm0sis' technical analysis on the current situation when he checks in to this thread today.
[Magisk] Migsi:
I'm aware of these new fields. They get eliminated when using the migrate script, which I guess is fine. Also the osm0sis specific var DEVICE_INITIAL_SDK_INT gets added properly, so it is definitely not an issue of the module. Guess it is related to all these banned fingerprints. Just tried some Galaxy S9 ones, which didn't work as well :/

I'm not using Wallet/GPay die to missing NFC on the phone, but I require device integrity to pass for other services. Anyway, these are already all on the denylist.

Guess now the only thing left to do for me is sit and wait to see if my current print gets magically unbanned 🤷‍♂️
[Magisk] EuK_V:
Three different prints on my three phones just stopped working today.

Updated to @osm0sis's fork V7 - can't pass device with any of my previously working prints and none of @TheFreeman193 prints is working. On the latest @chiteroman's module can't pass device either.

Can't figure out what is wrong..
[Magisk] turonl12:
We may have a bit of calm again (at least for a short time), although wallet says, "security not met", I’ve verified the payment with the newly chosen fingerprint – and it went OK 😊

However, it’s strange it doesn’t work on other fingerprint that was passing device.

Verified 2 times that it passes the device – oldpriv (device passed) -> Xiaomi.eu (only basic) -> oldpriv (device passed).

Let’s hope that this is not a beginning of some bigger action by G☹
[Magisk] SoyDPR:
this method is the easiest I have found, it also keeps working and every time they ban a fingerprint you click on the APK until you find another one available

PlayIntegrityNEXT/Gms apk to use with play integrity next at main · daboynb/PlayIntegrityNEXT

Contribute to daboynb/PlayIntegrityNEXT development by creating an account on GitHub.

github.com
[Magisk] simplepinoi177:
user on Telegram said this isn't working....figured Google banned xiaomi.eu ROM's....
[Magisk] esatch:
I switched to osm0sis v7, but my private fp still won't pass.

Other "mined" fps are fine.

EDIT: same fp passing on a different device with dev2...i'm confused.
[Magisk] 1jkan:
For me, PlayIntegrityNEXT works on Samsung 20+
[Magisk] m0han:
Wow, you mean now? I believe you've seen this post. https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89297149
[Magisk] Fishawy:
Two things:

If you have private print failing and others passing, please compare them side by side and try to spot the difference. Unfortunately all mine are failing now so I can't do this.

Mind sharing that Dev2 module? Have you tried it on your phone since it's passing on others?
[Magisk] FIERA03:
A little more detail...

If the device supports NFC-F, this application is almost certainly pre-installed. The presence or absence of this app seems to determine whether STRONG is checked.

If you succeeded in displaying the login screen last time, I would like you to install this app and try again.

おサイフケータイ アプリ - Apps on Google Play

The Osaifu-Keitai app is an app that displays and introduces a list of Osaifu-Keitai compatible services. You can use other functions required to use Osaifu-Keitai.

play.google.com
[Magisk] aygul12345:
I have running xiaomi 13 pro with display 1.3 safetynet fix module
[Magisk] aygul12345:
I'm passing safetynet.

- Safetynet fix Of Display 1.3 version
[Magisk] aygul12345:
Can I make a donation to support this project?
[Magisk] aygul12345:
Please upload the full version also on github.
[Magisk] chiteroman:
I would be very grateful ❤ https://paypal.me/chiteroman
[Magisk] aygul12345:
Payment is done.

Please support this project, I will make continuous donations.
[Magisk] chiteroman:
Thanks ❤
[Magisk] shoey63:
Full 9.0 version working fine on Pixel Tablet.

Shipped with A13, updated to A14 (y)
[Magisk] Incomtus:
Hello, I am ot able to pass strong integrity

My configuration : magisk 26.3 , shamiko, play integrity fix full 9.

Can you suggest another configuration?

I have redmi note 8t with arrows os A13
[Magisk] chiteroman:
Read OP again. 👍
[Magisk] Incomtus:
I don't understand correctly I think (my English is bad) it says that I need the module if I have old Xiaomi with custom ROM.

What should I do so?
[Magisk] chiteroman:
You can't pass Strong verdict anymore.

Flash stock ROM and lock bootloader 😊
[Magisk] Incomtus:
It s the only solution?
[Magisk] DougMG:
If you want or need to pass strong integrity then yes going back to stock and locking your bootloader is the only option.
[Magisk] Oswald Boelcke:
Moderator Announcement

I've subscribed to this thread! Please refrain in future from any support or assistance related to the use of Lucky Patcher! Do not ask for such support! Any further post related the use of Lucky Patcher will deleted without further notification and the author might expect conseqeunces to the account.

Please support us by just reporting respective posts! I want to avoid to close this very helpful and important thread. Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Magisk] Incomtus:
Aaaaa aaaaa 😅😅😅😅😅noooooooo. My Uber driver seems to need that strong integrity.... No Shure at 100% but....
[Magisk] sawdoctor:
If you search the thread there's a couple of posts about Uber driver. Most people are struggling to get it working with root but I'm sure one person managed to get it working
[Magisk] Catfriend1:
The update button for that module was greyed out there yesterday and vanished today.
[Magisk] chiteroman:
I think I finally found a way to make it work on all devices, check the new version! v9.1 released!
[Magisk] esatch:
Here's a recap:

1) private fingerprint, device A; NOT passing (anymore) with OLD dev v2 and osm0sis v7

2) same fingerprint, device B; PASSING with dev v2 (not tried with osm0sis' v7 yet)

Sorry, I wrongly wrote dev2 before; it's simply the old dev v2 by chiteroman

https://github.com/chiteroman/PlayIntegrityFix/releases/download/DEV-v2/PlayIntegrityFix-DEV_v2.zip
[Magisk] sawdoctor:
Same Google play services version?
[Magisk] Fishawy:
Thanks for this.

Are you able to perhaps spot any difference between both devices? Modules, GMS, or anything that might be a culprit?
[Magisk] xcl1pse:
Maybe this one https://github.com/chiteroman/PlayIntegrityFix/releases/tag/DEV-v2
[Magisk] Bladius:
For me, PlayIntegrityNEXT works perfectly on Redmi Note 10.
[Magisk] sawdoctor:
Can people who are failing grab any logs and upload them? Will give the Devs a better idea of what is being detected
[Magisk] bakaekze:
I'm noticing a similar behavior today. Something new. Module version doesn't matter. Just same fingerprint failing on one device and passing on the other. Play services version same. Android version same. Same module as well.
[Magisk] EuK_V:
@chiteroman PIF v15.2, I hid working fp data, if needed can send PM.

Spoiler content hidden.
[Magisk] CZ.Kostra:
FP Xiaomi.eu from 15.1.2024 still works.
[Magisk] bakaekze:
Not for everyone apparently. Google seem to have added some extra checks.
[Magisk] badabing2003:
People who are failing with known working print, can you please run the following command an post the output.

adb shell "su -c 'ls -al /data/data/com.google.android.gms/app_dg_cache'"
[Magisk] bakaekze:
Spoiler content hidden.
[Magisk] EuK_V:
Spoiler content hidden.
[Magisk] blu.italia:
It is possible that Google grabs the PIFS fingerprints and blocked all these ones?
[Magisk] blu.italia:
su

:/ $ su

:/ # su -c 'ls -al /data/data/com.google.android.gms/app_dg_cache'

total 30

drwxrwx--x 10 u0_a352 u0_a352 3452 2024-01-19 02:18 .

drwx--x--x 35 u0_a352 u0_a352 3452 2024-01-24 21:13 ..

drwx------ 4 u0_a352 u0_a352 3452 2023-12-25 12:33 11D405CD9F66346CECE7F04B13ED0823DD7BB56F

drwx------ 4 u0_a352 u0_a352 3452 2023-12-25 12:34 1FF1CAAF27B5C2D89CCDAAC2580B20511F43612A

drwx------ 4 u0_a352 u0_a352 3452 2024-01-18 23:28 37FC500541014CED511312DE94C04F404D04E00E

drwx------ 4 u0_a352 u0_a352 3452 2023-12-25 12:34 5AFAE28EC5E49B4875EB3132E096617BAA2EBA6A

drwx------ 4 u0_a352 u0_a352 3452 2024-01-18 07:54 5B980760123E8D4F8398A691301E61F9BC6EB0CF

drwx------ 4 u0_a352 u0_a352 3452 2024-01-19 02:18 6D7C2BED07EDD194A1C659B6D25C19C2AC483B0A

drwx------ 4 u0_a352 u0_a352 3452 2024-01-18 05:20 9BE10F83DFFDB00C88B68F60B209E79A20D1B3B5

drwx------ 4 u0_a352 u0_a352 3452 2023-12-25 17:41 FF8387A88D6E79E16C23B7AC6189C8206742633E

:/ #
[Magisk] badabing2003:
Thank you @blu.italia @bakaekze @EuK_V @Fishawy

If you feel comfortable, please post your failing print and I'll test to see if it passes locally.

I only need one that fails for you and passes for me to troubleshoot further.
[Magisk] Fishawy:
DM'ing that, don't wanna post it publicly.

Thanks in advance.
[Magisk] bakaekze:
the general public one https://raw.githubusercontent.com/daboynb/autojson/main/pif.json
[Magisk] badabing2003:
Yeah, that xaiomi.eu print still passes for me.
[Magisk] EuK_V:
Sent in PM
[Magisk] badabing2003:
Thanks people , I don't need more prints, your prints pass locally.

So please try these steps.

1- delete the contents of /data/data/com.google.android.gms/app_dg_cache

2- Wipe Play Services data

3- Run YASNAC (yes YASNAC)

4- Now run PI check
[Magisk] bakaekze:
No change
[Magisk] LucasBS1:
Hello. Me again

I managed to pass both Basic and Device, but Root Beer Sample, Momo, and a banking app are detecting root

Could be related to the fingerprint, or the PIF module ?

The banking app is my concern: it says "debugger mode is on", even though I disabled it and confirmed to be disabled via su settings get global adb_enabled: 0

I suspect this is a generic message, and it actually detected root

Magisk 26404:

- PIF v7

- Shamiko 1.0.1 (300)

- etc

LSPosed 1.9.2:

- DevOptsHide

- HiddenCore Module

- Hide USB debug mode

- etc

Triple checked if the apps are listed on the modules above. Also, denylist
[Magisk] EuK_V:
Sorry, no luck
[Magisk] badabing2003:
Thanks for the feedback.

That theory goes out the window.

What is your device, module in use, are you using custom ROM / Kernel ...

Anyone having issues on Pixels with stock ROM / Kernel?
[Magisk] tom1807:
Pixel 6 here

Play System Update November 1, 2023

Google Play Services: 24.02.13 (190400-599553831).

PIF Fork v7, private FP since December 12, 2023

All is good.

Cheers

Tom
[Magisk] Fishawy:
For those failing, is any of you on Pixel 7 Pro and using a specific beta kernel by any chance?

I just found out that changing kernels affects this. On kernel X it fails DEVICE, and changing to kernel Y makes it pass!
[Magisk] EuK_V:
Redmi note 9 pro, Los 20, pif 15.2/osmosis fork v7. Default kernel in los20.

Edit: I have three devices which do not pass device now. All run lineageos. Is problem with kernel?
[Magisk] EuK_V:
What's that and how to do it?
[Magisk] Fishawy:
Flashing custom kernels.
[Magisk] EuK_V:
How do i know if the kernel is "X" or "Y"?
[Magisk] chiteroman:
Maybe checking device ABI 🤔
[Magisk] badabing2003:
I doubt it, before that they block Xiaomi.eu print, which is still passing for me.

They're detecting something else.
[Magisk] chiteroman:
Oh, maybe checking /proc/config.gz or /proc/version

If I'm not wrong, you don't need root to read that files.
[Magisk] GN-z11:
I actually don't use the Magisk/KernelSU modules, I just rebuild my custom ROM with patches from PPU then adapt the values to pass. Works wonders. FP found in FP's Github around the middle of Dec still works for me.View attachment 6059767
[Magisk] GN-z11:
Probably. Anyone should adapt the fake config.gz to their custom Kernels to work around. Use the one from Stock.
[Magisk] Fishawy:
Just random names mate, changing from kernel A to B.
[Magisk] Fishawy:
/proc/version is empty. What am I looking for in /proc/config.gz ?
[Magisk] frasca61:
My phone still passes the basic and devices integrity, I just made a payment with Wallet and works.

I am still with my fingerprint on December 12th and Chiteroman Dev V2
[Magisk] sawdoctor:
Same here on stock QPR2 beta, but I've not had an issue yet
[Magisk] trevtdogg:
the fact that the exact same fingerprints can be working on some devices while not working on others is strange.

could it have something to do with the API level?

I know a lot of people started changing the API level, maybe now google is checking to see if this value is in conflict with some other value that your phone sends?

eg. if you have a really new phone, but the fingerprint uses API level 24, maybe it detects something strange - and results in the print not working for your device?
[Magisk] SoyDPR:
Play integrity next works well
[Magisk] Tajnymag:
I have exactly the same 8 files and I also cant pass device with any fingerprint since today.
[Magisk] SoyDPR:
of course it works, I have been using it for almost a month, the application searches for fingerprints automatically, you just have to try until one works, you usually find one that works on the 3-4 attempt.View attachment 6059774
[Magisk] Fishawy:
I'm on stable, and /proc/config.gz is full of lines. Not sure what @chiteroman wants to look for.
[Magisk] ionut310:
The same but with a Pixel 6a.

Fork V7 and a FP from mid december still works.
[Magisk] trevtdogg:
to the people who have confirmed that a fingerprint works on one device while the exact same fingerprint doesn't work on a different device:

does the device which doesn't work now only pass basic and no longer pass device?

or does it still show it passes both basic and device, but just fail to do an expected action (eg. NFC payment, Netflix app, etc.)
[Magisk] traversone:
in my case, it no longer passes device integrity, then all expected actions fail
[Magisk] sawdoctor:
Is it stock kernel that passes and custom kernel that fails?
[Magisk] Fishawy:
Alright, I have 2 more people in a private beta testing group confirming that changing kernels of Pixel 7 Pro passes DEVICE integrity. Apparently, that latest beta messed things up somehow. I've flagged it with the dev.

Without randomly changing kernels for unrelated reasons, I would've never guessed that.

@badabing2003 many thanks for your assistance.

For everyone else still failing - perhaps check if you changed your kernel recently, and test another one as a troubleshooting step.
[Magisk] Fishawy:
Nah, all custom. One fails (recent release) and the others pass.
[Magisk] thubble:
Fingerprint from a specific model of an obscure old device that I've been using since early December (and not publicly available other than a ROM dump site for the specific manufacturer, at least that I know of) just started failing this morning.

OnePlus 9 Pro (LE2125) running the latest crDroid 10 build (Jan. 18 build) with default kernel. Haven't changed anything since the last update on Jan. 18. Latest KernelSU and ZygiskNext, osm0sis Play Integrity Fork (I updated from v6 to v7 this morning but that didn't fix it).

Don't have another device to test with. I'd normally assume that Google just banned the fingerprint somehow, but with so many other people suddenly having this issue, I'm thinking it might be related.

EDIT: I just found another print in the PlayIntegrityNEXT repo (searching manually and trying random ones), and it's working now. So maybe my (I'm assuming very rare) print really did just get banned along with a bunch of other ones?
[Magisk] manjaroid:
Pixels 5 and 7 passing basic/device running --

- stock 14 w/ Nov '23 Play update

- v7 fork w/ different print for each
[Magisk] badabing2003:
Just to be clear, you're passing?

I'm looking for people who are failing with stock ROM / Kernel on Pixels.
[Magisk] EuK_V:
I flashed custom kernel and now pass device. So what do I do? Stick on custom kernel as a workaround? Will it be possible to return to los kernel?
[Magisk] Fishawy:
I'm not sure what device or kernel you're on, but I had an issue with a specific kernel, and changing it resolved the problem. I reported that to the dev and he will be looking into it.

IIf integrity is important to you, then I would leave the passing setup as-is until clear answers are provided.
[Magisk] EuK_V:
I was on official Los20 kernel (from official firmware) and today stopped passing device. Flashed positron kernel and now passing device. Redmi note 9 pro.
[Magisk] Fishawy:
I thought it was only a Pixel 7 Pro kernel thing. Now you have me worried lol.

I hope Google isn't doing some shady plot on kernels.
[Magisk] manjaroid:
Yep, no problems with Pixel 5 in the past couple months, started messing around with 7 a couple days ago just for grins as it's going to market soon. Haven't used either phone for banking or buying lately.
[Magisk] osm0sis:
Works fine here, probably just a bad download on your side.

The last 7 pages were a real rollercoaster.

Your case sounds like something new to add to the custom/example.app_replace.list, if there's a system/system_ext/product/vendor copy of the APK. Feel free to experiment! I made it extensible for this very reason.

Your case is clearly something new in the latest kernel builds for your devices, both custom kernel and custom ROM.

I wonder if the breaking change in the kernels comes from AOSP or from the custom ROM side.
[Magisk] ehsansani:
View attachment 6059793
[Magisk] immortalwon:
Well gentlemen, it seems a lot of prints just got banned, is this the end?
[Magisk] osm0sis:
My very first print is still working here. 🤷‍♂️

If others experiencing fails aren't on PixelOS with their apparent new injection overlay apk, or Lineage and/or custom kernel and recently updated with their kernel changes, then there may indeed be some new banned prints involved too, but then let's be clear we're looking at 3 separate external issues here.
[Magisk] immortalwon:
Is your prop extractor script still the same one? Has it been updated recently?
[Magisk] osm0sis:
Doesn't need to be. Last was bug fixes back in early January, and is solid now. My format hasn't changed since v5. 👍
[Magisk] immortalwon:
I hate how I had to use Freemans pick a print script, but I don't have the time to look at rom dumps right now. I foresee they will all be gone soon.
[Magisk] linuxares:
Guys that have failures now. Tried the xiaomi.eu one on 0smosis v7?

Some info of my phone:

Pixel 7 Pro

Stock Rom

Stock Kernel

Magisk 26.4 - the stable release

January 05 OTA release

Magisk modules:

MMRL Install Tools

Music Revanced Extended

Play Integrity Fork v7

Simple Bootloop Saver

Systemless Hosts

Youtube Revanced Extended

zygisk-detach

EDIT: Noticed there is an update to Android Device Policy in the store now. Let me do a full update of all my apps.

EDIT2: still works, rebooting phone to test.

EDIT3: still passes
[Magisk] justDave:
Pixel 2/LOS 20 not working.

Pixel 7/Stock working.

Same fingerprint.
[Magisk] GN-z11:
All good here as well. I'm not sure why a lot of people seems to be having some certification errors.
[Magisk] osm0sis:
Roll back to the previous LOS build and see if it works again.

LOS wouldn't be caught dead adding anything spoofing related to their common kernel patches, so it's definitely some other change gone awry. From the latest security bulletin perhaps.
[Magisk] sawdoctor:
So far all the reports of failed prints are either Los or custom kernel? If this is correct it's actually good news as it's not the fingerprint being banned but something the ROM/kernel Devs need to change on their end
[Magisk] sawdoctor:
Probably a blank field that Google are now enforcing or something like that I'd guess
[Magisk] osm0sis:
Nah, what you're saying is not kernel related.

I'm going to walk my OP9Pro on LOS forward from the 01-01 weekly build and see if I can reproduce the issue.
[Magisk] GabbyWC:
Here's the Android version information from the custom ROM that I'm using with the kernel that it comes with. I noticed that clicking on the kernel version expands it with more detail which is provided in this screenshot.
[Magisk] osm0sis:
Read my post where I quoted you, and my next post after. You have a separate issue. 🧐
[Magisk] fbirraque:
Poco F3 (alioth)

Xiaomi.eu MIUI14 Stable 14.0.8.0

Kitsune Canary 26404 (R65A24840)

Play Integrity Fork v7 (osm0sis)

custom.pif.json (same since Nov/2023)

Still passing Play Integrity Certification (BASIC + INTEGRITY)
[Magisk] badabing2003:
OP5 LOS 13, Jan 08, 2024

Still passing.
[Magisk] GabbyWC:
I've read your responses and will do so more testing with my phone today. My mother's phone also stopped passing device integrity yesterday with the same custom fingerprint that I had been using. Her phone is flashed with official Pixel Experience Plus v12.1 which dates back to November 2022.

I'm about to do some more testing now. Based on the screenshots provided here, would adding the following lines to the custom.app_replace.list file be sufficient to avoid an injection conflict?

# PixelOS

/system_ext/overlay

The config.xml file seems to allow the overlay to be disabled but I have not tried that.
[Magisk] Umgak:
I'm on OP9Pro LOS as well, 2024-01-22 build. Zero issues with my 2023-12-01 fingerprint, which I actually sent to @Fishawy for testing. It passes for me, but fails for them.

Kernel version is 5.4.259-qgki-g62f6bf8ea712. If the change is upstream in AOSP, it hasn't been merged into the OnePlus LOS kernel builds yet.
[Magisk] osm0sis:
No... That would disable all overlays and likely break your ROM...

I guess I could extend app_replace even more to differentiate between files and directories, to support blocking this new overlay style ROM spoofing method. 🤦‍♂️

In the meantime, yes, try uninstalling any updates to it and disable the overlay in app info.

Ah, thank you for saving me the time!
[Magisk] meiser:
I have 3 device with 3 different fingerprints, all are broken. And I haven't changed anything on these devices for approx. 2 weeks.
[Magisk] Nergal di Cuthah:
But have changes been made without your intervention (specifically play services but there might be other components similarly auto changed).
[Magisk] blu.italia:
I am on crdroid with the Rom kernel. I've nothing changes this week. FP working good until today. Now I don't have device integrity anymore.
[Magisk] osm0sis:
We're still investigating, but it seems like a lot of fingerprints from older ROMs have been banned. Anyone who's seeing a full fail (i.e. not even passing BASIC) now and is on a fingerprint from Android 5 or 6 should try switching to an Android 7+ fingerprint instead.

Also we can safely say it has nothing to do with PIFS, since a lot of the banned ones aren't in the 5% of the database which is available there.

I was wondering if at some point they'd start "raising the floor" on us by removing older devices first, since it seemed like the most logical way to phase out their loose enforcement on spoofing.. So this may be the case here..
[Magisk] DivintyQQ:
As I already said, my custom prints stopped working today. They were working fine for almost 2 months. I haven't changed anything, didn't even update my custom ROM.

I'm using POCO F3 running ArrowOS 13.1 fork, build is from October 22 with October security patch.

Maybe this info helps, if it's really kernel related.

Edit: All the fingerprints I tested and are not working are from Android 8.0 or 8.1.
[Magisk] aliabda:
Hello Guys could anyone help me please?

I used the rootAVB to install magisk on the android studio emulator and then download playintegrityNEXT as well and install it but still did not fix the Play Integrity problem

I try magisk delta, other modules and lots of ways on the github, but I couldn't find a way to fix it. If anyone uses anyway in android studio, I will be grateful if you share it here I just got tired of try and fail
[Magisk] raptor22:
Facing the same changes leading to failing Device Integrity;

Pixel 8 Pro, Jan update, stock kernel: Pass

Pixel 8 Pro, Jan update, custom kernel: Fail Device Integrity

Pixel 6 Pro, Jan update, custom kernel: Pass

All three using the same fingerprint, on stock ROM, and all three on kitsune Magisk, with Play Integrity Fork v7
[Magisk] osm0sis:
Guess that 8 Pro kernel has the bad commit, report it to the kernel developer so they can hopefully help figure it out for everyone.