yashsingh1/xdaforums huggingface dataset:
[Magisk] fragtion:
Just a quick update on my struggles passing safetynet with microG and PIF. I was using flashable zip from MinMicroG which contained outdated microG APK's. As soon as I installed the latest official microG apk's (com.android.vending-83752400.apk & com.google.android.gms-233515000.apk), my problems with microG Services Core crashing, went away, and I am passing all tests with SafetyNet! :D So PIF v15.1 confirmed working with microG, at least on my device

thx to all who offered suggestions and I hope this helps someone else facing the same problem :D
[Magisk] yeswap:
A web search for "brand and oreo and 8.0" will turn up articles like "These are the brand devices that will get Oreo". Anything updated to Oreo is a good canidate for PIF testing.
[Magisk] Vision:
I download just now the latest PixelFlasher, and Google block it because detect virus :ROFLMAO:
[Magisk] majorfigjam:
I'm sure devices released with oreo work, so don't stress on finding nougat ones that updated.

It seems though that you want to fully understand the process, finding roms without taking shortcuts to build prop files. So, to get an understanding of the brand / device history, xda is probably your best bet. Look for the individual device forum and threads on stock roms. Who knows, there may even be stock roms to download and play with, although many links are now broken.

My recommendation is to find a brand where you have device options and regional variations of rom, get any special software you need to work with it, and then pull the build prop files out.
[Magisk] BunnyPig1:
Read the main thread on why this happens. Nothing to worry about, it's expected because of how it works.
[Magisk] Umgak:
Discussed in this thread and the PixelFlasher thread several times, PyInstaller is sometimes used by malware and so some over-active antimalware programs decide to block all PyInstaller exes instead of actually trying to filter malware from innocent use of a legitimate tool.
[Magisk] Vision:
Yeah i read, but first time Google block it after scan it, and if not scan and download after deleted from Windows Defender :ROFLMAO:
[Magisk] diesteldorf:
I apologize if this was previously discussed/answered, but I've been reading every page from 180-203 in preparation of grabbing a custom print.

However, I am currently using a PIXEL 8 PRO ROOTED with stock firmware, MAGISK DELTA 26.4 ZYGISK

with the following MODS:

1) MAGISK HIDE PROPS CONFIG 6.1.2-V137 by Digeridoohan

2) Shamiko v 0.7.5

3) Zygisk - LSPosed

4) Play Integrity Next 14.1 by Chiteroman forked by daboynb

Prior to using Play Integrity Next, I was using Play Integrity 15.0 by Chiteroman

As of right now, my device passes BASIC and DEVICE integrity. STRONG INTEGRITY fails, obviously because my bootloader is unlocked.

BANKING APPS AND ANDROID PAY WORK FINE since I went to Play Integrity Next 14.1

Eventually, I am guessing PLAY INTEGRITY NEXT 14.1 will also fail. Is that when I'll need to modify /data/adb/pif.json file and find a custom print?

Everyone has their own reasons to root. I root primarily for SWIFT (and Titanium Backup) backup and am a bit of a hoarder of apps, probably have over 600 because I just keep transferring existing apps from one phone to another...LOL.

I also utilize CALL RECORDING.

I know CUSTOM FINGER PRINTS are really important for those that run CUSTOM ROMS, but I always stick to the stock Nexus and now Pixel experience.

For people like me that run STOCK FIRMWARE, will CUSTOM FINGERPRINTS still be needed?

I probably need to do some more reading too, but is there an existing post that explains how PLAY INTEGRITY NEXT 14.1 is functioning that allows DEVICE AND BASIC integrity to pass where prior versions of PLAY INTEGRITY failed?

Finally, thanks to chiteroman, dabonyb, and everyone else for sharing your knowledge and expertise.
[Magisk] simplepinoi177:
Play Integrity Next fingerprint will fail, but will update in-module to the new one (taken from xiaomi.eu ROM) -- which is a deficiency that PIF (the subject of this thread) didn't have; if it needed to update the fingerprint, a whole new version had to be released with it embedded in the module.

So while you should be on top of updating PINext, it's not in the same manner of keeping PIF where it's so vital to apply the working fingerprint. I've never used PINext, but as I roughly understand it, when you fail MEETS_DEVICE_INTEGRITY, you restart gms/Play Services, and it downloads the new, working print....?
[Magisk] Umgak:
Yes. If you use your stock fingerprint, Play Integrity will require hardware-backed key attestation, which cannot be spoofed, and you will fail. By using a fingerprint from a device which does not support hardware-backed key attestation, you are able to fallback to the significantly less secure software-backed key attestation, which is easily broken.

