yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
No idea what you want with that, or why you're trying....

PIF should just work with that, but may break RCS per discussion here...

But you may not really need PIF anyway on your pre-hardware-key-complaint device (no fallback to basic needed, no serverside HARDWARE_BACKED evaluationType enforcement bypass needed), and there's less issues not Spoofing prints of course (eg RCS may work if device itself is compliant). Edit: Actually, device props/fields may not work w/ A10+ ROM apparently...

If you want to try however, you could try removing PIF and just add GMS DroidGuard (unstable) and GMS core processes in denylist (to hide root), don't enforce that and use Shamiko (for sensitive props). If it's official LineageOS it won't adjust security patch date for A14 base and, as ROM probably embeds 2022 fingerprint, you'll need to correct that, eg install MagiskHide Props Config and use terminal emulator to configure it with an S8+ fingerprint from its list... Alternatively, @osm0sis' PIF fork in scripts-only mode (adds GMS DroidGuard (unstable) process in denylist automatically; check and add the core process too as may be needed with A11+) with the MHPC fix above could also work...

Because there isn't one is there? 🤔😜 PW
[Magisk] badabing2003:
🔧 [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] markdewet:
OK, will reply in order:

I thought I needed the build.prop in order to create a pif.json, but turns out that is a waste of time, as per my edit posted above.

As far as the ROM, is is NOT an official ROM, it's built by a member here on XDA (ivan_Meler).

re " install MagiskHide Props Config and use terminal emulator to configure it with an S8+ fingerprint from its list", apologies, but this is WAY over my head, so I really do not understand what this is trying to tell me.

Re "Because there isn't one is there? 🤔😜 PW", actually there is, but for A7, not A9, and besides, how can there NOT be one, if you tell me above and I quote "i

install MagiskHide Props Config and use terminal emulator to configure it with an S8+ fingerprint". So either the ARE fingerprints for S8+ or there ARE NOT.

With all due thanks and respect, your reply is a PERFECT example of why us noobs get totally confused and ask dumb questions over and over. I personally appreciate any response from the more experienced members here, but as I do not even understand the references, it really is frustrating to try to implement.

I suppose I will start at the top and search for Magisk Props Config, then take it from there.

OH, and the same with "PIF fork in scripts-only mode".

Thank you again for your response, @pndwal it really is appreciated, if not understood.
[Magisk] sawdoctor:
I'm not 💯 certain what you are trying to do and I'm certainly not the most knowledgeable person. But I'll try and give you some helpful points.

Out of the 100,000+ Build props/fingerprints out there on the internet there are less than 100 that actually pass device integrity so the chances of the fingerprints your are downloading passing device integrity are almost zero.

Most people are using the fingerprint included in chiteroman pif module as it's one of the few left passing device integrity. Unfortunately with that print RCS chat is broken but you can still use Google wallet
[Magisk] markdewet:
@sawdoctor Thank you, yes, I am aware that most fingerprints are dead, I was simply really thinking out loud as to why one could NOT use a fingerprint from the original stock ROM of a device, in my case the S8+, however, as I found out from the droidwin.com website, that is also an effort in futility. So I will stick with the fingerprint file that I am currently using as it definitely works for me.

As regards RCS, that for me is not an issue, hardly anyone uses it here in South Africa. Wallet is far more important to me.

Your recommendation of using chiteroman's PIF module is another case of confusion, as I see most here recommend Osm0sis' PIF fork, which is what I am using currently. Are you now saying I should instead use chiteroman's? If so, may I ask why?

Just as an aside, @pndwal from the MagiskHide Props Confg XDA thread "Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again." :unsure:

:unsure::unsure:
[Magisk] pndwal:
Still works fine where only global (not targeted) prop configuration is required... PW
[Magisk] markdewet:
OK, thank you.
[Magisk] pndwal:
So may (possibly) have security patch adjusted already...

Use it if fail due to mismatched security patch and fingerprint... Of course you'll need to read usage yourself...

As I bolded in your own reply (above)... MagiskHide Props Config. 😜

There's no "pif.json from the stock ROM"... Sorry, that's just wrong.

Of course there are fingerprint props. And fields... But you said 'pif.json'.

Tried my best, and you said you didn't want 'spoon-feeding'... My reply was accurate, but your questions were pretty confusing/confused, hope you see that...

🤷

👍 PW
[Magisk] markdewet:
My apologies, I actually did not know there is no pif.json in stock ROMS!!! LOL, learnt something new today.

