Enable ADB USB Drivers for Nvidia Tegra based Android Tablets

Nvidia TegraThis is a quick hack that enables ADB access and installs USB drivers for NVIDIA Tegra and Tega 2 based Android Tablet devices including Notion Ink Adam Tablet, Advent Vega, Toshiba Folio 100, Toshiba AC100 smartbook, Viewsonic G Tablet and more. For the detailed guide, read on after the break.

If you have tried connecting to your Android tablet from your computer via USB and using tools provided by the Android SDK, you must have noticed that the USB drivers available through the SDK do not support most of these tablet devices.

Fortunately, this can be fixed by simply adding a few lines of text to the driver file and issuing a command. Once you have enabled these drivers, you can use access your device via the SDK tools such as ADB and root it as well using methods that require ADB.

Here are the steps that you need to follow in order to enable these drivers:


  1. You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
  2. Open the google-usb_driver folder that you will find inside your Android SDK folder.
  3. Open the android_winusb.inf file in notepad or any text editor to edit it.
  4. Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
    ;NVIDIA Tegra
    %SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
    %CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01

    Don’t edit or replace any other text that is already there; just add these new lines and save the file.

  5. Open a command prompt window and enter this command:
    echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"

Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:

  1. On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
  2. Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
  3. Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
  4. Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
  5. Choose to view all devices and click ‘Have Disk…’.
  6. Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
  7. If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
  8. Once the drivers have been installed, you should be able to use ADB with your device.
  9. 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.

Although these instructions were originally written for Toshiba AC100, they should work for any Nviaid Tegra or Tegra 2 based Android device.

[via Hacking the Toshiba]

