Sg3//RF - Google Blocking RCS on Rooted Android Devices
 

I posted a version of the below article on the r/AndroidRoot subreddit, but it was removed without explanation. It documents Google's ongoing silent restriction of RCS (text) messaging on rooted Android phones. For the full context, including details on the post's censorship and subsequent moderation issues on Reddit, see The Full Story section at the bottom.

GOOGLE IS SILENTLY BLOCKING RCS TEXT MESSAGING ON ROOTED DEVICES

As of 2024, Google is now quietly blocking RCS text messages on rooted android devices. Even if your device only has it's bootloader unlocked, it is now at risk of being quietly shadowbanned from sending RCS text messages.

Owners of unlocked / rooted Android phones exhibiting this behavior will send a text message, only for it to instantly disappear. Incoming text messages are completely and silently blocked with absolutely no way of knowing if someone attempted to contact you. No explanation, backup option, or 'accept the risk' checkbox. You have been shadow-banned from your own device.

This form of silent blocking is known as 'shadowbanning', whereby users are restricted from transmitting or receiving content without being explicitly told. Shadowbanning is one of the most classic, Orwellian tools in the online censorship toolbox.

After the fallout caused by my article, Google updated this behavior to instead show a cryptic 'Not sent' warning below censored text messages (in some cases only appearing after the blocked message is tapped)

This restriction is activated when root or an unlocked bootloader is detected on an Android device. Detection is performed by 'Play Integrity' checks and 'DroidGuard' - mechanisms built into Android (and it's hardware) that are designed to check for modifications to the operating system, it's services, bootloader, or file structure- even if the changes are completely benign and pose zero practical security risk.

There are plenty of benevolent and well-meaning reasons users root / unlock their Android phone.

It doesn't matter if you are texting a friend, in a life threatening emergency situation, or communicating with someone in need themselves. If you are one of the tens of thousands of Android root enthusiasts who enjoy customizing the phone that you paid for, you are at risk of being silently and suddenly prevented from sending or receiving text messages at any time.

Google spends millions of dollars developing these overzealous security mechanisms that go completely beyond ethical and moral lines to detect anything they consider 'unsafe', and punish the user with draconian censorship if a detection is tripped.

While Google cites 'spam and abuse prevention' as the rationale, blocking core communication features on personally owned and modified devices is a complete overstep of hardware ownership rights, and a reckless, dangerous, and likely even illegal act of communications censorship.

The ultimate irony is that Android root access / unlocking / tweaking is where many Android Engineers at Google got their start. Punishing the curious is only suppressing this pool of upcoming talent.

Media Coverage of my article



Other Threads



XDA Developers Discussions

The Full Story: My Original Post, Its Removal, and Reddit Moderation Issues

My initial detailed post on r/AndroidRoot gained significant traction, leading to coverage in major outlets like Forbes, The Verge, 9to5Google, and others. Google even responded publicly (though their statements were a complete joke, completely downplaying user impact).

Shortly after this attention peaked, the post was removed from r/AndroidRoot without explanation. Attempts to seek clarification from moderators went unanswered. Months later, when I noticed the AndroidRoot subreddit was unmoderated (the primary moderator's account, 'dongl_tron', was banned site-wide), I submitted a legitimate request via r/redditrequest (forum to request ownership of orphaned subreddits) to take ownership of the community, citing my active contributions and interest in Android rooting discussions.

Unfortunately, priority was given to another requester who claimed to be a "friend" of the banned moderator and stated they would continue under the banned moderator's guidance- a clear case of ban evasion, which is blatantly against Reddit's policies. Despite highlighting this concern in updates to my request, the subreddit ownership was granted to that sock puppet 'friend' account. Soon after, an alternate account resembling the original banned moderator was added to the team. Unsurprisingly, I was then banned from r/AndroidRoot in retribution, despite many years of contribution to the AndroidRoot subreddit.

Multiple reports to Reddit admins detailing this situation received no meaningful response.

The issue itself remains relevant: Google's RCS restriction continues to this day.

How You Can Help