yashsingh1/xdaforums huggingface dataset:
[Magisk] casouzaj:
This is not entirely true. I have official LineageOS 21 on my Sony Xperia 1 II, rooted by KernelSU, and with modules PlayIntegrityFork CI#227 and latest Zygsik Assistant (along with latest ZygiskNext, of course), RCS is working for me.
[Magisk] Nergal di Cuthah:
Is wallet working too? So far we've seen RCS works wallet doesn't or vice versa.
[Magisk] Magik_Malfici:
That's why I'm so intrigued... 🤔
[Magisk] Nergal di Cuthah:
@pndwal could native bridge zygisk be a factor here (as opposed to zygisknext used by quoted member)
[Magisk] Magik_Malfici:
What's Zygsik Assistant ?
[Magisk] Nergal di Cuthah:
[MODULE] Zygisk Assistant (FOSS Root Hider)

Zygisk Assistant (FOSS Root Hider) This module is designed to hide root similar to Shamiko. While capabilities may not be the same, it's worth noting that this module is open-source whereas Shamiko is closed-source. One of the advantages of this...

xdaforums.com

Alternate to shamiko
[Magisk] casouzaj:
Yes, both Wallet and RCS work for me.
[Magisk] hackthis02:
What is your method for selection. Also how are you getting the build.props? Do you have a faster method then just finding/downloading the system zip and extracting the imgs?
[Magisk] Erecik:
I think You can just use Pixel Flasher built in PIF finder. It takes like 15 seconds to check if found FP is working.
[Magisk] Magchild:
Do you also happen to have a physical sim card? I have a similar phone but different setup. PIF8, sailfish print. Magisk27, configured denylist but not enabled, shamiko. I don't believe I have ever lost RCS and when I check it shows connected to my Verizon sim card. P.S. wallet still working.
[Magisk] hackthis02:
PIF finder? There isn't a PIF Finder, you might mean the PIF Manager. And I'm already using that. I was referring more to the other side. Looking for a better/quicker way to find/download the rom images to pull the build.props to use with osm0sis' gen_pif_custom.sh.
[Magisk] casouzaj:
Yes, my phone, a Sony Xperia 1 II, is not e-SiM enabled.
[Magisk] Nergal di Cuthah:
That repo is burned and closed, only use get xiaomi print
[Magisk] osm0sis:
Sounds like you may have not removed the user app update to the ROM's built-in spoof injector after installing the module, as it told you during install:

PlayIntegrityFork/module/common_setup.sh at main · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

Then it'll likely all start behaving.

What ROM? PM me and I'll help troubleshoot it with you either way, in case it's a new ROM or app to add to my list:

PlayIntegrityFork/module/example.app_replace.list at main · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com
[Magisk] HippoMan:
I was indeed mistaken.

There is another set of fingerprints besides the one I referred to as having been reduced to 3 working prints. And in that other set, there are indeed around 70 or so.
[Magisk] simplepinoi177:
@Magik_Malfici , unfortunately, this statement only describes what SPIC shows, not what exactly you passed (are you resulting in "DARK ORANGE" or "LIGHT ORANGE" or even "RED"?). And your attached screenshot just shows your Play Store info.

You should enable Developers Options in Play Store and Check Integrity in there and confirm you are passing MEETS_DEVICE and/or come back with it here. Of course, if you are indeed not passing DEVICE, then that's the reason why your RCS is no longer working...
[Magisk] s1dest3pnate:
Can we understand why RCS works on this guy's? I don't give a f about wallet or anything else, just please help me get RCS working 😢
[Magisk] casouzaj:
Try my setup.
[Magisk] awtompson:
It works on my P7Pro with PIF 15.9.9. I have no idea why. Happy to share any logs or settings to see what's different.
[Magisk] osm0sis:
Seems like A-B testing or a rollout that isn't complete yet if you're all on the same public print, PI DEVICE is passing, Play Store is certified and Wallet meets security requirements.
[Magisk] mac796:
For anyone that cares I uninstalled updates on messages app and rcs working again.
[Magisk] manjaroid:
Edit:

Anything other than the module? I see that you're on T-mobile and you don't appear to be the same person who posted earlier about the same setup on a 7 Pro with working RCS connected to Fi.
[Magisk] Magchild:
Do you happen to have a physical sim card or are you running esim?
[Magisk] pershoot:
+1. There should be no reason why the same public print, widely in use, triggers a different RCS working status (while maintaining Wallet operability), across devices, if its all ultimately going through the same place (El Goog).
[Magisk] s1dest3pnate:
Physical sim
[Magisk] sir_bazz:
So this showed up a couple of hours ago.

