Many a developer has been excited over getting a new device to program/code around on. One of the hardest things to do is look at a device, know what you want to do but have no way to get that idea onto the device because you cannot push the program to the device. No developer support is not a fun game to play. Well, Barnes and Noble have realized that not everyone wants to have access to developer options like ADB and have disabled it by default. The good news, they have made it possible through a file dropped on the root folder of the device, much like installing a manual nook update for the tablet to enable ADB Access. This is exciting news and there are a few required steps that need to be taken and we wanted to take this article to explain them step by step so there is no confusion. Check out below for what needs to be done so you can receive this file and get pushing items to your Nook Color/Tablet ASAP!

The first thing we want to do is is go to the nook developer home page which can be located at and sign in. If you have not done so already, you will want to sign up to become a developer which will take you through entering all of your information to start getting you verified.

After we have logged in for the first time we will be asked to verify and agree to a couple terms of service to develop for Android. These are fairly standard but feel free to sit for a couple hours and read through them. We decided to accept them and move on.

After you have logged in, there is the Tools and Services option along the top right of the website in the menu. In the image below you can see it highlighted by the tooltip we have hovered over it. Clicking this will take us to a page we can utilize as we will explain below.

As you can see, once you have become approved as a Barnes and Noble developer, the developer mode option will appear on the left hand verticle toolbar that when clicked will take you to a page that requires you to enter your devices series number and give it a name.

We decide that we would give our device a fairly simple and standard name of Nook Dev Tablet and entered our serial in the box provided. After you click Add Device you will be shown that your device has been added to the list.

We can now see that there are a couple different options available for this device. These include renewing the time that you have to use the provisioning file and the option to download the provisioning file. We are going to want to download the provisioning file, first making sure that the Nook Development Device is plugged into your computer and you can access the devices hard drive root.

As you can see we just saved right into the Nook Device and then safely ejected the device then removed the cable. We took precautions and this does not have to be done, but once the provisioning file is on the device we decided to restart the tablet before hooking it up to the computer where we utilize the Android SDK and more importantly, ADB. Some may have troubles with getting the drivers to install on Windows when reconnecting the device so we have the solution, right from the horses (no offense Barnes and Noble) mouth below.

If you are on a Windows system –

You will need to associate the Google USB driver (which is included in the Android SDK) with your device. The Nook Color device is NOT included in the drivers settings by default. You will need to use the drivers attached to this note.

Also you will then want to do the following

Add the string 0x2080 to your ~/.android/adb_usb.ini file.
Windows7 is super aggressive with auto-associating drivers.

You have to go into the system settings (Right Click on My Computer -> Properties -> Advanced System Settings – >Hardware

Then click on Device Installation Settings and tell it ‘No, Let me choose what to do’

Then go back into device manager, yank out the mass storage device, unmount/remount the device and you should get into a state where the device manager now has an ‘other device’ with Nook Color under that heading.

This should get you where you need to be in regards to having the device register and install drivers for ADB access on the Nook Tablet. We also want to make sure that platform-tools folder in the Android SDK is added to our path as shown below.

This will ensure that you can start pushing files onto the Nook Tablet without having to drop the files in the platform-tools folder and use ADB there. It will make it so that we can use ADB globally from the command prompt.

This should cover how to get ADB access on your device up and running. If there are any problems that you run into along the way, feel free to drop a comment in the comments section below and either I or another developer will help you our as soon as possible. Let us know if this tutorial was useful in the comments below as well as we always enjoy it when people can come to Binary Wasteland to find the answers they need. Until the next Nook Development tutorial, Happy Hacking!

Share This