yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
The issue has been discussed here and in USNF and other Magisk threads for yonks...

ctsProfileMatch w/ BASIC only evaluationType and the PI MEETS_DEVICE_INTEGRITY equivalent is designed to be available on devices launched with Android 7 and earlier (pre Keymaster 3) and is also available on devices with broken OEM Keymaster/hardware attestation implementations (since failure to register the keystore causes an exception that triggers a fallback to BASIC-only attestation on device/by DroidGuard and Google doesn't enforce HARDWARE_BACKED evaluationType server side for these devices) like so many relatively modern OnePlus devices and more.

MEETS_STRONG_INTEGRITY is essentially the same verdict but with no provision for BASIC-only evaluationTypes, ie. use of HARDWARE_BACKED attestations are always enforced, meaning that bank customers and app users will any device launched with pre Android 8 OS (even if running Upside Down Cake!) or even with modern (2SI boot type) OnePlus devices (I believe they only fixed their Keymaster implementations with Android 11 IIRC) immediately become collateral damage upon migration to MEETS_STRONG_INTEGRITY requirement.

I've also noted that values for KeyDescriptions are available in key pair extension data that would allow Google to enforce HARDWARE_BACKED evaluationType on the basis of hardware backed attestations to keymasterVersion / keyMintVersion as well as AuthorizationList field values like attestationIdDevice, attestationIdModel etc rather than the user-space based props and fields that have allowed this community to spoof CTS/VTS compliant (certified) devices for SafetyNet, Play Integrity and Play Protect purposes however...

https://developer.android.com/privacy-and-security/security-key-attestation

My conclusion (unchanged for half a decade at least) is that Google has favoured modders over banks in their efforts provide a 'meaningful' attestation to deviceIntegrity... In making MEETS_DEVICE_INTEGRITY the default PI label and leaving banks to decide when to implement the 'optional' MEETS_STRONG_INTEGRITY verdict, Google has supplied the meaningful attestation banks want... BUT (BIG But) it's still (at least till a critical mass of customers in lower socioeconomic regions have Keymaster 3+ compliant devices) a white elephant for them and a gift horse for moders.

Even with the latest DroidGuard / server side changes, MEETS_DEVICE_INTEGRITY remains attainable for modders despite no good technical reason for the necessity... I continue to wonder about the possible motivation (because I'm sure it's not a simple oversight), but I say Thanks Google (for the years-long reprieve afforded simply by the way you designed this thing)! 👍👍 🙂

Of course when banks finally flip the MEETS_STRONG_INTEGRITY switch, the lights will surely go out here... Have fun while it lasts folks, but don't think you'll be able to hold your breath forever! 🙃

Yup, those and more... But I doubt Google is about to flip that switch themselves. 🤠 PW
[Magisk] aygul12345:
I'm going to start over. Fresh install / flash over the last hyperOS.

Xiaomi 13 pro
[Magisk] GabbyWC:
Yeah, it's better than being stuck with a phone that won't load an operating system. You'll need to download and flash the correct ROM for your device (nuwa) and use the same computer which is authorized to run fastboot commands on that phone.
[Magisk] beeshyams:
yes, it does, that's the beauty of a very well designed program . Thanks to the developer @badabing2003

Sorry, I meant to reply to @arkzok 's question
[Magisk] aygul12345:
I was already on hyperos 1.0.4. Version after updating the fix module in magisk the phone couldn't boot into to the rom.
[Magisk] PandarianFury:
Alright so please be patient with me, I am technical but it seems like everyone on this forum knows this stuff better than I do.

Previously I found a fingerprint for an LG V7 and that worked. Now it's not working anymore.

I have installed v7 of the Osmosis fork, but I still fail device integrity.

Could someone please assist with the steps I am missing. I installed termux and ran autopif.sh as a root, but still not working. There's definitely 'obvious' things that I am missing.
[Magisk] GabbyWC:
Just keep in mind that my instructions are for flashing a Xiaomi.eu custom ROM and not an official factory ROM.
[Magisk] stanley321:
Do we have a new or updated guidelines for finding new FP?

Or it is still the same with the ones osm0sis posted on Nov 30 2023?

🔧 [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

All FPs in my pool are not working. I have to resort to autopif.sh for now, but I don't like using a public FP. However I have no glue of what FP to use.
[Magisk] GabbyWC:
Did you copy the resulting custom.pif.json file over to the /data/adb/modules/playintegrityfix folder and then do an integrity check?
[Magisk] mates21:
Has anyone managed to find their own fingerprint after most fingerprints were banned yesterday?
[Magisk] aygul12345:
I was using official Xiaomi Rom not the . Eu rom.

It was working before after updating the module it couldn't boot into the rom, it's not a ROM problem.
[Magisk] carlese:
I tried putting autopif.sh in my Rom folder, then after su command I type this:

sh /storage/emulated/0/sdcard/Rom/autopif.sh

But it says no such files or directory..
[Magisk] GabbyWC:
The Xiaomi Flash Tool is used for flashing official ROMs through fastboot mode but be careful not to lock the bootloader if you plan to root your device again. By the way, chiteroman's PIF v15.9.2 was just released and the changelog says "Fix bootloop issue on few devices." Yours must have been one of them.
[Magisk] pershoot:
adb push autopif.sh /sdcard/Download

adb shell

su

cd /data/local/tmp

mkdir autopif

mv /sdcard/Download/autopif.sh ./autopif && chown root:root ./autopif/autopif.sh && chmod u+x ./autopif/autopif.sh

cd autopif && sh autopif.sh
[Magisk] HippoMan:
The lights would go out for "banking apps", but that would only affect those who use those apps in the first place.

The more deleterious effects on us modders would occur when non-"banking" app developers start jumping onto the STRONG-integrity bandwagon ... and also if the Telephone Sanitizers ever decide to require STRONG integrity for the use of RCS and perhaps other Googlefrinchian-supplied services.

But even without any kind of increase in STRONG-integrity restrictions, the actual mechanisms of performing rooting and other modding have already "evolved" (ha ha!) into complex, error prone, and painful burdens.

For example, one of the "helpful" (ha ha ha!) "improvements" (ha ha ha ha!) that the Googlefrinchians have bestowed upon us is the redesign of recent Android versions which ends up causing it to be much more difficult for nandroid backup/restore software to be written. Without nandroid, bootloops and other booting problems are now much more difficult and painful to correct after rooting errors and other mishaps.

IMO, the only reason to thank the Googlefrinchians is because these "gifts" of theirs are less onerous than something much worse, such as having lots more STRONG integrity forced upon us.

And I want to make clear what I've explained in the past: I don't believe that the Googlefrinchians are out to get us modders. I believe that they barely take us into consideration at all, neither positively nor negatively.

These unpleasant features that I'm describing are merely side-effects of corporate policies and goals that have been implemented without much thought being given about the modding community itself. Our woes are just unintentional collateral damage.
[Magisk] :
If you're loosing your data anyway, you can try a wipe/factory reset from recovery first.
[Magisk] GabbyWC:
I could be wrong but I don't think that will wipe his root partition which is where the problematic module version is. Perhaps he can let us know whether your suggestion worked or not.
[Magisk] ipilcher:
grep: Unknown option 'P' (see "grep --help")
curl: (23) Failure writing output to destination
curl: (3) URL using bad/illegal format or missing URL
./autopif.sh[41]: apktool: inaccessible or not found
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
grep: /data/local/tmp/tmp.LcPqvlLDM3/Extractedapk/res/xml/inject_fields.xml: No such file or directory
{
"PRODUCT": "null",
"DEVICE": "null",
"MANUFACTURER": "null",
"BRAND": "null",
"MODEL": "null",
"FINGERPRINT": "null",
"SECURITY_PATCH": "null",
"FIRST_API_LEVEL": "null"
}

Any ideas?
[Magisk] carlese:
Worked and downloaded something but it still meets only basic integrity..
[Magisk] kornball:
Did you move the custom.pif.json file to /data/adb/modules/playintegrityfix?
[Magisk] pershoot:
You have to copy it (pif.json / custom.pif.json) in to the appropriate place (within /data/adb) and then kill gms.unstable or reboot.
[Magisk] pershoot:
Make sure you grab the latest version. osm0sis added some changes to accommodate for failures.
[Magisk] PandarianFury:
I get a WGET error on the github for Apktool. (TLS Error from peer (alert code 80).

I suspect that there might be something blocking us, and as a result, we can't run autopif.sh

EDIT: I installed wget and which with "pkg install wget" and "pkg install which" and it worked
[Magisk] ScaryBugThing:
My TheFreeman193-random print got banned as of yesterday, and I've been searching for an hour (slowed via integrity-check throttling) for a new print. None are passing Device. I'm on the latest Chiteroman integrity fix, starting to think I should try 0smosis.

Edit: TheFreeman193 has updated the Github page as of yesterday, to say it appears most of his prints have been banned and to use the xiaomi print for now (PixelFlasher has this as an easy option). I'm sure that will get banned quickly given the influx of people using it, but FYI.

GitHub - TheFreeman193/PIFS: A collection of build properties for the PIF module

A collection of build properties for the PIF module - TheFreeman193/PIFS

github.com
[Magisk] GabbyWC:
@osm0sis What do you think about adding this or similar code to your next release? It would be nice to keep the directory clean after the script has done its work. I noticed, however, that the apktool_2.0.3-dexed.jar file is still left behind when the exact code shown above is used.
[Magisk] Vision:
I try again 10+ (50+ yesterday, 50+ in the morning) only basic and some not pass even basic.

For the love of God

I can't more, need rest
[Magisk] awarexda:
There is some bootloop fix in chitero's release, if we get a bootloop how we flash a zip? I don't think I have TWRP...
[Magisk] GabbyWC:
For now, at least, use the autopif.sh script from osm0sis to obtain the current public fingerprint and get some rest. You don't need to stress out over this.
[Magisk] Vision:
Thanks for info. i appreciate

Yeah you have right, my eye need rest
[Magisk] pershoot:
This one as well:

🔧 [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

@osm0sis @FrogMaster- @GabbyWC
[Magisk] luciorasta:
I use osmosis V7. In the past, when I had problems, I used TheFreeman193 pickaprint.

I'm sorry, I know there are dozens of guides on how to use the autopif.sh script, but I just can't figure out how to do it. Can anyone point me a link with foolproof instructions.
[Magisk] pershoot:
I just pasted instructions on this. Please scroll up.

<edit>

🔧 [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

🔧 [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] pythonimus:
This fingerprint even fails basic integrity for my Pixel 8 Pro, its even worse than a random freeman one...
[Magisk] aygul12345:
Still can't boot into the ROM of the phone module of chiteroman version v15.9.2. I flashed my phone Xiaomi 13 Pro stock everthing deleted.

Vv15.9.1 V15.9.1 works but .2 phone won't let me boot into the phone. It keeps rebooting at the screen logo Xiaomi HyperOS.

How to fix this?

Download the firmware Recovery OS/image and flash it over. Magisk/root will be lost. but the phone boots in to the ROM. Try different fork also no succes.

Hope there will be a fix to this.

Back on version: v15.9

Can't boot into the ROM - After module version v15.9 (15.9.1 & 15.9.2 - Broke) - Xiaomi 13 Pro · Issue #277 · chiteroman/PlayIntegrityFix

After updating the module to the version: V15.9.2. on my Xiaomi 13 Pro. Phone keeps crashing on the logo screen. V15.9.1 was no issue. Still can't boot into the ROM of the phone module of chiteroma...

github.com
[Magisk] GabbyWC:
1. Download and install FX File Explorer from Google Play.

2. Open FX File Explorer and accept the license agreement.

3. Allow its notifications if you're asked about that.

4. Use or skip the app's tutorial.

5. Uncheck the 7-day "FX Plus" trial option and select OK.

6. Press the "ENABLE ACCESS" button at the bottom and allow FX to have "All files access" in Android.

7. From the FX home screen, press "Upgrade" and navigate all the way to the right where the DEVELOPER/ROOT tab is.

8. Press the green "Enable" button and agree to the information shown about root access.

9. Download osm0sis' autopif.sh script.

10. Execute the autopif.sh script in FX with root access and wait for the script to do its work.

11. Copy the resulting pif.json file to (root)/data/adb/ if you're using chiteroman's Play Integrity Fix module or copy the custom.pif.json file to (root)/data/adb/modules/playintegrityfix if you're using osm0sis' Play Integrity Fork module.

12. Check the Play Integrity status with any capable app or from the Google Play app's developer options menu to see if the fingerprint passes basic and device integrity.
[Magisk] WhoIsJohnGalt1979:
1.5 Root will not work on FX File explorer unless you flash Busybox for Android NDK by osm0sis and change busybox path in settings to /system/bin/busybox. Root addon of FX explorer is no longer compatible with phones like Pixel 8
[Magisk] Iridule:
@osm0sis claims to have found a working print that isn't the one everyone is using. Would be nice to know where as I've tried about 100 prints all only pass basic or fail.
[Magisk] GabbyWC:
I didn't have to do any of that on my Redmi Note 9 Pro with PixelOS 14 but now that I've taken a closer look, there are more steps which I will add for enabling root in this app.
[Magisk] HippoMan:
As has been mentioned dozens, if not hundreds times in this thread over the past few months, publicly sharing working FP's makes them *much* more likely to be banana-ed soon for everyone by the Googlefrinchians.

Therefore, it's best that the location of that FP should unfortunately not be divulged.

Given the recent mass-invalidation of something like 95 percent of the formerly working FP's, it's indeed more time-consuming now to find a working FP. However, doing that repeated FP-searching as you have done is still what we need to do.
[Magisk] PandarianFury:
Same
[Magisk] droidman1992:
My unique print got banned yesterday in the presumed mass banning after 1.5 months. I tested thefreeman193 script and tried 100 prints with no success.

I may try the autopif.sh, however, it's clear that the end times are near and if you want up to date android and full functionality, you simply have to buy a new device (preferably with 7 year updates) and keep it stock.

I plan to buy another flagship and unfortunately stop using custom ROMs, however, nothing is good enough this year. The Samsung S24 Ultra is overpriced, has a grainy screen and only 12 GB of RAM, while the Pixel 8 Pro has a substandard SOC/modem and only 12 GB of RAM as well. The OnePlus 12 has great specs and value, however, only 4 Android updates is rather lame. I will have to keep my OnePlus 7 Pro on play integrity life support until next year.
[Magisk] Vision:
@GabbyWC I try it and pass 2/3. Thanks again for info

@osm0sis fork v7 (forever futureproof)

The strange is this PIF is public from Xiaomi.Eu, why Google not block it yet?

Google something test here with all of us
[Magisk] osm0sis:
Alrighty... Where to get started here...

First of all, don't rename it. Read on, this is important.

Second, you both are removing/changing something you clearly don't fully understand... That code is what allows it to work when run sourced from a file explorer app like FX or MiX...

If you stop to read the case you're hacking apart you'll see that in that scenario $0 is NOT *.sh, which is why the script then uses lsof to find itself and find its operating directory.

Why? It's designed to run from /sdcard/Download or anywhere on /sdcard you want, so there's no reason to mess around with permissions and stuff. My instructions are pretty clear about it all. For Termux, use a su prompt and go to /sdcard/Download and run it from there with sh autopif.sh.

My script intentionally doesn't use curl at all, so I'm not sure where you got that, but it's not mine. Maybe go download mine, read the instructions fully, and try again.

Why are you intentionally hacking out the root check? If you ran it in Termux with root from a su prompt like it tells you to then it would have Android's which command and access your root solution's busybox for wget.

No, I think it's completely unnecessary. I leave the files behind for a reason, and it's to not download them again unnecessarily or hammer the servers.

Look at the rest of this post and you can see what people hacking up my well thought-out script has gotten them. 🤨

If people want it contained, simply put it as /sdcard/Download/AutoPIF/autopif.sh or /sdcard/AutoPIF/autopif.sh or something and delete old ones only as new ones come along.

Just go to MY autopif.sh post, read the full post and all the edits.

Well, not FOREVER, just a lot more. 😜
[Magisk] HippoMan:
I have speculated elsewhere that maybe the Xiaomi people might have made an under-the-table arrangement with the Googlefrinchians to allow their FP's to have some sort of grace period before being banana-ed.

It's probably not very likely, but it's fun to speculate about that.
[Magisk] pershoot:
@osm0sis Up to you; just trying to help. I did not read the context only sorting an edge case (from humanness) which was presented adhoc. I usually write things to be as dynamic as best I can. I do not run things of this nature from the /sdcard nor let things go wild, if I can help it. Anything requiring root stays away in to its own sect. and is locked down.
[Magisk] miimaa:
Hi guys!

I'm on the same boat than everyone else. Good friend of mine was burned.

I was about to read Osmosis instructions from Github. I found his AutoPif Next -app. I downloaded it, granted super user rights and now I pass device and basic integritys.

I've been following these thread for few months and I have to say, I have no idea what that app does. And I really don't care because I wan't my Google Wallet to work.
[Magisk] osm0sis:
You can still run it from wherever you want as it already is, without hacking it up. 👍

I don't have an app, and you shouldn't trust any app that claims to be mine. Use my autopif.sh script from my post only.

🔧 [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] carlese:
When you say "go to download" what's the command? I am using juicessh and cd command doesn't seem to work, it says that the folder /storage/emulated/0/sdcard/Download doesn't exist..
[Magisk] osm0sis:
If you're not at a root prompt yet it might not have access to sdcard.

Type su

Then I usually do cd /sdcard

If you're not comfortable with shell commands this is also exactly why I wrote it to run from a file explorer app like FX or MiX.
[Magisk] Vision:
Grounded speculated, because read the first line 😂🤣

View attachment 6075307
[Magisk] BrimoFan123:
Just thinking... "9 of them never used before" - but you checked every single one of them the day you found them to see if they gave you a Basic and Device attestation, right?

Maybe this initial checking what we all did left some "fingerprint" at G database and it had been used to ban all of our own FPs at once?
[Magisk] carlese:
I typed su but still no luck with the command, really strange.. I'll try with termux
[Magisk] miimaa:
****, sorry! I was wading around Github and apparently I got lost in someone else's profile. Here's the app I'm referring to: https://github.com/x1337cn/AutoPIF-Next
[Magisk] aygul12345:
I can confirm now that the version v15.9 works for Xiaomi devices.

After v15.9 phone won't boot in to the ROM Xiaomi Official ROM.

Advise to stay at v15.9.
[Magisk] GabbyWC:
PIF v15.9.3 was released a minute ago.

"Fix bootloop issues x2"
[Magisk] osm0sis:
Yeah, very much not me. Accept no imitations. 😉
[Magisk] Vision:
@chiteroman @osm0sis @zgfg @pndwal

Forgive me, if i forget someone else

It's time for the big brains, to join force :cool:
[Magisk] osm0sis:
I already have always been working with 3 of those 4, and several more. 😉

(Edit: including myself there 😛)
[Magisk] Vision:
Good for the rest of us to know that.

Τhank you for your contribution and your hard work. We Appreciate that
[Magisk] aygul12345:
Testing 15.9.3 on the Xiaomi 13 pro.

EDIT: Phone booted in to the ROM. So 15.9.3 is working. While 15.9.2 & .1 is stuck at the bootloader/logo.
[Magisk] miho171:
Yeah, of course I tested all before collecting, but if Google banned for this simple reason then the last fp of 15.9.x should be burned days ago.
[Magisk] miimaa:
Understood.

Maybe you should check that app or profile because it worked for me? I deleted the app right away and I still pass the integrities.

And again, sorry for the confusion!
[Magisk] carlese:
@osm0sis so Termux worked just fine, I think it there was a problem with JuiceSSH, but I have 2 questions:

1) the script created a lot of filex in the Download folder, can I delete them?

2) after the script finished I rebooted but google play still passes BASIC only

3) out of curiosity, and I don't mean to sound rude at all, what are the advantages of autopif compared to manual running the scripts in the PIFS github page? Like I said the key found by autopif is not working for me, so I have to still run the script again just like I did in the past.. Am I missing something big here?

Thanks for you patience with us newbies :)
[Magisk] BrimoFan123:
Not necessarily... They might have burned (banned) all "fingerprints" collected in their DB since December (when majority of us started mining and testing FPs) and "new" FPs found last two-three days are not yet added to the batch of burning action.
[Magisk] GabbyWC:
It hasn't been banned yet so there must be another reason why it isn't working on your phone.

See my answer directly above.