yashsingh1/xdaforums huggingface dataset:
[Magisk] chiteroman:
You can create one, but will be useless because certificates must be signed with Google private keys.

If you want to pass Strong, you should search for a leaked one :p
[Magisk] kholdstayr:
Thanks, just tried it. Using with APatch and Zygisk Next. Device passes, but not RCS. This is just using the default PIF that comes with this version.
[Magisk] Aman Dewett:
If I don't use LsPosed then how will my use "Hide my Applist" app, which is required to hide magisk and other root apps.
[Magisk] mattburga1984:
Same thing is happening to me after flashing STRONG 16.2 PIF. I reverted back to 15.9.9 and it didn't work.

Cleared app data / storage. Uninstalled and reinstalled. Installed the 16.3 PIF. It is still not working. I get the same error. Oddly enough, Tangerine app is working fine.
[Magisk] Syoenth:
I want to use my device keybox
[Magisk] Aman Dewett:
Hah, finally someone with the same issue, I thought I am the only one whose ScotiaBank app is not working anymore after v16.2
[Magisk] Aman Dewett:
@chiteroman bruv, do you have any idea, why it is happening?
[Magisk] K1nsey6:
My husbands phone didnt have Lsposed installed and he still lost RCS
[Magisk] chiteroman:
This thread isn't for this... But maybe it's Zygisk detection.
[Magisk] chiteroman:
Found Android 15 fingerprint passing Device 😂
[Magisk] LLStarks:
The latest I've observed is that the full print is needed. Extra props and everything apparently.
[Magisk] LLStarks:
I wonder if we're talking about the same thing.
[Magisk] passionicon:
On behalf of all noobs, Any thread/faq to understand what keybox is🫣?
[Magisk] crypticc:
I don't mean for banning prints on "Real" devices.

