yashsingh1/xdaforums huggingface dataset:
[Magisk] Slayde.K:
Yep unfortunately after about a month of working RCS just broke again for me as well :/

It's such a pain in the butt they are doing this because it doesn't default to SMS when it stops working.. and even if I set it to SMS it doesn't update for others texting me so their RCS messages just never come through.
[Magisk] Vision:
Displax v2.4.0-MOD_1.3 have riru, my request and he did, with some modification, maybe still work in older devices and with some riru hide module
[Magisk] Redn2000:
I'm sadly in the same state as you. I had a few people switched over to signal thanks to the SMS option, but they all dropped it once SMS was (stupidly) removed. I can't see myself moving away from root though because of all the useful features. If you're interested in another alternative, I've been looking at Deku-SMS, though it doesn't seem to currently have wifi texting and is less user friendly. And the fossify team are looking at RCS for their fork of Simple Messages.

Here's hoping another Integrity Fix update will fix these issues so we can keep using RCS.
[Magisk] osm0sis:
No... The print is banned...
[Magisk] Vision:
For that i said with some modification, if we can change the print insid in the classes.dex
[Magisk] ki4mor:
At what point do we have to make some kind of service like Bluebubble to forward RCS from an authorized phone to our rooted ones like I do with imessage. It's sad to see Google going the way of Apple and starting to try and wall garden their services for "Security Reasons" *cough cough* control *cough cough*
[Magisk] kornball:
Yep, same here on my P7. For about 5 minutes I thought it was an issue with the recipient, but then it dawned on me to check this thread. So incredibly frustrating.
[Magisk] Captain_Throwback:
Can you confirm that your RCS messages are actually sending and being delivered (and not just RCS showing as "Connected" in Messages Settings)? I just checked my device, and although I'm able to send an RCS message to my wife (since I have Strong Integrity), it's not actually getting delivered to her, as she's only passing DEVICE (last I checked - she's using the XEU print).

It could just appear to be working, while actually not. Just want to confirm, since this seems like a new problem.
[Magisk] zzzeros:
RCS not going through

Passing Basic and Device Integrity

Wallet working

PIxel 8 Pro 240105.004

Magisk 27.0 27000

Play Integrity Fork, osm0sis v8
[Magisk] kornball:
This is what's happening to me. My phone is passing both device and basic. Messages says it's connected to RCS, and individual messages show as sent/delivered, but the recipient never receives them. The same vice versa - I never receive RCS messages even though the sender's phone shows them as sent/delivered.
[Magisk] osm0sis:
Yeah I constantly RCS message with my wife and it never stopped working, even on Feb 29 before I noticed the fail and switched to the XEU print until I could find my own again.
[Magisk] Redn2000:
Just tried installing and using Shamiko for the first time (enforce deny list is off now) and sadly there was no change. I made sure to choose play services, play store, and the Messages app itself for the deny list with no success even after clearing cache of these apps. I also doubt my OP9Pro is listed as unsupported for the integrity check so this is even more strange...
[Magisk] zgfg:
Play Services will be removed from DenyList by PIF.

And Play Store just tests over Play Services, hence no need to be put to DenyList

I dunno does RCS app need to be in DenyList, I don't use RCS
[Magisk] Vision:
For safetynet with new FP from current Xiaomi.EU

If anyone with Android 7 or below Android 8 with riru want test it, i have modify some parts, and test it in emulator with 7 and original Magisk to be sure the zip flash proper.

I don't have rooted device with 7 to test it unfortunately.
[Magisk] joefuf:
Interestingly, this was the first time that Messages defaulted to SMS for me when RCS broke. Historically, when my fingerprint would get banned, I wouldn't know until I went to send a message to my girlfriend and it would do the whole disappearing act thing where a message moves into the thread and then just disappears. This time, I was minding my own business when I got a duplicate text from my girlfriend. It had come through as RCS just a few minutes earlier, but came through again as SMS. I thought it was because her phone was linked to her Android Auto which sometimes sends messages as SMS, but she said she was still in her office.

View attachment 6085704

