Restored Hardware Wallet but Balance Is Zero? What Usually Went Wrong

If you restore a hardware wallet and the balance is suddenly zero, the most likely explanation is not that the coins vanished. The more common explanation is that you opened the wrong wallet.

With self-custody, the wallet app is just a window into keys and addresses that already exist on-chain. If the restored wallet shows the wrong addresses, the wrong passphrase wallet, or the wrong derivation path, the app can look empty even while the original coins are still sitting untouched at the old addresses.

Short answer

Before you panic, assume wallet mismatch before coin loss.

The first five checks to do before you touch anything else

1. Confirm the receiving address you used before

If the receive address in the restored wallet does not match the address that originally received the coins, you are looking at a different wallet.

That is the core rule across Ledger and Trezor support guidance: addresses do not randomly change after recovery. A different address means different private keys, which means a different backup and/or a different passphrase was used.

2. Check whether you used a passphrase wallet before

This is one of the most common causes of an "empty" recovery.

Ledger and Trezor both separate the standard wallet from passphrase-protected wallets. If you restore only the base recovery phrase, but your real funds lived behind a passphrase, the normal wallet can appear empty even though the recovery itself technically succeeded.

A few easy ways this goes wrong:

• you restored the seed phrase but forgot to load the passphrase wallet
• you typed the passphrase with different capitalization
• you added or removed a space
• you changed keyboard layout
• you accidentally opened the standard wallet instead of the hidden/passphrase wallet

If this sounds familiar, read Forgot Your Hardware Wallet Passphrase? before guessing further.

3. Re-check the backup itself before wiping or resetting again

Trezor explicitly recommends running a backup check when balances do not appear after recovery. Ledger's support guidance is similarly blunt: a zero balance usually means the device currently holds a different recovery phrase than the one that created the original accounts.

That matters because repeated resets do not help if you keep restoring the wrong words.

Use the brand's official check flow before making the situation more confusing:

• Ledger: verify the recovery phrase and re-add the correct accounts in the official app
• Trezor: run the dry-run backup check in Trezor Suite
• Tangem: double-check the imported seed phrase, passphrase, and source-wallet details before resetting the cards again

Our guide on How to Test Your Hardware Wallet Backup Before You Need It covers the safer mindset here.

4. Make sure the coin or account is actually enabled in the app

Trezor notes that reinstalling or resetting Trezor Suite can leave some coins disabled in settings. Ledger also explains that a fresh app install does not magically remember your locally added accounts.

This check is boring, but worth doing:

• re-add the account in the official app
• enable the relevant coin/network in settings
• check whether you are viewing the right account index
• confirm whether the wallet used one account or several for the same chain

Do this before you assume a recovery failure.

5. Stop entering the seed phrase into random apps and websites

An empty recovery screen makes people desperate, and desperation is when phishing works.

Do not test your seed phrase in a browser form, "wallet recovery" website, Telegram support chat, or AI-generated troubleshooting script. Use only the official Ledger, Trezor, or Tangem recovery flow.

If the phrase has already been exposed during this panic, switch to Seed Phrase Exposed? What to Do Before Your Crypto Is Stolen instead of continuing to experiment.

Ledger: zero balance usually means wrong recovery phrase or missing passphrase

Ledger's support documentation spells out two especially common causes:

1. a new install of Ledger Wallet / Ledger Live needs accounts to be manually re-added because app data is stored locally;
2. a zero balance after re-adding the account usually means the device currently holds a different Secret Recovery Phrase than the one that created the original account.

Ledger also warns that passphrase-protected accounts are completely separate from standard accounts. If you used the passphrase feature before, you must load the exact same passphrase again to see those balances.

A useful mindset for Ledger users is simple:

• new phone or computer can make the app look empty even when recovery is fine;
• zero balance after re-adding the account usually points to the wrong seed phrase;
• wrong private keys / selected account error usually means the wrong seed phrase, wrong device, or wrong passphrase is active.

If you are also deciding whether to keep the same backup model after this scare, Ledger Recovery Key vs Ledger Recover explains the practical tradeoff.

Trezor: wrong wallet backup or wrong hidden wallet is the usual culprit

