[DRIVER PACK] Easy USB ADB Installer for Windows (32/64 bit)

Search This thread
By:
Advanced…
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
Howdy everyone!

Without further ado, I humbly present my gift to the community (and the #nookcolor irc channel :) )

This collection of scripts will automagically install:
  • NookColor USB ADB Drivers
  • The necessary adb_usb.ini file for adb to recognize the NookColor
  • A stripped-down copy of the Android SDK, with just the requirements for adb.exe
  • adb.exe is added to your %PATH% variable.

Tested on Windows 7 32/64, Windows Vista 32, Windows XP SP2/SP3

Now I realize not everyone wants the do-all end-all script, so there's two versions: one that contains the drivers AND a cut down Android SDK, or the version that only installs the ADB driver and the proper adb_usb.ini file.

Instructions for use with combo pack (please read!):
  1. Download the combo pack
  2. With your NookColor unplugged from your PC, run the nookcolor-easyADB.exe file and allow it to extract to c:\
  3. Follow the on-screen instructions and wait until you see "All done!"
  4. Plug in your NookColor, tell Windows not to use Windows Update, and let it search your computer for the proper drivers.

Once the package has finished installing, and the drivers are installed, you can just open a command prompt window and type:
Code: 
adb devices
If you see your device's serial number listed, you're good to go!

Instructions for the driver-only pack:
  1. Download the driver-only pack
  2. Extract it somewhere on your PC (may I recommend c:\android-sdk-windows\usb_driver ?)
  3. Run install.exe in the extracted folder and follow the onscreen prompts.

For those of you that would like, the source of the driver installer is contained in both downloads as install.au3. Driver installation is accomplished using dpinst.exe from the Windows Driver Development Kit.

Also, to avoid any confusion, I am also known as IOMonster on IRC.

Okay now for the good stuff...

DOWNLOADS:

Update: 0.2 version has been released. Should fix CPU architecture errors when installing. I have also changed the download protection on my server, you should be able to use download managers now.. just keep it to a sane number of concurrent downloads by IP.

Troubleshooting:
  1. Make sure you're rooted
    Sounds dumb, but trust me, it's happened.
  2. Make sure you haven't used ADBWireless and forgotten to disable it
    Guilty here. I spent a good half hour trying to figure out why it didn't work on one of my Nooks until I realized that I had left ADBWireless on.
  3. Check device manager for a "Nook" device, you may just have to do an "update driver" on it
    Just like it says, check for any devices labeled "Nook" or "USB Composite Device" with a VID of 2080
  4. Uninstall ALL Nook-related devices in device manager
    Check device manager for any USB devices (usually USB Composite Device or USB Mass Storage) with a VID of 2080 and PID of 0002, uninstall 'em and unplug/replug your Nook.

Please note that this is a VERY initial build. It may not work for you under some circumstances, but on the few machines I've tried it on, it seemed to work for me. If you encounter any weird bugs, please let me know- I'd love to know so I can fix it.

(As a side note, I really need to standardize my nomenclature for my driver pack..)
 
Last edited:
  • Like
Reactions: gaxapu1808, .:RooZi.BeH:., jonathan.hemming and 58 others
TheTodFather

TheTodFather

Senior Member
Aug 9, 2010
692
57
Huntsville
nice job...I had helped test it in the irc channel for ya. I def think this will be great for the community now we just need something to root and and superuser. Anyway good job
 
S

suroot

New member
Dec 28, 2010
1
0
First post. Wanted to let you know it worked on my windows7 x64 machine perfectly fine. so much easier than the long way.
 
T

tunwear

Senior Member
Aug 28, 2010
93
4
I'm using Windows 7 32bit. I unzipped the driver pack, clicked install.exe, then it said something about not having a correct version of windows and to get windows 7 x86 or x64, then a window popped up saying it successfully installed. Assuming that it didn't and using my extreme deduction skills, I opened DPInst.exe and it did it's thing and installed fine. Don't know what happened with install.exe but it works now. Thanks!
 
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
Strange... do you remember the exact text of the error?

My install.exe runs DPInst.exe with the /q (quiet) switch, so it shouldn't have even given an error (even if there was a legit error message thrown by DPInst.exe).

Do you think you had install.exe set for compatibility mode? (check the properties for install.exe and possibly DPInst.exe)

Thanks for the feedback! I sure hope this alleviates most of the headaches associated with installing ADB on Windows.
 
R

Rylynmila

Member
Jan 2, 2011
13
0
Fault when I install but it installs fine.

It installed fine even though I got this message.
 

Attachments

  • 121212.JPG
    121212.JPG
    35.2 KB · Views: 2,622
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
Hm, that's strange.. this worked on my XP SP2 machine, I wonder if it's possible that some machines report the architecture differently..

I'll make a quick script that should let me figure this out easier. It's probably just an error in my script's logic for deciding which version to use.
 
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
EDIT: Newly released version has been uploaded. This should fix the CPU architecture problems.

Ah, well, just found the culprit! My AutoIT script checks the architecture of the CPU itself, not the OS you're running.

On the Windows XP machine I tried it on, the CPU itself is only a 32-bit cpu (Athlon XP 3200+), therefore it reported it right.

I should have used @OSArch rather than @CPUArch in AutoIT. Oops.

I'll make an updated version and release it later today.
 
Last edited:
D

DrewLGT

Senior Member
Aug 15, 2010
56
1
cant seem to get this working on my 64 bit vista machine.


installed fine, but adb devices shows nothing
 
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
DrewLGT said:
cant seem to get this working on my 64 bit vista machine.


installed fine, but adb devices shows nothing
Click to expand...
Click to collapse

When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.

If you do have that entry, try running
Code: 
adb kill-server
then
adb devices
and see what you get.
 
D

DrewLGT

Senior Member
Aug 15, 2010
56
1
thecubed said:
When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.

If you do have that entry, try running
Code: 
adb kill-server
then
adb devices
and see what you get.
Click to expand...
Click to collapse

my wife is using the NC right now, so i'll give that a try when shes done.


i have another question though. i already had adb installed for my phone, now i have it twice. can i combine the two?
 
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,458
Austin, TX
If you just want the ADB driver, just download the driver only pack.

If you had adb installed already, this will overwrite it if it's installed to c:\android-sdk-windows.
 
B

barbo

Senior Member
Sep 17, 2008
350
47
NY
no luck with easy adb

I have xp and followed the directions given in the first post in this thread for the combo pack. I now have a lot of files in c:\android-sdk-windows\ but when I follow these directions (from Nook Devs) I do not get the proper output...
"Start > Run > cmd > Enter
* cd\
* cd android-sdk-windows\platform-tools
* adb kill-server
* adb devices
If you get output that looks like the following you have succeeded:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[YOUR NOOKCOLOR SN] device"

For my output, I get the first three lines but not the
[YOUR NOOKCOLOR SN] device

I looked in Device manager and do not see anything about Android in there. I am obviously an android noob - can anyone help me? Thanks
 
Disgustoid

Disgustoid

Member
Jun 12, 2010
28
2
Can't wait to try this. Thanks!

I consider myself pretty proficient with electronics and computers but I could never get ADB working on my Win7 64 PC no matter which set of instructions I followed. The benefit of this is that I've learned how to use Root Explorer to accomplish a lot of things. :)

EDIT: This worked perfectly on my PC, although I wasn't prompted to install any drivers. Guessing I had already done so previously trying to get this to work. Thanks much!!
 
Last edited:
You must log in or register to reply here.

Similar threads

D
[DEV] CM11 Work-In-Progress
Replies
4K
Views
2M
owim
owim
V
[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards.
Replies
2K
Views
1M
A
AdilJ
mrg666
[ROM+Kernel] MiRaGe - Custom CM7.2 for Nook Color - 07272013
Replies
2K
Views
758K
Z
zagzag99
xboxexpert
[SCRIPT] Nook Color USB Drivers and ADB Setup (WinXP&7)
Replies
100
Views
135K
M
MargretMinette
fattire
[ROM] CyanogenMod 10 Nightly Builds for Nook Color
Replies
2K
Views
708K
leapinlar
leapinlar

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 61
    thecubed
    thecubed
    Howdy everyone!

    Without further ado, I humbly present my gift to the community (and the #nookcolor irc channel :) )

    This collection of scripts will automagically install:
    • NookColor USB ADB Drivers
    • The necessary adb_usb.ini file for adb to recognize the NookColor
    • A stripped-down copy of the Android SDK, with just the requirements for adb.exe
    • adb.exe is added to your %PATH% variable.

    Tested on Windows 7 32/64, Windows Vista 32, Windows XP SP2/SP3

    Now I realize not everyone wants the do-all end-all script, so there's two versions: one that contains the drivers AND a cut down Android SDK, or the version that only installs the ADB driver and the proper adb_usb.ini file.

    Instructions for use with combo pack (please read!):
    1. Download the combo pack
    2. With your NookColor unplugged from your PC, run the nookcolor-easyADB.exe file and allow it to extract to c:\
    3. Follow the on-screen instructions and wait until you see "All done!"
    4. Plug in your NookColor, tell Windows not to use Windows Update, and let it search your computer for the proper drivers.

    Once the package has finished installing, and the drivers are installed, you can just open a command prompt window and type:
    Code: 
    adb devices
    If you see your device's serial number listed, you're good to go!

    Instructions for the driver-only pack:
    1. Download the driver-only pack
    2. Extract it somewhere on your PC (may I recommend c:\android-sdk-windows\usb_driver ?)
    3. Run install.exe in the extracted folder and follow the onscreen prompts.

    For those of you that would like, the source of the driver installer is contained in both downloads as install.au3. Driver installation is accomplished using dpinst.exe from the Windows Driver Development Kit.

    Also, to avoid any confusion, I am also known as IOMonster on IRC.

    Okay now for the good stuff...

    DOWNLOADS:

    Update: 0.2 version has been released. Should fix CPU architecture errors when installing. I have also changed the download protection on my server, you should be able to use download managers now.. just keep it to a sane number of concurrent downloads by IP.

    Troubleshooting:
    1. Make sure you're rooted
      Sounds dumb, but trust me, it's happened.
    2. Make sure you haven't used ADBWireless and forgotten to disable it
      Guilty here. I spent a good half hour trying to figure out why it didn't work on one of my Nooks until I realized that I had left ADBWireless on.
    3. Check device manager for a "Nook" device, you may just have to do an "update driver" on it
      Just like it says, check for any devices labeled "Nook" or "USB Composite Device" with a VID of 2080
    4. Uninstall ALL Nook-related devices in device manager
      Check device manager for any USB devices (usually USB Composite Device or USB Mass Storage) with a VID of 2080 and PID of 0002, uninstall 'em and unplug/replug your Nook.

    Please note that this is a VERY initial build. It may not work for you under some circumstances, but on the few machines I've tried it on, it seemed to work for me. If you encounter any weird bugs, please let me know- I'd love to know so I can fix it.

    (As a side note, I really need to standardize my nomenclature for my driver pack..)
    View
    4
    G
    gr8sk8
    it's a driver issue, don't install from windows update

    Here's how I got adb to work on my Win 7 64-bit system, hope it helps you guys out.

    First, let me say thanks to Sempai67, his suggestion gave me the inspiration to work on the problem some more. Although deleting the .android folder didn't fix my problem, it was during this troubleshooting session that I stumbled on the answer.

    The key is in thecubed's first post, step 4 he says not to let windows update download the latest driver and to search the system instead. I was never prompted for it, my system was set to automatically download from windows update. During this round of troubleshooting, I noticed the nook 'searching for the latest driver on windows update' - luckily, my laptop was connected via ethernet cable, not wireless, so i quickly yanked the cable which resulted in 'no device driver found.' In device manager, I selected to update the nook driver and pointed it at the \android-sdk-windows\usb-driver folder, was warned that the driver wasn't signed and bam, I had a shiny new android device in device manager. The thing is, I don't know how I 'uninstalled' the nook driver because during my troubleshooting sessions earlier today I did try uninstalling, but it seems I only uninstalled the mass storage device drivers. If it helps, there was a google driver I uninstalled under programs and features in control panel, it hasn't returned since I got adb working.

    Also, to disable the automatic downloading of drivers from windows update, go to system in control panel, then select advanced system settings, then the hardware tab, then device installation settings. In there you'll probably find your system is set to "Yes", instead, select "No, let me choose what to do" and there are a few sub-buttons to select, either choose "Never install driver software from Windows Update" or "Install driver software from Windows Update if it is not found on my computer." Either setting should result in a prompt at which point you can point the installer at the \android-sdk-windows\usb-driver folder.

    I hope that helps you guys out, and thanks for everyone's input, I'm on to fix the ad-hoc wifi networking. Good luck, and happy rooting!
    View
    3
    D
    dzigns
    TT01 said:
    I've tried this (and several other methods ) to get my NC to be seen by ADB. My EVO ADB works fine.
    I have uninstalled and reinstalled from device manager many times. Your scripts (tried them both) finish without error, but ADB devices produces an empty list.
    I used autonooter, have superuser and root explorer working fine. I wanted to ADB into my nook to solve some problems I'm having with multi touch, the market, and the slide it keyboard not working correctly.
    I'm running a 32bit Win7 system, and no matter what I do, MyNOOKcolor always shows up under portable devices with a Wpdfs.dll driver. When I try to update the driver, 'Windows has determined the driver software for your device is up to date.' and will not let me proceed. It's using WPD FileSystem Volume Driver.
    At this point I'm considering renaming the WPDfs.dll and WUDFRd.sys in my Windows directory and just hoping that no other device is using them, but I'm a little hesitant to mess with my windows directory because then the registry would be pointing at non-existent files.
    I guess I could use a little guidance here.
    Click to expand...
    Click to collapse

    I was having the exact same issue. Here's what I did to finally get the driver to reinstall.
    1. Changed the Device Installation Settings (Select 'No, let me choose what to do' & then 'Never install driver software from Windows Update')
    2. Rebooted my computer.
    3. Connected my Nook via USB.
    4. Opened Device Manager.
    5. **Deleted the driver for 'USB Mass Storage Device' with VID_2080 found under Universal Serial Bus controllers (this what tripped me up!) ***There might be several USB Mass Storage Device, so to find the one with VID_2080, to find the VID, double click on a USB Mass Storage Device, click on the 'Details' tab, in Property drop down select 'Hardware Ids'. ***
    6. Click on 'Action' and 'Scan for hardware changes'
    7. My Nook then showed up in the Device Manager with the yellow exclamation icon. Right click and choose 'Update Driver Software'
    8. Choose 'Browse my computer...'
    9. Select the drivers from 'c:\android-sdk-windows\usb_driver\' folder
    10. Yay! My Nook shows up in Device Manager as 'Android Phone' and ADB works! :)

    I am sure these are the exact same instructions that others have posted, but I had a hard time with #5. I wasn't finding and deleting the right drivers. Hope this helps someone else. :)
    View
    2
    S
    Sempai67
    Windows 7

    gr8sk8, make sure you don't already have a .android folder in 'C:\Users\gr8sk8t' (or whatever yours is). I had the same problem. Removing that .android folder and then walking through the instructions again took care of it.
    View
    2
    thecubed
    thecubed
    Okay, just got back from a quick road trip, and it appears that some people are having issues with the drivers still...

    Here's my troubleshooter:
    1. Make sure you're rooted
      Sounds dumb, but trust me, it's happened.
    2. Make sure you haven't used ADBWireless and forgotten to disable it
      Guilty here. I spent a good half hour trying to figure out why it didn't work on one of my Nooks until I realized that I had left ADBWireless on.
    3. Check device manager for a "Nook" device, you may just have to do an "update driver" on it
      Just like it says, check for any devices labeled "Nook" or "USB Composite Device" with a VID of 2080
    4. Uninstall ALL Nook-related devices in device manager
      Check device manager for any USB devices (usually USB Composite Device or USB Mass Storage) with a VID of 2080 and PID of 0002, uninstall 'em and unplug/replug your Nook.

    Those instructions should solve most issues, except for the .android folder issue. My script is supposed to overwrite any files in c:\users\...\.android\, so that shouldn't be an issue, but I suppose like the architecture problem earlier, I'm not a perfect coder :)

    Thanks for all the responses so far, it seems (by sheer download count!) that this utility is useful. I'm glad to be of help!
    View

New posts