Use this BitBox recovery help page before restoring, resetting, replacing a device, changing firmware, or responding to any support message asking for recovery words.
Independent wallet security guidance. This site is not BitBox.
BitBox help topics
Wallet security
Quick issue summary
Ledger and Trezor support teams should never ask for a recovery phrase, seed phrase, private key, or remote access to a wallet.
Recently Reported Issues
BitBox recovery help starts with one rule: do not share or type the recovery phrase into websites, chats, forms, screenshots, or remote sessions. Restore only inside the intended wallet flow.
Common wallet topics include BitBox recovery help, recovery phrase problem, restore issue, lost seed phrase, missing accounts after restore, reset concern, or fake BitBox support request.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
If funds look missing after restore, check account and sync display first.
OpenReview backup readiness before firmware or reset steps.
OpenConnection issues should not require seed words.
OpenApp troubleshooting should not require recovery phrase entry.
OpenReturn to BitBox Wallet support for safe next steps.
OpenReport non-private recovery symptoms to PhraseWallet.
OpenBitBoxApp troubleshooting is safest when you separate display, sync, device, firmware, and recovery phrase concerns before changing wallet settings. Use official BitBox support links for device-specific instructions.
Use these checks to separate ordinary setup friction from wallet safety risk before you reset, restore, reinstall, or open wallet support portals.
Use a data-capable cable, confirm computer permissions, avoid untrusted browser prompts, and check whether the official app recognizes the device before restoring anything.
Handle firmware updates only through verified official software. A firmware prompt should not require typing seed words into a website, chat, or support form.
Zero balance or missing transactions can come from the wrong account, network, passphrase, derivation path, sync delay, or exchange withdrawal still pending.
Keep the phrase offline and private. Do not photograph it, paste it into support, or use a recovery check page from an ad, email, DM, or search result.
Read the device screen carefully before approving. If the destination, network, fee, or contract request is unexpected, reject and investigate first.
Avoid remote access, paid recovery, messaging-app helpers, fake live chat pages, and anyone asking to be added to your wallet or computer.
Start with the most common causes before resetting the wallet, restoring from a recovery phrase, or trusting a support message.
Step 1
Do not type, upload, photograph, or read recovery words to any BitBox-looking website, support account, form, or caller.
Step 2
A PIN or app password unlocks local access. The recovery phrase controls wallet restoration and must stay offline.
Step 3
If you must restore, use the official wallet flow and confirm word order, language, wallet account, network, and any passphrase context you intentionally used.
Step 4
If the phrase was entered into a website or chat, treat the wallet as at risk and use official safety guidance before moving funds or depositing more.
Before reinstalling, confirm backup readiness, selected wallet account, and whether the issue is app access, device detection, or balance display.
Do not reset a hardware wallet unless you understand recovery requirements and have the phrase safely stored offline.
If addresses or balances differ after restore, check account, network, sync, and passphrase context before restoring again.
Expected flow
Any request for recovery words, seed phrases, private keys, remote access, or wallet screenshots with secrets should be treated as a serious warning sign.
Do not type, upload, photograph, or read out recovery words to any website, chat, form, or caller.
Use official BitBox support links directly instead of links from messages, ads, comments, search results, copied Suite/Live downloads, or firmware mirrors.
If the phrase was entered online, assume the wallet may be compromised and avoid further deposits.
Use official wallet safety guidance before moving funds or restoring on a device, and avoid remote-access helpers during recovery.
No legitimate wallet support should need your recovery phrase, private keys, PIN, or one-time wallet credentials.
What users commonly report: Fake support flows often appear after a restore, update, QR-signing failure, or missing-balance panic and ask users to validate seed words or connect to a remote helper.
For official BitBox help, downloads, updates, or contact options, use BitBox's official portal and verified official channels. This page helps you prepare safe, non-private context before opening support portals.
No legitimate wallet guidance should need your recovery phrase.
A recovery phrase controls wallet restoration. Treat it as private self-custody information and review how phrases work before using any wallet.
Community reports
BitBox troubleshooting reports often involve BitBoxApp behavior, USB detection, firmware prompts, balance visibility, recovery planning, and fake support warnings. These examples avoid private wallet data and focus on the support pattern.
These examples are informational and reflect common user-reported wallet issues. Never share your recovery phrase, seed phrase, private keys, PIN, or wallet backup with anyone. Official wallet support should never ask for your recovery phrase.
“A support message said it could fix BitBox if I shared my seed phrase or screen.”
Fake support often appears during update, restore, missing-balance, and QR-signing stress. No legitimate wallet support flow should ask for recovery words, private keys, PINs, or remote access.
“The restore finished, but BitBox is showing different addresses or no expected funds.”
Some restores initially show empty wallets until the right account type, passphrase context, derivation path, network, or imported account view is selected.
“BitBox shows an empty or delayed balance after the app or firmware update.”
Users often report temporary balance delays after firmware or app updates until the device reconnects, account discovery runs, and the correct network or token view refreshes.
“BitBoxApp connection stopped working after an app update or reconnect.”
Pairing and detection problems commonly involve stale app sessions, device prompts, USB data, firmware state, permissions, or another wallet session holding the connection.
Report wallet issue
Submit a non-secret wallet problem for moderated review and safer routing. PhraseWallet is independent and this is not official wallet support or emergency recovery assistance.
Never enter your recovery phrase, private key, password, PIN, or payment details.
Common wallet issues
Use these maintained support paths to move from a symptom to the right setup, recovery, troubleshooting, or security help without sharing private wallet data.
Related problems
If this page is close but not exact, check these nearby support topics so the next step matches the failure pattern.
Separate app launch from USB permission, cable, device prompt, and firmware readiness checks.
Open helpCheck account selection, BitBoxApp sync, transaction status, and restore/passphrase context after updating.
Open helpA different backup, passphrase, or account view can restore cleanly while showing no expected funds.
Open helpAvoid remote helpers and anyone asking for recovery words, private keys, PIN, or wallet validation.
Open helpOfficial wallet support should never ask for your recovery phrase, seed phrase, private keys, PIN, wallet backup, screen sharing, or remote access. Verify downloads, QR tools, and update prompts on the official wallet site before acting.
FAQ
No. Self-custody recovery depends on the recovery phrase or backup method, and legitimate support should not ask you to share it.
No. A PIN or password unlocks local access. The recovery phrase restores the wallet and must remain private.
Treat the wallet as potentially compromised, avoid further deposits, and use official wallet safety guidance before moving funds.
Possible causes include wrong phrase, word order, passphrase context, account path, network selection, or app sync delay.
Use official BitBox support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.