Advertisement
  • Pingback: How To Root Toshiba Folio 100 Android Tablet

  • Pingback: Install FolioMod Custom Android ROM on Toshiba Folio 100 Tablet

  • Pingback: Install Notion Ink Adam ROM on Toshiba Folio 100

  • Pingback: Install Android 3.0 Honeycomb and Market on Nook Color

  • Joe_flash

    One minor (maybe) error.. that string in the adb_usb.ini file should be 0×2080, not 0×9055. Works with 2080, not 9055.

  • Dan

    “The specified location does not contain information about your device.” is the prompt that i get when i try to install the drivers after step 6 from the above. I’ve had honeycomb for 2 weeks and cant figure out how to get the ADB to work so I can download the android market. I would really appreciate some help. I’ve spent hours trying to figure this out on my own. Thank you

  • Joshua

    I found that the lines:
    ;NVIDIA Tegra
    %SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
    %CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01

    were not correct for my Color Nook. If you right-click and select Properties -> Details you should see the Device Instance Id. Change the USB\VID_#### to match what you see in the Device Instance Id (2080 as the previous post mentioned) and the &PID_#### to what you see in the Device Instance Id (0002 in my case). With those changes and 0×2080 in the adb_usb.ini file, it worked for me. Good luck!

    My Corrected Lines:

    ;NVIDIA Tegra
    %SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
    %CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01

    • daniele

      Great!!!
      That was the real solution.

      I also replaced
      echo 0×955 >> “%USERPROFILE%\.android\adb_usb.ini”
      with
      echo 0×2080 > “%USERPROFILE%\.android\adb_usb.ini” (single > to rewrite the previous text).

      And now perfectly works.
      Great.

  • Rockstar

    Whenever i try to save the edited notepad file, it asks if i want to replace
    ,i say yes then when i click save it says access denied???

    • MarttiM

      I need help,

      I am trying to update the driver (in device manager)
      android_winusb – as a driver file

      , but everytime that i do it, it says that the folder you specified doesnt contain a compatible software driver for your device. If the folder contain a driver, make sure it is designed to work with Windows for x64-based systems.

      Thanks for a help,

      • kkarr

        I have a similar problem, but for x32 based system. Any suggestions?

        • Piti

          Same here….
          Anyone found out how to solve this problem?

          • Dan

            I did. My “Hardware IDs” are USB\VID_0930&PID_7100 for a Toshiba Thrive.
            So, initially we had this in the .inf and the echo:
            ;NVIDIA Tegra
            %SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
            %CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
            &
            echo 0×0955 > “%USERPROFILE%\.android\adb_usb.ini”

            Which was giving me the “make sure it is designed to work with Windows for x64-based systems” error. So I changed mine to read…

            ;NVIDIA Tegra
            %SingleAdbInterface% = USB_Install, USB\VID_0930&PID_7100
            %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_7100&MI_01
            &
            echo 0×0930 > “%USERPROFILE%\.android\adb_usb.ini”

            And then when I went back to device manager and selected the driver again it allowed it (it wasnt happy about it but it worked and now I have adb) :P

            • HMishkoff

              Dan, you saved my life. I have a Thrive, and I’ve been trying to create an app for it with PhoneGap, which requires a USB connection from my development machine. I’ve been going nuts trying to make that connection ever since I bought the Thrive a few weeks ago, and I was starting to think that I might NEVER be able to get it to work until I ran into your note. I can’t thank you enough.

              I should point out that I had to make a slight modification to your procedure, my Hardware ID strings were slightly different from yours. For the benefit of anyone reading this who’s even more hardware-challenged than I, you find them as follows (this works on Windows 7, and it’s probably nearly identical on XP):

              1) Click Start.
              2) Right click Computer.
              3) Click Properties.
              4) Click Device Manager.
              5) Right click on the device.
              6) Click Properties.
              7) Click the Details tab.
              8) Select Hardware ID’s under Property.
              9) Right click each Value in turn, then click Copy.
              10) Paste each value into its respective place in the procedure.

              Thanks again, Dan, I can’t tell you how much I appreciate you taking the time to post your note.

              • Dave Maclean

                A HUGE thank you to Dan. I started panicking when I first tried to connect my Thrive to my XP box and it gave me the MTP and AT100 driver errors. I did exactly as Dan suggested and it worked perfectly for me. I have a question for HMishkoff though. You say to refer to the Hardware IDs under the device details. I got two lines, and they weren’t exactly what Dan showed, nor what I used. You say to paste each value into its respective place. Does that mean the first value listed goes in as %SingleAdbInterface% and the second as %CompositeAdbInterface% ? My interface appears to be working just fine, but if it could be better I’d like to make it so. Would you clarify please?

                • HMishkoff

                  Dave, if it’s working, I’d leave it alone, but… It’s been a while, so I don’t remember which was which, but as I recall I pasted the longer Hardware ID into the %CompositeAdbInterface% line in Dan’s code (because it’s longer), and I pasted the shorter Hardware ID into the %SingleAdbInterface% line in Dan’s code (because it’s shorter). Not especially scientific, but it worked for me. But as i said, if you got it working, I think you’d be nuts to mess with it.

              • jameadows

                Thanks all, this got my setup working.  Wanted to point out one more thing that wasn’t obvious to me.  When you look at the hardware IDs in device manager they will be different with debugging mode turned on and off.  Originally I got the values with debugging turned off and it didn’t work, the values with debugging turned on did.

    • Aaron41971

      try safemode, then edit the file, just press f8 before to goto windows

    • Joe Schmoe

      You can change the permissions by right clicking the file (adb_usb.ini), and make sure that you have write permissions. 

  • mr_brown

    i cant see any changes in my device manager (adb interface) but it is in storage device when i connected my Folio via usb to computer? Is that the one that i should “update the driver” because when i did it, an error saying that the driver is incompatible with x64 base system? I’m using x86 on my laptop? how to solve this.. help me please…

  • JS

    I have been able to get the driver installed successfully, but I am having trouble with the device being recognized by ADB. After I type in “adb devices” the lines below are blank. When I open the device manager, the device is listed in the “Android Phone” folder and the device is named “Android Composite ADB Interface”.

    Please help!!!

    • TerryC

      I’ve got exactly the same problem. The device is just not seen.

      • Cameron

        I had the same problem, try this method.

        1. When windows picks up the device as a Portable Device – AT100, update the driver and select USB Composite Device.
        2. Once this is done, there should be an AT100 device in ‘Other Devices’, update the driver on that, but just browse to the google/usb_driver folder and let windows figure it out. It should find the driver itself as an ‘Android Composite ADB Interface’

        After this was done, ADB could see the device.

  • KJ

    I’ve got the same problem as the last two guys. A blank space when I type adb devices. I even updated my .ini file tot he 2080 and 0002 but still no luck. Any ideas or help would be greatly appreciated.

  • Coco

    Dan’s values works on my Toshiba Thrive and Windows XP. Thanks again.

    ;NVIDIA Tegra
    %SingleAdbInterface% = USB_Install, USB\VID_0930&PID_7100
    %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_7100&MI_01
    &
    echo 0×0930 > “%USERPROFILE%\.android\adb_usb.ini”

  • Nathani

    Thanks a lot for this post. Worked like a charm. I can’t wait until development for these tablets are really, expressly, and by the manufacturers, supported.

  • DropBear9

    Worked a treat on my Toshy AT100 (Oz version) exactly as per instructions above :-)
    Thank you very much!

  • shao
  • themaster

    That worked! :) but I had to do an extra step, I run USB deview and uninstalled envidia tegra driver, then I plugged again the device, it automatically installed the driver again and BAM it showed up

  • Shiraz Qayyum

    Is there a way to work it for mac osx?  I am trying to connect to elocity A7 040 android device

  • Joe Schmoe

    Thanks YOU ALL SOOOOOOO MUCH.  I bought my tablet specifically FOR ANDROID development and using it was a side note.  I was thinking I was going to have to return my Toshiba Thrive and buy a Galaxy, but THANKS!!!!!

  • Joe Schmoe

    ;Toshiba Thrive
    %SingleAdbInterface% = USB_Install, USBVID_0930&PID_7100&REV_9999&MI_01
    %CompositeAdbInterface% = USB_Install, USBVID_0930&PID_7100
    &MI_01Was my final edit of android_winusb.ini. So it looks like you just need to type whatever in “Properties->Details” on the device.

  • Anonymous

    I have problems in step 6 above in Updating  Driver software.

    I was trying to install Android Market in a Nook Color running  Honeycomb on a microSD, I have installed Android SDK, set up the Path variables, when I tried to install the ADB usb driver, the first
    part worked, for the second part, I managed to complete step 1-5, somehow the system could not locate the driver software.

    I got an error message: Window was unable to install your Nook color, Window could not find the driver software for your device.

    I checked again for android_winusb.inf, the file is under the above directory of
    C:android-sdk-windowsextrasgoogleusb_driver

    Wonder why the Updating driver software failed ?

    Anyone can help?

    Thanks

  • Anonymous

    Dan,

    Thank you so much!!!!

  • Guest

    everything worked fine 

  • Guest

    everything worked fine for me, except that under “list of devices attached” in the cmd, it didn’t show my nook color, it was just blank

    (don’t mind the post below, I didn’t mean to post that)

  • Boimans

    Hi, this worked on my Toshiba AT200 as well using
    USBVID_0930&PID_0960&REV_0216&MI_01USBVID_0930&PID_0960&MI_01
    and echo 0930

    • Raysaun

      Does not work for me. Gets picked up ok as the ADB Interface device but does not show up in “adb devices” command

  • denis

    i cant install
    android_winusb.inf as a diver for my toshiba at100
    it writes ” there isn’t any data about device/s in chosen place
    what i have todo whis this ?!

  • Neeraj

    you saved my day… thanks a lot !!!

  • Neeraj

    you saved my day… thanks a lot !!!

    • Neeraj

      This is for AT100 toshiba on windows vista

  • Houssem

    Thank you very very much ! It works like a charm.

  • Mohammed Nassim

    you are princ

  • Ryan

    It keeps saying “Windows has found driver software for your device but encountered an error while trying to install it. The hash for the file is not present in the specified catalog file. the file is likely corrupt or the victim of tampering”

    • Ryan

      I have a Toshiba AT100