No changes from my end to precipitate this. Didn't update or change anything. Still passing Device and Basic Integrity. Sounds like the same problem the rest of you guys are having.
[Magisk] osm0sis:
Only gets removed if it's enforcing.
[Magisk] bentree:
I think RCS has different rules depending on region. FYI my RCS has died, running Osm0sis V8, basic and integrity both passing. I'm wondering if they have allowed RCS to check if the pif that gms is using is the same as what the playstore pif says. It would be the easiest way for them to detect any "Modding".
[Magisk] GabbyWC:
The disappearing act of RCS messages is back and this time it's happening even with device integrity passing. I already had the Google Messages app on my (not enforced) DenyList for use with Shamiko. My phone is running PixelOS 14 with Play Integrity Fork v8 and the public fingerprint. It sounds like private fingerprints are still working with RCS based on some recent posts. If that's correct, we can rule out a strong integrity check as the cause of the current RCS issue.

As determined as I am to stick with custom ROMs, my Redmi Note 9 Pro's touch screen no longer responds at all. I have to use an external keyboard / touchpad / air mouse remote with it until I buy a new phone which will probably be the upcoming Poco F6.
[Magisk] freeza:
Broken for me too. Rip
[Magisk] bentree:
For me they don't "disappear". I just get an error that the message can't be sent. That and I don't receive any RCS messages from other people. Have turned RCS off for now.

I am using the public key, have tried finding a private one but since the mass ban I have had no luck at all.

Before that it only took me a day to find half dozen working keys but now I can't find any after about a week of searching.

Would someone out there who has a few working private keys, consider PMing me one so I can test to see if that fixes the RCS not working?

