- 234 Posts
- Nookie Froyo/Honeycomb
[TIPS] for adb "device not found" error
This is a common issue, getting your computer to recognize your NC in adb. Some have an easy time, for others, it's a struggle. Here are the best tips we have to get it going. Let us know how it works out:
first, reboot your Nook and your computer and see if it changes.
If that fails, download and unzip this file, open install.exe, and follow the on-screen prompts (this will install drivers so your computer will recognize the nook).
If that doesn't work, try opening the Super User app on your nook and then issuing the commands.
If that still doesn't work, refer to the steps in this wiki, repeating if necessary.
- 01-28-2011, 11:44 PM #2
- 01-29-2011, 10:41 PM #4
- 01-29-2011, 10:53 PM #5
- 02-13-2011, 03:54 AM #6
- 02-13-2011, 08:32 AM #7
- 02-13-2011, 09:37 AM #8
- 02-13-2011, 09:51 AM #9
- 20 Posts
After follow the instruction to the exact letter, seeing nc in device manager but no device in adb cmd devices, this fix worked for me:
Go device manger and uninstall driver at device manager - android device - android composite adb interface.
Unplug nc from usb. wait
Plug nc back in. W7 recognized new usb device, auto search for drivers and installs drivers. cmd adb devices now sees my nc serial #.
I havent had any issues since.
- 02-13-2011, 10:00 AM #10
- 02-13-2011, 10:13 AM #11
- 02-13-2011, 11:00 AM #12
Never mind. I rebooted computer and it installed adb, next problem
opening command prompt to sideload GApps and i get
"adb is not recognized as an internal or external command, operable program or batch file."
Last edited by quixoticelixer; 02-13-2011 at 11:45 AM.
- 02-13-2011, 04:52 PM #13
- 02-14-2011, 12:02 PM #14
- 02-14-2011, 12:44 PM #15
I use the install executable in the OP. After a while(couple of days, couple of weeks) the nook is not recognized, and I just use the install executable again, and then everything is fine.
It could stop seeing the nook because I connect my LG Optimus S and my HTC Hero to this laptop as well."I love talking about nothing. It is the only thing I know anything about." - Oscar Wilde
- 02-21-2011, 02:15 PM #16
I can't get it to work...
I have reached the point where the device manager accepts the NC as Android Phone/Android ADB Interface (no luck at all with the Android Composite ADB Interface version).
All these tips telling me to remove the USB device with the VID_2080 and plug NC off and on again leads to the same USB device being reinstalled. The only thing helped to get to this point was to manually point this device to the right drivers and it will be recognized as ADB inteferface (no composite).
Is it correct that at this point the NC will not get recognized as a harddrive anymore? To get this back I have to uninstall the Android device, a "search for new hardware" then brings me back my Nook (and its card).
But, "ADB devices" fails to find anything, with or without the ADB Interface being found in device manager.
I tried this in my Win7 (64 bit) and a XP VM within my Win7.
To make things even harder, my computer is in (my native) german, so I always have to guess how the english devices might translate to the german version...
What does the SuperUser comment of the OP mean? I have no idea how to "issuing the commands". The log file does not see any attempts of a connection by my Win7.
necroscopev's comment, "I was only changing the mass storage device driver and not the composite driver. Once i changed the composite one i was all set!" sounds promising, but I just find one USB device with the hardware ID VID_2080.
Can anyone point me to what I'm doing wrong here?
- 02-21-2011, 03:54 PM #17
- 60 Posts
- Rted stk, Froyo,HC,Cm7 sd
cant get laptop to recognize as android
I have to jump in the pool. I cannot even get my computer to recognize the NC as an android device. It shows up under mass storage. i have reinstalled driver at least 3 times. When i search for ADB nothing comes back...HELP Please. BTW froyo burned to boot from card.
- 02-21-2011, 04:23 PM #18
- 224 Posts
I was able to use adb a week or so ago, but have had no luck at all today. I tried all of the hints in this and other forums without luck.
I ended up using dropbox to send the adbWireless app to my rooted NC then used Root Explorer to move it to /system/app and change the prefs to match the other apps. At that point it worked and I could talk to the NC with adb again. I tried the same procedure with AngryBirds but it didn't work, however I was now able to install it wirelessly using adb.
I didn't expect the Nook to come with quite this much of a learning experience, but having been retired since 1994 I need an occasional technical challenge to keep the "little grey cells" active
- 02-21-2011, 06:48 PM #19
- 6 Posts
Cant get "Android ADB composite interface" in Device Manager
I've tried every option on android central, droidoholics, and wiki... I keep getting two "B&N Ebook Disk USB Device" showing up under Disk drives in the device manager. I haven't once seen "Android ADB composite interface" or Android Platform sooner single ADB interface, or anything else.
plus I keep getting the error of "device not found" after I put in:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
I even tried deleting everything off my computer and starting over.... same result.
- 02-22-2011, 03:01 AM #20
bradrr, have you tried to point the driver of the USB device with the hardware-ID VID_2080 to the path of one of USB drivers from central of droidoholics?
This way I got the NC at least to show up as Android ADB Interface, but no luck with ADB at all.
I now even installed the whole thing to my Netbook (XP). Same result. So it is not a Win7 64bit problem.
Can it be that the Android SDK has changed and is not incompatible anymore?
I use Revision 9, and I think some of the sites talked of using Revision 8.
Did anyone get it to work on Revision 9?
Is Revision 8 still available somewhere, or does that really not matter since this is just the program that installs the other things?
- 02-22-2011, 07:28 AM #21
I've struggled with this issue as well, for many days on end.
WIRELESS ADB will work, once you have the market installed ;-)
But I too wanted a hardwired debug interface, just loaded Froydo on SD
and need market installed. While I followed Bills link in the froydo-sd thread
I did find this---
I could get it to connect and see the device (this was on NC rooted rom).
After that what I did was repetitive connects, to see if once the usb was
disconnected and reconnected if it would discover the device again.
I basically found once connected I needed to poweroff the NC before I'd
be able to make another connection, don't know why just know those were
- 02-23-2011, 06:30 AM #22
Unmount the nook from your pc, go into the app NookColor Tools and click All Settings->Development then uncheck Auto Mount. This will prevent the SD card from being mounted automatically when plugged into the PC
After that I removed the VID_2080 card reader again and let Windows search for new hardware. It found the Nook and installed it as the ADB Composite interface, and ADB for the first time finds my Nook!
- 02-23-2011, 07:18 AM #23
- 60 Posts
- Rted stk, Froyo,HC,Cm7 sd
Booting from SD card
Does anyone have any suggestions on this. I have froyo 0.6.7 (Ibeleive that is the correct build number) burned to an sd card to boot from card not flash to rom. I can see the nook coclor under disk drives and storage but nothing shows up as android in device manager. My question is this
1 is there way possible to get GAPPS and market onto this card so it will boot when the card is inserted. Th ADB way has beat me down.
2 Is there a way to get the wireless adb onto the card so it will boot when the card is inserted.
I am a newbie and enjoy challenges but this is getting to me. Any help would be greatly appreciated
BTW NC is rooted V1.1 i dont want to lose this thats why i opted to boot from sd card.
- 03-22-2011, 10:18 PM #24
- 03-23-2011, 06:24 PM #25