Troubleshooting

Trezor set-up problems, and how to get past them

Nearly every failed start-up is one of five things: a cable, a port, a driver, a firmware write, or a browser. Work down this page in order — it is written from the most likely cause to the least.

7 minute read Reviewed September 2026

1. The device is not detected by Suite

Try this first: a different USB cable, plugged straight into the computer, with the device awake. Charge-only cables and unpowered hubs account for most "not detected" reports.

  1. Use the cable that came in the box. If you no longer have it, use a cable you know carries data — many spare cables charge only.
  2. Plug into a port directly on the computer. Avoid hubs, docking stations, monitor USB ports and front-panel extensions.
  3. Wake the device first: press its button or tap the screen, then reconnect the cable.
  4. Try another port, and on a desktop try one on the back of the machine.
  5. Close any other wallet software, browser tab or app that may be holding the device.
  6. Restart Suite (fully quit, not just minimise) and reconnect the device.
  7. Restart the computer, then try again before reaching for anything more drastic.

Windows-specific notes

  • If the device shows up as an unknown device, install the official Suite build again — it includes the components it needs.
  • Antivirus software occasionally blocks the connection; if the problem appeared right after an update, test with the blocking temporarily disabled.

macOS and Linux notes

  • On macOS, approve the connection prompt the first time the device is plugged in.
  • On Linux, normal desktop users rarely need extra rules, but containerised environments and restricted user accounts sometimes do — try a standard desktop session first.

2. Firmware installation fails or hangs

The firmware write is the one step where interruptions genuinely matter. If it stops partway, do not unplug and retry repeatedly — recover the process calmly.

  1. Wait a full minute before assuming it is stuck. A write can look frozen and still be progressing.
  2. If Suite reports a failure, leave the device connected and let Suite retry the installation.
  3. If the device restarted unexpectedly, reconnect it and let Suite detect the state it is in.
  4. Prevent interruptions before you start again: plug the laptop in, disable sleep, and close heavy applications.
  5. Use a shorter cable, and once more, a port directly on the computer.

A device with no valid firmware holds no keys, so a failed installation during first-time set-up threatens nothing except your patience. The dangerous case is a partial update on a device that already holds your wallet — but even then, your recovery seed still restores everything.

3. The device is stuck in bootloader mode

Bootloader mode is the device's own firmware-installation state, and it is not damage. You will usually see a distinctive message or a blank screen instead of the normal welcome.

  • Open Suite and connect the device. Suite normally detects bootloader mode and offers to install firmware.
  • If it does not, disconnect, wait ten seconds, and reconnect — detection on the second attempt is common.
  • Let the installation complete without unplugging, then let the device restart on its own.
  • If the device loops back into bootloader mode after a "successful" install, try a different cable and port before assuming a hardware fault.
  • If it still loops, contact official support with the model, the version shown on screen, and exactly what Suite reported.

4. Suite will not open, or opens blank

  1. Reinstall the app from the official source — it is a small download and this resolves most launch problems.
  2. Update your operating system if it is significantly out of date; very old system libraries break modern desktop apps.
  3. If a security tool quarantined part of the app, restore it and add an exception, then reinstall.
  4. On a work-managed computer, group policy may block USB device access entirely. Use a personal computer.
  5. Blank window or stuck loading: quit completely, reopen, and let it finish syncing before clicking anything.

If you only have access to a browser, the web version at suite.trezor.io can be a stopgap for viewing balances — but do the initial firmware and seed steps on the desktop app if you possibly can.

5. PIN problems

"My PIN is rejected"

  • Remember that you enter the PIN on the scrambled layout shown by Suite or on the device — use the on-screen positions, not the digits you memorised in order, when the layout asks for positions.
  • Slow down. Two fat-fingered attempts are normal; more than a few are a risk, because a device wipes itself after too many wrong entries.
  • Stop and write down which digits you believe you used, in order, before trying again.

"I have forgotten the PIN"

  • There is no PIN recovery service, by design. Your recovery seed is the only way back.
  • Let the device wipe itself after the failed attempts, then restore the wallet from your written seed.
  • If you do not have the seed, the funds on that device are unrecoverable. No support team can change that.

Anyone who contacts you offering to recover a wallet for a fee, or asking for your seed words to "unlock" it, is running a scam. There is no legitimate recovery service for a hardware wallet.

6. Seed and backup problems

"Suite rejects one of my seed words"

  • Check the word against your paper copy letter by letter — most rejections are a single swapped or missing letter.
  • Check the order. Word order matters as much as the words themselves.
  • Check the spelling language: the seed list is a fixed set of words, and a near-miss is a different word.

"I restored and my balance is zero"

  • If you used a passphrase, a typo opens a different, empty wallet. Try again with exact capitalisation and spacing.
  • Confirm you restored the seed of the wallet you are looking for — people who own two wallets often mix them up.
  • Wait for Suite to finish syncing accounts before concluding anything is missing.

One good rule: practise a restore before you need it. Wipe the device deliberately, restore from your paper backup, and confirm the accounts reappear. That is the only proof your backup works.

7. Balance or address issues

  • Funds sent but no balance: check the transaction on a public block explorer first. If it is unconfirmed, the wallet is right and the network is slow.
  • Sent to the wrong network: an address is only valid on its own chain. Test with a small amount, and check the network name in the sending app, not just the address.
  • Address mismatch between Suite and the device: stop. Trust the device screen only, and treat the computer as potentially compromised.
  • Missing tokens: some assets need their account to be added inside Suite before they display.

8. If your device or an app asks for your recovery seed

This is the one "problem" that is not a problem — it is an attack. Legitimate firmware, legitimate Suite versions and legitimate support never ask for your seed words.

  • Do not type the words into the computer, a website, a chat window or a form.
  • Do not type them into the device because a page on your screen tells you to.
  • Disconnect, close the page, and re-install Suite from the official site before continuing.
  • If the words were already entered anywhere digital, treat that wallet as compromised: create a new one and move funds.

9. Getting real help

Where to go

The official knowledge base and support channels, reached from the official website, are the only places to take a genuine hardware or firmware fault. Have your model, firmware version and exact error text ready.

Where never to go

Direct messages, comment replies, "official support" accounts that message first, and anyone offering a remote session. Real support will not ask for your seed, your PIN or your screen.

Back to the walkthrough

If the device is behaving, the next step is waiting for you.