yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
I'm not sure that there is any such thing as a FP that is actually totally "universal".

I think that there are other factors in play which are device-specific and/or OS-specific.

For example, if a given FP gets banana-ed for the spoofing that we are doing, in most cases, the same FP still works fine on the original device. And also, some FP's are still working for some people on their devices, while some of those same FP's seem to have gotten banana-ed on certain other devices.

The DG (DroidGuard) software used by the Googlefrinchian Telephone Sanitizers to do integrity checking is pretty much a "black box". There has been some decompiling and investigation being done on that software, but we still don't know all of its operational details. And it may very well be that there is software on the Googlefrinchian side of the DG connection which goes through some unknown (to us) logic to tell DG to give a thumbs-up or thumbs-down. Furthermore, for all we know, that logic on the Googlefrinchian side might sometimes get modified, thereby yielding different banana-ing behavior on certain devices as time goes on.

And, of course, there's the recent "enhancement" (ha ha!) of the integrity-checking procedures which now give a thumbs-down to integrity if certain kernels are in use. The Telephone Sanitizers are also very likely to continue to "improve" (ha ha!) their integrity checking in other ways as time goes on.
[Magisk] zgfg:
Xiaomi eu developers do not need 'universal' prints. Their injector applies only to their own Xiaomi eu custom ROM

Also, Im personally not interested in the 'universal" prints - I need the pronts for my own phone, hence when I mine(d) them, I test them on my phone (my 'universum')

Btw, as a result of sharing the 'universal' prints they become widely used and then more promptly banned by G

So, from my side, I don't really see a need for the 'universally' working prints, or to know if some are or not
[Magisk] Umgak:
Sir, this is a Wendy's the Play Integrity Fix thread on the XDA Forum. XDA Forum is meant for discussion of the development, modification, and use of Android phones.

If you have a question, comment, or concern about the Play Integrity Fix module or Play Integrity itself, feel free to post them here. If you have trouble communicating in English, please feel free to use machine translation and include the original text at the bottom of your post.

Please don't just post random logs from TOR, as it isn't relevant to the topic at hand.
[Magisk] Nergal di Cuthah:
They were given plenty of room to be clear. These logs look like junk so i reported them as spam. My apologies to the Mod who has to decide.
[Magisk] trevtdogg:
not sure if others have read something different in my post then intended, but I too am against the using of public shared prints.

when I use the term universal, I literally just mean that it works on all devices. this was the normal while public shared prints were used (the ones included in earlier versions of the modules). even though Xiaomi eu custom rom developers don't need to find true universal prints, in practise their prints have been used as universal prints.

even many times in this thread, the use of Xiaomi eu custom rom prints has been a trouble shooting step suggested to see if all other variables for a particular device are working in order to pass device integrity.

I'm just personally interested in how many prints are still universal, how many are device specific, and if we have any guesses as to what makes a print universal or not.

it seems there must be a way that devs are discovering if a print is universal or not, since it has been rare for an included print to not work for certain devices.

are universal prints rare now? or are most working prints still universal, but there's a few other "bonus" prints that work on some devices and not others?
[Magisk] Nergal di Cuthah:
I think, in general, fingerprints are "universal" it's just that different DG versions catch different devices.

I'm still not convinced that a mismatched fingerprint "test id", as seen in pi checks in playstore, doesn't have general device data, not yet being spoofed, and sees that it's mismatched so DG can ban a fingerprint on a family of devices that don't match. Then, if a fingerprint shows up often, they ban the print instead of the more focused device/fp mismatch.

This would explain why some users can get away with public fingerprint long after it was banana'd

This is all guessing based on what above was described as a black box that we don't completely understand.
[Magisk] chiteroman:
Released v15.8 !

Release v16.5 · chiteroman/PlayIntegrityFix

Update hook framework: Dobby Fix Device not passing in few devices Improve code Reduce Zygisk libs size

github.com
[Magisk] Flr Power:
Anxiously awaiting future drama bugs 😳
[Magisk] beeshyams:
My theory for what it's worth is that DG ensures additional checks if Wallet is available in that region

I am from India where we don't have wallet and Gpay works with certified Play Store. I'd mentioned this theory earlier but it was logically rebutted, yet, that seems to be possible