Play Integrity NEXT uses the fingerprint currently in use by the Xiaomi.eu ROM project. This is also what older versions of Play Integrity Fix used, difference being that all of the ones used by Play Integrity Fix got banned and chiteroman stopped updating the fingerprint, opting for users to find their own. NEXT didn't, instead automating the dumping of Xiaomi.eu's fingerprints for less maintenance required.
[Magisk] simplepinoi177:
it's curious & fascinating how quieted down this thread (and TG channel) has gotten since chiteroman embedded a working print that previously got burned (temporarily, so it seems).....

Then, as we all expect, within a couple of days, it will be burned and BAM! this thread will start blowing up 5 pages overnight type of pace (so many, "why isn't it working?!" "help please!" "I didn't read anything, but I want to know why this isn't working!"....

Better enjoy the relative peace/slowness now, gents!
[Magisk] majorfigjam:
Yes, if we override the download warning, Windows Defender (Win 11) blocks the latest version, and that did not happen with the previous version.
[Magisk] Vision:
Yeah exactly, i disable temporarily the Windows Defender, download again to make it work
[Magisk] majorfigjam:
But one thing I just found, as I needed to try the "extract pif from legacy device" option, is that if I save the .exe file direct from Linux into the Windows instance Program Files, then Windows Defender doesn't alert to anything on boot, or even if I then run the program in Windows.
[Magisk] HippoMan:
I especially enjoy posts like this:

Doesn't work. Please fix!

🤣
[Magisk] Vision:
That useful to we know it
[Magisk] Dragon Kumera:
yup I understood all of that but where is this termux thing everyone is mentioning? Google play store terminal? Or can we use windows?
[Magisk] thf1973:
Let me Google that for you:

Termux

The main termux site and help pages.

termux.dev

Termux - Apps on Google Play

Terminal emulator and Linux environment.

play.google.com

You are most welcome :rolleyes:
[Magisk] Nergal di Cuthah:
Defender's threat file may have been updated in between. It didn't trigger at all for me except the usual edge procedure of "this hasn't been downloaded alot are you sure you want it" >click keep anyway>click down arrow and keep.
[Magisk] Dragon Kumera:
by any chance could I get the finger print from my pixel xl gen 1 phone? (its running lineage os 20 android 13 atm).

Would I need to go back to stock? I cannot lock the boot loader due to it being a verizon model and well got lucky in getting it unlocked before that was patched.
[Magisk] Dragon Kumera:
i just needed a picture to make sure I was getting the legit version lol. Thx though.

edit. Rip. Not compatible with any of my devices but my amazon tablet. Pixel 8 pro wont let me install it from the website link.

I decided to download f droid version apk. Going to sideload and see if it works..

edit again. Yup that version worked. its more up to date to.
[Magisk] Nergal di Cuthah:
If there's no 64bit in termux you won't be able to use it on pixel 8 which did away with 32bit processing
[Magisk] Dragon Kumera:
I got it working. re read my post I updated.
[Magisk] Nergal di Cuthah:
Must've been editing while i typed. Just to put the last nail in my coffin i found this
[Magisk] Dragon Kumera:
huh interesting.

Side note my apk extractor app vanished from google play. Luckily had the latest version on my tablet so I just backed it up and sideloaded it back on my phone.
[Magisk] osm0sis:
Log looks good to me. Not sure what to tell you. Any difference with PIF 14.9 or 14.0 instead?

Ahhh, yeah wget on my device comes from busybox. Install my busybox module to get it working quickly, and I'll add a check to use Magisk's built-in busybox wget later tonight when I get the chance. 👍

Not sure why asking me, but no need to mess with your other phone, go look up a Pixel XL build.prop or search a fingerprint from one and you'll find working ones from that device.
[Magisk] V0latyle:
It's because there's no certificate for the file, so authenticity can't be determined - beyond checking hash against that published on the releases page.

I don't have Chrome's file protection turned on but I do use NordVPN Threat Protection, and it's annoying that it's not possible to add exceptions for false positives.
[Magisk] Vision:
Yeah, i disable temporarily the Windows Defender, when download i click in google take it anyway, to make it work
[Magisk] wfred:
@osm0sis I switched to v5 last night and completely failed integrity.

my original json, which has worked since the beginning, was

"FINGERPRINT":

"All of the print info:user/release-keys",

the script thought" FINGERPRINT": was blank since the info was on a different line.

Changed it to

"FINGERPRINT":"All of the print info:user/release-keys",

Reran migration, everything populated and it worked fine
[Magisk] Lord Sithek:
Yea, for me too... It's the ulimate mystery lol 🙃 Havent tried with these versions but I'll do
[Magisk] badabing2003:
But that will get the LOS print, I think @Dragon Kumera is asking for stock.

If that is the case, get it from a dump.

Otherwise if you want a print from a device that you possess, just connect to PixelFlasher and select

Device (menu) | Get pif print.
[Magisk] Vision:
Oh yeah, sorry i got confused, you have right, need the stock
[Magisk] Nergal di Cuthah:
Switched from? V4? 14.x? PIFNEXT?

If anything but v4 you probably need to move/rename the custom to be what v5 requires. Pixel Flasher (which despite its name works on any fastboot device) can reformat it for you
[Magisk] wfred:
From v4 to v5 of the osm0sis fork.

The module contains migrate.sh which uses your current v4 custom.pif.json to automatically populate additional fields in the new v5 json.

In my case migrate thought the FINGERPRINT field was empty so failed to populate the new v5 file
[Magisk] trevtdogg:
hmmmm that is strange. I'm not at a level to help with your situation, hopefully someone else reading might know why the service integrity stops working so quickly each time.
[Magisk] FrogMaster-:
It sounds like you may be hooking something into Google Play Services, which will cause all checks including basic to fail once the code is hooked into the service.

Do you have Google Play Services checked in any Magisk Module?

Do you have any LSPosed modules? Are any of them enabled on Google Play Services?
[Magisk] Kopasz999:
The 15.1 is the last update ?????
[Magisk] osm0sis:
Hmm yeah, that'll have to be a known caveat (i.e. make sure you're following normal json format with a single entry of quoted key and value per line), because I'm not out here trying to code a full json parser into a shell script. 😅😛
[Magisk] osm0sis:
You must have some other module running something at boot completed messing it up?
[Magisk] Kopasz999:
@osm0sis what??? 🤣
[Magisk] osm0sis:
Literally nothing indicates that. 🙄😉
[Magisk] osm0sis:
Fixed the wget issue!

