RCS Wont Work about playintegrityfix HOT 38 OPEN

A few findings so far:

• The new detection doesn't seem completely rolled out to Messages, and/or Google might be A-B testing it only on a portion of users.
• The checks on the Google Play services/DroidGuard/SafetyNet/Play Integrity side all outwardly seem the same as before (e.g. nothing added to the checker app verdict responses), so whatever's changed seems to be dictated by and possibly checked on the Messages side.
• RCS silently fails initially, then eventually it'll start showing "Text message" in the entry box, "Texting with (SMS/MMS)" and "Resent as SMS", etc., though may still show "Connected" in settings.
• RCS fails specifically using the current public mass-use Xiaomi.eu print (griffin), even though that print otherwise passes Play Integrity and SafetyNet verdicts on most devices currently.
• Other privately found passing prints still work, e.g. I had a user switch back and forth from griffin to a different print I supplied and RCS consistently worked with mine and broke with griffin.
• To test the user found that disabling RCS, changing print, then rebooting, enabling RCS again and waiting (a while) for it to provision was sufficient. No need to wipe or downgrade anything.
• Some report using an old known banned print (i.e. passes SafetyNet, but no longer passes DEVICE with Play Integrity) will get RCS working, though of course Wallet will fail. Note my tester couldn't verify this actually works.
• Using a PIF module with no json, or no PIF module at all, will still fail RCS though it might pass BASIC with Play Integrity like a banned print does.

One thing I'm curious/concerned about is whether this represents a new "shadow ban"/"restriction" system (beyond just "working" vs. "banned") on some prints even though they show the same in checker apps, since the griffin print was also reported to recently start failing DEVICE with Play Integrity but only on some older Android version ROMs/devices.

from playintegrityfix.

Confirmed. Google Wallet working and passing every integrity check except the strong one. RCS shows as connected but it is effectively disabled.

from playintegrityfix.

Confirmed here. Has been happening for approximately 36-48 hours. Uninstall updates for Google Messages works briefly but quickly reverts to SMS. Play Integrity passes, Google Wallet works, RCS status is "Connected", but no messages are transmitted via RCS.

This was previously noted about a month ago on many Android blogs, but only for users that didn't pass Play Integrity. The module was updated and it's been working since... until now.

from playintegrityfix.

I tried changing my pif print and rcs works for now, it was set to griffin before

from playintegrityfix.

did they break it again today?

from playintegrityfix.

I tried changing my pif print and rcs works for now, it was set to griffin before

I'm familiar with changing the print, but what is this griffin thing everyone keeps talking about?

Griffin is Moto Z. Its what Xiaomi EU (custom rom) is using to for their print

from playintegrityfix.

So ive fixed it. the solution was to go into the settings app, and under the google account settings there is a hidden tab for mobile data and messaging. while on data only i had to toggle auto verification off and on, after having turned off the deny list, used the may version of messages with latest play integrity fix 15.9.7 and shamiko, as well as clearing data for all play services and carrier services, then i was able to verify rcs and it finally works. fuck google for hiding these settings

from playintegrityfix.

It just broke again for me today. google must be rolling out the break again.

from playintegrityfix.

from playintegrityfix.

I would like to see what happens to someone who is on an old device and not faked fp. If it fails for them, perhaps it got switched to strong integrity. Honestly subscriber info is accessible on android, we could feasibly send third party RCS messages so it would not be the end of the world, rip e2e tho.

from playintegrityfix.

Been down for me since night of March 28th or morning of March 29th... Tap to Pay Setup everything passes...

from playintegrityfix.

Happening here too. Was able to get it back a couple times for a few minutes each time but then it just switches itself back to SMS/MMS.

from playintegrityfix.

Same here. Note that messages are sent as RCS, but fail.
Maybe Google is using MEETS_STRONG_INTEGRITY this time? Would be surprising considering that Google Wallet/Pay is still working fine

from playintegrityfix.

Do you know if RCS will stay working if you switch back to the griffin print?

If this is specifically targeted at the Xiaomi print, then this would basically be banning a custom rom right?

Can we pass in a fake print to RCS only?

from playintegrityfix.

I answered that already. Switching back to griffin will eventually fail RCS again. The print doesn't belong to Xioami.eu, they and chiteroman are just the ones using it en masse... Please check my findings comment again in case you missed some edits.

from playintegrityfix.

Right i was just a bit unclear so wanted to make sure on the RCS re break thing. Xioami makes MIUI which is a popular custom rom right? Which is why I was assuming google wanted to target them specifically, an alternative is google wants to target.. us.

Perhaps someone will make a third party RCS app...

from playintegrityfix.

So if they did switch to strong integrity, anyone with a modded Android is pretty much screwed now in terms of RCS. Sometimes I wonder if it's worth it anymore. My main reason for rooting was to have my theming apps to make things look like I want them to. I'm considering that maybe it's not worth the trouble if this is gonna be a reoccurring thing now.

