Configuring and Using Android Debug Bridge (ADB) with Elo M51 and M51C Mobile Computers

This guide explains how to configure and use Android Debug Bridge (ADB) with Elo M51 and M51C Mobile Computers from Elo — Now part of Zebra Technologies.

Android Debug Bridge (ADB) is a versatile command-line utility included with Google's Android SDK Platform-Tools. ADB establishes communication with your mobile computer over Wi-Fi/Ethernet or a direct USB connection to facilitate application deployment, debugging, file transfers, and shell diagnostics.

Step 1: Set Up ADB on the Host Computer

1. Download the latest Android SDK Platform-Tools package directly from the official Android Developers Website.
2. Extract the downloaded ZIP file to an easily accessible folder on your local system (for example, C:\platform-tools).

Step 2: Enable Developer Options and USB Debugging

1. On the Elo Mobile Computer, open ⚙️ Settings.
2. Navigate to ⚙️ Settings > About Device and locate Build Number.
3. Tap Build Number seven (7) consecutive times until a pop-up confirmation confirms that Developer Mode is enabled.
4. Return to ⚙️ Settings.
5. Select System > Developer Options.
6. Locate the USB debugging toggle and switch it to ON.
7. Select OK when prompted with the "Allow USB debugging?" dialog.

Step 3 (Option A): Connect Over Wi-Fi or Ethernet

The Elo Mobile Computer and host computer must be able to communicate over the same network.

1. Ensure the Elo Mobile Computer is connected to the network.
2. On the Elo Mobile Computer, go to ⚙️ Settings > Network & Internet > WLAN (or Wi-Fi).
3. Select the active network connection.
4. Select Advanced and locate the IP Address.
5. Make note of the IP address assigned to the Elo Mobile Computer.
6. On your host computer, open Windows Command Prompt or Windows Terminal and navigate to your platform-tools directory.

7. Execute the following command, replacing <IP-address> with the device's actual IP address:

   adb connect <IP-address>

   Example:

   adb connect 192.168.1.100

8. Enter the following command to verify the connection:

   adb devices

If the M51/M51C is listed with a status of device, the wireless ADB connection has been successfully established.

Step 3 (Option B): Connect via USB Cable

1. Make sure the USB cable is not connected to the Elo Mobile Computer.
2. Open ⚙️ Settings and select System > Developer Options.
3. Make sure USB debugging is enabled.
4. Connect the USB Type-C end of the cable to the M51/M51C and the USB Type-A end to the host computer.

5. On the host computer, open Windows Command Prompt or Windows Terminal and navigate to the extracted platform-tools folder.

6. Enter the following command:

   adb devices
7. If prompted on the Elo Mobile Computer to allow USB debugging, select Allow or OK.
8. If available, select Always allow from this computer to authorize the host computer for future connections.

9. Enter the command again:

   adb devices
10. Verify that the M51/M51C serial number appears in the device list with a status of device.

If the device is listed, the USB ADB connection has been successfully established and the M51/M51C is ready to accept ADB commands.

Troubleshooting USB ADB Connections

If the M51/M51C does not appear when running adb devices, try the following steps:

1. Disconnect the USB cable from the M51/M51C.
2. Go to ⚙️ Settings > System > Developer Options.
3. Verify that USB debugging is enabled.
4. If available, select Revoke USB debugging authorizations and confirm the selection.
5. Disable and then re-enable USB debugging.

6. On the host computer, enter the following commands:

   adb kill-server
   adb start-server
7. Reconnect the USB cable to the M51/M51C.
8. If prompted on the Mobile Computer, authorize the host computer for USB debugging.

9. Enter:

   adb devices
10. Verify that the M51/M51C appears with a status of device.

If the device still does not appear, verify that the USB cable supports data transfer and try a different USB port or USB cable.

Additional Information

For additional information about Android Debug Bridge, see Android Debug Bridge (ADB) - Android Developers.