yashsingh1/xdaforums huggingface dataset:
[Magisk] pr3dicament:
YASNAC isn't useful imo.. i use tb checker.. not that it matters cause I've been passing PIF from the start.. om0sis patch. I'm about to install the new prepbuilt.apk and then ill report what i have. Usually with what i currently have, i pass the two that need to be passed. I do not pass strong. I only have done that obviously on stock OOS.
[Magisk] pr3dicament:
I'm exhuasted. Jesus. I've been on one of my binges of attempting to get the current benefits that I have but plus the RCS.. I rarely use the phone but I need RCS for certain reasons.. Doesn't matter which reasons. I use AWall and you need root for that. I have many other things I install.. so.. I need root. Please don't mention stock either unless it's a guide to help me somehow lmao. Otherwise, just looks like I'm not doing well.
[Magisk] BillGoss:
I like to keep things simple. My minimum requirement is to have root access. And then, ideally, I want to have Wallet and RCS working. I'm a long time user of Magisk but I decided to try APatch as well.

From my testing here's what I found:

Magisk and using PIFork v9 (and no other modules):

- Sailfish fp: passes device integrity; Wallet works; RCS doesn't.

- Private fp: passes device integrity; Wallet works; RCS works.

APatch and no modules:

- Passes device integrity.

- Wallet doesn't work; RCS works.

Summary:

1. If you have a private fingerprint, Magisk + PIFork (and I assume PIF will be the same): you'll pass device integrity and have both Wallet and RCS working.

2. If you use Sailfish fp instead you'll get device integrity and Wallet working but not RCS.

3. If you use APatch (and no PIF(ork) module) you'll get device integrity and RCS working but no Wallet.
[Magisk] pershoot:
Some more data to add from my own testing on my own device:

Magisk w./ a FP (spoofed via PIF) that is not banned for RCS purposes and allows for a DEVICE verdict:

RCS is non-functional; Contactless / Wallet is functional

APatch w./ a FP (spoofed via PIF) that is not banned for RCS purposes and allows for a DEVICE verdict:

RCS is functional; Contactless / Wallet is functional

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] pndwal:
It is if you want to know if you device props/fields actually trigger HARDWARE_BACKED evaluationType enforcement for S/N API...

Of course, it's per API but PI API doesn't give any such clue... Still, if S/N HARDWARE_BACKED evaluationType is enforced w/o PIF, PI API will invariably be doing the same... If S/N is not enforcing it however, PI may or may not be.

Just trying to help...

At least that confirms scenario 2) for broken OnePlus above... Still, test for S/N evaluationType w/ no PIF/spoofing might be helpful. 🙃 PW
[Magisk] markdewet:
Apologies for the late reply. I hear and understand about the gen_pif_custom.sh command, I just am having a hard time finding a user-friendly terminal app to install on my phone, so let me ask this:

Will that command work if I am in TWRP and run it from the terminal app in TWRP?
[Magisk] majorfigjam:
Mate, I think you're over complicating this again. Think like a beginner, and don't try to blind him and everyone else with your undoubted grasp of the minute details.

He needs root, he uses Osm0sis fork, he has device integrity, what he needs is a private print to make RCS work - for as long as Google allows.

There are ways to point him in the right direction without going overboard with all the technical verbiage.
[Magisk] pershoot:
From a PC / Mac with the phone connected and booted in to the OS and running:

adb shell

su

cd /data/local/tmp

mkdir pif && cd pif

You can place file(s) in that area and work in there.
[Magisk] markdewet:
Appreciate the reply, however, the USB port on my phone is shot, so cannot connect to PC.
[Magisk] pershoot:
You can use ADB Wireless.
[Magisk] markdewet:
Really? How does one do that? I have never heard of using ADB wirelessly.

EDIT: Apologies, I will search for it, I do not want to be accused of requesting to be spoonfed. Thank you for your advice.
[Magisk] pndwal:
Thanks Bill!

This confirms that neither PIF fallback trigger nor target prop spoofing are needed for OP8T! (Guessing YASNAC naturally shows BASIC only for evaluationType.)

