yashsingh1/xdaforums huggingface dataset:
[Magisk] beeshyams:
This was asked earlier too and is a valid doubt but the answer is no, they aren't affected. That's why it is a "soft-ban", only devices that are Spoofing are banned in the sense they fail the integrity tests.. Till such time they switch to another valid FP... And get banned... And the game goes on, unless you find your own custom FP

Hardly anyone here using a custom FP seems to be banned
[Magisk] beeshyams:
One day after you.. Going 💪
[Magisk] trevtdogg:
started using my first FP on dec 11th, so 1 week ago, still working fine.
[Magisk] sethieplayz:
I'm not sure how this managed to happen, thought I'd let it be known here;

Was grabbing some dinner and had not seen that the 14.4 FP had been banned earlier today. Went to pay, saw device does not meet requirements, new patch had not been released yet, so went to grab another (physical) card to pay with (cashier had said transaction didn't go through)

However when I got home I noticed I'd been charged through my GWallet linked card. Managed to get a refund and all is well but I'm confused how I could get the banned message, but still authorise a transaction?

Thanks for any input in advance!
[Magisk] devilsshadow:
Still on the same print I found (based on a 10minute google search) when PIF14.0 came out. Forgot to even check back on this thread in the past couple of days. Very funny to see that prints are still being banned at a regular rate. Literal definition of insanity. Just find your own prints, it's not hard. If it *is* too hard for you, maybe you shouldn't be running a rooted device in the first place.
[Magisk] sawdoctor:
At the very least people on rooted devices should read the release notes and wiki before flashing a module. Even if people using the PIF don't come to xda both osm0sis and chiteroman have excellent links/guides on their GitHub
[Magisk] trevtdogg:
out of interest, has anyone been able to 'rescue' a banana-ed fingerprint that was used by the masses by just lowering the API level?

i know that lowering the API level can help with a potential candidate custom fingerprint, but would be interested to know if the 'banana-ing' of the print extends to include all possible API level options too or not.
[Magisk] kingpeppermint:
Missed that earlier mention somewhere in the 300+ pages /thank for clearing that up.

They seem to have changed their approach although i never have been charged, it used to give an error message stopping you from paying.(before the payment went trough) Now the payment seems to go trough but is refused at the last step.
[Magisk] sethieplayz:
I've always been stopped prior to payment previously like you described. With that purchase though I believe I heard the gpay ding before seeing the device requirements message.

A mistake on my behalf, possible, I don't see how though, as I've never had this issue before... Very bloody annoying since I had to go get a charge back

Otherwise it's a bit sinister, allowing the money to flow but not authorise the transaction...
[Magisk] Dj Telo:
Slightly off-topic question if you allow me... I just updated the module to the version released a moment ago and, upon restart, I've lost root. I have system auto updates switched off. What can have happened? Thanks!
[Magisk] sethieplayz:
Did you get a toast saying that? I had that once, think I just restarted again and it solved itself, apparently magisk can confuse itself sometimes lol
[Magisk] Dj Telo:
I got a toast saying that a certain app could not get root privileges, but, as you said another restart did the trick... Thanks!
[Magisk] dts83:
My Samsung s21 ultra fails strong integrity check anyone help me out here as I carnt use NFC payment ATM
[Magisk] Vision:
Your setups is good, you pass 2/3 that the point of this module, can't pass Strong with this

View attachment 6045366

View attachment 6045367
[Magisk] beeshyams:
You will never pass strong integrity with boot loader unlocked. Period

I can't help with NFC issue
[Magisk] HippoMan:
... and will we soon be needing to receive 14.6 for a Merry Christmas?
[Magisk] switchem:
With the new 14.5 default FP, I'm finally able to pass device integrity. Woohoo! However, Netflix still doesn't work for me. :( That's the whole reason I was doing this, lol. Anyone know what Netflix is looking for and how to trick it? The Key Attestation app gives me a "KEY_COMPROMISE" message. Is this the reason Netflix isn't working? My device is a Lenovo Legion Y700 (2023) with a SD Gen+1 SoC. I'm rooted with Magisk. Unlocked bootloader, of course. I've also installed the Zygisk - LSPosed module with the the BootloaderSpoofer module for it.
[Magisk] switchem:
Hi, here are those screenshots. As I mentioned in the previous post right above this one, I'm able to pass device integrity now with PIF 14.5. Nextflix still doesn't work though.

Here are the screenshots when i was on 14.4 default FP and it was timing out. Will post the other ones in a new post next.
[Magisk] Iridule:
Seems chiteroman has made it easier to find the fp in his code. Used to be in "...main/app/src/main/java/es/chiteroman/playintegrityfix/EntryPoint.java"

PlayIntegrityFix/module/pif.json at main · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] trevtdogg:
Seems to be a DRM issue, see this post: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-314#post-89210440
[Magisk] switchem:
And here is when I tried a custom fingerprint...it passed Basic for the first time...
[Magisk] Iridule:
Try using shamiko module instead of enforcing deny list
[Magisk] switchem:
Here are the results with PIFork. I've also attached a DRM Info screenshot showing Widevine L1 and a Key Attestation screenshot which shows a different error than the one i'm getting now. But I think the error I'm getting now is due to the LSPosed BootloaderSpoofer module because if I disable that, I get this same attached error again.
[Magisk] switchem:
Will do!
[Magisk] switchem:
Thanks for this. I am passing device integrity, but netflix still doesn't work.

Thanks for the link. I tried clearing the data of the ones mentioned, and also check that the DRM Info app says I have Widevine L1. Not sure if maybe I missed something else in that post?

This one fails device integrity check.

In this guide for my device regarding unlocking (link below), the author talks about the netflix/DRM issue. Like me, his device shows Widevine L1 in DRM info. He makes reference to TEE.

To be honest, I'm confused about what this thread's PIF module does exactly and the relationship to Key Attestation, TEE, etc. So, I'm not intentionally trying to be off-topic. Please let me know if I should take this elsewhere. I guess if I'm achieving Device Integrity, then that's all this module is expected to do? Or is there more to it and how it relates to Key Attestation, TEE, DRM, etc.?

Here's a link to that guide. It's in japanese, so I've also attached a translated screenshot of the relevant section. FYI, I'm running the stock ROM not a GSI. https://smartasw.com/archives/17857#index_id9
[Magisk] pndwal:
I might need to edit that post... Seems there is a Play Store dependency on DEVICE_INTEGRITY for Netflix, but how it's cached is strange...

I noticed that if DEVICE_INTEGRITY and Play Protect 'Device is certified' fail, Netflix still appears in Store (with it uninstalled) for some time even If I clear data for Play Store and Play Services (Nb. I don't have Google Play Protect Service app on my older device), but some hours later it is unavailable (listed as incompatible)... Conversely (and perversely), if DEVICE_INTEGRITY and Play Protect 'Device is certified' are restored, Netflix remains unavailable in Store (with it uninstalled) for some time even If I clear data for Play Store and Play Services, but some hours later it's available again!...

Nb. On my device Widevine L1 is retained regardless of DEVICE_INTEGRITY.

I'm guessing, but I now think there may be some check done at intervals for both L1 Widevine DRM and Play Protect (DEVICE_INTEGRITY dependant) certification in the case of Netflix which could account for delay in listing/unlisting in Store... Apps requiring Play Protect certification/DEVICE_INTEGRITY only appear to have Store status updated immediately if data for Play Store and Play Services/Play Protect Service (late devices) is cleared...

... So Netflix will likely appear in Store for you some hours after seeing Play Protect Device is certified (assuming you also have L1 Widevine)...

Also, the above relates only to Play Store status for Netflix... AFAIK, Netflix will install and run (eg one can just sideload the standard app) regardless of L1 Widevine DRM and Play Protect certification or lack of these... It will simply fail to decode HD (DRM) content if not compliant (ie L3 security level is showing for Widevine)...

👀 PW
[Magisk] beeshyams:
Very informative though I don't use Netflix. I feel it deserves a separate thread
[Magisk] supermansaga:
Dumb question. Exactly how do I need to make it happen for my windows subsystem for Android?
[Magisk] pershoot:
That's been happening to me, as of late, with apparently any module(s) I try to auto-update using the Magisk UI. It doesn't appear to happen all the time. May be a bug in the latest stable Magisk itself; unsure. Re-flash patched kernel to restore.
[Magisk] Lada333:
I was unable to keep up with the thread for a while now because of exams (I think I've missed out on literally like 100 pages lmao).

Are we still playing the cat and mouse game of burning through fingerprints when Google bans them?

Has there been progress made on finding a more stable solution, so to speak?
[Magisk] ArzZenic:
1st question - Yes, cat & mouse

2nd question - No, only custom FP
[Magisk] switchem:
For me, I've been able to get the app to show up in the play store. Have also sideloaded it, installed from Aurora, etc. And DRM info has always shown I have Widevine L1. However, when opening the app I would get an immediate error message with error code 15001 and it won't let me proceed.

I actually just fixed it though! Turns out all I needed was a module called liboemcrypto disabler to get past that error screen. https://xdaforums.com/t/magisk-modu...rm-protected-content-netflix-my5-etc.3794393/

Netflix thinks I have Widevine L3 though, so the battle continues, hahah. EDIT: Damn, I just noticed the DRM info app now shows L3 for the first time instead of L1. Interesting. 🤔

EDIT: Ah, it seems L3 is indeed a compromise of using the module. Shoot. Now back to the drawing board to figure out how to get past that error without using the liboemcrypto module. If possible? From the readme: "Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality,"
[Magisk] Umgak:
Most stable solution so far is to dump props from an older device & version that not many people will be using and use that instead of public prints. Bans seem to be based entirely on volume - and the public prints have tens of thousands of users.
[Magisk] Iridule:
Try clear Netflix cache and data or uninstall and reinstall
[Magisk] Iridule:
Probably because it's used by many in the fix integrity module...may have got banned today :) pm me ill give a working print.
[Magisk] ArzZenic:
Wow, 14.5 banned in record time? :D

8hours since release, congrats for burning another FP (kudos Xiaomi.eu devs), now with the burn speed of thermite.

View attachment 6045487
[Magisk] Iridule:
Literally 8 hours...check back here to watch them burn...

PlayIntegrityFix/module at main · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] Iridule:
@ArzZenic though I do wonder where these prints are mined from... I've never seen any used in the module on the sites I've been using and I've got 50 working ones and 5 I consider rare with API 30 from very obscure sites that have to be translated
[Magisk] ArzZenic:
Yup, I knew that, thats why I was reacting to you.

This is just so sad.. and actally ungrateful to the community. Even me, who is in no way an advanced user, got my own custom FP via help of @osm0sis and @badabing2003 .

There is no excuse to be lazy, all it takes is just to read like literally 3posts which include the manual & how to push it into device via badabing's Pixel Flasher.
[Magisk] V0latyle:
Please DO NOT share working fingerprints in public threads!

For those trying to use this print, try changing your First API level and try again. Suggest 23, 25.
[Magisk] sawdoctor:
It was the print provided/included in 14.5. chiteroman shared the fingerprint as a json file as well. I totally with you but he was only sharing the bundled fingerprint
[Magisk] V0latyle:
Fair enough

@chiteroman I don't know why you keep ignoring expert advice, but I'm going to say it again: Please stop bundling fingerprints with your module.. This is a problem because everyone using your module will be on the same print, which makes it more obvious to Google.

For now, I (and others such as @osm0sis) suggest that you ONLY support custom prints, until you develop a way to assign a random print to each user.
[Magisk] okij:
🎶🎵 Burn mother-fp, burn! 🤟😎

Mr. Play Integrity just wanted to show us that he has more than a 9-to-5 job at Google. Or he needs to earn some extra money by working overtime. 😂
[Magisk] ArzZenic:
It's year's end bonus time, ofcourse there is a lot of GDevs, who love to lurk this awesome forum. Every info they can bring in before their 1:1 is a plus :D
[Magisk] ArzZenic:
TBH osm0sis via his fork already does this :) He only has custom FP support.
[Magisk] V0latyle:
I know, I'm using it.

What I'm saying is that we should either:

Only use custon prints and let people find their own (best solution)

Not include a default print with the module and maybe find a way for the module to pick a random working print

Either way, the net result is the same: We need to avoid mass use of the same print, everyone should be using different ones.
[Magisk] xSnowLeopardx:
Chilling with v14.4 and custom FP :giggle:
[Magisk] sawdoctor:
Do you know any of the miui Devs? @chiteroman has started to use the fingerprint they use to minimise the amount of fingerprints burnt. Pressure/reasoning needs to be put on the custom ROM devs as well. Everyone using the miui EU roms are all going to be using the same fingerprint which is just a bigga problem
[Magisk] ArzZenic:
@ingbrzy ? As the Admin and MIUI Multilang project leader MIUIos.cz, maybe some insight?

Also, unfortunately the xiaomi app (apk) can be decomplied in like 3seconds, so it doesn't solve anything, if they use 1 FP at a time, see:

View attachment 6045505
[Magisk] switchem:
I deleted and reinstalled but same result.
[Magisk] switchem:
Was this addressed to me?
[Magisk] wide_load:
We could create a little API to return a random valid/working fingerprint. Then modules like this could hit a URL on each boot to request new one.

I could do the code for that pretty quickly but a few people would have to help out finding valid values.
[Magisk] V0latyle:
I don't.

It would be better if these fixes didn't have a print built in, but rather picked a random print from a collection. I think it would be fine if that collection was only random prints (although not ideal) because as long as it was randomized, this means that fewer people would be using similar prints, therefore less likely to be detected.
[Magisk] wide_load:
Idea being, keep the full list out of public view but all everyone to grab one or two from it :)
[Magisk] V0latyle:
Yeah, this would be a better solution.
[Magisk] ArzZenic:
The best idea FOR EVERYONE, who wants Wallet to work, just to make like 30mins to 3hour effort to find their own individual FP.

