USB-Connection issues: My BitBox02 is not detected?

    If the BitBoxApp on your computer does not detect your BitBox, please try the following:

    1. Ensure that you have removed the screen protection sticker.
    2. Ensure the BitBox02 is plugged in with the display pointing upwards. (The logo sticks out on that side).
    3. Plug your BitBox02 in without an adapter or cable if possible.
    4. Try using a different USB port.
    5. Try using a different computer, or an Android phone.
    6. When using the extension cable: Make sure the logo on the cable is on the same side as the BitBox02 display.

    To check if your computer detects the BitBox at all:

    Mac

    1. Plug in the BitBox02 and tap on the side to choose the display orientation and connect the device.
    2. run ioreg -p IOUSB -l -w 0 | grep "Bit" in Terminal.
    3. You should see an entry containing “BitBox”.

    Windows

    1. Plug in the BitBox02 and tap on the side to choose the display orientation and connect the device.
    2. Open “Device Manager”.
    3. Go to “Universal Serial Bus”.
    4. Look for “USB composite device” (there could be multiple).
    5. For each of the “USB composite devices”:
      1. right-click and select “Properties”.
      2. in the dropdown select “Hardware Ids”.
      3. if the ID contains “VID_03EB” and “PID_2403” it is a BitBox.

    Linux

    1. Plug in the BitBox02 and tap on the side to choose the display orientation and connect the device.
    2. Run lsusb in the command line.
    3. You should see an entry containing “BitBox”.

    If the device is not detected by the app, you may need to manually adjust USB permissions. To do this for most recent distributions, copy and execute the following commands in a terminal (sudo permissions required):

    printf "SUBSYSTEM==\"usb\", TAG+=\"uaccess\", TAG+=\"udev-acl\", SYMLINK+=\"bitbox02_%%n\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\"\n" | sudo tee /etc/udev/rules.d/53-hid-bitbox02.rules > /dev/null && printf "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\", TAG+=\"uaccess\", TAG+=\"udev-acl\", SYMLINK+=\"bitbox02_%%n\"\n" | sudo tee /etc/udev/rules.d/54-hid-bitbox02.rules > /dev/null
printf "SUBSYSTEM==\"usb\", TAG+=\"uaccess\", TAG+=\"udev-acl\", SYMLINK+=\"dbb%%n\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2402\"\n" | sudo tee /etc/udev/rules.d/51-hid-digitalbitbox.rules > /dev/null && printf "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2402\", TAG+=\"uaccess\", TAG+=\"udev-acl\", SYMLINK+=\"dbbf%%n\"\n" | sudo tee /etc/udev/rules.d/52-hid-digitalbitbox.rules > /dev/null

    Run the following commands and then replug your device:

    sudo udevadm control --reload 
sudo udevadm trigger

    Alternatively, you can download this script from our GitHub repository (containing the same commands) and execute it instead.

    If the above does not work for your distribution, add your user to the "plugdev" group. If you're not already a member, a reboot may be required on some distributions.

    Copy and exute the following commands in a terminal (sudo permissions required):

    printf "SUBSYSTEM==\"usb\", SYMLINK+=\"bitbox02_%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\"\n" | sudo tee /etc/udev/rules.d/53-hid-bitbox02.rules > /dev/null && printf "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", SYMLINK+=\"bitbox02_%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\"\n" | sudo tee /etc/udev/rules.d/54-hid-bitbox02.rules > /dev/null
printf "SUBSYSTEM==\"usb\", SYMLINK+=\"dbb%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2402\"\n" | sudo tee /etc/udev/rules.d/51-hid-digitalbitbox.rules > /dev/null && printf "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", SYMLINK+=\"dbbf%%n\", GROUP=\"plugdev\", MODE=\"0664\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2402\"\n" | sudo tee /etc/udev/rules.d/52-hid-digitalbitbox.rules > /dev/null

    Run the following commands and then replug your device:

    sudo udevadm control --reload 
sudo udevadm trigger

    Note: On some distributions, the plugdev group might not exist yet. If you're still facing issues, try to create the group first and add your user to it. Proceed with the steps from above again.

    Published