🔧 [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] mike.s:
Depends on whether "last" means "latest" or "final."
[Magisk] Kopasz999:
@mike.s Final🙃
[Magisk] simplepinoi177:
FYI ALL THOSE WHO INTEND TO HELP HERE​

I've seen many helpful experienced members help new members and those seeking assistance refer to looking at the "most liked post on the right"....

but i've now observed that due to XDA's site indexing/policies, @osm0sis' most influential and quintessential post is no longer there (unless "All time" is clicked on)...

Should be kept in mind if/when advising members to that post....
[Magisk] majorfigjam:
As Osm0sis noted, literally nothing indicates that this is the case.

Chiteroman has said he won't supply a default fingerprint again, but then he said that at least once before. He may well provide further updates, with or without fingerprints, only he knows

Seriously though, find your own fingerprint, and step off the treadmill. Some of us did that when Chiteroman and Osm0sis first gave the option, a month ago now, and our prints are still going strong.
[Magisk] majorfigjam:
So it's a month then since that post.

Thanks Osm0sis on behalf of all of us who bothered to read, learn and sleep soundly with our own prints.
[Magisk] Dragon Kumera:
So that is why I have no idea where this most liked post is lol. thx! Just fixed that.
[Magisk] Kopasz999:
Thank you for your normal answer🙏 @majorfigjam

Yeah I want to do own fingerprint but i still dont know how🤣
[Magisk] Nergal di Cuthah:
How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)

It seems Google has banned more than 95% of custom fingerprints, so this thread/guide has kind been laid to the wayside. But it's still a great resource to understanding the foundations of fingerprints and all that... This is for any/all utterly...

xdaforums.com
[Magisk] Dragon Kumera:
im still trying to learn lol. But at least I have a safety net for the moment
[Magisk] WhoIsJohnGalt1979:
@osm0sis Never quite understood why it always felt so cool to use your Play Integrity Fork since v3 lol . After using v3 for almost 2 months I transitioned to v5 a few min back. Always been a sucker for step by step instructions (its more for me to remember).

