yashsingh1/xdaforums huggingface dataset:
[Magisk] Bonoboo:
Reminder: to be notified in advance about banned fingerprint (and to take cash / card) use GPay Checker
[Magisk] V0latyle:
Were you failing all 3 or only passing Basic?

I tested this theory on my Pixel 5. Used a print that only passes Basic, still able to receive phone calls.
[Magisk] osm0sis:
gki can't be, and dirty wasn't before but I'll check it again. 👍

Could make sense with the above conflicting openela ones as well.
[Magisk] SOCOM-HERO:
lawsuit time if only there were a class action in Europe this would end this bs from google. I would highly recommend you file an FCC complaint regarding this at the very least. Free and easy for a user to do. I did it myself when AT&T stopped support for certain devices that didn't have 5G radios which led to my calls being redirected to their support center (EVEN WHEN I TEST DIALED 911) and I got a call from their President's office the NEXT DAY resolving it.

Slightly different than your story here, but very similar grounds for right to ownership/repair and usability. I wish Louis Rossman would cover this.
[Magisk] GabbyWC:
The latest public fingerprint from Xiaomi.eu (obtained with autopif.sh) is not passing device integrity on my phone with a January 2024 build of PixelOS 14. The kernel string is as follows:

4.14.336-YAMK-LA.UM.9.1.r1-15500-SMxxx0.QSSI14.0

For those who might wonder why I don't update to a newer build of PixelOS, my Redmi Note 9 Pro has multiple hardware defects and will be replaced with a Poco F6 next month.
[Magisk] delicalouison:
my kernel string matches -openela and PIF is not working

The error I get is that checks cannot bind to the service in the play store (CANNOT_BIND_TO_SERVICE). Is this the error caused by a banned kernel string or is something else missing in my setup?
[Magisk] Red_Acid:
Mine is similar and also not working: 4.14.340-openela-perf-g23fae8dac89a.

I'm running crDroid 10.5 on OnePlus 7T.
[Magisk] JonanomisK:
I'm on evox on a pixel 5 and mine isn't working despite all of my troubleshooting. uname -r returns 4.19.306-ge10e810df8f0 for me
[Magisk] notanSU:
Anyone know if PIF works on lineage os 21/ android 14?
[Magisk] Adiker:
Aospa on OnePlus 9 Pro passes just fine, but PixelStar on Poco F4 fails. Probably kernel or ROM issue.
[Magisk] chiteroman:
What kernel is that 🤔
[Magisk] samhhmobil:
Yes, it works for me (los21/a14, PIF 15.9.9, running on "pioneer").
[Magisk] DarkEagle82:
PixelOS 14 with uname -r -> 4.14.343-openela-REVUELTO-//3eff55750f

Not working
[Magisk] D€INOS:
Serious developers like EvoX, Crdroid shouldn't have a vanity kernel string after google starting to ban certain kernels.
[Magisk] ComradeWave:
PixelOS 14 (QPR2) with uname -r -> 5.4.242-QuicksilveR-lisa-07bc678b doesn't work, i'll try building a kernel with another name, i'll report back soon
[Magisk] sawdoctor:
All thier work is open source so anyone can fork thier repo's and build themselves with whatever strings they want can't they?
[Magisk] papasso:
Hint: https://github.com/chiteroman/kernel_vayu/releases/tag/1
[Magisk] D€INOS:
Yeah it's open source. But I think you missed the point, i.e., why have kernel string at all.
[Magisk] chiteroman:
My kernel 🥰
[Magisk] papasso:
Yeah ;) With your first kernel I have experienced the 'ghost touches' effect, but with this one everything seems fine. Highly recommended ;)
[Magisk] IBq536XJaWThZsjwwwApTUiV:
Doesn't that check the database, which lags behind the Play Integrity status? Is there an app that notifies directly on Play Integrity status changes? For me, Google Wallet still showed "Your phone meets security requirements" yesterday when the fingerprint got banned.
[Magisk] BunnyPig1:
This is so fascinating.

Thank you for taking your time answering my question, sorry I can't really respond more in depth but I barely know anything regarding all of this. Thank you all for the great work you do.
[Magisk] zgfg:
Some don't mind. They don't make the ROMs for Google thingies like Wallet, RCS
[Magisk] zgfg:
The best reminder: I open this thread on XDA before going home from work and I see that I'm already several pages behind

Then I know, something has happened, and what😬
[Magisk] osm0sis:
Seems like regardless of many having normal/unbanned kernel strings, EvoX, crDroid, and PixelOS all are being blocked somehow.

