yashsingh1/xdaforums huggingface dataset:
[Magisk] Gilg@mesh:
works now with P8P.
[Magisk] TraderJack:
Suggestion:

Use hard coded values

Ship with pif.json.custom

If file renamed to pif.json use instead of hard codes values

This should provide the stability of using hard values with the flexibility if using a pif.json for those that want it until you figure out the reason for the failure.

?
[Magisk] HippoMan:
Both the latest 13.8 and the previous 13.8 beta (with its own contained pif.json) are giving me BASIC and DEVICE integrity.
[Magisk] TraderJack:
This is quite literally what the majority of posts for the past week have been about.

13.8 Beta (someone linked a few posts back) is the version to use to customize your own.

Fingerprints are not unique to a specific device (as in each individual device does not have a unique setting that no one else's has). There is no need to buy one to get a unique one. Just need to find a props file from a device that isn't in Google list. Again, this has been the topic of this thread for over a week now.
[Magisk] badabing2003:
What changed between 13.8 beta and 13.8 beta2? I must have missed that.

Is that the same as props1.2?
[Magisk] Vision:
I don't understand, for that it is the new feature pif.prop or pif.json, if Google block the old fingerprint, we write another and pass again, why removed? I missed something
[Magisk] Pirateguybrush:
Thanks for the information - I'm not familiar with what a fingerprint or build.prop file is/does, I've read the last 10 pages or so and didn't fully grasp it. That's provided some helpful context.

If Google is banning these fingerprints, does that mean the original/legitimate models are getting banned as well?
[Magisk] olimondo:
now working with *new* version of 13.8
[Magisk] chiteroman:
Updated custom spoof build.

Release CUSTOM SPOOF · chiteroman/PlayIntegrityFix

DO NOT USE THIS BUILD IF YOU AREN'T A DEVELOPER, ALWAYS USE LATEST STABLE. THIS BUILD IS JUST FOR TESTING PURPOSES. Removed custom resetprop. Fix JSON parsing. Less libs size. Few code improvements.

github.com
[Magisk] Vision:
I write this to @chiteroman, if @osm0sis, @pndwal, @zgfg you agree and everyone else, please tell him

View attachment 6037462
[Magisk] beeshyams:
Thanks for your help

I presume, I put those pesky apps in hide, disable Zygisk If I disable Zygisk, I wouldn't be able to run LSPosed right? Quite confused and frankly lost
[Magisk] chiteroman:
Custom resetprop does not work well on some devices, not only on versions prior to Android 10. Furthermore, the purpose of the module is to certify the Play Store and pass the DEVICE verdict, not to hide the root, for that there are already other modules.

If someone wants the custom resetprop, use the corresponding Magisk version.
[Magisk] FIERA03:
Thanks for your quick working.

However, Big G is definitely watching at your default custom props, so I guess it is one way to put a bullhead in the template that no longer dares to work.

At least it would be an impediment to them taking action.
[Magisk] Vision:
Yeah exactly this i write you before, i agree, the purpose of the module is to certify the Play Store and pass the DEVICE verdict and it does that perfectly. Thanks you for all your hard work
[Magisk] TraderJack:
I haven't been keeping up with the resetprop issue because generally I don't have Magisk/root issues.

I know that resetprop is used to reset/change a prop value, and generally these values need to be changed during a certain phase of boot.

But I don't understand what these variants of resetprop do and how exactly this is different then just modifying the necessary props in another way (if that can be done)

Can someone (looking at you @pndwal maybe :)) give a quick primer so I and others can continue on with a basic knowledge of the issue here.?
[Magisk] wfred:
I can log in with my password, but not with fingerprint
[Magisk] HRSE:
Play Integrity Fix v13.8 76.9 KB works now.
[Magisk] rseiler:
While I see the release notes for 13.8, what I don't see is anyone saying 13.7 no longer works. So is 13.8 mainly for people who never used 13.7? That is, if you installed 13.7 today for the first time it wouldn't work?
[Magisk] zgfg:
I agree about removing the custom reserprop binary

Btw, last week I debugged and provided a simple test easily proving how it breaks root detection (for me not n PI but in TBChecker, SCheck, etc, hence no wonder the others might have had problems with banking apps) - unfortunately, I didn't see anybody followed-up

However, that has nothing with support for custom JSON. Google has now killed bullhead but there are still two other devices whose values were used in the previous builds, tai___ and sail____.

I had extracted those spoofs from previous logs, created JSON files and both still perfectly work with v13.8 Beta - the version that supported custom JSON
[Magisk] acwcanada:
13.8 failed device integrity on p6p, going back to 13.7
[Magisk] dosbuddy:
can't confirm.

