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
Related
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.
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!
I installed the usb drivers for my nook as per the instuctions in this guide: http://nookdevs.com/NookColor_USB_ADB#Windows_XP.2C_Vista_and_7
It seems to have worked and in device manager "ANdroid composite ADB device" shows up under Android Phone.
But when i type adb devices when my nook is plugged in, i still dont get and devices there.
Im running 64 bit Windows 7 on an Intel Core i7 machine.
I couldn't get the ADB drivers to work via those instructions either. Luckily we have people around here that are MUCH smarter than I am.
http://forum.xda-developers.com/showthread.php?t=910008&highlight=adb+driver+install
Follow the instructions and install the software from that thread, worked for me great.
I am having the same problem here. It seems like everything is installing fine. I deleted the old usb mass storage device, installed everything, but then when I try to do adb devices, I get a blank line. No serial number. I then tried adb wireless, I connected using adb connect 192.168.2.4 and it said connect it was connected. I then ran adb devices and it spit back that it was connected to that ip address but it still doesn't give me a serial number.
This is what I get:
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>
Sorry for the multiple posts.
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>
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.
For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud
Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080
anyone have problems in ubuntu 10.04 can't get it :'(
I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk
I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.
[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.
If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs
I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps
Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.
Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave
I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.
HI,
I've had success installing my other android devices on my windows 7 x64 computer, have even used my (ADB) Nook Colour on a windows 7 32Bit laptop fine.
Problem: Android Composite ADB Driver wont install/ isn't found, Device is Auto Nootered on 1.1 using rooted stock firmware.
Tried:
I have the .android folder in my user profile dir with the device ID in it
Followed various wikis and guides (that worked for the 32Bit version)
Watched the driver load/unload in device manager as I tick 'Development Mode (enable ADB)'
Tried various driver packs from here and googles latest offering, still only matches up with Android ADB Driver not the Composite (wont even show me the composite one)
Wireless ADB works and is disabled, worried about installing CWM using wireless for some reason USB feels safer to me
Thinks I noticed:
Hardware ID is listed as USB\VID_2080&PID_0002 which matchs up with %SingleAdbInterface% in the ini file for the driver, composite aka %CompositeAdbInterface% has &MI_01 on the end. Not sure if that means its not getting the right hardware ID from the device when ADB/ Development mode is enabled of if having the wrong driver loaded on it shows up the wrong Hardware ID.
Things I havent tried, enabling ADB on the Nook using sqlite3 method, but if it works on another coputer didn't think it would be a good idea.
Plan:
Install CWM, flash CM7 or similar to device.
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
ouldsmobile said:
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
Click to expand...
Click to collapse
Same here!
This one is weird...
I'm on win7x64 and I *have* got adb to work at times. When I was first rooting my new NC (1.1.0), I fiddled with it and I had it running over usb fine. But now, when I plug in the usb and I either get that the device is unrecognized or it goes into usb sync mode. Haven't quite figured that out...
But, ultimately, I just use adb wireless for any adb stuff, although it's "not recommended". It's worked perfect for me all along.
Check this link
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
loupnook said:
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
Click to expand...
Click to collapse
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
UR Welcome and USB Automount?
NewZJ said:
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
Click to expand...
Click to collapse
Glad to help. What do you mean USB Auto Mount? I kind of thought that should happen?
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've installed DropBox but it keeps asking for an SD card, which isn't a big issue, just i haven't found the time to go buy one. Is there a way to use db without an SD card?
unfortunately no, db requires external storage. if you opened the apk to recode its default directory maybe but im not sure its possible
usb auto mount I can disable in nook tools but its a persistant system that defaults every reboot, I dont like to see it popup while using the nook when I plug it in just one of many peeves
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
GateheaD said:
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
Click to expand...
Click to collapse
I thought that as well and flashed back to the EC 1.0.1, sideloaded 1.1 update and repartitioned, used cw to add HC back and all that, and still had the same issue. Came down to the ini file not having a NookColor section.
Did you check the link http://forum.xda-developers.com/showthread.php?t=987409
I'm no stranger to drivers, I could force it to use the driver by changing the ini files but it still wouldn't appear in ADB Devices.
Flashed Nooky FroYo and now the device driver states the hardware ID has the missing '&MI_01' which means the composite driver works out of the box.
I used IOMonsters Easy USB installer and it seems to have installed the drivers for Windows 7 64Bit Fine
After running the install .exe I also had to execute the Inst64.exe