I am yet to see any Indian complain of banned FPs (going by profile names not actually checking profiles)

Maybe true for other regions where wallet isn't available.. IDK
[Magisk] Nergal di Cuthah:
Nope it's pay in the US too and plenty of US users have banned prints (including the two I've had since december until this week).
[Magisk] beeshyams:
Thanks, so that kills my theory

I am currently on Freeman print since end December working fine. Before that I was on a print from a Tg group that was also working fine till I switched to Freeman

I have a stack of 3 dozen mined prints but not upto checking how many are valid.. At some point soon I may go back to locked BL... This damn game is draining
[Magisk] Klappp:
Hmmmm.....
[Magisk] simplepinoi177:
you either gotta wait 48 hours, or clear data of Wallet, Play Services, GPay -- the latter will remove cards from Wallet and you'll have to re-add & re-verify each of them...
[Magisk] Klappp:
I already cleared Google play services, wallet and play store and rebooted
[Magisk] badabing2003:
There's nothing in your screenshots that show that you pass device integrity.

Passing YASNAC is not enough, please check the FAQ.
[Magisk] simplepinoi177:
Oh i didn't look closely enough at your screenshots (I thought one of them was TB Checker)....passing YASNAC is currently not enough to show/prove you can run things past DroidGuard (Wallet being one of them)....

You need to check your Play Integrity (there are 4 Play Integrity checkers) and achieve/show "MEETS_DEVICE_INTEGRITY" to get Wallet to work....

EDIT: ninja'd by @badabing2003
[Magisk] meiser:
I found version 0.9.2.1 in the TG channel which fixed device integrity for me.
[Magisk] Klappp:
And would changing only the fingerprint allow my device to pass or do I need to do something else?
[Magisk] simplepinoi177:
It depends.....

If you are on a custom ROM or custom kernel and it is part of Google's blacklist, no amount of fingerprint will allow you to pass DEVICE (you'd have to look back in this thread to learn how to remove the identifying details [name]). If you are on stock everything, then it may be your set up since the latest version of Play Integrity Fix has a working fingerprint included (for the short time being now). You can change the fingerprint, but you'd have to mine & test various ones until you find one that works for you; but once you do/did, passing would allow you to use Wallet with an unlocked bootloader & rooted as well as bypass other restrictions.

Note that in many/most such situations, you'd still have to either wait 48 hours or clear data on Wallet/Gpay/Play-Services and re-add & re-verify each card to get Wallet to work as expected...
[Magisk] Klappp:
Freeman's script saved the day again! Thanks
[Magisk] rocketda7331:
haven't kept up with posts here for last 80ish pages, but reporting in that custom fingerprint still working just fine since early december or whenever the whole fiasco started
[Magisk] Vision:
My FP dead today R.I.P. (21/12/23 - 16/2/24)
[Magisk] Flr Power:
Funny how the public Xiaomi FP is still working 😳🤔
[Magisk] Nergal di Cuthah:
They probably changed it recently?
[Magisk] Vision:
Really? and this is my second FP R.I.P. and i choose a FP for a not very common phone
[Magisk] xSnowLeopardx:
Mine's still working since Dec 2 - at v14.4
[Magisk] Vision:
You have the most continuous FP
[Magisk] Flr Power:
No, has been in use for at least 3 weeks. Even chiteroman has decided to include it in his last 15.8 module.
[Magisk] Nergal di Cuthah:
Weird
[Magisk] Vision:
Very strange, Google not have R.I.P it yet
[Magisk] xSnowLeopardx:
I am never lucky so I think my time will come this month as well haha
[Magisk] acwcanada:
Android 15 Developer Preview 1 is out, I am curious about if present method would work with it!
[Magisk] Vision:
I understand that feeling :ROFLMAO:
[Magisk] osm0sis:
My main print on my daily driver has been working since November 19, and still is. For now.

But, bans are increasing. When the kernel string bans were added to DroidGuard they also banned a bunch of prints at the same time. From our testing the bans seemed to be mostly of older device prints from older Android versions like 5.x and 6.x.

