> 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-5.md).

# Physical SIM #5

{% hint style="info" %}
This is method has been reported to work for Verizon
{% endhint %}

{% hint style="warning" %}
This method is *sort of* the same as the other methods posted, but has a few changes.

* It's recommended to have an old Verizon SIM that was previously connected to your phone number
* Verizon will send a notification that the SIM card has been swapped to a new device, please accept it.
  {% endhint %}

## Steps:

1. Put your Android device on **Airplane Mode**; disabling cellular data and the Wi-Fi
2. Take your active SIM card and put it into your iPhone
3. Turn on iMessage and the iPhone should send a 6 digit code to confirm if the SIM is connected to the iPhone
4. Your iPhone might be stuck on **"Awaiting Activation"** even if your iPhone gotten a code sent through text
5. **Restart** your iPhone
6. Send a few test text messages to see if the number is working, once everything seems to be running smoothly, continue to the last steps.
7. Turn on **Airplane Mode**, but keep the **Wi-Fi** on
8. Take out your active SIM and put in your inactive old SIM card
9. Put your active SIM back into your Android device
10. On your Android device, turn off **Airplane Mode**; enabling cellular data and the Wi-Fi
11. 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 anddI haven't been deregistered yet!*
12. On your Mac, make sure to accept the "**new number**" being added to your Apple ID

***

### Credits: [CrewF24](https://www.reddit.com/user/CrewF24/)


---

# 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-5.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.