If your BitBox02 does not connect to MyEtherWallet (MEW), identify the stage that fails: finding the hardware-wallet option, detecting the device, unlocking or pairing, or handling a specific error. The checks below use a BitBox02 Multi with an existing wallet, connected by USB to desktop Google Chrome through MEW's legacy interface.
If the dashboard already opens but an expected balance is missing, use Find funds sent on another EVM network with MyEtherWallet and your BitBox02. That is an account, network, or transfer investigation rather than a device-connection test.
Keep wallet secrets out of MEW
Never enter recovery words, a private key, device password, optional passphrase, or wallet backup into MEW. If a site requests these details or the pairing codes on your BitBox02 and in MEW differ, stop and contact BitBox Support. Do not continue approving connection requests.
When the BitBox02 option is missing
MEW's newer interface can differ from the legacy hardware-wallet interface used by this guide. Check the route before changing software or device settings.
-
Open the official legacy access page. In desktop Chrome, open MyEtherWallet's legacy wallet-access page. Check the address
https://www.myetherwallet.com/wallet/accessand the page heading Access my wallet. - Check the hardware options. Select Hardware wallets, then look for BitBox02 in Select a hardware wallet. If it appears, select it and continue with Connect your BitBox02 to MyEtherWallet (MEW).
- Report a continuing route problem. If the option is still absent at this exact route, record the visible page heading and any non-sensitive error. Ask Support to verify current integration availability rather than selecting a software-wallet import option.
When Chrome does not list the device
This branch applies after Unlock BitBox02, when Chrome's device chooser is empty or cannot open the device. If you simply cancelled the chooser, open it again and select the device; this is not a wallet-password failure.
- Release competing connections. Close the BitBoxApp completely and close other wallet applications or tabs using the BitBox02. Leave only the MEW access tab for this test. If you have several BitBox devices attached, leave only the intended BitBox02 connected.
- Reconnect the intended device. Disconnect and reconnect the BitBox02 by USB, then select its display orientation. Retry Unlock BitBox02. If Chrome lists the device, select it and choose Connect; continue with device unlocking in the connection guide.
- Separate USB detection from MEW access. If the device remains absent, close MEW before opening the official BitBoxApp with the device connected. Check whether the app recognizes it; do not initialize, reset, or restore a wallet for this test. If it does not recognize it, follow How to fix a BitBox not recognized via USB.
- Retry after an ordinary detection test. If the BitBoxApp recognizes the device normally, close the app completely, reopen the official MEW route, and retry. Normal app detection narrows the issue to the browser or integration path. If Chrome still cannot open it, report both results to Support instead of repeating wallet setup.
If Chrome still cannot open the device after other apps and tabs are closed, quit and reopen Chrome, then retry the official route. Do not disable a firewall, antivirus, VPN, or browser privacy protection as a generic connection fix.
When unlocking or pairing does not complete
A message or animation waiting for the device is not a request to type its password into the website. Enter the device password and, if enabled, the intended wallet's optional passphrase only on the BitBox02.
- Check the device's current prompt. If it is locked, complete password entry on the device. If you cannot unlock your existing wallet, stop the MEW test and ask BitBox Support for the appropriate access guidance. Resetting the device is not a connection fix.
- Compare pairing codes when shown. Check the full code in MEW against the code on the BitBox02. If they match, confirm on the device first, then select Confirm in MEW when that button becomes available. If they differ, reject the pairing and contact Support.
- Retry only a deliberate cancellation. If you knowingly cancelled a matching pairing or an ordinary connection request, restart from Unlock BitBox02 when ready. If rejection is unexplained, repeated, or associated with differing codes, stop instead of repeatedly approving.
A previously paired session may proceed without a new pairing code. Successful access is the intended account and network appearing on the dashboard; an unfamiliar account belongs to the wallet/account checks in the connection and missing-funds guides.
When MEW shows a specific error
Use the error's meaning and the failed stage to choose the next action. Some legacy error wording is outdated; a message referring to Bluetooth does not establish that this USB procedure requires Bluetooth.
| Error or state | Safe next action |
|---|---|
| BitBoxBridge not found | The documented desktop Chrome method can use direct USB without BitBoxBridge. Retry that method through the connection guide. If a bridge-based path was intentionally used, see the bounded bridge check below. |
| A firmware upgrade is required | Close MEW and follow How to update the BitBox02 firmware through the official BitBoxApp. After a completed update, close the app before retrying MEW. Do not obtain firmware from an error message's unofficial link. |
| MEW does not support this firmware version | Record the firmware version and exact message, then contact Support. Do not downgrade, reset, or restore the wallet to force compatibility. |
| The device is not initialized | This guide assumes an existing wallet. If a device that should contain your wallet unexpectedly appears uninitialized, stop and contact Support before setup. New-device setup is a separate task. |
| Unsupported device | This procedure covers BitBox02 Multi. The Bitcoin-only edition cannot access Ethereum accounts. Ask Support to check an uncertain model or compatibility message rather than changing wallet secrets or firmware editions. |
| Trying to connect from a non-whitelisted origin | Stop on that page and check the exact official URL. If the warning appears again at the verified official legacy route, contact Support; do not bypass the origin check. |
If you intentionally use BitBoxBridge
This check applies only to a connection method that actually uses BitBoxBridge; it is not a prerequisite for the direct Chrome procedure.
-
Check the local bridge status. In a new browser tab, open
http://127.0.0.1:8178/. This is a local address on your own computer. If a bridge status page appears, the bridge is reachable; it does not prove that the device is available or that MEW can complete access. - Interpret the result. If the page appears, apply the competing-connection and device-detection checks above. If it does not load, record that result and the bridge error for Support. Do not begin reinstalling software or disabling protection layers solely because this page is unavailable.
Confirm the result or contact Support
The connection is resolved when MEW opens the dashboard for the intended account and network without bypassing a trust warning. You do not need to send or receive funds to test the connection.
If it still fails, contact BitBox Support with the failed stage, exact error without confidential information, operating system, Chrome version, BitBox model or edition, firmware version if known, and the result of the app-detection test if performed. Include bridge details only if that method was used. Never send recovery words, passwords, passphrases, private keys, wallet backups, or authentication codes.