1. Fingerprint I have been using for 3 months now has a build.prop only. Hence PIF folder in Downloads folder of my phone already has the build.prop and an empty vendor-build.prop file.

2. Transferred the updated gen_pif_custom.sh file to the same folder (thank you for updating it)

3. Ran the script using Fx explorer. I kid you not, every time i use this script I watch the green interface on the screen with the utmost excitement while the custom.pif.json is generated (I almost feel like Neo doing something really important)

4. Renamed example.pif.json to custom.pif.json and edited its contents within the zip. Flash (in airplane mode). Delete data and cache of playstore, wallet and playservices. Reboot.

5. Capital :p
[Magisk] Kopasz999:
Its complicated🤣
[Magisk] simplepinoi177:
I think the complication from my guide is because I attempted to explain it in a non-Android-technical fashion -- me and my way of speaking (Wall of Texts) is most likely intimidating....I'm hoping if one gets passed that, they'll find it's fairly straightforward (that's why I put it in sections and spoilers; to easily reference and digest)....🙏
[Magisk] tom1807:
Ok, I really don't understand why people struggling with Fingerprints.

Thanks to @badabing2003 and his PixelFlasher and with a test from @TheFreeman193 I got a FP from a Google device which meets Device Integrity.

Encouraged by that, I downloaded 2 more images from Google and they all pass Device Integrity.

Downloading and get the build.prop took longer than testing the build.prop and passing.

Edit: Update, just for fun, tested a few more and now I have 6 Google Devices passing Device Integrity.

Won't use it though (for now), because my initial FP is still working.

Cheers

Tom and a Happy New Year
[Magisk] Umgak:
Made it harder on yourself there, in my opinion. Much easier to just flash and then copy the custom.pif.json over to /data/adb/modules/playintegrityfix - or even let the update script handle it for you (it backs up your old PIF json before flashing, and then restores it after - and v5 runs migrate.sh on it too!).
[Magisk] WhoIsJohnGalt1979:
I was so tempted to do that right until the last minute before flashing, but I was too chicken to attempt it lol. Ah well, I most certainly would be braver while updating the next time. Thank you for noticing.
[Magisk] pndwal:
Nb. Android 14 issue for QPR2+ should now be fixed (2 weeks ago)! 🙂

Fix for Android 14 QPR2 B2 changes was merged in Magisk 26403...

Please confirm if this fix for regression (apparently began sometime after 26001 since reverting to 26.0 fixed issues on some devices) affecting Android 14 solves issues for you... I mentioned details here:

Seems this should fix issues in with late beta A14 firmware, but fix for "new method signatures and arguments" may help/be needed for other (stable etc) A14 builds by now also... 👍 PW
[Magisk] pndwal:
Yes, I check before modding too...

Can I assume you mean only China region phones fail STRONG_INTEGTITY?... And that you check before even unlocking bootloader? Because (of course) all stock devices will fail even DEVICE_INTEGRITY as soon as unlocked...

However Xiaomi (incl. Redmi) devices (for example) should all pass STRONG_INTEGTITY out of the box unless China region, but I believe even China region models (at least some) often have the core Play Services (GMS) framework needed (I don't know how that's licensed) to support added Google apps although the GMS App Suite itself (proprietary user apps) is not loaded in system (or licensed?)...

🤠 PW
[Magisk] pndwal:
Yes... Since Google began using adding fingerprint to the prop set they use (via DroidGuard) to identify devices they've slated for server end HARDWARE_BACKED evaluationType enforcement for verdicts, we need mismatched (ie. not expected) props for bypassing this enforcement, but fingerprint must (of course) also be legitimate (ie. CTS/VTS compliant)... That's why since 2.4.0 and earlier (in @Displax modded builds) USNF has been a complete fix even for custom/China region/beta etc ROMs... PIF forks are no exception; one stone kills two birds as mismatched bit valid print spoofing is now needed regardless of whether ROM is stock or not...

Please see posts on how hardware-backed verdict enforcement and bypassing this is achieved (basics of how USNF and forks (inc. PIF) work) and more under 'a bit of history' I linked at end of this post:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89240356

👀 PW
[Magisk] pndwal:
Yes, there's no real point AFAICS, but FWIW & IINM, official LineageOS always builds with current stock fingerprint and won't manipulate other props either due to policy, so it'll match stock... (That's why from March 2018 ctsProfileMatch failed w/o spoofing since Google required date matched Security patch level prop value and LOS team weren't prepared to fudge (spoof) that; MHPC simply properly matched Fingerprint and Security patch level prop values for selected prints.)

