yashsingh1/xdaforums huggingface dataset:
[Magisk] poulopoulosa:
I usually update my apps and phone to the latest version when available, I guess it is an OCD thing.

Im on:

Pixel 7pro

android 13

LOS version:20-20240213-NIGHTLY-cheetah

Magisk setup

Magisk Canary 27001

Osm0sis PIF fork (with Xiaomi script)

Shamiko v1.0.1

Zygisk - LSPosed v1.9.2

Zygisk - Next v4-0.9.2.1

Hide my app list (hiding all dodgy apps)

When my wallet refused to pay I just fetched a new FP thanks @osm0sis for the script (I wish I knew more programming languages other than JavaScript to understand them 😭). Cleared caches and waited for everything to re-update.

Remember wallet has to work everywhere you go, even in times without internet so your phone can supply the virtual card and token to the card machine. That is why the wallet (most likely Google play services) are caching your certified status. Of course you can force with data / cache wipes but if that is not the case just be patient and use a plastic card.

Magisk, my OS, and Zygisk next are asking to update. No thanks, im fine with what I have so far. I don't want to update magisk or my OS and risk tripping any bank apps. I want to remind sometimes its best to stay on old versions.
[Magisk] EmPiFree:
How do I run the "fp" script? I only found the PIF.apk, but nothing with "PlayCurl".

What I currently have:

- KernelSU v0.9.4

Modules:

- Zygisk Next 1.0.5

- Play Integrity Fix v15.9.8

Currently my Google Wallet works, but I am afraid when it doesn't work anymore and as far as I understood correctly I could run the "fp" command to make it work again.

What am I missing?
[Magisk] trevtdogg:
don't even bother replying to anyone who asks about "all green" or strong integrity, cause they clearly haven't even read the OP. it's clear as day in the OP that 2 green checks are all you should be striving for at the moment.

any other incredibly basic questions, just point them to the FAQ, which is also linked in the OP.

