[Resolved] Problems connecting Nook with adb

[rmbsoft]

Hi,

Trying to install the usbdriver for Nook Color on Windows 8 64 bits.

In Device Manager, I have 2 portable devices:

BN Classics
I:/ (Or Sometimes Nook Color)

Whenever I try to update the driver for both of these, Windows always tells me that the latest driver is already installed. I can remove the drivers, unplug and replug the Nook Color, but at soon as Windows detects the new hardware, it re-installs the default drivers, and refuses to install anything else.

On the Kindle Fire I had the same problem, but ended up emailing myself the APK files so I could install them.

Not on the Nook, when tryi9ng to install any APK it gives me errors.

So, without being able to get adb running, what are my options to install and test my apk files on the Nook Color?

Anyone?
[import]uid: 50459 topic_id: 33871 reply_id: 333871[/import]

[Joshua_Quick]

I remember getting Windows to recognize the Nook was painful. I don’t fully remember how I did it, but here is Barnes & Noble’s official documentation on how to do this…
http://nookdevs.com/NookColor_USB_ADB
[import]uid: 32256 topic_id: 33871 reply_id: 134661[/import]

[rmbsoft]

Thanks,

I’m trying to make it work on a different computer now, running Windows XP.

Fingers crossed

[import]uid: 50459 topic_id: 33871 reply_id: 134662[/import]

[rmbsoft]

Well after trying it it my laptop with XP for 3 hours, still no luck connecting the Nook with adb, ugh.

Whats up with this rooting a Nook Colo9r, would that be a solution?

[import]uid: 50459 topic_id: 33871 reply_id: 134699[/import]

[Joshua_Quick]

I recommend that you do not root your Nook for testing reasons, so that it duplicates the same behaviors that your customers’ Nooks will exhibit.

Does your Windows machine at least detect the Nook device? Can you access your Nook’s files via Windows Explorer? Is the problem just with “adb”? If so, then that means that your PC has successfully detected your device, but you need to set up your Nook for developer mode via a “provision file”. You can find information about this at the following website…
https://nookdeveloper.barnesandnoble.com/tools-services/developer-mode.html
[import]uid: 32256 topic_id: 33871 reply_id: 134718[/import]

[rmbsoft]

Yes, it detects the Nook.

Windows 8 detects the Nook as follows:

Device Manager -> Portable devices

• BN CLASSICS
• MyNookColor

Whenever I try to update the driver for both of these devices, Windows always reports:

The Best Driver Software for your device is already installed

(WPD FileSystem Volume Driver)

I will try the developer mode, thanks for the info.

[import]uid: 50459 topic_id: 33871 reply_id: 134807[/import]

[rmbsoft]

I got 1 step further, here’s what I did:

1. Removed the USB Mass Storage Device in device Manager. Both Portable devices are now gone too.
2. Scan for hardware changes, now the Nook Color is listed as ‘Other devices’, with a yellow exclamation icon
3. Tried to update the driver, now Windows 8 says: The hash for the file is not present in the specified catalog file.
4. Search Google, now trying to disable Driver Signature Enforcement in Windows 8, so the driver installs.
5. Followed instructions here to disable Driver Signature Enforcement in Windows 8: http://laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/
6. Restarted, updated driver succesfully.
7. ADB recognizes Nook Color! Hooray!

Thanks everybody for the help

[import]uid: 50459 topic_id: 33871 reply_id: 134813[/import]

[Joshua_Quick]

Great! I’m glad you got it working.

Just to let you know, if you edit the “adb_usb.ini” file, you then need to restart the adb server in order for it to recognize your INI file change as follows:
> adb kill-server

I have to wonder if you ran into the above problem because it started working for you when you restarted your PC. I have to remember to do this because some Android SDK updates blows away my “adb_usb.ini” file changes and I then have to re-add the Nook and Kindle Fire USB IDs again… which is not cool. [import]uid: 32256 topic_id: 33871 reply_id: 134867[/import]

[Joshua_Quick]

I remember getting Windows to recognize the Nook was painful. I don’t fully remember how I did it, but here is Barnes & Noble’s official documentation on how to do this…
http://nookdevs.com/NookColor_USB_ADB
[import]uid: 32256 topic_id: 33871 reply_id: 134661[/import]

[rmbsoft]

Thanks,

I’m trying to make it work on a different computer now, running Windows XP.

Fingers crossed

[import]uid: 50459 topic_id: 33871 reply_id: 134662[/import]

[rmbsoft]

Well after trying it it my laptop with XP for 3 hours, still no luck connecting the Nook with adb, ugh.

Whats up with this rooting a Nook Colo9r, would that be a solution?

[import]uid: 50459 topic_id: 33871 reply_id: 134699[/import]

[Joshua_Quick]

I recommend that you do not root your Nook for testing reasons, so that it duplicates the same behaviors that your customers’ Nooks will exhibit.

Does your Windows machine at least detect the Nook device? Can you access your Nook’s files via Windows Explorer? Is the problem just with “adb”? If so, then that means that your PC has successfully detected your device, but you need to set up your Nook for developer mode via a “provision file”. You can find information about this at the following website…
https://nookdeveloper.barnesandnoble.com/tools-services/developer-mode.html
[import]uid: 32256 topic_id: 33871 reply_id: 134718[/import]

[rmbsoft]

Yes, it detects the Nook.

Windows 8 detects the Nook as follows:

Device Manager -> Portable devices

• BN CLASSICS
• MyNookColor

Whenever I try to update the driver for both of these devices, Windows always reports:

The Best Driver Software for your device is already installed

(WPD FileSystem Volume Driver)

I will try the developer mode, thanks for the info.

[import]uid: 50459 topic_id: 33871 reply_id: 134807[/import]

[rmbsoft]

I got 1 step further, here’s what I did:

1. Removed the USB Mass Storage Device in device Manager. Both Portable devices are now gone too.
2. Scan for hardware changes, now the Nook Color is listed as ‘Other devices’, with a yellow exclamation icon
3. Tried to update the driver, now Windows 8 says: The hash for the file is not present in the specified catalog file.
4. Search Google, now trying to disable Driver Signature Enforcement in Windows 8, so the driver installs.
5. Followed instructions here to disable Driver Signature Enforcement in Windows 8: http://laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/
6. Restarted, updated driver succesfully.
7. ADB recognizes Nook Color! Hooray!

Thanks everybody for the help

[import]uid: 50459 topic_id: 33871 reply_id: 134813[/import]

[Joshua_Quick]

Great! I’m glad you got it working.

Just to let you know, if you edit the “adb_usb.ini” file, you then need to restart the adb server in order for it to recognize your INI file change as follows:
> adb kill-server

I have to wonder if you ran into the above problem because it started working for you when you restarted your PC. I have to remember to do this because some Android SDK updates blows away my “adb_usb.ini” file changes and I then have to re-add the Nook and Kindle Fire USB IDs again… which is not cool. [import]uid: 32256 topic_id: 33871 reply_id: 134867[/import]