PixelStar looks like a fork of PixelOS so likely in the same boat as the above 3.
[Magisk] crypticc:
Maybe by identify ROM/kernel vs PIF G* can identify comprised PIF? I'm guess what I mean is if bank X with method Y can identify comprised device, then it's not too much of a leap of faithv to imagine G* to implement that, look for PIF, say Z, and then ban ALL PIF Z.

It's why I was asking, what happens to the owners of real devices Z. Did they have a working device and suddenly it's not working when their PIF in circulation got banned?
[Magisk] osm0sis:
Again. Not how it works. FAQ #2.

https://xdaforums.com/t/pif-faq.4653307/
[Magisk] albinoman887:
@osm0sis you can add SigmaDroid to the list of affected custom roms. i'm the lead dev for sigma and cant seem to pass device integrity on husky (pixel 8 pro)
[Magisk] D€INOS:
Yeah this is true , but it's bad practise as it creates thousands of unnecessary tg messages on their channels of new and/or uneducated users spamming "safety net fails, help!!!"
[Magisk] makeyourself:
I'm passing on Vayu (Xiaomi Poco X3 Pro) and failing on Redwood (X5 Pro). LineageOS on both devices. There's a few differences, the Vayu one is running a custom kernel and this is reflected in the kernel string. The Redwood one is running the stock Lineage kernel with kernel string (edit: actually, not giving away the kernel string but it's fairly generic). Also the LineageOS on the Redwood device is unofficial because there is no official Lineage for that device. The Vayu one is on official Lineage. The Android version on Redwood is Android 14 but on Vayu it's 13.

No idea if any of those things are relevant, or if it's something else! Also, both devices were passing yesterday.
[Magisk] purgy:
Tbh there shouldn't be any expectation that a custom rom would pass google checks, and anyone unlocking their bootloader and flashing custom fw should be aware of that on some level...
[Magisk] HippoMan:
The Googlefrinchian Telephone Sanitizers would be extremely foolish to not be paying attention to this thread and the related threads.

Of course we know that their ancestors, the original Golgafrinchians, were quite foolish in wanting to defoliate the Earth's forests in order to increase the value of the leaves that they were using for currency at the time. However, today's Googlefrinchians are at least very slightly less foolish than that, so *we* would be foolish to not expect them to be paying attention to all the things that we discuss here.

So let's not discuss specifics about what works and what doesn't work here in these threads.

And let's revert to private conversations for sharing meaningful technical info, where we at least can make an attempt to screen out suspicious potential Telephone Sanitizers in disguise.
[Magisk] aiute_111:
Maybe my next device will be an iPhone
[Magisk] Nergal di Cuthah:
Because it's not locked down and doesn't need a (often device feature breaking ) exploit to "make it your own". Right?
[Magisk] aiute_111:
iPhones can be used longer than Android, and the minimum system version restrictions for running APPs are much better than Android.

In my country, some bank APPs have been restricted to a minimum of Android 10 to run.

However, At the same time, iPhone8 can run perfectly
[Magisk] HippoMan:
I managed to get a keybox to work properly with my wallet in which I keep my payment methods!

No more hassles with Play Integrity when I try to pay for things, and my wallet is secure in the keybox.

View attachment 6105936
[Magisk] bdr127:
I can't say that I checked repeatedly or even checked in between each reboot or when I got each "Google Fi not fully activated".... I know I checked it when I first read this thread yesterday, and at that point I was passing only Basic. No idea what the deal is.
[Magisk] mike.s:
Since it's so critical, they should simply revert to stock and relock their bootloader.
[Magisk] mike.s:
LOL. If someone breaks their phone, they own both pieces. It's on them, not Google.

It's really hypocritical to say both "Google DOES NOT OWN the phone." and then turn around and say you can sue them when you change something and it breaks.
[Magisk] Paz9:
Someone give the Dev a beer

All working after last update
[Magisk] Flr Power:
What dev and what update is this?
[Magisk] Paz9:
Pif @chiteroman just sent a beer your way! Love your work, only reason I put up with keeping my BL unlocked
[Magisk] joeyhuab:
🔧 [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

Check my post a few pages back. My kernel on Evo doesn't have a vanity string. Dirty was only added after compiling the kernel with KSU modules.

Anyways. I did what @osm0sis asked and removed all persist.sys.pixelprops and replaced with persist.sys.goggle or persist.sys.pp and it still doesn't pass device. Tried with or without KSU.

Our new Evo X is based on LineageOS so afaik it should pass like some replies here but I'm guessing some ROM properties are now being checked as well?
[Magisk] XDM inc:
mine just broke 2 days ago, now im cts failing and google pay no longer works one my pixel fold
[Magisk] D€INOS:
Google really screw over custom ROMs

more and more sadly 🥴
[Magisk] Nergal di Cuthah:
Yes clark print and some private prints were banned in the past few days. Get the new public print or update to the newest PIF or scour for a new private. Some custom kernels may have been added to banned kernel list but that's still in testing

Want more? Read the last two days of posting and write a clearer and complete post
[Magisk] joeyhuab:
I've been reading several stuff on telegram regarding Paranoid Android (AOSPA) and most reports are they got stuff passing again by installing pif module (mostly chiteroman's) and the common denominator seems to be that their builds are signed? Not sure if that's gonna be a factor.

My Evo test builds are currently userdebug so I'm not sure if that's a factor as well. Really exhausted trying to find what's tripping on custom ROMs now.
[Magisk] bakaekze:
Currently none due to the crappy integrated fix on that rom messing with the module and not working itself
[Magisk] Dark Warlock:
Can this fix be removed by Magisk module or RW system?
[Magisk] bakaekze:
Not that I know of
[Magisk] thesingular:
It's quite possible, but I don't really know. So I won't be able to help with that. But hey, at least the device is certified now and you should be able to use Gpay again.

Also, I'm asking a bit too late but, what is your Play Store version? Mine is currently "38.1.18-29 [0] [PR] 575289603".

Lol I made a typo in the version number when I posted it(fixed already)
[Magisk] Difusal:
I'm on the same boat as other users... Today, my Google Wallet started complaining with

Something must have changed recently because I was able to use Google Pay yesterday night. I am on the EU MIUI rom, but I have not updated it (nor did it update automatically).

Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY]
Build fingerprint: Redmi/ruby_eea/ruby:13/TP1A.220624.014/V14.0.6.0.TMOEUXM:user/release-keys
Brand: Redmi
Device: ruby
Model: 22101316G
TestId: dGVzdGluZy1mMzMyOWNmYi0yZDYwLTQyNjctOTI3NC1kYzBkY2Y1Y2IxMzI=