I mean to find devices by linking IP address used when obtaining certification, and linking that to submitted diagnostics that includes unknown app and other system information. Put another way, if they're not using it to "improve android" it would really surprise me.
[Magisk] Aman Dewett:
@chiteroman sorry, where can I ask this question? App was working until yesterday's evening but once I installed v16.2 it stopped working and no matter if I use v15.9.9 or clear cache, data or reinstall the app. It did not work after.
[Magisk] crypticc:
I hide Magisk by renaming it (don't rename as default "system" as I know my bank app detected that...saw in logs way back

And then once I've done that I use Icebox to alternatively hide Magisk and root apps, or to keep bank apps suspended when I've unhidden the root apps.
[Magisk] crypticc:
The telegram channel for unofficial Magisk has chit chat on issues with specific apps.
[Magisk] Aman Dewett:
But now I have no idea how to make scotiabank app work. I really need it for daily chores.
[Magisk] crypticc:
PMd
[Magisk] Scholeggo:
(Deleted)
[Magisk] Aman Dewett:
PMD?
[Magisk] Nergal di Cuthah:
They mean they sent you a private message
[Magisk] mattburga1984:
I'm having the same issue as Aman.
[Magisk] Aman Dewett:
I see, thanks
[Magisk] pndwal:
Ok... (I tried to be as clear as possible; even the part you responded to clearly stated 'Since device 'prints' apparently worked for the STRONG verdict/attestation only with KSU LKM or APatch...' But I know people are skimming here due to the volume of posts. 😉)

Less 'overloaded' version (?): Point is, the STRONG episode still didn't seem to allow use of 'banned' prints for Magisk users, but there was no such restriction for KSU (LKM mode) or APatch users... Reasonably, this may only have become apparent as device prints could be used (since they support hardware backed attestation anyway). For KSU/APatch users to be aware that their setup bypasses the 'bans' for use of spoofed prints to allow passing DEVICE verdict w/ basic-only attestation, they'd need to test specifically by spoofing prints from devices that didn't launch with DroidGuard spec HKA (ie. Keymaster 3+, either OnePlus etc or those launched with Android 7 or earlier), ie. they'd need to set JSON with such a print to test.

Not sure I did get it less 'overloaded', but re-wording may make it clearer for all(?)...

This may possibly be an important test; It seemed to me that discovering the reason for differences between Google treatment of prop/field sets used for HKA verdict enforcement in SU-in-kernel and SU-in-ramdisk solutions may help a lot in understanding the 'print ban' mechanism.

🤠 PW
[Magisk] Stillhard:
@chiteroman

View attachment 6115595

PIF v16.3

View attachment 6115594

BootloaderSpoofer /w "sw"

in the same device, means 'broken tee' is fixable...
[Magisk] LLStarks:
Husky print: Pass device

Marlin print: Fail device
[Magisk] ThatOneGuyOverThere:
where can one find these leaked keybox.xml s. I found 3 on tadiphone but they all don't work.
[Magisk] BillGoss:
I'm interested in how you've got your phone to pass device integrity.

I'm also on husky. I used @osm0sis's gen_pif_custom.sh to create the pif.json file using the system, vendor, and product build.prop files.

I'm running APatch, with @chiteroman's 16.3 PIF and replaced its pif.json file contents with my husky version, but I changed the DEVICE_INITIAL_SDK_INT value from 34 to 24.

Now I'm only passing basic integrity.

What did you do differently?
[Magisk] majorfigjam:
Given the ongoing problems with RCS and Sailfish, and now prints passing Device that should not do so* , and forgetting all about the recent Strong loophole that Google closed so quickly, it will be intriguing to see what 29 June will bring.

*based on all our previous understandings about initial api levels, and not being able to spoof with your own device's fingerprint.
[Magisk] osm0sis:
From our testing it's only a beta print that seems to allow the original api_level (>25). 🤔

If you read back to Monday and Tuesday you'll see me alluding to them and them being special. 😛
[Magisk] Scholeggo:
Did you use pif from @chiteroman or @osm0sis?

I'm trying it now and I do indeed get device, but rcs hasn't come back yet
[Magisk] LLStarks:
chiteroman
[Magisk] tryigitx:
Once the BL is unlocked, the certificate is completely invalid.

You must unlock the BL lock before you can see the system files and do a rom dump.

So the main reason why this is Strong is because the only way to find out is through leaks from the manufacturers .d

Of course, the most difficult method is to bypass the TEE algorithm when your own phone is locked, i.e. to hack it (💀 if your phone has a tee security chip)

You can buy paid keyboxs on some forums or you can search for them. Make sure they are not banned and delete anything other than release-keys in the pif.json file.

Old fingerprint and low api level bypass the hardware backed method. So you can't pass strong.

I don't know why @chiteroman didn't mention this, if there is a keybox file only release-keys can be spoofed and pif.json can be bypassed. Something like this could also make sense but I'd rather be informed.
[Magisk] Scholeggo:
Well now that you've said it here, I gotta keep a closer eye on when they'll be banned too
[Magisk] Scholeggo:
Interesting.. what about rcs?
[Magisk] osm0sis:
What are you talking about? Like 5 people mentioned the beta today. Cat's obviously out of the bag.

But yeah, I wouldn't expect them to last forever.
[Magisk] Lucius.sh:
Buying a keybox... you really need a lot of trust on the seller before you do that because also this key can get leaked to the public.

But soon or later its the only way to pass Play Integrity exept someone find a completely new way to bypass this. :rolleyes:
[Magisk] LLStarks:
I don't set DEVICE_INITIAL_SDK_INT
[Magisk] Scholeggo:
I'm just catching up and I skimmed most messages, so if anyone else other than @LLStarks mentioned it, I missed it.

(Redacted)
[Magisk] tryigitx:
However, it is always best to use the device's own fingerprint.

There's a chance you'll fail the Strong test because of the fingerprints (device model etc).

By the way, I hope Google doesn't make a fingerprint/prop and keybox matching algorithm in the future 💀

It already check some props, but not device-specific ones.

This is possible because it is like random number derivation programs (Code generate programs etc)
[Magisk] osm0sis:
LLStarks, pershoot, joeyhuab, RAZINARES, chiteroman. 😵😛

I'm not going to speculate, we'll see how long the prints last. Stable is coming. 😉
[Magisk] passionicon:
these names are legendary
[Magisk] mac796:
So are none of the other private prints working for RCS? Just curious?
[Magisk] LLStarks:
It's not really private. And short of testing a bunch of stable, QPR, 15 beta, etc build.prop pifs from a number of Pixel devices, I'm not sure. I can only imagine that once I start mismatching or missing props, CTS will start failing.
[Magisk] mac796:
Yeah I understand They're not private lol I searched through over a hundred of them yesterday. everyone's talking about the one I found. I think lots of us found it
[Magisk] ThatOneGuyOverThere:
Can I dump a working keybox.bin from another phone?
[Magisk] Scholeggo:
Now that print, pray to God it's not the same one I'm using, has a likelihood of getting banned much sooner than later
[Magisk] joeyhuab:
My bad, could try now. But either way, will try future prints from future devices too soon
[Magisk] K1nsey6:
The person I was replying to was claiming it was Lsposed tripping RCS, I was replying it was not the case
[Magisk] Aregtheeditor:
RCS doesn't work again with 16.3 :<
[Magisk] Vision:
So with v16.3 can add keybox.xml and PIF.json in /data/adb.

The key attestation must show the same as before? BL is unlocked? 🤔
[Magisk] vygavedha:
Do plz share if you found anything
[Magisk] mac796:
If it's the one that's been mentioned by name like four times on here than probably yeah
[Magisk] passionicon:
As far as i know, it can be found in vendor folder. It's keybox.xml

To test just replace with same keybox file inside after installing latest pif6.3 and restart.

That's all i know
[Magisk] Syoenth:
where is located kexbox.bin and how can I dump it? I want to use my phone keytbox.bin
[Magisk] pndwal:
Yeah, guess that's the beta print... Not banned... I'm interested in banned prints from devices launched with A7 and earlier...

So that's with APatch? Tried various API levels?... If so, sadly APatch may not be bypassing Google 'print' bans... ☹️ Thanks for trying! 🙃 PW
[Magisk] yjcbn:
Does the default FP of PIF 16.3 prevent me from getting STRONG? I wonder how to efficiently test if a keybox works. Thanks in advance.
[Magisk] pershoot:
RCS works fine with Lsposed.

🔧 [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] markoppp:
FYI: I just verified your conclusion and here what I have:

Phone: Samsung S10e with LineageOS installed, Android 13

SafetyNet:

Basic Integrity - passed

CTS Profile Match - failed

Play Integrity Check:

Basic Integrity - pass

Device integrity - fail

Strong integrity - fail

Virtual integrity - fail

Play Store works fine. I can do other checks if needed.
[Magisk] pndwal:
Did try to put it back 4 U!:

😥 🙃 PW
[Magisk] JazonX:
Randomly Searched Keybox in the PC and I found a "Keybox Keymaster Tool" from my older ROG Phone II Dumps. I recall getting these from some Chinese Site which had paywall access to RAW Firmwares.

Anybody has the time - have a look whether it has some capability to generate keyboxes or something.
[Magisk] CityKev:
I'm now a bystander in this in terms of unlocking the bootloader on my primary device (phone). I had a Redmi Note 10 Pro up until a couple of weeks ago and my plan was to unlock it and install a custom ROM now it's clear that it won't be getting any more official updates. I ditched that plan and bought a new Xiaomi phone with (hopefully) four years of updates and I'll keep the bootloader locked and on stock. I'm happy to have custom ROMs on my tablets as I don't have banking apps, wallet etc on them so I get my customisation fix from them.

Google must have all but won in this battle as they keep raising the bar in terms of being able to use key functions until there is only a hardcore of Bitter Enders who are determined to go down fighting. It's sad really as the owners of a product should have the choice of what level of perceived risk they are prepared to accept in modding them rather than a nanny approach of enforcing maximum 'security' on them.
[Magisk] intel_core_i7:
Well, there is a problem with that. The users are willing to take those risks, but the enterprises offering services to those aren't. Enterprise security sucks because it strips away all the freedom, but when the users are given freedom and something went wrong within the IT system partly due to that decision (not that rare), the enterprises are often the ones who take the loss, not the users.

I'm really dissatisfied with the direction modern mobile app security is going, but it's reasonable enough.
[Magisk] BillGoss:
I left that attribute in the json file and it works just fine.
[Magisk] majorfigjam:
Yes indeed.

Their concern is not with whether you or I can freely use our own modded phones to make payments, send secure messages, buy burgers or book rides from our own accounts; it is with stopping anaonymous "baddies" from using their modded phones to make payments, send secure messages, buy burgers or book rides from OUR accounts.

We are just collateral damage as they seek to secure their systems from such misuse.

And on the evidence before us, Google still haven't got beyond beta testing their Play Integrity efforts.
[Magisk] mwzdalne:
how's the progress on rcs?
[Magisk] majorfigjam:
Works with a non-Sailfish print if you have Device Integrity
[Magisk] mwzdalne:
wdym non sailfish? i wasnt following this thread for a while

Sent from SM-S711B using ReLabs
[Magisk] pershoot:
Please go back and read a few pages as this thread is ginormous, as it is.
[Magisk] passionicon:
Other fp apart from sailfish
[Magisk] osm0sis:
All working prints that aren't the current mass-used public print (i.e. sailfish now, griffin in March/April) work for RCS.

FAQ #13:

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] pershoot:
Replying here to confirm, for the data points. All is well, after being in a dormant state (since last ban; RCS), for some time (nothing was touched and all options were left since that previous time).
[Magisk] V0latyle:
Yes, Play Store will work just fine but you may not be able to install certain apps if not Play Certified. Netflix for example
[Magisk] mwzdalne:
I'm completely lost 😕