It relies on RCS to function so may help to explain why Messages security has been tightened.

View attachment 6111225
[Magisk] pndwal:
Yeah, a few red herrings given...

Fingerprint itself needs to be 'un-banned for spoofing purposes', but aside from that, must simply be from a device Google doesn't enforce a PI API HARDWARE_BACKED evaluationType at the server end for... (The altered prop/field set is needed to spoof a device that doesn't meet the DroidGuard/PI API requirements (ie. Keymaster 3+, mandatory for A8+ although various OEMs broke it for some time) for hardware key backed attestations to bypass the enforcement.

... So if built for a device that launched with Android 7 or earlier or a later OnePlus etc w/ broken keymaster implementation, the LOS properties "may possibly" work/be "un-banned"... If for later devices it'll be on the "remotely possible" list since Google still may not have tested some devices with working hardware backed key attestation meaning that these won't trigger the enforcement. Of these, some may remain 'un-banned'.

A CLI command has been given to reset DroidGuard service a few times here; may not work on all devices... Or just force stop Play Services before retesting.

🤠 PW
[Magisk] jbm76:
wallet is working for me - but no rcs - before the message would disappear I'd try to send, now it says can't send and give me the option to resend as a sms. Is it still working for you?

EDIT - it only gave me that option once now it is disappearing again
[Magisk] tom1807:
You refer to the Google Play Protect Service?

This is the only separate app I have on my Pixel 6 and never had to wipe this to get Play Store certification back.

Or is this a newer thing? Because the last time I had this issue was maybe 6 months ago.

Cheers

Tom
[Magisk] jbm76:
I took a log when the rcs messages fails to send - I can attach the whole log if anyone is interested. I am hopeful a change might be able to be made to frameworks_opt_telephony to fix rcs.

Here is the log here - https://katb.in/cacikiluzab

This is some of the log-

Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10239 RequestorUid: 10239 RequestorPkg: com.google.android.apps.messaging UnderlyingNetworks: Null] ]
[Magisk] Magik_Malfici:
Hello @simplepinoi177 ,

Yeah, I have misunderstood the principe of the application. Sorry 😐.

I attach the screenshot for clarifying the situation.

Some say that it is the fingerprint that will no longer work?

My fingerprint is : 4.19.157-perf-g1a6087bc0325-dirty so ?
[Magisk] Magik_Malfici:
Same situation... With Xiaomi Redmi 9T on MIUI 14, with a fingerprint strange : 4.19.157-perf-g1a6087bc0325-dirty so...
[Magisk] pndwal:
Not familiar with microG options... Please say if Play Services (GMS) app is official, microG's gmscore or other, and if came with ROM or you loaded yourself... Likewise, do you have official Play Store (vending) app?... Did you install yourself? Did you replace microG FakeStore or microG-companion?... And do you have Google services framework? (It "provides core functionality like authentication to your Google services"... not sure what happens if it's missing though.)

If you have official GMS (G Play Services) app, I believe it caches Play Protect signals where there's no separate Google Play Protect app... Clearing it's data may help 'certified' status. (Play Services apparently caches various signals, eg for G Pay/Wallet it monitors security, eg lockscreen changes or PI verdict failures even when Pay/Wallet isn't running.)... If not official (gmscore?), Play Protect caches may be absent...

Maybe this helps. 🤠 PW
[Magisk] simplepinoi177:
another member did as I suggested elsewhere and "uninstall updates" and was able to reactivate RCS after "Verified" it in Settings RCS chats. But, then again, another member did the same and got initial results, but it went back to being deactivated soon after...
[Magisk] Magik_Malfici:
At the moment, I'm stuck on the Group RCS: You can't send messages to XXX at the moment.” having uninstalled the Messages App updates.

Could this have anything to do with the Security updates? I'm stuck on MIUI Global 14.0.3 Stable SJQMIXM (I took my source here: https://xiaomi.eu/community/threads/miui-14-stable-release.67685/ so I'm still on original Xiaomi / MIUI orignal)

To be continued...
[Magisk] awtompson:
I don't know what Fi is. Other than that, my setup is plain. P7p May stock build, Shamiko, Magisk 27 & Pif 15.9.9.

View attachment 6111348
[Magisk] pershoot:
You will show connected, even if RCS is inoperable, if the previous state was connected (pre-ban). Try to send a new RCS chat / message (not use an existing chat; although those should have bombed / reverted by now (if you have the option enabled)).
[Magisk] awtompson:
I've done that. All chats still show as RCS.
[Magisk] pershoot:
You've evaded Google (for now), if you can initiate a new chat / send message via RCS on the cur. pub. print; dont reboot / recycle Carrier Services ;)
[Magisk] osm0sis:
Was just trying to find us a reminder of how it went down last time since it seems pretty much the same...