Banking apps are not complaining though... Just Google Wallet. SafetyNet and integrity checks are passing.
[Magisk] HippoMan:
My PlayStore version is the same as yours.

And yes, GPay and Wallet work fine, as long as I disable AdAway.
[Magisk] thesingular:
So it's not the kind of modification that prevents it from being updated.

Hooray to that! 🥳
[Magisk] HippoMan:
Yes, but it's a PITA to have to enable/disable AdAway just to be able to use Wallet.
[Magisk] zandatsu06:
Ohh no, i checked mine and now i have the same issue, i only passes basic integrity
[Magisk] osm0sis:
Yeah, I agree, it's frustrating that the commit history and releases continue to get wiped out for whatever reason... It makes the fast paced development here feel even more chaotic, and almost impossible to track regressions.

If kdrag0n's doesn't break the camera and Displax's does, then compare the service.sh, post-fs-data.sh and system.prop for those two (should be easy since they're direct forks with common commit history intact). You could even go so far as to copy those files into the PI v12.1 module directory and see if it fixes things for you.

Countdown until Google bans the new fingerprint? 😆

Keep reading ... 😛
[Magisk] thesingular:
It's weird that those checks pass now. Perhaps try waiting a bit to see if Wallet fixes itself?
[Magisk] cbendan:
Just for your info.

- Oneplus 11 (2449), OOS13 A10.

Magisk 26.3, Zygisk-LPosed 1.9.2, Shamiko 0.7.3 (1.7.4), Displax USF 2.4.0 2.0.

- Basic ok, CTS fail.

- All my 5 banking apps working 100%, only one of them not updated.

- Google wallet working.

- Google Play certified.

I don't move to PIF because all is working till now.
[Magisk] thesingular:
Is it due to AdAway itself or the hosts file it uses?
[Magisk] jesusmolon:
Xiaomi.eu will not do anything to solve this problem

We will have to look for another ROM for our Xiaomis

View attachment 6030841
[Magisk] thesingular:
😂🤣😂🤣

On a more serious note, the passing SafetyNet and Play Integrity checks are a major feature of this ROM (in my opinion). But calling it not a bug when such a feature is broken is a bad move, technically or not. Also, whether they like it or not, they'll have to fix it and they'll have to do it sooner rather than later if they don't want to lose their supporters.
[Magisk] voetbalremco:
I like Xiaomi.eu but that dev is so ignorant...
[Magisk] aygul12345:
I have installed this module 9.7.2 and there was a popup with something with the module: ''Shamiko" '' if you use banking etc.etc. etc'' Can't get that notification or memo, so I'm searching for that kind of memo before updating it. Could you retrieve the memo what it was?