from playintegrityfix.

It's very clearly not linked to STRONG, go read my findings comment above please.

from playintegrityfix.

Could we maybe install an alternate version of Google Messages to get around this? I doubt it, it's probably server side, right?

I did try reverting to the factory version on my Pixel 8, which happens to be Google Messages from May of 2023, and like @blackwind mentioned, it worked for a few moments, but ultimately failed again.

I tried doing what @osm0sis said and disabling RCS, changing prints, rebooting, and enabling RCS again, but it's been hanging on setting up for about ten minutes now. Every other time I've tried to enable/disable it's only taken about twenty seconds to set up.

Would love to try anything else if anyone has suggestions.

from playintegrityfix.

My tester waited overnight generally for the provisioning to complete. But he only tested the restricted griffin print, a working one, a known banned one, and none at all. 🤷‍♂️

from playintegrityfix.

I tried changing my pif print and rcs works for now, it was set to griffin before

I'm familiar with changing the print, but what is this griffin thing everyone keeps talking about?

from playintegrityfix.

I tried changing my pif print and rcs works for now, it was set to griffin before

I'm familiar with changing the print, but what is this griffin thing everyone keeps talking about?

Griffin is Moto Z. Its what Xiaomi EU (custom rom) is using to for their print

I have a Google Pixel 8. Can I do anything, or just keep trying to use the FP Downloader app through playcurl?

from playintegrityfix.

I changed nothing today and suddenly RCS is working again... Will continue to investigate

Device: Pixel 8 Pro

from playintegrityfix.

There are numerous reports that the griffin print spontaneously started working for RCS again this evening. Nothing to investigate. Just hope it stays working and that Google's ended the experiment for good.

from playintegrityfix.

Yes it's back for everyone, for now... no need for further confirmations.

from playintegrityfix.

mine is stuck on "setting up" for rcs and my myaccount.google.com/phone says auto verification is pending for a day now. despite this fix probably working for everyone else i think Google or my carrier blacklisted me for trying to verify too many times. any ideas?

from playintegrityfix.

@AlexS2412 I tried what you suggested, and mine is stuck on verifying still. I'm on a Pixel 8. Not sure what the deal is. I'm running PIF, playcurl, and Shamiko.

from playintegrityfix.

I was also experincing this issue but google messages updated this morning and RCS chats seem to be back. Ill comment again if it stops working again. The update is version 20240312_00_RC02

from playintegrityfix.

I just checked my messages and RCS is back between me and my dad. I know he didn't update any modules on his phone, so Google must've pulled the plug on the experiment, at least for now.

from playintegrityfix.

@AlexS2412 I tried what you suggested, and mine is stuck on verifying still. I'm on a Pixel 8. Not sure what the deal is. I'm running PIF, playcurl, and Shamiko.

FINALLY working. Tried updates/downgrades to Google Messages, both beta and no beta. New FP, cleared data of Google Play Services, added Google Messages to my deny list and upgrade Magisk to Canary.

Not sure if anything I did actually mattered, or if it just decided to work.

I'd say Google's experiment was successful. I assume they will turn this back on at some point and screw all us rooted users over. Hopefully we can figure out a fix, but I'm doubtful. It's getting harder and harder to deal with the consequences of rooting.

🎵 Wish we could turn back time, to the good old days 🎵

from playintegrityfix.

@BrodyStone21

FINALLY working. Tried updates/downgrades to Google Messages, both beta and no beta. New FP, cleared data of Google Play Services, added Google Messages to my deny list and upgrade Magisk to Canary.

Not sure if anything I did actually mattered, or if it just decided to work.

I'm on the Google Messages beta. Updating it to the latest release (from 3 days ago) was all I needed to fix RCS.

from playintegrityfix.

@AlexS2412 I tried what you suggested, and mine is stuck on verifying still. I'm on a Pixel 8. Not sure what the deal is. I'm running PIF, playcurl, and Shamiko.

you can't use playcurl. it just auto installs a pif. go manually delete the pif in /data/adb/ then use play integrity module and shamiko. make sure to clear data on all things that failed integrity like messages, then go into google account settings to toggle off and on the auto verify toggle. this last step is the crucial part as half of their check was network based somehow and depended on both google and your carrier verifying your number.

from playintegrityfix.

Is RCS working fine for everyone on the latest update from two days ago? Not sure what's changed, no update notes from Google. I don't want to mess anything up by installing it.

from playintegrityfix.

Adding it to the deny list with shamiko fixed it for me

from playintegrityfix.

It's not broken anymore, it's back to only needing to pass DEVICE from any working print including the griffin print in Xiaomi.eu/PIF.

from playintegrityfix.

Oh, weird.

from playintegrityfix.

It's the common public print that got banned. Update to the latest Xiaomi.eu one using my autopif.sh and you'll pass attestation again, and RCS will work:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-387#post-89233630

from playintegrityfix.

from playintegrityfix.