The above trend continued with late May banning all but 1% of previously known working prints, the ROM testkey ban, and a new RCS ban/restriction (test?). Making up for taking April off I guess!

...And, it seems @chiteroman outright deleted the old RCS issue so we've lost my full summary explanation of all the evidence we had from last time. Really frustrating. That was a lot of work from me and @BillGoss. 😠🤷‍♂️ https://github.com/chiteroman/PlayIntegrityFix/issues/297#issuecomment-2029934310

Don't suppose anyone saved a copy/paste or screenshot of it?
[Magisk] manjaroid:
I talked about this a couple days ago but couldn't remember the error. As @306bobby explained, a group message thread starts with one set of encryption keys and toggling RCS off and on creates new mismatched keys and nothing sends. To untangle it I deleted the thread and started a new one. There may be a better way out that doesn't involve deleting messages.
[Magisk] manjaroid:
You're connected and Messages may show the RCS prompt, but is RCS actually sending and receiving? Google Fi is a T-mobile MVNO.
[Magisk] pershoot:
I am on Google FI (MVNO); it is awall. @awtompson is on TMO.
[Magisk] changhuapeng:
RCS Wont Work · Issue #297 · chiteroman/PlayIntegrityFix

For some reason RCS is not working even when passing device integrity. This could be related to PIF... Posting the issue here just in case it is.

web.archive.org

That's as far as I could find for the latest archived copy.
[Magisk] deepongi:
View attachment 6111360

My RCS is working fine.
[Magisk] mwzdalne:
My RCS says it's connected but only sends sms. 😢

View attachment 6111361

View attachment 6111362
[Magisk] Nemosfate:
Did you read @pershoot post above?
[Magisk] osm0sis:
Amazing!! Didn't know archive.org indexed GitHub! 🤯

So, here's my summary post of what we found last time:

RCS Wont Work · Issue #297 · chiteroman/PlayIntegrityFix

For some reason RCS is not working even when passing device integrity. This could be related to PIF... Posting the issue here just in case it is.

web.archive.org

Everyone should take a second and read that.
[Magisk] mwzdalne:
yes, sad it's f-ed for now :cry:
[Magisk] osm0sis:
And I'll just copy it and keep it in this thread now I guess, where I previously had linked to it, so it can't get "lost" again... 🙄

