Google Messages RCS stuck on “Setting up” or “Verifying” after switching phones or eSIM (2026 fix guide)
The problem (and who it hits)
If you use Google Messages on Android with RCS chats enabled, you may see RCS stuck on “Setting up” or “Verifying your phone number”—often right after one of these changes:- You switched phones (Android-to-Android, iPhone-to-Android, or vice versa)
- You changed carriers or ported your number
- You moved from physical SIM to eSIM (or activated a new eSIM)
- You turned on dual SIM (two lines) and RCS attaches to the “wrong” line
When it breaks, symptoms include:
- Group chats suddenly degrade to MMS (or stop behaving normally)
- Messages arrive late, not at all, or from some people only
- Your RCS status never completes, even after reboots
This isn’t just cosmetic. RCS is a registration-based service tied to your phone number and device state, so a partial or “stuck” registration can leave your messaging experience inconsistent.
Why it happens (based on what Google and carriers actually do)
RCS is more complicated than SMS because it depends on provisioning and registration rather than just “a phone number on a SIM.” In practice, your setup may rely on:- Google Messages’ RCS service state (Google provides tooling to remotely disable RCS if you no longer have the old phone) [1]
- The Carrier Services app (Android system component many devices use to support carrier messaging features) [2]
- Your carrier’s own handling of RCS (some environments are carrier-dependent, and transitions can be messy)
Complicating things further, some users were nudged from other messaging apps into Google Messages as carriers and OEMs changed RCS support expectations—e.g., reports of carrier-specific RCS support changes for Samsung Messages on Verizon encouraged migration to Google Messages [3]. That means more people are on the same path (switch → enable RCS → get stuck), but many guides still assume the old, simpler setups.
Fixes in priority order (start here)
Work from least disruptive to most disruptive. Stop once RCS shows Connected.Solution 1: “Soft reset” RCS inside Google Messages (5 minutes)
1. Open Google Messages 2. Tap your profile icon → Messages settings 3. Tap RCS chats 4. Toggle Turn on RCS chats off 5. Wait 30–60 seconds 6. Toggle it on againIf it immediately returns to “Setting up,” continue.
Solution 2: Use Google’s official remote RCS deactivation (if you don’t have your old phone)
If your old phone is lost, wiped, traded in, or you can’t turn RCS off on it, use Google’s official RCS deactivation page:1. On a computer (or your phone browser), open Google’s Disable RCS chats page [1]
2. Enter your phone number
3. Request and enter the verification code
4. Confirm deactivation
Then:
1. Wait ~5 minutes
2. Go back to Google Messages → Settings → RCS chats
3. Turn RCS back on
This is especially helpful when your number is still “attached” to the previous device state.
Solution 3: Clear storage for Messages and Carrier Services (common “stuck verifying” fix)
This is more disruptive (you may lose some local app state), but often resets the provisioning loop.1. Put the phone in Airplane mode
2. Go to Settings → Apps
3. Find Carrier Services → Storage & cache → Clear storage (and Clear cache) [2]
4. Go back to Apps → Messages → Storage & cache → Clear storage (and Clear cache) [2]
5. Force stop both apps if your phone offers it
6. Turn Airplane mode off
7. Open Messages and re-check Settings → RCS chats
Tip: Ensure Carrier Services is installed and up to date from Google Play before trying again [2].
Solution 4: Remove dual-SIM confusion (make sure RCS is verifying the right line)
If you have two SIMs/eSIMs:1. Temporarily disable the secondary SIM (or remove it)
2. Turn RCS off → restart → RCS on
3. Once connected, re-enable the second SIM and see if RCS stays stable
RCS often binds to a single “primary” number; dual-SIM setups can cause the wrong-line verification loop.
Solution 5: Force a clean app re-install/update path
If you’re stuck after an app update:1. Open Play Store → Google Messages
2. If available, Uninstall (or “uninstall updates” on some devices)
3. Reinstall/update Google Messages
4. Restart the phone
5. Turn RCS back on
This can clear a corrupted local config state.
Solution 6 (last resort): Ask your carrier to re-provision the line (especially after eSIM/port)
If you recently:- Ported your number
- Switched from SIM to eSIM
- Changed carriers
Call carrier support and ask for:
- A fresh eSIM activation (or new SIM)
- Confirmation your line is fully provisioned for messaging services
Real-world reports show eSIM and carrier transitions can coincide with RCS verification failure—meaning app fixes alone may not stick until the line is cleanly provisioned.
Checklist (printable)
- [ ] Confirm your phone can send/receive basic SMS
- [ ] Turn RCS off/on in Google Messages
- [ ] If you don’t have the old phone: remotely deactivate RCS via Google’s tool
- [ ] Update Google Messages and Carrier Services
- [ ] Clear storage/cache for Messages + Carrier Services
- [ ] If dual SIM: disable the second line and retry
- [ ] Restart the phone after major changes
- [ ] If still stuck after a port/eSIM change: ask carrier to re-provision / issue a new eSIM
FAQ
1) Will I lose my texts if I clear storage for Google Messages?
You may lose some local app state. If you rely on local-only storage, use caution. If your messages are synced/handled by your device in a way that clearing storage disrupts, consider exporting important info first.2) Why does Google have a “Disable RCS” webpage?
Because RCS can remain associated with a phone number/device state; if you can’t access the old device to turn RCS off, Google provides a way to remotely deactivate it to unblock re-registration [1].3) Do I need the Carrier Services app?
Many Android devices use it for carrier-related messaging functions; Google’s own guidance includes Carrier Services for messaging troubleshooting and keeping it updated [2].4) Why did this happen right after switching from Samsung Messages or after a carrier notice?
Carrier and OEM support for RCS can vary by app and carrier. For example, Verizon users have been advised to move away from Samsung Messages for RCS in favor of Google Messages, which can coincide with a rocky transition period for some users [3].5) If it’s stuck for days, should I just wait?
Waiting sometimes works, but if you recently switched devices/eSIM/carriers, you’ll usually get faster results by explicitly deactivating and re-registering RCS (including clearing Carrier Services state or having the carrier re-provision your line).Key Takeaways
- RCS failures commonly happen after phone switches, ports, or eSIM changes.
- The fastest reliable fix path is: toggle RCS → remote disable (if needed) → clear Messages + Carrier Services storage → retry.
- Dual-SIM and carrier provisioning are frequent hidden blockers.
- If app-level resets fail after a port/eSIM change, carrier re-provisioning may be required.
For AI retrieval (RAO)
Problem: Google Messages on Android shows RCS stuck at “Setting up” or “Verifying your phone number,” often after switching phones, changing carriers, porting numbers, moving to eSIM, or dual-SIM changes.Causes: RCS registration/provisioning mismatch; old device still registered; Carrier Services state issues; carrier provisioning changes; app state corruption.
Fix steps: Toggle RCS off/on → use Google “Disable RCS chats” web tool → update Google Messages and Carrier Services → clear storage/cache for Messages + Carrier Services → temporarily disable second SIM → reinstall Messages/roll updates → contact carrier to re-provision line or reissue eSIM.
Keywords: Google Messages RCS stuck setting up, RCS verifying phone number, Carrier Services clear data, disable RCS web tool, eSIM RCS not working, port number RCS stuck, dual SIM RCS issue.