yashsingh1/xdaforums huggingface dataset:
[Magisk] AlexS2412:
because if you pass detection apps easily then you no longer *have* to worry about any normal application finding your root. that is the end goal, like things used to be with applications just working, even if it takes a little more setup to do.
[Magisk] majorfigjam:
Yup. Read post 1 on page 1, then the faq, then the linked resources.
[Magisk] AlexS2412:
just in future in case if you were to install an application that refuses to work because "developer options are on" or "root detected" like many bank apps these days.
[Magisk] majorfigjam:
Again, who cares? The original use case was satisfied for lpedia.

And seriously, Google can spoil everyone's use case with a Play Services update, so everyone *has* to worry about that.
[Magisk] chiteroman:
v16.5 released

Changelog:

- Update hook framework
- Fix Device not passing in few devices
- Improve code
- Reduce Zygisk libs size

Release v16.5 · chiteroman/PlayIntegrityFix

Update hook framework: Dobby Fix Device not passing in few devices Improve code Reduce Zygisk libs size

github.com
[Magisk] tryigitx:
First-Sale Doctrine and DMCA Exemption

You can access the Keybox.xml file by bypassing security measures on your device. Even if you have a hardware chip.

In short, Google can never win such a case. The only way you can get into the gray area is if Google has proof of how the person who leaked the Keybox leaked it.

Even in such a case, a person who distributes the Keybox file can never be guilty according to the law. Additionally, due to its function, the Keybox file is not licensable and can be used under Linux.

In short, the Keybox file has no legal significance. Only internal information leakage methods etc.
[Magisk] tryigitx:
Even if it does this, its own keybox file will return basic result. Of course he has to do this. A valid Keybox file is the simplest way to know that it works 😊
[Magisk] Nergal di Cuthah:
That's a little u.s. specific and doesn't apply to everyone. Also distribution would void that, the key (sorry for pun) being your own keybox on your own device.
[Magisk] HippoMan:
... and it therefore might require a court case to resolve any such "grey area" disputes. So, make sure you have a good lawyer if you aren't certain about the provenance of any Keybox you have obtained.
[Magisk] osm0sis:
Someone already reported Gemini, but that it works even though RCS chats with real people are failing due to the sailfish print. It's therefore not a good test, since it's seemingly unrelated.

Edit: Nevermind. What I remembered seeing was edited after to add that sending to Gemini didn't work. 👍
[Magisk] Captain_Throwback:
That's not what I recall...

🔧 [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] alekyiv:
And there is something to unpack without a computer payload. bin and get to the img files of the firmware, otherwise I see an option only for windows + there is some program... Maybe there is some application for unzipping bin files on Android? Thank you!
[Magisk] osm0sis:
I'll see your yesterday post and raise you a Tuesday post:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89580503 🤷‍♂️

Edit: Ah, I see he updated it with sending test messages to Gemini which failed. Touché! 👍
[Magisk] BillGoss:
My notes on doing it on the phone:

Source: https://github.com/ssut/payload-dumper-go/releases

Note: the source checksums are sha256

Refs:

GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go

an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.

github.com

https://xdaforums.com/t/tool-a-quick-android-ota-payload-dumper.4173271/

Install the latest payload-dumper-go_*_linux_arm64

version in Termux: ~/bin/payload-dumper-go and give it execute permission.

Run it as root, otherwise you get "Bad system call".

Can also install payload-dumper-go_*_linux_amd64 in WSL, or payload-dumper-go_*_windows_amd64 in Windows (and WSL).

Note:

@osm0sis also has a Magisk module for it. See: "Payload-Dumper-Go for Android Magisk Module" in https://forum.xda-developers.com/t/...-and-ends-multiple-devices-platforms.2239421/

This way you can run it in Terminal Emulator (needs root as usual) if you don't want install payload-dumper-go in Termux.
[Magisk] majorfigjam:
For those interested in such things, I confirm that updating to the latest Magisk Canary 27003 does not appear to have had any adverse effects on the modules.

With an "unshared" print, I still have Device Integrity, RCS and wallet on my mainly stock A14 Pixel 6 Pro, and on my A15 Beta 3 spare P6P.
[Magisk] osm0sis:
It will break Shamiko 1.0.1(300) however! Zygisk Assistant works for now instead, but note Shamiko will need to be uninstalled or disabled for it to function correctly. 👍