All you need is PIF module, ADB, repo with FPs, Pixel Flasher (to make it faster) & TB checker.. It's not rocket science.
[Magisk] Iridule:
Pretty wild the fp I posted (included in the module btw) was removed when it's in clear view on the creators GitHub page...I figured if I post it people will realize it's a waste of time to keep burning prints...soon they will all be gone and you'll have to dump your own room from a device to get a print.

PlayIntegrityFix/module at main · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] sawdoctor:
Tbh we are only guessing it's the number of users with the same print triggering the ban. It could also be Google are just watching this thread/chiteroman GitHub/miui ROM.

Either way we've all been saying the same for weeks but unfortunately the only thing that's changed is custom ROM devs and chiteroman seem to have agreed to use the same print.

Chiteroman posted a poll if he should keep supplying prints and 80% voted yes so it seems the silent majority won 😞
[Magisk] Iridule:
Ok no more sharing prints from the module.

Also, You can just change API to 00 as well and it will work.
[Magisk] ArzZenic:
TBH, it's mostly combination of the number of verifications getting to Google & getting THE print on the silver plate via github & apk decompilation.

//also I'm gonna be really salty when my FP is going to get banned in 8 hours through the public 🙃 (and that's the only thing, that I can do about that..)
[Magisk] Iridule:
I'm starting to think these prints are banned by some AI or once a limit of users is reached.
[Magisk] okij:
Nah. Doesn't happen on weekends.
[Magisk] wide_load:
I know it's easy enough; my point was we'd be able to better control how the values are used. Atm a lot of people will be trying obvious brands still so those will stand out and get banned. If we have a controlled pool we can keep the usage perfectly even so there won't be any outliers at all - and maybe none will get banned at all.
[Magisk] Iridule:
I just checked the modules print it works with API 00 or even 0-21. Every single print I have ever found that API can be changed you can simply put 0 or 00
[Magisk] ArzZenic:
Wouldn't that pool of jsons have to be somewhere on like a secured server and also E2E encrypted, so nothing could read it?

