• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE] Enable ADB USB Drivers And Fastboot For Tegra Devices(windows, linux and mac)

Search This thread

Jon2555

Senior Member
Jan 17, 2011
789
242
Belgrade
1. Linux(easy)

2. Mac(easy)

3. Windows(medium):D

________________________________________________________


1. Linux

You don't need any special drivers for SDK on linux(adb shell), but you don't get fastboot binary in SDK package. To set fastboot for linux follow instructions:

1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot linux binary
http://www.mediafire.com/?ldlovlzi9mx3pbh
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
if you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it?
Copy this file to /etc/udev/rules.d
EDIT:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Easy?;)
______________________________________________________________

2. Mac

I don't have Mac, but it should be like for linux:

1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot Mac binary:
http://www.mediafire.com/?kjozh1q5dyyqhn3
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
(I don't know that this is possible on Mac, try to change nautilus with Mac's default file browser?)If you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it? Easy?:p
______________________________________________________________

3. Windows

1. Download SDK
http://developer.android.com/sdk/index.html
2. Download Google USB Drivers from SDK Manager
3. After download, there're located in /path_to_your_SDK_directory/extras/google/usb_driver
4. Open android_winusb.inf and add this after [Google.NTx86] or [Google.NTamd64](32 bit or 64bit)
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
(Here is my modificated android_winusb.inf file here, but it's old and an updated version arrived from Google and it's compatible with 32bit and 64bit)
5. Open CMD from Start>Run and type:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
6. Reboot
==========================================================
7. On tablet go to Settings > Applications > Development and enable USB Debugging if it wasn't enabled and connect tablet with computer via USB.
8. Right-click on Computer and click Manage. Identify your device from the list(I think it's Tegra with board icon), right-click it and click Update Driver Software
9. Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer
10. Choose to view all devices and click Have Disk
11. Browse to the google-usb_driver folder inside your Android SDK folder(/path_to_your_SDK_directory/extras/google/usb_driver) and select the android_winusb.inf file
12. If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing
13. Once the drivers have been installed, you should be able to use ADB with your device
14. To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB
For fastboot you need to go to /path_to_your_SDK_directory/platform-tools in terminal(cd /path_to_your_SDK_directory/platform-tools) and type fastboot(.exe) <action> and before it to change ADB Interface to ADB

That's it, if you have some complaints, post them.
Bye!!!

EDIT: Changed android_winusb.inf file due error in it.
EDIT2:Changed android_winusb.inf file due error in it again.:D
 
Last edited:

mauri90

Senior Member
Jun 19, 2011
65
36
Bari
Hello guys I have a problem, the step 5. Open CMD from Start> Run and type:
echo 0x955>> "% USERPROFILE% \. Android \ adb_usb.ini"
I run this step but I open a txt file that says this:
Android # USB Vendor ID 3RD PARTY LIST - DO NOT EDIT.
# USE 'adb Android update' TO GENERATE.
USB Vendor ID # 1 FOR LINE.
0x955

I now do not understand where I write echo 0x955?
 

mblaster

Inactive Recognized Developer
Aug 2, 2007
433
95
Nice guide. Think you forgot the udev rule for Linux:
Create a file called /etc/udev/rules.d/51-android.rules containing:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
Without that Linux won't give you write permission to the device.
 

brunte

Senior Member
Aug 19, 2009
76
6
So when I want to use fastboot, I install the Android Bootloader Interface driver? Not the ADB interface driver?
Needless to say I haven't got fastboot working yet but ADB works. One other thing: If I manage to install a firmware and do a wipe and everything works; can it be that I would experiance better performance if I as well managed to to a full wipe with fastboot? I mean, can it flush things that CWM can't? I'm using the latest cyanogenmod (test version) from DerArtem, but I am a bit interested in trying the latest progress of honeycomb...
 

Jon2555

Senior Member
Jan 17, 2011
789
242
Belgrade
I have problems with interfaces. On one computer is ADB interface and on other is something else but I prefer linux for doing any job that's connected with android. In theory wiping should be same with fastboot and recovery but, again, I prefer fastboot because it's JUST erase all on data/cache/system partition and recovery might don't have support for other partition types as well as other problems, but I don't say that it can be different.
 

brunte

Senior Member
Aug 19, 2009
76
6
Thanks. I hope I continue to have a functioning cwm. If it breaks I will have to install Linux :)
 

ozieee

Member
Nov 30, 2011
7
0
When the tablet is open in USB Debugging mode I can see my device adb devices list but when ı restart my tablet fastboot mode ı can't find :confused::confused::confused:
 