Can you suggest what to do to improve this result? ⬇️ BTW my real device model is SM-A546B

View attachment 6115762
[Magisk] pershoot:
You are passing a DEVICE verdict; you should be good with contactless / wallet. For RCS, if you are currently on a banned print (for those purposes), you'll need to search out / find a build with a print that has not been banned for those purposes while keeping contactless happy (i.e. passing DEVICE and not banned for RCS purposes). You may also need to change your particular privilege escalation method (i.e. magisk, apatch, KSU, etc.).

Please search this thread, as there are helpful hints to do so and guidance.
[Magisk] frasca61:
I am using Sailfisch now and Griffin in March, and in both cases RCS has always worked perfectly ...
[Magisk] pershoot:
You may be (one of) the only ones (there was another that posted here stating also the same, a little time back). Either it has not caught up to you (yet), or perhaps there is not any governance there, w./ regards to this on your particular network (I surmise; it should all ultimately go up to El Goog though).

I confirm, sailfish definitely does not work for RCS in my part of the world, network (I just re-tested this in the last +24 hours across (2) priv. escalation methods) and device. Perhaps the shipping API level of device plays a factor in this. Others can chime in with their thoughts on that one.
[Magisk] Vision:
I see huge images take forever to scroll down.

If we can add smaller image to take less space.
[Magisk] aliantonio:
Which mod version are you using of lsposed? Each time I've installed lsposed with apatch, it either crashes immediately or breaks RCS immediately.
[Magisk] pershoot:
https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89571341 (I'm on the 'Newer one').
[Magisk] HippoMan:
... and I believe that we modders are key players in those beta testing efforts. We are giving the Googlefrinchians valuable information about the effectiveness of their efforts by our spoofing of fingerprints, messing with keys and attestation, etc.

Everything that we are doing is helping them to better lock down Android.
[Magisk] pershoot:
I've tested a few apps, that I was hiding escalation from previously and none have detected it, thus far. I'll keep observing and perhaps move towards removal and / or disabling of Zygisk Assistant.
[Magisk] ThatOneGuyOverThere:
Has anyone found a working keybox.xml to pass strong?
[Magisk] aliantonio:
Thank you. I'll test in a bit and report back.
[Magisk] geokilla:
I'm failing device integrity even on v16.3. I cannot get some of my apps to update on Google Play Store, saying it won't work for my device. Any suggestions?
[Magisk] intel_core_i7:
Well, I have said a few times that Android getting locked down or not also depends on third party app developers. Not every bank/government is willing to pay google to make more than 10000 PI API requests per day.
[Magisk] Stаr:
Run 'unzip -l /system/etc/security/otacerts.zip' or run this app to check if your rom is signed by test-keys. If it is, you have to update to a rom signed with release-keys.
[Magisk] HippoMan:
And I have said several times that I agree about the third party developers' role in all this.

We are helping the Googlefrinchian integrity calculating efforts and integrity reporting efforts, and this then helps developers to better cripple their apps on modded devices.

And we're also helping the Googlefrinchians to better prevent RCS usage on modded devices
[Magisk] intel_core_i7:
Well there hasn't been any progress on RCS for a while, I don't even know if we had helped them any in that regard.

About Play Integrity they can ban every print and force strong to have Wallet/RCS working, and until now they have decided not to, so there's some hope left.

I'm glad that I'm living in a country where's literally no RCS support from network carriers (everyone downloads and use a third party messaging app), and banks/government haven't implemented PI API in their apps despite the option is available for years. One app uses local hardware attestation but the apk can be modded easily, I don't know why they haven't implemented app signature checking like others. Card payments can be made by... Plastic cards, and it's not that popular anyway since our bank (money) transfer system does it instantly, though upcoming changes next month making users to use phone camera to take a video of their face in real time if transaction is above around 400US$
[Magisk] generalculprit:
Let's all revert to stock and lock our bootloaders again.

Eat this, Google! 😉
[Magisk] ibyb008:
Noob question. How to pull up pif from an unrooted android 8 device ?
[Magisk] Vision:
Read 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] mustang00066:
I love that amazing and dedicated people have and will, I believe, continue to beat goog at this stuff. Just give it some time.
[Magisk] markdewet:
I would just like to make a few observations, specific to my device, which as mentioned is the S8+ SM-G955F (drean2lte):