EDIT: Well, DUH, of course there would not be a pif.json in a stock ROM, pif is Play Integrity Fix!!! Sheesh, sometimes the obvious will just slap you!!!!

Yes I do see that my questions can be confusing, I do not always know how to express myself in a way that will make sense to the experts. Is can be frustrating, however, I am getting there.

Re what MHPC stands for, yes I realised that and deleted my line in my reply, but you beat me to it evidently!!! LOL
[Magisk] Toasty1Too:
As poorly as Google(Android) and Apple treat their customers, I'm ready to find a new provider for a smartphone OS.

At this point, it's either simply abandon both companies completely, or maintain three separate phones to be able to do things any customer should be able to do with their device. Ostensibly, I own my phone, but it sure doesn't feel like it when Google comes along and starts disabling features remotely.

Seems the industry has lost it's collective mind, but I guess that's what we get when corporations control everything good.

Still, I'm glad this community exists. Things have been better because of all of you, than they would've been otherwise.

TL;DR: I tried this fix to get RCS working again on my phone, and it still doesn't. Is there really no other service provider making a good messaging application that can fallback to SMS when it's end-to-end encrypted messages can't get through due to connectivity problems?
[Magisk] Nergal di Cuthah:
From whom, right now there isn't really a third player. Everyone ignored WebOS, which encouraged "rooting" and complete customization.
[Magisk] BlackSoulxxx:
I have a working keybox (check via PixelFlasher) and put in correct folder (data/adb/keybox.xml). However it still not have Strong. Does that mean my phone have broken TEE, or something else broken? (Xiaomi 12S Ultra and 14 Ultra, stock fw)
[Magisk] Kiaraoki:
(Noob question)

What this means? I literally just rooted and installed PIF + LSposed

View attachment 6115916
[Magisk] aliantonio:
Still breaks RCS for me. Interesting. Stock pixel 7
[Magisk] pershoot:
I have been running that for more then 24 hours now, with functioning RCS, on lynx.
[Magisk] aliantonio:
It's possible I'm doing something wrong.
[Magisk] Vision:
Broken TEE 😔
[Magisk] Vision:
Without the module, what key attestation show?
[Magisk] Kiaraoki:
How this affect to me and it has fix? I'm on stock OS using Magisk without Custom Recovery
[Magisk] Vision:
Accordingly, if you want to relock BL can't pass, I think only basic, and @chiteroman know and say thisView attachment 6115925
[Magisk] Kiaraoki:
English Is not my main lang, do you mean I can't relock de BL anymore?
[Magisk] BlackSoulxxx:
With PIF 16.3 (+working keybox) or without module (disabled in KSU), its the same, really. This is 12SU with PIF disabled (on 14U the same, except 14U have keymint v3 strongbox instead)

View attachment 6115934
[Magisk] Vision:
Yeah, as I understand, the key attestation with PIF v16.3 not change, but with PIF.json and working keybox together, can get the desired results.

EDIT: Because is about keybox, if you feel more comfortable, you can PM me.
[Magisk] osm0sis:
No, you'll be fine.
[Magisk] Vision:
I write my answer according to this.

View attachment 6115937
[Magisk] chiteroman:
You can lock bootloader but the device won't pass Device neither Strong verdicts anymore.
[Magisk] Vision:
So, my answer is right.

Only basic, and is meaningless to relock BL.
[Magisk] osm0sis:
Not necessarily. A user reprogramming and breaking their TEE is completely different from OnePlus' broken TEE from the factory.
[Magisk] BlackSoulxxx:
So i need a matching fingerprint (PIF.json) correspond to the keybox to have it working? Or just need working keybox (+default PIF.json) and should have strong?
[Magisk] pershoot:
What is your configuration?
[Magisk] markdewet:
Really sorry to be lazy, guys, but can someone PLEASE post the link to the website where you can paste build.prop details and it gives you a pif.json file? It was created by Osm0sis, I think. I have tried searching for it, but doing something wrong.

Thank you
[Magisk] Vision:
The first part is discussion and second part yeah this is enough I think.

Oh sorry, I did not know that, my mistake.

By @chiteroman

PIF json from build.prop file
[Magisk] Kiaraoki:
What is persist partition? I just flashed boot.img
[Magisk] markdewet:
Ah Thank you, sir!!! You are a star!!