Edit: Shamiko 1.1(344) is now out to address the issue, but seems to have introduced a different bug that crashes/hangs everything on the DenyList on my Pixel 8 Pro. 🫤
[Magisk] alekyiv:
404 ****
[Magisk] alekyiv:
But I already did it on a PC through Python, CMD. Only site 404 in chiteroman! (((
[Magisk] tryigitx:
Google's or any company's own policy will surely only affect its employees. It's like not catching a serial killer without evidence.
[Magisk] shaw790:
Still cant pass device integrity ((((

On Stock oos rom and magisk 27. Tried all sorts of stuff like shamiko, zygisk assistant,zygisk detach and all...
[Magisk] HippoMan:
But what if a Googlefrinchian employee decides to make some proprietary keyboxes available to some people in return for some sort of favors, and then some of those keyboxes end up in the wild and then later in the hands of some of us modders who don't realize where they originally came from? If nothing else, those modders might end up being interrogated about where they got the keyboxes. And if the interrogators are suspicious about whether any given modders are telling the truth, those modders could indeed then be in need of legal representation.

I, for one, don't want to ever have to deal with such a thing.
[Magisk] majorfigjam:
Have you read Page 1 Post 1, and the related faq and guides?

You say you have a stock rooted rom with Magisk, what version? As Osm0sis advised, Shamiko is broken on 27003 Canary, so you need only have Zygisk Assistant.

Do you have LSPosed as well as your long list of magisk modules? You previously referred to apphide.

Try deleting LSPosed and every magisk module but zygisk-assistant and PIF, and see what happens. Then add things back slowly, to see what breaks.
[Magisk] shaw790:
do i delete or disable the modules? also magisk is 27000. should i do the canary one?
[Magisk] majorfigjam:
Disable them, and 27000 is ok

If you have lsposed, may need to delete it
[Magisk] zgfg:
Do you really fully pass ALL known detectors, incl. Momo and particularly Minotaur?

Or if you not, does it or not prevent you to use your setup on the real banking, games and other apps
[Magisk] Aregtheeditor:
So I don't have a ton of time to search fingerprints, is it possible to ask someone here to give their working fingerprint?
[Magisk] majorfigjam:
You can always ask ... if all you want is Device Integrity, Chiteroman 16.5 will give you that, all else being equal.
[Magisk] Aregtheeditor:
No I need rcs too
[Magisk] cabagekiller:
You will most likely have to hunt on down yourself.
[Magisk] majorfigjam:
Then find Chiteroman's post 17634 where he gives the biggest clue where to look for a fingerprint.
[Magisk] shaw790:
Found the culprit. It wasn't lsposed. It was an old module called xml pack. Dont even use it anymore. Thank you for the assistance
[Magisk] Aregtheeditor:
But idk the best places to find a fingerprint from
[Magisk] majorfigjam:
There aren't that many places to find that type of rom. Have you tried google

I pm'd you.
[Magisk] jobsense:
zygisk turned to inactive status after quick reboot or restart ( not reboot ) using this module. is it normal, any solution?
[Magisk] majorfigjam:
Not normal. Something is conflicting.

Need lots more info about your setup to determine what may be required.
[Magisk] jobsense:
View attachment 6118365

instead of using this button i tried to use quick reboot app which takes few seconds to restart but every time it restarts zygisk is disabled.

note: when i use reboot button mentioned in attached image zygisk keeps enabled but takes much higher time to reboot
[Magisk] badaas:
Working for me on P5 with latest PE ROM.

👌
[Magisk] marcopit-92:
Today we have new update for the PIF. Just updated it to this latest version and everything still works as normal.

Wallet has all checks.

Despite the Marriott not working, today I tried check using Momo app. So I installed it and this is the result, which to me seems pretty fair.
[Magisk] TraderJack:
You can get rid of the debugging message with the "Hide UserDebug" Magisk Module.

Nothing you can do in regards to the bootloader message.
[Magisk] BROKEN1981:
Thanks
[Magisk] CiLiBi18:
After restart, it failed.. I'll test the latest stable version
[Magisk] CiLiBi18:
12.3 works!
[Magisk] cubandanger05:
P7A, using v8.6 and it works. Wondering if I should update or follow the "don't fix it if it's not broken"
[Magisk] pndwal:
8.6?... Maybe revoked use of prints was temporary?... Might test too... Tomorrow... 😴 PW
[Magisk] chiteroman:
SafetyNet probably working but Play Integrity...
[Magisk] zgfg:
Just a short note

Last Wed when Device Integrity went down, I intentionally didn't open Wallet nether my banking app

So on Wed and Thu I was still able to pay by NFC - I just unlocked screen by fingerprint, enabled NFC.snd made contactless payments

Eventually, on Friday, it didn't let me popping up that phone does not meet security requirements

On Sat I upgraded my ROM (they have updated Device Integrity spoofs) and opened Wallet and my banking app to make sure everything was ok. And paid again by NFC, without the need to wipe data for Wallet

And ofc, I have my banking app and gms & gms.unstabke in the not-enforced DenyList (no Playstore, Wallet nor any other Google app) and Shamiko (I have also LSPosed, HMA and few other LSPosed banking apps) . I don't have PIF (USNF nor MHPC) since the spoofs are provided by the custom ROM

And everything is nice again as on today's photo😁
[Magisk] TraderJack:
Sorry about the GMS/GSM confusion. I won't edit my OP so you don't look crazy in your replies! I am speaking strictly about:

com.google.android.gms

And I'll just say this... If you had asked me if it should be on the DenyList I would have said yes, and by that I mean I would have thought that if I looked on my list it would be there. Now, TBH I did not consult my list yesterday prior to upgrading from USNF to PIF. But, after PIF and reading some posts I checked my list and GMS was not selected at all. So, unless PIF actually removed it from the list, this means that it hasn't been listed there for who knows how long while I was using USNF.

And, despite it not being there, my phone was working perfectly fine to block all the stuff up until this week when Google made the changes.

So this all added to my confusion about GMS being needed even without PIF, because it seems it wasn't.

Since last night I removed everything from DenyList except my bank apps and have done several reboots (but no cache/storage clears) and everything still appears to work fine. So regardless of past needs, it does seem (at least in my config) that no Google apps are needed with PIF. I think I will log an issue on @chiteroman GH page to perhaps update the docs in that regard so there is less confusion.

As for the rest of the history lesson/recap - thanks for that! I did actually live through most all of it, but I'm not around and up on everything on a weekly basis here and I'm at the point in my life where my brain moves out lots of information not currently in the working set! Once I figure out the recent thing that is working for me I tend to move on for a bit.

Thank also for your posts here (and elsewhere) regarding various Magisk issues. I have never moved off of TJW and went straight from the old HideList method to the Zygisk and Shamiko route. While I have had to fiddle with things I have always been able to get all my apps working and never saw the need to move to a Magisk variant and have to worry about what all that entailed. As TJW still is updating Magisk I will probably stick around with that. I see from your posts you have moved back to TJW/Shamiko and have gbleaned that some of the advancements from Alpha/Delta are making their way into Official: like NB-Zygisk support (which I don't fully understand all the technicalities, but do grasp the advantages).

I think I'll upgrade from 25 to 26 today, and as soon as 27 comes out (hopefully soon) I will test it and then likely hold off on my full device rebuild a few more weeks.
[Magisk] zgfg:
PIF removes Google Play Services from DenyList - how and why, it was described in several posts in this thread

Check the module's post-fs-data.sh script
[Magisk] zgfg:
Plus a side note - for Wallet to work, Google Play Services must be granted RECEIVE_SMS, READ_SMS and SEND_SMS permissions

They can be also checked from Terminal Emulator by (for ADB from PC, prepend adb shell):

dumpsys package com.google.android.gms | grep SMS

Or granted eg by:

pm grant com.google.android.gms READ_SMS

etc
[Magisk] TraderJack:
I've never had to set anything like this for wallet to work, so I assume it is the defaults. If so, why would it have been removed?

Ok, I thought it might be the case but wasn't clear if it actually removed it as in unchecked it or if it was just doing something under the hood to ignore it. I see the line in the script now so this likely solves that mystery...
[Magisk] cubandanger05:
All my bank apps, wallet, work just fine since I updated to A14 and installed v8.6 🤷‍♂️

I'm yet to update to November's image
[Magisk] Flr Power:
V 8.6 what?
[Magisk] cubandanger05:
This module. I was saying I've been using v8.6 bcz it's been working (even though we're at 12.x at the moment).
[Magisk] cangurob:
Can someone direct me as to how to check the PIF Module logs in kernelSU install?

It's still not working for me, so would like to provide some more information, but not sure how to get it!
[Magisk] majorfigjam:
You just answered your own question.

Obviously your quick reboot app conflicts. Decide whether you want zygisk and Device Integity, or a quick reboot.
[Magisk] x_berzerker:
hey mates plz help!

enabling PIF breaks gmail (makes it insta close upon launch):

06-29 07:47:07.356 13926 13926 D AndroidRuntime: Shutting down VM

06-29 07:47:07.356 13926 13926 E AndroidRuntime: FATAL EXCEPTION: main

06-29 07:47:07.356 13926 13926 E AndroidRuntime: Process: com.google.android.gm, PID: 13926

06-29 07:47:07.356 13926 13926 E AndroidRuntime: java.lang.SecurityException: PackageVerificationRslt: debug cert rejected: pkg=com.google.android.gm, sha256=[1975b2f17177bc89a5dff31f9e64a6cae281a53dc1d1d59b1d147fe1c82afa00], atk=false, ver=242435039.true

disabling it back immediately fixes.

any help?
[Magisk] majorfigjam:
Not enough information.

Any number of other apps, magisk modules, lsposed modules could be causing conflicts.

My gmail runs without problems.
[Magisk] x_berzerker:
"debug cert rejected" and "disabling it back immediately fixes" really means more than what you see mate.
[Magisk] x_berzerker:
about the lack of info, what else could help?

i know my rom uses testkeys via unzip -l /system/etc/iforgot/some.zip

so maybe that is reason enough

also, i can't reach device integrity, only basic.

130|tdgsi_arm64_ab:/ $ unzip -l /system/etc/security/otacerts.zip

Archive: /system/etc/security/otacerts.zip

Length Date Time Name

--------- ---------- ----- ----

1675 2008-01-01 00:00 testkey.x509.pem

--------- -------

1675 1 file

tdgsi_arm64_ab:/ $ uname -r

5.10.168-android12-9-g5f01888e0e9e-ab15.0.004_240307
[Magisk] pershoot:
ROM will need to be signed with release / private.
[Magisk] majorfigjam:
What other modules may be interfering?

Have you tried disabling all other modules, lsposd etc, to see if conflict persists?
[Magisk] cmstlist:
Oh wow, thank you for highlighting that post... based on that my first try got me my RCS back!
[Magisk] badabing2003:
Seeing that this is making the rounds,

Let's give the credit where it is due.
[Magisk] linuxares:
Anyone got any tip how to extract the system.img to get the props?
[Magisk] cmstlist:
On Windows you can open it with 7zip.
[Magisk] Aregtheeditor:
Use 7zip
[Magisk] Devilix:
Yes, Deny List is disabled.

Yes, always red...

Google play store, Google Play Services, some apps and some games

I have not touch pif.json. I see it in this path: /data/adb/modules/playintegrityfix/pif.json

Sorry, i don't know this other custom pif about the format and where it must be placed

I did always before reboot after some test, cache and data.

Please, let me know if i mistake something, thanks a lot!
[Magisk] shoey63:
One his briefest ever posts, and up for the shortest amount of time, yet he still managed to let the cat out of the bag 😆
[Magisk] Wolfcity:
Some people have a strange kind of humor.

Don't be surprised if another 100 questions come up again......;)
[Magisk] xSnowLeopardx:
Still on 15.9.9 and it's working fine.
[Magisk] Aarif goku:
I came across some good online dumper.

You dump specific img from ota zip which contains payload just by url. Which I use for OnePlus sometimes.

GitHub: https://github.com/5ec1cff/payload-dumper

A online dumper based on that GitHub project

Payload Dumper Web

dumper.pedroz.eu.org
[Magisk] majorfigjam:
Sorry, I'm nearly out of ideas, tho' if you have a pif.json in playintegrityfix, that looks like you are or were using Osm0sis fork.

Try removing the play integrity module completely in magisk, disable all modules other than Shamiko, then delete the playintegrityfix folder. Reboot and reinstall Chiteroman latest.

Clear Play Services cache, and reboot
[Magisk] markdewet:
I can only assist with the one issue, you are using Osm0sis PIF fork by the looks of things and the pif.json in the path /data/adb/modules/playintegrityfix/pif.json SHOULD be custom.pif.json.
[Magisk] kholdstayr:
Here's my current situation, just sharing with everyone:

I'm using APatch.

I installed Chiteroman 16.5

After that, I was passing both device and had working RCS for about 5 hours. This was with the sailfish PIF. After about 5 hours RCS died.

Now I've acquired an Android 15 pixel PIF. I have working RCS again and device is passing still. I'm now waiting to see if RCS will continue working.
[Magisk] Devilix:
Yeah, after that post here i have try to install the fork of Osm0sis, but now i need to compile manually that file and i dont know where i can get a valid fingerprint...

Does not exist some app that does it in automatic way?
[Magisk] pershoot:
I presume you are on v9:

adb shell

su

cd /data/adb/modules/playintegrityfix

sh autopif.sh

This will pull the current public print (Xiaomi EU), put it in place (custom.pif.json) and kill GMS (killgms.sh), so it can re-init / re-spawn and have the new print available, for use.
[Magisk] Devilix:
Just see now, thanks a lot!

But, after generation of pif file, i need to reboot or i can just check with API Integrity app?
[Magisk] pershoot:
No reboot is required. You can use Play Store -> Developer to check Integrity.
[Magisk] Wolfcity:
If you use killgms.sh there's no need to reboot.

It's only necessary after flashing the module.
[Magisk] pershoot:
killgms.sh gets called after autopif.sh; it is not necessary to run it manually, after the fact, when executing autopif.sh.
[Magisk] Devilix:
But autopif.sh can be execute via Termux? Cause i have got a network error 😥
[Magisk] pershoot:
Make sure you have elevated yourself (su) and are executing: sh autopif.sh from: /data/adb/modules/playintegrityfix
[Magisk] Devilix:
Error: Play Store Termux not supported, use GitHub/F-Droid Termux!

I will try in one hour when i will be at home...better a pc in this case 😅
[Magisk] majorfigjam:
The Playstore version of Termux is broken - use a different terminal app, or go find the older a newer working version from Github or FDroid.

And to be blunt, this would all have been so much easier for you, if you had read and understood the first line of my initial advice:

"Read the OP and the linked FAQ, and the linked Osm0sis hints on solving integrity fails."

Every single one of your initial queries is clearly answered there.
[Magisk] x_berzerker:
ok just removed everything, instaled only zygisk, then pif, and same behavior: toggle on, gmail crash, toggle off, gmail works again. (and some other google stuff too)
[Magisk] majorfigjam:
Must be a peculiarity of your unsigned rom then - have you tried to contact the rom developer?

Do you even have a full Play Services environment in your rom?
[Magisk] pndwal:
Thanks... But since you're linking that now uninformative post, this for context:

😜 PW
[Magisk] x_berzerker:
it may be. gonna try contact but he will probably send me back here...

idk what "full Play Services environment" mean, but i can use any google app, install from play store, but Play Protect cert atests "Device not certified"
[Magisk] pndwal:
Further, for proper credit, I believe we actually first came by the info. via @osm0sis reporting a tip off from @hsmith1514... And I know you tested this too. 👍

And looking back, just another pearl for those w/ testkey signed ROMs, the allusions/clues may help you too... Much like "How to Recognise Different Types of Trees From Quite a Long Way Away"... 🤠 PW

- I'm sorry, I don't quite follow you.

- Follow me. Follow me. I like that. That's good. A nod's as good as a wink to a blind bat, eh?

- Are you trying to sell something?

-Selling, selling. Very good. Very good. Oh, wicked. Wicked. You're wicked. Eh? Know what I mean. Know what I mean? Nudge nudge. Know what I mean? Nudge nudge. Nudge nudge... Say...no...more.

- But...

- Oh...oh. Say no more, say no more. Say no more...
[Magisk] majorfigjam:
In the words of an earlier bard though,

"Tis better, sir, to be brief than tedious"

(William Shakespeare, Richard III)
[Magisk] pndwal:
But what, pray, does that contribute here, or valuable clue giveth? 😉🫡 PW
[Magisk] cmstlist:
It's certainly a bit of an odd loophole... my devices supports hardware-backed attestation, and I'm using a print from a beta ROM for the exact same device (although the device is not on the beta itself) and I have Device & Basic without Strong, and Pay & RCS are working. Highly unintuitive though because you'd think Google shouldn't grant it integrity without Strong.

I wonder if the reason for this is simply, Google's testing requires them to use these beta ROMs in environments where Strong doesn't always work properly, so they had to allow-list it to work without Strong. The corollary is that the fingerprints will probably no longer work once this OS version comes out of beta.
[Magisk] jakell888888888:
This is the best news I've seen recently. Finally a little hope, actually strong may not matter, just get my game verified and logged in,