Issues related to the use of Windows under ADB

Issues related to the use of Windows under ADB

Applicable environment:

In Windows XP. WIN7 can be done under this article. No experiments were carried out under WIN8. But the operation settings are roughly the same. Except for the 4th step. The location of the Adb_usb.ini may vary, and the other sections can be operated as described in the article.

Description: Please be aware of permissions issues when installing drivers under WIN7,WIN8. Please agree to install the driver during installation. Otherwise, the driver may fail to install.

The following issues should be noted for normal use of ADB under Windows:

1. Mobile phone to open debug mode

In Settings, open the developer options and turn on the USB debugging options

2. PC-mounted device driver

USB drives may vary for each device. Take Spreadtrum as an example.

Disconnect the device from the PC before installing the drive.

Spreadtrum USB drive androidsci-android-usb-driver-jungo-v4.zip, after decompression there is a specific driver installation instructions, distinguish between the first or The system, according to different systems to choose their own suitable driver. For installation.

Mobile device side at the same time will have such as the following tips,

after the program is installed, USB linked devices;

PC The end will prompt to find new hardware. The driver is being installed. Wait for PC -side installation to drive successfully.

then, in Device Manager, there will be a new Android Phone

The following figures are drivers for the status of the Device Manager after the normal installation

Viewing device properties

You can view your device here VID Information

3. change adb_usb.ini

End the ADB process in Task Manager, or run ADB kill-server in the command line form. Make the following changes to exclude the possible effects.

Locate or create a new Adb_usb.ini file under the folder that the emulator holds < for example: C:\Documents and settings\administrator\.android>. At the same time add or write the above device 0xVID (vid is the above vid_ followed by the number, such as: 0x1782 (Spreadtrum USB device vid)

4. Restart the ADB service

Assuming that the ADB command tool path has been added to the environment variables of the system, you can do the following directly in the Open command line form, assuming that the ADB command tool path is not joined to the system's environment variable, and after opening the command line form, you can switch to the Platform-tools folder of the folder where ADK is located. (ADK the folder where the ADB command tool is located).

Then run ADB devices in the command line form

So far. ADB on the line normal link on the device

5. ADB frequently uses commands

Adbkill-server #停止adb服务进程

Adbstart-server #打开adb Service Process

Adbdevices #显示链接到的设备

Adbshell #进入设备的shell模式

Adbversion #查看adb版本号

6. Frequently asked questions

The common problem is that the device cannot be found. Detailed phenomena such as the following

C:\USERS\CC>ADB deviceslist of Devices attachedc:\users\cc>adb devices* daemon not running. Starting it now on port 5037 * * Daemon started successfully *list of devices attached

There may be many reasons why the device could not be found, except that the phone device side debug item is not open. Other reasons are almost all PC -side environment configuration problems caused by, in general, such as the following ideas to go through the experiment until resolved.

-------------------------------------------------

confirm this document individually 1~4 These four operations are complete .

Under normal circumstances, these four steps are complete. The device can be connected, assuming that there is no link, in principle please continue to perform such as the following check and Operation

1. Turn off Some mobile phone software on your PC (similar to pea pods, phone assistants, etc.)

2. Close some adb in the process . It is possible that other names, such as tadb, encapsulate the process of ADB functionality.

3. guaranteed to have only one android device

4. Disconnect the device and restart the ADB service

5. USB connection device, you can find the device

If you can't find your device yet, you can restart your computer. Check the above steps again.

----------------------------------

Welcome to browse and technical ExchangePlease respect the fruits of labor Reprint Please indicate the source, thank you!

http://blog.csdn.net/netwalk/article/details/38069383

Issues related to the use of Windows under ADB