I am developing Android app, using my Nook HD+ for debugging.
When I hook up my Nook to Linux (Ubuntu 12.04), "adb devices" shows my Nook as "0123456789ABCDEF Connected"
However, I am using a Windows (+IntelliJ Idea) for development
I see my Nook HD as a portable device with ability to browse internal/SD card content. However, it is not listed with a "adb devices" command
The device is shown in Device Manager as "Other devices" with an exclamation mark and "The drivers for this device are not installed. (Code 28)"
I've tried to use USB drivers from Google and B&N - no help
https :// nookdeveloper.zendesk.com/ent ries/21943338-nook-developer-start-up-guide#_Install_Gusb
And "usb_driver_r04-windows" mentioned on forum
USB debugging is enabled and I see the "Android debugging" icon in status line
I can use an ADB Wireless, though it way less convenient.
And I can't use Linux in my case, I'd prefer to use it though
Thank you
The problem is CM10 changes the ID of the device so the B&N drivers have the wrong address in the driver files. You need to look at the other device with the exclamation point and click properties and details and get the device ID. Getting ADB to work on USB Windows is a real pain and you would be better off using wireless if you can. If you look at my HD/HD+ tips thread linked in my signature and read through the thread, you will see how difficult it is.
Sent from my Nook HD+ running CM10 on Hybrid SD
Related
Hello,
I have a rooted nook and am currently running adb over wireless but I need to be able to run it over usb so as to fix the ad hoc wireless network with the nook color.
I followed the steps at nook devs to enable adb over usb but I don't see it in my device manager except under disk drives. I am running Win 7 32 bit. What should I see when I plug my nook into my system in the device manager?
Any help would be SOOO much appreciated. Major issues updating this driver!
Thanks.
neilsolanki said:
Hello,
I have a rooted nook and am currently running adb over wireless but I need to be able to run it over usb so as to fix the ad hoc wireless network with the nook color.
I followed the steps at nook devs to enable adb over usb but I don't see it in my device manager except under disk drives. I am running Win 7 32 bit. What should I see when I plug my nook into my system in the device manager?
Any help would be SOOO much appreciated. Major issues updating this driver!
Thanks.
Click to expand...
Click to collapse
Taken from the page.
You may not see nookColor in the device manager. That's ok. You should see an Android Composite ADB Interface in the device manager list, if so, you're done.
Hey guys, Im sure this is on here, I just cant seem to find it. Im running HC v4 on a SD card and when I try to ADB into it to install the market ADB doesnt see the device. I have usb debugging turned on, and ADB worked on my stock rom. Any suggestions?
Search for the nook color usb drivers on google. That worked for me at the following thread here on XDA: "[SCRIPT] Nook Color USB Drivers and ADB Setup (WinXP&7)"
I just worked through this the other day in my honeycomb .03 rooted nook. Follow the detailed directions on nookdevs (search "nookdevs: nook usb drivers"). Make sure you are admin on a windows PC while you do this. One other detail is to make sure to install the honeycomb labeled items in the SDK tool. You may not need them but they are in there so you might as well.
Are drivers always the cluprit?
I've been having similar problems with ADB not seeing my Nook. I did root it (Autonooter 3.0) and verified that USB Debugging shows to be on...and then downloaded the ADB set I found on XDA-Dev that had the full zip (adb and all) and another with just the USB drivers. But issuing the ADB command to list the devices found it still shows nothing in the list.
Are the right Nook USB drivers always the problem, since that seems to be the one thing everyone suggests trying/changing?
My ADB install never did try to use Windows Update to search for drivers (which we were warned about), and just to be safe I reran the second file to reinstall just the drivers. But at this point I'm at a loss what to try. So if it's invariably a problem with the USB drivers, well, I'm looking for pointers on a next step.
Thanks,
JTT
I am having this issue too, but USB drivers for Windows can't possibly apply as I'm running Snow Leopard (Mac OS X 10.6).
I'm guessing it has something to do with the version of ADB I'm running but I just did a fresh install of the SDK release 10, so I doubt that that is it too unless there is a particular ADB I need for Honeycomb?
Any help would be appreciated.
Guys try the same over wifi. Linky
try going into cwm recovery, go to "mounts and backups", and click the first option "mount system". then plug in the NC and, in a command prompt on the computer/laptop, kill the server, restart the server and look for devices again. also, make sure no other adb devices are connected to your computer/laptop (i.e. your phone)
i followed the directions on nook devs (mentioned above by bike4food) and all was like it said it should be by the end. unfortunately, the laptop still wasn't recognizing my NC. when i mounted the system like i described above, it recognized it.
good luck!
Well, here we go.
First of all, I'm hardly new to the world of ADB. I've got a Nexus 7 and a Kindle Fire. I've set up ADB successfully on those devices (even though The Kindle Fire was a pain). Hoiwever, I'm completely flummoxed by the NookHD+. I'm running Windows 8 x64, I've disabled Driver Signature Enforcement (twice, to be on the safe side), followed the steps on the Nook Developers website to the letter, but keep hitting a dead end. I've verified I've got the correct drivers (downloaded from the Nook Developers site), I've got Android SDK installed, I've verified the Vendor ID as 0X2080 in the adb_usb.ini file, and even have the Nook SDK installed. Hoiwever, when ever I try to update the drivers in Device Manager, it displays "MyNOOK," and if I try to update the driver, I receive the following message:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work for Windows with x64-based systems."
I've uninstalled and reinstalled the drivers, rebooted my system multiple times, disconnected and reconnected my device, tried different cables and ports, and still, nothing.
Any help would be greatly appreciated.
Anyone figure this out?
abarax said:
Anyone figure this out?
Click to expand...
Click to collapse
I don't know if I can help but I did succeed in installing the driver in win 8 x64. I got the B&N driver zip file from leapinlar's tips thread and followed the instructions from the B&N site. Nothing deviated much from their instructions except that I had to view hidden drivers in the windows device manager before I found "Other devices" and when I updated the driver I had to identify it as a Portable Device. I didn't connect the cable until the driver was installed. I do have certain developer options enabled on the Nook itself. I had previously gotten wireless adb working. For adb itself I needed to extract files from the most current Android SDK (leapinlar's older versions didn't work, at least not with CM 10.2).
BTW, I am totally new to adb.
Edit: Also, mine didn't say MyNOOK anywhere. It showed the device name in device manager, something like BN Nook HD+.
Sent from my Nook HD+ running CM 10.2 from SD card
Hey, I'll just get to the problem:
I got the last 10.2 on my nook hd+ (MBG4GA) with trim on (flashed the kernel trim zip)
I wanted to try the android Supercharger from this thread: http://forum.xda-developers.com/showthread.php?t=991276
I ended up unistalling the nook usb drivers (from device manager, MY NOOK, unistalled) and installing the google usb drivers to have a .bat script recognise the device from pc through usb. Unfortunately it didnt go as planned, so I decided to do it manually (getting the script on the nook and running it there from the script manager).
But unfortunately my pc does not see the device anymore. If I plug it in and disable debugging mode the computer plays the classic sound but it doesnt detect the storage, whereas before my "messup" it detected "MY NOOK", that had the 32GB mass storage and micro sd icons. So I can't put any file in there anymore.
In the device manager I only see "Android Phone", and, under this voice, lies "Android Composite ADB Interface".
How can I make my pc detect the device as before?
bump
Nolfer said:
In the device manager I only see "Android Phone", and, under this voice, lies "Android Composite ADB Interface".
How can I make my pc detect the device as before?
Click to expand...
Click to collapse
Try uninstalling those two devices and start fresh.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Try uninstalling those two devices and start fresh
Click to expand...
Click to collapse
Thanks! that worked
Hello. At first this may seem like I have not done my due diligence, and am posting a duplicated problem I have seen posted all over about using ADB to connect to a Kindle Fire HD 7' (mine is 2nd gen). I have installed jave/android sdks, eclipse, have updated everything, read through countless threads, followed amazon instructions to set up my environment for running apps on my kindle. The emulator is set up and runs. Here is where I am having serious issues:
My Kindle when I started showed up under portable devices in the device manager. I uninstalled the driver and have tried both the Kindle drivers from extras/amazon as well as google usb drivers. (I also even tried changing the google driver .inf file to include code for a Kindle).
This is where my problems seems to be unique to the countless thread posts I have read through. The drivers for both methods result in the driver showing "Android ADB Interface" without the Composite keyword. I have manually changed the driver by selecting to locate it myself. The only three options read "Android ADB Interface" each. I uncheck the box for "Show compatible hardware" and two more options appear:
"Android Composite ADB Interface Version: 1.3.1000.0 [12/3/2012]"
and
"Android Composite ADB Interface Version: 1.0.0.0 [8/20/2012]"
I have tried both. ADB devices from the cmd prompt still list zero devices.
If I update the driver to let Windows search for it in the amazon or google locations, it always gets (updated?) changed to just "Android ADB Interface".
This is driving me crazy. Any suggestions? I would really appreciate it or any links I can try reading.
Thanks in advance.
Try the drivers in my signature, but as I remember it is supposed to say what you are seeing as the device name. I use Linux most of the time so I don't have any issues but I'm pretty sure that android adb interface is what windows lists it as.
Sent from my Amazon Kindle Fire HD using Tapatalk
Thanks for a quick response.
stunts513 said:
Try the drivers in my signature, but as I remember it is supposed to say what you are seeing as the device name. I use Linux most of the time so I don't have any issues but I'm pretty sure that android adb interface is what windows lists it as.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Hey Stunts. Thanks for a response. I tried using your usb drivers from your signature. The updated driver list changed to list the Device as Android Device and the Driver as Android ADB Interface. It used to list the Device as Kindle, and the Driver as Android Composite ADB Interface. I ran ADB with your driver and it still lists nothing under connected devices (in the cmd).
Just to clarify: yes, ADB is enabled on the kindle (under security), and also it allows installation of applications from unknow sources (under Device).
Also, I can use ADB with other Android phones on my same setup. So this, I am assuming, is some sort of driver issue(s)?
Thanks.
Interesting, usually when it shows up as an MTP device and a adb device there's also a composite USB device under USB devices, check for a composite USB device with a vid of 1949 and try uninstalling it if you find it, and then search for new devices and see what happens.
Sent from my Amazon Kindle Fire HD using Tapatalk