yashsingh1/xdaforums huggingface dataset:
[Magisk] GabbyWC:
Does the RCS breakage happen even if that old version is not updated? I've considered downloading previous versions of Google Messages from APKMirror (working backwards from the current version) and disabling updates to see if RCS keeps working. My phone is defective as it is, though, and RCS isn't an important enough feature for me to spend much time on. I'll stick with Telegram for its better features and versatility.

Download Google Messages APKs for Android - APKMirror

Download Google Messages APKs for Android - APKMirror Free and safe Android APK downloads

www.apkmirror.com
[Magisk] Tornado15550:
I decided to disable Google messages and switched to Textra. RCS is not worth all this hassle for me only for it to break again in the future. I'm not going to unroot my phone to make a texting app work properly. If Google wants to reduce RCS adoption, this is a great way of going about it IMO.
[Magisk] intel_core_i7:
Trading a few rooted & bootloader unlocked users for around 40-50% of smartphone users globally potentially is probably their best RCS adoption strategy.

Apple probably pushed them to do this.
[Magisk] GabbyWC:
I think this is a valid theory. It's already bad enough that Apple is such a shameless and greedy company. Google is also headed in that direction if these kinds of changes continue.
[Magisk] YHMWU7Rc9TkDAtu4NT6:
+1

Got rid of Google Messages yesterday.

Once (IF ) Apple fully adopts RCS , am moving to iOS. If I have to be treated like a child, belittled, and treated as a renter rather than owner , may as well be Apples fool for my daily driver. 😞
[Magisk] mackdacre:
If this is how it's going to be on Android, I will probably switch to iPhone. If I can't root (to block ads among many other things) and stuff and have features still work, well, they have that on iPhone, too, so I might as well have iMessage.
[Magisk] menuisier3:
Hello, despite the fix, RCS chat and France Identity do not work. Thank you all the same for your work
[Magisk] alecxs:
thanks to the help of @osm0sis we managed to include most of the play integrity stuff finally! any questions? ask here

Introducing the XDA DevBox - The Future of Development is Here

Update April 2nd: This was of course our April Fools' joke for 2024. Thank you all and be sure to check out our update here. The signature most mods had: The post: Fellow XDA Developers! We here at XDA are always pushing the boundaries of...

xdaforums.com
[Magisk] mackdacre:
I know it's an April fools day thing but I kinda don't get the joke
[Magisk] pndwal:
FWIW, we may get a better handle on what's required for RCS on modded devices once Google implementations stop breaking RCS on stock/locked devices.

Meanwhle, it seems apparent to me that (once again) big G isn't yet shutting down use of enhanced functionality like RCS messaging for mod users (even if they're playing around with print based restrictions ATM), and anyone who has a modicum of understanding about how device integrity works knows it would be a very simple exercise for them to shut all that down and much more if they wanted too... The time may well come when that happens, but why get excited until then?

Obviously while big G is still messing with the measurements they require for this thing to work, achieving consistent spoofs or other bypasses for the same is going to be difficult or impossible... And the cross carrier/platform initiative to include many more players including Apple has already spanned 17 years from it's proposal with (some) end goals still out of sight, so this is just another phase in the evolution of Google's RCS adoption and evolution.

Be patient folks... Read below for RCS history, to understand Google's investment in this thing (ie. making RCS a proper universal communication standard) and why it should (probably) be largely solidified (at least) by September at the latest. 😜:

Spoiler content hidden.

... And this is all deadly serious despite the date!... Hope the Big Picture helps... 😅 PW
[Magisk] pndwal:
Yeah, it's not funny to me either (big surprise), but I do want the XDAI NPU to replace my Sirius Cybernetics Corporation prototype personally drive... It's already rooted but it didn't help. ☹️

Don't talk to me about life. 🤖 Marvin
[Magisk] rodken:
Stopping and clearing the Play Services cache could be a more targeted approach compared to clearing the entire GMS app data, but on the other side of the coin, there isn't an official confirmation on whether clearing only the Play Services cache will prevent a full Wear OS reset. It's possible that the system might still trigger a reset due to underlying dependencies.
[Magisk] rodken:
Spite the fact that Android offers more built-in customization options compared to iOS. However, we all know that rooting unlocks even more options, while jailbreaking iOS is more complex and risky.

