Firmware Update issues to 1.0.39 and please publish the firmware hashes conveniently

[Marc-Gee]

Hi, I am following the jade firmware upgrade instructions as per here to update to 1.0.39
(but 1.0.39 isnt tagged as a release on the Github??)

I have tried Option 3 (Jadelink) but that again stalls permanently at 2% with no error information. I have re-tried it after several reboots and usb unplugging. Still unsuccessful. And I did find not find the authentic firmware hases listed anywhere. (So I checked it to the hash on the download file, before realising how dumb that was. )

The same issue failed upgrade at 2% progress happened with ver 1.0.38 a few months ago on the same just-unboxed (1.0.32?) jade plus firmware update.

After option 3 multiple failures, i tried option 1. It worked fairly smoothly, however how is an even-somewhat-technical person supposed to determine that its a different firmware hash is expected from the one for option 3! My jade device is showing a hash that matches to a "cmphash" , not the (firmware) fwhash??!! what is a cmphash ??

https://jadefw.blockstream.com/bin/jade2.0/index.json

As much as I want to support Jade for less-technical friends and family, I once again am reminded why i cant: the QA / user experience is just too frustrating. This still feels like a pre-release software (with language like initialized QR login separated for login etc etc. ) .
The accompanying website documentation for the Jade is sadly not written for even somewhat-technical-people to easily follow.

2hrs for a firmware update so far. aaaargggghhhh!

Lastly, since 1.0.39 the USB icon is displaying when its plugged into the wall charger!! ( I think that is a new bug in 1.0.39)

I am willing to assist to make the improvements, but this really isn't a consumer-ready HWW.

Thanks,
M

[jgriffiths]

Hi @Marc-Gee, appreciate your feedback. Thanks for opening a new issue for this also.

1.0.39 isnt tagged as a release

I've just pushed the tag for this release.

I have tried Option 3 (Jadelink) but that again stalls permanently at 2%

We made a bunch of changes in 1.0.38 to fix issues with USB devices. If you'd like to verify that this works, you can "upgrade" using JadeLink to the same version you are currently on (1.0.39). Assuming this goes smoothly you should have no issues going forward with USB updates. We are moving to flash new units and outstanding stock with 1.0.39 so hopefully these issues shouldn't cause problems going forward.

what is a cmphash ??

See https://help.blockstream.com/hc/en-us/articles/50614746819097-Manually-verify-firmware-binary and for more details and history you can optionally read up here #160.

Where did you see the text cmphash specifically? I've asked for the firmware update docs to be updated and a link to the verification page added. If the wallet apps are confusing I can reach out to the wallet team to ask them to simplify things.

Lastly, since 1.0.39 the USB icon is displaying when its plugged into the wall charger

I'm pretty sure this is by design now.

[Marc-Gee]

Hi @jgriffiths Thanks for your reply. Apologies that i am only replying 1 week later.

Thanks for tagging the 1.039 release. 👍

Regarding the USB firmware upgrade:

We made a bunch of changes in 1.0.38 to fix issues with USB devices. If you'd like to verify that this works, you can "upgrade" using JadeLink to the same version you are currently on (1.0.39). Assuming this goes smoothly you should have no issues going forward with USB updates. We are moving to flash new units and outstanding stock with 1.0.39 so hopefully these issues shouldn't cause problems going forward.

Sadly it still fails at 2%. I am using the same file as last time (last weekend), on the Jade plus that was/is already updated to 1.039ble ("0d2be1a26dbc16f3f64e04634297c9bc98131e25ab5534f5c67fbd0bdf1e0f36").

