Weird update procedure from firmware 4.1.4 to 4.1.5

[salim-b]

Before today's update, my Somu was on:

$ solo key version
4.1.4 locked

The first attempt to update allegedly fails:

$ solo key update
Wrote temporary copy of firmware-4.1.5.json to /tmp/tmpe_d2ccfr.json
sha256sums coincide: f36bb365bfddf75004f28af392ae1439192ca0ed821ef496084a75a00d05087a
Switching into bootloader mode...
using signature version >2.5.3
erasing firmware...
error:ng firmware 100.00%...
problem flashing firmware!
(27264, b'')

But it actually downgraded my locked Somu from 4.1.4 to an unlocked 3.0.0? 🤨

$ solo key version
3.0.0 unlocked

After that, the update to 4.1.5 seems to work fine:

$ solo key update
Wrote temporary copy of firmware-4.1.5.json to /tmp/tmpn0w3w0zz.json
sha256sums coincide: f36bb365bfddf75004f28af392ae1439192ca0ed821ef496084a75a00d05087a
using signature version >2.5.3
erasing firmware...
updated firmware 100%             
time: 9.31 s
bootloader is verifying signature...
...pass!

Congratulations, your key was updated to the latest firmware version: 4.1.5

And my Somu is locked again:

$ solo key version
4.1.5 locked

Now I'd like to ask: Is this really the expected update behaviour? I thought it wouldn't be possible to unlock a key once it was locked...

^{I'm using v0.0.30 of the solo-python CLI.}

[jonathonf]

I also hit the same thing this morning (and after panicking tried update again and it worked on the second attempt).

For my Somu, after it hit this point on the first update,

problem flashing firmware!
(27264, b'')

no other solo key commands succeeded, all returning an error. Possibly it was stuck in an intermediary state?

[conorpp]

If you read the version while the key is in bootloader mode, it will return the version of the bootloader and not the application, which can be confusing.

[salim-b]

If you read the version while the key is in bootloader mode, it will return the version of the bootloader and not the application, which can be confusing.

Ok, so the key was stuck in bootloader mode after the failed update? Still bears the question: Why did the update fail in the first place? Might the error (27264, b'') be related to solokeys/solo1-cli#113?

[olof-nord]

I just faced the same issue, running the upgrade a second time ended up with a successful update though.
Had a short moment of panic as well, not the best user experience I would say.

$ solo key update
Wrote temporary copy of firmware-4.1.5.json to /tmp/tmpxw3nz_jh.json
sha256sums coincide: f36bb365bfddf75004f28af392ae1439192ca0ed821ef496084a75a00d05087a
Switching into bootloader mode...
using signature version >2.5.3
erasing firmware...
error:ng firmware 100.00%...
problem flashing firmware!
(27264, b'')

$ solo key version
3.1.2 locked

$ solo key update
Wrote temporary copy of firmware-4.1.5.json to /tmp/tmplqndku9k.json
sha256sums coincide: f36bb365bfddf75004f28af392ae1439192ca0ed821ef496084a75a00d05087a
using signature version >2.5.3
erasing firmware...
updated firmware 100%             
time: 9.25 s
bootloader is verifying signature...
...pass!

Congratulations, your key was updated to the latest firmware version: 4.1.5

$ solo key version
4.1.5 locked

[fcartegnie]

That's worse than expected as the firmware update will trigger again when already on 4.1.5

[vaygr]

Same here with Somu.