> For the complete documentation index, see [llms.txt](https://atbluebubbles.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atbluebubbles.gitbook.io/guide/new-methods/getting-your-phone-number-registered/physical-sim-4.md).

# Physical SIM #4

{% hint style="info" %}
This is method has been reported to work for Xfinity and Verizon, but it may work for other carriers as well.
{% endhint %}

{% hint style="warning" %}
This method is *sort of* different from the other methods posted, but it requires you to activate a new SIM card in your Android 
{% endhint %}

## Steps:

1. Order a ***new*** SIM from your carrier and wait until get your ***new*** SIM card
2. Take your active SIM card and put it into your iPhone **(Please wait about 10-20 minutes to make sure that Apple has your number registered to iMessage.)**
3. Turn on **Airplane Mode**, but keep the **Wi-Fi** on
4. Take your ***new*** SIM card and put it into your Android device
5. Call your carrier and activate the ***new*** SIM card for your Android device
6. Keep your iPhone always powered on, plugged in and connected to Wi-Fi
   * *Keeping the iPhone always on may not be necessary, I'm currently testing it and I haven't been deregistered yet!*
7. On your Mac, make sure to accept the "**new number**" being added to your Apple ID

***

### Credits: [MatthewB92](https://www.reddit.com/user/MatthewB92/) & [RadiatingLight](https://www.reddit.com/user/RadiatingLight/) (for proving that a similar method works for Verizon!)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atbluebubbles.gitbook.io/guide/new-methods/getting-your-phone-number-registered/physical-sim-4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.