I myself found that on my Nexus 7 a well known Google tablet print I was using was banned, and later found they'd banned all 8.1.0 prints from that Google tablet. This latest wave of bans has now banned 8.0.0, 7.1.2, and some 7.1.1 prints from that Google tablet, with a cutoff date of everything 2017 and later now appearing banned.

So it's interesting, and seems like for some devices they're "raising the floor" by banning the oldest prints first, and for others they're "lowering the ceiling" and working their way back by banning the newest prints first.
[Magisk] Vision:
In that case you're the Winner 🏆 with the most continuous FP

Yeah this is interesting, i read somewhere here, some users say the few banned FP start work again, little confused
[Magisk] zgfg:
From my previous experience by sharing prints im the closed group, PM and personally over TG, and when communicating with ppl who properly configure things on ther devices, vasr majority of peints work for most

However, how would you prove that sone prints work on ALL and EVERY device - how can you test

So exclude all yada, yada about 'that and that banking app does not work'...

And generally, prints from older devices (until they get banned) have higher chance to work on old and new devices/Android versions then prints from the newer devices. Although that can be partially suppressed by loewering API level

Eg, I have few prints here with A5 and many (still not banned) from A6 and I'm pretty sure they will be more 'universal' than thenone from A14 (with Sec Patch from Nov) and several from A13 ROMs
[Magisk] Umgak:
Actually, I think that title probably goes to @osm0sis.

Edit: I scrolled down and yes, it does.

Mine still works as well, got it 2023-12-01
[Magisk] Vision:
That's is good, only mine R.I.P in this round 😂🤣

View attachment 6069313
[Magisk] Whyherro1:
I haven't used a custom FP, currently on Chitero's 15.7.2. Everything is working, subscriptions and wallet are 100% working for me. Is this normal?
[Magisk] purgy:
Yeah, till that print gets the boot.

What with the delays between FP being banana'd and gpay / wallet actually checking integrity again, it's quite possible that @chiteroman will get a new version out in time, but it's equally possible that he won't, as his position on including prints changes fairly frequently.

If you don't rely on wallet being accessible, it's *probably* fine, if you do, finding your own print is a better long term solution imo
[Magisk] eac5:
Exactly, better to be prepared than getting caught with your pants down. Not to mention it's just annoying to readd the cards back to wallet after it detects the lack of device integrity
[Magisk] Jirachilover:
Google confirms it just laid off around a thousand employees

Engineering and Assistant teams were impacted too

www.theverge.com

One can only hope that Google includes the teams responsible for Play Integrity and fingerprint banning in the january layoffs and in future layoffs. Can't imagine it earns them any money in bothering to do so and is a waste of time.
[Magisk] frank93:
using a fingerprint from a "rather known manufacturer"’s device, i thought mine would be banana’d sooner, but: still working since beginning of december, too. fingers crossed. pixel 7a hardware.

also, my "stash" of pre-checked backup prints sourced from one of the bigger rom-dumps, around 10 or so, also seem to still work. WHAT AM I DOING WRONG? (ok, jk, i won’t complain ..)
[Magisk] manjaroid:
Reminds me of an old disk drive diagnostic that would say, "Everything is running fine. This can be corrected with any sharp, blunt or conductive object."
[Magisk] bobo_15:
sorry for the off topic. but can someone point me to a working magisk or Xposed module to force apps in full screen?
[Magisk] Wolfcity:
I wasn't playing that game "who has the longest:LOL:" but just as a piece of information: You narrowly beat me by 2 days.

Mine is working until 12-3. Of course on @osm0sis PIF v7 now.(y)

But from around 30 prints the half of them has been banned. Almost all are 8.0.0/8.0.1, some 7.1.2 too.
[Magisk] xSnowLeopardx:
So, not only you're asking something completely different from the topic, you're also asking something you could have searched for via Google and you would have more information than now.... Wow.
[Magisk] bobo_15:
Already searched, otherwise I would not ask here
[Magisk] xSnowLeopardx:
But here is not the place to ask...
[Magisk] Wolfcity:
Are you sure? I haven't checked these hits but I think it will take you further than asking in a wrong forum. No offense but searching the net (maybe with keywords like XDA or GitHub) will help you more.

