yashsingh1/xdaforums huggingface dataset:
[Magisk] dmenezes:
I've used @chiteroman's v14 until March, when I switched to @osm0sis' V8 which is what I'm using to this day.

Both worked great, my reason for switching to @osm0sis was the more paced (ahem 😁) development cycle, and the fact it comes with autopif.sh ready to use.
[Magisk] zgfg:
Advice: Read the posts from today afternoon . There are not so many. And you'll know what to do to get your Device Integrity passing again
[Magisk] rrusek:
Thanks, that worked!
[Magisk] chiteroman:
topjohnwu has much more knowledge than me.

Plus, he works at Google and I don't want legal problems with a multibillion-dollar company.

I am currently using my new Poco X6 Pro (duchamp) with the bootloader locked and I have no problems, maybe I will put Magisk in it in the future to mess around with a few things.

Honestly, I think that nowadays root is not as necessary as it was years ago.
[Magisk] G5-User7080:
wdym with "it comes with autopif.sh ready to use"?

also, to migrate I only have to rename pif.json to custom_pif.json or something, right?
[Magisk] G5-User7080:
Until they add the ability to control charging speed and level, I need root.

Aside that,.. I'm more or less happy, I uninstall bloat with adb commands anyway, and I think app manager can also work with adb permissions.
[Magisk] dmenezes:
EWIW 😁

You mean, migrating from Chiteroman's to Osm0sis?

Not sure, long time since I migrated, memories are faint and I didn't take notes on that.
[Magisk] Nergal di Cuthah:
They're not actually A6 the x fingerprint didn't have that information. The script/PF/other methods might be adding that

Might be wrong though as in fingerprint code, in original non converted, it does say 6.0
[Magisk] osm0sis:
What do you mean? It does have that information, it's directly in the fingerprint field, and those should (almost always) match the 8 next fields below...

autojson/pif.json at main · daboynb/autojson

Contribute to daboynb/autojson development by creating an account on GitHub.

github.com
[Magisk] Nergal di Cuthah:
Yup that was the "i maybe wrong part" i typed the first part in then had the idea to recheck. Was expecting a separate field but then saw fingerprint line had 6.0 in it.
[Magisk] zgfg:
Besides the Griffin, two more are gone, one Lenovo and one Pixel

Other privates are still ok
[Magisk] G5-User7080:
I did, but I still don't know if there's a difference between the two modules now..

And if I knew why stuff was happening I wouldn't be asking questions.

People seem to be able to find many fingerprints from roms, but for some reason I found exactly one after checking like 8 different roms + different versions of them.

So I can't exactly help but wonder if I am overlooking something important here.
[Magisk] Nergal di Cuthah:
Not since feb 29. There are a few working prints. most of us are, begrudgingly, using the print provided by xiaomi.eu rom.
[Magisk] sir_bazz:
Thanks @osm0sis

Up and running again with autopif.
[Magisk] ashish1989:
I ran this command in terminal, but it says directory not found
[Magisk] casouzaj:
You should run the command either inside the folder where the .sh file is, or specifying the full path to it.
[Magisk] ashish1989:
Yup, you were right, done it
[Magisk] ashish1989:
You are right, device integrity is back again with Clark print on my A8.1 device. Lets hope it stays like this for long.
[Magisk] tom1807:
Your Pixel and Lenovo prints were still working until yesterday?

My ones all died at the Red Wedding (aka the great purge).

After that, I didn't bother anymore to find new ones.

Cheers

Tom
[Magisk] blu.italia:
I've asked Google AI (Gemini), how we pass strong integrity, his answer is below. For me it doesn't work, but when you read the complete conversation you are mind blowing how good Gemini is, and perhaps someone find the right question that we get the right answer to solve this annoying problem.

‎Gemini - Umgehen der Play Integrity-Zertifizierung mit Magisk

Created with Gemini

g.co
[Magisk] menuisier3:
Hello, once again the RCS chat has not been working since this morning.

