yashsingh1/xdaforums huggingface dataset:
[Magisk] esatch:
JFYK Tried, not working on my pyxis.
[Magisk] nicoco19:
Hello again @tom1807 and @Nergal di Cuthah @majorfigjam

I apologize for bothering you again, I can't find the: "To find out how to proceed, start with the second most liked article of all time in this thread" that you are telling me about. Is it possible for you to provide me with the second most popular article that you are telling me about or the link so that I can access it and which can help me solve my problem of an uncertified device if it Please??? (Your Samsung has a "software" fingerprint contained in 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 that your Samsung has device integrity.)

I have no ill will, but I am French and I use Google Translate in order to be able to make myself understood and understand the answers to my problem as well as possible.

Thank you in advance for your help ;-)
[Magisk] aliabda:
I want to fix Android studio emulator but I cannot. Could anyone help? I ask this couple of time. With this many people here no one even bothered to answer. At least if I'm in wrong section let me know. Everyone like you not master in these things some people like me are beginners and come here to learn
[Magisk] chiteroman:
Emulators aren't supported. Only real devices.
[Magisk] LTFOUND:
This method worked for me! I'm using PIF v7 (by osm0sis) :D
[Magisk] aliabda:
Thank you you don't know how much I appreciate that someone answered. Is there any way to fix emulators or it is just not even possible
[Magisk] Vision:
@chiteroman I'm curious, when you say, New way to spoof field values! What exactly mean that? What have the old method ?

View attachment 6060506
[Magisk] 666biker:
how to know, if device integrity fails really because of fingerprint or it is due to kernel?

Device like I have OnePlus 3T running on LineageOS 18.1 which is Android 11, has no option to put stock kernel, since last official is I think Android 9. So just thinking, if make sense to play with PIF random generator or I will never pass because of my LineageOS kernel :-/
[Magisk] nicoco19:
Hello again @LTFOUND @tom1807 et @Nergal di Cuthah @majorfigjam

Sorry for my question which is certainly very stupid for some:

Concretely, what features do I lose on my rooted Galaxy S23 ULTRA by having the status: device not verified in the Play Store???

Thank you in advance for your feedback
[Magisk] sawdoctor:
No one knows ATM as no one seems to know what Google has changed yet. Only way to tell is to change the kernel and trial and error
[Magisk] 666biker:
this is a bit challange for me, since OP3T is old device and haven't found some kernel which I should to try with LOS 18.1 android 11 :)
[Magisk] 666biker:
e. g. Google Pay wallet (nfc payments) stops to work due to this change.
[Magisk] tom1807:
E.g. Netflix, banking apps, apps which provide a pay functionality, McDonalds app (?!) and some other maybe.

Some you can't download because Play Store not certified.

As for your other question, scroll up to the top, on the right side you see a header, Top Liked Posts. Select All Time and you are presented with the second most liked post of all time in this topic.

Cheers

Tom
[Magisk] nicoco19:
Hello @666biker ,

Thank you for your response and is it only this functionality that we are losing?? (Google Pay wallet (NFC payments) stops working due to this change.)

Because at one time I found myself blocked from downloading certain applications from the Google Play Store (e.g. Disney application for children) and the only solution I found to get around the problem was to install the Yasnac application and the Play Integrity Fix_V9.8 module, after doing so I was able to install the Disney application for my children from the Google Play Store. Is this feature blocked again as Google Pay wallet (NFC payments) stops working due to this change? Are there other blocking features?

Thank you in advance for your feedback and help.

Nicoco19
[Magisk] tom1807:
Which Play Integrity Fix v.9.8? Do you refer to the version of @chiteroman or any other source?

Cheers

Tom
[Magisk] 666biker:
If you fails at device integrity check, then all google apps which requires this verification will fails, or not able to install from play store as you mentioned. me personally missing google pay feature, other things like disney, netflix.. i am not using yet
[Magisk] Oneplus#:
It was reported on the official Pif group too, people that are using a custom kernel are not passing device integrity anymore.

Pif is not working for them since 25/01/24.

This is happening only for some people, not all!

AS FOR NOW :

- some pixel stock kernels

- some sultan kernels

- lineage os

