Use this BitBox support page when BitBoxApp opens but does not detect the hardware wallet, recognition fails during setup, or the device disappears during wallet actions.
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
A BitBox wallet not detected problem is commonly a USB session, app permission, device prompt, firmware mode, stale BitBoxApp state, or wrong setup context issue.
Common wallet topics include BitBox wallet not detected, BitBoxApp recognition problem, USB session issue, device prompt problem, firmware state, or fake BitBox app warning.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
Use broader USB connection checks if detection is one part of the problem.
OpenIf BitBoxApp fails before detection, troubleshoot app launch and permissions.
OpenIf the wallet is detected but assets are missing, troubleshoot account and sync display.
OpenFirmware state can affect whether BitBoxApp recognizes the device.
OpenReturn to BitBox Wallet support for broader troubleshooting help.
OpenReport non-private BitBoxApp detection 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
Confirm the app source before reconnecting. A fake app can look like a detection tool while trying to capture recovery words.
Step 2
Quit BitBoxApp, unplug the device, reconnect with a data cable on a direct USB port, unlock the device, and retry the detection step.
Step 3
Detection can fail when the device is waiting for setup, unlock, firmware, or confirmation while the app expects a different state.
Step 4
If BitBoxApp detects the wallet but assets are missing, move to balance visibility checks instead of repeating detection.
Check app version, USB permission state, selected wallet, pending prompts, and whether a previous connection attempt is stuck.
Unlock the device, review the current screen, and do not enter recovery words into any website or support form to make detection work.
Use a known data cable, direct computer port, and trusted computer before trying deeper app reinstall or recovery steps.
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.
“My KeepKey powers on, but the wallet app will not connect to it.”
Connection issues may involve charge-only USB cables, unstable hubs or adapters, device prompts, app state, firmware mode, or another wallet session using the device.
“My Trezor is connected by USB, but Trezor Suite does not recognize it.”
Connection issues may involve USB cable type, bridge or web permissions, outdated firmware, browser support, or device authorization prompts.
“My KeepKey firmware update is stuck and I do not know if it is safe to continue.”
Firmware update problems can involve USB instability, update mode, app prompts, operating system permissions, or fake support pages exploiting update panic.
“KeepKey shows zero balance after reconnecting, but I expected funds to be there.”
Zero-balance displays may involve wrong account, network, stale wallet app sync, missing account after restore, or a different recovery phrase context.
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 support paths to move from a symptom to the right setup, recovery, troubleshooting, or security help.
Related problems
If this page is close but not exact, check these nearby support topics.
Use the BitBox support hub for BitBoxApp, USB, firmware, balance, recovery, and security help.
Open helpShare non-private symptoms to help organize recurring BitBox support problems.
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, or wallet backup. Verify downloads and update prompts on the official wallet site.
FAQ
Common causes include blocked USB permissions, stale app state, a charge-only cable, wrong device screen, old BitBoxApp version, firmware mode, or fake app source.
No. Detection problems are usually local app, device, cable, or computer issues. Check address and network separately before assuming funds moved.
No. Detection should not require typing recovery words into a website, chat, app prompt from an unverified source, or support form.
Computer type, device model, BitBoxApp version if known, current step, error text, and screenshots without private information are safer than private keys or seed words.
Use official BitBox support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.