Google Messages Error 3100 (Trouble Connecting. Awaiting Retry): What It Means and What to Try

Error 3100 in Google Messages means your phone cannot connect to RCS. It mostly hits Galaxy owners after a phone or carrier change. Google's recommended steps, what not to do, and where things stand.

Abstract illustration of a smartphone with a warning triangle representing Google Messages Error 3100 : What It Means and What to Try

Error 3100 in Google Messages, shown as “Trouble connecting. Awaiting retry”, means the phone is failing to connect to the RCS servers. Your texts still go out as SMS and MMS, but RCS chat features stop working. It has mainly affected Samsung Galaxy owners who moved to a new phone or a new carrier. Google has said it is a carrier-side problem it is working on with its partners, so the steps below help some people and not others.

What error 3100 means

RCS is the system behind typing indicators, read receipts and full-quality media in Google Messages. Before it works, your phone number has to be registered with an RCS service. Error 3100 appears in the RCS settings screen when that connection keeps failing.

According to 9to5Google’s reporting from August 2026:

  • A Google account on Reddit described code 3100 as “Trouble connecting. Awaiting retry.”
  • The reports came from Galaxy phones, mostly from people who had just upgraded to a new device or changed carrier. Two of the cases involved the Galaxy Z Fold 8.
  • The same Google account raised two possible causes in individual cases: a problem during number porting, and Samsung Smart Switch carrying over corrupted cache files from the old phone.
  • Google told 9to5Google: “We’re aware of this issue and are working with our carrier partners to get it fixed as soon as possible.”

We have not found a later public statement from Google confirming that the problem is resolved. If you are seeing it in November 2026, assume the steps below are still the best available.

What to try

These are the steps Google has given affected users:

  1. Update Google Messages to the latest version from the Play Store.
  2. Turn RCS off: open Google Messages, tap your profile picture, then Messages settings, RCS chats, and switch it off.
  3. Clear the data for Carrier Services: Settings, Apps, Carrier Services, Storage, Clear data. If you cannot see it, turn on “Show system apps” in the Apps list filter.
  4. Restart the phone.
  5. Turn RCS back on and leave the phone on a stable connection while it verifies your number.

To check whether it worked, go back to the RCS chats screen. The status should read “Connected”. Verification can take several minutes, so give it time before repeating the steps.

Results are mixed. 9to5Google describes success with these steps as hit or miss. Android Central reports that some owners only got RCS working again after factory resetting the phone, and that even a reset did not work for everyone. Treat a reset as a last resort, and back up first.

2. Send Google the diagnostics

If the reset does not work, a Google employee has asked affected users to open the RCS settings screen and use the feedback option there. That sends diagnostic information to the engineering team. It will not fix your phone on the spot, but it is the route Google has asked people to use.

3. Ask your carrier to check RCS provisioning

Because Google describes this as a carrier issue, and because it often follows a number port, it is worth contacting your carrier. Tell them RCS will not register on your line after a device or carrier change and ask them to check that the number is provisioned correctly. This is our suggestion based on Google’s description of the cause, not a documented fix.

4. In the meantime, use SMS

With RCS off, messages are sent as ordinary SMS and MMS. You lose read receipts, typing indicators and high-quality media, but nothing fails to send. Leaving RCS switched off while the error persists avoids messages hanging while the app retries.

What not to do

  • Do not turn off two-step verification on your Google account. One user-reported workaround involves disabling it and clearing Google Play services data. 9to5Google advises trying Google’s own steps first. We would go further and skip it: it weakens your account for an uncertain result.
  • Do not install an older version of Google Messages. Reports on this issue cite a Google warning that older builds can wipe your message history.
  • Treat the VPN trick as unproven. Some users say turning RCS off, connecting to a VPN and turning RCS back on fixed it. TechRadar reported it as a user workaround, not an official fix. If you try it, use a VPN you already trust.

Frequently asked questions

Is error 3100 a problem with my phone?

Unlikely. Google has described it as a carrier-side issue, and it appears after phone or carrier changes on otherwise working devices.

Will I lose my messages?

The error affects the RCS connection, not stored messages. The risk to your history comes from workarounds such as installing old app versions, which is why we advise against them.

Does it only affect Samsung phones?

The reports collected so far came from Galaxy owners, which suggests Samsung devices or the Smart Switch transfer are part of it. No complete explanation has been published.

Why did it start after I used Smart Switch?

One possibility raised by a Google account is that Smart Switch copied corrupted cache files from the old phone. Clearing Carrier Services data, as in step 1, addresses that.

How this page was put together

We did not reproduce error 3100 on a device. This page is based on Google’s statement and troubleshooting steps as reported by 9to5Google in August 2026, and on TechRadar’s reporting of the user workaround. We could not find confirmation that Google has shipped a fix, and we will update this page when that changes.

Newsletter

Tech that matters, in your inbox.

Occasional, no-spam roundups of our best AI tools, guides and fixes.

Get in touch