Is there a solution, thanks
[Magisk] Nergal di Cuthah:
Turn off rcs

Load the new working fingerprint

Clear messages data (maybe)

Turn on RCS

If you want more read this thread's important posts
[Magisk] majorfigjam:
Short answer - update your print, like most others have.

Longer answer - try reading the last few pages before asking a question that has just been answered ten times over.
[Magisk] pndwal:
Yeah, a good bet with current changes/use... Doubt they impose limits on themselves...

https://developer.android.com/google/play/integrity/overview#have-anti-abuse

Were they smart? 😆 PW
[Magisk] pndwal:
Process... Google Play Services com.google.android.gms.unstable (Droidguard/attestation process)... If hiding root, you need to hide from Google Play Services com.google.android.gms (main process) also on modern devices...

👀 PW
[Magisk] Cichy26:
I'm on A13 KernelKSU. After your module i got this information. I lost Google Play Certification. And Gpay didn't work too. Any solution?
[Magisk] Lord Sithek:
Man, it's not the fault of the module, actually it makes you pass Play Integrity. You have to clear Play Services data or just wait for Google servers to do periodic check
[Magisk] thesingular:
Check the quotes below:

GMS is a typo (actuıally not a typo, check the reply below) and is for Google Play Services. GSF is Google Services Framework (in my opinion you don't really need to clear the data for that one)

Alternatively, try this one:

The complaining Google apps here are Play Store and Wallet obviously.

Now that I think about it, you might need to force stop Google Play Services as well, not sure, I forgot lol. I'll edit it back in the post. You may also reboot instead of force stopping apps.
[Magisk] pndwal:
+ @Cichy26

Not a typo... Google Play Services/Google Mobile Services, is GMS (com.google.android.gms)

... Typo was here but corrected to GSF:

Agree... I've never had a need...

Maybe he was thinking of Google Play Protect Service (where it is separated from Google Play Services in late devices) since Play Store polls that for a cached PI verdict to set Play Protect certification status and registered requirements individual apps to be available in Store... It's Data should be wiped to restore Device is certified status if it exists...

🤠 PW
[Magisk] thesingular:
Oh, right, THAT GMS....oops. Thanks for correcting.

How late are we talking about here?

My Xiaomi 12T which launched with Android 12 seems to not have that one.
[Magisk] HippoMan:
Great work!!!!! Although the cat-and-mouse game continues, this particular battle is a definite win for the mice!

Can anyone report that there are indeed no problems when using this latest PIF version with Magisk Delta 26301 under A13?
[Magisk] marcopit-92:
Hi guys yesterday I realized my wallet app was not working. My device is Asus Zenfone 8 flip, rooted with bootloader unlocked. I have magisk, shamiko, the new play integrity fix, lsposed with some modules.

Seems my meet device integrity is again green but wallet application says the device is not secure to use to pay.

I have just tried all the cache clean on all play app and wallet also with airplane mode but nothing works.

I have read I have to wait 24 hours, is it true?
[Magisk] kred1:
Any solution for not working Gpay since yesterday for non rooted devices with custom roms? Do the maintainer need to to something?
[Magisk] 130ryokohama:
i'm in the same boat. mine clears MEETS_DEVICE_INTEGRITY and MEETS_BASIC_INTEGRITY using google play's test in "developer options" and via integrity checker app but still google pay/wallet still shows "Your phone doesn't meet security requirements" :(

do you need to wait 24 hours and it will automatically clear without clearing cache etc?
[Magisk] pndwal:
Pixels have it... Seems from Android 12, and since I know some P5 series devices have it, it seems it can be included in updated ROMs...

Here's an old XDA article announcing it:

https://www.xda-developers.com/google-publishes-play-protect-as-separate-app-for-quicker-updates/

👀 PW
[Magisk] marcopit-92:
I hope it is the wait. Have no idea, I tried everything. I uninstalled also YASNAC, clear cache of all app and rebooted. I also deleted data for wallet but nothing.

The only thing I did not try is change calendar date in future to force update as somebody wrote.

Thanks to developer for the effort anyway!
[Magisk] pndwal:
Wait (could take several days depending on device actually), try the change-time-forward to force PI check(?) trick mentioned above, or clear data for instant fix... Cache isn't enough... 🤠 PW
[Magisk] 130ryokohama:
same as me. I did the same with no luck.

I hope it will clear automatically like a few people on here said.

keep us posted on yours
[Magisk] viniciuskmv:
On my Redmi Note 10 PRO with MIUI 14.0.8.0 it worked, but it seems unreliable.

It either pass or fails in the integrity check, but I got to use GPay in 2 occasions. Better to wait for the Xiaomi.eu devs to fix this.
[Magisk] marcopit-92:
Ok I will wait and keep you updated if it still does not work. What about Shamiko and hide my applist? Shamiko was needed before on my device to access gpay.

Hide my applist was not needed but I thought would be helpful, if it is not necessary for gpay I may uninstall it
[Magisk] chiteroman:
Are you using Xiaomi.eu rom or stock MIUI ?
[Magisk] chiteroman:
Only basic and device integrity pass not strong integrity · Issue #15 · chiteroman/PlayIntegrityFix

Only basic and device integrity pass not strong integrity Im using redmi note 9 Pro 4G Evolution X Android 14 Community Build My Safetynet Passes By Default

github.com

🤦‍♀️🤷‍♀️
[Magisk] pndwal:
Clearing data usually does it, although I have had to uninstall updates also in the past... This can be fraught however: app may revert to Google Pay and may take some time to properly update to Wallet again... Also, had to reboot immediately after cleaning data (before opening app) or Activity lists would refuse to populate although contactless would work... If clearing data really fails and you have confirmed you do have Play Integrity (nb. this is NOT SafetyNet) DEVICE_INTEGRITY, I'd be inclined to wait a while to see if it resolves itself... 😬 PW
[Magisk] majorfigjam:
But we know the answer is easy for devices A9 or above - factory reset and lock your bootloader.
[Magisk] zgfg:
They worked on May 13, last time I tested them before the yesterday. Yesterday they stopped working.

I do not retest all 'private' prints every day. Retested them yesterday and all the others still work

There are many eg Pixels, not one. And for a one, single device/model you may have 30 or more ROM versions /OTAs (being different in Fingerprint and its derived fields and Security Patch), and if one of them passes, all others usually do not pass. There are very small number of devices from whom you can find more than one prints working

In other words, if for device XYZ you ovserved that crrtain prints got banned on Feb 29, it doesn't mean that some other prints from the same device did not remain unbanned. You just need to test all prints (from all official ROM version and releases) you could find from that device
[Magisk] dmenezes:
It's impressive how stuff in German sounds automatically more authoritative and "right", even when it turns out to be the complete opposite

Just like in that ages-old joke: https://www.astrodigital.org/digital/achtung.html

🤣
[Magisk] zgfg:
Jawohl und Achtung bitte. Can you copy/download the whole JSON, I can get only up to the hmacsac_module_8

Btw, there are syntactical errors in the JSON (causing that modul will not read those fields), they cannot be:

"ro.kernel.android.feature.android.kernel.lzma", "1", // LZMA-Flag

(and all bellow)

instead, it must be:

"ro.kernel.android.feature.android.kernel.lzma": "1", // LZMA-Flag

So, his Zusätzliche Felder should be:

// Zusätzliche Felder für MEETS_STRONG_INTEGRITY
"ro.boot.hw_version": "XT1575", // Hardware-Version
"ro.boot.revision": "10", // Revisionsnummer
"ro.boot.product": "clark", // Produktname
"ro.boot.board": "clark", // Board-Name
"ro.boot.manufacturer": "motorola", // Gerätehersteller
"ro.boot.baseband": "msm8937", // Baseband-Version
"ro.boot.radio": "msm8937", // Radio-Version
"ro.boot.selinux": "enforcing", // SELinux-Status
"ro.boot.serialno": "1234567890", // Seriennummer
"ro.boot.mkrokernel": "v3.10.40", // Kernel-Version
"ro.boot.uboot": "U-Boot-2016-04-30", // U-Boot-Version
"ro.boot.mode": "normal", // Boot-Modus
"ro.secure": "1", // Secure-Flag
"ro.debuggable": "0", // Debuggable-Flag
"ro.kernel.qemu": "0", // QEMU-Flag
"ro.kernel.android.boot.attest": "0", // Attest-Flag
"ro.kernel.android.exception.hwm": "1", // HWM-Flag
"ro.kernel.android.feature.android.kernel.lzma": "1", // LZMA-Flag
"ro.kernel.android.feature.perf_driver": "1", // Perf-Driver-Flag
"ro.kernel.android.feature.boot_perf": "1", // Boot-Perf-Flag
"ro.kernel.android.feature.report_event": "0", // Report-Event-Flag
"ro.kernel.android.feature.sec_hmacsac_module": "1", // HMACSAC-Modul-Flag
"ro.kernel.android.feature.sec_hmacsac_module_2": "0", // HMACSAC-Modul 2 Flag
"ro.kernel.android.feature.sec_hmacsac_module_3": "0", // HMACSAC-Modul 3 Flag
"ro.kernel.android.feature.sec_hmacsac_module_4": "0", // HMACSAC-Modul 4 Flag
"ro.kernel.android.feature.sec_hmacsac_module_5": "0", // HMACSAC-Modul 5 Flag
"ro.kernel.android.feature.sec_hmacsac_module_6": "0", // HMACSAC-Modul 6 Flag
"ro.kernel.android.feature.sec_hmacsac_module_7": "0", // HMACSAC-Modul 7 Flag
"ro.kernel.android.feature.sec_hmacsac_module_8": "0", // HMACSAC-Modul 8 Flag

However, it still passes Basic and Device, not Strong - hence no use of all that, FALSCHE :)
[Magisk] tom1807:
I had several different props, just didn't have time to download the other images from these devices and extract the prop file and test again.

I'll do when I have some more time, until then its the XEU print.

Cheers

Tom
[Magisk] Vision:
I thought, you buy this phone for test.

I have only my main phone 😂🤣

View attachment 6103440
[Magisk] zgfg:
pif-test-json-files.sh script can help you for automated testing:

https://xdaforums.com/t/tools-zips-...tiple-devices-platforms.2239421/post-89482876
[Magisk] chiteroman:
v15.9.8 released!

Release v15.9.8 · chiteroman/PlayIntegrityFix

MEETS_DEVICE_INTEGRITY is green again ✅ Refine code You can define your own native props in pif.json!

github.com
[Magisk] tom1807:
Thanks, I used Pixelflasher before to test the build.props, still need to get the images and extract the build.prop. (Well, I can use Pixelflasher also for the download).

Cheers

Tom
[Magisk] osm0sis:
Uhhh, you're welcome. 😐
[Magisk] dmenezes:
Ausfahrt, Parken Verboten, Ein bier bitte!

(the three most useful expressions for foreigners in Germany)

🤣

Same here. Sounds like Gemini isn't as good as Google hypes it to be 😁
[Magisk] zgfg:
Moreover, there are syntactical errors in Zusätzliche Felder für MEETS_STRONG_INTEGRITY

I just edited my previous post with the corrected fields, but still it doesn't help to pass Strong

Falsche!
[Magisk] pershoot:
15.9.8 fails DEVICE. Rolling back to 15.9.7 restores it.
[Magisk] osm0sis:
Sounds like the usual unnecessary rewrites at play. 😉
[Magisk] ref114270:
I have a Xiaomi 13pro, but the device doesn't work just by installing this.
[Magisk] Spartacus500:
Working 🥰
[Magisk] ref114270:
Just install it? Why?
[Magisk] LAwLB15:
Just updated to 15.9.8 and after almost 2 months of only getting basic integrity IM FINALLY BACK TO DEVICE INTEGRITY

Running LGV20 (h918) Android 8.0

Thank You so much for this!!

We back baby😁
[Magisk] Spartacus500:
I installed it and it works ✅
[Magisk] xcl1pse:
Why adding props in json? seems redundant
[Magisk] chiteroman:
feat: add prop ro.secureboot.lockstate locked by scruel · Pull Request #317 · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] xcl1pse:
why not user adding itself? also what device will crash after adding that prop?
[Magisk] Cheesethief:
Working just fine here on a Pixel 5a and a Nothing Phone (2a).
[Magisk] ref114270:
After deleting pif.json, the device worked. I didn't read the instructions. I apologize to you for a fuss over.View attachment 6103486
[Magisk] dlads:
After quite some time, my fingerprint just failed today..

Bugger...😭
[Magisk] zgfg:
Last six pages here (since yesterday afternoon) are all about that, with instructions and everything you will need to restore Device Integrity
[Magisk] G5-User7080:
When updating to the newer version, does it keep my custom pif.json?

And is it even necessary to update if I'm currently passinv device?
[Magisk] pndwal:
Plaudits for the soothsayer (and for XEU)...

Perhaps we take these things much too seriously when perhaps the right response is simply to laugh ourselves silly – then fall on our knees and pray like madmen for salvation from all these jokes and jokers we keep inflicting on ourselves. Somebody pass the Demerol – and beware the Ides of July! 😜 PW
[Magisk] Vision:
Something like that 😂🤣

View attachment 6103542View attachment 6103543
[Magisk] pndwal:
clark_retus, "cleric, clerk"_"a little touch-up"...

Time for a clerical touch-up I guess... 💣 PW
[Magisk] JustinCretible:
Is it normal that the fingerprint from my old LG V30 does not work? I thought all phones have a unique fingerprint, making them immune to being banned. I tried lowering the FIRST API level from 25 to 23 and 22 but it still didn't work.

Anyways, after messing around without any luck, I updated to chiteroman's Play Integrity Fix v15.9.8 and deleted my pif.json.

Now I'm passing device integrity, but I'd like to find my own custom fingerprint in the future. And I don't understand why my old phone's fingerprint did not work.
[Magisk] G5-User7080:
as far as I get it, the fingerprint is limited to the model and specific rom version, but all phones on that rom version have the same.

So those fingerprints are known to google and the oem.

Why some Android 8 or 9 phone with stock and locked bootloader works but an unlocked one using it's props,.. I have no idea.
[Magisk] CZ.Kostra:
Read first post of this thread. Continue by opening links in it.
[Magisk] pndwal:
You're pretty much right, except that use of the word "banned" in these forums only considers effect when device print is spoofed... It won't be 'banned' by Google for LG V30 in combination with all it's native properties... We haven't yet figured out the exact cross-checks Google must be doing to differentiate between PIF spoofing methods and genuine device properties however... That would no doubt be immensely helpful.

We know Google is kaiboshing (better term?) more and more print/prop/field sets for PIF purposes (and I wonder why any are exempt personally)... All we really know is that somehow we're being left some wriggle room. (Still some 4% of what we might have expected to work?)... 😂
[Magisk] patrioticparadox:
And I have been reading that back and forth for the last ~40 minutes at least six times and I'm just not catching it. I understand the concept of what happened but reading through the thread since the conversations about it all started, I can't understand what to put where.

I see the comments from @dmenezes and @osm0sis but I can't connect them to my admittedly limit knowledge of replacing prints.

I have PlayIntegrityFix v15.9.8 installed. I understand that I need to run one of the scripts and then copy the output to a specific location. (and reboot)

What I'm not grasping is:

Which script do I run? Is it already included with that module or is it one that's in the links in the previous pages that I need to manually download and execute? And if so, which one?

I saw something about not running it with Termux and something else about simply making sure Termux was updated first. Termux is my goto but should I use something else?

Is there anywhere in particular that the script needs to be run from? I saw something about one script even being able to run from /sdcard/Download so is there an ideal place to run it from?

Where do I copy the output file(s) and what should their name(s) be?

This is my first print update so any help is greatly appreciated.
[Magisk] pndwal:
You can just (clean) install very latest @chiteroman PIF (v15.9.8) and it should work for now... 👍 PW
[Magisk] zgfg:
It's all normal because you unlocked the Bootloade. And you probably installed some custom ROM, maybe custom Recovery, root (otherwise, why would you unlock Bootloader). But just even unlocking Bootloader was enough

Once you did that, you don't have your original stock/official device and Play Integrity finds that and fails PER DEFINITION

If not happy with that and not willing to read and understanding how and why you need to spoof things now - simply unroot, return to your official ROM, re-lock Bootloader and enjoy with the not-modded phone that will happily pass Strong Intehrity and you will never have problems with Wallet, RCS, banking apps, anything
[Magisk] JustinCretible:
You can simply install chiteroman's v15.9.8 Play Integrity Fix. Then search the folder root -> data -> adb and delete the file "pif.json" if you have one there. That file is the custom fingerprint that you may have generated previously. Most likely that fingerprint is no longer working.

Reboot your phone after completing the steps and you should have device integrity passing.
[Magisk] patrioticparadox:
I see. Thank you so much for that clarification. That means I've gotten something else wrong because I'm still failing device. At least that part I feel comfortable troubleshooting myself. It had been working so I probably borked something trying to figure out this part that I didn't need to do. Ain't that just how life goes?

Anyways, thanks for the help. My mind is at ease on that part, at least.

Edit, saw after posting: Thanks @JustinCretible and @zgfg that did it. PASSED

Love this community!
[Magisk] pndwal:
So Galaxy S4 LV 4.2.2 w/ LOS A13!... Just bank app data?... Did that fix PI DEVICE_INTEGRITY? (Did you clear Play Services data to?)

Is it official LOS?

Your device doesn't actually use PIF main functions ie. Doesn't need fake/broken keystore registration to force fallback to basic attestation on device because devices can only usebasic attestation, nor do you need targeted print/prop/field spoofs to bypass HARDWARE_BACKED evaluationType enforcement server side as Google won't enforce that for S4...

Would be interesting to know if you pass PI DEVICE_INTEGRITY with PIF uninstalled, DroidGuard/attestation (Google Play Services, com.google.android.gms.unstable) process added in denylist, DenyList not enforced and Shamiko hiding module (only module you should need) installed (to fix sensitive/suspicious props)... (Nb. Your fingerprint prop should be old enough not to need to spoof matched security patch+ print set assuming LOS uses S4 print... If official it will.)

Secondly, it'd be interested to know if @osm0sis's alternative to this, ie his PIF Fork module running in scripts only mode, works too.

Please report results if you try. 👍 PW
[Magisk] zgfg:
Edit: From the latter post, seems you have passed
[Magisk] pndwal:
Please see @JustinCretible's post above yours about custom pif.json if you had module installed previously... It's why I said 'clean' installation.👍 PW
[Magisk] dlads:
Yea I'm already sorted mate, I was in the gym, tried to get a protein shake, failed.

Uninstalled, reinstalled another, removed the card,cleared data on wallet and readded it.

Bought my shake and necked it.

Was fixed in about 5 mins tbh.

I know what I'm doing was just stating it's failed for me as well....I'm not reading any of the last whatever pages.
[Magisk] chrbur:
You can simply install chiteroman's v15.9.8 Play Integrity Fix. Then search the folder root -> data -> adb and delete the file "pif.json" if you have one there. That file is the custom fingerprint that you may have generated previously. Most likely that fingerprint is no longer working.

Works for me an Pixel8Pro - uninstalled AutoPif apk

Thx so much :-)