1: It seems to be incredibly difficult to find a build.prop dump for this specific device. I have searched Google, looked in the site mentioned by Osm0sis in his Odds and Ends thread, and so far nothing has been found. Still looking, though.

2: I do have the original A9 stock ROM downloaded, however, I cannot seem to find a way to extract the build.prop from the system.img.lz4 file, located in the AP.....tar.md5 file, which is one of the 5 files used when flashing the stock ROM via Odin.

3: At least, for the moment, my Google Wallet is working with my current setup, so as someone once said, if it ain't broke, don't fix it. However, I have just been informed that the ACTUAL ROM I want to use, LineageOS 21.0 (A14), is now signed.

4: As such, with regards to point 3, I will back up my Magisk settings (manually, if I have to), then install EVERYTHING from scratch, re-install Magisk, Shamiko, PIF v9 and see if Wallet STILL works.

Now, please note!!!! I am NOT asking for any guidance or ANY spoonfeeding regarding points 1 and 2 above, I am simply stating my experience so far, so please do not take offence, anyone. Please.

I DO have ONE question and that is:

Why can one NOT simply use the ORIGINAL pif.json from the stock ROM in order to get basic and device integrity? Is it because it shows a lower version of Android in it which then conflicts with the ROM version installed?

Now, again, If the above question has already been answered elsewhere, simply tell me it has been answered and I will do my best to search for it, however, having read all 886 pages of this thread, I have seen mention of stock pif.jsons but nothing that really states that one CAN or SHOULD use the stock .json.

