Just one more problem. (I hope) Maybe I'm missing something obvious, but I've been unable to figure out ADB drivers for a cm10.1 Nook HD. I've only been able to find ones for stock. Where would these be found/how would I get this to work?
Ardent_V said:
Just one more problem. (I hope) Maybe I'm missing something obvious, but I've been unable to figure out ADB drivers for a cm10.1 Nook HD. I've only been able to find ones for stock. Where would these be found/how would I get this to work?
Click to expand...
Click to collapse
You really don't need to use ADB USB with CM10.1. You can go to developer options and enable ADB over network and you can use wifi to connect with ADB. Just type adb connect xx.xx.xx.xx:5555 in your PC prompt, where the x's is your Nook IP address.
Sent from my Galaxy Tab 2 using XDA Premium
Thanks, but adb over wireless seems to require authorization over USB. If it is supposed to be able to do that over wifi, I haven't been able to start it. I do have the latest abd, but it hasn't helped.
Aha! I've got both USB and wireless adb working. It was quite annoying, so I made a step-by-step guide in General-here.
Related
Sorry guys, I am new here and am having a problem getting ubuntu to work on my NC. I am trying to get it to boot using adb but it will not show up on my PC. I have tried 3 different PCs (2 win7 64bit and 1 vista 32bit), installed the nook drivers but it will never show up in the command prompt. I have tried enabling and disabling development mode and I disabled USB mount. I don't know what else to try. I am on 1.1.0 of the system software if that matters. I got ubuntu to work once using terminal emulator but am having problems getting the script to work. But my main objective is getting adb to see my nook. If you could help, I'd appreciate it. Thanks
I dont follow you very well, what's your problem? Your PC doesn't see NC or something else?
Sent from my HTC Vision using XDA App
ADB does not see it is what I'm saying. I will say that I am not using the stock USB cable that came with the nook as I don't have that cable anymore. Could it be that the cable I'm using doesn't work properly? It see's everything fine when I tell it to mount the SD card. I just using a froyo card in it and adb saw it although it said offline. Could the cable be a reason why it wouldn't work?
It's possible, but not likely as I am using diiferent cable for communication between PC and NC all the time... My original is connected to a charger from the purchase of NC...
did you install the right drivers for it? It depends which OS flavor you have on your nook. Honeycomb uses different drivers vs Froyo
edein said:
did you install the right drivers for it? It depends which OS flavor you have on your nook. Honeycomb uses different drivers vs Froyo
Click to expand...
Click to collapse
I'm having the same issues. I'm on a Windows 7 Box and I can not see the NC.
In Device Drivers under <Other> I find the NC but the driver is invalid. I have DL'ed the Android SDK with the USB drivers and I have tried pointing to the driver manualy. No Joy.
Any Help would be greatly apreciated.
TY
-NJ
have you tried this? http://forum.xda-developers.com/showthread.php?t=882751 ...run the .bat and follow it's instructions.
Also: it's very important that you reboot your Nook at least once after your first OS installation.
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 installed the CM10.1 emmc version, but after doing that, I can not get adb debug working as suggested in http://forum.xda-developers.com/showthread.php?t=1994129
Did anyone encounter the same issue? Thanks a lot!
ccaappton said:
Hi. I installed the CM10.1 emmc version, but after doing that, I can not get adb debug working as suggested in http://forum.xda-developers.com/showthread.php?t=1994129
Did anyone encounter the same issue? Thanks a lot!
Click to expand...
Click to collapse
The easiest way to get ADB working with CM10.1 is to go to settings and choose the wireless option. Then you do not need to set up USB windows drivers. Just get ADB installed on windows by using my ADB rar files from that thread you referenced and use it to connect wirelessly.
Sent from my Nook HD+ running CM10 on Hybrid SD
Yesterday I flashed cm-10.1.3-RC2 over a relatively recent nightly on my nook HD+, wiped cache and dalvik-cache and rebooted and all seems well except I can't access the nook from my Windows 7 laptop over USB.
When the USB cable is connected between the nook and my laptop, the laptop continually beeps like it does when you plug or unplug the USB even though the cable is plugged in all the time and windows explorer flashes a window open and immediately it closes. I tried setting USB to both MTP and PTP on the nook and neither works.
ADB doesn't work either - it says device not found.
On the nook I still have notifications that USB is connected and ADB is enabled even though the cable has been disconnected all night.
Anyone else experienced this?
Thanks!
You need to uncheck Android Debugging in developers options. But first you need to activate developer options. Go to settings, about tablet and tap the build number several times. Then you can access developer options in settings.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You need to uncheck Android Debugging in developers options. But first you need to activate developer options. Go to settings, about tablet and tap the build number several times. Then you can access developer options in settings.
Click to expand...
Click to collapse
That fixed not being able to access the nook over USB but ADB still doesn't work. The message I get is:
C:\sdk\platform-tools>adb.exe shell
error: device not found
it used to work before I flashed RC2
Thanks!
BuddyP1952 said:
That fixed not being able to access the nook over USB but ADB still doesn't work. The message I get is:
C:\sdk\platform-tools>adb.exe shell
error: device not found
it used to work before I flashed RC2
Thanks!
Click to expand...
Click to collapse
ADB is not easy to set up for windows. Just because it worked before does not mean it will work later. The device id keeps changing in your device driver. The solution is to not use ADB over USB, use wifi. There is a setting in developer options (ADB over network) that is much easier than USB. Just type adb connect and the IP address shown in the developer options. Much easier.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
ADB is not easy to set up for windows. Just because it worked before does not mean it will work later. The device id keeps changing in your device driver. The solution is to not use ADB over USB, use wifi. There is a setting in developer options (ADB over network) that is much easier than USB. Just type adb connect and the IP address shown in the developer options. Much easier.
Click to expand...
Click to collapse
Thanks. I was able to accomplish what I needed to using adb over IP
I revived a glass unit from the home try before you by program. The Version is XE13 and I want to update it to XE16 but it won't update and it says it's up to date. The micro USB port will charge but won't connect to my PC so any idea guys?
Sent from my iPhone using Tapatalk
Not really related, but could you dump the rom if it first?
(im not sure how easy this part would be without a working usb port, you would normally simply "adb pull /system" if it worked)
I doubt that there is an ota for it to begin with, they likely never made a patch for it since it isnt public.
(unless the glass team's policy differs from the standard android one) they generally do not make otas for combinations that they would not expect in the wild
Normally if this were a nexus device, the course of action would be to just use the factory image, but like you mentioned the usb port isnt able to be detected by a pc.
If you can root it without using the usb port, it might be possible to manually get CWM loaded on it and update with a manually made update zip. But without a usb port, if anything goes wrong then it would be very difficult to recover from that.
XxCyberHackerxX said:
I revived a glass unit from the home try before you by program. The Version is XE13 and I want to update it to XE16 but it won't update and it says it's up to date. The micro USB port will charge but won't connect to my PC so any idea guys?
Click to expand...
Click to collapse
Almost positive you can't just force an update. From what I read, the Glass unit should update whenever it's plugged in and on WiFi, but I couldn't get my try-on Glass to update no matter what.
One thing that "should" work is to just push the update OTA through adb, but doing this through USB would prove... difficult. Wireless ADB didn't seem possible either unless you hooked Glass up via USB at least once to enable it.
Can you provide me instructions about wireless abd? Thanks In advance!
Sent from my iPhone using Tapatalk
XxCyberHackerxX said:
Can you provide me instructions about wireless abd? Thanks In advance!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
https://coderwall.com/p/vq-eaw
How to get the IP address of Google Glass:
In ADB, run adb shell netcfg and get the IP adress of wlan0
Now, to access ADB, you need to open up port 5555: adb tcpip 5555
Now, to connect your ADP via TCP, execute this command: adb connect IP you got from step-1
And then, start accessing the ADB Shell by typing: adb shell
And boom, that’s it. You’re now accessing ADB via TCP. Unplug your usb and type adb devices to check.
To go back to usb mode type adb usb
Click to expand...
Click to collapse
And: http://www.the4cast.com/2013/04/how-to-fetch-the-ip-address-of-google-glass-for-adb/
Basically, you need to just get the IP of Glass (when connected to WiFi) and then do adb connect ADDRESS. Everything I see though says you had to of hooked the device to the computer at least once though to activate wireless ADB, but I could be wrong (I didn't venture too far into it at the time).
Since Debug mode is enabled by-default on those units, maybe you don't need the initial USB connection.
I hope not lol otherwise I'm screwed but is it safe to do a update over adb wifi?
Sent from my iPhone using Tapatalk
Is there anyone who could help step wise instruction on how to update glass to latest firmware?