Trezor's troubleshooting flow is very direct: if the restored receive address does not match the old one, you are accessing the wrong wallet.

Trezor lists five common causes:

1. the coin is not enabled in Trezor Suite;
2. the wrong wallet backup was imported;
3. the passphrase was typed incorrectly;
4. the funds are in a passphrase wallet but you opened the standard wallet;
5. the funds were in the standard wallet but you opened a passphrase wallet by mistake.

Trezor also emphasizes an important passphrase detail that catches people off guard: every incorrect passphrase creates a new hidden wallet. That means a typo does not fail loudly. It can succeed quietly by opening a different empty wallet.

If you think the words may be right but the wallet is still wrong, Trezor's dry-run backup check is one of the best sanity checks you can do before wiping the device again.

Tangem: imported wallets can look incomplete because of path and address-type differences

Tangem is different from Ledger and Trezor because many users either run Tangem seedless with backup cards or import an older seed phrase from another wallet.

For imported seed-phrase wallets, Tangem's help-center guidance adds two problems that are less obvious:

• the source wallet may have used a different derivation path;
• the source wallet may have used address types Tangem does not currently restore in the same way.

Tangem says a zero or incomplete balance after import can happen when:

• the wrong seed phrase was entered
• the words were entered in the wrong order
• a passphrase used by the old wallet was not entered during import
• the source wallet had multiple accounts for the same coin
• the source wallet used non-standard derivation paths
• the source wallet used unsupported Bitcoin address types for import, including some P2SH or Taproot setups

Tangem's derivation-path documentation is especially useful here: if the old wallet created several addresses for the same coin, Tangem may show only the first consecutive addresses by default. In that situation, the balance can look missing even though the original funds are still on the old addresses.

This is one reason some readers are better off creating a fresh wallet and transferring funds, rather than assuming any seed import will map perfectly across apps. If that buyer decision is relevant to you, see Should You Import a Hot Wallet Seed Phrase Into a Hardware Wallet? and Tangem Wallet Review.

A practical order for troubleshooting without making things worse

Use this order instead of jumping straight into more resets:

1. check the old receiving address you expect to see
2. confirm whether the old wallet used a passphrase
3. verify whether you opened the standard wallet or the hidden/passphrase wallet
4. re-check the recovery words carefully, in the correct order
5. enable the missing coin or re-add the account in the official app
6. review whether the source wallet used multiple accounts or unusual derivation paths
7. only then consider another wipe-and-restore attempt with the correct information

If you still have access on the original device, that device matters more than the new restore attempt. Do not wipe it just because the new wallet looks empty. First use the still-working device to confirm addresses, passphrase behavior, and account structure.

If the original device still works but the backup situation looks shaky, read Lost Seed Phrase but Wallet Still Works next.

When the balance problem is probably not a recovery problem

Sometimes the wallet is correct, but the app is still misleading you. Official support docs across these brands point to a few non-recovery causes too:

• app settings or account lists were reset on a new device
• the token is not added to the home screen yet
• the wallet app is outdated or still syncing
• the balance is on a different network than the one you opened
• the wallet used a third-party app for a coin that does not display the same way in the main app

That is why "my wallet is empty" is too broad a diagnosis. The real question is: are the original addresses the same, and are you viewing them through the same backup + passphrase + path combination as before?

Bottom line

A restored wallet showing zero balance usually means the restore opened the wrong wallet, not that the blockchain erased your coins.

For Ledger and Trezor, the biggest culprits are the wrong recovery phrase and the wrong passphrase wallet. For Tangem imports, derivation-path and address-type mismatches can also make real balances look missing.

The safest response is calm verification, not repeated resets:

check addresses, check passphrases, check the backup, and only trust official recovery flows.

Source notes

How we checked this guide: we reviewed official Ledger support articles on missing accounts, wrong private keys, and passphrase-account recovery; Trezor support articles on missing crypto, hidden-wallet/passphrase issues, and backup-check troubleshooting; and Tangem help-center/blog documentation on seed-phrase import issues, incomplete balances, derivation paths, and supported address-path behavior before publishing.