yashsingh1/xdaforums huggingface dataset:
[Magisk] Scholeggo:
I'm still trying to figure out how to actually test tee.. does this mean it's broken?

View attachment 6115167

Motorola edge 40 Pro

Official Lineage 21

KSU w/ Zygisk, PIF v16.2

Passing Basic only
[Magisk] Vision:
Yeah Broken TEE 😔
[Magisk] Scholeggo:
@chiteroman here you said you'd soon be back for broken tees.. does that still apply here or did i read that wrong?

View attachment 6115172
[Magisk] spida_singh:
16.2 passing all 3

Pixel 6

LOS21

KSU

Brilliant work!
[Magisk] sawdoctor:
I don't have a working fingerprint to test but hopefully someone will confirm.
[Magisk] orlando23:
I installed v16.2 on my rooted Google Pixel 6 with Magisk v27. However, still get "This device can't be set up to tap to pay, it may be rooted or running contactless payments". I didn't use other models like PlayIntegrityFork or PlayIntegrityNext. Do I still need to add pif.json to /data/adb?
[Magisk] David B.:
Neither do I. The reason I ask is because this contradicts what @chiteroman said:

Although, considering that the behavior people are seeing here does not match what he claimed here, I suspect that he's unfortunately wrong. 😕
[Magisk] rocker00:
@chiteroman Thank you man and everyone involved in this awesome work, Samsung Galaxy A52s user, my modified stock ROM with an EMPTY AVB img on AP & BL slots, no AVB on any partition, removed AVB config from fstab & kernel, and finally i passed the strong integrity with v16.2, v16 didn't pass strong and i haven't tried v16.1, magisk alpha, latest shamiko from alpha's telegram channel and zygisk next.

Just hope that Google won't do any ****ty stuff soon!

Thanks again, you guys rock!
[Magisk] Renzke:
Eerything which is bigger 15.9.9 - - > "Basic" only in my case. (latest test was 16.2).

TEE is not broken.

Went back to 15.9.9 - Pass "Device" again.

Latest Magisk Canary + Zygisk + Shamiko 1.0.1 + Bootloader Spoofer

Test in Key Attestion 1.6 looks good.
[Magisk] chiteroman:
If you are using stock rom with KSU LKM or APatch patched kernel, it passes Strong with your device's fingerprint.
[Magisk] mac796:
Ok I installed my private print over this new pif module got rcs back but lost strong. Oh well.
[Magisk] David B.:
I am using KSU LKM with the stock rom, but I am not passing strong with my device's fingerprint. My TEE is not broken either.
[Magisk] orlando23:
Seems not working now, even If extracting prop and generate pif.json to /data/adb
[Magisk] chiteroman:
Mine it's working, idk 🤷‍♂️
[Magisk] Vision:
On Magisk or Kitsune Mask? 🤔
[Magisk] David B.:
What modules do you have installed on your phone? And what is your phone model?
[Magisk] chiteroman:
Detected, like using KernelSU GKI or custom kernel.

I'm using KernelSU LKM with modules: ZygiskNext, zygisk-detach, youtube revanced and PIF.

I can use LSPosed and still pass Strong.
[Magisk] mac796:
Im using canary. Maybe that's why no work for me.
[Magisk] David B.:
Are you using YouTube Revanced via a module or via the ReVanced Team release? I also use LSPosed and pass Strong without issues.

Here is how I went about setting up my device fingerprint, by the way.

🔧 [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] Vision:
Even with the frameworkpatch method via simple module without zygisk? 🤔
[Magisk] eac5:
Passing strong here on Pixel 7, stock ROM, latest Magisk Alpha.

Using my own device print results in no integrity or basic. Sailfish works. Not gonna try messing with KSU and such, probably this will get patched pretty soon anyways, the keybox data is public on GitHub it's a public SW cert, so I guess some shenanigans are happening server-side.