Any ideas?
[Magisk] Slim2none4u:
Kirirasura On my P7Pro passing Passing basic and device for over a month now.
[Magisk] kocsogfax:
Xiaomi 13 pro, xiaomi.eu rom, kernel: 5.15.74-android13, with chiteroman/PlayIntegrityFix v14.0 FAIL for basic and device for all my custom pifs. It's worked since 01 December.

Without PlayIntegrityFix: Fail for basic too.

But updated to chiteroman/PlayIntegrityFix v15.3.4 - PASS basic, fail device for all my custom pifs.
[Magisk] Emmes:
try using the pf from the xiaomi module, that is the only one that works with my xiaomi.eu rom (use pixeflasher simply for that)
[Magisk] kocsogfax:
Tried pf from xiaomi module, only pass basic too.
[Magisk] Nekromantik:
Becoming difficult to find fingerprint now using play integrity next or pixel flasher. :(

These still best way to find prints?
[Magisk] Emmes:
maybe i installed the module.apk as well, for me it worked then
[Magisk] :
4 devices with LOS working perfectly (e.g. I could install Netflix) with stable magisk 26.4 (or lygisk), @osm0sis v6/v7 and fingerprints from @TheFreeman193

Thanks again, guys.
[Magisk] osm0sis:
That's because chit's PIF doesn't actually work for Xiaomi.eu, whereas my Fork v7+ does. 👍
[Magisk] Oneplus#:
🔧 [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

I tried on those devices your fork without success can you help me?

Good fingerprint, zygisk enabled.

It works on some lineage os builds but not on all.

Tnx
[Magisk] osm0sis:
Not clear to me what you're saying. You replied to me about Xiaomi.eu but are talking about devices that don't have that ROM.

About the current kernel issues: I'm sure we're all working on it for everyone:

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

About the current new print bans: Go find a new print. It worked for me:

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

The problem is everybody mixing these 2 things together.
[Magisk] changhuapeng:
Use PixelFlasher and test with Xiaomi.eu PIF, if your print is failing due to kernel issue then you won't pass device integrity using that print.

Follow this tutorial here: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-179#post-89189970
[Magisk] Oneplus#:
Sorry for my bad English, I'll write as best as I can.

Since the 25/01/24 your fork and the chiteroman's one stopped working on some devices.

The fp is valid.

Today I've tested the module on some devices, they have lineage os, some of them passes device integrity but others no.

For example on this build device integrity doesn't pass "https://ibb.co/BzfdWgm"

On lineage os with Yuki kernel all is good.

Sorry for the quote on the eu message, I saw your name and I quoted you. Since you were the person I wanted to talk to.
[Magisk] 666biker:
this is currently my problem, I am not sure, if it is because of LOS 18.1 kernel or wrong print. Since there is no way / knowlwdge to find root cause for the integrity check fail ( fingerprint or kernel or both)
[Magisk] chiteroman:
adb shell md5sum /proc/config.gz (as you can see, you don't need root)

c4d5137e519181837d696d406dcffb66 /proc/config.gz

std::string str = "c4d5137e519181837d696d406dcffb66";

(DroidGuard sends to server...)

if (str == [ORIGINAL KERNEL CHECKSUM]) return true;

else return false;

Kernel developers should spoof original kernel config, like this: https://github.com/aosp-clhex/kernel_xiaomi_vayu/commit/4c8b7c8cd4eb37230a876807f42214a4345d6194
[Magisk] changhuapeng:
Xiaomi.eu PIF is working. Test play integrity using that print and you'll know immediately whether your kernel is the root cause to your problem.

Kernel (no issue) + Xiaomi.eu PIF = PASS device integrity

Kernel (has issue) + Xiaomi.eu PIF = FAIL device integrity
[Magisk] badabing2003:
If you're testing xiaomi.eu print (which is known not to be banned yet) and are failing, then your failure is due to kernel or misconfiguration / wrong module use.
[Magisk] Emmes:
your fork works with the xiaomimodule fp, yes, but not with my other fp that work with my other device.

Here are the results of my testings:

Poco X3 Nfc - surya

- xiaomi.eu non rooted with module: passes device integrity

-xiaomi.eu +ksu +PIF or PIF-Fork passes device integrity only with module fp

-xiaomi.eu +magisk +PIF or PIF-Fork passes device integrity only with module fp

-crdroid +ksu +PIF/Fork does not pass device integrity

-MIUI14 +ksu +PIF/Fork passes device integrity with every working fp!

Poco F5 (main driver, didnt test that much with it)

-greeshan MIUI Mod (based on MIUI ID) +ksu + PIF/Fork passes with every working fp
[Magisk] kocsogfax:
I don't know why, but my xiaomi 13 pro pass device again after this:

1. Remove chiteroman/PlayIntegrityFix v15.3.4 module from magisk

2. Install XiaomiEUModule_2024.01.15.apk

3. fail for basic and device

4. install chiteroman/PlayIntegrityFix v15.3.4

Pass basic and device again! :)
[Magisk] osm0sis:
Some prints work for some devices and not for others, that's just how it is. Nothing to do with the module.

PIFork v7 is confirmed working on Xiaomi.eu by many users, so I presume your testing wasn't with v7.
[Magisk] osm0sis:
First of all, on my Pixel:

:/ $ md5sum /proc/config.gz
md5sum: /proc/config.gz: Permission denied
1|:/ $

Second of all, then why does going back to a December custom kernel from a January one work around it? There's clearly a commit in there at fault.

And I don't see any mention of Play Integrity in Sultan's commit message (from October). Looks like it was more preemptive than anything.
[Magisk] 666biker:
so my data are: Oneplus 3T on LOS 18.1 (Android 11, rooted with Magisk v26.4, bootloader unlocked), PlayIntegrityFork v7 module installed, Zygisk enabled, force deny list enabled, (Play framework, Play services, Play store, Gogle Pay set to hidden)

My steps:

1. Use PixelFlasher

2. Get Xiaomi PIF

3. Press "smart paste"

4. Update Json

5. get random Freeman PIF

6. now Smart paste or just Paste?

7. update json

8. integrity check

I tried these steps for several random PIFs, and for now only basic integrity pass, device integrity fails.

Missed I something or made some step wrong?
[Magisk] Emmes:
i don't think so, with MIUI + ksu +pif, all of my 42 fp work, where none of them, 0/42, worked with xiaomi.eu/crdroid +ksu/magisk +pif/fork.
[Magisk] osm0sis:
No I can guarantee you that some only work on some devices, we've seen that in our testing all along.

Again, PIF never worked correctly on Xiaomi.eu, and my PIFork has it confirmed fully working in v7.
[Magisk] Slim2none4u:
My mods.
[Magisk] Emmes:
i used your v7 all the time while testing, i tested PIF from chiteroman and yours the Fork. it doesnt depend on the device, it depends on the ROM. Because the same fp is working on MIUI with v7 or PIF, but not on xiaomi.eu or crdroid, doesnt matter if i use your fork or chiteromans.

EDIT:

after fresh install, i deleted module inject (pm uninstall -k --user 0 eu.xiaomi.module.inject), and after that every fp worked again on xiaomi.eu
[Magisk] Emmes:
if you don't need your stored data on your phone, you can test if it is working with the stock rom and magisk. Maybe it works then and then you know that the problem is los18.1
[Magisk] osm0sis:
In that case it suggests that there's a new field or property to be spoofing, because it's the ROM's unspoofed ones making the difference. PIFork v7 definitely works on other Xiaomi.eu devices, @fbirraque and @CZ.Kostra can attest to that.

You should then compare full "VERBOSE_LOGS": "100" json, logcat | grep 'PIF/' from Fork v7 on both ROMs to see if you can figure it out.
[Magisk] 666biker:
latest available stock rom is Android 9 :) only with support of LineageOS team OP3T is alive with latest possible custom rom as Android 11 and latest monthly security patches, so only wait probably for some general fix, if something like that happen, or time to look for some new device after such long OP3T using, or ignore this integrity check and dont pay with nfc 😁 other apps works
[Magisk] :
Denylist is not necessary. Hiding magisk is also not necessary, btw.

By "PIF" you mean fingerprint?

Why do you get a random fingerprint after downloading the Xiaomi fingerprint?

I have a working Tab S2 LOS 18.1
[Magisk] changhuapeng:
These are the correct steps:

1. Use PixelFlasher

2. Get Xiaomi Pif

3. Smart Paste Up

4. Update pif.json

5. Play Integrity Check

If it passes device integrity, then your kernel and set up are fine and you can proceed to the next series of steps listed below. If it fails device integrity, then you will have to try other kernels and repeat the above steps.

Now you can choose to stay with Xiaomi.eu PIF, or to find a new random PIF that is not as widely used that still passes device integrity. If you choose to stay with Xiaomi.eu PIF then you don't have to do anything but simply repeat the above steps whenever you start failing device integrity.

If you would like to find a new random PIF then follow these steps:

1. Use PixelFlasher

2. Get TheFreeman193 Random Pif

3. Smart Paste Up

4. Update pif.json

5. Play Integrity Check

6. Repeat step 2-5 until it passes device integrity and then click Favorite button (the heart) to save the new print in your favorites
[Magisk] 666biker:
I am failing after first part unfornunately

1. Use PixelFlasher

2. Get Xiaomi Pif

3. Smart Paste Up

4. Update pif.json

5. Play Integrity Check

only basic pass on my device.
[Magisk] Flr Power:
15.2 doesn't work properly on my device (vayu) and other devices as well...
[Magisk] Ludo13B:
Hey,

Thanks for the module!

I don't understand why I fail the device integrity test (TB Checker) or CTS profile match - HARDWARE_BACKED (YASNAC).

On Samsung S20 (SM-G980F), with Magisk alpha, Shamiko and Play Integrity fix (v15.3.4, but same with 15.2).

Do you know what I can check to pass this test?

Thanks!
[Magisk] Slim2none4u:
This type of comment helps nobody in any way what so ever. Give some info guy ffs
[Magisk] :
Try https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89233489
[Magisk] :
What fingerprint are you using?
[Magisk] 666biker:
this I already tested, same result, just basic integrity pass
[Magisk] changhuapeng:
Unfortunately, there's nothing you can do to pass device integrity right now except going back to an older kernel build or switching to another kernel.
[Magisk] Kkjin:
Custom (pif)

Can you give me the information?
[Magisk] osm0sis:
That wasn't a bug report from @Flr Power, that was a reminder. 😛

Since this thread has once again turned into a constant churn of Telegram-esque bullsh*t with nobody searching/reading back, and collective goldfish memories...

Here's the info: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-496#post-89298308

😉
[Magisk] nicoco19:
Hello again @tom1807 and @Nergal di Cuthah @majorfigjam @666biker

Indeed, when I go to my Play Store and search for the Netflix application to install and test it, it gives me a message saying that it is impossible to install it on my device from the Play Store.

On the other hand, I think there is another solution but less secure in terms of security, it must be possible to download versions of software like Netflix on alternative application markets (Aptoide for example)??? By downloading the application that interests me like Netflix on Aptoide and allowing the installation of applications from unknown sources, I think it should work???

I have another question, do you think that the next modules of Play Integrity Fix and also of the Yasnac application will allow over time to resolve this device integrity problem and to be certified again with Play Google Store to directly download applications like Netflix for example???

I admit that rooting my phone seemed much less complicated than using Play Integrity Fork and its tutorial to find a fingerprint to spoof. So I don't prefer to get started because I admit that it doesn't seem easy to do.

Thank you in advance for your feedback.

Nicoco19
[Magisk] Sheist!:
Safetynet servers are active until June. It passes both and my bank apps work, while device integrity started failing with the recent fingerprint reports. Play now shows not certified. KernelSU vs Magisk might not make any difference since the issue now is fingerprints.
[Magisk] nicoco19:
No real positive solutions to come as a result.
[Magisk] HippoMan:
You could try a number of other FP's to see if perhaps any of them work better than your current FP. That could at least shed some light on the "fingerprint or kernel or both" question.
[Magisk] 666biker:
regarding fingerprints I tried I thing almost everything what was suggested here, many random fingerprints or try to get some from old stock rom years ago, without any positive result, so I'm waiting if some solution will be find or I will live with that until I change my device to some new one.
[Magisk] HippoMan:
OK, I understand.

Knowledgeable people with lots of Android and general software experience are investigating this recent phenomenon. Over time, the cause and (hopefully!) one or more solutions will be uncovered.

It does seem like it might be related to some kernels. If so, that would be sad, because it could mean that we will now be more restricted concerning kernel choices, and also possibly even concerning custom ROMs.
[Magisk] 666biker:
finger crossed :)
[Magisk] sawdoctor:
Has anyone actually