It that even possible through Magisk module?
[Magisk] Iridule:
I bet randomizing a pool of like 50 prints (random for each user) every hour or so would work, but it would be a pain to clear google services each time. Now that Wallet is it's own app and does not use GPS for transactions it may not be so much work, I'm not so sure. Still using the same print I found on Dec 5th with no issue.
[Magisk] HippoMan:
As someone mentioned a couple weeks ago (either in this thread or the TG channel), a poll like that is like taking a poll in elementary school to ask the children whether they want salad every day for lunch or pizza.
[Magisk] Iridule:
I know you can use Android Studio to create a virtual device to dump L1 Widevine keybox to create your own encryption keys. I wonder If you can use Android studio to create test-key fingerprints from a virtual device that would pass device integirty in a similar way? I have noticed every fp that says no integrity...if you change release-keys to dev-keys or test-keys it will then pass basic integrity.
[Magisk] HippoMan:
Given the the results of this poll and the fact of PIF continuing to offer a constant fingerprint file for people to utilize, it's doubtful that this methodology is going to change. This got me to think of an analogy to the joke that I've posted here before.

The original joke:

A guy goes to the doctor.

Doctor: "So, what seems to be the problem?"

Guy: "Well, doc, every time I move my arm this way, it really hurts". He moves his arm to demonstrate.

