What do you need help with?

Configuring Android adb, fastboot, and Flashing Images to the R-7


This is an excerpt from this reference:

Taken from section 3.1 & 3.2.  Turns out that this is the same procedure needed for supporting the Snapdragon 805, which is the CPU in the R-7.


Install Android adb, fastboot, and USB driver for Windows:

R-7 requires the following USB device support:

  • Android USB Driver (android_winusb.inf)
  • Android adb Interface
  • Android Boot Loader Interface (fastboot)

1. Before installing the drivers, edit the qcmdm.inf and qcser.inf files to make sure that they contain support for the R-7 (Qualcomm SURF/FFA) with appropriate entries in each section, as indicated in Step 4.

2. Go to http://developer.android.com/sdk/win-usb.html, and follow the instructions to install the SDK and USB driver.

3. Right-click My Computer, and select Properties > Advanced > Environment Variables, and set the path to include the directory c:\android-sdk-windows\tools.

4. The Android USB driver for adb and fastboot needs to add the R-7 VID/PID, which supports the connection to it. Edit this file to add the DragonBoard 410c VID/PID lines to each section: android-sdk-windows\usb_driver\android_winusb.inf.



;Qualcomm SURF/FFA

%SingleAdbInterface% = USB_Install, USB\VID_05C6&PID_9025

%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9025&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D


;Qualcomm SURF/FFA

%SingleAdbInterface% = USB_Install, USB\VID_05C6&PID_9025

%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9025&MI_01

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D

In addition, make sure that there are matching entries under the [Strings] section.


SingleAdbInterface = “Android ADB Interface”

CompositeAdbInterface = “Android Composite ADB Interface”

SingleBootLoaderInterface = “Android Bootloader Interface”

5. The adb client (adb.exe) supports a built-in list of recognized USB VID/PID devices. To add another device to the list of recognized devices, which is not included in the built-in support list, create this directory if it does not exist: %USERPROFILE%\.android.

6. Navigate to the %USERPROFILE%\.android directory.

7. In the directory %USERPROFILE%\.android, create the file /edit the adb_usb.ini. If the file exists, it contains a DO NOT EDIT message. Disregard this message and edit the file anyway. Add a line to the end of the file containing 0x05C6.

NOTE: Do not run android update adb or it resets the contents of this file and overwrites the line just added.

After editing, the adb_usb.ini file must look like the following:


# USE ‘android update adb’ TO GENERATE.




Configure adb and fastboot in Linux

1. To configure adb, modify the USB driver by navigating to the following directory:

cd /etc/udev/rules.d/

2. Enter the command:

sudo vi 50-android.rules

The result must be similar to the following output:

#Sooner low-level bootloader

SUBSYSTEM==”usb”, SYSFS{idVendor}==”18d1”, SYSFS{idProduct}==”d00d”, MODE=”0664”, GROUP=”plugdev”

# adb composite interface device 9025

SUBSYSTEM==”usb”, SYSFS{idVendor}==”05C6”, SYSFS{idProduct}==”9025”, MODE=”0664”, GROUP=”plugdev”

3. After editing the file, to see the list of target devices connected to the Linux box, type:


4. After a build is complete, the adb and fastboot executables for Linux are located in the android\out\host\linux-x86\bin directory in the Android software release. If the android\out\host\linux-x86\bin directory is not in the executable search path, use the following steps to add it from $BUILDROOT (build directory).

a. Type the command:

source build/envsetup.sh

b. Type the command:

lunch msm8916_64-userdebug

Note: To run adb or fastboot, pseudo or root access on the Linux machine may be required. This is a useful link for Linux and MAC OS to setup adb and fastboot (note that device ID “9025” is needed in 50-android.rules or 51-android.rules) : https://code.google.com/p/adb-fastboot-install/

Have more questions? Submit a request


Powered by Zendesk