It doesn't seem to be an "age " issue with kernels as several custom kernels are working. It's more likely a missing field that's being checked for now like osmoSis said. Once we figure out the extra check pretty sure it can be added
[Magisk] unicunic8:
Currently google is hostile to the shamiko, all the ways the shamiko works are being blacklisted by google
[Magisk] majorfigjam:
Not true - I have Shamiko 1.0.1 with TJW Canary 26404, and (lucky for me) I'm not having problems.
[Magisk] Ludo13B:
Hey @alchemon , thanks for your help.

I did understand (a little late), it is probably because I did not implement the pif.json file.

So I read a little, and I have now the information I need from my old Galaxy S7.

I can't find the correct template for the @chiteroman Play Integrity Fix pif.json.

Can you tell me if I have to add something or if it is correct and I can continue the process?

{
"MANUFACTURER": "samsung",
"MODEL": "SM-G930F",
"BRAND": "samsung",
"PRODUCT": "heroltexx",
"DEVICE": "herolte",
"BUILD_ID": "XXXXX",
"FINGERPRINT": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"SECURITY_PATCH": "XXXXXXXX",
"FIRST_API_LEVEL": "23"
}

Thanks!
[Magisk] Ludo13B:
Ok, with the pif.json, the CTS profile match - HARDWARE_BACKED (YASNAC) is now solved (CTS profile match pass), but Play Integrity API Checker has always MEETS_DEVICE_INTEGRITY fail and TB Checker Device Integrity Fail.