I suppose that if iMessage is somewhat of a major factor for you, switching to iOS might give you access to that functionality seamlessly with other Apple devices.
[Magisk] osm0sis:
Only thing I've ever seen actually needing to be done between testing different prints is:

killall com.google.android.gms.unstable
[Magisk] intel_core_i7:
At least iMessage and Apple Pay don't break when the iPhone is jailbroken, on Android on the other hand it's a constant cat-and-mouse game with increasing difficulty
[Magisk] psone:
Sonic is a business that uses RCS 877-282-7660
[Magisk] osm0sis:
Summary of RCS ban/restriction information:

chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

( Edit: Now deleted... 😠🤷‍♂️

Archive.org Backup: https://web.archive.org/web/2024040...tegrityFix/issues/297#issuecomment-2029934310

...And pasted for posterity...: )

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 tried but 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.
​

Thanks to @BillGoss for the methodical (as always) testing!

Edit: The above is from the original Mar 29 - Apr 1 (Easter weekend) apparent RCS ban/restriction test on the public Xiaomi.eu "griffin" print of the time, but it all seems to still hold true for the new May 29 onward RCS ban/restriction (test?) on the current public "sailfish" print.
[Magisk] Vision:
I want to test RCS with another FP beside griffin, but i have no luck to find a working one, i try the last month more than 500+ without success, some even basic not pass.

And i have retired from this for a little while, i need it for my health
[Magisk] sawdoctor:
We're all in the same boat unfortunately i think osmosis said there were something like 10 working prints left on the site we've all been using
[Magisk] majorfigjam:
What do you mean by official confirmation?

I have a Samsung watch 6 wear OS, and "officially" confirm that I never have to reset it when testing different prints on my Pixel if I stop and clear caches of Play Services and Play Store.

" killall com.google.android.gms.unstable " also works from terminal, if you prefer.
[Magisk] osm0sis:
Nah, ~30. Said so yesterday:

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

The other ~250 we have found are all from other places, none of which are from factory image/full firmware sites (which we never even got into by the way), so keep looking, they are out there!
[Magisk] Vision:
Yeah i know, very difficult to found just one for now.

I take time from search FP, because if continue, my health going down

0% in arm or arm64.

This mean only build.prop from a arm7?

EDIT: Now see is about TheFreeman
[Magisk] osm0sis:
What? That part was about pickaprint/PIFS, which is divided by architecture of donor device, so it should be pretty clear what I meant.

PIFS/JSON at main · TheFreeman193/PIFS

A collection of build properties for the PIF module - TheFreeman193/PIFS

github.com
[Magisk] Vision:
I forgot to read the most important part say is about the TheFreeman😂🤣
[Magisk] sawdoctor:
Any pointers you can give where to look? I'm happy to do the leg work but it's getting soul destroying trying to find one
[Magisk] KeplerK20:
I have a Oneplus 3 Rooted with Magisk with Zygisk enabled.

Android 7.1.1

Oxygen OS 4.5.1

Which PIF Version shall i use for my device as the latest version is not getting installed (gives error that cant use this module with android < 8.0)

