Need help adding Thingy:91X IMEI to my nRF Cloud account

[KazuNino]

Hello Nordic team,

I have a retail Thingy:91X device.
IMEI: nrf-359404230239544

It connects to hello.nrfcloud.com, but I cannot add it to my own nRF Cloud account because the device requires PIN/HWID.
The retail Thingy:91X does not include a PIN/HWID.

Could you please transfer/unlock this IMEI to my account ([email protected])?

Thank you very much.

[Øyvind]

Hello, 

The nRF9151 uses a different method of provisioning i.e. auto-onboarding which uses the device’s attestation token (AT%ATTESTTOKEN). The Asset Tracker template programmed through our Quick Start app in nRF Connect for Desktop. 

Please follow the steps in Managing claimed devices using the nRF Cloud portal. Note the documenation states Multi-service sample, but the Asset Tracker template should work in a similar way. If you do meet any issues, please let us know to improve our documentation.

Kind regards,
Øyvind

[KazuNino]

Hello,
Thank you for your reply.
Currently, my Thingy:91x is not recognized by the Quick Start app even when connected to my PC's USB. Therefore, I cannot register the device using the method you suggested. I just found a document on restoring it to factory settings, so I plan to try that method.
If you have any advice, please let me know.
Thank you.
KazuNino

[Øyvind]

Hello, the Thingy:91X should be recognized out of the box via USB C. Is this a new device or has someone else used it before you?

Kind regards,
Øyvind

[KazuNino]

Hello,
I took the Thingy:91X out of the box, connected it to hello.com, and checked that it was working. The Quick Start app also recognized the Thingy:91x, and I changed the device name. After that, I wrote software created with the nRF5340DK, but it stopped being recognized via USB.

I just performed a recovery to return it to factory settings and discovered a problem.

I am experiencing a serious hardware issue with my Thingy:91X (Board PCA10095, S/N: 1050092139).

When I try to connect via SWD using `nrfutil device-info`, the results are inconsistent and unreliable:

- Sometimes it detects **nRF5340_xxAA_REV1** (correct).
- Sometimes it incorrectly reports **nRF52832_xxAA (REV1 or REV3)**, which is not part of Thingy:91X.
- The **nRF9151 core is never detected** and always fails with errors such as:
Device error: Unknown device: Unknown DPIDR revision 4
Unable to detect a supported core

- Recovery (`nrfutil device recover`) always fails with “Unable to detect a supported core”.

This strongly suggests that the **SW2 switch (nRF91 <-> nRF53 selection) is defective** or the related circuitry is broken.
As a result, I cannot recover or program either core reliably.
USB DFU mode also does not work anymore, since the connectivity bridge cannot be programmed.

The device is therefore unusable for development.

I kindly request guidance on the **RMA/board replacement process**.
The device was purchased through [Digi-Key japan].

Thank you for your support.

Best regards,
KazuNino

[KazuNino]

Hello,
I have good news.
Until now, I've tried to perform recovery via the nRF5340Dk but it had failed. However, when I performed the operation via the nRF9161DK, it correctly recognized the nRF9151 and nRF5340 and successfully recovered. I was able to connect it to my PC and check the two COMs. When I open the Programmer on nRF connect desktop, I can see the nRF9161Dk and Thingy:91x. It's fully recovered.
So there is no need to replace the board.
Thank you for your support.
KazuNino

[Øyvind]

Hello, my apologies for the late reply. Great work in recovering the device and making it work again. 

I hope you are able to continue with your testing. 

Kind regards,
Øyvind