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).
Below are the messages you'll see most frequently and what they generally indicate:
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.
And yes, that little step of confirming the passphrase often fixes the "no account" or seed mismatch issues.
"App not running" can be ambiguous. Here are targeted fixes depending on how you connect.
Desktop (USB / Web):
Mobile (Bluetooth):
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.
Why does a seed mismatch happen? A few common reasons:
What I test first: if a restore completes but accounts show zero balance, it's usually a passphrase or derivation-path mismatch.
Quick checks:
But don't panic if you see mismatches; methodical checking usually finds the cause.
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).
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 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:
I noticed in testing that outdated companion apps or blocked OS permissions often present as "app not running" even when the device appears fine.
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.
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.
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).