Quick summary
Restore errors are stressful. I get it. What I cover here: real causes of messages like "App not running", common restore errors during a Ledger Nano X (and earlier Nano models) recovery, and practical step-by-step fixes.
This guide is based on hands-on testing and months of real-world troubleshooting. I also link to deeper setup and firmware guides when you need them (nano-x-setup, firmware-update, seed-phrase-management).
Common restore errors and what they mean
Below are the messages you'll see most frequently and what they generally indicate:
- "App not running" — the companion software or the coin app on the device isn't active or accessible. Could be a permissions, connection, or firmware mismatch.
- Seed mismatch / incorrect seed — the words you enter don't map to the private keys the device expects (wrong order, wrong word list, or wrong length: 12 vs 24 words).
- Recovery failure after entering seed — often caused by an unexpected passphrase, a different backup scheme (e.g., SLIP-39/Shamir), or corrupted backup.
- Device not detected or stuck in bootloader — USB/driver or bootloader issues preventing the restore.
What I've found: most errors are fixable with a methodical checklist. But some failures point to more serious problems, like a forgotten passphrase (25th word) or a non-standard backup method.
Step-by-step checklist before attempting a restore
- Stop and breathe. Don't rush the restore.
- Confirm you have the correct seed phrase length (12 or 24 words) and an optional passphrase if you used one. (Passphrases are invisible to the device until applied.)
- Fully charge the device and use a known-good USB cable or stable Bluetooth connection.
- Update the companion app and the device firmware if possible—see firmware-update. But do not update firmware mid-restore unless instructed.
- Use a clean, offline machine if you have a large balance—avoid public Wi‑Fi and unknown computers.
- Have your metal backup or written seed at hand; check spelling and word order slowly.
And yes, that little step of confirming the passphrase often fixes the "no account" or seed mismatch issues.
Fixing "App not running" during restore (desktop & mobile)
"App not running" can be ambiguous. Here are targeted fixes depending on how you connect.
Desktop (USB / Web):
- Make sure the device is unlocked (correct PIN) before the companion app tries to connect.
- Check OS permissions: Windows, macOS, and Linux sometimes block WebUSB or U2F. Try restarting the browser or using a different browser profile.
- If using a browser-based wallet, ensure the necessary bridge/driver is installed and the browser supports WebUSB.
- If the device is in bootloader mode it will not load coin apps—exit bootloader and retry (see troubleshooting-bootloader).
Mobile (Bluetooth):
- Toggle Bluetooth off/on on both phone and device and re-pair.
- Close other apps that could be holding the device connection.
- For Android USB-OTG restores, ensure OTG is enabled and use a cable known to support data (not charge-only).
If repeated attempts still show "App not running", try connecting to another computer or phone. If the device is not detected at all, check troubleshooting-not-detected.
Seed mismatch, passphrase (25th word), and display recovery issues
Why does a seed mismatch happen? A few common reasons:
- Word order errors. A single swapped pair prevents a match.
- Wrong word list or language. BIP-39 uses a specific English wordlist unless you explicitly used another.
- You used a passphrase (a.k.a. 25th word) during setup. That passphrase is not saved on the device and must be entered exactly the same to derive the original accounts.
- You used a different backup standard (SLIP-39 / Shamir) rather than BIP-39.
What I test first: if a restore completes but accounts show zero balance, it's usually a passphrase or derivation-path mismatch.
Quick checks:
- Recount words and verify each word against the official word list.
- Try restoring into a trusted, offline compatible wallet that supports BIP-39 (only if you accept temporary risk) to confirm the seed.
- If the device normally displays the recovery phrase but now won't, do not type the seed into any app. Instead, consult seed-phrase-management and escalate to support if the screen is unresponsive.
But don't panic if you see mismatches; methodical checking usually finds the cause.
Restoring Monero and other special-case coins
Some blockchains require extra steps. Monero is one of them. You typically need a desktop Monero client that supports hardware wallets. Restoring Monero from a hardware wallet often involves opening the blockchain client and choosing "Restore from hardware wallet." For detailed, step-specific instructions see monero-guide.
Other coins may require specific derivation paths or a third-party wallet. If a restore shows unexpected addresses or no balance, check the wallet integration documentation (wallet-integration).
Recovering when the device is broken or lost
Short answer: if you have the seed phrase and any passphrase, you can recover funds on another compatible device or software wallet. Long answer: nothing stored on a single hardware wallet is unique—your private keys are derived from your seed phrase, so the recovery is possible anywhere that supports the same standards.
If the device is physically damaged and you have only a paper backup, act quickly and use a trusted environment. See full steps at recover-if-broken.
If you lose the passphrase and never recorded it, recovery is effectively impossible. That is why passphrase management is part of the early checklist.
Firmware, app authentication, and supply-chain checks
Firmware authors sign releases for a reason. Running an unverified firmware or using an unofficial companion app can break restores or introduce risk. Before a restore:
- Verify firmware signatures when prompted (follow the device's on-screen steps).
- Use the official companion manager and install only official coin apps.
- If you bought a device second-hand, check supply-chain guidance (authenticity-supply-chain).
I noticed in testing that outdated companion apps or blocked OS permissions often present as "app not running" even when the device appears fine.
Common mistakes to avoid
- Typing your seed phrase into a website or an email draft (never do this).
- Buying from an unofficial seller (see where-to-buy-safely).
- Forgetting about an added passphrase (25th word).
- Attempting a firmware update mid-restore.
Who this hardware wallet is for (and who should look elsewhere)
Who it's for: people who want mobile connectivity, wide coin support, and a compact device for everyday self-custody. In my experience it fits hobbyists and intermediate users who trade and hold across several blockchains.
Who should look elsewhere: users who require fully air-gapped workflows or prefer built-in multisig features out of the box. Also, if you are uncomfortable with Bluetooth or mobile pairing, consider a strictly USB-only workflow.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes, with the seed phrase and the exact passphrase if used. See recover-if-broken.
Q: What happens if the company goes bankrupt?
A: Your seed phrase is standard; you can restore on compatible wallets as long as the standards (BIP-39, SLIP-39, etc.) are supported. But always check compatibility before relying on a single vendor.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth increases convenience and the attack surface. However, the secure element on the device performs signing locally, and secure protocols minimize risk. If extreme air-gapped security is required, avoid Bluetooth.
Q: I'm getting "restore seed phrase app not running" — what now?
A: Follow the desktop/mobile troubleshooting steps above, confirm firmware/app versions, and verify you are entering the correct seed and passphrase.
Conclusion and next steps
Restore problems are usually resolvable with a calm, step-by-step approach: confirm your seed and passphrase, verify device and companion app state, and check firmware status. What I've found repeatedly is that patience and the checklist above solve the majority of errors.
If you're still stuck, consult the full restore walkthrough (restore-recovery) or the troubleshooting index (troubleshooting-general). And if you need hands-on help, the support and warranty page can guide you next (support-warranty).