v13 works, and bullhead fingerprint in v13.3 pif.prop works also. So what?
[Magisk] V0latyle:
13.8 working for me, haven't used custom PIF.

Should I divulge device and build number? In case they are reading this thread, I don't want them to know what devices to "fix"
[Magisk] Vision:
No, only with private message if you want
[Magisk] osm0sis:
@chiteroman My friend, can I please teach you about git branches?

Please run this on the current repo so that you don't need to keep reverting the custom prop changes and adding them back over and over again (possibly introducing regressions each time):

git checkout -b custom
git push -u origin custom

Then you just `git checkout main` or `git checkout custom` to get back and forth between the two branches. 👍

Then I can open a pull request to the custom branch to preserve custom props between updates, tidy up scripts and such. 🙌
[Magisk] osm0sis:
It came after props1.2, and after a brief earlier 13.8 beta that got replaced with another 13.8 beta (which I'm calling "beta2") to maybe fix more prop stuff.
[Magisk] jesusmolon:
I'm having a problem with rcs chat in the google messages app.

It remains in "status: configuring"

The number is not verified and does not go to "status: connected"
[Magisk] HRSE:
I'm having the same issue, but I don't know what is the cause. Please PM me if you get any lead.

Hosts file is not the reason.

Xiaomi Redmi Note 9 Pro Global (joyeuse)

MIUI Global 14.0.3 Stable (Android 12) (heavily debloated)
[Magisk] osm0sis:
No such problem here on Pixel 8 Pro with PIF PROPS v2.0 and my custom pif.json.
[Magisk] rodken:
Maybe,

-- Disable RCS, wait a few minutes and re-enable RCS chat

-- Reset network settings

-- Force stop the Carrier Services app (if installed)

-- Clear the cache and data for your messaging app

-- Re-Verify your phone number

-- Turn off chat for two weeks. Yep, 14 days. Leave chat features off for the full period. Then wipe Google Messages and Carrier Services again. If you feel that 14 days is extreme, try 12 hours first.

-- You can even try to deregister from RCS and wait 48 hours.

This is not a lead, just suggestions which is why I didn't bother with a PM.
[Magisk] jesusmolon:
I have the latest version of the play integrity fix (v13.8) and I have tried everything and nothing has worked

I uninstalled the application, deactivated RCS chats, restarted mobile, activated it again

delete all carrier services data

And it was not solved, it remains in "status: configuring"
[Magisk] osm0sis:
And disabling the module actually fixes it? Might just be coincidental.
[Magisk] chiteroman:
Done 😁
[Magisk] zgfg:
IDK about 13.8 Beta 2

There was Beta supporting custom JSON.

That was removed and replaced by Stable 13.8 no more supporting custom JSON input file

However, that first 13.8 had custom resetprop binary built-in, but it caused Device failing to some.

After 40 minutes or so it was replaced by a new 13.8 Stable without that resetprop binary
[Magisk] ashus:
Uh since this got a bit offtopic, are the spoofing thing going to take care of my situation?

I have BASIC and DEVICE integrity green, Wallet seems to be happy with NFC payments, but my banking app (csob - Czech) detects root no matter what. It is already blacklisted in Magisk/Zygisk and I also tried Shamiko with the same result. Other blacklisted apps seem to work fine. I'm seriously considering getting another phone and not rooting it just for the purpose of these few stupid apps - to transfer my trust of all other apps as well in case s*** like this happens again.
[Magisk] osm0sis:
Amazing! You can even clone each branch to different directories so you don't need to checkout each time to work with them in Android Studio. 😁
[Magisk] jesusmolon:
I can't try again until tomorrow.

I spent all the verification attempts jajaja

But before all this Google stuff happened, I had it in "status: connected" with this same mobile

And another user has the same problem.

Say that I also have Android 12 like the other user
[Magisk] zgfg:
Just shortly, problems introduced by the custom binary resetprop lib (instead of using the 'official' resetprop from Magisk) were described here (at that time it was in v13.3 Beta or something)

Thu, few days ago:

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

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89179229
[Magisk] Vision:
I have v13.3 i think stable, not have inside the bin folder with resetprop, this is inside in the module zip

View attachment 6037500
[Magisk] HippoMan:
Sadly, some banks go beyond the standard Googlefrinchian integrity checking. These banks (as well as some other non-banking apps) do their own checking for various apps, etc.

I'm guessing that your bank might be doing something like this, and if so, PIF won't be able to help you.
[Magisk] zgfg:
It was 13.3 Beta (not 13.3 Stable) and I think 13.4 Stable.

Anyway, 13.x Stables are available on the Github, so they can be checked there
[Magisk] Vision:
Yeah right, until now v13.3 stable with custom fingerprint pass 2/3
[Magisk] FERRARI81:
Noob here.

What do u mean for custom fingerprint?

Do you use fingerprint from a friend's phone?

Do you use random fingerprint?
[Magisk] titomax82:
I want to share my experience till now... Maybe it can be useful.

Xiaomi Mi 10T Pro, stock EU rom 14.0.1 (android 12).

When all the problems started, I was with Magisk 25.2 and Displax SafetyNet Fix, Zygisk and Hide Magisk app enabled, no google apps or services in the deny list (only banking and other personal apps), "Systemless Hosts" magisk's module. Suddenly I uninstalled Displax module and updated Magisk to 26.4:

1st) PIF 12.1 - Airplane mode and then manually set date 10 days ahead in the future (to force google's various checks when online again) - Force close and clear all (cache+data) of Google's: Play Services, Play Store, Services Framework, Wallet, Reboot and set date back to the correct state. All working again, even if, I discovered for my pain that I had to add debit cards again, but especially lost connetion to my Wear OS Xiaomi Watch 2 Pro (all procedures to repeat, from pairing to reinstalling all).

2nd) About 10 days ago (I don't remeber precisely), device integrity lost again and Wallet not working... So I tried to do as in the 1st case, PIF 13.0, but only clearing cache (no data!): Perfect result! All working again without the side-effects!

3rd) Today: I repeated as in 2nd case with PIF 13.8. All working again and without pain or side-effects :D
[Magisk] Bec de Xorbin:
Good for you.
[Magisk] xSnowLeopardx:
All very well, but eh, v13 "Not working"? It definitely still is for me.
[Magisk] Serveh:
Hello, I installed the 13.8 version and my phone pass basic and device integrity but gwallet says that I don´t meet security requirements.

