Database Develop

Need help with NookColor USB ADB

I've been trying to install a few APK's on my NC but I haven't been successful with NookColor USB ADB instructions listed here: http://nookdevs.com/NookColor_USB_ADB
First of all i'm using Win7 64bit. I've gone all though the steps and did everything fine, the problem is when I get to the last step it doesn't bring up my NC serial number.
I did the troubleshooting and the adb_usb.ini is exactly what it needs to be 0x2080, I also tried to let Win7 update the nook automatically but that failed.
The one odd thing I did find is after I force the driver onto the nook it shows up in my device manager as Android Phone, and Android ADB Device not Android Composite ADB Device like the tutorial says it should.
Any help would be appreciated, thanks.

I couldn't get mine to work properly until I got my device manager to say Android Composite ADB Device - that is your clue that it is still using the wrong driver.
I found that a reboot, and changing/updating the driver worked for me - after about 3 tries!

Thanks ill give that a try.

When I plug in my NC in the device manager it shows up under portable devices. Is that the one I need to force the driver to or the USB Mass Storage Device under Universal Serial Bus Controllers?
It won't let updated the NookColor entry under portable devices so I'm assuming the correct one is under Universal Serial Bus Controllers. I can't seem to get it working. Not sure what the problem is. I've rebooted about 10 times now with no luck.

[Q] No adb access.....

Once i got my new nook color i rooted it with auto nooter, and im running 1.0.1, on my previous nook i rooted it and adb worked right then, now i cant get adb access, im using the same computer and everything, all thats diferent is its a new nook. I have full root access and can install apps and everything. Any help?

Seems to be a common problem. You can launch NookColorTools and fix it temporarily. Go to "Development" and then unchecked and then recheck the USB Debugging box.

Ok I've been doing that for a while and finnaly got the message that USB debugging is only for development. It works now......
Sent from my LogicPD Zoom2 using XDA App

Get ADB wireless, it works great.

I've had zero luck using usb adb, but adb wireless works great!

I was having similar issues so after many many attempts I just decided to go with adb wireless and would definitely recommend going that route if you can't get it working over usb.

Yeah, getting ADB to work requires a lot of uninstalling/reinstalling drivers and unplugging/replugging the device, it's very temperamental.

can someone link me to a link on how to use/setup adb wireless

beezy69 said:
can someone link me to a link on how to use/setup adb wireless
Click to expand...
Click to collapse
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.

chemical1der said:
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
Click to expand...
Click to collapse
is there any tutorials on how to use it and what commands i need to install apps?

beezy69 said:
is there any tutorials on how to use it and what commands i need to install apps?
Click to expand...
Click to collapse
once you've installed adb on your computer type "adb" at your terminal prompt and you should list of commands there.
here's the link to Android Developer's ADB website (this also lists commands):
http://developer.android.com/guide/developing/tools/adb.html
files and installation directions can be found here:
http://developer.android.com/sdk/index.html
Good luck!

Ok so me being my dumb self forgot to install the adb drivers for the nook....... im dumb haha, but i cant get them to install, every time i uninstall the mass storage driver so i can install the proper driver it automatically re-installs it....... HELPPPPPPP

Is there any way to download this to the SD and install it from there? I've upgraded to a version of froyo, which doesn't have the market, and my command line won't work after swapping nooks.

I can't seem to get mine to work with either adbwireless or via usb.
Using USB I get this:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
But it doesn't show a serial number like all the HowTo's says it should. What am I missing?
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.

This thing really needs to be pinned somewhere, preferably with IOMonster's first post. There's so many of us starting on this from scratch not able to get adb to see the device. har02's crosspost of hacku's post is what finally got it to work for me. there's a ton of junk out there that just doesn't make sense, and the installing the second driver on the "android interface" is a step that is completely missing from just about every post on this topic.
Aside from that, this forum is what got me buying a nook and happily learning all sorts of cool new things!

THANK you so much har02052, this marks the end of a 6 hour nook-fixing marathong....ahhhhh

[Q] ADB over USB driver installation troubles [SOLVED!]

Hi,
I'm trying to install the USB driver under Windows7 64 using the instructions at nookdevs.com/NookColor_USB_ADB, but can't get the Android Composite ADB Interface driver to install (only get ADB Interface).
I turned USB debugging on using NookColor Tools.
Any ideas?
Thanks!

Adb is 50/50 for me. Sometimes it works and sometime it doesn't. Restart computer and try again.

Ok, I figured out this one by accident. The USB debugging setting goes away after the nook is unplugged from the computer! Even though in NookColor Tools it's still checked, you have to uncheck it and check it again.
So here's the steps to install the driver:
- get the driver and adb_usb.ini as described nookdevs.com/NookColor_USB_ADB
- go to NookColor Tools / Development, turn USB debugging off, then turn it back on
- plug your nook in, and do not unplug until you are done with all steps!
- go to Device Manager
- if you have installed Android ADB interface, uninstall it and check delete file when the confirmation comes up
- if you don't have Android ADB interface, then uninstall the USB Mass Storage driver that corresponds to your nook (easiest to identify is to unhook all USB stick and harddrives, then there should only one remain)
- select Action/Scan for Hardware Changes
- under Other devices, the NookColor should come up, right click and select Update Driver
- select Browse...
- select Let me pick...
- Select Have Disk and browse to the USB driver folder, select the .inf
- the Android Composite ADB interface should now be in the list, install it and enjoy
Hope this helps someone.

I gave up on ADB using my brand new Win7 pc. The only solution for me was to use my old xp laptop--connected the first time, would have saved me hours of frustration. Glad it worked for you with Win7.

This took me a couple hours of trying to stumble upon, too.
But now I have it installed on two win7 64 machines, so I'm pretty sure it works.
I wish the USB debugging mode would stick. That's what messed me up.

[Q] Windows 7 ADB Drivers / App restores w/o root?

I'm looking to port app restores - mostly game saves - from my old phone to the Droid Turbo. I've used Helium in the past but I can't get the Turbo to connect to Windows 7 yet. I've been trying to use the drivers linked from the Helium URL and here, but without success.
Anyone have luck tracking down USB drivers?
Any suggestions other than Helium?
Update:
Looks like the Motorola drivers started working as soon as I posted this (of course...).

This one was driving me nuts the last two days. On Win8.1 x64, the driver wouldn't auto-load when the device was plugged in. Until I saw your edit reason, I didn't even think to go through the manual device list and select the driver manually. "ADB Interface/Mot Composite ADB Interface" worked for me, as well.
Also, if you change your USB Storage mode on the phone, it may also change how the ADB Interface is detected. I had to manually add the ADB Interface driver a second time when I turned on MTP mode for the USB Storage connection. I had had it previously disabled while trying to figure out the ADB issues, once I had ADB working, I re-enabled MTP and subsequently Windows "forgot" the ADB device driver again.

For others: I had to go through the device manager, pick the unknown adb device and update drivers, pick drivers, select the clockworkmod section on the left and instead of mot composite I had to use the first option, android composite adb interface. Now my mtp connection works. Haven't tried reconnecting yet so it may well forget the drivers again, but at least I know what to do now!

Need the drivers from google sdk kit. Just google search installing adb drivers. I used helium fine.

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?

Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.

Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!

OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse

mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!