search
[Magisk] HippoMan:
However, you unfortunately didn't make a good choice of an alternative place to ask.

There are many other topics and threads here on XDA, and I'm sure some of them are much more pertinent to what you are asking.

You can search here on XDA for those more to-the-point topics/threads. Have at it.

This particular thread is enforced fairly strongly against off-topic messages.
[Magisk] TPelangi:
All my prints work fine with v7 fork on Redmi Pad tablet stock rom MIUI A13, but not working on my phone AOSPA A13 custom rom, no event passes CTS or Integrity, all fails with KSU or Magisk.

I just try PI fix 15.8 by chiteroman and it worked.

I don't know why 🥴😅😂
[Magisk] Nicknoxx:
Mine died today - has been working since Dec 12th
[Magisk] osm0sis:
Try the chit module's public print on my v7, I'm sure you'll see it works too.
[Magisk] TPelangi:
i forgot to test input chit print to v7, i go back miui with xiaomi eu module right now on my phone.

only tested input my all print to chit module 15.8 and all print worked fine my tablet, but when i used it on my phone with the custom rom it's fail Integrity only basic also CTS profile fail to.

So the problem is my all print with v15.8 and v7 worked fine on my tablet but not on my phone with the custom roms.

I think it's rom issue or kernel issue but chit public print working fine in my phone with custom rom.

i think my print got banned but my all print still working fine on my tablet.

this is really got me confused 🥴

it's been 3 month old now and my all print still working 🥰

So yeah i will test again later on my phone with the custom rom.
[Magisk] zgfg:
On Xiaomi.eu, you must properly disable Xiaomi-eu built-in injector if you want to use PIF instead (read about in this thread, on Xiaomi.eu forum, etc).

Or uninstall the module, update their injector to the latest and pass that way

At the end of the day, you will use the same prints if you use the PIF module forks or tools that unpack Xiaomi.eu injector and copy those prints to the custom pif json
[Magisk] TPelangi:
just ignore the xiaomi eu module because my phone is unrooted right now with xiaomi eu module.

the problem is when i use custom rom in my phone.

All my print not working with v7 or 15.8 on custom roms in my phone. It's don't even pass CTS profile.

i'm pretty sure my print still working not got banned, because i used it right now on my tablet.

When i think it's custom roms issue or custom kernel issue but public print 15.8 from chit worked fine, when i think the problem is from my own print but my own print still worked fine on my tablet not got banned.

Sorry i'm very hard to explain 😅
[Magisk] osm0sis:
FAQ #5 most likely, unless your kernel changed or got banned or something.

PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com

What's your `uname -r` output on AOSPA device?

Edit: Oh wait, you said chit's print worked fine, so yeah, FAQ #5 it is, and like I said, I'm sure the working print will work with my fork as well.
[Magisk] zgfg:
If not rooted you cannot use PIF (or any fork) module bcs they require Magisk

However, there is no problem with custom Kernel or the name of the kernel/ROM with Xoaomi.eu, like with LOS (you supposedly read here about)

Xiaomi.eu provides their own mechanism to trick Play Integrity with the unlocked Bootloader.

NO ROOT REQUIRED but you MUST update to the latest Xuaomi.eu injector - ask/read on Xoaomi eu forum, not here

---

Or, if you want to use PIF module, you must root (Magisk) and disable their built-in Xoaomi eu injector from their ROM.

That was my previous post about

Please make sure to read things about, like the FAQ here (and/or on the Xiaomi eu forum), etc

And I know what I'm talking about, I have Xiaomi.ei too, and Magidk and PIF...
[Magisk] osm0sis:
My fork replaces/hides all the X.eu injector apps properly, so the only thing left is for the user to uninstall any user app updates for it, and it warns them to do that during install.

Anyway, his X.eu ROM device was working fine all along, it was his AOSPA device he was having trouble with.
[Magisk] sawdoctor:
Found this on GitHub

GitHub - ravindu644/Kitchen: Boot image unpacker and repacker while keeping Android Verified Boot.

Boot image unpacker and repacker while keeping Android Verified Boot. - ravindu644/Kitchen

github.com