I cleaned all cache of gwallet and play store before installation
[Magisk] xSnowLeopardx:
Clean data from GPS, then reboot.
[Magisk] gpvecchi:
13.8 stable fails device integrity on P8P beta.
[Magisk] Serveh:
Still with the problem :/
[Magisk] xSnowLeopardx:
Maybe go back to a previous 13.X version then :/
[Magisk] Vision:
Oh sorry was not clarified, i pick up one from here (Deleted) and write it in pif.prop
[Magisk] HippoMan:
Just out of curiosity, is there any way that we can have one, single release with the use of resetprop being controlled by a true/false entry in pif.json (and with the missing entry signifying false)? ... or perhaps via the existence/non-existence of a certain zero-length file in the zip file?

This way, we could switch between versions simply by installing a different pif.json or adding/deleting the zero-length file, and then re-installing the zip file?
[Magisk] Pheggas:
Latest v13.8 works okay for me. Just a small flaw: youtube won't open and it crash always.
[Magisk] Revontheus:
At the time of writing, Version 13.7 works without issues on my end. I'm Android 13 and GPay works.
[Magisk] Nergal di Cuthah:
If playstore integrity check reports the correct brand/model etc (in my case raven is detected) does that mean plug-in's prop not being used (not a big worry because i pass both with 13.8, just wondering)
[Magisk] zgfg:
13.8 Stable does not read pif. prop, it uses built-in spoofs

Inspect logcat for PIF, you will see which spoofs it uses
[Magisk] Vision:
I'm little curious what exactly mean this? is from my old phone with stock rom Android 7.1.1

View attachment 6037536
[Magisk] TKruzze:
Make certain ALL processes are in the deny list for the app. If not, wipe after configuring as below. This has worked for me for sometime now.
[Magisk] chiteroman:
I want that AOSP root certificate private key, but dev doesn't want to give me 😭😭😭😭

Where you get AOSP_ROOT_PUBLIC_KEY ? · Issue #18 · vvb2060/KeyAttestation

Also, is it public the private key? Is this? https://android.googlesource.com/platform/build/+/refs/heads/main/target/product/security/testkey.pk8

github.com
[Magisk] biTToe:
13.7 still works for me [P6P magisk 26400]

I see no reason to upgrade until wallet breaks again.

That said, my Barclays CCapp hasn't functioned since the safetynet stopped working, and I assume that won't change anytime soon given my limited understand of what is going on with fingerprints etc...
[Magisk] borisSweden:
has anyone noticed if Play Integrity fix breaks RCS chat?
[Magisk] Vision:
I wish you found this key 🗝️, and what does mean in my old phone? Because have stock rom🤔
[Magisk] Nergal di Cuthah:
Thank you, but that wasn't actually my question. I'll try again.