Kindly guide
[Magisk] osm0sis:
There have been several other sites mentioned in this thread previously that have the required info to make a working print, some with just build.prop pastes, some with just fingerprint/security_patch info.
[Magisk] Vision:
Try this
[Magisk] markfm:
That's what I've been seeing. I paste the following in a terminal app (Termux for me, others work fine too as long as they've been granted root permission):

su -c killall com.google.android.gms.unstable

(In Termux, if testing multiple prints just flip to Termux and press the up arrow to have it pull in the command again)
[Magisk] badabing2003:
Clearing cache is not the issue with watches, try clearing Play Services data and come back and tell us if your watch still stays synced.

CAUTION: You're going to have to setup your watch again.

And clearing cache by itself doesn't do any good for the PIF/RCS testing.
[Magisk] TotallyAnxious:
Or you'll have to reset your watch 4 times to get it to work again. That was a terrible experience.
[Magisk] s1dest3pnate:
How can I tell that the custom.pif.json that I have in /data/adb/modules/playintegrityfix is actually being used? I've changed my FP a couple times now but RCS is still stuck on "Trying to verify" and I'm getting the feeling that my FP changes aren't taking effect (I've been rebooting in between changes), and my integrity check in Play Store does not look any different.
[Magisk] sawdoctor:
Or just use pixelflasher if you don't like using terminal commands
[Magisk] me_droid:
I'm still limping along with RCS using the Griffen print. The following is andecdotal but may be of interest. I have only one contact, a work colleague, who could only be messaged via RCS. So I had intermittent issues messaging with him based on the back and forth with Google banning prints and locking down (or fubar'ing) RCS. He has an S21 and was using an app called "Messages". Not sure if it came as default on his phone or he downloaded it but I asked him to show me what he was using. Google Messages wasn't even installed - I asked him to try it out and then when texting back and forth it defaulted to SMS. He says his family, all on iphone, were having issues with texting him as well and this was going on for at least a year! I bet that problem goes away for them too. Apparently this "Messages" app only used RCS - we looked through all the settings and couldn't find any way to switch it off or have it bounce to SMS if RCS failed. The icon for the app is below. I'm leaving RCS turned on as long as it works in case anyone else who only uses RCS tries to text me. If you've only got a handful of contacts that you can only message with RCS and you're in a position to ask them, you may want to ask what messaging app they're using. I just assumed that most Android users would be using Google Messages.

View attachment 6086763
[Magisk] majorfigjam:
I'm fully aware of the issues with clearing Play Services data - my response was to a specific question about clearing caches only.

And yes, after one extended batch of testing recently, I needed to clear Play Services data, and then had to go through the full painful reset of Wear OS.
[Magisk] osm0sis:
Last I heard Samsung uses a slightly rebranded/reskinned version of Google Messages, still developed by Google, per an agreement between them to push RCS.
[Magisk] Nergal di Cuthah:
https://play.google.com/store/apps/details?id=com.chating.messages.chat.fun

Sketchy package name just saying
[Magisk] mackdacre:
That's just Samsung's Messages app. Third-party apps can't use RCS. The app in the play store is probably not the app he was using.
[Magisk] KeplerK20:
I am trying this now , will report back ,

May i know the github repository for this fork for future updates ?

EDIT:

Found it

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

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

github.com

Also I am embarrassed to ask for help here but i am not able to get it working.

Play Integrity Checker Fails All three tests.

What am i missing i dont know.

What i did till now:

1. I have Rooted One Plus 3 (OxygenOS 4.5.1 - Android v7.1.1)

2.I have Magisk Latest with Zygisk

3.PlayIntegrityFork v8 Module Installed

4.DenyList Enforced for the PlayIntegrityChecker API App

It Fails DEVICE , BASIC and STRONG Integrity Tests

WHAT TO DO ? What am i missing ?
[Magisk] Vision:
GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

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

github.com
[Magisk] me_droid:
Didn't know that, thanks. Wonder if anyone else using the Samsung app is locked in to RCS only? We couldn't determine how to turn that off. Or maybe if it detects that I have RCS enabled, it automatically attempts to use RCS?
[Magisk] KeplerK20:
What i did till now:

1. I have Rooted One Plus 3 (OxygenOS 4.5.1 - Android v7.1.1)

2.I have Magisk Latest with Zygisk

3.PlayIntegrityFork v8 Module Installed

4.DenyList Enforced for the PlayIntegrityChecker API App

It Fails DEVICE , BASIC and STRONG Integrity Tests

What am i missing ?

are there any steps that I am missing?
[Magisk] bdr127:
It looks like that number is for Mobivity, a marketing company that uses text messaging services. Perhaps Sonic uses them, but that number isn't specifically Sonic, apparently.

