Related
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.
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
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.
Hey, everyone, I tried posting about this in the CM7 general discussion thread, but no one seemed apt to respond.
I think this was a problem that popped up in the 60s or 70s in terms of nightlies, but I'm having it again now since around the 155 mark.
I'm on 160 and when I plug my NC into the USB cable, I no longer get any options to connect for file transfers in the notification area. If anyone could help me out with this, I'd really appreciate it. It's just so perplexing and no one seems be having this issue except me. If it's user-side error, that's fine as well, I'd just like to know how to fix it.
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
votinh said:
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
Click to expand...
Click to collapse
1. No, nothing comes up.
2. The notification area remains blank.
3. I'm running it off eMMC.
Thanks for taking the time, by the way!
If so, unplug the usb cable then replug in a few times and see what happens.
If still nothing, try to use other usb cable.
Oh, btw, have you had Nookcolotweaks app installed?
I do have Nook Tweaks installed, yes. I'm using the cable that came with the Nook, but I'm not sure I have any other cables around.
Do make sure you check OFF the USB Host feature (reboot and reconnect)
I gave that a try, too, but still nothing. So confusing!
Don't be so hard on yourself.
Let try it on different computer if you have.
Also try difference usb cable.
Last, if nothing works, update latest nightly build
When you disconnect and reconnect the nook in testing/trying to get it recognized... unplug usb cable from computer... its made a difference at times.
I know this sounds basic but in applications-settings ensure you have usb debugging checked. Sometimes when flashing different nightlies, settings change.
Sent from my NookColor using Tapatalk
Thanks again for all the help, everyone! I made sure USB debugging was checked and tried unplugging/replugging the cable, but there's still no notification coming up.
A new development:
I tried connecting it to my Windows PC instead of my Linux and it brought up this message that said it didn't recognize the device. I also tried to get ADB to see it and it can't. Does this information help or am I in trouble here?
Next time, do clearly indicate that you are using Linux or Windows. I'm sure many members here are Linux but still far less support than Windows world.
When I provided those suggestions in previous posts, I meant in Windows.
Anyway, back to your issue.
1. "it didn't recognize the device" because of missing adb usb driver. You need to get it installed first in order to use ADB, however it has nothing to do with your usb mass storage function. For now, you don't need to worry about it just yet.
2. Back to my question before, have you seen any "removable" on the PC (Windows)
Along with USB Host uncheck, if still having problem, I would suggest you either downgrade to the earlier versions or wait until tomorrow and update with another nightly build.
Good luck
I have the ADB drivers installed in Windows, as far as I know. I've used it before.
I typed "adb devices" into the prompt and it doesn't see the NC at all. Since one of the nightlies seems to be what prompted this sudden change in connectivity, I guess I'll just hope that one of the new ones can fix it. Thanks again.
Also, Windows doesn't show anything "removable" except for my external HD.
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
arda99 said:
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
Click to expand...
Click to collapse
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
junkrobot said:
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
Click to expand...
Click to collapse
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
If you've installed ADB drivers, you might want to remove it as this might mess up usb storage.
arda99 said:
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
Click to expand...
Click to collapse
Alrighty. I have those two. I've connected my NC to ADB both wirelessly and and with the cable in the past, so this should all be straightforward anyhow. It just plain refuses to cooperate.
Go to the Marketplace and download "Nook Color UMS" app. Follow instructions and it will mount properly. I had the same issue used it and it mounts proper through the app.
[Edit, first post and I got the board wrong. -_-. I thought I was in the troubleshooting section, sorry.]
Hello,
I've bought a used Galaxy Samsung GT-P1000 running Froyo.JPJM5, Firmware 2.2, and Kernal 2.6.32.9, 27.7GB internal memory.
My problem is that I can't get the PC to identify the tablet using the USB cable.
What I do and what happens when I plug in the tablet~
(USB Debugging on)
I connect the USB cable into the PC first. I plug the cable into the tablet. A 'USB is connected' notification shows up. I open it, and click mount.
I look at my computer's monitor and there's absolutely nothing showing that it EITHER identified or not! It doesn't even show a popup.
So I went to my Disk Management to check if it was hidden or something. There's nothing. It just shows my regular hard disks and that's it. No mounted anything. I even looked into my Device Manager and all seems working.
(USB Debugging off)
Nothing happens in either the PC or Tablet.
Things I've tried-
1) Enable USB Debugging.
- Plugging in the tablet, restart computer, and then enable USB Debugging while connected.
- Disable USB Debugging, restart computer w/ tablet connected.
- Plug tablet into PC, and then restart tablet. (with USB debugging and not)
2) Get KIES.
3) Uninstall KIES and only download the USB_drivers.exe thing that comes with KIES.
4) Uninstall everything (including drivers) and getting Android SDK + update everything (about 370mb).
5) Install Ubuntu and trying to get it identified + downloaded Android SDK package and updated everything. (also did lsusb- it doesn't see the tablet)
6) Tried each and every USB port in my PC. (10 ports). [Note: My other Android phone works in any of them)
7) Tried my bro's and sis' comp (win7 32bit)
8) Tried my dad's laptop (win7 64bit)
9) I unplugged tablet, placed the memory card(2GB) of my Android phone into it. Plugged it in my computer and yet it doesn't want to see it.
10) I went to a shop because I thought the USB cable is broken or the port hub is broken. The guy took it and plugged it on his PC using my own cable. He identified the problem and said "It needs its software to be updated". I asked how much, and he said $15. **** that ****. If he can do it, I can do it.
Conclusions up until now:
Tablet knows that its getting hooked up by the computer yet it doesn't send any information to the PC letting it know that it's a mounted drive.
USB Cable is fine.
Port hub is fine since it can detect the USB cable on *usb debugging* mode and I can charge the tablet with the USB cable plugged into the charger.
---------------------------------------------
Note: I tried to root it using z4root which doesn't require a USB connection. It doesn't work. It would work and work until the application crashes and I can't re open it as it always crashes after the first try. I tried using the temporary root option and it would load forever. All in all, doesn't work.
Note2: I attached 2 screenshots. One for my Disk Management window showing my partitions while the tablet is connected (and I pressed Mount on tablet). Second, is for my Device Manager window showing that there no unidentified devices and that the USB devices don't show any Android connected, yet on tablet it says it's mounted.
Thanks.
I don't know too much about how to fix windows.
But when you are using ubuntu,
did you put in this line to your /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
btw, the 51-blabla filename can be 51-xxxxxanything
once done
sudo /etc/init.d/udev restart
plug in your tab to USB port
then if you have your Android SDK, you should have adb?
do
adb devices
does it show your tab?
priyana said:
I don't know too much about how to fix windows.
But when you are using ubuntu,
did you put in this line to your /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
btw, the 51-blabla filename can be 51-xxxxxanything
once done
sudo /etc/init.d/udev restart
plug in your tab to USB port
then if you have your Android SDK, you should have adb?
do
adb devices
does it show your tab?
Click to expand...
Click to collapse
I did what you just said. There's nothing. :|
Hmm..
Out of idea.
If it isn't recognizing the sd card you could try another one. Format it in the tablet, plug it into the computer, put the update on the sd card and update that way and see if it gets recognized that way.
Sent from my SCH-I815 using XDA Premium HD app
czach5932 said:
If it isn't recognizing the sd card you could try another one. Format it in the tablet, plug it into the computer, put the update on the sd card and update that way and see if it gets recognized that way.
Click to expand...
Click to collapse
What do you mean by 'put the update on the sd card'. What update?
Anyways, what I tried is that I used another SD Card (128MB), placed it in, formatted it in the tablet, and plugged it into the computer. Nothing happened on the PC. :|
'adb devices' doesn't show any devices connected either.
(I wanted to confirm that 'adb devices' is indeed working so I tried plugging my Android phone (ST-GT602) and ran adb devices- it showed it. But not the tablet.)
Is there anything other than z4root to root a phone without a USB connection? Or is there anything that might trigger the tablet to let the PC identify it? For example, is there anything that I can place on the SD Card (through another connection.. using my phone for example), then plug it into the tablet, then run that application?
I don't care if it's for rooting or not. Perhaps it would help.
Why don't you spend that $15 at the shop?
Very curious why it works for him.
Sent from my GT-P1000 using xda app-developers app
You might find the Android update online (ICS to GB) or something like that and try to flash a signed update but if your computer doesn't recognize an Android formatted sd card I'm not sure how you would get the card formatted and then get the information to the card. You might search for the update on your tablet, download it and flash it using stock recovery. Maybe getting it updated might work but I have no idea why an out of date tablet won't show up
Also you could try searching online for modified drivers for the device.
Par that I have no idea. Might have to go back and pay the 15 but I would ask the repair guy if you could watch step by step what he is doing.
Hope the best for you.
Sent from my SCH-I815 using XDA Premium HD app