When i run PI, from within playstore, it replies with my actual model and fingerprint. This is true for all versions of PIF. I pass both checks, so it's not urgent, but i wonder why it reports the actual correct info rather than info from the spoof.
[Magisk] BillGoss:
From previous info in this thread, I understand that PIF hijacks the call to Google and the Play Store doesn't actually know what got sent. It's showing what it would have sent (your current phone info) if PIF hadn't hijacked the call.
[Magisk] Nergal di Cuthah:
I may need a different terminal app. I use one that i just read doesn't work wiyh my device (simply named "terminal emulator" from f-droid's repo by jack palevich). When i run (under su) logcat | grep PIF i get an empty flashing cursor.

What is a good terminal for Android 14?
[Magisk] xSnowLeopardx:
Maybe it's an idea to change the v13 not working to "Working for some, use at your own risk".

Since it's working fine for me and I bet it does for some others as well.
[Magisk] Vision:
View attachment 6037539
[Magisk] rodken:
Might explain why on some devices, Call Screening, Direct My Call and Hold For Me is on the fritz.
[Magisk] zgfg:
Spoofing targets specifically the single process

com.google.android.gms.unstable

aka PI API/DroidGuard
[Magisk] Nergal di Cuthah:
And the playstore integrity test doesn't read from that?
[Magisk] Qnorsten:
The latest props version seem to work great for me.

I created a fork and fixed the handling of non defined/nulled defined FIRST_API_LEVEL and SECURITY_PATCH to something that feel better for me. Feel free to look at the pull request and do what ever you want with it. It should fix the "bug" that @osm0sis has complained about at least. My C++ is very rusty as well, so the code can probably be improved.

Properly handle non and nulled defined FIRST_API_LEVEL and SECURITY_P… by qnorsten · Pull Request #96 · chiteroman/PlayIntegrityFix

…ATCH This commit change how the module handle when SECURITY_PATCH and FIRST_API_LEVEL is either Undefined/Missing from pif.json Defined as null in pif.json Defined as "" in pif.json It will pass...

github.com
[Magisk] osm0sis:
PROPS v2.0 with custom pif.json working fine here. Should have zero effect on YouTube.
[Magisk] miss:
no funciona para mi, pixel 6 A14View attachment 6037558View attachment 6037559
[Magisk] whatsisnametake2:
google wallet and Lloyd's credit card apps are now detecting my bootloader unlocked. i'm not even rooted! when I got this pixel 8 pro I thought I would try not rooting for once, but I unlocked the bootloader first thing anyway to avoid later wiping if I decided I did want to root.

so now google wallet and mbna are throwing up a security/root issue. it has to be the bootloader as that's all i've done. I wasn't expecting this. will play integrity fix, shamiko and one of the magisk versions be able to get round this? I may as well root now, or lock the bootloader and hence reset the phone which is a total pain.
[Magisk] Nergal di Cuthah:
Are you sure it's not one of your other plugins or lsposed triggering it. Disable them all, reboot, check pi and add them one by one if it passes. Also please, per rules off site, translate your Spanish to English.
[Magisk] Vision:
That is good news, i don't understand why the YouTube won't open and it crash always like one user say 🤔 (with v13.3 stable not have this problem)
[Magisk] chiteroman:
Properly handle non and nulled defined FIRST_API_LEVEL and SECURITY_P… by qnorsten · Pull Request #96 · chiteroman/PlayIntegrityFix

…ATCH This commit change how the module handle when SECURITY_PATCH and FIRST_API_LEVEL is either Undefined/Missing from pif.json Defined as null in pif.json Defined as "" in pif.json It will pass...

github.com
[Magisk] zgfg:
I don't know for A14 but I always use NetHunter Terminal (and never tap to Kalu mode since I don't have NH, so using Android and Su modes)
[Magisk] Homeboy76:
@zgfg

Whew, I was planning to delete all older Play Integrity Fixes today, but checked this thread for the latest information and saw your post.

Guess i'll hold on to the few older versions I have a bit longer. :)
[Magisk] arda99:
PI is handled inside standalone "com.google.android.gms.unstable" process instead of the calling app itself. The app reads the real phone info, calls the api without passing any of these, the unstable process reads the phone info(and PIF injects fake prop), do the test and return the result.
[Magisk] zgfg:
Yes, it does

More than that - from the v13.7 logcat it can be extracted what to put to the custom pif.json

It's a different device/spoof than in the v13.8 or latest Beta v2.0

And that custom JSON can be used with the previous v13.8 Beta or new v2.0 Beta, and it works fine