What should I do with it, anyway? Like, text them and say I'm testing RCS on my phone?
[Magisk] Vision:
Only 2/3 can pass, forget the Strong

Why you have in the .DenyList Enforced the PlayIntegrityChecker API App ?

You have a custom.pif.json inside in the module folder?

You have reboot?

EDIT: And please read and this excellent guide by @osm0sis

is explain everything about 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] justDave:
You shouldn't have to go that far. Start a chat and see if it shows text or RCS.
[Magisk] cambunch:
RCS just started working for me randomly after the widespread issues on Friday. Using @chiteroman's official 15.9.6 release with no custom PIF. Pixel 7 on stock ROM on VZW. 🤷‍♂️
[Magisk] osm0sis:
Google must be pulling levers behind the curtain still or something... 🤔

I have also seen people spontaneously switch test groups in A-B testing before, so who knows. 🤷‍♂️
[Magisk] sawdoctor:
Can confirm just sent and received a rcs message on ee in the UK using your pif and griffin fingerprint

Edit

Just double checked PI checker and still passing so the print hasn't been banned so it must be something googly
[Magisk] g33gz:
Looks like my rcs is now working again. Using a one plus 8 pro (stock rom) with PIF Next
[Magisk] unsafe8989:
OnePlus 10 Pro here stock with @osm0sis fork using griffin fingerprint and RCS is working again
[Magisk] immortalwon:
I also confirm it's working again, well played Google. The april fools joke got me as I uninstalled and reinstalled the app multiple times.
[Magisk] bombadier:
In the uk and have just turned RCS back on and can send RCS messages again, fork and griffin
[Magisk] pershoot:
Confirmed; RCS just started working and messages sent via that medium have started coming in.
[Magisk] joefuf:
Didn't change anything. It just started working again on its own.

View attachment 6086816
[Magisk] blinoff82:
Omg... What happened???
[Magisk] sawdoctor:
Just be patient, the OP has discovered the issue and is probably working on a fix. He probably doesn't want people downloading until it's fixed
[Magisk] iruiz2:
Yasnac reporting everything is OK here (with v9. 8). Google Play says certified. Integrity Checker doesn't pass Device Integrity.

OnePlus 9 pro with OOS 13.
[Magisk] chiteroman:
View attachment 6030512View attachment 6030513View attachment 6030514View attachment 6030515

WHAT HAPPEN GOOGLE? NICE TRY 😘😘😘

Should I release v12?
[Magisk] DanGLES3:
......YES (please)
[Magisk] emyaqin:
Oooo, you got em
[Magisk] MrLumin:
Do it!
[Magisk] thesingular:
Whoa 🤩🤩🤩

And to answer your question, yes please!
[Magisk] sawdoctor:
It doesn't get said often enough, thank you for all your hard work ❤️❤️
[Magisk] i5lee8bit:
@chiteroman, 9WT19101Y17865255

With no actual set expectations, nor expecting any guarantee of future fixes (this prospective v12 included), just as appreciation for what you've done for the community up to this point, here ya go.

For those who are able to express their appreciation with a small monetary donation, what say we shower chiteroman with an early Xmas donation train gift??

https://paypal.me/chiteroman

Take your time with the fix bro. Take some time for yourself. You deserve it 😉

Edit: stupid url "unfurl" crap
[Magisk] thesingular:
You're right.

Truly thank you so much @chiteroman
[Magisk] Fiufsciak:
I used to use this module until now. I'm kind out of the loop, so should I uninstall it completely, and then install the new one? Unsure whether they're the same module, because the description mentions Displax. View attachment 6030519
[Magisk] thesingular:
PlayIntegrityFix will uninstall USNF upon rebooting after installation. You can uninstall it manually before rebooting as well.
[Magisk] DanGLES3:
Yes, tho this modules will automatically remove that module when installing
[Magisk] iruiz2:
Impressive, hermano.

THANK YOU for your work
[Magisk] thesingular:
View attachment 6030521

