Hey,

After weeks of seeking help from this community and elsewhere, I’ve finally found a workaround for the issue of my SIM not registering on the network on my NP2, resulting in “Emergency Calls Only.” While I’m not suggesting anyone attempt this, I wanted to share the steps I took to document my experience and provide insight into the issue.

Please note that I’m not recommending anyone try this, as there’s a risk of misconfiguring your phone .

Steps I took

1. Opened the Testing Menu:

Dialled *#*#4636#*#* on my phone’s dial pad.

2. Went to Phone Information:

Selected the SIM slot that corresponded to my SIM.

3. Changed the Preferred Network Type:

Found the dropdown menu labeled “Set Preferred Network Type.”
IMPORTANT: At this point I wrote down what it’s currently set as, in case I wanted to change it back at any point.
Chose the following configuration (although any work that don’t include ‘NR’): GSM/WCDMA/LTE (PRL)

4. Toggled Airplane Mode:

Turned Airplane Mode on and then off again to apply the new settings.

5. Tested Network Registration:

The SIM registered successfully on the network after making these changes.

Note that this meant that I couldn’t access the 5G network, so I then changed back to a Preferred Network Type that included “NR”, which is 5G. e.g. NR/LTE/GSM/WCDMA. However, if I then lost connection to the network due to no signal or airplane mode, it would again not register so I’d have to perform the above steps again. So I’ll probably just use 4G from now on until Nothing (hopefully) releases a fix.

In terms of some of the acronyms, you can find this information easily online, but incase it helps, here’s a list of what they mean:

GSM: 2G

WCDMA: 3G

LTE: 4G

NR: 5G

Important Notes:

- Caution: Changing settings in the testing menu can affect your phone’s functionality.

- Temporary Fix: This workaround is not a permanent solution, but it allows the SIM to function until a proper fix is released.

I’ve been in regular contact with Nothing Customer Support over the past few weeks, trying to debug this issue and I’ve updated them with this latest workaround. Hopefully they provide a fix soon!