Btw, ppl ask how to extract spoofs from their 'not-rooted' phones (of whom, most won't be suitable for) and overlook the low fruit under the nose😁
[Magisk] dcarvil:
Termux is my favorite. It is much more than just a terminal emulator, though, so may be more than you need.
[Magisk] zgfg:
Good question.

I checked and see the same

But what Playatore displays there in Dev options upon testing PI is not really the JSON that comes from the G server as a verdict.

You can see that JSon from Play Integrity API Checker, and it shows only what you passed, the request ID and so

The app that asks for attestation, does not collect the info about device. It just calls the API and obtains the final JSON verdict asa result

I'd say that Playstore ads there how it sees your phone itself.

And btw, it would be bad if Playatore would think that you are running a 4-5 years old phone with an old ROM and Android version (according to the spoofs for PI)

So Playstore (aka Finsky or Vending [machine]) is com.android.vending, not com.google.androud.gns.unstable and is not affected by the PIF targetted/Zygisk spoofs
[Magisk] fbirraque:
At least for me it didn't.
[Magisk] Nergal di Cuthah:
Sorry to disrail but all playstore found was fake "termux & linux tools" scams (according to reviews) is there a better source like f-droid
[Magisk] purgy:
13.3 (with pif.prop) just started failing device integrity, 13.8 (no pif.prop/json) is passing both basic and device.

Am I correct in thinking I could extract the values from 13.8 then applying them through pif.prop in 13.3? Is there a later stable release that includes the pif.whatever functionality?

Further to this, is there a way to find the values used from the code on github to use? Installing a newer version to extract the values via logcat kind of defeats the purpose.

Thanks for all the work you're putting into this @chiteroman (and everyone else)
[Magisk] dcarvil:
Yes, termux should be installed from f-droid, not the play store.
[Magisk] TraderJack:
This is correct. The injection is just done under the hood directly to the Droidguard process. Even though that component is utilized by the Play Store, the Play Store does not see the PIF injection. The Play Store will report your correct device model both when you use it to do a PI check, and when the store is searching for apps for your phone.

I was actually meaning to ask this question - and now is a great time. Is anyone aware of a way/module that CAN inject a specific device just to the Play Store and/or to any specific app? There used to be a module that specifically tricked the Store to thinking you were a different model for purposes of getting apps not "approved" for your device. I think that MagiskHideProps can do this, but it is kind of a lot to setup and also if you change the model of your phone there it is reflected OS wide. It doesn't seem to conflict with PIF, as the PIF injection will still override this, but ideally I would like to find an extension that allows spoofing a model directly to the Play Store (and/or other apps of your choosing as a bonus).
[Magisk] Nergal di Cuthah:
Sadly i found it and got the same result. Not sure if A14 issue or what I'm typing is wrong.

I'm typing

su
logcat | grep PIF

su invokes magisk as it should, but logcat results in a new line without prompt and waits. I can type on no prompt but to no avail
[Magisk] zgfg:
Bullhead spoofs as in v13.3 failed this morning

Nevertheless, you can take PlayIntegrityFix_PROPS-v2.0 (Beta) from GitHub, supporting custom JSON input
[Magisk] purgy:
Yes, in fact the play store version is terribly out of date, and can't be further updated there due to needing to target a lower SDK than google will let them.

Fdroid or GitHub are the places to get it and related plugins.
[Magisk] zgfg:
Resetprop your model, etc through the service sh in PIF.

Those are generic, not targetted spoofs - but as that, they will apply to ALL apps, hence may cause troubles with camera, or who knows (app will think you have a different hardware)
[Magisk] Nergal di Cuthah:
Fdroid version is two years old and says may not work for my device and won't be updated automatically.
[Magisk] dcarvil:
Those commands work fine for me on A13, but you will not get a result until you invoke PIF (i.e. do an integrity check).
[Magisk] dmenezes:
Nope, 13.8 stable working great here too.

Thanks @chiteroman for the great job!
[Magisk] borisSweden:
Because there has been a global breaking of RCS, it verified but doesn't work. Maybe the degree of Gapps package is at fault. So USNF is really depreciated for the most basic stuff?
[Magisk] dcarvil:
Do "pkg update", then "pkg upgrade" to update termux. It is just like linux, and you must initiate updates.
[Magisk] sawdoctor:
I'm rooted and using Lloyds and MBNA
[Magisk] Wolfcity:
Did you do anything after entering the command? At least you have to run Integrity Checker or Playstore integrity check to log some PIF activity. That's what it's waiting for. Should work with every terminal emulator.