Questions: Did you have GMS DroidGuard (unstable) process in denylist (or APatch equivalent; I'm unfamiliar) for this?... And GMS core process (needed)?...

I suspect after clearing data or waiting (sometimes days) it would have started working however.

This means that you should not need PIF in Magisk either (and things will be much simpler if you can avoid it's spoofs)...

In theory, seems just hiding root from GMS and a solution (eg Shamiko) for sensitive prop adjustments is all you should need, however @osm0sis said that PIFork scripts-only mode doesn't work w/ Android 10+ in some cases on non-HKA-for-DroidGuard devices, so possibly more will be needed.

Have you tried just GMS DroidGuard (unstable) and core processes in denylist, w/ Shamiko active (and no PIF) with Magisk? Or PIFork in scripts-only mode?... And please say if ROM is not stock!

Thanks for tests! 👍 PW
[Magisk] pershoot:
How to connect to adb over wifi - PixelExperience Wiki

How to connect to adb over wifi - PixelExperience Wiki

wiki.pixelexperience.org
[Magisk] markdewet:
Thank you, however, I have one more question, I see I will need to activate developer options but I have read elsewhere that enabling developer options can break Google Wallet, which is currently working for me. Do you perhaps know if this is in fact the case or did I read wrong?
[Magisk] pershoot:
Developer options does not break wallet and is required when bootloader unlocking a (Pixel) device (which does break wallet; hence the need for PIF, hehe :) )

If you have (various) concerns for a non-vanilla manufactured phone, please perform some due diligence, w./ regards to this.
[Magisk] markdewet:
Oh, I do understand all this, I have an S8+ that is running a custom ROM (RisingOS), so I do fully understand the implications and necessity of using developer options.

So thank you for reassuring me about Wallet, that is my one and only concern with my current setup. RCS is not used in South Africa as much as elsewhere in the world, as far as I am aware anyway.
[Magisk] pndwal:
Nah. Just trying not to sell coal to Newcastle... Happening far too often here...

I just asked for YASNAC results to try to see if bypassing HARDWARE_BACKED enforcement was necessary in order to help further, but I didn't give any details... An explanation only became necessary because the member said 'YASNAC isn't useful imo'...

Anyway, @BillGoss has now answered my ping and confirmed the bypasses aren't needed anyway... Means OP8T can use native device props for both DEVICE_INTEGRITY and RCS... Spoofed PIF prints aren't needed...

No HKA (once unlocked) to bypass is no minute detail. It should fairly jump up and hit you in the face mate.

No he doesn't need a private print...

He has OP8T. That's what needs to be understood... Just a little technical understanding is needed. 👍

What verbage? 🤔 ☹️ ... Honestly, why not understand what goes on under the hood and not just drive the car?... And be sold a lot of accessories that you don't need and that actually wreck performance and break stuff??

Getting both RCS and DEVICE_INTEGRITY/ contactless to work with proper root hiding only will be FAR easier than finding a totally unnecessary 'unbanned print'...

Tip: PIF is for devices where DroidGuard is HKA capable, just like USNF was. 🤷 PW
[Magisk] pershoot:
If all you require is Wallet / contactless on a bootloader unlocked phone (w./ out RCS), you can do this:

Magisk (topjohnwu) + (PIF Fork v9 (osm0sis) + autopif (osm0sis)) or PIF 15.9.9 (chiteroman)

or

APatch (bmax121) + Zygisk Next (Dr-TSNG) + (PIF Fork v9 (osm0sis) + autopif (osm0sis)) or PIF 15.9.9 (chiteroman)
[Magisk] markdewet:
@pershoot Thank you, appreciate the advice, I do currently have Wallet working, including contactless payments, with Magisk + PIF Fork V9 and Shamiko.

I am not familiar with autopif, could you perhaps explain what this is used for, please?

Thank you
[Magisk] pershoot:
Autopif is a shell script which pulls down a (public) FP from Xiaomi EU, for use.
[Magisk] markdewet:
Ah, I see, that sounds like a great module, I will look into it, I am in the process of moving from RisingOS, which is unsigned to the latest unofficial LineageOS 21 for S8+, which IS now signed, so will definitely look into that. Thank you.
[Magisk] osm0sis:
What you want is TermOne Plus. Follow my setup instructions here:

[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

Not a module, it's built into my PIFork from v9 onward. Simply go execute it from a command prompt or a file explorer app that supports script execution and it'll do its thing. All this is covered in my PIFork README on GitHub by the way!

Not OT, it's spam. Report and move on. 👍
[Magisk] badabing2003:
PixelFlasher generates pif.json compatible with currently installed module, and places the file in the directory that the module requires.

Your statement suggests that you have the fork installed but want to have PIF generated and placed for Chiteroman's module.

If this is not the case, please generate support.zip file in PF and post it in PF thread.

No need to clutter this thread more than it already is, besides I might miss it here considering how much OT chatter goes on here, I often skip pages of comments just to get a pulse of current events.
[Magisk] majorfigjam:
You just reinforced my point! Like watching a Rob Sitch rerun in Utopia.
[Magisk] pershoot:
Since you are on PIF Fork V9, autopif is already contained in-path (along with killgms): /data/adb/modules/playintegrityfix
[Magisk] markdewet:
Yes, thank you, Osm0sis just also replied to me about this, I appreciate all the help. It really makes a difference when one gets assistance like this, being a noob and all. This is when things go right with modding, as then one knows EXACTLY what is what and which app/command/module/item is where.

This is much appreciated, guys, thank you again
[Magisk] halfbytecode:
As suggested above, you can simply use a file manager app, like MiXplorer which supports script execution.

You should place the corresponding build.prop files renamed as system-build.prop, product-build.prop, and vendor-build.prop in the same folder as gen_pif_custom.sh script, then select the script in MiXplorer and execute it from the three dot menu.

Upon successful execution, it should generate a custom.pif.json file in the same folder, which you can use with @osm0sis PIF Fork directly.
[Magisk] osm0sis:
Better to start with just the system one as build.prop and to follow the instructions in the script output from there, since some will only need build.prop (which is system), and vendor-build.prop.
[Magisk] markdewet:
Ok, I hear you guys, however, these .prop files, are you referring to the .prop files from a STOCK ROM? I have finally found a way to extract these files successfully, by the way.
[Magisk] Mitezuss:
was you asking about use the own "pif.json" from stock, right ? what was the reply ?
[Magisk] markdewet:
As above, there is NO pif.json in stock ROMS. My bad.
[Magisk] Mitezuss:
dude, your question was "pif from stock"

but i think, you were asking about "can do a PIF.JSON from MY STOCK BUILD.PROP (system and vendor)"

and pndwal was over complicating....
[Magisk] markdewet:
Yes, I was asking, but I was also confused initially, I honestly thought there was an actual pif.json file in a stock ROM, which there obviously is NOT. I DO understand now that one can create a pif.json from the build.prop
[Magisk] Mitezuss:
is working the PIF from your device ? (system props and vender props)

are you device unlocked ?
[Magisk] markdewet:
I am using a different pif.json, not one generated from the prop files.

I'm not sure what you mean by device unlocked? I am running a custom ROM, RisingOS, but going to be moving to another ROM soon.
[Magisk] Mitezuss:
hi, i have a questions, for clarify: for create a PIF.JSON to pass Basic and Device:

1. need props from a device with the bootloader locked ?

2. need a old device ? (2000-2018) or can be new ? (2022+) for extact a valid FP

3. can use my own FP from my device unlocked ? (2023, to pass basic and device) ?

4. fingerprint from new device: force hardware attention ? with the module we force basic or depend of the FP ?

5. can pass bassic with fingerprints from new devices unlocked ?

thanks

regards
[Magisk] osm0sis:
Just answered this in my own thread:

[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] shoey63:
Assuming gen_pif_custom.sh and prop files are in Download folder, in twrp terminal do -

cd /sdcard/Download

Then

sh gen_pif_custom.sh
[Magisk] markdewet:
Wonderful, thank you, sir. Luckily, in the S8+ ROM, once you extract the system.img, the file is already called build.prop:p

:p:p
[Magisk] markdewet:
AH, great, thank you, @shoey63. Should not be a problem to copy those two files to a folder on my SD Card, however, I will also look at MiXplorer, it looks like a great app and something I definitely could get used to using.
[Magisk] kholdstayr:
Is there a difference between using prop files embedded in the firmware ROM files vs using prop files that are in your system at runtime? I assume that they would be the same. The reason I'm asking is that I have a Moto phone, I have the firmware, but I've been unable to extract anything from the bin files.
[Magisk] LLStarks:
Valid keybox.xml according to PixelFlasher but still not passing STRONG. I don't get it.
[Magisk] osm0sis:
Don't use your own device's files.
[Magisk] BlackSoulxxx:
Based on my testing and someone in here, PIF 16.3 have some bug with keybox parsing or patching. Even if you have valid keybox, it will not work. Framework patch method is working.
[Magisk] LLStarks:
Ugh. That's a colossal pain in the ass to do manually.
[Magisk] majorfigjam:
And you likely never will, unless you lock your bootloader.

At this point, there is no viable way of spoofing strong. Google slammed that door within 24 hours.
[Magisk] halfbytecode:
@chiteroman mentioned successfully passing Strong Integrity using a private keybox on PIF v16.3.
[Magisk] pr3dicament:
Okay so I won't pass basic or device or i'd just not have access wallet? I have wallet disabled to begin with, i debloated it. Hate Wallet and Google's payment system. the one thing i dont care about is wallet, but if it says device is certified with RCS, i'm fine with it.

^ I'm speakng of APatch method btw, sorry, I didn't give clarification.
[Magisk] pndwal:
Well do need a leaked valid OEM keybox at least; apparently @chiteroman has one (haha)... Most are just 'sw' boxes it seems... 😜 PW
[Magisk] changhuapeng:
What valid keybox really means is that the certificates are valid and not listed in Google's revocation status list. The script doesn't check if the keybox are signed with Google root certificates so you could create and sign your own certificate chains and the script would probably still say valid.

Edit: Unless you got your hands on some rare unrevoked google-signed keybox, you will never pass strong integrity. The strong integrity we saw a few days ago was a mistake on Google's part and was not supposed to happen.
[Magisk] Lucius.sh:
There was a way few days ago that worked.

But Google patched it.

So "no viable way" is not true.

But how is the other question.

The current method is just certification spoofing with leaked keys.
[Magisk] pndwal:
Bill said he had DEVICE_INTEGRITY and RCS with APatch with no PIF installed... He'd also have Play Protect 'Device is certified' in that case. 😁

(For others, note that this is peculiar to OP8T with no DroidGuard compliant hardware key attestation when unlocked) 🤠 PW
[Magisk] pr3dicament:
No PIF at all installed? I've been told about 50 different things. I don't mind trying this Apatch method if it actually will give you RCS cause I dont give a crap about google wallet. i debloated that crap, frozen.

As long as the device is "certified" etc.. I don't care about McDonalds either or even banking aside from PayPal ot Cashapp. I don't bank on my phone. I don't pay with my phone, etc. You guys understand the point.

Also, tried @joeyhuab Pifprebuilt and it just says it conflicts with an already installed package.. Looked for it in "Apps" and could not find it. How do I actially remove this to reinstall?
[Magisk] Vision:
This is all we want.

But like Magisk sooner or later, Google can broke and the APatch.
[Magisk] ykjae:
What devices is TEE broken on other then oneplus? Is Honor one of them?

Sent from KB2003 using ReLabs
[Magisk] ThatOneGuyOverThere:
Where can one find working keybox.xml's?
[Magisk] pndwal:
So a bit further; the valid keybox must be leaked from OEM so attestation certificates are signed by the Google Hardware Attestation Root certificate... 'sw' keyboxes generally produce the same sort of attestation certificate but signed with a key hardcoded in Android source code. This signing key isn't a secret and the keybox supports only a software implementation of attestation, not hardware attestation. 👀 PW
[Magisk] Mitezuss:
dude... i said "for clarify"... (i read another post from you, but the english is not my language...)

so, can you reply yes or not to my items ? Thanks

your post only reply "3":

3. can not use my own FP

But, what about:

1. need be locked ? CAN/YES/NOT?

2. need be old ? CAN/YES/NOT?

4. new device force hardware attentions ? or basic with this module ? YES/NOT?

5. FP from new device (unlocked) can pass Bassic and Device ? YES/NOT?
[Magisk] changhuapeng:
Start a factory and apply to join Google certified partnership programme so you have your own keyboxes. Alternatively, you can also get them if you have a zero-day TEE exploit.
[Magisk] osm0sis:
Dude, "it's not for files from your own device, it's to be used on dumped files from another device's stock ROM to make a print you can use on your device" can't get much more clarified or concise...

1. No. Doesn't matter. Read the FAQ and the How-To Guide.

2. Yes and no. Read the How-To Guide.

3. No. As I just said several times. Read the How-To Guide.

4. Yes. Read the README.

5. What? Read the FAQ and the How-To Guide.

Start here, then follow links as you go. They'll point you to everything you are asking and could ever want to know:

PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com
[Magisk] pndwal:
Yeah, apparently not needed. As I said:

... He probably did have GMS DroidGuard (unstable) and core processes in denylist (or APatch equivalent; I'm unfamiliar) for this to work. (ie. Must hide root from GMS)

One thing I don't understand is how sensitive props were handled since he said no modules were installed... Guessing APatch has a proper hidelist?... (If not, I'd have thought at least Shamiko or some other solution would be needed.)

... Check my post for info on how a similar setup might work with Magisk. (Theoretically only.)

Happy testing! 🤠 PW
[Magisk] markdewet:
OK, just providing some feedback on my latest endeavor. Installed LineageOS 21 (A14) for S8+ (signed), installed NikGAPPS Omni, Magisk, PIF Fork V9 and Shamiko. Then also backed up and copied over my working custom.pif.json from my previous install and copied to

/data/adb/modules/playintegritfix.

So far, passing basic and device integrity in both TB Checker and Google Play Store developer options. Will check Google Wallet next as I first have to reinstall my banking app, then authorise the adding of the bank card in Google Wallet via the banking app.

Will update once Wallet is tested on Monday.

Thanks a bunch to all that assisted and especially to all the developers who create these wonderful apps and modules for us so that older decent phones can carry on functioning.

My ONLY pipe-dream is that I could SOMEHOW get Samsung apps to work with this ROM, but hey, cain't have everything!!! LOL
[Magisk] Aarif goku:
It's broken for Most Moto just like OnePlus and some Samsung as well and In OnePlus case it seems not just OnePlus but OPPO, Techno and few other common brands from BBK.

I do have a Vivo V15 which is old with a working TEE it passed Strong integrity few days ago due the exploit which Google patched so I need to find valid keybox it seems.

For Moto in my case unlocking breaks TEE and locking fixes it with strong integrity on stock rom.
[Magisk] tvall:
if anyone has a valid keybox, ill trade you my private pokemon go plus secrets file. not quite a fair trade, but autocatchers are fun
[Magisk] BlackSoulxxx:
To make keybox working with PIF, you need to change DEVICE_INITIAL_SDK_INIT to 30 in PIF.json. Doing so will enable hw attestation AFAIK, but it will break stuffs for those without valid keybox. So only modify when you have actual valid working keybox.

View attachment 6116217
[Magisk] BlackSoulxxx:
Another test device

View attachment 6116225
[Magisk] LLStarks:
How do I force hw for husky? Always wants to do basic.
[Magisk] Aarif goku:
Both using same keyboxes with their original (device's own) props?
[Magisk] RAZINARES:
Does valid keyboxes allow you to pass integrity with any device fp or just oem specific devices fp?

Sent from Pixel 7a using ReLabs
[Magisk] BlackSoulxxx:
Yes, pass strong with any fp that passed Device
[Magisk] devaponnadsm:
So you have a valid keybox now?
[Magisk] BlackSoulxxx:
I have triple digit amount of valid keyboxes :cowboy:
[Magisk] pershoot:
[DEV] APatch - an alternative root solution to KernelSU and Magisk

The patching of Android kernel and Android system. A new Kernel-based root solution for Android devices. APM: Magisk module like support KPM: Kernel Patch Module support. (Allow you to inject any code into the kernel, Kernel function...

xdaforums.com

@aliantonio While that particular user is using PIF to spoof (an older FP), in your case, attempting to hide it (APatch / related) from RCS / related at a deeper level via Cherish peekaboo, may sort you out, when Lsposed (mod) is in use (as is the case with that particular user).
[Magisk] BlackSoulxxx:
You gotta do what you gotta do ;)

Anyway someone need to find another profile because sailfish aint cut it with RCS. RCS broken even with strong.
[Magisk] joeyhuab:
Wanna trade a keybox for a working RCS print? 😂 I joke but would be cool tbh to test even just one of those.
[Magisk] mwzdalne:
Lich rom: tg group a54 developer