ADB install screwed my Nook Color

[slayda]

Grimm, I can't help but do hang in there. I understand the frustration. With my problem I just finally had to take a day off from it & managed to get out of the cycling problem I had (still not sure how). Now I back to unrooted & will wait a while to start over - probably next year. Scion is our resident expert & morale booster.

[SCION]

Originally Posted by slayda

... Scion is our resident expert & morale booster.

Definitely the latter.

[zartemis]

Originally Posted by Grimm

Trying to use the usb driver when Device Manager shows a Nook doesn't work. It says the driver is not compatible with 64-bit version of Windows 7.

Check adb again. I had trouble getting the driver installed correctly, too. However, I started getting the above message just before it started working. But I don't know why it is so flaky or difficult to get installed correctly.

If you want to give up, you should be able to get back to default by plugging in the Nook via USB, then uninstalling all drivers associated with each entry associated with the Nook (and there may be several entries, under Android Phone, under Portable Devices, and under USB. Gotta search for the correct hardware IDs, pain in the tuckus), then unplug the Nook, reboot your PC, and plug it back in. When you do that it should know nothing of the drivers you tried to install and reinstall the standard USB storage drivers.

[zeroh]

Originally Posted by Grimm

Trying to use the usb driver when Device Manager shows a Nook doesn't work. It says the driver is not compatible with 64-bit version of Windows 7.

Did you follow the steps exactly? If you don't follow it exactly and try to just browse for the driver (windows will let you do that without getting to the Have Disk button), it will give you that message. You MUST go through each step and do the Have Disk to select the driver.

From Nook Devs:

# If the "Nook" device is detected skip to step 2.

*** Skipped to step 2 ***

2. Now that you have identified the nookColor
1. Right-Click the device > Update Driver > Browse my computer > Let me pick > Have Disk
2. In the "Copy manufacturers files from:" window enter C:\android-sdk-windows\usb_driver
3. Press OK. This should install the correct drivers. (If a dialog appears asking which driver to choose, select "Android Composite ADB Device")
4. Disconnect nookColor from your computer (unplug the USB cord)
5. Reconnect nookColor
* Windows should automatically detect the device and install all necessary drivers, including ADB.
* You may not see nookColor in the device manager. That's ok. You should see an Android Composite ADB Interface in the device manager list, if so, you're done.

[zartemis]

Originally Posted by zeroh

Did you follow the steps exactly? If you don't follow it exactly and try to just browse for the driver (windows will let you do that without getting to the Have Disk button), it will give you that message. You MUST go through each step and do the Have Disk to select the driver.

FWIW, I got that error without ever using Browse -- I always did Have Disk and then entered in the path manually. In fact, the first time I applied the drivers, it gave no error, but the Nook serial never showed up in adb. It was only after I uninstalled the drivers and rebooted to try installing them again (using Have Disk, manually enter path) that I got that error. I recall doing another reboot for some reason and trying a third time (after redownloading a fresh copy of the drivers), still getting that error, yet when I tried adb just for kicks once more, it was able to detect the Nook. So I considered it done. Shrug.

[zeroh]

Originally Posted by zartemis

FWIW, I got that error without ever using Browse -- I always did Have Disk and then entered in the path manually. In fact, the first time I applied the drivers, it gave no error, but the Nook serial never showed up in adb. It was only after I uninstalled the drivers and rebooted to try installing them again (using Have Disk, manually enter path) that I got that error. I recall doing another reboot for some reason and trying a third time (after redownloading a fresh copy of the drivers), still getting that error, yet when I tried adb just for kicks once more, it was able to detect the Nook. So I considered it done. Shrug.

Your experience sounds very similar to mine except that I didn't get the error message except when I tried to skip the "Let me pick..." and use the "Have Disk" button and just clicked the browse button to choose the ini file. And after I corrected that, it came up as the ADB device. It did eventually get recognized as the android composite device after rebooting and replug.

I would try uninstalling all the devices that show up when you plug the NC and reboot (both NC and PC) then retry the usb driver update.

[swallman]

I had a similar problem - couldn't get ADB to "see" the NC (wouldn't give me a serial number) and no longer had access to the memory or SD card when connected via USB.

I disconnected the USB cable and reconnected it and Windows 7 then connected correctly. Haven't had a problem since. I am running the 32-bit version of Win 7 however.

[Grimm]

Followed it EXACTLY a number of times. Nook Devs says it's totally optional so I'm opting for the non-use path and not worried about it.

[Care]

Can somebody explain to me what exactly you need ADB for? I am contemplating getting a NC, but only if I can root it. I thought it seemed easy enough, but then I read things like this and I wonder if maybe I should wait.

Grimm, I hope you find a solution that works for you.

[SCION]

ADB is a necessity for troubleshooting and managing the state of the device. If you encounter problems that could easily be rectified using ADB, you may be forced to reset to factory and re-root to correct the problem.

From NOOK Devs: http://nookdevs.com/NookColor_USB_ADB

For users who have failed at implementing the instructions below several times, the NookColor community reccomends that you use market and download adb wireless, and perform your adb work over the wifi connection to the NC rather than painfully trying to install and modify the drivers over and over. If you would prefer to do that in the first place rather than the instructions below, we won't be insulted.

Someone here commented that they used ADB wireless.

[Grimm]

Well, I don't know what to tell you SCION, I followed the instructions to the letter three times and the results were always the same. I'm an ex-IT guy so I have some ability with devices but this simply would not cooperate.

[SCION]

I'm not doubting your ability for a minute Grimm. I'm just disappointed that we can't get you through this.

[Grimm]

Like I said, I'm not concerned. Going to have to re-root most likely with the 2.2 update so maybe there will be an package along the lines of autonooter by then.

[ColdSun]

I had this same problem. I believe the device drivers that are provided for the NC from NookDevs are badly written or something. I had problems with Windows 7 on two different computers, have had to delete the drivers several times and have had problems with the device showing up (it registers as offline) almost every time I try to connect it after the initial time I get it working.

The next problem I had with this whole rooting process is my NC would freeze during shutdown sometimes. It would sometimes not boot. I played with it many times, but for now I'm going to wait for better drivers and firmware before doing anything else. I have restored my NC to factory settings and it is working perfectly for what I need it to do (read books in dark situations). I don't like the idea of making this thing an expensive paper weight. I love it that much just the way it is.

I did however install everything I could under the rooted firmware. Dolphin HD was such a pleasure. The live wallpapers were cool. I could go on and on about all the exciting stuff I got off the market. I know I seem to be contradicting myself here, because I loved playing with all the Android stuff, but this thing is first and foremost an excellent ebook reader for me. Books load much faster from the book icon under the stock firmware too. I don't know. I might decide to go back to rooted in a month or so.

[RoboRay]

Originally Posted by Care

Can somebody explain to me what exactly you need ADB for? I am contemplating getting a NC, but only if I can root it. I thought it seemed easy enough, but then I read things like this and I wonder if maybe I should wait.

ADB is not really necessary for anything, if you install the appropriate apps such as Root Explorer and Titanium Backup.

If you like typing long, complicated commands instead of pushing a button or two, ADB is there for you. You can save all of $6 or so by using ADB instead of using the right apps.