🔧 [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

I'll add something to the FAQ about the RCS restriction too, once we know whether it's a long-term/standing thing now or just another short-term test.
[Magisk] manjaroid:
Are you using the public print? I'm seeing posts lately from T-mobile and Fi users with working RCS, but nothing yet about other MVNOs. I'm on Mint and RCS only works for me when I'm using a private print.

My SIM card is old and I'm wondering if newer APN configs might make a difference with the public print (like the effect MNC 240 versus 260 has on 5G connectivity). An eSIM should answer that.
[Magisk] pershoot:
I am on the cur. pub. print.
[Magisk] manjaroid:
I had a shortcut to that page and noticed it gone a couple days ago. Assumed it became obsolete. Apparently not!
[Magisk] mwzdalne:
What about SMessages and its RCS??

Sent from SM-S711B using ReLabs
[Magisk] osm0sis:
Presumably deleted instead of closed like normal only because of my involvement. Pretty sad. 🙄

Apparently just deleted by mistake! 🤷‍♂️
[Magisk] ThatOneGuyOverThere:
Tried what was in the github and got a single RCS message to work but stopped working after.
[Magisk] chiteroman:
Ahhhh, I removed a lof of issues few days ago because most of them have the same solution. I must have deleted that one without realizing it, sorry 😭
[Magisk] osm0sis:
Okay, fair enough.. just seemed weird that you actually deleted that one instead of closed like the other 234 issues. Sorry if I jumped to the wrong conclusion. 🫤✌️
[Magisk] Magik_Malfici:
So tonight I tried to put a custom PIF.JSON via gen_pif_custom.sh which gave me this :

{

// Build Fields

“MANUFACTURER”: “Xiaomi”,

“MODEL”: “Lime for arm64”,

“FINGERPRINT”: “Redmi/lime/lime:12/SOMETHING/V14.0.3.0.OTHERSOME:user/release-keys”,

“BRAND”: “Redmi”,

“PRODUCT”: “lime”,

“DEVICE”: “lime”,

“RELEASE”: “11”,

“ID”: “SOMETHING”,

“INCREMENTAL”: “V14.0.3.0.OTHERSOME”,

“TYPE”: “user”,

“TAGS”: “release-keys”,

“SECURITY_PATCH”: “2022-01-01”,

“DEVICE_INITIAL_SDK_INT”: “29”,

// System Properties

“*.build.id”: “SOMEHTING”,

“*.security_patch”: “2022-01-01”,

“*api_level”: “29”

}

Unfortunately, with this fingerprint, I only have MEETS BASIC INT in dark orange. and I don't pass SafetyNet's CTS Profile.

I tried autopif.json Spoiler content hidden. which gives me :

{

“MANUFACTURER”: “Google”,

“BRAND”: “google”,

“DEVICE”: “sailfish”,

“PRODUCT”: “sailfish”,

“MODEL”: “Pixel”,

“FINGERPRINT”: “google/sailfish/sailfish:8.1.0/SOMETHING/SOMETHING:user/release-keys”,

“SECURITY_PATCH”: “2017-12-05”,

“FIRST_API_LEVEL”: “25”

}

Here I am as usual, I have Meets Device Integrity in yellow and SafetyNet OK. I'll have to wait and see... It's a pain not to know...
[Magisk] K_a_m_i:
I don't have GMS, MicroG replaces that. However Play Store is official. I installed minMicroG, no FakeStore, no companion. I have microG services framework instead of Google services framework.
[Magisk] mwzdalne:
Suggestion:

*DISCLAIMER* I'M NOT A ANDROID DEVELOPER AND I DON'T KNOW IF THIS WILL WORK. THESE ARE JUST THOUGHTS.

if the check is client based maybe make a patched version of the app/thing that checks it so it returns StrongIntegrity=TRUE, if its server based than redirect the server to a server which will output StrongIntegrity=TRUE

Sent from SM-S711B using ReLabs
[Magisk] popieee:
works on T113NU with LineageOS 14.1?? ( Android 7)
[Magisk] mwzdalne:
probably

Sent from SM-S711B using ReLabs
[Magisk] popieee:
ok! i try it!
[Magisk] fbirraque:
Try don't public share pif.json
[Magisk] Nergal di Cuthah:
In the first part of any check droidguard downloads its latest iteration and overwrites what was there before, in my non developer understanding .
[Magisk] mwzdalne:
read only?

Sent from SM-S711B using ReLabs
[Magisk] HippoMan:
FYI: the "app/thing that checks it" is something called DroidGuard. The way that DroidGuard works is ...

Every time an integrity check is performed, the Googlefrinchian server pushes its current version of DroidGuard onto the device. It gets loaded onto the device as bytecode which then immediately gets executed on the device, and at that time, as part of the work that DroidGuard performs, it looks up relevant properties and attributes of the device in order to determine what level of integrity to assign at that moment.

In other words, there is no "app/thing" that we can alter on the device itself that can modify this DroidGuard behavior. All we can sometimes do is install "fingerprints" which spoof some of the device's properties that DroidGuard looks at, in order to fool DroidGuard during its integrity testing

Also, over time, the Googlefrinchians sometimes update the behavior of DroidGuard to perform stricter integrity checks. This is part of the reason for why over time we are seeing more and more instances of DEVICE-level integrity not being assigned to modded devices, and to devices running custom ROMs. These "improved" (ha ha!) versions of DroidGuard keep getting more accurate at identifying spoofed fingerprints and looking at other non-spoofable features of the device.
[Magisk] Nergal di Cuthah:
Would likely throw an error and fail the test, but above is better answer
[Magisk] mwzdalne:
🫤

redirect googles server to get modded bytecode which always returns true??

Sent from SM-S711B using ReLabs
[Magisk] mwzdalne:
just suggesting

Sent from SM-S711B using ReLabs
[Magisk] HippoMan:
One other thing which DroidGuard does during its integrity checking is to communicate with the Googlefrinchian server. This is done with cryptographically signed messages, and the bytecode itself is also cryptgraphically verified. Therefore, modded bytecode would not be able to successfully communicate with the server, and such integrity checks would fail.

If our Android devices were advanced quantum computers (more advanced than anything in existence today), then perhaps the cryptographic verification itself could be cracked in real time. But we're totally out of luck for such a thing to occur with today's technology.
[Magisk] mwzdalne:
oh.

😢😢😢

Sent from SM-S711B using ReLabs
[Magisk] mwzdalne:
how's the work on bypassing the checks?

Sent from SM-S711B using ReLabs
[Magisk] HippoMan:
Sadly, the work isn't functioning too well any more because of the ongoing updates to the Googlefrinchian Integrity-checking mechanisms. A couple months ago there were literally hundreds of spoofed property fingerprints which worked to enable DEVICE-level integrity. Now, most of them have been invalidated, and now there are only 70 or so.

Also, recently the Googlefrinchians enabled checks on custom ROMs, and now, any such ROMs that are not signed with production keys are now invalidated. Many current custom ROMs are signed with test keys, and these now fail.

It's possible for ROM developers to sign the ROMs with production keys and re-release newer versions of the ROMs, but that's a lot of work, and also some custom ROMs that are in use are no longer supported by their original developers.

Another recent issue is that RCS message communication is now often failing on modded devices. The ultimate solution to this is not yet determined, and it isn't known definitively yet as to whether this will even be solvable. All we can do is hope and pray that someone discovers a workaround.
[Magisk] popieee:
need android 8.0 :(
[Magisk] zgfg:
No. It is IN ORDER for Wallet payments - Wallet requires Device Integrity and it will work

What Google is doing with RCS now is different story and changes almost on daily basis
[Magisk] popieee:
should work on android 7 :(
[Magisk] zgfg:
If you have a built-in mechanism to pass Device Integrity in your ROM, then better don't use additionally the module - it will not help you to 'better' or 'double' pass - to the contrary, there is a chance one will mess with the other and you will not pass at all

Or, if you still want to use the module, then make sure you disable the spoof mechanism fron the ROM forst
[Magisk] zgfg:
Really?!

You have tested those eg 77 and only 3 of them now only pass Device Integrity?

Or you mean only 3 are good for RCS - you have tested with RCS or what?

Or maybe you got it from the Googlefrinchians😁

If not, please don't rise the panic
[Magisk] Stаr:
He corrected himself a couple pages after:
[Magisk] zgfg:
Couple of comments

1) With the prints from your own phone PI would force Strong Integrity and you will fail that. PI would not then mind to test Device Integrity - already knowing that your phone is modded

That's the reason why you need a specific prints to fool the PI to test instead Device Integrity, and then that those prints would indeed spoof the Device Integrity

2) What you get here by the gen script are not your stock prints - Model cannot be ... arm64

I will not go into the details here (why do you see that on your Xiaomi...), but I can suggest you to take a look to the Fingerprint, Model, etc from your /vendor/build.prop. There you should find your real prints that must work for Strong Integrity but if you didn't unlock the BL

With your unlocked BL you would not pass more than Basic Integrity with them

Besides, if your stock prints would be 'good' (for the unlocked BL), then why would you use the module to spoof/replace that same original prints with them same themselves (extracted from the same ROM)?!
[Magisk] zgfg:
Yeah but stillI don't agree with rising that panic about 'Googlefrinchians', with or without the grounds in real facts

And I'm maybe sensitive on that bcs I know who really tested them and who didn't (although being available there to test) 😁
[Magisk] cabagekiller:
I wonder if the fingerprint from my nexus 6 would work? Or is it a fingerprint is for all of the devices of that model?
[Magisk] passionicon:
Someone here told me it's 1 fp for all devices in the model. I was gutted
[Magisk] zgfg:
It has been mentioned in this thread several times that out of tens of thousands prints from various vendors, models.and their OTA versions only up to 80 are still good to pass Device Integrity on the (nodded) phones WITH UNLOCKED BOOTLOADER

That are the results from the hard tests

Now, count the chances for the prints from your particular ROM, one vs thousands

(Even, for those ~80 working prints, there are usually only the prints from one specific OTA version..Ie, you take the prints from the same phone model but from the OTA version a month newer or older, and they will not work for spoofing)

Or, how somebody else could tell you if don't specify the prints - but then, just extract and test yourself and you would know

But again, chances are so slim. And if you don't already pass Device Integrity on that same ROM, on your phone with unlocked BL, then you basically know the answer - if you spoof and replace that prints with the same themselves, that would not make any better
[Magisk] cabagekiller:
Yes I get that. But that is why I asked is it for all the devices that are the same model or individual.
[Magisk] osm0sis:
Neither, it's unique to the ROM build. Go read the FAQ please.
[Magisk] HippoMan:
I just usually call them "Googlefrinchians". I happen to like that nickname, irrespective of what the circumstances of the reference to them might be ... no matter whether it's positive, negative, or neutral. I also like to use the word "banana-ed" instead of "banned" in all cases, for the same reason.

In a private discussion, it was discussed that out of a certain set of 70-ish fingerprints, most were recently banana-ed, and only 3 remained. That's why I mentioned 3 in my earlier message.

After that message of mine was noticed, I was told in that same private discussion that there is a different set of 70-or-so fingerprints which are still working. That's when I corrected that earlier message.