yashsingh1/xdaforums huggingface dataset:
[Magisk] V0latyle:
Hmm. What is your configuration? Magisk version, apps in DenyList?

SInce you're using a custom ROM, may have to spoof additional props to get BASIC. DEVICE won't pass if BASIC doesn't pass

I might have misunderstood your prior statements. Did you ever pass BASIC after flashing PixelOS?

Perhaps you need to try a new print. Pickaprint will not automatically find a working one; you have to keep trying prints until you get one that passes.
[Magisk] glennza:
I have ordered the Ticwatch Pro 3. That might be worth a look.

https://www.xda-developers.com/mobvoi-ticwatch-pro-3-review/

Good deals on Aliexpress!
[Magisk] vamteusz:
Ahhh, sorry, I didn't have Google Play Services in DenyList. After this change I pass basic integrity every time. For now I rolled about 20 times but I need to roll more because I didn't get device integration yet. Thanks!
[Magisk] V0latyle:
You shouldn't need Play Services in DenyList. I don't even have Wallet or GPay in DenyList, only a couple of banking apps.
[Magisk] vamteusz:
without it I can't even pass basic integrity.

1. magisk 26.4 (has different name), only google play services in DenyList (gms and gms.unstable)

3. yes, right after flashing when i didn't used pickaprint yet.
[Magisk] Nergal di Cuthah:
Everyone missed out on that for not taking Palm Webos seriously. All it needed to root and mod was konomi code (type in upupdowndownleftrightleftrightBAStart and you were rooted
[Magisk] Umgak:
I don't know why you did that when I explicitly told you not to. In any case, though, it won't work - DenyList unmounts all modules and Magisk binaries within the targeted processes, meaning Play Integrity Fix isn't even running now.

You should be able to pass BASIC and DEVICE with DenyList completely disabled so long as your prints are good and your json is correctly formatted - that's all I can think of at this point.

Logcat output may also be helpful in diagnosing your issues. adb shell "logcat | grep PIF" immediately after boot should give some helpful information.
[Magisk] poulopoulosa:
Hello peeps after a long period of time I found a working print. I was desperate earlier and thought that it was the module's fault.

I am saying it as few people write for successful prints. I have a pixel7 pro latest osmosis fork.

I was kinda ready to give up with finding a print. I had no Gpay and Google secretly updating my Vanced YouTube to the latest version. So I felt helpless to their power. But I stopped abd thought that this is my device and I will do whatever I want. Every morning I would uninstall and reinstall old Vanced YouTube app. Tried different stuff. However I found a solution for that by using hideMyAppList and this encouraged me to search for a working print.

All I wanted to say is that at times it might feel you are hitting a wall but perseverance gets rewarded...
[Magisk] Yellow571:
I'm not sure what's going on with my setup, I recently unrooted my Pixel 4a and flashed stock ROM (previously LOS) and device integrity still fails. Am I missing something obvious? I just needed to login to Snapchat before rooting again but I still cannot do so because of this.
[Magisk] xSnowLeopardx:
What's the status of your bootloader?
[Magisk] BunnyPig1:
Thank you for the great explanation. I really appreciate the time you put into your answers! Made me a bit smarter about the entire situation.

Interesting! If you find anything interesting (even if it's not helpful in this specific topic) please, do let me know! I'm very fascinated by all this even though I don't know much about Android other than some small tinkering.
[Magisk] Yellow571:
Currently unlocked, version s5-0.5-10252351. Does it need to be locked to pass device integrity? I'd prefer not if possible because it might risk Verizon preventing me from unlocking again.
[Magisk] intel_core_i7:
You can use zygisk detach to prevent YouTube being seen in the app list and updated by Google Play (services)
[Magisk] V0latyle:
No, that's the whole point of this thread. BASIC and DEVICE can be passed by causing Play Integrity to fall back to basic attestation instead of hardware backed, by use of a fingerprint of a device that would only be able to pass 2/3 because devices pre Android 8 are not capable of hardware backed attestation.
[Magisk] osm0sis:
Updated again to fix a regression from the Christmas script release that broke generic value detection. 👍
[Magisk] pndwal:
Some custom ROMs integrate their own spoofing to pass integrity verdicts, and some do so in a "strange" manner that breaks PIF if used, eg XiaomiEU was notorious but now publish both ROMs with their fix and 'clean' ROMs that work/don't break PIF... I'm guessing your PixelOS may be an example of the former...

If the integrated spoofing works before rooting (ie is not outdated), this will with root simply by adding the main and DroidGuard GMS processes you added to denylist to hide root from GMS... Note this should not be done if using PIF as, just like USNF, it integrates its own Zygisk based root hiding... If you only get BASIC_INTEGRITY that way (nb. you must have uninstalled PIF) you can assume ROM spoofing doesn't exist or its spoofed props are outdated ('banned'/blocked by Google)...

If ROM itself spoofs and prevents PIF from working (must NOT have GMS processes in denylist), you should check a ROM update (incl. spoofed props) has been produced or switch to a 'clean' ROM (ie. one that doesn't integrate spoofing for PI verdicts). 🤠 PW
[Magisk] pndwal:
Thanks for the additional information...

Still not not sure if newer IN region devices now accept locking with other Global variant ROMs or if other Global region devices accept locking with IN (Global) ROMs due to recent addition of India to hardware enforced regions (now 3, includeing China, India and Global) which you haven't covered... I do know that the measure was taken in order for Google to comply with CCI (Competition Commission of India) findings/requests and affect whether Xiaomi’s messaging app and dialer app are bundled instead of Google Messages or Google Phone on IN (Global) region devices among other things...

Aside from the above, please say what you think I'm surprised or confused by. 🤔 PW
[Magisk] intel_core_i7:
Should work though, I don't know why it should not since the ROM is still "MIUI Global". I can understand why you asked, because IN variant was made in India instead of China and may have -in suffix in codename. I may be wrong.

If you're not confused then probably the first guy was, if not then I was mistaken
[Magisk] pndwal:
The only things I'm currently questioning is whether Global device can be locked with China ROM (many say not, some say can although clearly China device cannot be locked with Global ROM) and what (locked) combinations are now prohibited by the new hardware region enforcement for India devices. (As noted, with India this is now expanded to 3 device variants; no longer only China and Global)... PW
[Magisk] pndwal:
MIUI Global ('bastardised'/ unstable) and MIUI China ('pure'/original) are simply the two incompatible software ROM variants and have nothing to do with hardware region locking... That's due to governmental, licensing and other differences...

Actually, Ive just seen another confirmation that Global devices can (technically) be locked with China MIUI ROMs, but (presumably since they've not been tested with pure MIUI) some devices may not turn on if locked... PW
[Magisk] intel_core_i7:
I would say India is still within "Global", because even non-India devices may still have difference in hardware, namingly NFC (cost cutting) and camera (Leica on Xiaomi 13T series being unavailable in some regions, 13T series are not sold in India).

What do you mean by that, the device bricking itself when installed with a rom from another "Global" region or the hardware being disabled by software like NFC-F on global Pixel device? Because on Xiaomi devices when it's unavailable it's because the hardware was completely changed/removed.

Very few will be willing to do that, since chance of bricking is high (well because doing the other way, locking China devices on global rom will brick) and to resolve it will cost quite a lot, reflashing original firmware via EDL on newer devices won't be free for a while (unless someone finds an exploit)
[Magisk] V0latyle:
Just going to throw this out there...

Someone who participates in this thread tested well over 28,000 prints on Play Integrity Fork v5...and had 6,517 that passed DEVICE. That's just shy of a 24% success rate.

Just in case anyone was feeling discouraged about finding working ones.
[Magisk] Umgak:
I'm skeptical about 100% success rate, considering mine personally were closer to about 60% - but still, either way there are far more working FPs than you might think with how many got 'banned.'
[Magisk] Iridule:
Still using first print found nearly 31 days ago. The print I shared privately with 18 people is also still active and working. ;)
[Magisk] pndwal:
Yes, it's a Global compatible ROM, but not because of hardware... Hardware will simply either work or not on devices it's not aimed at... Global ROM has been described as "far from MIUI" (meaning the original China developed MIUI, before any of the non-Chinese-specific applications and features like Google Phone, Messaging, and Contacts apps are substituted... These result in the system running unstable and "far from MIUI" because the MIUI structure is reconfigured to resemble pure AOSP .Pure MIUI is different so Global and China ROM applications cannot be cross-installed... This is the reason for the two software variants...

Hardware enforcement of regions when devices are locked may have happened to coincide with the two MIUI software variants in the past but can be enforced regardless of which MIUI is used... It restricts stock/locked use because of governmental, licensing and other differences... Other differences could include incompatible hardware but not necessarily...

Nb. recent hardware enforcement for India region may be due to the need to make MIUI messaging app and dialer from China ROM work interchangeable with Google Messages or Google Phone on IN devices (they can't ordinarily be cross-installed as noted above) to meet the CCI (Competition Commission of India) requests/requirements, making for a third incompatible ROM structure despite it being a Global MIUI variant (it actually must restore some pure (China) MIUI compatibility while remaining as close to pure AOSP as possible).

Yeah... To prevent devices being locked with wrong ROMs for the reasons I've given...

The reason Global devices can be locked with China ROMs (some may fail to boot due to unintended/untested configuration) but China devices simply can't be locked with Global ROMs is clearly to enforce different governmental and licensing requirements...

Yeah, I don't know enough to be sure "fail to start" means only soft brick... Those who try should certainly do their due diligence... PW
[Magisk] trevtdogg:
just to be absolutely clear - V0latyle means to say yes, for phones with hardware attestation the bootloader does need to be locked to pass device integrity without any spoofing. once you unlock the bootloader of a phone that uses hardware attestation (which is any model launched with android 8 or later i believe) then you will immediately fail device integrity.

the only ways to get device integrity passing on those phones is to lock the bootloader again with stock rom and get hardware attestation working, or use a play integrity fix module with a fingerprint spoofing a different device that requests software attestation instead.
[Magisk] intel_core_i7:
Actually to an extent, they can. People here cross install the apk of some system apps of Global ROM (might be modified, but posts indicated that it's directly extracted from Global ROM) onto Chinese MIUI to make system components display in Vietnamese (MIUI CN only bundles like 3 to 5 languages)

The wording got me confused... But I got what you said. The unstableness and the differences, perhaps seems to be more and more significant in recent MIUI versions. New HyperOS thing seems to minimize this a little bit, but under the hood we all know the name change is a last-minute decision.

Many including myself would say it's to deter international users to buy Chinese devices from gray markets instead of buying in their partnered stores. Chinese variant always sold at a way cheaper price, sometimes $200-$300 US so they should have some tricks up their sleeves to prevent revenue loss
[Magisk] Vision:
Old good days
[Magisk] mesiu84:
But why if it's the same fingerprint it doesn't work with version 15.1 but works with version 14.6?

I even have my own fingerprint (pulled directly from one of my old phones) and that one works with version 14.6 (I can see it's applied in logs) but it doesn't work in version 15.1.
[Magisk] simplepinoi177:
I was wondering if that was the case -- you didn't specify if you ever ran 15.1.

So, I imagine it has something to do with under the hood stuff. chiteroman did a whole bunch of things after 14.6 that caused it not to work -- to the point that many people still can't have it working properly at 15.0 & 15.1, and so much so that that's why 14.7 was skipped and almost went straight to 14.8 after 14.6 and the decision to no more embedded fingerprints! @osm0sis has spoken/commented to the numerous bugs and inconsistencies since 14.6 in one or two of the posts in this thread...I imagine something like that is happening to your set up -- which is why the fingerprint and your own fingerprint works in 14.6 but not the newer one.
[Magisk] sawdoctor:
What

What base is pixelOS? If it's based on A14 beta that maybe your problem. PIF 14.0 works best for me on A14 beta, the later versions and forks can cause issues but it could also be something the Devs have done, is there anything in thier support thread?
[Magisk] sawdoctor:
When i tested 15.1 it took my working fingerprint and renamed it pif.json.old and replaced it with a blank template. Are you sure the same hasn't happened to you
[Magisk] dmenezes:
This is *exactly* my use case for PIF.
[Magisk] dmenezes:
That's the spirit!

Congrats and welcome to the club!
[Magisk] dmenezes:
The *real* good old days were not with WebOS but with PalmOS: for a lot of my uses, it was faster and worked better than Android *and* had more useful features, while using much less resources and exposing much less of my privacy.
[Magisk] dmenezes:
More probable IMO is that it's cheaper because effing CCP subsides the heck out of it.

This would explain not only how it can be so much cheaper in China, but also why they don't allow it to be flashed with Global ROMs: they don't want their slaves citizens getting rid of the tons of monitoring and spying the CCP no doubt forces Xiaomi to embed into their Chinese ROMs.
[Magisk] xSnowLeopardx:
1 month 1 day later -- all is still good with my FP.
[Magisk] intel_core_i7:
Perhaps
[Magisk] ace2nutzer:
Play Store got an update and DEVICE is still passing! Hell yeah! (y)
[Magisk] badabing2003:
Because 15.1 requires additional keys in the pif.json file.

I bet you haven't added those.

One of those fields is to force basic attestation, if you don't set that to true, it will never pass for you.

I suppose @chiteroman added that so that he can use it with his strong passing keys by setting it to false.

Try this, load your pif in PixelFlasher in the bottom pane of pif manager, and hit the smart paste and update your pif.json.

See if it passes.

Other than that I don't understand the obsession of always using the latest version, if it works with 14.6 what compelled you to change to 15.1?
[Magisk] Vision:
Yeah true, after the Google and other manufacturer get greedy and make the ROM and the android less useful and only for profit
[Magisk] V0latyle:
Well, it was all trial and error. IIRC he scraped the Tadiphone dumps for props and tested them all. I'm not sure how many total prints he tested, or what criteria (if any) he used to sort them. All I know is that out of all the prints he tested, he found 6,517 working ones, and I believe this was out of more than 28,000
[Magisk] HippoMan:
And that's *exactly* my own use case for a leather wallet containing plastic bank cards.
[Magisk] dmenezes:
+1 to this: I'm not into cellphone payments either, and don't plan to be as I always carry my wallet anyway.

If it wasn't for the effing apps that insist on DEVICE even when it's makes no effing sense, I wouldn't bother with Play Integrity at all.
[Magisk] intel_core_i7:
None except google pay require it here, very fortunate
[Magisk] intel_core_i7:
plastic cards? that's a luxury thing. I use paper and polymer thing that has numbers and figure of someone on it!
[Magisk] HippoMan:
Oh, yes, and also those small metal disks with more people's figures on them, correct?
[Magisk] intel_core_i7:
we don't have that here, unfortunately. (or fortunately?)
[Magisk] V0latyle:
They say "money doesn't grow on trees" but paper is literally made from trees so

Can I use cash for contactless pay?

Better yet, instead of using some sort of currency with no real value, can we just trade? I'll give you some of my food in exchange for some of your medical supplies
[Magisk] Umgak:
Ah, but there's also the ugly deception - money isn't made of paper! They're often made of cotton, linen or other textiles. If you're in Canada (or a few other countries), your money might even be made of plastic! So money doesn't grow on trees, it's actually grown in cotton fields.

I wouldn't say that 6,517/12,000 counts as "100%." That's closer to 54%, which is still a lot of fingerprints. So no fear of running out any time soon, more likely Play Integrity team attempts to find some way to detect our hooks or block all mismatch situations globally.
[Magisk] lmvuong1997:
Working perfectly!
[Magisk] Utini:
Same here. ATM all my apps work with only BASIC but I guess it's only a matter of time until all the 2 factor auth apps and banking apps turn against me.
[Magisk] V0latyle:
Dangit, you're right. 75% cotton, 25% linen.

True, when I originally typed that I was referring to the fact he only had 266 failures out of 6,517...but after reading more I discovered those all passed on retesting. I'm not 100% sure on how many TOTAL prints were tested, I think around 28k. I've gone back and edited my posts.

As @osm0sis pointed out we have the ability to spoof pretty much everything in userspace so I honestly don't know how effectively the PI engineers can combat this. It doesn't seem like they're really interested in "defeating" us entirely - they just want us to be more creative. In this regard I think @TheFreeman193's PickAPrint is a huge step in the right direction - randomization of prints, coupled with the ability of Play Integrity Fork to spoof more props.
[Magisk] simplepinoi177:
That, and the fact that they are only seemingly temporarily banning/burning fingerprints -- as proved that the 14.6 fingerprint works a couple of weeks after they banned it and only then we moved away from it....
[Magisk] TraderJack:
There were about 34K unique prints tested. This is what was able to be generated out of probably over 50K prints collected. some were duplicates, others could not be properly generated from required dump files. Additionally, the 34K tested were not even filtered down initially for Android version. If we filter out incompatible versions the unique prints tested were probably closer to around 21K.

So out of 21K unique prints of likely versions that were actually able to be tested, ~6.5K passed.

That means ~31% hit rate.

EDIT: Small correction as I didn't factor in removed duplicates from those non-passing. So there were actually only about 20K unique eligible prints, which moves the success rate closer to 33%.
[Magisk] simplepinoi177:
I'm fascinated at how you tested 50,000 prints. Was this using TheFreeman method? I'd be interested in seeing a full write-up on how you went about it -- and more particularly getting ~6500 fingerprints to pass DEVICE!
[Magisk] TraderJack:
This was using my own methods, though I am in conversation with TheFreeman now in addition to several other community members who have all been engaged in similar pursuits. We have recreated each other's work in some regards, but the testing of these batches was done using standard methods which have been discussed in these threads in one regards or another.

There is nothing magic about it, I am only able to test about 5 prints/minute/device so yes, this has been ongoing for a few weeks now. Additionally, many of these prints were tested on more than one occasion (in fact all of them processed at least twice, if not 3 times).

The information to mine your own prints has been spelled out enough in these threads. TBH, it isn't a good idea for anyone in the community to make anything clearer than it has been. As it stands, anyone with the least bit of gumption and know how could repeat my work and make it public which would likely be disastrous.

These posts are simply here to say - it isn't that hard to find a working print. If you have *one* that works for you that's all you need. I don't suggest anyone do what I did, as it isn't necessary for your personal use. We are attempting to do analytics and come up with a solution that might work better down the road for everyone. For now, if everyone tries to do what I did you will likely make things worse. Ofc I can't control what people do, but this is just my recommendation.
[Magisk] simplepinoi177:
Oh okay...cool! I was just curious if it was more along the lines of what @zgfg described he'd been doing (I'm betting he's even one of those you are collaborating with) and if it was a method that hadn't been described here in one way or another, or if it wasn't a more manual way. Thanks for clarifying.
[Magisk] Yellow571:
Thanks, I'm not fluent in this topic so I was a little confused. Anyway, my setup is now stock ROM with official Magisk v26.4 + PIF-Next and HMA. Basic and device integrity now pass however Snapchat still locks me out. I have it added to denylist and HMA but no change. Is this something I can fix?
[Magisk] rodken:
I totally get where you are coming from, spoofing userspace like boss level ninjas. I seriously don't think the PI folks are out to crush the creativity entirely. They're more like the gym trainers keeping us sharp, right? New checks, fresh challenges, just fuel for the next level-up.

On a real note, spoofing's cool and all, but it's a double-edged sword. Wrong hands, bad things happen.
[Magisk] V0latyle:
I'm not sure about gym trainers...I think, as I've mentioned before, that it has more to do with the fact that Google Mobile Services is a proprietary product that they're trying to market, and PI is just one of the many APIs provided through GMS. They're constantly trying to improve their product, like anyone would, and in so doing means they're inevitably going to fix some of the exploits that we are using. I don't think that they are fixing these exploits explicitly because we are using them, but rather it's a matter of coincidence.

The one possible exception would be banning fingerprints in mass use. With prior versions of this and other modules, everyone was using the same exact print. I don't know how many people there are with rooted devices using these fixes, but it's definitely several thousand, possibly tens of thousands. So, when they see their servers getting spammed by thousands of devices all using the same print, it seems like abuse and they take measures to mitigate the problem.

The good news is that it seems temporary, because some of the prints previously used are magically working again. So, this tells me that our "creativity" might simply mean we all need to use different prints, that way we aren't abusing a particular one.