Will be quite useful for editing kernel names and should make kernelsu and Apatch a lot easier too (not that those 2 are relevant to the thread)
[Magisk] osm0sis:
Just uses avbtool to sign with the default verity keys. Kinda pointless since it also includes magiskboot and could just use it to mimic the original OEM signature. 😛
[Magisk] sawdoctor:
Think it makes things easier for us less techno users
[Magisk] osm0sis:
magiskboot is what you should be using. badabing and TheFreeman's scripts automate things the right way.
[Magisk] TPelangi:
Yeah really got me confused 😅

I'm not in the custom rom right now 😅 but this some screenshot of two kernel i use before

Based on FAQ #5 maybe i just try other custom roms later to how it's work or not.
[Magisk] osm0sis:
Nah, you've got a working print with chit's included Xiaomi.eu print, so it's nothing to do with kernel. Just rename it to custom.pif.json and flash mine over top to migrate and I expect it'll still work.

Your devices just behave differently as per FAQ #5.
[Magisk] Hasan9540:
Is it possible to set (Meets Strong Integrity) to green? The other two are green except for the last one, which is red
[Magisk] osm0sis:
FAQ #6:

PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com
[Magisk] iruiz2:
Haaaaahahahaha
[Magisk] Wolfcity:
Here "Hahahahaha" means "just read and search the thread". Keyword could be "strong integrity". No offense @Hasan9540 but this question is kind of a running gag.

Check FAQ #6 as @osm0sis posted.
[Magisk] zgfg:
The thread for Pixel Flasher - see the OP post #1 (Delta was the old name for Kitsune)

📳🔥 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] dmenezes:
Ditto here, my fingerprint is from 2023/12/03 and it's still alive and kicking (2.5 months and counting, yay 🎉) and still with @chiteroman's v14.0-resetprop (it may be old but it ain't broken so I'm definitely not going to fix it 😆 -- but when it breaks, I'm going to @osm0sis').

That said, WTF is going on at the PIF scene?

Long time since I visited this thread, but after a couple notifications from GitHub re: new @chiteroman versions (which I couldn't make heads or tails from the changelog), I'm starting to get worried... and after reading the last couple pages here in this thread, I'm still none the wiser....
[Magisk] sawdoctor:
I wonder if you me and osmosis are all using the same print 😂😂. I've been using the same one since end of November, osmosis even earlier. I was on Pif 14 for ages but decided to switch to osmosis fork when it updated for QPR2 beta
[Magisk] zgfg:
There are still hundredths of working prints (nobody knows exact number). They worked at the beginning and still work today. I wonder, why do you think you should be using exactly the same one

Also, if a certain print worked two or almost theee months ago with a particular version of a module at that time, and if the peint was not banned later, it would still work with the same old version of the module - and with the same old json format as used by that module's version

Btw, I stopped updating the module back around the XMas. I cannot say that I use the same print all the time - to the contrary, I usually just leave the last that I tested and it worked.

But probably, it would be safer to not test unnecessarily and to 'keep the low profile'
[Magisk] chiteroman:
No, that's for sensitive_props module 😂 link
[Magisk] chiteroman:
Uh, are you sure is it problem of the module? Very strange because the build is almost the same :o
[Magisk] magaedy:
I tested both builds and didn't change anything else and Now I'm stick with v 9.3 as it is very stable
[Magisk] magaedy:
Also v9.2 is working well, My device is Poco f2 pro , Android 12, MIUI 14 Stock

My recommendation is to start working again from v 9.2 if you want to include Dobby and solve root detection problem
[Magisk] Kuronosu:
OK, @chiteroman, I'm happy you're actively trying to improve your stuff, but I would suggest you test your builds more thoroughly before releasing them to the public.

The change logs look like a mess, because there's constant reverting to previous versions and replacing this and that. Why the constant updates? The module was working fine since v8.x.

Now it seems something's completely broken. I can barely use Chrome anymore, if at all. I get constant error messages of apps crashing. All I did was update to the latest version of this module.

Deleting the module gets rid of the error messages, but Chrome still doesn't work. Installing an older version of the module doesn't help either.

I'm on a OnePlus 11, with the latest version of OxygenOS 13.1. Magisk Canary 26302.