My nook use to be able to connect to my fedora computer at home and my windows computer (had to install Motorola drivers for that) at work.
I had no troubles connecting either with my rooted stock nook or with running CM7 from the SD card.
I installed CM7 internally and really messed that up. Eventually I got it working and everything works fine except I cannot get it to connect via usb on either my linux machine nor my windows.
What information can I provide?
Windows sees it but the driver fails according to device manager (explorer shows the drive letters but when I select it, it tells me to insert a disk.) Linux shows nothing in kde but I can run lsusb when I get home to see if it even sees it.
I tried pugging it into my fedora machine.
The only new line between when it is plugged in and not is
Bus 002 Device 004: ID 2080:0002
What version of CM7 are you running? My USB connectivity stopped working with nightly 69. It worked fine with 7.0.2.
That must be it. I have been updating hoping the problem would be resolved. I'll try downgrading to a build pre-69.
I am at 75 right now. I couldn;t get 76 to boot and the comments said that 77 suffered the same affliction.
I had to wipe my nook and start over so I really didn;t notice the version change otherwise I would have started there.
Thanks for the heads up.
I'll post back tonight on weather downgrading solved this issue.
At home, I ssh into my nook, but this isn't possible at work since I can't get the nook on a network there.
I used the usb apk to get around this issue.
Thank you
I just upgraded from CM7 nightly 76 to nightly 87, and now usb storage works perfectly. The internal emmc partition and my sd card pop right up in Windows.
I just installed nightly 87 today & I am still having no USB connectivity at all. Did you also install an OC kernel?
christoophat said:
I just installed nightly 87 today & I am still having no USB connectivity at all. Did you also install an OC kernel?
Click to expand...
Click to collapse
Nope, stock kernel that came with CM7.
Alright...looks I have some work to do tonight, thanks
Related
Like I said, I finally decided to take the plunge after running it exclusively on my sd for over a year, and now usb connectivity isn't working. Before all I had to do was install sd split widget, hit it and wait for aboug,t 20 minutes the first time, then each one after that was only about 1 minute.
Anyway, I flashed to scooter's cyanogen, but I was having issues with the lcd density(I use 320x480 for swype, and he didn't include roguetools, and I have no data and I couldn't connect to my computer to transfer it over, so I could not use it), so I flashed to super froyo rls16. I had been using it on SD so I was familiar with it. I installed it fine, used Titanium to restore all my apps and stuff, but when I went to hook it up to my computer to transfer some apps, I couldn't get it to connect. I have left it in split activated mode for 2+ hours and still nothing.
Some things to note
In both scooter's and superfroyo, I get a message from windows saying if you use a 2.0 usb port then it can perform faster.
I have tried the built in share files functionality in superfroyo and it just sits there for as long as I let it
I've tried different USB ports
I've tried uninstalling windows drives and reinstalling
I'm using windows 7 x64
Like I said, while running on SD, I had no issues with this stuff at all.
Its not urgent, thanks to titanium, I got all my apps and data back the way they were, but since I have no data and MMS doesn't work for verizon/android/vogue, now I have no way of transferring files or pictures on this phone.
Thanks for reading this all and a special thanks to all the devs who got me to this point.
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel-release.git;a=tree
Download the latest 2.6.25 kernel from there - 10/31/10
Works fine on USB 2.0 mode for my Touch
Same thing happened to me. My theory is that Windows looked for a driver and it installed one that won't let you use your phone as a mass storage device. Try using a different computer and see if it has the same affect.
And the 2.6.25 kernel is not compatible with Scooters Cyanogen Mod.
mikurej95 said:
Same thing happened to me. My theory is that Windows looked for a driver and it installed one that won't let you use your phone as a mass storage device. Try using a different computer and see if it has the same affect.
And the 2.6.25 kernel is not compatible with Scooters Cyanogen Mod.
Click to expand...
Click to collapse
I had the same problems with both kernels (.25 or .32).
I use the Dual Mount SD widget.
Did you install the ADB drivers?
waterpolo said:
I had the same problems with both kernels (.25 or .32).
I use the Dual Mount SD widget.
Did you install the ADB drivers?
Click to expand...
Click to collapse
Yea I installed the ADB Drivers. Thing is Ubuntu and Mac OS X detect it fine with no problems and instantly at that. Silly Windows trying to find drivers.
But it also didn't work on my brothers netbook with XP and it didn't have the ADB drivers
I'm using the latest .32 kernal.
And I'm using ADB drivers with the dual mount widget.
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.
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
This is getting frustrating now, no matter what I do I get this message: "USB Device Not Recognised"
Here is what I have tried:
Connect on android
Connect as MTP
Different USB cable (5 to be precise)
DIfferent USB port
WebOS recovery
Reinstall Novacom Drivers
Restart PC
Restart Touchpad
I have no idea what else I can try, no matter what I do, this annoying message persists!
Platform? ROM?
What's the ROM you are using? Also, which platform is your PC on? Linux/Windows/Mac?
In case you are on some 5.1.x ROM, I would recommend a nandroid backup and flashing a known 4.4.4 ROM which might tell you if it's your hardware or just Android. If you were on a stable ROM earlier where USB was working, then I would recommend trying that. :fingers-crossed:
Similar Issue.
My TP actually works (sort of) via MTP but it frequently disconnects when transferring files and freezes my explorer window. I tried to use Mass Storage on PAC KitKat FINAL and windows reports that it can't find a driver for it and when I try to reboot into recovery it only mounts a tiny SD Card partition of some 800mb. This probably won't be answered but whatever. I've been trying to solve this issue the past 8 hours. I have nothing to lose.
Blaze Viper said:
My TP actually works (sort of) via MTP but it frequently disconnects when transferring files and freezes my explorer window. I tried to use Mass Storage on PAC KitKat FINAL and windows reports that it can't find a driver for it and when I try to reboot into recovery it only mounts a tiny SD Card partition of some 800mb. This probably won't be answered but whatever. I've been trying to solve this issue the past 8 hours. I have nothing to lose.
Click to expand...
Click to collapse
hi, had some trouble with my win7 PC detecting touchpad (using JC's 4.4 Cm11), although ADB was installed - I couldn't see it as a storage drive despite the driver installing. touchpad was connected via MTP.
what worked for me was on windows - go to Device Installation Settings (drivers) and choose never install from windows update. Then under device manager -> android device -> uninstall. reconnect and it should work properly. hope that helps