yashsingh1/xdaforums huggingface dataset:
[Magisk] freeza:
Using a working private print for now but i only want to use it in emergencies not as a daily driver lol. 😭😭
[Magisk] wilsonhlacerda:
That info is GOLD to Google. Better NOT publish how many we have. Keep that info only among each donators.

Lets Google (and thus users in general) discover when it finish, can be 10, can be 1000.

This way they probably will not work/invest on alternative ban methods, that can be useless in a few days (or not).
[Magisk] kholdstayr:
This might be dumb, but what is the process for generating your own pif? Is there a script that comes with chit's module?
[Magisk] wilsonhlacerda:
Only BASIC it seems:

Comparison of Android ROMs

Comparison of Android ROMs

eylenburg.github.io
[Magisk] ionut310:
From my point of view even if the remaining working prints are shared or not, this will not change a thing. One day none of them will work., the same day when someone somewhere will just get bored. They banned 95 percent of the prints at once and i`m sure they know exactly whats left.
[Magisk] xantrk:
Mass testing prints is also not the best idea as far as I can see.
[Magisk] sawdoctor:
Just because a working print isn't being used doesn't mean it won't get banned. I can guarantee the vast majority of prints banned today weren't being used
[Magisk] freeza:
Good point. Guess it's all bad no matter what
[Magisk] manjaroid:
That's right. See this.
[Magisk] kornball:
I've been rooting since I had my Nexus One, but Google is starting to make this more trouble than it's worth. If I could simply re-lock the bootloader without wiping my device, I may actually go that route. I hate to acquiesce and give them what they want, though.

Thank you to all the developers who work hard to provide ongoing workarounds to Google's BS!
[Magisk] SchmilK:
https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-177#post-89189572 waaaaaaay back on page 177
[Magisk] zgfg:
But there are no more ~300. Most are nuked
[Magisk] SchmilK:
thought so too, then rebooted again and looked - my root browser was in the wrong path :D it stuck after the reboots.
[Magisk] HippoMan:
All this speculating and second-guessing and fantasizing about the Googlefrinchians' motives regarding fingerprint blocking is a lot of fun.

But irrespective of whatever we ultimately discover about these motives (assuming we discover anything about them in the first place), I believe that modded Android devices are still going to continue to become less and less usable.

I'll keep availing myself of modding for as long as I can, and in the mean time, I'm wishing for one or more usable, non-iOS alternatives to Android to come along.
[Magisk] fbirraque:
My private print still BASIC and DEVICE certified after the today's ban but the Google Wallet (NFC Payments) stopped works at the same time Google banned "Clark" public one.

Seems like Google are playing a different game now.

As you probably know many private prints also banned today. This game suck!

- Poco F3 (alioth), MIUI14.0.8.0 by XiaomiEU

Note: The SafetyNet & Play Integrity are still certified so all bank apps are working fine but Wallet is R.I.P. at least for me now.

(*) That's a die slowly game since last Friday when Google begin to change the rules.

🔧 [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] ScottIsMyName:
Does anyone have a working print still? I have like 10 saved but haven't got home to test them
[Magisk] mugna91:
I don't believe this is the way they think.

As we all know, Google needs to generate revenue. Their strategy of banning certain fingerprints gradually, rather than all at once, is a calculated move. Banning everything in one go would significantly impact their earnings. This approach appears to be a blend of economic strategy and resilience testing, designed to gradually wear down the community’s resistance. Additionally, we still don't know how significant the community's impact is on the total number of units in use, so we cannot completely dismiss its potential economic influence.
[Magisk] IBq536XJaWThZsjwwwApTUiV:
It's very likely they mass-banned a bunch of fingerprints; a lot of fingerprints on my computer only pass basic integrity.
[Magisk] osm0sis:
I think you just need to wait for it to clear the Requirements check again now that you pass again.
[Magisk] fbirraque:
I hope so too. Anyway there's nothing else I can do once I'm still the lucky ones that can reach PI Device certified even now.

But not everything is so good... I copied the same private fingerprint to other device and it only get PI Basic certified. So there's one more rule that Google could be changing... TBC

If possible check it your current private print can certified a new device now.

(*) Screenshots with same private PIF
[Magisk] purgy:
Welp I guess I better make sure I don't forget my analogue wallet in future.

So long, and thanks for all the fish!
[Magisk] osm0sis:
Old version of Android on the failing device? For awhile there they had griffin only failing on old Android ROMs.
[Magisk] hackthis02:
Am I missing something? I have the latest PlayIntegrityFix from @chiteroman. And I recently made myself a PIF from my own build props. Everything is working (RCS, GPay, Bank) but when I run SPIC it says I only have Basic Integrity.

I tried searching this thread but didn't see an answer.
[Magisk] BunnyPig1:
Fair point.

------ Removed -------

This was waaay off-topic so I deleted it to ease the clean up for the moderators.
[Magisk] fbirraque:
No both devices in Android 13

- Poco F3, MIUI14 by XiaomiEU

- Redimi Note 8T, EvolutionX

Also both Kitsune 27001; LSPosed 1.9.2; PI Fork CI #223
[Magisk] Eula13:
you can't just create your own pif using your device own build.prop and pass device that way. also PIF FAQ for more information
[Magisk] Syoenth:
I tried doing that but it doesn't pass Device test
[Magisk] osm0sis:
Interference from EvoX again perhaps?

PM me a verboseLogs 100 log again. 👍
[Magisk] IBq536XJaWThZsjwwwApTUiV:
Someone on Reddit wrote about intercepting a Play Integrity request to another device that passes the integrity check and then forward the result back. Would such a thing even be possible?
[Magisk] fbirraque:
I don't think so.

EvoX always has less troubleshooting than XiaomiEU with certification.

I'll pm
[Magisk] osm0sis:
Sounds like there are ~69 (nice) known prints left. So that's 1/5 of the 5%, so... 1% of previously known pre-Leap Day prints remain. 😕
[Magisk] roirraW "edor" ehT:
Everything is possible. Just takes time, motivation, and money. :D
[Magisk] Fishawy:
Keen to know the best strategy going forward.

If a decision is made in favour of using these, I guess most - if not all - of us agree on not sharing print details publicly.
[Magisk] HippoMan:
I don't see how that would be any different from simply spoofing the fingerprint from another device, which is what's already done with Play Integrity Fix and Play Integrity Next.
[Magisk] ScottIsMyName:
Dang, I searched today (after checking my 10 or so stashed FP's) and couldn't find any working prints after an hour or so. This really seems like it might be the end.
[Magisk] IBq536XJaWThZsjwwwApTUiV:
I'm not sure how Play Integrity actually works, but the Reddit posts can be found here:

https://www.reddit.com/r/Magisk/comments/18be2ek/_/kc3yssi

https://www.reddit.com/r/Magisk/comments/18nqht2/_/kfgtfax
[Magisk] Captain_Throwback:
Well, assuming 1 gets banned per week (optimistic), we have a little more than a year to come up with another solution (if the devs agree to share them in some covert way).
[Magisk] LifeVirusZERO:
Good to know it's not just me. Was trying a bunch of different stuff earlier today to figure out why RCS wasn't working. Then I remembered I had playcurl installed. Reinstalled it, reinstalled PIF, ran the FP downloader a few times, etc. Once I realized I couldn't even use any of the usual integrity checkers due to API timeout, I started to figure out what was going on. Play integrity makes sense for Wallet but RCS? Come on, Google.

Edit: EvoX user on a Moto One Action (Android 13)
[Magisk] HippoMan:
I understand what's being proposed. But routing the Play Integrity call to another device is not different from having a spoofed fingerprint from a different device returned from the original device via Play Integrity Fix or Play Integrity Next.
[Magisk] D€INOS:
Assuming that one print is banned, but these two recent times, a bunch is banned, prints that isn't being used , so there isn't much of a point of holding 69 fp because they can be nuked even though they aren't being used.
[Magisk] QuadCore_xRV:
I'm curious to know, if fingerprints are being banned, does that mean the device that those fingerprints originally came from are now no longer passing integrity? If not, then why? If so, then isn't it just a matter of finding popular devices that google can't just block the print for?
[Magisk] simplepinoi177:
from the PIF FAQ (you should give it a look over, it's a good read; you can click on "osm0sis said" to get there)...
[Magisk] osm0sis:
FAQ #2

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] BunnyPig1:
Just a question regarding that one.

It says "the exact mechanism isn't known", do you think it'll ever be discovered?

And if so, do you think it's something that can be exploited if discovered?
[Magisk] Nemosfate:
No one will know for sure IF it will be, we all hope it will.

As far as it being recognized exploited IF found, usually someone finds a way.
[Magisk] Claus….:
@chiteroman did you ever considered or tried this?
[Magisk] Brava27:
Here I thought my phone was the issue... Stupid google.
[Magisk] s1dest3pnate:
Please share a working fingerprint. I can't receive some important messages and I need to get them and then transition back to SMS since they are killing RCS for modded phones.
[Magisk] trevtdogg:
i don't have any private prints, but i fully support if those who have them decide not to share them at all and keep them for testing purposes.

we are almost run out anyway, better i think at this stage to do as little as possible to poke the bear - while those much smarter than myself work on a possible new solution. the remaining prints that still work might make it easier to find a better new solution.

then of course maybe they might not help after all, who knows. but better to give them a chance to be helpful, rather than accelerating faster towards 0 left.

until then, back to analog card for me. that is until i can buy a cheap watch to use instead.
[Magisk] robbins:
How do they verify that it's a different device spoofing the fingerprint vs the actual device with that fingerprint? Since everything software/props wise can be spoofed, and they by definition don't support hardware-backed attestation.
[Magisk] jnss98b:
I'm pretty sure you can still receive rcs messages with PI failing. You can deregister from rcs as well
[Magisk] jnss98b:
Many apps cache their SN/PI responses for days instead of doing checks constantly. Do nothing and wait for a week and watch all of those apps starting to misbehave
[Magisk] beeshyams:
Fully agree with you

Besides, asking for working FPs is wrong at multiple levels. Needn't elaborate that

I too don't have a working print but making adjustments to my usage. Today I counted and realized that 20% of my apps (out of the 99 installed) are in Magisk DenyList, the latest being a society maintenance app, which of course deals with payments.

IDK if things are this bad in other countries, but here in India it looks like it's going to get worse with apps jumping on strong integrity wagon. I was on the fence but not anymore, next device is going to be stock, unrooted
[Magisk] sawdoctor:
That low 😞. Fully understand if they are kept for testing purposes only. If the decision is made to share any maybe a private GitHub or something?
[Magisk] Claus….:
For me it seems that fingerprints are banned no matter whether you use them or not. Maybe for a totally different reason than what we think.
[Magisk] 에어 론 리:
yeah, to force ppl to buy new phones ;)
[Magisk] chiteroman:
With FrameworkPatch you can use your device fingerprint 😊
[Magisk] Claus….:
Hmm, can you elaborate a bit more on the steps? I cannot find anything about this anywhere in the thread.
[Magisk] crypticc:
Uugh. Saw this just B4 bed last night. Work and wallet dead.

Very tempted to do this... I only root because unlocking bootloader triggers a waterfall of checks and hiding.

What happens when Google bans the prints, Are the original phones blacklisted too?

e.g. if I charge and see if my old HTC magic works.
[Magisk] crypticc:
It's on this thread. Second link on Google. Looks complicated though.

🔧 [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] HippoMan:
Yes, we need to remain vigilant in order to continue to protect ourselves against the Googlefrinchians.

Also ... I installed PIF and set the date to 10 days in the future. But after rebooting, clicking "Play Store version" multiple times in the Play Store "About" section does not bring me to any developer-features-related screen.

Could this be due to the fact that I'm running a custom A13 ROM (crDroid 9.8) on the device I'm testing with?

I had this test device turned off for a long time before trying this today, so should I perhaps "Update Play Store" first and then reinstall PIF and try again?
[Magisk] bakaekze:
It won't work on XEU
[Magisk] HippoMan:
Turns out that I was told that my play store version is up to date when I selected "Update Play Store". And with PIF installed, it also turns out that it says "Device is certified". So, it looks like the custom ROM still works with PIF ... at least it doesn't crash.

I'll do more testing now.
[Magisk] SpiderAang:
Doesn't work on Oneplus 8T
[Magisk] chiteroman:
Crashing ? Provide logs plz.
[Magisk] g1b50n:
View attachment 6030821

View attachment 6030822

Not work on One Plus 11 stock ROM. Aby suggestions?
[Magisk] thesingular:
If the devoper features are already enabled, it'll display a toast about it ("No need, you're already a developer") on the 3rd tap onwards. If play store isn't recent enough, no such toast will be displayed and it'll check the updates for play store instead. Those versions don't have a separate Developer options in General section and no built-in play integrity check either.

No need to reinstall PIF though.
[Magisk] Dark Warlock:
Xiaomi 13, xiaomi.eu, A13. No crash, but safety doesn't pass and i can't add credit card to gpay wallet, because it doesn't meet the certification
[Magisk] Rom:
Ok thx, i just see now that chiteroman have release a new 12.1 version, i will test it and check the camera.
[Magisk] HippoMan:
OK. But when I select "Update Play Store", I am told that Play Store is up to date.

So, the lack of developer options being offered might be due to the fact that I'm running a custom ROM.

I tried the same thing on my other device: A13 stock ROM on a Nothing 2, and without PIF installed. On that device, I can get the developer options using this method, and this seems to add evidence to the supposition that being a custom ROM is what causes those developer options not to be available on that crDroid-based device.
[Magisk] bobby8921:
Thank you for the hint.

I'll try without Ad-Away once Wallet let me try again
[Magisk] thesingular:
3 options:

1. Just wait. It'll definitely fix itself as long as the device integrity passes. It'll take at most a few days.

2. Set the date to the future manually and force close the related apps(or reboot) to force the check.(Just don't forget to change the date back after it's fixed)

3. Clear the data for Play Store, Google Play Services and Wallet(Also Google Play Protect Service if you have that app), then reboot. This will also force the app to check again.
[Magisk] Dark Warlock:
It worked before
[Magisk] bakaekze:
Now it doesn't. Google changed things.
[Magisk] chiteroman:
EvolutionX developers build the fix inside their ROM: https://github.com/Evolution-X/frameworks_base/commit/0cf8a4f3a5153de17e2b09f27bf405e140d7fa2c

🥳
[Magisk] thesingular:
I see, so it was already up to date. That's good to know I guess. I've never had a crDroid based ROM so this whole situation is a first for me. My device is also on the stock ROM. (there really aren't any custom roms for Mediatek devices, I can only get Xiaomi.eu, and that too only through their patreon)
[Magisk] EuK_V:
View attachment 6030827

Big thank you, dev. Gpay is working again!(y)
[Magisk] Dark Warlock:
So what is works on XEU or is there no solution?
[Magisk] HippoMan:
If my memory serves me, I think that this crDroid ROM required a set of custom Gapps to be installed. In that case, I assume that it could be possible for those Gapps to not be set up to use the latest Google Play Store software.

I like crDroid in general, because that ROM has more customizable features and less noise than stock Googlefrinchian-based ROMs. But on the other hand, there are some pieces of software which don't seem to work well in custom ROMs.
[Magisk] crypticc:
Looks like new FP won't be coming via AutoPiF or derivatives...

View attachment 6105647
[Magisk] Claus….:
Ooh, this is the TEE hacking, out of my knowledge and I did not see anyone being able to do it. I thought @chiteroman was referencing to something else.

Anyone that succeeded with TEE method?
[Magisk] linuxares:
GitHub - chiteroman/FrameworkPatch: Modify framework.jar to build on system level a valid certificate chain

Modify framework.jar to build on system level a valid certificate chain - chiteroman/FrameworkPatch

github.com

Any "idiots guide" for this?
[Magisk] 에어 론 리:
tried to make it on my rom for LG v50 (A12), stuck on bootloop, mb my Abdroid Studio knowledge is far from normal :(
[Magisk] sawdoctor:
There's a "work in progress" module that i think works along the same principle of the framework patch

GitHub - hex3l/PlayIntegrityForkKsBypass: PIF fork that provides attestation by bypassing the Android KeyStore while using a valid keybox. Not complete and explicitly set to work only in the context of Key Attestation app

PIF fork that provides attestation by bypassing the Android KeyStore while using a valid keybox. Not complete and explicitly set to work only in the context of Key Attestation app - hex3l/PlayInteg...

github.com
[Magisk] asisandroid:
does that module work without a very special fingerprint and without some rare difficult tofind leaked keys?
[Magisk] chiteroman:
v15.9.9 released!

Release v15.9.9 · chiteroman/PlayIntegrityFix

MEETS_DEVICE_INTEGRITY is green again ✅ Refine code logic

github.com
[Magisk] Lord Sithek:
Nice but didnt work for me
[Magisk] Dehumanizer77:
Doesn't work for me, I'm still only left with basic integrity :-/
[Magisk] frank93:
same here. :/ that fingerprint included seems to be from the OG pixel, sailfish!? i thought i read somewherer in these millions of comments that those were all already "burned" in the past, but i may be wrong though ..
[Magisk] sawdoctor:
Do you still have a custom pif installed? Might need to remove it 1st if you have
[Magisk] sawdoctor:
It can use the key box from your device but the module is still a wip
[Magisk] bakaekze:
make sure to delete a custom fingerprint from /data/adb/pif.json and disable any modules that feed it like playcurl
[Magisk] kiradotee:
Mine is still red. I'll try to play around with disabling/enabling other modules but so far no luck at the moment...
[Magisk] Dehumanizer77:
I don't have any custom pif there at the moment...
[Magisk] immortalwon:
Sailfish is banned, not working
[Magisk] chiteroman:
May sailfish fingerprint has Magisk patched boot detection? I'm using KSU LKM and it works great.

Users who can't pass Device, could you post what setup are you using?
[Magisk] Dark Warlock:
For those who do not work v15.9.9, have you deleted Xiaomi.eu-app?

Through terminal

su

pm uninstall -k --user 0 eu.xiaomi.module.inject
[Magisk] kiradotee:
I did this and also reinstalled PlayIntegrityFix_v15.9.9 and it worked!!!!
[Magisk] KwstPap:
worked for me. Pixel8Pro
[Magisk] Dehumanizer77:
I am running Pixel Experience ROM on Poco F3, latest magisk 27.0 and apart from Playintegrityfix module I only have systemless hosts module enabled.
[Magisk] kaem84:
v15.9.9 works for me. Hope is back

View attachment 6105676
[Magisk] felek73:
It worked for me , device_integrity is back , but wallet is throwing a warninig that device doesnt meet bla, bla, bla .. will wait and see
[Magisk] KwstPap:
force close wallet and check again + clear cache
[Magisk] jesusmolon:
I think it doesn't work in custom ROM

On a mobile with official hyperOS it works for me and on another with crdroid it does not work
[Magisk] Dehumanizer77:
Strange, on my wife's Redmi it is also working.
[Magisk] sawdoctor:
Working on pixel fold using latest magisk canary with shamiko and zygisk-assistant installed (enforce deny off)
[Magisk] bakaekze:
it will take upto 72 hours for wallet cached result to clear
[Magisk] Dehumanizer77:
Yes, my wife has official xiaomi rom and it works for her too...
[Magisk] sawdoctor:
Does cdroid have any spoofing baked in? Any custom rom with any sort of spoofing installed will likely interfere
[Magisk] Claus….:
Thanks, works for me :)
[Magisk] immortalwon:
I am using evox custom rom, maybe that's why it's not passing?
[Magisk] jesusmolon:
No, I have an old version of crdroid

I have tried with pixel experience and it doesn't work either

Only works with official ROMs
[Magisk] blu.italia:
Thank you so much chiteroman.

Works great with Pixel 6 Pro on latest LineageOS 21.
[Magisk] aiute_111:
Only one of my 4 devices worked, lineage 21 A14 (which worked) APatch , Nameless A14 APatch , crDroid A14 KernelSU、HavocOS A11 magisk
[Magisk] joeyhuab:
Evo lead dev here. Installed 15.9.9 on latest Evo X with KSU (GSI). Disabled ROM PIF and checked logs.

https://paste.evolution-x.org/vEqmqU

It seems it now passes on stock and some ROMs for some reason. I'm still investigating myself.
[Magisk] LordDemecrius83:
Strange, it works on my Tecno Pova 4 Pro both on XOS and with Project Sakura GSI(Apatch)
[Magisk] dmenezes:
Well, talk about jinxing it... just woke up to this:

View attachment 6105685

So it seems the infamous PIG over there at Google is back at his/her weekly-ish schedule of screwing over our fingerprints...

Well, back to the usual... ConnectBot, then autopif.sh, then moving the generated file to its proper place, and reboot.
[Magisk] carlese:
Can confirm it's not passing on EvoX, both with built in PIF and PlayIntegrityFork
[Magisk] CHV:
Unfortunately it doesn't pass on crDroid 10.5.
[Magisk] Koeties:
Maybe first go back one page and read the posts. All Xiaomi prints burnt.
[Magisk] officialputuid:
Still not passing MEETS_DEVICE_INTEGRITY on (AwakenOS v4.5) May 2024 ASB
[Magisk] dmenezes:
And less than 15 minutes later, after following the described procedure, here am I back with DEVICE:

View attachment 6105696

So it seems it's same old, same old and deja vu all over again 🤔

See y'all next week, I guess... 😁

Just out of curiosity, does anyone know approximately how many prints are left? I'm curious on how long we have until the PIG manages to get all available prints bananaed with this new, weekly-ish schedule...
[Magisk] dmenezes:
Uh? What gave you the notion that my FP had anything to do with Xiaomi? 😵‍💫
[Magisk] majorfigjam:
Maybe this time read back a few pages. 69 was the best estimate, or 1% of pre March numbers.