Database Develop

[Q] Nook, ADB problems

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.

USB Mount Issues (CM7)

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.

[Q] Nook HD cm10.1 ADB

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.

Need help trying to unlock bootloader on HTC One

So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.

First off, I barely know anything with regards to phones as I still learning. However, last night had a similar issue and ended up having to use cmd prompt to navigate to adb and then used it to see the device.
MrTechie890 said:
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
Click to expand...
Click to collapse

New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.

BD619 said:
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
Click to expand...
Click to collapse
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?

MrTechie890 said:
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
Click to expand...
Click to collapse
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).

tdhite said:
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
Click to expand...
Click to collapse
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.

MrTechie890 said:
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
Click to expand...
Click to collapse
Then try this:
adb backup
That should create a backup file called: backup.ab

tdhite said:
Then try this:
adb backup
That should create a backup file called: backup.ab
Click to expand...
Click to collapse
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.

MrTechie890 said:
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
Click to expand...
Click to collapse
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.

tdhite said:
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
Click to expand...
Click to collapse
For me, doing it on Linux wouldn't be a huge issue but since I have a mac as my primary machine I'm trying to make due with it.

I think I just firgured it out actually. I just had to install the android sdk, I was using the abd files provided from a tutorial. anyhow, thanks for trying to help tdhite.

[Q] No ADB access out of box

So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked

Cheetohz said:
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Click to expand...
Click to collapse
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?

PaisanNYC said:
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
Click to expand...
Click to collapse
I actually did nto check device manager. but I had the safely eject Nexus 6 show up in my task bar, so it was recognizing it as a nexus.