Thank you so much once again @chiteroman

v12 has been released!

🎊🥳🎉
[Magisk] chiteroman:
New update released! Check Play Integrity now 😎

Release v16.5 · chiteroman/PlayIntegrityFix

Update hook framework: Dobby Fix Device not passing in few devices Improve code Reduce Zygisk libs size

github.com
[Magisk] thisislukas:
Wallet also works again. Thanks bossView attachment 6030524
[Magisk] iruiz2:
Universe is balanced again ;)
[Magisk] MrLumin:
Yeah baby! I'm appreciating your work. 💝
[Magisk] HippoMan:
Let's hope it doesn't stop working again!
[Magisk] mackdacre:
It's the second thing.

If you're having problems with RCS, you need to disable it so that other people's phones know not to try sending RCS messages to yours. If they see that your RCS is enabled, other phones will attempt to use that instead of SMS and you will not get your messages.
[Magisk] ardiesel:
The fix has been posted to telegram, updated the magisk module and RCS immediately returned to functioning properly
[Magisk] joefuf:
Mine started working before I updated to v15.9.7.
[Magisk] Alitheia:
It was clearly just an outage we were all panicking over. Mine just started working again and I haven't touched a thing. 😂
[Magisk] SchmilK:
I haven't changed anything in 24 hours and RCS just all of a sudden started working. I wonder if Google missed some ssl certs renewal 😜
[Magisk] D€INOS:
Sounds good , now all I need is someone with rcs that is awake
[Magisk] bentree:
I is awake, it's daytime here in aussie land.
[Magisk] Mr. Apocalypse:
Yeah, all of the RCS messages that my wife sent me for the past 2 days just came in.

EDIT: I think Google is messing w/ us for April Fools
[Magisk] sawdoctor:
No update needed, it just started working on its own. Osmosis hasn't updated anything and his PIF has rcs messages working now
[Magisk] ardiesel:
Strangely enough, I believe RCS must have been broken across devices because my wife has a galaxy s20 Plus using the Samsung stock messaging app and suddenly RCS messages started flowing into the inbox, and her phone is completely stock
[Magisk] Nergal di Cuthah:
Great thanks google, a message system that can worldwide crash. When people use messaging in disasters when phone services are bad/overloaded probably not good that messages vaporize or turn into snail mail with it all coming in at once.

Glad i use textra and have no interest in rcs until it's a stable infrastructure like sms is

yes i know privacy, blah blah, encryption. if i want privacy and encryption i can get them using a different type of app like whatapps or mastadon or whatever. Or just talk to somebody face to face
[Magisk] pndwal:
(and others)...

As I said:

... Unless this:

😜 PW
[Magisk] HippoMan:
Which TG channel?
[Magisk] ardiesel:
Play Integrity Fix

https://www.paypal.com/paypalme/chiteroman	https://github.com/chiteroman/PlayIntegrityFix	https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/

t.me
[Magisk] ImjustSaiyan92:
*Edited irrelevant info*
[Magisk] osm0sis:
Nobody changed anything to outfox anybody, Google clearly just stopped restricting the Xiaomi.eu griffin print for RCS use.

Would be great if people could stop spamming "hey it works now" to the thread and burying this obvious fact.
[Magisk] HippoMan:
Oh, just the standard channel.
[Magisk] ImjustSaiyan92:
Apologies.
[Magisk] Joshyfry93:
So glad it's back 😁 Three, UK, Chiteroman 15.9.6, no idea what griffin is.
[Magisk] osm0sis:
Presumably the contacts your wife was receiving those messages from couldn't all be rooted and using a PIF module?

This might be a clue about why the griffin print works again for RCS, maybe they were having false positives on stock locked devices from the added detections so needed to stop the experiment. 🤔

Sh*t, going a bit tinfoiled here, but maybe this is why griffin wasn't banned yet so that they could test the new restriction out on just the single mass-used print to see if there would be negative side-effects like this. Could even explain why only 95% of prints got banned on Leap Day. We've been corralled like livestock... 🤯