Jon2555

Senior Member
Jan 17, 2011
789
242
Belgrade
The best slow to install Linux via VM. It complicated on windows, it's different from computer to computer.

Sent from my IDEOS S7 Slim using XDA App
 

joevik

Senior Member
Nov 14, 2009
289
22
do i type this exactly with all the " ???

echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"

????????????????/

HELP PLEASE
 

joevik

Senior Member
Nov 14, 2009
289
22
When i tipe the echo 0x955 line

It keeps on saying that system cannot find the path specified

can someone please help?

even when i open comand prompt and type adb it says adb is not recognised as an internal or external.........
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    1. Linux(easy)

    2. Mac(easy)

    3. Windows(medium):D

    ________________________________________________________


    1. Linux

    You don't need any special drivers for SDK on linux(adb shell), but you don't get fastboot binary in SDK package. To set fastboot for linux follow instructions:

    1. Download SDK(this isn't need if you want just fastboot)
    http://developer.android.com/sdk/index.html
    2. Download fastboot linux binary
    http://www.mediafire.com/?ldlovlzi9mx3pbh
    3. Copy it to your SDK directory
    /path_to_your_SDK_directory/platform-tools
    or
    if you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
    1. Open Terminal and type:
    sudo nautilus
    to get file browser with root privileges.
    2. Copy fastboot binary to /bin directory
    Now, just open terminal and type fastboot <action> and that's it?
    Copy this file to /etc/udev/rules.d
    EDIT:
    Code:
    sudo chmod a+r /etc/udev/rules.d/51-android.rules
    Easy?;)
    ______________________________________________________________

    2. Mac

    I don't have Mac, but it should be like for linux:

    1. Download SDK(this isn't need if you want just fastboot)
    http://developer.android.com/sdk/index.html
    2. Download fastboot Mac binary:
    http://www.mediafire.com/?kjozh1q5dyyqhn3
    3. Copy it to your SDK directory
    /path_to_your_SDK_directory/platform-tools
    or
    (I don't know that this is possible on Mac, try to change nautilus with Mac's default file browser?)If you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
    1. Open Terminal and type:
    sudo nautilus
    to get file browser with root privileges.
    2. Copy fastboot binary to /bin directory
    Now, just open terminal and type fastboot <action> and that's it? Easy?:p
    ______________________________________________________________

    3. Windows

    1. Download SDK
    http://developer.android.com/sdk/index.html
    2. Download Google USB Drivers from SDK Manager
    3. After download, there're located in /path_to_your_SDK_directory/extras/google/usb_driver
    4. Open android_winusb.inf and add this after [Google.NTx86] or [Google.NTamd64](32 bit or 64bit)
    ;NVIDIA Tegra
    %SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
    %CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
    (Here is my modificated android_winusb.inf file here, but it's old and an updated version arrived from Google and it's compatible with 32bit and 64bit)
    5. Open CMD from Start>Run and type:
    echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
    6. Reboot
    ==========================================================
    7. On tablet go to Settings > Applications > Development and enable USB Debugging if it wasn't enabled and connect tablet with computer via USB.
    8. Right-click on Computer and click Manage. Identify your device from the list(I think it's Tegra with board icon), right-click it and click Update Driver Software
    9. Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer
    10. Choose to view all devices and click Have Disk
    11. Browse to the google-usb_driver folder inside your Android SDK folder(/path_to_your_SDK_directory/extras/google/usb_driver) and select the android_winusb.inf file
    12. If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing
    13. Once the drivers have been installed, you should be able to use ADB with your device
    14. To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
    adb kill-server
    adb start-server
    adb devices
    If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB
    For fastboot you need to go to /path_to_your_SDK_directory/platform-tools in terminal(cd /path_to_your_SDK_directory/platform-tools) and type fastboot(.exe) <action> and before it to change ADB Interface to ADB

    That's it, if you have some complaints, post them.
    Bye!!!

    EDIT: Changed android_winusb.inf file due error in it.
    EDIT2:Changed android_winusb.inf file due error in it again.:D
    2
    I'll try because I'm not at home, I went to my grand parents and I have really slow internet.
    1
    echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"

    shut the cmd say something ? because when i write the command and push enter its just jump to another line and says nothing ???
    1
    No. You can go to that file("%USERPROFILE%\.android\adb_usb.ini") and manualy add 0x955 to it.
    1
    /documents_and_settings/[your user name]/.Android(hidden file)/adb_usb.ini

    Sent from my Xoom using Tapatalk