Database Users

[Q] Cannot get adb to connect to Nook Color

Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG

I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.

Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG

Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL

Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.

themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile

my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.

Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.

Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.

that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.

I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.

Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps

[q] Help ADB was working, now device not found (CM7)

I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?

I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html

[Q] What's the micro usb port for?

Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq

It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.

Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.

I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was

I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq

Drivers from acer website.

I have adb installed should this not be enough?

You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.

I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq

I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6

I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium

Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq

don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.

If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App

gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.

I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.

sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.

Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try

Not able to ADB my STR

Hello folks,
I had a WinXP computer, and I installed android SDK, and I was able to connect to my nook via ADB. As it was aging and having fan problem, I bought a new Dell (i5, win7, 4Gb RAM, 500 Gb HD). I installed android SDK, but never tried to ADB my nook. Yesterday I tried it, and whenever I try to connect via IP, or use adb devices, nothing shows up. I tried messing with the firewall, but it was not working at all.
Does anybody have any idea to help me? And also on how to get my firewall back (removed Norton, which I believe is a bloating spyware, and installed avast antivirus, but firewall was not released either, and it gives a 0x80070424 error).

Try this
Attach the usb cable to the NST and see if it is visible in device manager. Ideally if no driver is installed, you would just see it there with an exclamation mark.
Then follow ros87's instructions here. If adb_usb.ini doesnt exist create it.
Then from device manager, update device drivers for the unrecognized nook and point it to the i386/amd folder within the android drivers folder.
once that is done, restart adb, run "adb usb", then try "adb devices". If it worked it should show you the device.

ADB wifi was easier. In fact, it was such a long time since I last used it (before 1.1.1), that I forgot to add the adbwireless button to turn it on.
But thanks anyway. I've never dared to use USB due to inner messiness of the process.

[Q] Adb sideload nexus 10 not recognized

My tablet is in developer mode, USB data bugging is clicked on. In storage, MTP is clicked on. Using the latest Android SDK along with the latest Google Win USB drivers (also different cables, different ports, uninstalled and reinstalled all drivers and software, turned on and off debug, debug authorization.. Just about everything I can think of.) Also, no, not rooted, fully stock. Been searching for a few days for this problem that occurs while trying to upgrade to Kit Kat 4.4 from JWR66Y 4.3 on my nexus 10.
Plug in my n10 normally and WIN7 will see it in the device manager as Android Device, Android Composite ADB Interface, Hardware Ids =
USB\VID_18D1&PID_4EE2&REV_0226&MI_01
USB\VID_18D1&PID_4EE2&MI_01
Boot the n10 into recovery and the adb sideload, the n10 shows everything correctly and waits for the adb sideload file. CONNECT THE USB cable and Win7 does not recognize the device. Tries to find a driver for 'other devices, nexus 10' but eventually returns with no driver found. Tried installing from specific directories (new google usb driver download), letting it search windows update evewn search my entire hd. It cannot locate a driver. Device manager shows an entirely different Hardware Id for 'other devices, Nexus 10' =
HARDWARE IDS (OTHER DEVICES, NEXUS 10)
USB\VID_18D1&PID_D001&REV_0226
USB\VID_18D1&PID_D001
I did a search with this information and found others had this ID/problem with their Nexus 7 during the Jelley Bean upgrade!
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
There is no Nexus 10 in this file, but the second line of 'google nexus (generic)' list the ID that I have when booting normally.
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
I assume that if I replace this number with the ID I see in adb sideload mode (USB\VID_18D1&PID_D001) I should be able to install the correct USB and ADB drivers as others did on their n7 (shown in that link)?
My problem is identical to tbe description on that link, but I am guessing at the fix for the n10. This sounds like the solution to me, but I am also worried if it could be a sign of a bigger broblem or might brick my nexus. So any help would be appreciated!
Thanks all!
Ed

I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.

Duplicate deleted

KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Wow, I hope someone finds this thread and it saves them the headaches and searches I have been through. Worked just like you said, installed this adb usb driver and it picked it right up. I wonder why google couldn't get the google driver to read their own nexus 10 tablet!
Now running Kitkat 4.4 with no data loss, thanks to you Kira!
Thank you!
Ed

KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Thank you, been banging my head around to try and find a fix, worked like a charm for sideloading KitKat.
cheers

Oh my god, pushing this thread because I almost needed 6 hours to root my Nexus 10 with other ADB drivers but this one worked!