Doctor: "So don't move your arm that way."

And the following is my newly thought-of analogy to that joke:

Guy: "Well, doc, every time I install a version of PIF with a constant fingerprint file, it soon gets banana-ed by the Googlefrinchians."

Doctor: "So don't install any version of PIF with a constant fingerprint file."

In other words, anyone who wants to continue to rely on using a version of PIF which offers a constant fingerprint will get what they deserve.
[Magisk] ArzZenic:
Actually, this is quite correct, but everytime "the arm hurts" and they do nothing & vote for public FP, all of us, even them, get a little chip of our "arm" (defense) fu*ked, until the "arm" doesn't move anymore.
[Magisk] sawdoctor:
Your preaching to the choir with me. Totally agree with you but unfortunately a lot of PIF users are too lazy to even read the release notes or op yet alone look for prints.
[Magisk] HippoMan:
Yes, I know. But fortunately, given that there are hundreds of working, downloadable PF's out there, and given that only one PIF-based public FP at a time gets banana-ed, we who manage our own custom PF's will not see the supply get depleted for quite a while.

However, in any case, even if there were an infinite number of custom downloadable FP's to choose from, I believe it's just a matter of time before the Googlefrinchians close that door ... either by starting to enforce STRONG integrity for their own apps (such Gpay and Wallet), or by simply coming up with some sort of effective block for spoofed FP's.

