Wallet resilience
Lost or broken hardware wallet: understand your recovery options
By Jolly Ledger editorial · Published · Reviewed · 4 min read
Short answer
A lost or broken device does not necessarily mean lost funds: a compatible backup and any required passphrase can provide a recovery route. Missing hardware also requires a separate assessment of possible unauthorized access.
A hardware wallet is a signing device, not a container holding coins inside its casing. Losing it or breaking its screen can interrupt access without changing the blockchain’s records. The next question is which recovery materials remain available, followed by whether the missing device creates a credible risk of someone else gaining access.
First distinguish failure from possible theft
A device that stopped working after an accidental drop presents a different situation from one missing after a burglary. Neither observation alone proves the recovery phrase has been disclosed. Record what happened, whether the device could have been unlocked, and whether backups or passphrases were stored with it. Avoid sharing those secrets while seeking help.
Reach the manufacturer through a previously verified address or independently located official site. Follow its model-specific lost-device or damage guidance. A PIN is relevant to device access, but it is not a universal guarantee against every physical attack. Do not rely on a guessed number of attempts or a protection claim from another model.
What recovery normally requires
For a compatible deterministic wallet, the backup allows keys to be reconstructed on supported hardware. A passphrase, if used, is an additional requirement. BIP-39 makes different passphrases derive different wallets, so a plausible-looking empty wallet can reflect a passphrase mismatch rather than missing assets.
For SLIP-0039 backups, the configured share requirements must be met. Other arrangements have different requirements; multisig can also depend on wallet configuration and enough surviving signing keys. A device PIN is not a substitute for recovery material. Review PINs, passphrases and recovery phrases before deciding what is missing.
| What remains | What to establish next |
|---|---|
| Backup and required passphrase | Confirm format, hardware support and account settings. |
| Working spare accessing the same wallet | Confirm its access and assess the missing device separately. |
| Backup with insufficient shares | Locate the required combination without disclosing shares. |
| No backup and no usable signer | Ask official support about device-specific options; recovery may not be possible. |
Keep diagnosis from becoming exposure
Do not send a damaged device or backup to someone claiming they can recover everything. Ask official support what a repair or return involves, what information is required, and whether its process is suitable for a device that held keys. Never include a recovery phrase in a parcel, photograph or support ticket.
If another device still works, preserve it while planning recovery. Do not reset it to make the setup match an online tutorial. A recovery rehearsal helps identify requirements before any irreversible step. Actual recovery should use the manufacturer’s documented hardware workflow, not a website or desktop form asking for the words.
Before you proceed
- Write down what failed or disappeared, without recording secrets.
- Establish which backup format and passphrase requirements apply.
- Verify replacement support for your networks and accounts.
- Locate official instructions through an independent channel.
- Keep any remaining working access intact.
- Treat evidence of exposure as a separate issue from ordinary breakage.
A replacement is not necessarily a new wallet
Restoring the existing backup can restore access to the existing wallet. It does not revoke the missing device’s keys or make a disclosed backup private again. If evidence suggests actual exposure, seek the vendor’s official incident instructions promptly. The distinction between replacing hardware and creating a new wallet determines what a recovery plan can accomplish.
Sources
- BIP-39: Mnemonic code for generating deterministic keys — Bitcoin BIPs contributors
- SLIP-0039: Shamir’s Secret-Sharing for Mnemonic Codes — SatoshiLabs / SLIPs contributors
- Check backup on Trezor Safe 5 — Trezor
Reported facts are attributed to their sources. Spotted an error? Read our corrections approach.
Turn this into a preparation plan
Answer 16 calm questions about your setup. Get findings, scenario walkthroughs and a family briefing — on your own device, no account, no wallet connection, no recovery words.