Previously(last saturday) , i was only able to get the update to run via the webserial upgrade. Today, i tried the USB firmware update:
From 1.039ble ("0d2be1a26dbc16f3f64e04634297c9bc98131e25ab5534f5c67fbd0bdf1e0f36")
to: 1.039ble ("0d2be1a26dbc16f3f64e04634297c9bc98131e25ab5534f5c67fbd0bdf1e0f36")
and it hangs at 2%. :(( I let it sit for 10 minutes, no change. the device was unlocked.

the proposed hash for the update was correct:("0d2be1a26dbc16f3f64e04634297c9bc98131e25ab5534f5c67fbd0bdf1e0f36"), so the fw file was not damaged or altered.

I then switched off jade. unlocked, retry'd update firmware from same USB files.
It worked, but that didn't feel very good. From itself to itself still get's stuck!
LMK if you have questions to help you debug it further. will serial number help?

On the going forward USB updates idea you proposed for other customers- , while its great for blockstream that you will update and only sell devices >1.039 FW ( and maybe the 2% USB FW issues wont appear for customers, but today it seems that they will reappear...) - that doesnt help the issue for your many 1,000's of existing customers not yet on 1.0.38 !!
Basically you should say at this point that the USB firmware is unreliable and they cant use it. Use webserial or app updates. It will save them the many hours of frustration on the Jade Plus new but-not-working feature that they think they have. I thought I was the only one user with this issue, meanwhile its known issue and could have saved us both 3 hours.

what is a cmphash ??

See https://help.blockstream.com/hc/en-us/articles/50614746819097-Manually-verify-firmware-binary and for more details and history you can optionally read up here #160.

Where did you see the text cmphash specifically? I've asked for the firmware update docs to be updated and a link to the verification page added. If the wallet apps are confusing I can reach out to the wallet team to ask them to simplify things.

this file https://jadefw.blockstream.com/bin/jade2.0/index.json is the only place to get your firmware hashes. (esp if user is doing USB updates.)
your document describes the cmphash as the compressed hash. but that is the value that the jade device showed me as the proposed hash (upgrading from 1.038BLE to 1.039BLE last Saturday. I didn't know what was was correct a correct hash but via searching for 10 mins, I found your hidden page. https://jadefw.blockstream.com/bin/jade2.0/index.json
I then saw that the proposed hash matched something called cmphash on your site, so I accepted it as probably valid. In retrospect, that was a terrible security decision on my part, . (and misguided i know, considering I knew about the Dec 2025 vulnerabilty disclosure. so it could have been an exact repeat!).

So thats the 1.039BLE hash the jade device showed me immediately prior to my upgrade and thats the webpage where I horribly matched it to. Yikes!

Todays update is a full one, so that matched on the device to the webpage's:
"fwhash": "0d2be1a26dbc16f3f64e04634297c9bc98131e25ab5534f5c67fbd0bdf1e0f36"

Yes, please do urgently ask the web team to revisit those pages as a beginner/intermediate user. The Webserial page is tonight thankfully showing the file hash during the update! :) but not the others yet.
(I updated a separate classic device tonight from 1.038BLe to1.039BLE) via webserial , so thats how i saw that. I know classic doesnt support usb updates so i didnt even try that.

Lastly, since 1.0.39 the USB icon is displaying when its plugged into the wall charger

I'm pretty sure this is by design now.
Yes, i subsequently saw that code change on the icon.
I feel that it is now the wrong icon to be displaying. the device is only charging and the power symbol was already correctly showing over the battery icon. There is no data flowing over the usb cable, so considering the security nature of the device, - IMHO it shouldn't indicate a data connection if there is not one.
(perhaps the board isnt able to determine if its data or power only), but thats for the hardware devs to say.

If they are interested in fixing the other icons, the bluetooth icon should change when its connected vs not connected. the 2 dots are that indication () . 1.039ble currently only shows the un-connected icon, even when it is connected over bluetooth.

Thanks for your work here.
M

[jgriffiths]

I then switched off jade. unlocked, retry'd update firmware from same USB files.
It worked, but that didn't feel very good. From itself to itself still get's stuck!
LMK if you have questions to help you debug it further. will serial number help?

From itself to itself getting stuck tells us that it was not the application of the update that hung (since that gets detected as a no-op), but the loading of the data from the USB. We found that there are some O/S issues that can cause this - we worked around them where we could but if it still happens intermittently (and you are using an official JadeLink USB device and not say a cheap drive that may have its own power/firmware issues) it will likely be fixed by upgrading the O/S underlying the Jade firmware, which we are working on at present and hope to roll out in 1.0.41.

[jgriffiths]

your document describes the cmphash as the compressed hash.

The docs and the hashes are confused somewhat by the fact that we added compression (which results in a different file hash) after the initial release of the Jade. As a result they are attempting to cater for users on older versions that may see the uncompressed hash instead.

I think it won't be long before we can remove the uncompressed hash, nonetheless I've forwarded your comment to our documentation writer to see what he can address in the meantime.

[jgriffiths]

If they are interested in fixing the other icons, the bluetooth icon should change when its connected vs not connected. the 2 dots are that indication (Image) . 1.039ble currently only shows the un-connected icon, even when it is connected over bluetooth.

Thanks, I've raised this to track internally.