So what's the trick to getting adb to work with the HD+ and Ubuntu? I have CM10.1 on the HD+.
I have the UDEV rule set, but it doesn't show up in adb devices. I can transfer files using MTP, so the USB is working and file access is working. Just something is up with adb. I have turned on USB debugging and entered "Developer Mode" on the HD+.
FWIW My Rugby Pro and Nook Color both work fine with adb.
Is there something else I need to do on the HD+?
A bit late, but it might help others. You need to add the following line to ~/.android/adb_usb.ini
Code:
0x2080
Related
installed easyadb, drivers seem fine but when I type "adb devices" I get nothing under devices listed. I've read a bunch and tried several different things concerning usb debugging and different drivers, nothing seems to be working.
Thanks.
EDIT - It finally connected but I have no idea why. Is there anything I can do to make this less of a PITA?
here is what worked for me
Had the same issue on windows 7.
Took days for me to figure this out.
Clue was one time when i connected the nook, the add hardware popup reported an error. I looked at the details, which by the way, showed up behind my other windows. It stated that B & N Nook Color..., USB Mass... and USB Composite... installed correctly, but a device named NookColor did not.
So the fix i figured out was to open the android_winusb.inf file in the C:\android-sdk-windows\usb_driver folder and add
;
;NookColor
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
;
under the [Google.NTx86] and [Google.NTamd64] sections.
Note: I don't believe that the lines with the single ; mean anything other then to make the file more readible. you should make every effort to keep the file neat, orderly and easy to read though. You should be able to figure out the simple patern in the ini file.
Make sure that you have the .android folder and adb_usb.ini file with the 0x2080 contents in your user directory. (easily found in windows explorer and adding it is detailed in almost all instructions to get ADB set up)
Next step was to connect the nook via usb if not connected. Delete all of the devices with HW id which have the first value of USB\VID_2030&PID_002&REV_0216&MI_00. There could be 1 to 3 listed as USB Composite Device, USB Mass Storage Device under Universal Serial Bus Controllers, and Android Coposit ADB Interface under Adroid Phone.
I ran adb kill-server from the cmd line at this point. this is a good trick if at any point your having a problem replacing or editing anything in the .android folder.
Unplug the nook usb and (i like to wait a few seconds) plug it back in. windows should start to reconize and add the device.
when windows is finished being windows, you can check if this succeded by runing adb devices from the cmd line. If it is successful your device serial number should be listed.
If not successful delete all of the devices mentioned above from device manager. unplug the nook and reboot. When windows finishes booting up, try to plug in the nook again.
If that doesn't work I suggest deleting the any of the 3 devices from device manager again, check that the .android folder is there and contents are correct, make sure the android_winusb.inf has the changes recommended above, disconnect nook, reboot and plug in nook again. As this is windows, rebooting often isn't a bad idea either.
Hope this helps the weary Nook HC nobe as i am one. Keep pluging away.
Also if you get this working check out the root forum. I'm still trying to figure the fax speak out myself but it looks like the next step.
http://forum.xda-developers.com/showthread.php?t=953110
Edit: above instructions worked for me. my faxspeak is getting better. errrermmmmmeerrebeeep.
Do the nebe group a favor as well and if you figure something out post it to the general forum.
After you make all those device edits, do you always get adb or can you turn off debugging in nook color tools and get the usb mode for regular transfers?
Just Tested
doncaruana said:
After you make all those device edits, do you always get adb or can you turn off debugging in nook color tools and get the usb mode for regular transfers?
Click to expand...
Click to collapse
I think your asking can you browse the nook HC folders from a PC the same way you can browse BN media folder when you connect the usb, so for instance you can drag and drop files onto your nook HC. i'm assuming your dual booting eggclair and HC.
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I did just test if i could use the same drivers to connect the rooted BN eclair and still access the drive from my pc and was successful. remember you have to unlock the BN eclair to access the drives.
ADB doesn't block access to the drives. you don't need to turn it off. HC v4 just doesn't have the right stuff yet to allow the mount. my guess is that it is mostly a linux filesystem, i'm guessing the media directory is a fat or windows filesystem and that is why you can mount and use from a PC.
i assume that if you just have rooted eggclair this ADB settup method should work, and it should still allow access to the BN media directory from your PC.
If that still doesn't work for you, I got mine to work under Win7x64 by removing everything with that VID in device manager and using the USB cable from my Evo. The Nook one had serious issues getting the composite ADB device.
Anyone found a solution for the Mac?
EDIT: Never mind. Found a solution here: http://nookdevs.com/NookColor_USB_ADB
Love the internet
My experiences with Adb has been a hit and miss kind of thing. Stopped trying to use it since there was not point in it.
I've been using the wireless adb app from the market without any issues.
I was having trouble setting up ADB but then just gave up via usb *being lazy that is all* and used the adbwireless app and had no problems at all
I have cm10 up and running on my nook hd+ used the adb interface to load it all worked great in the end.
my question is now that its all installed how do i get windows to recognize the nook for regular file transfer. when i connect the nook i only get the Android adb interface. i want to put some books and movies on it
baview said:
I have cm10 up and running on my nook hd+ used the adb interface to load it all worked great in the end.
my question is now that its all installed how do i get windows to recognize the nook for regular file transfer. when i connect the nook i only get the Android adb interface. i want to put some books and movies on it
Click to expand...
Click to collapse
You have to uncheck the enable adb box. Then mtp should work. It shows up as a portable device in windows explorer.
Sent from my HD+ rooted stock using Tapatalk
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
Just one more problem. (I hope) Maybe I'm missing something obvious, but I've been unable to figure out ADB drivers for a cm10.1 Nook HD. I've only been able to find ones for stock. Where would these be found/how would I get this to work?
Ardent_V said:
Just one more problem. (I hope) Maybe I'm missing something obvious, but I've been unable to figure out ADB drivers for a cm10.1 Nook HD. I've only been able to find ones for stock. Where would these be found/how would I get this to work?
Click to expand...
Click to collapse
You really don't need to use ADB USB with CM10.1. You can go to developer options and enable ADB over network and you can use wifi to connect with ADB. Just type adb connect xx.xx.xx.xx:5555 in your PC prompt, where the x's is your Nook IP address.
Sent from my Galaxy Tab 2 using XDA Premium
Thanks, but adb over wireless seems to require authorization over USB. If it is supposed to be able to do that over wifi, I haven't been able to start it. I do have the latest abd, but it hasn't helped.
Aha! I've got both USB and wireless adb working. It was quite annoying, so I made a step-by-step guide in General-here.
Yesterday I flashed cm-10.1.3-RC2 over a relatively recent nightly on my nook HD+, wiped cache and dalvik-cache and rebooted and all seems well except I can't access the nook from my Windows 7 laptop over USB.
When the USB cable is connected between the nook and my laptop, the laptop continually beeps like it does when you plug or unplug the USB even though the cable is plugged in all the time and windows explorer flashes a window open and immediately it closes. I tried setting USB to both MTP and PTP on the nook and neither works.
ADB doesn't work either - it says device not found.
On the nook I still have notifications that USB is connected and ADB is enabled even though the cable has been disconnected all night.
Anyone else experienced this?
Thanks!
You need to uncheck Android Debugging in developers options. But first you need to activate developer options. Go to settings, about tablet and tap the build number several times. Then you can access developer options in settings.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You need to uncheck Android Debugging in developers options. But first you need to activate developer options. Go to settings, about tablet and tap the build number several times. Then you can access developer options in settings.
Click to expand...
Click to collapse
That fixed not being able to access the nook over USB but ADB still doesn't work. The message I get is:
C:\sdk\platform-tools>adb.exe shell
error: device not found
it used to work before I flashed RC2
Thanks!
BuddyP1952 said:
That fixed not being able to access the nook over USB but ADB still doesn't work. The message I get is:
C:\sdk\platform-tools>adb.exe shell
error: device not found
it used to work before I flashed RC2
Thanks!
Click to expand...
Click to collapse
ADB is not easy to set up for windows. Just because it worked before does not mean it will work later. The device id keeps changing in your device driver. The solution is to not use ADB over USB, use wifi. There is a setting in developer options (ADB over network) that is much easier than USB. Just type adb connect and the IP address shown in the developer options. Much easier.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
ADB is not easy to set up for windows. Just because it worked before does not mean it will work later. The device id keeps changing in your device driver. The solution is to not use ADB over USB, use wifi. There is a setting in developer options (ADB over network) that is much easier than USB. Just type adb connect and the IP address shown in the developer options. Much easier.
Click to expand...
Click to collapse
Thanks. I was able to accomplish what I needed to using adb over IP