yashsingh1/xdaforums huggingface dataset:
[Magisk] WhoIsJohnGalt1979:
I have been on v2.0 the day it was released all the way to version 170 on both mine and wife's pixel 8 pros. Same two finger prints since November I reckon and backup prints all working as of yesterday. I take the backups on a test drive once every month. Lol have a folder called Fork which has all the backup prints beautifully generated using your gen_pif_custom script.
[Magisk] 4sz0m:
Momo detects your device's real fingerprint. PIF spoofs the print only for DroidGuard.
[Magisk] :
Good. No vanity strings. So you just need to find a working print.

As written before (sigh, yesterday?) go to playstore - settings - info and tap playstore version until you are developer. Then go to playstore - general - developer options and test your integrity.
[Magisk] CZ.Kostra:
1. leave momo alone

2. install this app: Integrity Checker

3. take the test
[Magisk] 4sz0m:
Or just don't use any 3rd party app, and do it instead in the Play Store:
[Magisk] badabing2003:
You said you're creating prints with PixelFlasher, but it looks like you haven't read the usage guide.

As for your other questions, they're all answered in the FAQ.
[Magisk] CZ.Kostra:
I agree, but I'm trying to make it easy for him. 😉
[Magisk] 4sz0m:
To be frank, @badabing2003's right - we've probably gone beyond the reasonable level of help. Best to point out existing documentation (and I'm saying this to myself too) ;)
[Magisk] zgfg:
Forget Momo - Momo does not test Play Integrity

Besides, you will hard, if ever, satisfy the Momo

Hence Momi is out-of-topic here and waste of time. If you are interested in passing Device Integrity, follow the instructions you were given
[Magisk] xSnowLeopardx:
That one? Would really recommend this one if you are going 3rd party.

TB Checker
[Magisk] YoShake:
It's not about getting info from build.prop from my currently installed rom on motorola. It's a GSI image where all the info contains some kind of generic data, and I doubt that using it will help passing integrity check. Like for example:

ro.product.system.device = generic

....manufacturer = android

that's why I asked for help getting build.prop file from stock rom image file I have in case of I would ever have to revert back to stock. All tools I knew and had from eyars ago are not anymore suitable for this.

Installing stock rom on my phone only to get th build.prop data, and then getting back to custom rom with all config, apps and so on is really not worth all this struggle :(

Getting the info from my older moto is worthless, as it's working on LoS for long time, and from things I've already read all popular custom rom kernels are already blocked.

But, since I've got some older LoS version I might give it a try.

mucho thanx for explanation and clarifying things about all this mess.

As I mentioned above, replying to @zgfg I ended up with GSI image from over a year ago, unfortunately without any further updates. Thus now when some apps require g.play to work, and magisk's safetynet module became obsolete I have to look for other solutions. And things complicated a lot more for over a year.

I'll try to get the build info of my old phone, as reinstalling stock rom only to get original properties and revert back to GSI with all things is helluva lot of work. Not worth the time.
[Magisk] zgfg:
Without root you can still grab all props by:

adb shell getprop

However, you won't have them in the input format for the gen script (however it was called) but you can manually create the json from the props (for some fields you will probably need to experiment with the combinations you will find in the props)

Compare how the script looks for the props . If it reads from vendor, you should use the corresponding prop with the vendor prefix, etc
[Magisk] osm0sis:
Not a fan, personally, with all the unnecessary root checking stuff; sends people on fanatical quests to pass it all when they don't even have real apps that need it. Same goes for RootBeer, Momo, and Native Test/Minotaur.
[Magisk] badabing2003:
Or you connect to PixelFlasher and do Device | Get pif print and get it in JSON only the fields that matter.
[Magisk] Umgak:
They're on GSI wanting to dump stock, so they'd have to extract them from the build zip. There is no shell to run commands in, no device to connect to PixelFlasher.

This is a much more in-depth question, and is device-dependent. You will need to determine the format the update is in and the tools needed to extract that format. A great utility for this is the file command on Linux for determining what format .img files are in, if a tool like 7-zip can't pull them automatically. If you don't want to set up Linux (or WSL) it's also available in Termux on Android or via git bash on Windows.

As mentioned, though, the exact steps are device specific.
[Magisk] badabing2003:
I was merely responding to @zgfg
[Magisk] pndwal:
Not really a fan of TB either, but such apps, especially Momo and Native Test (as well as Applist Detector and/or Ruru Detector) are very useful for comparing installations as well as what banks in the wild may be detecting (eg if injection is detectable to degree these apps are developed, and Native Test for example has usually not lagged behind new bank methods for very long... Seems to be updated more often than Momo currently)...

Of course for deviceIntegrity verdict purposes (ie. PIF), these are indeed totally unnecessary/superfluous (they're 'root checking stuff' as you said, or may offer means for testing the extent to which users have been able to hide suspicious traces or even presence of 'suspicious' apps etc detected by banks willing to abuse/exploit loopholes, eg. QUERY_ALL_PACKAGES permission etc) so simple Play Integrity API checkers (with ability to view raw JSON) are really all we need here.

... Just that many banks don't even care to check PI, or maybe do that along with all kinds of root trace detections and other opportunistic searches for apps or mods they deem compromise our devices...

In these cases (where banks don't simply trust Google's PI API, which may be most in practice) such detector apps can be very useful tools provided users take a pragmatic (as opposed to an uninformed 'give it the works' or 'fanatical quest to pass' everything) approach; ie. use these for comparative purposes, to compare your environment with user's who are able to use certain apps or to check if a hiding approach has likely worked.

🤠 PW
[Magisk] zgfg:
Then I don't get you - once you would go to flash the stock, stock would itself overwrite all the custom props from GSI

You cannot just replace custom props to stock - if you want to save from flashing (and factory resetting)

Or if you still want to have build props from your stock ROM, look for public repositories with extracted dumps for your particular device and ROM version, and download from there

Repos were available and long ago links were here, but that's the usual cat and mice game, you might need to google - actually, there is, and still is active, one TG channel with that link in 'impressum')
[Magisk] shadowstep:
I only use it because it's a better looking app than Play Integrity API Checker. 😛
[Magisk] zgfg:
But TB Checker is really good app and there is not a big problem to setup things to pass all its Root and XPosed detections (unlike with Momo or Minotaur)

And that's really useful for anybody who need to setup things for his bankng apps (since they go beyond the plain Play Integrity and it's absolutely not true that they all 'require' Strong Integrity, locked BL, etc)
[Magisk] :
A question if I may, more to check my understanding of the subject than anything else.

I have an old phone, a OnePlusX, running lineage 20, magisk alpha, enforced deny list and PIF. An identity app (a French one, Identité Numérique) runs happily as do my banking apps. No idea about wallet, it's moot since the device doesn't have NFC.

My primary phone is a Xiaomi Rednote 10s running RiceDroid (Android 12L) + as above. Banking apps and Wallet all work BUT the identity app does not - it detects root. (uname - r gives 4.14.186-perf-.....

I'm guessing the key difference is the age of the device. On the newer device, a hardware (?) level check can be invoked. Would that be about correct?
[Magisk] pndwal:
Assume RN10s has PI DEVICE_INTEGRITY... Running Magisk?... What version?... And is OPX running fairly late Alpha Magisk?... PW
[Magisk] Vision:
@chiteroman Xiaomi Poco X3 NFC fresh flash Android 11 MIUI 12.5, i try the 15.8, and pass 2/3 but after i add some google accounts and all detect as connected device the spoof FP why ? i delete the module and the account, add it again the account but not send me email new device connected with my real device. is this problem ? or can ignore
[Magisk] osm0sis:
Right, but Native Test/Minotaur has also been known to add things that aren't even being exploited in the wild, which developers are then pressured to implement, which seems a bit silly and wasteful of people's time, even if it is technically proactive. 🤷‍♂️
[Magisk] :
Thanks for the reply. Yes, The RN10s has DI (2 green lights on PIC) and is running Magisk alpha 27000. The OPX has the same version of Magisk.
[Magisk] xSnowLeopardx:
You are not a fan but proceed to give arguments for the app's other functions, but the checker itself is what works well for me. :)
[Magisk] osm0sis:
Well yeah, nothing wrong with the PI checking part. I'm just saying simpler is better, with no bells-and-whistles to confuse an uniformed newer end user, so I like Nik's PI API Checker. 😛

That and I still like YASNAC in addition to checking with PI API Checker, since it still provides some useful information we don't get anywhere else.
[Magisk] 4sz0m:
I'm curious, what information can we get from YASNAC that we can't from TB Checker? Or you're comparing with only Nik's here?
[Magisk] osm0sis:
See my explanation from a couple months ago here: https://xdaforums.com/t/how-to-sear...e-noobs-from-one.4645816/page-2#post-89220253

:)
[Magisk] 4sz0m:
Thank you - that's really useful information... and I missed it (is EOY holidays an acceptable excuse? :))
[Magisk] osm0sis:
Well, things seem to have gone smoothly in both private group testing and in early public testing over in my Odds thread, so let's open it up to the wider group in this thread for final testing... 🙌

PIFork CI #172 (v8 Release Candidate) is up to expand support of replacing/hiding specific conflicting ROM spoof injection apps/overlays from any directory to now also allow any file, and has added some more default conflicting ROM spoofs to go with that, as well as some other minor fixes/cleanups/improvements.

Commit diff log:

Comparing v7...main · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - Comparing v7...main · osm0sis/PlayIntegrityFork

github.com

Build: https://github.com/osm0sis/PlayIntegrityFork/actions/runs/8023130338

If nothing major happens in the next week I'll push out the stable v8 update. Please test it out! 👍🤞

Note: If upgrading from cross-fork (i.e. chit's PIF), see the section of the README here: https://github.com/osm0sis/PlayIntegrityFork/blob/main/README.md#about-custompifjson-file
[Magisk] Vision:
I'm confused if anyone can answer me

I fresh flash via MiTool my Xiaomi Poco X3 NFC to A11 MIUI 12.5 and lock the bootloader pass 3/3, after unlock and flash boot.img with Kitsune Mask latest stable and flash module, pass 2/3, the strange is, in one app show me the info of my phone and in the Fingeprint say xxxxxxxxx/ release-keys but in the Display: RKQ1.200826.002 test-keys, and the more strange is in the netflix say in info about phone, Build: RKQ1.200826.002 test-keys

If apps read test keys maybe they refuse to start regardless pass 2/3 with module?

Because i forgot to check, maybe before unlock the bootloader and flash after boot.img with Kitsune say release-keys and after unlock say test-keys ?
[Magisk] ldeveraux:
Does the deprecation of Pay for Wallet that Google just announced affect the ability to pay moving forward?
[Magisk] Nergal di Cuthah:
Ot thanks for the heads up i installed wallet and uninstalled pay, my card carried over.

Does not look like it "affects the ability to pay" as my card has a nfc icon above it. But i don't use phone payments so can't tell 100%.
[Magisk] :
@pndwal So, does that mean root is hidden on the OPX because it's older?
[Magisk] zgfg:
Android Security whitepaper with an overview of Hardware-backed Securitiy (TEE, Key Store, etc)

And a bonus for @HippoMan, about Sanitizers on the pg 25😁
[Magisk] pndwal:
Ah...

Different hardware/configuration can affect detectable root traces... Also, some custom l ROMs spoof props/signals well, some don't and others make no attempt...

And DenyList is NOT proper hiding; have you tried with Shamiko?

PIF generally has no problem causing an on-device fallback to BASIC-only attestation which is it's principal function... It's successfully bypassing server-end enforcement of HARDWARE_BACKED evaluationType for verdicts (without which BASIC-only evaluationType is disallowed even if it's used and should otherwise pass with user-space evaluated signals, for devices Google blacklist for such old school attestation), which is fortunately enough based simply in prop-based device identifiers and now some additional strings that can be edited, that's the complicated thing for PIF/modders to achieve... However it seems that you do have PI DEVICE_INTEGRITY for both devices so you issue seems to be the extra root traces app is detecting and Shamiko may help as mentioned above.

FWIW, you don't even need PIF for old devices (launched with Android 7 or earlier) like your OPX... You do need to hide root from DroidGuard (can simply add DroidGuard/attestation process, Google Play Services com.google.android.gms.unstable, to denylist) and to run a solution for setting sensitive props (original "MagiskHide props") to non-suspicious values (eg. MHPC module does that by default); Really, that's all PIF is actually doing for your old device to obtain PI DEVICE_INTEGRITY.

🤠 PW
[Magisk] zgfg:
I can't believe that you indeed have test-keys with an official ROM. Aren't you using some Xiaomi beta builds or what

PIF module use a Zygisk hook and captures requests from DroidGuard to spoof the prints it asks about

Hence if you indeed have the test-keys FP, that won't be spoofed by PIF to any other app except for Device Play Integrity attestation.

You may use the old MHPC module (but be aware that PIF looks for and disables the MHPC - although, you could modify its scripts to remove that)
[Magisk] :
I was using Shamiko with Magisk previously but was under the impression that Magisk alpha replaced the need for it. I can reinstall it (on the RN10s) and try it.
[Magisk] pndwal:
PIF hides root from DroidGuard... Bank apps may look for root using their own means and not rely on PI API... That's where proper root hiding like Shamiko may be needed. PW
[Magisk] pndwal:
No; Alpha just had the more hide-able native bridge Zygisk injection long before TJW Magisk, but Shamiko was still needed to take advantage properly. 👀 PW
[Magisk] zgfg:
Please, what is now the new about the deprecation here - afaik, Wallet had already replaced Google Pay around the globe back in 2022, except in the countries like States, India, Singapore

Google Wallet explained: Licenses, banks, new features, and the Google Pay shutdown

Google Wallet replaced Google Pay, which will shut down soon. Here's all the latest news and added features you need to know.

www.androidcentral.com

Countries or regions where you can make payments with Google - Google Pay Help

Some Google Pay and Google Wallet payments features are only available in certain countries or regions and on certain devices. Check feature availability Depending on where you live, you can pay the

support.google.com

Where you can use Google Wallet - Google Wallet Help

Some features in Google Wallet are only available in certain countries or regions and on certain devices. We’re working to bring many of these features to more countries or regions. Check feature ava

support.google.com

Since I know for and I use it (from about a year ago) I could only see Wallet on the Playstore
[Magisk] ldeveraux:
View attachment 6071792

Received this email today
[Magisk] Captain_Throwback:
I mean the email itself literally tells you that nothing about paying will change.
[Magisk] pndwal:
There's no indication in PI labels of evaluationType (ie. that HARDWARE_BACKED evaluationType enforcement is bypassed successfully)... In S/N API we do have evaluationType labels... Of course the prop and other signals used for enforcement purposes in PI have changed/been 'hardened' continually since S/N depreciation so necessary prop mismatches etc differ, however if S/N API returns BASIC only for evaluationType, PI evaluationType may already be BASIC-only or only minor prop/other tweaks needed to bypass PI API HARDWARE_BACKED evaluationType enforcement and achieve DEVICE_INTEGRITY... It thus provides clues about print/prop set viability for spoofing purposes... If you cannot achieve BASIC-only evaluationType with S/N API you'll generally be wasting efforts to pass PI without trying other prints.

Nb. If PI DEVICE_INTEGRITY is achieved it's almost certain you also have BASIC-only evaluationType in S/N, but the reverse (achieving S/N ctsProfileMatch) is not true, ie. work may be needed to achieve the equivalent BASIC-only evaluationType in PI, and you're doing it 'blind' to boot.

FWIW, looks like we'll loose the S/N evaluationType clue with it's 'Full turndown' at end of January 2025. 👀 PW
[Magisk] Vision:
Before i flash A11, had A10 official rom with same test-keys from february 2023 until yesterday

Yeah official rom, i know very strange and for that i ask if caused by unlock the bootloader or flash boot.img with magisk, you have magisk and pif and say release-keys ? without some other mod to make it release-keys ?

I extract from ROM the build.prop from system folder, i check inside and say this ro.build.keys=test-keys

View attachment 6072019

From this i download the rom:

View attachment 6071799
[Magisk] pndwal:
Yeah, but looks like they're just migrating USA etc fully to wallet as occurred a couple of years ago already for the rest of the world... Bringing Pay app 'hold-out' regions in line with other lands, although I imagine they're still going to need region specific Wallet app variants. PW
[Magisk] ldeveraux:
I still have the GPay app installed, along with Wallet, should I not? Admittedly I don't know how this module works or what's entirely needed so I kept everything the way it was. I thought something with GPay would affect my ability to use it.
[Magisk] zgfg:
Wow, so US switches from Pay to Wallet (the rest of the world did two years ago)😁
[Magisk] Nergal di Cuthah:
No need for both, dump pay if you're in the u.s. as pay is being closed as a separate app.
[Magisk] pndwal:
FWIW, when it happened here there were a few issues (so we may have been guinea pigs to an extent) but G Wallet was just an update for Pay, so on devices that came with Pay preloaded both apps were present after updating but only latest would open. Even with Wallet update, G Pay logo appears when paying. Also, Wallet becomes Pay again if updates are uninstalled, but for practical purposes it seems we use either Pay or Wallet, not both...

I'm not sure how it works for you, but seems if you are able to have both installed and use either, then for you Wallet isn't simply a Pay update... Don't know whether you should or shouldn't have both installed either, but you may already have best answers above. PW
[Magisk] purgy:
I found that when we had both (pay is now gone from my phone, except that it lives on as my "default payment app") cards would fail to add via the pay app, I was able to add them to wallet instead.
[Magisk] :
I installed Shamiko on my RN10s but the identity app (Identité Numérique) still detects root. Never mind, it's not like I need nor used the app anyway. I would like to install the France Identité app though (when they get the thing working properly!) as it can store your drivers licence, so I'm kinda hoping I can get the reasons for root detection. (I'm assuming both will use the same/similar detection method) It's a question for another thread methinks.

On the Pay/Wallet saga, as others, Pay was replaced for me some time ago. So long that I don't remember how long. Though coincidently, I looked at Wallet yesterday and found all my cards had gone! Ah shoot, I thought, if my fp hasn't been burned then adding the cards back might trigger it. I shouldn't have worried, the cards were still shown in my google account and adding them back was more-or-less seamless. No idea what happened though, why they disappeared.
[Magisk] 4sz0m:
Spitballing here, but you could give a try to Kitsune Magisk with Zygisk and Enforced SuList. Plus your current PIF module. And nothing else root/PI-related installed to keep it clean.
[Magisk] :
Ok, I'll give it a go. There are a number of different combos of versions of Magisk with or without Shamiko. I guess only trial and error finds out for real.
[Magisk] Matthew3955:
Can i use custom pif with play integrity FIX module?
[Magisk] CZ.Kostra:
With Play Integrity Fix (latest version) by @chiteroman you can use a custom fingerprint.

With Play Integrity Fork (all versions) by @osm0sis you have to use a custom fingerprint.
[Magisk] trevtdogg:
@Slim2none4u why are you angry reacting to so many comments???
[Magisk] simplepinoi177:
lol I was wondering the same thing and was considering asking (in pm).... 😅
[Magisk] mike.s:
Maybe that's just his RBF.
[Magisk] arkzok:
Is it okay if I grab a build.prop from RMX3562_domestic_11_A.32_220525, and use it to install the fix on my current RMX3563_13.1.0.800(EX01)? Or does it have to be from my current firmware version? (My device: Realme GT Neo 3 150W, there aren't full ROMs for every firmware version)
[Magisk] trevtdogg:
it doesn't matter which build prop you use, as long as it passes device integrity.

you might have to try many different build props until you find one that works.

it does not need to be from a similar rom to what your device is using at all.
[Magisk] zgfg:
Nobody would tell you here, yes, with that and that FP you will avoid hardware based TEE attesting and instead the prints will force and pass softtware based Device Integrity

That would mean publicly disclosing that the particular FP is generally good (not only for you with that Realme phone but also for others with different devices, even from other vendors) to pass Device Integrity - but there was a consensus not to name/list those prints here
[Magisk] arkzok:
I already know why they don't want to list some FPs here, so that they don't get banned by Google. But didn't really understand any of the other stuff you said😅
[Magisk] zgfg:
Then read again - and the explanation I just added/edited above

Ie, if that particulat FP A or B you are naming and asking above would be good for you to pass Device Integrity on your Realme, then those same FP A or B shall be also good for me on my Xiaomi and the others here with Pixel, Samsung, Motorola or whatever

It doesn't matter that we have different phones - it just matters if A = RMX3562_domestic_11_A.32_220525 and/or B =

RMX3563_13.1.0.800(EX01) are generally good or not
[Magisk] arkzok:
I'm using this guide for installing PIF, but in the PixelFlasher PIF Manager, there's no Update pif.json button, and when I paste the text from Output to Active Pif, the Create pif.json button grays out. If I don't paste, the console just gives the ERROR: Not a valid json. What should I do? And btw, is there anything supposed to be here?

Spoiler content hidden.
[Magisk] majorfigjam:
Look or ask here ...

📳🔥 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