Would be interesting to combine a modified FrameworkPatch with this to also obtain locked bootloader on local attestations, i.e. KeyAttestation
[Magisk] Erecik:
Same here. Using my own FP returns only BASIC verdict when checking integrity via Play Store. I will stay on Sailfish as for now.
[Magisk] Rares6567:
I don't know then
[Magisk] Joseahfer:
Passing strong on Google Pixel 6 Pro with PIF 16.2, latest stock June update, Magisk 27.0 and LSPosed.
[Magisk] V0latyle:
Well then.

Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY, MEETS_STRONG_INTEGRITY]
Build fingerprint: google/redfin/redfin:14/UP1A.231105.001.B2/11260668:user/release-keys
Brand: google
Device: redfin
Model: Pixel 5

Magisk 27.0, no other modules of note
[Magisk] mac796:
I passed strong just fine. Pixel 8 pro magisk Canary. I tried installing three different private prints. I still get basic integrity and RCS works but strong goes away. I'm guessing you need a patch or KSU maybe?
[Magisk] ninjakira:
I'm guessing y'all have unbroken tee that get strong also?
[Magisk] David B.:
An unbroken TEE is a requirement for this to work.
[Magisk] alekyiv:
View attachment 6115192View attachment 6115193View attachment 6115194
[Magisk] alekyiv:
Have idea?
[Magisk] Rex5979:
Heck yay 😊

Thanks man !!
[Magisk] dknight178:
Sucks to have a oneplus lately
[Magisk] dosbuddy:
POCO X3 NFC

xiaomi.eu 14.0.2 (first version w/o injector)

magisk 27, lsposed, shamiko, ...

PIF 16.0 ==> device

PIF 16.0 + "resetprop ro.product.first_api_level 34" ==> strong

PIF 16.2 ==> strong

thanks @chiteroman
[Magisk] passionicon:
I regret moving from Samsung before now, this whole TEE thing makes it worse
[Magisk] mac796:
I may have figured out my deal. I didn't realize there was a16.0 I flashed 16.2 first. So far 16.0 everything works. 👍
[Magisk] kholdstayr:
Same here. I am using APatch with Zygisk Next, I flashed pif 16.0 and now I have RCS with device integrity. I haven't had that since May when Google broke everything.
[Magisk] David B.:
Do you have hardware integrity?
[Magisk] mac796:
so this is off topic i know but messing around with the private print and this module my pixel 8 went into adb sideload mode and wont come out. i can get to bootloader even let me flash factory image from google site. but always boots back into adb sideload is there a secret to get out or is this some kind of brick? all i was doing was changing prints with pixel flasher and it jumped into this.

Edit. I got out of it. I can't tell you how
[Magisk] AlexS2412:
everything except rcs works even strong.
[Magisk] kholdstayr:
Just device, no hardware, but I have no idea about the whole TEE thing that everyone is discussing. At this point I'm happy to have device and RCS working at the same time.
[Magisk] AlexS2412:
i would like rcs to work i dont even care about strong. what did you do?
[Magisk] pr3dicament:
I hate my OnePlus 8T. Being a oneplus user sucks.
[Magisk] kholdstayr:
I don't know if this matters, but I switched to using APatch instead of Magisk. APatch is just as easy to install as Magisk is.

I have four modules installed in APatch:

Play Integrity Fix 16.0

