学步园

http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/

Update: 07/29/13
– In step 4, Android 4.2.x and up has Developer Options hidden. Added steps to make it visible
Update: 05/27/13
– Updated platform-tools (ADB) to latest version (Revision 17)
Update: 02/04/11
– HTC changed its Vendor ID, older phones have different ID than newer phones. Refer to USB Vendor IDs table
at the bottom of this tutorial to see the change.
Update: 01/02/11
– By mistake I had linked the ADB tool for OSX in step 3.1. Now it should be the correct one for Linux.
IMPORTANT
Update 12/11/10 – There has been a change to the new Android SDK. ADB Tool has been moved to /android-sdk-linux_x86/plataform-tools, so if you have the old SDK, please download the new one and update your path (Step 9.2 of this tutorial). If
this is your first time doing this, then disregard the update and continue with the tutorial.
Update: 09/21/10
– Working code with Ubuntu Lucid Lynx and added more USB vendor IDs.

1. Download the latest Android SDK from Google: Android
   SDK
2. Extract the TGZ file to your home/YOUR-USERNAME directory
3. To get ADB, you need to install the SDK: Installing
   the SDK
   • If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and proceed with the tutorial: ADB
4. On your phone, click Settings > Applications > Development and make sure USB Debugging
   is on.
   • In Android 4.2.x and up Developer Options is hidden, to make it visible, do the
     following
   • Tap seven times in Build Number: Settings
     > About Phone > Build Number
   • You will get a message saying you have enabled Developer Options or something like
     that, go back to Settings and you will see Developer
     Options in there.
5. Login as root and create this file: /etc/udev/rules.d/##-android.rules
   NOTE: In the above file replace ## with the number 50 if you are running Gusty/Hardy/Dapper (50-android.rules)
   or with the number 70 if you are running Karmic Koala/Lucid Lynx/Maverick Meerkat(70-android.rules)
   • Or simply type in terminal sudo gedit /etc/udev/rules.d/##-android.rules then enter
     your password
6. The file should read:
   • For Gusty/Hardy: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
   • For Dapper: SUBSYSTEM==”usb_device”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
   • For Karmic Koala: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
   • For Lucid Lynx: SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
   • For Maverick Meerkat: SUBSYSTEM==”usb”, ATTR{idVendor}==”0bb4″, MODE=”0666″

   NOTE: In the above lines the code ”0bb4″ refers to a HTC device. If your phone is from a different manufacturer,
   replace the code with the appropriate from the table below.
   NOTE: If you copy one of the lines mentioned above, make sure you replace the quotation marks with the ones in
   your keyboard, as these have different display code and it might give you a “no permissions” error.

7. Execute: sudo chmod a+rx /etc/udev/rules.d/70-android.rules
8. Reboot
9. To run ADB you need to add an environment variable to your bashrc file:
   • Open a terminal window and type: sudo gedit .bashrc
   • Add the following line at the end: export PATH=${PATH}:/home/YOUR-USERNAME/android-sdk-linux_x86/platform-tools
   • Save and close
10. You should be ready to go, type adb devices in a terminal window with your phone
    plugged in.
    If you see a serial number pop up that means you are done. Should look something like this:
    List of devices attached
    HT99PHF02521 device
11. If for some reasons when running adb devices gives you a “no permissions” error,
    try typing the following in terminal
    • db kill-server
    • adb start-server

USB Vendor IDs

Common ADB Commands

- Lists which devices are currently attached to your computer

- Drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly

- Lets you install an Android application on your phone

- Remounts your system in write mode – this lets you alter system files on your phone using ADB

- Rets you upload files to your phones filesystem

- Lets you download files off your phones filesystem

- Starts dumping debugging information from your handset to the console – useful for debugging your apps

Copyright © 2013-2018 学步园  保留所有权利.
软文销售 QQ客服：2265327166 （其他合作也可洽谈）

必威体育

必威电竞