Hardware Wallet Not Connecting? What to Try Before You Reset It
If Ledger Wallet, Trezor Suite, or the Tangem app cannot see your wallet, start with the connection—not a reset. This guide separates a cable or NFC problem from a recovery emergency.
When a wallet app says it cannot find your hardware wallet, the tempting move is to reset everything and start over.
Usually, that is the wrong first move.
A connection failure is commonly a problem with the cable, USB port, phone NFC position, app, computer, or network—not proof that the wallet or its funds are gone. Resetting before you check the recovery plan can turn a simple connection problem into an access problem.
Short answer
| What you see | Safest first move |
|---|---|
| Ledger powers on but Ledger Wallet cannot see it | Try a known data-capable cable, another port, and another computer before changing wallet settings |
| Trezor Suite does not see the device | Try another data cable first; then use Trezor's official app and driver guidance |
| Tangem card or ring will not scan | Check NFC, remove a thick case, and try the correct antenna position on the phone |
| You are considering a reset | Stop and confirm the recovery phrase, passphrase, or backup devices first |
| The device is not connecting and the backup is missing | Do not reset, update, or enter words into a website; read Lost Seed Phrase but Wallet Still Works |
First, separate a connection problem from a recovery problem
Your coins are on the blockchain. The hardware wallet holds the keys that authorize transactions, while the recovery method lets you restore those keys if the device is erased, lost, or damaged.
That distinction matters here. If an app cannot see the device, it does not mean the keys disappeared. It means you should troubleshoot the link between the device and the app without making a destructive change.
Before doing anything else:
- use only the official Ledger Wallet, Trezor Suite, or Tangem app;
- close browser wallet extensions and other wallet apps that could compete for the device;
- do not type recovery words into a website, chat, or “support verification” form;
- do not factory-reset until you know exactly how you would restore the same wallet.
If you are unsure whether the backup is complete or whether you used a passphrase, pause here. Read How to Test Your Hardware Wallet Backup Before You Need It before touching a reset or firmware flow.
Ledger: a charging cable can still be the problem
Ledger's current USB troubleshooting guidance makes an easy-to-miss point: a cable can provide power without carrying the data needed for Ledger Wallet to communicate with the device.
Start with the boring checks, in this order:
- unlock the Ledger with its PIN;
- use the original cable if you still have it, or a known good data-transfer cable;
- plug directly into another USB port rather than a hub or adapter;
- restart the computer and close other wallet apps and browser extensions;
- test a second computer or phone to work out whether the device or host is the problem.
Ledger also says that if a connected device is not listed in the computer's USB information, the cable, adapter, or port may be at fault. If it is listed but Ledger Wallet still cannot connect, software interference can be the issue; Ledger specifically points to VPNs, firewalls, proxies, and antivirus tools as things to isolate.
Do not treat “it lights up” as a successful test. Power only proves that the cable can charge the device. It does not prove that it can exchange data.
Mobile connection has its own limits. Ledger says Android USB connections need a data-capable OTG path and a phone that supports OTG. For iPhone, direct USB connections are not supported in Ledger's guidance; compatible models use Bluetooth instead. Check the official instructions for your exact model rather than buying random adapters.
Trezor: change the cable before changing the wallet
Trezor's support page leads with the same practical rule: changing the cable resolves connectivity issues most of the time. It also warns that a screen lighting up does not prove that a USB cable supports data transfer.
For a Trezor that Suite cannot see:
- use an original or good-quality data cable;
- try another USB port and another supported computer;
- make sure you are using the official, current Trezor Suite;
- temporarily rule out VPN, firewall, antivirus, and browser-extension interference;
- use Trezor's official driver guidance only if the basic tests do not work.
Older Model One devices have an extra wrinkle. Trezor says firmware 1.7.0 or older uses a transport type no longer supported by current Suite, with a documented official update path through an older compatible Suite release. That is a specific compatibility case—not a reason to install random drivers or firmware from a search result.
Any firmware update deserves the same backup discipline as a reset. Trezor warns that an update can wipe a device, so confirm that the wallet backup and any passphrase are usable before proceeding. See Hardware Wallet Firmware Updates if that is where the troubleshooting path is heading.
Tangem: the phone and NFC link are the usual place to look
Tangem has no USB cable or desktop app in the classic sense. The phone is the interface, and the card or ring is read over NFC. So a “not connecting” problem is usually a scanning problem, not a failed software pairing.
Tangem's official troubleshooting guidance says to check that NFC is enabled and notes that a protective phone case can make scanning harder. It also identifies the phone's NFC module and card placement as common causes of trouble.
Try this before assuming the card is dead:
- open the official Tangem app and make sure NFC is enabled in the phone settings;
- remove a thick case, wallet attachment, or metal accessory from the phone;
- move the card slowly around the phone's NFC antenna area rather than tapping one arbitrary spot;
- try another NFC-capable phone if available;
- keep any other linked card or ring separate and safe while you troubleshoot.
Do not share the Tangem access code with “support,” and do not turn a scanning issue into a wallet-creation or factory-reset experiment unless you understand the recovery consequences. If you use Tangem's seedless model, the linked backup cards or ring are the recovery path. Read Only One Tangem Card Left? if redundancy is already a concern.
When a connection failure is more serious
Stop doing routine troubleshooting and slow down when:
- the device is physically damaged, wet, swollen, or has an unreliable screen or battery;
- a reset or firmware update is the next suggested step but you cannot find the recovery backup;
- a stranger, ad, or search result asks for recovery words to “diagnose” the connection;
- the wallet suddenly connects only after installing unofficial software; or
- you can still access it but no longer trust the old setup for meaningful funds.
A working device with an uncertain backup is not a device you should casually reset. If the wallet is still usable and the backup is missing, the safer path may be to create a fresh wallet with a verified recovery method and move funds carefully. Start with Replace a Hardware Wallet: Same Seed or New Wallet?.
Is a different wallet a better fit next time?
A connection scare can reveal a real product-fit issue, but it does not automatically mean you need to replace everything.
- Choose Ledger or Trezor if you value a dedicated transaction-confirmation screen and are comfortable maintaining a cable, app, and seed-based recovery workflow.
- Consider Tangem if your real friction is desktop software, cables, batteries, or maintaining a traditional device—and you are prepared to protect multiple linked cards or rings.
- Do not switch just to avoid learning recovery. Every self-custody model has a recovery responsibility; the useful question is which one you will consistently manage.
For the buyer decision rather than the troubleshooting detail, compare Tangem vs Ledger, Tangem vs Trezor, or use the Wallet Finder.
Bottom line
A hardware wallet that will not connect is usually a troubleshooting problem, not an instant loss of crypto. Test the cable, port, app, host device, or NFC path first. Keep your backup private and untouched while you do it.
Reset only when you know how you will recover. Never reset just because a cable or scan failed.
More in this group
Device care and problems