Suunto Race 2 - Device is being restored to a safe state bootloop

BakxM

Pfff, two workouts during morning and afternoon, all fine and synced to SA

Started activity in the evening and device crashed and returned to ‘The device is being restored to a safe state’ & ‘Improving your watch for adventure’ & ‘this update will take less than 10 min’ . (screen with the green progress bar).

After a few of these update-cycles the device reboots and shows ‘Error 1403,1403,1403,1403, SW version 2.56.18’ & ‘the device recovered from an error’.

The device seems responsive because for a brief moment, my iPhone notifications come through (also newer ones from AFTER the initial crash) and in maybe 5 seconds, the ‘device is being restored’ screen starts again.

Going on for almost a day now …

I find lot of similar situations from other users, but did not find a definitive answer ?

Any thoughts ? (much appreciated)

BR, Marcel

Dimitrios Kanellopoulos

@BakxM I would try to wait if it resolves it self. Esle

Hold upper and middle button.
When it reboots try to release upper button but keep holding the middle. Will enter “safe mode” try reboot from there

BakxM

@Dimitrios-Kanellopoulos

Thanks for reaching out.
However … I cannot seem to have the device ‘operational’ long enough to perform a clean reboot. I believe after a short time it crashes again and the firmware-restore cycle starts over again.

One of the things I now noticed, is that the watchface seems to be blank after the restore, the secondary screen with ‘sun up’ & ‘sun down’ still is there and when I’m lucky I can quickly scroll to ‘Settings’ before it bootloops again.

What I did notice is the number of ‘1403’ error differs in each restore cycle. In my OP , I had 4x 1403, but this morning I also had cycles with 2x1403 or 3x1403 ??? And even once a 1405 error code instead of 1403
Does this mean anything for any Dev’s reading along ?

Is there any button combination to force a hard reset ? Or maybe leave the watch and first have it drain all power?

(it might be coincidental, but never had any issues with this watch before the firmware update this week )

Dimitrios Kanellopoulos

@BakxM try the moment it boots to issue a full reset. I would suggest that.

Else yeah let it drain the battery. Ill be checking this thread and immediately passing this info to the dev team

Dimitrios Kanellopoulos

@BakxM said:

What I did notice is the number of ‘1403’ error differs in each restore cycle. In my OP , I had 4x 1403, but this morning I also had cycles with 2x1403 or 3x1403 ??? And even once a 1405 error code instead of 1403
Does this mean anything for any Dev’s reading along ?

one more and important. Close all nearby BLE connections (phone belt etC)

makoc

Experiencing same issue with my Vertical 2, boot loop started this morning after trying to initiate a hiking activity. I think it’s firmware update related, I got a new firmware notification on the phone shortly before that. So far no key combination gets me out of it.

Danny Labrana

@BakxM
Pray the watch is still covered by guarantee and get in touch with Suunto support: they will probably request you to send it to them for a full check-up. I did report a similar error message/behaviour with my 9 peak pro and they couldn’t fix it. Since it was 2 months since the guarantee end date, the only thing I got was a coupon code for a new watch