And apologies to @chiteroman for crediting the wrong creator of the website.
[Magisk] chiteroman:
It doesn't work well because most of the props on newer devices are in vendor.prop

It's better to create the pif.json manually
[Magisk] chiteroman:
If you are using OnePlus that's normal, it will brick when unlocking bootloader, I don't know if it will restore to normal state when you lock it again.
[Magisk] Kiaraoki:
It's a motorola edge 20 pro
[Magisk] BlackSoulxxx:
View attachment 6115943

Seems like having a working keybox is not enough? per the man said. need both strongbox and normal keybox then?

View attachment 6115946
[Magisk] Vision:
Simple explanationView attachment 6115945

So after flash boot.img, key attestation show this?

For that I say you, PM me, if you have StrongBox is useless.
[Magisk] Kiaraoki:
I mean, I just flashed patched boot.img from Magisk, I don't know if the key attestation broke when I unlocked bootloader
[Magisk] Vision:
Yeah understand.

@chiteroman answer about this.

🔧 [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] Syoenth:
How do I check the keybox on Pixelflasher?
[Magisk] Vision:
View attachment 6115959
[Magisk] osm0sis:
Or my gen_pif_custom.sh has been working pretty well since we first started all this pif.prop/json fun! Just updated it again last week! 🤓

[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] Syoenth:
How can I extract my device keybox? I think my TEE isn't broken
[Magisk] alekyiv:
Have question if i extract payload.bin and take keymaster.img from stock firmware of my Redmi Note 11, after flash this the phone dont need use bootloader spoofer for spoof fake keys other devices?
[Magisk] Kiaraoki:
So there's a probability to relock BL and TEE just repair itself?
[Magisk] aliantonio:
Stock pixel 7. Apatch root. Only modules installed are zygisk next, zygisk assistant, and systemless hosts. Everything else breaks RCS for me. Not sure what I'm missing. Nothing hidden in apatch too.
[Magisk] pershoot:
Are you on the latest APatch and Zygisk Next? Are you passing a BASIC verdict pre and post activation of Lsposed (mod)?
[Magisk] majorfigjam:
Which print are you using?
[Magisk] pershoot:
The actual device (panther); PIF is not installed.
[Magisk] osm0sis:
Go back to PIF 15.9.9 or try my fork and see if it looks any better.
[Magisk] Kiaraoki:
I finally decided to relock Bootloader, and TEE repaired!
[Magisk] osm0sis:
Yeah, it was never broken. Just 16.3 making it show weird for some reason
[Magisk] aliantonio:
I wasn't on latest zygisk next so I updated and still does not work. RCS breaks after a few minutes. No modules activated in lsposed. And passing basic pre and post activation of lsposed.
[Magisk] dimm0k:
I do not... also do not have LSPosed
[Magisk] Haxival:
Hello people, I'm using an OnePlus 6 running OOS 10.3.11 (still on Android 10)

I've recently updated to Magisk 26.4

It's been causing all sorts of issues all around....

First my device has started soft bootlooping.

No biggie, it was the old safetynet (v2.4.0 by kdrag0n) module causing it.

Now I switched to this module and although my devices passes both basic integrity and CTS (with the old module it only passed basic integrity) the only two apps that detect root on my device will still recognize it when they worked fine in Magisk 26.1 with said safetynet module.

What should I do? Should I roll back everything and give up updating Magisk ever again?

NVM DENYLIST WAS SET UP BUT NOT TURNED ON AS AN OPTION. GREAT SUCCESS
[Magisk] HippoMan:
Another way that the Googlefrinchians could have handled this case is to provide for some kind of Android sandboxed app environment. Any apps running in this environment would be subject to all the integrity checks and rooting/modding-detection facilities that could be implemented. Apps running outside of this sandbox would be free to do whatever they want.

A facility could have been offered for signing and submitting "protected" apps to the Play Store, and such apps would always run in this proposed sandbox. Then, developers could write "banking" apps which would run in this isolated sandbox in the way that they currently run in a non-modded environment today -- i.e., without requiring the entire Android device to be crippled.

But of course, nothing like this ever occurred, and so again, we're stuck in this world of continuing Android deterioration.
[Magisk] EuK_V:
I can also confirm this app is working fine with magisk here:

View attachment 6031542
[Magisk] marcopit-92:
It might be different setup then. the other guy who was using had no LSPOSED, another member was using a different version of magisk.. I will stick to the older build
[Magisk] EuK_V:
I'm on LOS 20, Magisk 26.3, with only module pif v12
[Magisk] sawdoctor:
The problem is this would require time and effort by Google and the modding community is so small they really don't care. We as users pretty much have 2 options android with some customisation or iOS with none whatsoever. As long as it remains a duopoly why would Google put the time and effort in
[Magisk] HippoMan:
I'm not suggesting that the Googlefrinchians add any such functionality now to Android. It's way too late for anything like that.

I'm just lamenting that they never offered such capabilities in the first place.

Also, given the small size of the Android modding community, it's ironic that banks and other developers put out so much effort to "protect" us against a rooted/modded Android environment while doing absolutely nothing to "protect" us against desktop OS's (Windows, MacOS, and Linux) which are all rooted and all easily and readily modded, and which are utilized by a much greater number of users than those who use rooted/modded Android devices.
[Magisk] aygul12345:
Thanks for this!
[Magisk] RosarioDV:
So it seems like device integrity is now passing on xiaomi.eu without Magisk. But with Magisk it doesn't.

Can anyone confirm whether that is the case? Thanks to the developer! I wish xiaomi.eu wasn't incompatible with this module
[Magisk] aygul12345:
Thabks
[Magisk] aygul12345:
Did you pass safetynet by this config?
[Magisk] aygul12345:
Thanks
[Magisk] K0rgar:
I'm using the latest stable Xiaomi.eu for poco x3 NFC with this setup:

- magisk 26.4, hidden apk.

- pif 12.2

- shamiko

- enforce deny list off

- deny list populated by banking apps only.

- deleted app data of Google play services, Google play store, wallet.

Did one reboot, still wasn't certified for at least 2 hours then I checked wallet and it was fine to add cards.

Deleted again play store data and checked if I was certified and the pif response under developer options (the labels should say device integrity and another that I don't remember)

Still didn't try to pay.
[Magisk] chiteroman:
Don't use PIF in custom ROMs which inbuild the fix...
[Magisk] K0rgar:
I had only magisk 26.4 and the updated rom but I always failed the integrity checks.

Maybe I should've waited some time and having pif installed acted like a placebo effect...

Do you suggest to remove it and the same for shamiko?

I should test more.
[Magisk] K0rgar:
Tested without PIF, all the remaining setup is the same.

Integrity FAILED...

I'm on xiaomi.eu for poco x3 NFC, latest stable.

Will revert back to see if I will be certified again.

Edit: installed pif, did reboot and checked integrity inside play store, 2 labels populated and wallet doesn't complain.

Maybe the latest xiaomi should work fine without magisk else we had to rely to this module (and maybe to shamiko, dunno really)
[Magisk] digger16309:
No, actually, it is version 10.22.4 on TJW Magisk 26.4.
[Magisk] Catfriend1:
Magsik 26.4

Shamiko latest version

Latest xiaomi.eu beta (Android 13)

Xiaomi mi13 phone

- version 12.3 has three red X and does not pass anything

I've reverted to 12 release and pass nothing

I've reverted to your 9.9 release and then only pass basic_integrity.

I've reverted to 9.2 and pass basic only.

I've reverted to 8.7 and pass basic only.

#

my other phone , mi8, works fine using 12.3, same configuration regarding Magsik, Shamiko etc.
[Magisk] Reynald0:
12.3 lsposed crash, reverted to 12.2
[Magisk] majorfigjam:
OK the default Integrity behaviour on an unlocked Pixel seems to be:

Locked bootloader - Strong

Unlocked - initial status - Basic only

Rooted with Magisk - None

With PIF v9 and no custom.pif.json - Basic only

With PIF v9 and known working custom.pif.json - Basic and Device

So, without PIF on an unlocked Pixel, the best you can get is Basic. To get Wallet and RCS, you need a print other than Sailfish.
[Magisk] pershoot:
Please try Cherish peekaboo alongside Lsposed mod and then observe.

If not, please submit an issue and liaise with mywalkb to see if there are any further thoughts, regarding this.
[Magisk] aliantonio:
I gotta read up on how to install that module. I'm guessing that's a KPModule and I'm not totally clear on how to install it, I'm new to apatch. I'll look at it tomorrow. Thanks for the suggestion
[Magisk] flyoffacliff:
I am having a very difficult time getting a custom fingerprint.

I am trying to do this on my Pixel 5 using the gen_pif_custom.sh script.

There is no product props file, so I used the vendor one in place of it, and the gen_pif_custom.sh script gave an error "No fingerprint found, unable to continue".

Is there a workaround or another working method to make a custom fingerprint that will work on my Pixel 5 and support RCS?
[Magisk] geokilla:
I dirty flashed via ADB sideload and it mostly worked. I say mostly because android setup constantly runs in the background under "active apps". Adaptive Connectivity Services keeps stopping as well when I restart my phone.

Anyways to get back on topic, I pass integrity now and I can update my apps on Google Play again. Thanks for the help :)
[Magisk] majorfigjam:
What device are you building the print from? If it's the Pixel 5 then:

The product build prop is usually in the product \etc folder; but​

It's not very likely that the device print will work in the way you're hoping.​

​

There have been quite a few hints over the last 10 pages or so as to where you can find devices and source zip files that will produce working prints.
[Magisk] pershoot:
From an image:

(system) /system/build.prop -> system-build.prop

(vendor) /vendor/build.prop -> vendor-build.prop

(product) /product/etc/build.prop -> product-build.prop

sh gen_pif_custom.sh -> custom.pif.json
[Magisk] manjaroid:
Try giving the script empty files for product or vendor if a ROM doesn't have them. In some cases you may need to provide all three.

product-build.prop

system-build.prop

vendor-build.prop
[Magisk] Stillhard:
If that's mean broken tee, how to explain mine here?
[Magisk] Vision:
Unfortunately can't.

View attachment 6115988

That's is good 👍

And good to know can repair itself.

Read the above comment.

Eventually maybe TEE repair itself.
[Magisk] pndwal:
Sort-of unbroken... 🙃 PW
[Magisk] Scholeggo:
Hey man. I meant to ask: on pixel flasher, is there any way to make it compatible with @chiteroman's pif? Every time i use his module and apply a fp from my pc, it always ends up in data/local/tmp instead of data/adb/modules/playintegrityfix where it's supposed to go (and where it does go so long as i only use @osm0sis fork)
[Magisk] pr3dicament:
I hate OnePlus.. ;/ It can get really bad. *sigh* But if we can do this via LSPosed with cherish peekaboo or whatever it is called, you'd still need a private print, correct ? Or am I missing something? I'm using @osm0sis module at the moment and I know it's not good to mix multiple modules together. I hope I can get this working just for the hell of it at this point, that is, If you can spoof an unlocked bootloader, then wouldn't it be possible to just bypass the FP with no FP, including removing sailfish and achieve RCS possibly? I'm trying to just... troubleshoot and figure out suggesstions about it. Sorry if this seems like I'm asking for help, I'm just making sure about whether or not I'd need a private print because if I do, then I'm not going to waste any time as I don't have one available. So I'm a little confused. Could anyone clear this up?
[Magisk] pr3dicament:
Couldn't you just move it manually? I'm not comin' at you by the way, I am sorta lost at this point.. just trying to get some stuff to work but.. not as desperate as I once was.
[Magisk] pndwal:
OP8T?... So you have DEVICE_INTEGRITY with PIF ATM?... Think that's scenario 2 TEE breakage in my post above (have STRONG when locked)... Please say/show what you get in Key Attestation app, and with PIF disabled, what you get in both YASNAC and in a PI checker...

Further, I think @BillGoss is a OP8T guru... He may know if print spoofing is necessary or not...

🤠 PW
[Magisk] mwzdalne:
Idk i looked and I'm completely lost. Wallet works, RCS says connected but sends via sms, it can reconnect if i deregister but idk, i'm completely lost in this thread.
[Magisk] pndwal:
SM-A546B is Samsung Galaxy A54 5G, but screenshot shows SM-S711B, Samsung Galaxy S23 FE... Are you running MHPC?... Other global spoofing module?... 🤔 PW
[Magisk] majorfigjam:
Unfortunately, as pershoot said, you have reached as far as you can go on your journey with Sailfish as your spoofed fingerprint. You have device integrity, a working wallet, and RCS connected but not functional. That is more than many others have achieved, so congratulate yourself for getting this far.

The way forward, in the short term, is to follow the clear and helpful hints scattered liberally in only the last two days worth of posts, make the necessary inference, and then create your working "private" print.

In the long run, who knows. Google - as they showed with the closing of the "Strong" loophole a few days ago - can move very quickly if they want to close all this down.