EDIT: I will make a donation to your nice work. Keep updating this module.

Payment done: View attachment 6030843
[Magisk] sawdoctor:
Is adaway a device specific thing? I've not disabled it but wallet is showing as working but haven't actually used it today
[Magisk] Nheo12:
I have VoltageOS, Magisk27, PIF 15.9.9, N0kernel. In /data/adb have not pif.json

And DEVICE integrity not passed.

Does it work with this kernel and system?
[Magisk] wilsonhlacerda:
I may be wrong, but ALL success cases that I saw was:

stock

AOSP

LineageOS

And now you mentioning signed Paranoid.

Is it really that? If so, what can we say that they have in common (not props, technically) that could make Google endorse them but not the others?
[Magisk] joeyhuab:
It's not really endorsing them in a way, but more like being exempted. And now that I think deeper, it may be gapps related too? Since AOSPA and LineageOS doesn't have gapps by default, some or most have passed again with the new modules. Evo and other aosp custom ROMs mostly have gapps and still fail with the latest module. I might be overthinking, though.
[Magisk] bondik77:
https://review.lineageos.org/c/LineageOS/android_build/+/387096
[Magisk] Brava27:
Donated to @chiteroman This guy is the best!
[Magisk] intel_core_i7:
I thought crdroid didn't come with gapps by default, unless the maintainer decided to include it?
[Magisk] Frenik:
Sadly no luck on these 2:

Poco X3 Pro running ArrowOS v12.1|GAPPS with kernel 4.14.323-NoGravityKernel-v3.5.0

Redmi Note 9 Pro running ArrowOS v12.1|GAPPS with 4.14.295-Etherious-LA.UM.9.1.r1-12000.01-SMxxx0.QSSI12.0
[Magisk] samhhmobil:
Redmi Note 9 Pro is a "gauguin" variant, right?

I'm running Mi 10T lite (even "gauguin") with LineageOS20/A13 (and the included kernel) with MindTheGapps... and everything works.

So it seems, there is something specific in your configuration.
[Magisk] D€INOS:
This is true
[Magisk] Xorio71:
What is the commit about?
[Magisk] adinechin:
I'm lost, I'm on LineageOS 21 on Redmi Note 10 Pro (sweet), with latest chiteroman pif module and playcurl.

Right now I have a Google Pixel sailfish fingerprint, but it still does not work for me...

I'm using kitsune magisk, perhaps the issue is here ?

In addition to that, the checking apps are all saturated !
[Magisk] zgfg:
Just to make sure - have you tested without playcurl BUT with the original pif.json that is installed by PIF module (you can get it out from the installation zip or from PIF GitHub)

Same sailfish but details like formatting the json file could matter
[Magisk] Frenik:
No it's miatoll but it seems Lineage vs others makes the difference.
[Magisk] zoisa:
When i installed crDroid 9.15 i needed to install BitGapps, so, does it have gapps?
[Magisk] adinechin:
Yes that was my initial configuration, but I lost Play Integrity at least on my work profile and apps yesterday, and since then I'm trying different configurations....

I got back to my initial configuration right now following your message, but still no integrity on my work profile...

Which magisk are you using ?
[Magisk] joeyhuab:
Not all crdroid builds have gapps. I'll edit my statement. Besides, this is besides the point of the topic.
[Magisk] wilsonhlacerda:
It works with Kitsune. Girlfriend has a device with it.

Use Play Store's test on its developer mode enabled.

Do this:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] zgfg:
I'm using PI Fork and private prints...
[Magisk] Aryannn999:
It does not seem to be banned as it passes fine here.
[Magisk] osm0sis:
Because he burned another print for you? 🙄

I don't see him out here trying to troubleshoot the new custom ROM problem like me and @joeyhuab. 🤷‍♂️
[Magisk] Brava27:
Just a coffee. General help really. I like Halifax. I was there last summer.
[Magisk] Cristiano Lira:
Maybe the problem is user-debug kernels? I am waiting to have my phone bl unlocked but am watching this thread and users with it (not) passing could tell if their kernel is user-debug or not. Doesn't seem to be a kernel name issue.
[Magisk] RAZINARES:
I don't think it would make any difference. Some people have already tried user build.
[Magisk] adinechin:
Still no luckView attachment 6106026View attachment 6106027View attachment 6106028
[Magisk] zgfg:
Module injects the spoofed user-release FP
[Magisk] mrspeccy:
I can confirm that 15.9.9 works on a Xiaomi device (moonstore) running stock Android 13 and Kitsune.
[Magisk] fbirraque:
Yeah, sure
[Magisk] Machintosh@xda:
View attachment 6106030