So, our days are numbered, any way we want to look at it.
[Magisk] stanley321:
I am so glad that I did find a working custom FP, no more worrying that I can't pay with GPay at stores, no more updating PIF every week.
[Magisk] wide_load:
Yeah the values that form the json would go in a database table then we have a little script that picks a random one and outputs the pif.json.

There was a version that pulled the json from the github repo - basically like that but without making all of the valid values visible at once.

Sure Google will be able to see the value once it gets on to the phone - but they'd be able to do that anyway since we send it to their servers :P
[Magisk] ipilcher:
At a guess, they want a human being in the loop to ensure that they don't accidentally ban the actual devices from which the banned print came.
[Magisk] ArzZenic:
I do !completely! agree with you. "Whose looks, those finds" :) But you know, its still a limited pool, until the Google says "enough". And I would like to not spend 2hours more than necessary, because people are lazy (Now I look like I am lazy hehe)

But I believe, that the time before "now" and "enough" should be more comfortable for people, who do something and not for people, who do nothing.
[Magisk] ArzZenic:
I completely understand you.

But I'd still be more fortunate towards the reasoning, that if you wa't to use the Wallet, you should abit work for it. (devs have done most of the hard work for all @chiteroman, @osm0sis, @badabing2003).

Concept which is for most people completely unreasonable is, that everyone should give 30-180mins for their GWallet to work for weeks.

Don't be misled, I have highest respect, I sincerely salute and bow to him, for the original DEV - Chiter, I just don't understand the reasoning under the public PIFs.
[Magisk] HippoMan:
I agree!

I'm just pessimistic about our long-term prospects.
[Magisk] HippoMan:
Yes, but I believe that eventually, they will manage to fully software-ize that procedure ... maybe using Bard.
[Magisk] wide_load:
It kinds depends if they care enough, before the last couple of weeks the same fingerprint worked for months and months and in the past they've worked for literally years.

Someone important probably complained that the Play Integrity API wasn't actually any use so that's their focus for the time being :P
[Magisk] HippoMan:
Let's hope you are correct.
[Magisk] sawdoctor:
Tbh they starred to be a pia after Displax released the strong integrity fix. Like osm0sis said they don't mind us rooting and spoofing they just want us to be more discreet about it. Unfortunately we are definitely not being discreet any more