Thank you.
[Magisk] geokilla:
It's using test key RIP
[Magisk] Daccapo:
I would also like to find the original pif.json for my Samsung S9+, but I couldn't find anything on the net. :-(

The current Play Integrity v16.3 is not working for me.
[Magisk] okij:
This gives me the idea that we just need to spoof the date that Google LLC employees have on their clocks and calendars so that they don't have a 29 date. So let's hack their server time1.google.com (IP 216.239.35.09) to make them believe that e.g. after June 28 it's June 28.1, then followed by June 30. It's as simple as that. 😝
[Magisk] Stаr:
If you're still using the crDroid from your signature then flashing the latest version from early this month should fix it. Alongside crDroid, other roms like Evo X and PixelOS had to be rebuilt earler this month with release-keys.
[Magisk] markdewet:
EDIT: I have just found the answer to my own question on droidwin.com, it seems as follows:

1: Devices launching with Pie (Android 9) or later might not work.

2: Don’t go for the likes of Pixel, Samsung, Xiaomi, and other popular OEMs as most of their fingerprints have already been used or patched by Google.

So, NOW I understand why.
[Magisk] dickta:
Hello I really don't understand this tee thing. I'm on lineageos 21 on Poco F3 with apatch, pif 16.0/16.2, zygisk next, zygisk assistant with working tee (in theory) and never was able to pass strong only device + basic with the built-in fingerprint. If I change the fingerprint in pif by editing the pif.json no valid fingerprint is working, - only basic attestation. I tried a ton of fingerprint, all from my previous devices and only getting basic without device integrity. What should I do with this or what to do with tee? I think I'm getting old for this. 🥲

View attachment 6115869View attachment 6115870View attachment 6115871
[Magisk] geokilla:
Yes I am. The latest OTA isn't installing for me even though it installed all the prior ones so I have to look into why. Probably need a clean install, which is going to take me a few hours to do.
[Magisk] Vision:
So this is the Pathclassloader , no need anymore classesX.dex, because have inside Pathclassloader and only put this miui.jar in /system/framework and that it ? Can this can happen with frameworkpatch ?
[Magisk] Stаr:
From what I've seen on most roms, dirty flashing is good. I'm guessing OTA doesn't work because of the different signature, so it should go back to working for subsequent ones.