Do you know what I can do to fix that?

Thanks!
[Magisk] Nergal di Cuthah:
If you don't pass device, fingerprint json needs to be changed
[Magisk] Nergal di Cuthah:
Or below if on mobile

And nowhere if you're using the xda app
[Magisk] 666biker:
Play integrity check was executed after trying the xiaomi.eu PIF before starting random PIF generator, only not mentioned in steps, just forgot to mention it
[Magisk] badabing2003:
You reported earlier that it failed with xiaomi.eu print.

Which means no amount of Get TheFreeman PIF is going to help you find a working print.

You have to pass with xiaomi first.
[Magisk] 666biker:
yes, that is true and I got that understanding after my trials :)
[Magisk] giacomowrc:
Follow the instructions to find custom pifs in pixel flasher.
[Magisk] 666biker:
I haven't try stock, because latest stock is Android 9 and my current LOS 18.1 is Android 11, and did not find any kernel alternative for this my current setup.
[Magisk] CityKev:
What is the consensus about the Play Integrity issue actually making custom ROMs, root etc no longer viable for primary devices?

I have several tablets with custom ROMs and either Magisk or KSU (my preferred option when available) but they are just for entertainment/general use. I don't need to pass Play Integrity on them for the things I need. However, my phone is my primary device and I have two essential applications:

Firstly, my season ticket for Manchester City is digital only so Google Wallet is a must. I cannot have a situation where I get to the stadium and I can't access my ticket.

Secondly, I have several banking apps and I like the option of having access to funds whilst I'm out and about or on holiday or having the nuclear option of freezing my cards if stolen or lost.

To me it seems that the current situation is so hit and miss with posters thinking that having a working fingerprint for a couple of months is a great result and many others finding that theirs no longer works. This isn't a sustainable scenario in my view. I'd be interested in what other posters think about this.
[Magisk] sawdoctor:
If there's no alternative kernel for you to try then unfortunately there's nothing anyone can do to help you until the Devs find out what Google have changed/are looking for
[Magisk] simplepinoi177:
So...the mass banning of fingerprints from Google started in November. It was very hectic at that time with PIF releasing 2 or 3 times a week with an embedded fingerprint; and, of course, with tens of 1000s of users all using the same making it inevitable that it will get on Google's radar fairly obviously.

So by the end of November and into early December, the option was given to implement one's own custom fingerprint (to mitigate Google banning from tens of 1000s of users all sing the same one) and urged/insisted upon.

Since then, those who have opted for that method (as opposed to all using the same FP from the xiaomi.eu custom ROM [that chiteroman had opted to do in the later versions of PIF before stopping]) have had theirs consistently pass for more than a month. It is only very recently that that method proved mass fails -- but in fact there are still many of us that still have theirs working since December or November (mine is from Dec. 8)! So while I think we still have to see what Google has in store for banning fingerprints and/or how the leading modders/developers in the community will develop improved methods, I do believe history has shown & proven that it is somewhat a "sustainable scenario", it's just a recent hurdle has just propped is all.