Security alert · Oct 9, 2026: Ledger devices bought from a reseller in Southeast Asia were drained. Buy hardware wallets only from the maker. What to do →

Multisig Setup

Checklist

Hardware wallet firmware update failed: what now?

Last reviewed: October 2026

TL;DR

Your seed isn’t in the firmware and isn’t on the computer: it’s on your metal plate. Most failed updates are fixed by reconnecting and finishing the update in the maker’s own app. If the device ended up wiped, restore it from its seed (and set the passphrase again). Meanwhile, in a 2-of-3 your other two devices can still sign.

A firmware update stopped halfway, the device shows Bootloader, a red screen or asks to be set up as new. That looks alarming, but it’s a hardware problem, not a money problem. Your coins are on the blockchain and your multisig needs only two of three keys. Below is what each maker says to do, from Trezor’s and BitBox’s own support pages, checked in October 2026. The general routine for updates is in hardware wallet firmware updates.

Before you touch anything

Don’t reset the device, don’t restore it and don’t install firmware from anywhere other than the maker’s own app until you’ve tried the steps for your device below. Ignore emails, pop-ups and “support” messages offering a fix. No update or repair ever needs your seed words in an app, a website or a chat.

Trezor

Trezor Suite tells you when the device is connected in bootloader mode. To retry the update, start the Trezor in bootloader mode on purpose and install the firmware again from Trezor Suite:

  • Trezor Safe 5: connect the USB cable while swiping your finger from the bottom to the top of the touchscreen, then tap Install firmware.
  • Trezor Safe 3 (not used in my setup): connect the cable while holding the left button, then Install FW.

A red screen after an interrupted update usually means the firmware is damaged; Trezor’s advice is the same: restart in bootloader mode and update again. Be prepared for one more outcome. Trezor’s own support page says that when something goes wrong during an update, the Trezor may have wiped itself, as protection against someone installing unofficial firmware. In that case you restore it from your backup (see below) and, if you use one, switch the passphrase back on.

BitBox02

BitBox’s support page is specific about this. If the connection was interrupted, the update stopped, the BitBox02 stays on the Bootloader screen or the same update prompt keeps coming back:

  1. Don’t reset the device, restore a wallet or install firmware from another source.
  2. Wait until the BitBoxApp no longer shows an installation in progress. Then unplug the BitBox02 and plug it in again.
  3. Unlock it and check whether the update can now complete.
  4. Still stuck? Write down what the device and the BitBoxApp show and contact BitBox Support through the contact form on their website. Give the app version, firmware version and model, never your recovery words or passphrase.

BitBox also notes that the BitBox02’s bootloader checks that firmware is signed before it accepts and starts it.

Ledger

A Ledger can get stuck on Update, Bootloader or Booting during an OS update. Ledger has support articles for each of these screens on support.ledger.com; type the address yourself and follow the article for the exact screen you see, using the latest Ledger Wallet. I couldn’t check those steps against Ledger’s pages in full, so I don’t repeat them here. Ledger warns that a device can reset during an OS update, which is why you check your backup before updating. If it has reset, you restore it from your recovery phrase, as below, and install the Bitcoin app again through Ledger Wallet.

If the device was wiped: restore it

  1. Choose restore or recover from your recovery phrase in the maker’s app.
  2. Type the 24 words from your plate on the device itself, never on the computer.
  3. Using a passphrase? Set it again. A restore only brings back the words. On the Trezor, switch passphrase on in Trezor Suite; on the BitBox02 under Expert settings; on the Ledger attach it to a second PIN again.
  4. Update to the current firmware (and on the Ledger, install the Bitcoin app). Then quit the maker’s app.
  5. In Sparrow, check that the device’s master fingerprint matches your notes (see master fingerprint explained). If it does, it’s the same key as before.
  6. Show a receive address and compare it, as in step 8. A wiped BitBox02 has lost its multisig registration, so it asks you to register again; check the keys before you approve. The Ledger’s registration proof lives in your Sparrow wallet file and is tied to the seed, so a restored Ledger normally accepts it (wallet registration explained). The Trezor stores nothing, so there’s nothing to redo.

If the device stays dead

Treat it as a broken device. In a 2-of-3 that’s not an emergency: the other two devices can still sign. Replace it and restore its seed on the new one, which doesn’t have to be the same brand, as long as it restores a 24-word BIP39 seed and works with Sparrow for multisig. The full routine is in lost or broken hardware wallet in a 2-of-3. Buy only from the maker’s own shop or from Amazon.com itself (“Ships from and sold by Amazon.com”), never from a reseller (why), and do the tamper check.

Don’t wait months, though. Until the third key is back, you have no spare.

Common mistakes

  • Resetting the device straight away instead of reconnecting and finishing the update.
  • Downloading firmware from a link in an email or a forum post.
  • Restoring the seed but forgetting the passphrase, so Sparrow sees a different fingerprint.
  • Updating all three devices on the same day. One at a time keeps two working keys in reserve.

Related