Cheers, Bentree.
[Magisk] kudichode:
Deleted the post. Mod edit destroyed original message anyway
[Magisk] murdered by aus fbi:
Thanks
[Magisk] GeTex:
Adding in, I appear to have lost RCS sometime this morning, as we are once again experiencing the inability to send RCS messages :(

Honestly this is really kinda becoming sad
[Magisk] RAZINARES:
So, RCS is broken for everyone. I have tried all magisk hide methods, stock rooted isn't working neither is custom rom.

Sent from Pixel 7a using ReLabs
[Magisk] TKruzze:
View attachment 6085757

Same here on P7 in the U. S. Can't send or receive RCS even though it shows working.
[Magisk] Daimyo4:
Yep, not working on my Verizon Razer Phone 2. Started getting "message not sent" at around 2pm est.

Google has really been plummeting to the depths lately. All I'm trying to do is use my perfectly functional phone for longer than 2 years like the rest of the population. The greed of tech companies have no bounds.
[Magisk] Captain_Throwback:
I'm still baffled by this since it seems to be broken for everyone else...any idea why yours would be working and no one else's?
[Magisk] rom4ster:
Anyone on an ACTUAL old device that only can pass DEVICE verdict (not faked fingerprint?)
[Magisk] pershoot:
Confirmed, RCS is now broken (again); DEVICE and BASIC passing; Wallet working (I just used it a short while ago).
[Magisk] bentree:
A few people on other threads are reporting that it still works for them. It must be a region/area roll out. Will be interesting to see if overtime everyone ends up with no RCS.
[Magisk] Captain_Throwback:
It would make sense, then, to gather some empirical evidence to substantiate that hypothesis; perhaps we can try and find commonalities between the people for whom RCS is broken, and those for whom it's still working?

There must be a common denominator for either case.
[Magisk] chiteroman:
Maybe Google checks for a valid certificate chain, or just requires Strong integrity.

This RCS changes are weird...
[Magisk] chiteroman:
Someone with old device (without hardware attestation) can check if it's working ?
[Magisk] bentree:
I have been asking people in other threads, trying to gather data but it's not a fast process.

Cheers, Bentree
[Magisk] bentree:
Nope not require strong as my partner has a Sony 1ii that is locked but doesn't have "strong" her RCS is still working for her.
[Magisk] i5lee8bit:
Wanted to throw in my 2 cents and some insight. I don't even use RCS but... someone in a certain kernel testing group told me about the public XEU prints getting burned so I decided to check out this thread, only to find the issue is specifically about RCS.

So... I switched to Messages (eww) and enabled RCS on 2 different phones (both rooted, one is Pixel 8 Pro latest March A14 update and other is Pixel 4 XL latest ofw is A13). However, I'm USING MY OWN PRIVATE PRINTS for all my own devices. RCS is indeed working perfectly fine on them. Says it's using RCS encrypted, read receipts work and all... maybe it has to do with the print being used? Anyone wanna try logging and seeing if Messages or another dependent process is digging in somewhere with additional checks?

I shared an extra private print (as little I have these days) with the group and afaik the guy's RCS is now working again now that he's not using the public XEU print. He said he rode that print as long as possible so as to keep the "traffic" on my private print low haha. So he definitely had working RCS and like the rest of you guys it stopped working today or yesterday or whenever. Unfortunately I don't know what carrier he's on.

Or maybe it does has to do with the region thing, I dunno, and just in case I happen to be in the USA on Xfinity Mobile (a Verizon mvno).

Considering @osm0sis is 100% using his own print, I'm more inclined to think this has something to do with the print being used itself. Almost like Google saying "ok, these ppl wanna use an easily available PIF config? Fine, we'll find new other ways to screw em over!!". Although I'm totally lost about him saying it's continued to work during previous "bans" but again I don't use RCS normally so my thoughts on this are already shallow. But anyway tldr I do think a good place to start would be seeing if Messages or another process is doing checks on PIF related stuff.

Edit: I use osmosis Fork v8
[Magisk] Ultimoose:
For whatever it's worth data point wise - it broke today in the midwest of OK on my P8P around 1:30 p.m. CST on TMO.

it was a staged breakdown. On each thread it still said encryption was on under details and I had a list of encryption codes but my codes didn't match my girlfriends, she had roughly 8 more sets of numbers than I did, my last one was on her second line of numbers so it appears I stopped getting matching keys.

I was able to reconnect, turn RCS on and off and the thread with my son still showed RCS in the text box but it was the only one out of 8 threads that had been working.

Now while RCS is turned on and I can disconnect it and reconnect it on the Messages settings and it says it's on there, on each thread's details I get "Encryption is not available to you" and there's no encryption codes listed.

Seriously at this point eff google.

And I wonder if this bull**** is something to do with google announcing Apple will be supporting RCS in the fall. As in Apple demanding they break it on rooted phones or they won't support it.
[Magisk] i5lee8bit:
Anyone who is using a custom / their own (non-XEU) print that also has it failing? I've seen just about everyone with broken RCS saying they're using XEU print, but other than me and @osm0sis (and @Captain_Throwback with his obnoxious STRONG 😝) using our own custom prints still has RCS working...
[Magisk] bentree:
And yet to confuse things I have someone on another thread with 2 different devices, both running public pif and one has RCS and one doesn't. So there goes region theory. :(
[Magisk] GeTex:
As a weird update, my old nexus running android 8 with play integrity fork does have RCS working again. My pixel running 10 does not with identical settings.
[Magisk] BunnyPig1:
If Apple would be a factor in this and really pushing "banning" rooted devices from using RCS, I don't think Google would ban one fingerprint from RCS. Apple would never agree since there are ways around it (for now with private fp).

If Apple would be a part of this, they could simply tell Google to ban all fingerprints. It's been an entire month now since the last ban-wave.

At this point I'm more leaning towards the theory that Google prefers all devices with unlocked bootloader (and older devices trying to pass PI DEVICE) to be on the same fp for some weird reason (easier to track?)
[Magisk] kodycdrews:
This is probably just a coincidence, but Apple music had an update a couple days ago that added a root checker. Kinda makes you think maybe they do have a hand in this...
[Magisk] albinoman887:
I'm a custom rom dev. I'm trying to work this out too. can you guys pm me and we can work this out together maybe?
[Magisk] bdr127:
Is there an easy way to check if RCS is working in Messages (since the "Connected" msg is apparently meaningless) if you don't know anybody with an Android phone using RCS? Literally every single one of my extended family members, neighbors, and friends all have iPhones... :rolleyes:
[Magisk] Redn2000:
Just wanted to chime in here and say that I've only been using my own print thanks to the guide from osmosis and am still getting the RCS error while passing basic safetynet. So not sure if there's a common denominator with why his is passing but mine and others' aren't in that regard at least. With that said, would me generating the print using his guide again help in this situation?

I'm also not using his fork, so maybe testing with that is in order?
[Magisk] pndwal:
Point is, why would Devs or users want Riru support, especially since 26402 Magisk?...

And RiruHide was only ever integrated in Riru itself (from 22.0+) AFAIK... A new separate hiding module was needed for Zygisk because it's part of Magisk which no longer manipulates signals or traces for hiding purposes since 23010. Zygisk hiding is, of course, developed (although stalled ATM) in Shamiko by the same Devs that were behind native bridge refactoring in Magisk.

Of course much of the work of @RikkaW (and Canyie, Shana, others) is now assimilated in the new integrated hooking/injection framework that is Zygisk, and her name on Magisk App's main page is a tribute to that work from yesteryear.

👀 PW
[Magisk] albinoman887:
where is this guide
[Magisk] osm0sis:
I'll see tomorrow if RCS is still working for us since she's gone to bed and I am now too. Was working as of noon ADT today though. A message I just sent her looks by the icons on my side like it was received. 🤷‍♂️
[Magisk] pndwal:
Please say what you mean by 'basic SafetyNet'... It's not clear if your print set is even working. 🙃 PW
[Magisk] shoey63:
RCS working on 2 phones here in Australia which have different custom prints on each, both passing DEVICE integrity.
[Magisk] bentree:
Lucky! Mine stopped about 4am this morning in Aussie land. Great start to the weekend :(
[Magisk] rom4ster:
I think it would be helpful to post the messages app version and possibly gms version.

for me GMS: 24 09 14 190400-617895654 version code 240914038

Messages: messages.android_20240308_01_RC04.phone_dynamic , version code 226291063

FURTHERMORE wallet is working which is why this is strange.
[Magisk] Samg381:
I am back to being shadowbanned from sending text messages on the device I own :)

https://www.reddit.com/r/androidroot/comments/1b36hij
[Magisk] Nergal di Cuthah:
I think that's more to do with anti piracy than anything else
[Magisk] freeza:
Created a custom print and rcs is back. So yeah it's def the xiaomi one that's now burned
[Magisk] s1dest3pnate:
Is it possible they just hard banned the devices that used one of the banned fingerprints previously since they know we have been working around it with different fingerprints.
[Magisk] s1dest3pnate:
Oh good to know. I need to look up how to do this. We need to use osmosis steps?
[Magisk] YHMWU7Rc9TkDAtu4NT6:
What does "Created a custom print" mean? Changed something so the output of uname -r is not on the naughty list ?

Never mind, getting rid of Google Messages completely.
[Magisk] zgfg:
Or (also) different devices/setup/environment?
[Magisk] zgfg:
Basic SafetyNet?

Relevant case would be that you pass Device Integrity from Play Integrity.

Then, see above, for some having that RCS works (private prints), for some not (using public XEUnprints)

So, you have to use that guide and find the prints that pass Device Integrity. Finding prints that just pass SN Basic is trivial, there are thousands of prints satisfying
[Magisk] partoD:
thankyou very much sir it worked Realme 5i A13 Banana rom🤩👌
[Magisk] trevtdogg:
so are we thinking that griffin has been banana-ed for RCS but not for NFC?

as someone who only wants device integrity to get NFC payments working, if that's the case then hopefully griffin flies under the radar for a while now!
[Magisk] BROKEN1981:
View attachment 6085818mine is working. Using a custom print
[Magisk] GeTex:
This does not indicate RCS is working, send a text to another RCS user, if it's working it will send, if not it will simply say "failed to send"

Update to all: extracted some more fingerprints, changed mine and RCS is working again. Can verify the public print is indeed banned. I also don't pass device checks because of my kernel and the person who wrote my kernel is unlikely to unbrand it as it's an older device so I haven't fixed it myself. But Device is not required to use RCS. I can only conclude Google is checking the prints in the messages app and not actually checking for device integrity. I have multiple devices failing device but working with RCS.
[Magisk] flobo09:
Ok google won. I'm unrooting & getting another device for root.

I can live with google pay breaking here and then, but having basic messaging communication break every few weeks is something i can't work with.

Especially since they did it in such an evil way where it doesn't even fall back on SMS before you notice and might miss messages all over.
[Magisk] pndwal:
The Forbes article cited way back here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89378516

with it's Reddit article link established that spammers are already abusing modded Android devices and made the connection between automated spamming (automation allowed by modding along with all the extended multimedia and more capabilities of RCS) and how Android mod abuse would/could affect all mobile users incl. IOS with RCS, also the likelihood that Apple wants all RCS content to originate from "walled garden elements of [the] ecosystem" like their own. 👀 PW
[Magisk] HippoMan:
These "integrity" trends are motivating more and more people to purchase a second device, so that they can have one that's pristine with a locked bootloader, etc., and another one that can be modded.

This will increase the sales volume for mobile devices, and it therefore benefits investors in the companies which manufacture these devices.
[Magisk] bombadier:
Just reporting that RCS has stopped working for me, using the known print, still passing device/basic and Google wallet works, tried adding all the parts of messages to the denylist, rebooted, RCS tells me connected but can't switch to RCS messages and not receiving any sent from an unrooted pixel 7a,in the UK but can't say when RCS stopped working, just I noticed today

Version messages.android_20240321_01_RC01.phone.openbeta_dynamic

com.google.android.apps.messaging
[Magisk] Dark_Eyes_:
I also came to the conclusion that Messages don't rely on Play Integrity at all. Last time I tried to find a working print (after the mass ban), I got RCS working with a print that failed Device Integrity. I ended up using XEU like everyone else because I couldn't find a working print for everything in a timely manner. I guess XEU will get banned for Play Integrity at some point, but would it be possible to have PIF spoofing different prints to Messages and GMS, at least for now?
[Magisk] sawdoctor:
For all i feel your pain and need to rant at Google (I fee exactly the same) our modding community is so small no Google do not care if they lose us.

There's so few working prints now most of us still haven't found one no matter how hard we've tried. Hopefully xaiomi.eu will update thier print for us
[Magisk] Sheist!:
My 2nd keeps me from losing any communication time, and it's use as a hand computer, but reflashing takes so little time now. Both are unlocked with custom ROMs. I love testing new ROMs while one stays the daily driver. I see HyperOS is now out, but I'm not going back to stocks. Even if root becomes compromised for banking apps in the end, I still want it.
[Magisk] Vision:
Same here, Sony all stock, locked and without root, pass 2/3, and the RCS working

but and my Xiaomi all stock unlocked and Kitsune still works
[Magisk] Dark_Eyes_:
I can confirm that using the first print I found makes RCS working again without Device Integrity passing. So spoofing different prints to different system apps could be a way out for now @osm0sis .
[Magisk] ardiesel:
View attachment 6085880

We should all be sending feedback.
[Magisk] Link2811:
Yeah I was planning to get the 9 Pro but now, I think I will get something else.

The saddest thing for me is that I'm root for only one, tiny reason. It's the fact that you can't hide that awful navbar to get a true full screen.

All this hassle for something so simple for Google to patch...

Thanks Goog ! (y)
[Magisk] pndwal:
But Messages processes should be seeing native props (which should be fine) currently since PIF spoofing targets GMS... So seems likely that backend for GMS is passing the print set data to Messages back end or else apps may communicate on device. 🙃 PW
[Magisk] Vision:
If the DroidGuard send like you say back to Messages the info and we have spoof FP, and the app Messages see the original FP, after something in Google server intersects the 2 different FP and this make it fails, maybe something like that ?
[Magisk] HippoMan:
But what about all those Telephone Sanitizers who'd be out of work if the Googlefrinchians stopped all these "security" efforts?
[Magisk] badabing2003:
Interesting theory, but that should also fail RCS when people change the print, which is not the case.
[Magisk] pndwal:
There's many possibilities, and only much experimentation or some capable reversing may clarify what's really happening.

Of course it would have been very easy for Google to perform such cross-checks to prevent all PIF spoofing all along, so the fact that they've restrained themselves does seem to indicate almost that they're making some effort to accommodate the modding community at least until banks etc begin requiring STRONG_INTEGRITY with all it's implications... Maybe RCS development and it's cross-platform security standards and compatibility simply couldn't wait that long...

Personally, I think The kind of rhetoric seen above (eg calling such decisions 'evil') isn't helpful, shows lack of appreciation for complex considerations that must be made to facilitate progress, and may actually result in causing big G to become less benevolent and more malevolent towards modders. 😬 PW
[Magisk] Vision:
Yeah i get your point, because i think Google not did yet cross-checks to prevent all PIF spoofing all along, in this way, lose money and customer 😂🤣

And as understand the rest is another headache for us 🤯