... Unless @Dragon Kumera is using unofficial LOS... Then Devs may be using any print/security patch date and all bets are off... 😁 PW
[Magisk] dmenezes:
Another, fainter hope is that someone finds a way to consistently break into TEEs and get their keys.

The TEEs that can be broken now are the ones badly implemented, but if a way is found to break into *any* TEEs, then it's Google and its useless PI games that are screwed and we modders are saved.
[Magisk] Lord Sithek:
FYI, I've tried 14.9 and 14.0 - same result. I've tried resetprop version and without. I've tried official Magisk, Alpha and Kitsune. I've even tried PlayIntegrityNEXT (desperate, I know). Nothing gives me DEVICE integrity. The only explanation I can see is that Arrow team changed something in the source...
[Magisk] intel_core_i7:
All Xiaomi devices from China in recent years equipped with GMS pass STRONG out of box (locked bootloader). The GMS part is still licensed by Google, hence passing strong and the blue android robot logo at the splash screen, but at a lower price probably since it only has the most basic services (probably at microg level or even more stripped out)

play store is available and apps requiring google services will run, but no android auto, google cloud messaging - or whatever they use for push notifications works very poorly and delayed notifications for hours as a result, google wallet/pay is a hit or miss (some said it works but I never got it worked before I sold mine), etc.
[Magisk] sawdoctor:
If you have a custom fingerprint and everything is working fine why do people feel the need to update? I appreciate everything chiteroman has/is doing for the community but osmoSis methodology is better
[Magisk] sawdoctor:
Unfortunately the issue seems to be with shadow hook not magisk. Even on latest magisk canary pif versions built with shadow hook won't pass device but versions built with Dobby work
[Magisk] MartinShoob:
I am not sure about the first question, but I do have lsposed modules (disable flag secure and messengerex), they are not enabled on Google play services. I tried disabling them to no avail.
[Magisk] osm0sis:
As the new PIF releases continue to roll out every 1-3 days with large rewrites of the same code every time I have started to just think of chiteroman's as the "experimental branch" and my Fork as the "stable branch"... 🤷‍♂️😛
[Magisk] pndwal:
Ah, I knew they often had basic services... Thanks for confirming... Suspect there may be many issues if apps must all be user added, not optimised as system apps anyway... Maybe they run better as GApps + custom ROM?

Anyway, I suspect @livinx's statement:

may be flawed... if taken literally the statement

may still mean phone was unlocked before testing, and your experience adds to my suspicions that this is probably the case...

Certainly, if any are actually failing STRONG_INTEGRITY out of the box they should only be China region variants, not Global, India etc.

Some details on Xiaomi MIUI ROM variants FWIW:

Currently MIUI is apparently released in two software variants, China (pure stable MIUI) with China-specific Assistants, social media apps etc and no Play Store, and Global (inherently unstable due to many more Google apps added) with many 'software' set sub regions... It also has 3 hardware set region variants (a physical resistor enforces these three regions), China, Global and India... Where India ROM previously, included Google apps as in Global ROM, this changed after the Indian government penalized Google. Google changed the requirement for Google Phone & Messages app availability in India, and although manufacturers including Xiaomi can optionally embed these applications, Xiaomi added the (China) MIUI Dialer & Messaging application to MIUI India ROM... Also, supplied Launchers may vary and MIUI India ROM will disable NFC if installed on an NFC-supported device. The main Global ROM is MIUI Global (MI), and aside from hardware enforced India sub-Global region Global (IN), the software set sub-Global regions include MIUI EEA Global (EU), MIUI Russia Global (RU), MIUI Turkey Global (TR), MIUI Indonesia Global (ID), MIUI Taiwan Global (TW), MIUI Japan Global (JP) and other MIUI Regions (LM, KR, CL) where devices are specific to operators and include operator-specific applications.

🤠 PW
[Magisk] intel_core_i7:
Yes, if you don't mind about notifications and background stuff, MIUI is very agressive towards apps not optimized for Chinese market

These days only devices on the lowest end of their offerings in mainland china do not come with gms
[Magisk] pndwal:
I meant custom as in non MIUI or debloated MIUI, and maybe more stable for features you experienced difficulty with. 🙃

But I believe none come with Play Store and many Google apps even if ship with Play Services/Framework no?... Doesn't Play Store need to be side loaded in China region MIUI any more? PW