Zygisk Assistant (not sure if this helps but I'm using it)

Zygisk detach (not needed but I use it)

Zygisk Next

If you have any questions let me know and I'll help
[Magisk] Vision:
@chiteroman

So with this new PIF and this https://github.com/hex3l/PlayIntegrityForkKsBypass, if you modify this, we can have our FP (I hope in feature no need it) and keybox.xml

We will have it, 2 bird's with 1.

And with this the ultimate PIF module.
[Magisk] pr3dicament:
I'm still using @osm0sis patch.

Honestly, I wouldn't get too excited over this. However, great find.
[Magisk] pr3dicament:
I'm waiting for it to get nailed basically, and I don't wanna hear about how the whole "modding world" is small.. it's corporate greed at its finest.

I hate Google.
[Magisk] mac796:
Something new to try. His patch will be useless just the same. Soon as Google kills the rest.
[Magisk] BunnyPig1:
I'm just really surprised Google have allowed it to work for this long. I thought it would've been patched within a couple of hours.

I get that having device passing for the small minority of modders might not make a huge impact but STRONG is kind of a big deal I believe.

I'm just nervous that being able to pass STRONG now has made them shift gear into "haul butt". This might ban all FPs at once just to keep this from happening.
[Magisk] pndwal:
Guess for your device prop/field set, just use JSON configured properly but empty?... May need to add just DEVICE_INITIAL_SDK_INT, 34 however(?)

Not sure praying will help with this one... 😁 PW
[Magisk] David B.:
What phone and Android version are you using? I've not been able to get RCS working at all on my phone with this module.

So, are you suggesting that I try this?

{
"DEVICE_INITIAL_SDK_INT": "34"
}
[Magisk] pndwal:
... Or get just their act together and fix STRONG with only SW attestation certificates at least... Should never happen!😬 PW
[Magisk] pr3dicament:
Well if they don't patch this up soon then yeah, I might try it as in something to test..I guess this feeling is the soul crushing part regarding private fp's.
[Magisk] pndwal:
Looks right at a glance... Out of time to check properly now... Someone else will confirm... 👍 PW
[Magisk] intel_core_i7:
I wonder if Strong passing this time is intentional. Google executive probably decided to leave several vulnerabilities around the Play Integrity API, each with increased difficulty so it would take around a year for the community to find out. It's like an annual "Strong" party to cheer the community up a little bit after all the bs decision making the Android rooting & custom ROM community constantly living in gloom and doom, and the previous Strong exploit happened around a year ago.

Or just a happy little coincidence :cowboy:
[Magisk] kholdstayr:
I'm using a Motorola Edge+ 2022. It has Android 13.
[Magisk] David B.:
The development of the Play Integrity API should never have happened. I would love to see the European Union go after Google for this, but sadly, it will likely never happen.

When you set a custom fingerprint, does the module just override the values set in the module-embedded fingerprint or does it switch to using the device fingerprint and override whatever you define in the JSON? If it does the latter, then the result of trying this will not be any different than trying to use the whole fingerprint as I did before.
[Magisk] David B.:
Quoting me once would have been enough. 😂

Anyway, thanks for letting me know!
[Magisk] kholdstayr:
Lol yeah I'm doing this on my phone and the formatting is acting weird in my browser, oops, ok 😛
[Magisk] UberNorse:
I'm on P7P June OTA rooted with Apatch.

Installed Zygist Next and @chiteroman's 16.0 and Im passing strong and RCS still working for now.
[Magisk] David B.:
Perhaps this will be helpful to you!

[15.03.24] [NEW] XDA Forum Apps I Official with Domain Fix + Unofficial

XDA Forum Android Apps I am presenting here two apps for android for XDA Forums. 1.Original Fixed App Intro : As you might know, official XDA app is stopped working since migration of the domain. We've long waited to get official app to get...

xdaforums.com

Are you using a custom fingerprint?
[Magisk] westhaking:
Which version of APatch? I can't get my patched boot.img to flash on my P8P with June update.
[Magisk] UberNorse:
10763. I don't know if you're trying to just patch with Apatch's apk, but that didnt' work for me. I had to use Pixelflasher and it worked great.
[Magisk] UberNorse:
I simply installed the 16.0 and zygisk next to apatch and didn't modify anything at all so whatever @chiteroman has in 16.0 is working for me.

Edit- I just check the pif.json in the module and it's Sailfish. I repeat, RCS is still working.
[Magisk] kholdstayr:
I'm using

I had the APatch app generate the patch from my boot image, then flashed it using ADB and fastboot
[Magisk] UberNorse:
That method didn't work for me. Try using PixelFlasher and if you need help just pm me.
[Magisk] kholdstayr:
Wait. My RCS literally just died. No more RCS. Not joking!!!!!!
[Magisk] AlexS2412:
for me that one fails rcs and strong.
[Magisk] rrusek:
Can someone try this with lposed loaded? I'm getting my Pixel 8 Pro back tomorrow from repair and would would like to try this method but need exposed.

Thanks,

RJR
[Magisk] UberNorse:
Very strange. I won't pretend like I know the details as to why but mine is still working fine.
[Magisk] kholdstayr:
My RCS was working for about 2 hours and now just died. I had to disable the PIF module to get RCS working again.
[Magisk] UberNorse:
I don't expect it to last forever but we will see and I'm sure everyone will have different results. I've pmed you info on what I did with Pixelflasher and Apatch but never asked what phone you are using. If I'm not mistaken PF will work with most Android though I may be wrong
[Magisk] Nergal di Cuthah:
So ten pages and no one answered this so, of course you don't pass in Airplane mode, it needs to contact a server to get device and (i assume) strong
[Magisk] kholdstayr:
I know this is the wrong thread for this (probably), so if someone can direct me to the correct thread, that would be fine. But I have a question is about generating your own print from your own hardware. I've read instructions before that say you need your ROM, and that you can extract build props from the ROM.

I have my phone firmware downloaded, but I'm unable to extract buildprops from the ROM. However, I know that the build prop is simply on the Android filesystem in the /system directory. Why can't I just use the build prop from /system?
[Magisk] David B.:
That's so weird. Do you have any other modules installed or is that it?
[Magisk] osm0sis:
Mine will last longer than this Strong. 😄

Google could have killed all fingerprints for spoofing from the beginning but still haven't. 🤷‍♂️
[Magisk] UberNorse:
Only Zygist Next and Play Integrity Fix 16.0. I'm going to ride that out for a day or so and install more from there.
[Magisk] mac796:
I'm just saying it's all going to go away sooner rather than later it looks like. I hope they last a long time. Might as well enjoy it all while we can
[Magisk] orlando23:
My Google Pixel 6 isn't working with PIF 16.2. Have you just installed PIF16.2, Magisk 27.0 and LSPosed? Do you do anything special?
[Magisk] badabing2003:
Shameless plug.

PixelFlasher (see my sig)

Device Menu | Pif Print

View attachment 6115238
[Magisk] orlando23:
So Magisk isn't working for you?
[Magisk] dtingley11222:
Is there anything I have to clear before RCS works again? I have strong integrity but no RCS.
[Magisk] orlando23:
My google pixel 6 with Android 14 have vendor-buiild.prop, system-build.prop and product-build.prop. I also use gen_pif_custom.sh to generate pif.json and put it to /data/adb/pif.json. However, it's not working. I only install Magisk 27.0 and PIF 16.2. Anything is missing? THanks
[Magisk] Joseahfer:
Nothing special, except this LSPosed mod that works with the QPR3 June update. Stock kernel as well.
[Magisk] V0latyle:
It's a neat trick but I ended up going back to a regular 2/3 print so I can use RCS

@chiteroman what makes the sailfish print so special, and why don't other prints work with this?
[Magisk] orlando23:
Thanks Joseahfer, sorry, what do you mean for "Stock kernel"?
[Magisk] intel_core_i7:
Probably another hardware oopsie from Google, similar to that Walleye (?) print last year.
[Magisk] YHMWU7Rc9TkDAtu4NT6:
Just upgraded from chiteroman v15.9.9 >>TO>> chiteroman v16.2

No RCS, Only Basic = Pass , CTS = Fail

🥳
[Magisk] eac5:
Sorry for slight offtopic, but how does one check if RCS is working? I have it enabled in settings and it shows "status: connected", but when I initiate a conversation, under the send button it says 'SMS', and if I try to attach a photo, it says "attachments are not supported in this conversation". So I take that to mean RCS does not work, right?
[Magisk] joeyhuab:
Exactly that.
[Magisk] wugga3:
When did this thread become the PRAY integrity fix....
[Magisk] YHMWU7Rc9TkDAtu4NT6:
Yes , that is the symptom you are looking for. Once that starts happening its confirmed that RCS stopped working.
[Magisk] Zaxx32:
Ah...thanx for the update!
[Magisk] dtingley11222:
So.... I have strong integrity but no RCS? What is wrong with my phone? I have Shamiko, Zygisk Next, Lsposed, Playcurl, Pif (strong) installed. I am on KernelSu on a pixel 6 LKM. What am I doing wrong to not have RCS?
[Magisk] Joseahfer:
I mean I didn't change the kernel to Kirisakura or anything else.
[Magisk] geokilla:
I meant I restarted the phone in Airplane mode, and then took it off Airplane mode after. Regardless, still not passing so I must be doing something wrong despite being on v16.0.
[Magisk] David B.:
Yup, but let's enjoy it while it lasts!

I had the same problem. The only thing you can do is use the embedded fingerprint. You won't have RCS working, though.
[Magisk] YHMWU7Rc9TkDAtu4NT6:
Slightly off-topic conspiracy theory time:

Component and device manufacturers went to Google, and said please expand and enforce Play Integrity + Play Integrity Checks.

We are not selling enough new components and devices, the market is saturated. Do something to hobble the resale market. We want people to buy new devices.

Google , thinks 🤔 ... whats the most basic thing everyone uses & has a need for. Wait, lets get a strangle hold on messaging plus payments and gimp them, it worked for TimApple.

People will have to buy new devices. Hobbyists and modders are an insignificant minority.The resale and refurbished ( upgrade/update old device for resale ) market is big by comparison ( estimated to be 350 million units in 2024 ) @HippoMan & @okij had good posts about this here and here.

💰 📈 🥳
[Magisk] V0latyle:
Nothing. RCS doesn't work with the Sailfish print.
[Magisk] LLStarks:
I'm simply rooted with APatch at the moment and I have RCS and Wallet. Less is more, I guess.
[Magisk] orlando23:
Sorry for the interruption. I don't know what do you mean for the embedded fingerprint. Do you mean the default pif.json binded with play integrity API or like me, you extract from the factory image?
[Magisk] orlando23:
Do you think APatch is better than Magisk?
[Magisk] miku404:
I'm thinking google might be getting ready to rollout something like Apple Wallet ID its been 3 years since apple launched their version so google has to be working on a clone of it and they are probably being pressured because of the REAL ID mandate going into place. The US government wants everyone from every state to be REAL ID compliment. In which case it would make sense to crack down and start banning as many FPs being used by custom ROM/rooted users as they can make it easier to know which FP is connected to which ID. It would get very difficult to link someone to their state ID from their device FP if hundreds of other people are using the same FP and also have an ID linked. And being able to pull up the ID of a person from just their device FP that would be the holy grail of surveillance tech. And we all know how much google cares about our privacy and right to free speech 🤣.
[Magisk] orlando23:
Could you share how can I do for APatch to root my device and surpass RCS and Wallet working?
[Magisk] LLStarks:
For all else being equal, it seems to hide itself a bit better than Magisk or Kernelsu
[Magisk] Nergal di Cuthah:
Not here please, it's already 10 pages in 8 hours
[Magisk] orlando23:
For Magisk, because previously I worked out a LSPosed plugin to hook Android API. Is it possible for APatch?
[Magisk] miku404:
I only got issues when i switched from a ROM using kernelsu natively (what APatch does but to any ROM) to another ROM using Magisk. I have tried using APatch but every time i flash the patched Boot.img to Boot via twrp it always pushes me into a boot loop does anyone know of a fix or am i doing it wrong?
[Magisk] dtingley11222:
So what should I do instead?
[Magisk] orlando23:
By the way, what RCS do you mean?
[Magisk] JustinCretible:
He's referring to Google's RCS (rich communication services) which makes the default messages app more similar to iMessage. It allows you to send high-resolution photos, react to people's messages, supports end-to-end encryption, and more.

It's quite a nice feature to have, but Google has been blocking it on devices that fail Device integrity. And now they have even banned it on all devices using the Sailfish fingerprint (citation needed). Hopefully that helps answer your question.
[Magisk] pndwal:
Like the Android 14 Easter Egg (morphs Apollo 14 mission patch logo/spacecraft) but better?... Man, I hope they are doing it on purpose!! 🤣 PW
[Magisk] pndwal:
Should be the latter...

Yeah, but it's not really 'fingerprint'; it's a whole device ID (prop/field) set... So you can expertly include all needed fields etc as you did...

I responded to your comment, but really was just adding to your answer to this:

... No JSON wouldn't work; that would default to PIF inbuilt spoof values, but an empty JSON should result in stock/device prop/field set being used, and it's much easier to do that than re-creating it.

@chiteroman said device fingerprint will work if TEE is good; That should fix RSS issues if device is compatible too... Not sure if DEVICE_INITIAL_SDK_INT, 34 should still be spoofed...

🤠 PW
[Magisk] pndwal:
Please see my post above... 🤠 PW
[Magisk] njaya95:
Which device is that? Starqlte?
[Magisk] passionicon:
Samsung s9 snap
[Magisk] halfbytecode:
My device is somehow passing no integrity out of the blue. Until a few days ago, it was passing Device Integrity.

I'm on a signed custom rom, crDroid, for Pixel 7 Pro. I'm using Magisk, Zygisk, Shamiko, PIF v15.9.9. I tried v16.0 and v16.2 as well but it made no difference.

I even tried clearing data and cache for Play Store, Play Services, and Play Protect, with/without Airplane mode turned on. Nothing helped this time, whereas this used to work for me in the past.

EDIT: It turned out this time it was the result of adding Play Store, Play Services and Play Protect to the scope of Bootloader Spoofer LSPosed module. Removing all 3 from its scope made Basic and Device Integrity pass again right away for me on PIF v15.9.9.
[Magisk] BarackMitzvah:
Ok, threw a pif.json in the data/adb/ folder with just empty brackets and rebooted

Can't check if its functional bc all of the Integrity checker apps have hit their API limit, but we'll see how this goes

Thank you for the help!
[Magisk] trevtdogg:
what about developer options in google play?
[Magisk] BarackMitzvah:
never knew I could do that

Looks like just basic :/

Edit: Removing the blank pif.json once again achieves Strong Integrity on 16.2
[Magisk] Scholeggo:
Is there any way to still achieve at least RCS with this module? I still have yet to find a good private fingerprint, but iirc @chiteroman said any newer fingerprint may do it (unless I read that wrong too)
[Magisk] pndwal:
Tried with just the DEVICE_INITIAL_SDK_INT, 34 line in JSON?... PW
[Magisk] BarackMitzvah:
Okay, tried with the pif.json of:

{
"DEVICE_INITIAL_SDK_INT": "34"
}

and only have Basic integrity
[Magisk] BillGoss:
I was really intrigued by the possibility of getting strong integrity using the phone's stock fingerprint.

So I installed PIF 16.2 and replaced the sailfish pif.json (which gives strong integrity) with one using my phone's properties (it's a Pixel 8 Pro). I tried it with DEVICE_INITIAL_SDK_INT set to 32 (which gen_pif_custom.sh generated) and 34 but I only got basic integrity passing ☹️
[Magisk] David B.:
I meant the one embedded in the module.
[Magisk] sawdoctor:
Either lock bootloader and go stock, try Apatch or find an unbanned fingerprint
[Magisk] miku404:
I have this FP but i don't know if it work because every time i try to copy it its still keeps the original FP and does not report any changes even after rebooting in the play store. So if anyone whats to try this out and see if it will work.
[Magisk] koxipo:
Hello, I tested it and got a basic integrity result with it
[Magisk] Vision:
Unfortunately, the only info is this.

View attachment 6115304
[Magisk] addsfsds:
Good morning guys!

I have my old oneplus 8 pro with magisk 27 and old play integrity next fork 14.1 and I'm passing device integrity, so no problems.

My new oneplus 12 is only getting basic integrity with PIF 15.99, PIF 16 and PIF 16.2 and playcurl. Even tried to transfer the fingerprint from 8 pro to 12 but nothing. Any idea? Thank you