I'm using A Modified Xiaomi Hyper os rom , with Chiteroman's latest fix and playcurl. Its still passing for me. But in AOSP, it fails. Does all OEM based roms are passing ?
[Magisk] osm0sis:
Did you try doing a build with PixelPropsUtils completely gutted out? The ROMs that pass are ones that don't have it, so it might be something else intrinsic to it that they're detecting.
[Magisk] Lobod:
My brother has pass Device on PixelExpirience 13 (spes).
[Magisk] osm0sis:
That's not using the latest PixelPropsUtils source though, since PE is dead.
[Magisk] Vgl12258:
I also thought about this, I removed all the spoof related to PixelPropsUtils and signature spoofing implementation, as well as safetynet properties etc, and only let the lineage one signature spoofing (https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/383574) but no success unhappily.
[Magisk] Paz9:
Weird... I pass integrity but pay doesn't work, just fails, no error or anything
[Magisk] Lobod:
Clean gms data and readd cards or wait 24h. it will work fine.
[Magisk] mrjuniork:
PSA:

Ladies and gents,

it's been definitely a rollercoaster of impressions reading the posts over the course of the last 24 hours.

I lost count of how many off-topic posts I stumbled on 😅

I totally understand the outrage, disappointment, resentment etc., once a FP is burnt and therefore affecting a lot of ppl with their daily drivers.

That being said, I strongly encourage you to stay on topic, which shouldn't be too difficult imho.

As I stated in past, feel free to create a thread about all kinds of topics (especially the one being about G cutting ppl off from RCS etc..).

And also, this is not a ROM maintenance thread. Take it up with the Devs of various ROM's through the appropriate channels.

Thx for your understanding and cooperation and let's enjoy the fish as long as it lasts 😉

Cheers,

mrjuniork
[Magisk] joeyhuab:
Thanks for trying before I had to make another build. What if this is system/core related, @osm0sis? Since that's where most of the spoofing happens as well. Just an example:

View attachment 6106093

Should I try a build without any of these?
[Magisk] Vgl12258:
Yeah, I already tried that too, that's what I meant by "as well as safetynet properties etc".
[Magisk] beardedwonder:
I'm having a strange problem, with the Xioami PIF. On my tablet (Lineage, 20-20240117-NIGHTLY-gta4xl) using SPIC I pass Device.

On my Mi9T using: Lineage 19-20220719-UNOFFICIAL-GMS-davinci

I only get BASIC.

I am using Play Integrity Fork v8

Magisk modules: Shamiko + Systemless hosts

(on both devices)

Both devices have exactly the same in:

/data/adb/modules/playintegrityfix/custom.pif.json

EDIT: I have had it working on the Mi9T for a long time including a self-mined print until the great blocking that happened. From then I dropped onto the Xiaomi print.
[Magisk] Depressed T.Bear:
Not even perplexity ai is helpful right now :( ...

Spoiler content hidden.
[Magisk] Princknoby:
Hello gentlemen

Any light on this? It was working 100% up until now, but today, when I took the test, I didn't even pass BASIC.

Magisk Kitsune + PIF latest version + MagiskHide EnableView attachment 6106100View attachment 6106101View attachment 6106102
[Magisk] wilsonhlacerda:
unames of Mi9T?

🔧 [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] Ex novo:
On my MI 10T Lite (Gauguin) with official PixelOS (android 14) it is not working. So it's something related to the ROM.
[Magisk] beardedwonder:
Uname Mi9T (not working): 4.14.288-perf-g749f21a0823e

Uname Tab S6 Lite (working): 4.14.330-g2aef692b018b

Could -perf- be a newly banned release string?
[Magisk] wilsonhlacerda:
It does not seem banned, but if you want to double check change the name to "-beardedwonder" following this easy/safe instructions: (and let us know!)

🔧 [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] immortalwon:
Apparently someone shared this screen shot on my group, DroidGuard is checking gpu fingerprints of the device, but this is not confirmed if this is what is causing the integrity fails.View attachment 6106107
[Magisk] damondiamond1:
How to compile in Android Studio as a release to get classes.dex?
[Magisk] lamiricore35:
Hi i just install lineageOS 21 on my Poco F1 with magisk an last play integrity fix (15.9.9). My device pass device and basic integrity but my bank application still refuse to launch (CMB french bank).

Is there a way to soluce this ?
[Magisk] Lobod:
I have 1 device passing with -perf- kernel
[Magisk] sawdoctor:
As far as I'm aware the Devs have been aware of the GPU checking ability for a few months. It was discussed on chiteroman GitHub. I don't think it's being enforced or everyone would be failing