If you landed here because your ledger wallet showing 0 balance, ledger not showing wallets, or your ledger wallet wont open, you’re not alone. Hardware wallets are intentionally minimal: the device holds private keys while a companion app (desktop or mobile) displays balances and lets you sign transactions. When the display or app disagrees with on-chain explorers the cause is almost always one of a few categories: connectivity, account selection (derivation path), app/firmware mismatch, or synchronization issues.
I’ve been using hardware wallet setups since 2017 and in my testing the majority of problems are resolvable with methodical checks. What I’ve found is that small misconfigurations (one wrong account, an extra passphrase) cause most panic. But don’t panic. (Yes, really.)
See also: getting started and setup basics and firmware update & verification.
Do this first before deeper troubleshooting:
If those quick steps don’t help, proceed to the symptom-specific sections.
Below is a short table mapping symptoms to likely causes and quick fixes.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| Shows 0 balance | Wrong account / derivation path or app not installed | Compare device address to explorer; install the coin app; add accounts (multiple-accounts-and-wallets) |
| Missing wallets/accounts | App not installed on device or filtered accounts | Open manager, install app, add missing accounts |
| Device won't open / frozen | Firmware or power/connection issue | Force-restart, try another USB; see troubleshoot-firmware-stuck |
| "Last synchronization did not complete" | Network, firewall, or app cache | Clear cache/reinstall companion app; check network/proxy |
| App crashes | Corrupt cache, OS driver, antivirus interference | Reinstall app; check OS updates; try mobile client |
Common cause: the companion app is connected to a different account or derivation than the address that actually holds funds. First, verify the receive address on the device screen. Then paste that address into a block explorer. Does the explorer show funds? If yes, the device and private keys are fine — the companion app simply isn’t showing the derived account.
Step by step:
If addresses don’t match, check whether a passphrase was used. See passphrase-usage-risks and seed-phrase-basics.
This often happens when the device’s internal app for a blockchain is not installed, or when the companion app filters by token type. Install the required app on the device (manager) and then add the account in the companion app. Look at the supported coins list: supported-cryptocurrencies and wallet-compatibility-matrix.
In my experience, users forget to install the chain app after a firmware update. That’s an easy miss.
If the device won’t boot or the screen is stuck, try a forced restart (disconnect, wait 10s, reconnect while pressing the right button). If that fails, check the firmware troubleshooting guide: troubleshoot-firmware-stuck.
But if the device powers on and the companion app refuses to connect, try the cable and port swap mentioned earlier. Faulty cables are more common than you think. See usb-cables-pairing.
This error occurs when the companion app cannot fully fetch account data from remote servers. Typical causes: proxy/firewall blocking traffic, server-side hiccup, corrupted local cache.
Fixes:
Crashes are usually due to OS incompatibilities, corrupted cache, or interference from security software.
Try:
If crashes continue, collect logs and reach out to community resources (see resources-downloads-community).
A hidden passphrase (the so-called 25th word) creates a separate set of addresses. If you used one years ago and forgot, those accounts will not appear and balances look "missing." What I've found: many recovery headaches could be avoided by documenting passphrase use safely.
Derivation path differences (BIP-44/BIP-49/BIP-84 or custom paths used by third-party wallets) will also generate different addresses. If you manage multisig, companion app compatibility matters; check multisig-setups and advanced-derivation-paths.
If you use Shamir backup (SLIP-39) or metal backup plates, make sure your recovery flow matches the backup method. See backup-metal-slip39.
USB is simple and reliable. Bluetooth adds convenience but a slight increase in attack surface because it broadcasts; most real-world attacks require user interaction and an unlocked device, though. NFC is less common but similar: low convenience, low risk if used correctly.
Practical tips:
More on pairing and connections: connections-usb-bluetooth-nfc.
Restore only when you’ve exhausted connection and app fixes or when replacing a lost/damaged device. Restoring exposes your seed phrase if done carelessly, so prepare an air-gapped environment if possible.
Step by step (brief):
See full guides: restore-recover-failure and seed-phrase-basics.
I believe most problems are preventable with basic operational hygiene.
Q: Can I recover my crypto if the device breaks? A: Yes, if you have your seed phrase (recovery phrase). Use it to restore on a new compatible hardware wallet or supported software wallet. See: restore-recover-failure.
Q: What happens if the company behind the device goes bankrupt? A: Your private keys are non-custodial. As long as you have your recovery phrase, you can restore funds on compatible wallets.
Q: Is Bluetooth safe for a hardware wallet? A: Bluetooth has a slightly larger attack surface than USB but remains acceptable for many users. For maximum security use USB and avoid Bluetooth when performing high-value transactions.
Q: Why does my companion app say "last synchronization did not complete"? A: Usually a networking or cache issue. Try clearing the app cache, disabling VPN, or reinstalling the companion app.
If you’ve worked through the steps above and still see your ledger wallet showing 0 balance, ledger not showing wallets, or your ledger wallet wont open, collect logs, note exact error messages, and reach out to official support or community channels. And if you’re unsure about a step that touches your seed phrase, pause and review the recovery guides.
For step-by-step setup and deeper guides, check: getting-started-setup, firmware-updates-and-verification, and troubleshoot-cannot-connect.
If you want help diagnosing a specific error message, paste the full text of the error (don’t paste your recovery phrase). I’ll walk you through the next steps.