How do you get access to your nook color's ADB through a computer?
I used the process on nookdevs. I am really confused because a lot of things need you to use adb access through the computer
Related
I have two Nook Colors auto-nooted with 1.0.1 and both are running fine. I used my Nook to install the Android SDK on my computer and enable Nook USB ADB. ADB is working great for my NC and I can do everything in the command line that I want.
However, I plug my brother's NC (rooted and worked like mine) into my computer and it doesn't show up in ADB ("adb devices"). I even tried rebooting, shutting down and restarting the Android SDK. I'm a noob and I'm wondering is there a setting in the SDK that only allows one Android device based on serial number to be connected with the SDK?
Ok, been trying this now for 2 hours and getting ready to throw my nook though the monitor.
I've followed the instructions for setting up ADB to work with the NC on nookDevs and it's still not working.
Ok, I'm running windows XP x64 edition. Was a pain just getting ADB installed, but I digress. When I plug in the NC, I don't see it listed under "Other Devices" in the device manager, but rather as 2 disk drives (Barnes & Noble Ereader) and a USB MAss storage device. I update the driver for the Mass Storage device and then it shows up as an Android Phone, but ADB doesn't recognise it.
Help please, I only bought this thing to turn into a tablet, and I'm quickly failing at that.
I couldn't get my windows to recognize the device either so i just use adbwireless.
The easiest way to root your nook is get the monster pack with cwr, its a bootable image that you will need to burn onto your sdcard. And if your nc is already 1.1 then grab a 1.0.1 zip to flash within cwr before rooting it.
sent from my nookcolor
Which version are u using? There is a thread for ADB driver:
http://forum.xda-developers.com/showthread.php?t=882751
This should work on 1.0.1, however, I also have problem with prerooted 1.1 as usb debugging keeps turning itself off when connected to PC and I now use ADB over wifi instead.
arda99 said:
Which version are u using? There is a thread for ADB driver:
http://forum.xda-developers.com/showthread.php?t=882751
This should work on 1.0.1, however, I also have problem with prerooted 1.1 as usb debugging keeps turning itself off when connected to PC and I now use ADB over wifi instead.
Click to expand...
Click to collapse
did that, no dice.
I have 1.0.1. Anyhoo, thank god for bootable images, otherwise it looks like I'd be stuck stock
Used the Monster Root to root, install CWM, etc. so at least that part's done. Still no ADB love.
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!
Hey guys. ADB is working fine for me and can see both my D2 and Nook Color. When I plug in a buddy's Nook Color, the PC detects the device and all is good, but I have no ADB access.
Tried...
adb kill-server
adb start-server
adb devices
But his serial number does not show up and cannot be seen. Thus, I don't have ability to push things through. Any help would be appreciated. Thanks!!!
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