no matter how long a thread may be, at least reading the OP (especially when it's been updated in the last few months) should be the absolute minimum before asking any questions.
[Magisk] DarkestSpawn:
I believe it has been stated using Play Integrity Fix or Fork with Safetynet Sensitive Props conflicts with each other causing your issue. Try disabling Safetynet Sensitive Props and reboot. Then check with Play Integrity Checker for your results.
[Magisk] dlads:
Mine failed again today, ran through the same steps I posted before then added the same module.

Now working again.
[Magisk] pranciskus2:
After updating fix, it passes integrity check, but GPay says "Try that again" when I'm trying to pay. How to fix this? I tried clearing Wallet data, but it didn't work.
[Magisk] gerikobcn:
Hi everyone!

I'm on Xiaomi 15 on Hyperos Xiaomi eu rom latest stable with magisk and play integrity fix 15.9.8 meets device integrity sometimes and sometimes not, wallet start working after clear data and rebot but in a while it fails again...

Someone else happening hat?

Thanks at all!
[Magisk] CZ.Kostra:
There is a high probability that the PIF will collide with injector that is part of Xiaomi.EU ROMs. You need to disable injector and uninstall its updates.
[Magisk] szinyo1048:
guys, plese big help me. Use Samsung S24 ultra, DR Ketan rom U09 ( A14 )

i editing systemui.apk --> Change 4g Icon To LTE, than not boot my phone. How to signing the systemui than is edited, to work my phone? can u help me, instructions?

( Ketan rom have premium, include menu to change 4g insteate LTE, but no work.., i chaging only: edit the xml file in systemui,apk ) How to signing to no kill my phone? Please get me advice! Big Big Thank
[Magisk] Vision:
Out of topic.
[Magisk] szinyo1048:
ok, please show or link me topic to i get asking this, very very big thank.
[Magisk] Spartacus500:
PM 🙂
[Magisk] xSnowLeopardx:
Looks like clearing GWallet's data does not work, since it remembers my cards after wiping and rebooting. Weird.
[Magisk] fbirraque:
Since yesterday when checking the Play Integrity (BASIC and INTEGRITY) in the Developer Options at Google Play Store an error message happens always:

Error: -17: Integrity APl error (-17): There is a

transient error on the calling device.

Retry with an exponential backoff.

(https://developer.android.com/googl...ntegrityErrorCode.html#CLIENT_TRANSIENT_ERROR).

Then after clicking on the RETRY the expected Play Integrity Certification works and confirms that is certified.

Google Play Store: 41.0.28-31 [O] [PR]

633720010

Google Play Services: 4.20.13

(190400-633713831)

Play Integrity Fork CI #222

custom.pif.json (by autopif.sh)

Android 13, MIUI14.0.8.0 by XiaomiEU

Device: Poco F3 (alioth)

It was working flawlessly since the newer PIF last 15, may and Bank, Gov, Wallet (NFC Payments) apps still working even after this checking error message.

Anyone else with the same issue?

EDITED: The AdGuard 4.4 Nightly 47 seems to be the source of this issue

EDITED: When tested in another device with same AdGuard version installed, Android 10 and LOCKED bootloader none issue happened. So folks please check if when in the Developer Options (Google Play Store) same error message happens or not. (screenshot)
[Magisk] osm0sis:
It's just a frontend for Google Play Services, where all the Google Pay data is stored.

No issues on my Pixel 8 Pro when I checked in the Play Store just now.
[Magisk] JustinCretible:
Yes, I had the same issue. I think Google is throttling the number of API requests you can make within a certain period of time.

I tried again the next morning and it showed that it passed (two green check marks). You can also try the TB Checker app and see if that will let you run a Play Integrity Check without an error.
[Magisk] osm0sis:
Wait, are you saying of the 291 you had at the end of April that only 44 are left? 😵

That'd mean we've gone from ~5% of prior known working prints left after the Leap Day mass ban, down to ~0.75%. 😖
[Magisk] fbirraque:
I already edited the previous post.

Even none error (or blocks) in the AdGuard's log some filter update in their side seems to be the source of the error message. As I said everything still working flawlessly in apps and NFC so if none further issue happens it's nothing to be concerned.
[Magisk] xSnowLeopardx:
Ahh, got it. Forgot about clearing GPS. Cheers.
[Magisk] fbirraque:
Hi osm0sis

My previous post #15118 edited again:

EDITED: When tested in another device with same AdGuard version installed, Android 10 and LOCKED bootloader none issue happened. So folks please check if when in the Developer Options in the Google Play Store same error message happens or not.

I hope not but maybe the Google playing with things again.

Lets see if other users confirm same issue or not.
[Magisk] zgfg:
No, having now 290. Lost Griffin and two more, got Clark from Xiaomi.eu

Of them, only 44 are in the A9-A13 range, the rest fromA5 to A8. Majority A6-A8
[Magisk] pythonimus:
For me on Pixel8 Pro Wallet detects root now even though play store says I meet basic integrity. However yansac says CTS profile mismatch, how come? Does anyone else has this problem?
[Magisk] Nergal di Cuthah:
You need to meet basic AND Device to use wallet. Which PIF are you on, what kernel, what other modules and lsposed and its modules. Have you read the original post for this thread and the faq for PI?

YASNAC alone is not a viable test, you must use a PI detector (such as the one built into PLAYSTORE developer settings).

Redundant you say you used said checker
[Magisk] osm0sis:
Ah, phew. 😅

Check on the group PM by the way, there are more to test if you're interested. 😉
[Magisk] ScaryBugThing:
Apologies, I know the answer is probably somewhere here but after 10 pages back and not seeing it (and reading most of this thread at some point over the years):

I also lost DEVICE integrity a few days ago. I ran out of working custom prints (and after trying roughly 50 without success, gave up), so have been using the Xiaomi print, mainly for Google Wallet/Pay. However, I tried both PixelFlasher and Osmosis' autopif.sh script to get the new Xiaomi print (Clark, yes - tried both just to be sure it was being applied correctly), and verified that it is indeed in my Pixel 7 Pro's build.prop. But I am still only meeting BASIC and not DEVICE integrity on SPIC when I check. I'm on the latest Chiteroman Integrity Fix, 15.9.8.

Has anyone else had this issue with updating to the current (2024/05/18) Xiaomi print? Or is it just my device?

I am just seeing a lot of responses by people who either get DEVICE and are waiting for their attestation to clear, or have some other issue. But it seems like others have been getting DEVICE integrity pass with the Xiaomi print, so I suspect something's wrong with my setup.
[Magisk] majorfigjam:
You're description is confused - you talk about Osm0sis script but are using Chiteroman. They use differently named files in different locations. What do you mean by your build.prop - do you mean the json file appropriate to your module?

Which PIF are you on, what kernel, what other modules and lsposed and its modules do you have?
[Magisk] majorfigjam:
Given the amount of repeat questions, is it OK to remind everyone, including Mods, of Forum rules No 1 & 3:

XDA-Developers FORUM RULES

...

1. Search before posting.

Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.

...

3. Post using a clear and descriptive subject and message.

You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.

📚 XDA Developers Forum Rules 📚

XDA-Developers FORUM RULES List of Forum Moderators, click HERE Delete Your XDA Account HERE 1. Search before posting. Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new...

xdaforums.com
[Magisk] ScaryBugThing:
Sorry, my fault. Yes, I meant the .json file with the fingerprint details.

I am on Magisk 27.0, with Play Integrity Fix 15.9.8 by chiteroman, and Zygisk - LSPosed 1.9.2. I have a few other modules: Iconify (for hiding bottom nav. pill), Pixel Xpert, Systemless hosts, and BCR.

I used Pixel Flasher to directly download and apply the Xioami Clark print today. I verified Pixel Flasher applied it by reloading the print from my phone after writing, and it properly read the new Clark fingerprint. That passes BASIC but fails DEVICE integrity.

As a backup, I also used Osmosis' autopif.sh script, but I didn't realize it only works if you are running Osmosis's Play Integrity Fix. Either way, my DEVICE integrity failed both before and after running it.

(To be clear, I don't think this is a repeat question because others have verified in the last 10 pages that the Xiaomi Clark print works with DEVICE, and Pixel Flasher verifies the print was applied to my phone, so clearly I'm having some other issue. I know these massive threads suck both for those seeking and those giving answers. If it's answered, apologies, I'll fully admit I'm an idiot.)
[Magisk] majorfigjam:
What device? Have you uninstalled and reinstalled Chiteroman to get rid of any artefacts - such as a lingering pif.json? Have you tried disabling all the various modules to see if they conflict with the latest version of Play Integrity? Did you delete the caches and data of Play Services, Play Protect and Play Store?
[Magisk] Nergal di Cuthah:
AFAIK Fingerprint is embedded in latest chiteroman module. Remove the json, would be my suggestion.
[Magisk] ScaryBugThing:
Thank you, this is what I needed. It was an old custom pif.json that was superseding the Xiaomi print - presumably Chiteroman's PIF ignores the default print when the custom print files are present. The problem went away and DEVICE is now passing.

What I did for anyone else:

Root Explorer to /data/adb/modules/playintegrityfix/

Rename any *pif.json files to add ".old" extension

For good measure, do the same for any *pif.json files in /data/adb/ if any are present.

Uninstall Chiteroman PIF if present.

Reboot.

Reinstall fresh Chiteroman PIF. During this step it should NOT say it detects a custom print.

Reboot.

Run SPIC to check for DEVICE integrity.

Thanks for the help!
[Magisk] zgfg:
Yes, that's the point. Module uses built-in prints but if you have your own pif.json it thinks you put it intentionally (like your 'private' prints) and then uses them instead. It doesn't know is your pif.json good or not
[Magisk] HippoMan:
I have found that this "exponential backoff" error can occur occasionally in this case if lots of similar requests have been issued within a short time.

It doesn't occur nearly as frequently as 3rd-party integrity-checking apps get blocked due to lots of requests.

For me, I just have to wait maybe 30 seconds or so and then try again.
[Magisk] osm0sis:
To be clear, it's still written to work with both. 👍
[Magisk] HippoMan:
Thank you for this detailed "cookbook".

A good rule of thumb for everyone:

Whenever updating a JSON fingerprint file -- either for use with chiteroman's or osm0sis' utility -- first get rid of any and all *.json files in /data/adb and in /data/adb/modules/playintegrityfix, either by deleting them or by renaming them to no longer end with ".json".
[Magisk] Depressed T.Bear:
Autopif.sh never really worked for me, regardless if I use termux or any other terminal emulator.

It always fails with:-

:rolleyes:
[Magisk] ChocoboX:
Finally I got it to work on Pixel 7 Pro. This is how it worked for me:

I had pif.json before. So I deleted it via Total Commander. I also deleted the .old ones. Reboot. Tried it did not work. I deleted Play Integrity Fix and Reboot. I reinstalled Play Integrity Fix. It worked ! Thank you everyone for your help.
[Magisk] osm0sis:
Android version? Root?
[Magisk] Depressed T.Bear:
Android 11, rooted with Magisk 27 (27001) Kitsune canary.

However, in this case I suspected that my rom might be the culprit itself. I'm not an expert by any means, but as far as I know, Java code is executed by ART.

My rom is hardened, quote:

and

I might be mistaken and something other is going on... But it sounds to me like some hardening of ART messed it up for me?
[Magisk] fanticgamerw633:
hi im new to the integrity fix api. Autopif worked for me. I was wondering if we're looking into a long term solution to integrity fix for rooted device b/c I saw a lot of comments saying that we're just wasting fingerprints that meet device integrity..
[Magisk] osm0sis:
Hmmm could very well be.
[Magisk] majorfigjam:
I'm sure a number of developers are looking - eg Chiteroman's work on TEE and keyboxes, but you shouldn't expect to see much about that in this forum.

More to the point, if someone finds a way to spoof strong integrity, as opposed to device integrity, and then publicises the method, you can be absolutely sure that Google will close the loophole VERY quickly.
[Magisk] zzzeros:
Lost integrity, nothing I would do was working

Flashed the phone with wipe and the latest image

husky-ap1a.240505.005-factory-6fe67f4a

Only has unlocked bootloader, root not installed

Only passes basic integrity
[Magisk] Depressed T.Bear:
Either that or it's related to Kitsune Magisk.

I don't know how to find out, though.
[Magisk] pndwal:
Of course clark is Motorola (Moto X) print though... Just the current one XiaomiEU (custom ROM) Devs spoof with... PW
[Magisk] purgy:
Haven't followed this thread in a while, because I haven't needed to.

Til I forgot my analogue wallet when I went to get petrol this morning.

20 odd seconds in the corner with @osm0sis autopif script and good to go again :toot:
[Magisk] Nergal di Cuthah:
That is the correct state. Only way to pass device, with unlocked bootloader, is to root and use this module (or it's similar forks or nexts).
[Magisk] osm0sis:
What exact ROM zip and device? Does the zipsigner command work in my zip Magisk module? It's also a jar.

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc. General Information In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller...

xdaforums.com
[Magisk] zzzeros:
Ah so I have to lock bootloader to get device, thanks

EDIT: Installed Root and osm0sis with Xiaomi Pif, back in business
[Magisk] sga999:
Same for me on Android 11, Leeco Le Pro 3, AICP rom, standard Magisk, I.e. not Kitsune, osm0sis v8 fork I get the same error messages. But I never mentioned it because I pass basic and device integrity without using any custom.pif.json. But I do have to have the osm0sis module installed in Magisk for those to pass.
[Magisk] osm0sis:
Android 11 is the common denominator so far. Thanks for reporting, I'll see if I can reproduce it and figure something out. 👍
[Magisk] trevtdogg:
I'm on a11 stock (moto edge 20 fusion) with normal up to date magisk, lsposed, no shamiko, no deny list, no hma, using osmosis fork, autopif, working fine.
[Magisk] sga999:
Well, I also have Android 11, lineage 18.1 rom, Magisk, your v8 module, on another Leeco, and autopif.sh does not have a problem. As with the other Leeco, I do need your module in order to pass both, but I do not need to copy custom.pif.json to the appropriate folder.
[Magisk] sga999:
I don't know if this output from terminal emulator helps you more than what we already reported. But I saw some stuff about 'curl' earlier in this thread where you said that shouldn't be occurring as part of your script. Yet since it is showing here, I thought I would let you see it.
[Magisk] sga999:
I saw your Busybox updater in your Odds and Ends and installed it. That fixed it! I don't know enough to understand why it needed this on the Android 11 Leeco but not on others.
[Magisk] osm0sis:
Sounds like you might not be using my script then.

PlayIntegrityFork/module/autopif.sh at main · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

Not a curl in sight. Never was. 🤔

Edit: Do me a favor and uninstall my busybox, reboot, then do at a root prompt:

which -a wget; ls -al $(which wget); wget --help;

Sounds like your ROM might stupidly have wget linked to curl, so it's failing to download the jar correctly because the command line options are different.
[Magisk] sga999:
That --help error is strange. So I did another wget command with only one dash, just to see what it would do. Its result does mention curl. Not sure if this helps you.

:/ $ su

:/ # which -a wget; ls -al $(which wget); wget --help;

/system/xbin/wget

-rwxr-xr-x 1 root shell 5611 2008-12-31 16:00 /system/xbin/wget

/system/xbin/wget[160]: getopts: arguments changed since last call

:/ # wget -help

Usage: wget [wget args] [i need to fill this in later] <url(s)>

Download all URLs given using curl, but using wget's options.

:/ #
[Magisk] osm0sis:
Wow so definitely some kind of half-baked wget in your ROM currently. Not sure how to protect against that exactly in my script yet...

Did you install it using another Magisk module or did it come with your ROM? Does your ROM also have curl? Can you zip wget and curl up and upload them for me to test out?

Edit: The only reference I can find to that error on Google is this mention of "fake wget":

android_vendor_lineage

Forked from https://github.com/LineageOS/android_vendor_lineage

git.gugelfrei.de

Edit 2: Following the "wget-curl" "somasis" breadcrumbs in that link lead to a newer(?) version here: https://github.com/somasis/wget-curl/blob/master/wget

Both of those look like they should support the wget -O command your ROM was erroring out on however.. 🧐😕

-O
curl: (6) Could not resolve host: -O

apktool_2.0.3-dexed.jar
curl: (6) Could not resolve host: apktool_2.0.3-dexed.jar

https://github.com/osm0sis/APK-Patcher/raw/master/tools/apktool_2.0.3-dexed.jar
############################################################ 100.0%

Definitely send me your ROM's wget, I'll just detect these and not allow them to be used. 🤷‍♂️
[Magisk] zgfg:
It reminds me of a similar problem that I had with the built-in wget couple of years ago (I don't have that phone/ROM anymore), that was mossing -c or -T (or both, I don't recall but it was Android 11, Xiaomi) options.

Recently mentioned:

https://xdaforums.com/t/tools-zips-...tiple-devices-platforms.2239421/post-89505574

(Btw, in that post I wrongly accused Toybox - later I edited, but wget is not included to ToyBox; so, it was built-in I think as /system/bin/wget)

But you can execute: /data/adb/magisk/busybox wget
[Magisk] gloops100:
Hi all,

Since the upgrade of PIF module to 15.9.8 and shamiko to v1.0.1 the integrity doesn't work (only basic).

My config :

- Xiaomi fold 3 , Android 14 (hyperOS)

- Magisk 27

Modules :

- PIF v15.9.8

- playcurl v10.2 by daboynb

- shamiko v1.0.1 (300)

- Zygisk v1.9.2

What I can do to solve this please ?
[Magisk] osm0sis:
@sga999 try this one: https://github.com/osm0sis/PlayIntegrityFork/actions/runs/9145817676 🤞
[Magisk] sga999:
I think wget must have been included in the AICP rom (it has not been updated for a couple of years). But it could have gotten installed some other way though I certainly had no intention of doing so! I did have a busybox app, but I have uninstalled that. The system/xbin folder is still there with several things including wget.

I will attach wget script. Curl is in system/bin. I'll attach it even though you may not need it. It had no extension, but I zipped it. I'm not sure it's in a format that you need. Thanks for your help!
[Magisk] sga999:
I wrote that before seeing your latest post. I will try it soon.
[Magisk] zgfg:
Chiteroman PIF module includes prints, but for that you must not provide your own pif.json.

So, no playcurl or so and remove any your pif json

Please read instructoins on GitHub
[Magisk] osm0sis:
Thanks! Your wget is identical to the one from that ROM git I found. Hopefully my latest changes in #223 work around it for you. 🤞

autopif.sh: don't use half-baked wget-curl wrapper some ROMs include · osm0sis/PlayIntegrityFork@2dd7a17

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - autopif.sh: don't use half-baked wget-curl wrapper some ROMs include · osm0sis/PlayIntegrityFork@2dd7a17

github.com
[Magisk] gloops100:
Thanks !

In denylist, I only need to add :

Play store

Wallet

And delete cache then reboot ?
[Magisk] sga999:
That worked perfectly! Thank you very much. I mentioned this problem today after someone else reported it with another rom. Since I didn't really need a fix, I never said anything about it. I'm imagining there are others who may have seen this and just ignored it or gave up. It may have been mentioned and you responded about not using curl. I don't think I'm going back to find that now since you have fixed it!

Another way to fix it is with your busybox. But I won't install that until I find a reason.
[Magisk] zgfg:
Google Play Services and Wallet.

I never put Playstore

DenyList not enforced.

Reboot and wipe Wallet Cache
[Magisk] pythonimus:
I dont use any custom pif. Is the bundled one not working anymore?
[Magisk] purgy:
A print which had worked for ages, recently (not sure exactly when, last few days?) got the axe. I'm not sure on @chiteromans current stance on putting out updates to fix the detection, but check in magisk
[Magisk] osm0sis:
@Depressed T.Bear I think your issue is still different however, if you can still try #223 just in case, and then see if you can run zipsigner from my zipsigner module like I said before. 🤞