ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
2. Enable Android debugging in developer settings.
3. Plug Nook into PC and open Device Manager.
4. Go to Portable Devices/BN Nook HD/HD+ and open properties.
5. Go to the details tab and then hardware ID's in the menu.
6. Leaving that window open, unzip the usb driver. Open the folder, and then open android_winusb.inf in an editor. (I used Notepad++)
7. In the .inf file, scroll through [Google.NTx86] and find your device name. Replace USB\whatever with the first hardware ID in the list from step 5.
8. Do the same in [Google.NTamd64]
9. Save and close the file, and then go back to device manager. Click update driver/browse my computer for software in properties.
10. Navigate through and choose the modified usb_driver_r04-windows folder.
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
I had to install the Google USB android drivers from the SDK as well. Without these, I spent hours trying to get it to work. The b&n drivers alone were not enough.
Win 7 x64
jamus28 said:
I had to install the Google USB android drivers from the SDK as well. Without these, I spent hours trying to get it to work. The b&n drivers alone were not enough.
Win 7 x64
Click to expand...
Click to collapse
Thanks both Ardent_V and jamus28 for the explanation.
Yes I have to apply both methods in order to have the adb command to recognize my Nook HD+ device ID.
I'm using windows 7 x64.
Sorry. I assumed if you had adb you would have the SDK and Google drivers as well.
On previous devices, adb.exe and a few DLLs were enough.
Thank you for posting this!!!
I did have to deviate from the instructions a bit to get it working though.
1. In the INF file, I had to use the *second* line from Hardware Id's, not the first. The value that worked for me in the INF file is:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
The first Hardware Id's line has a "REV_02" in it; Windows would not accept the driver with that in it. Took that part out and it worked!
2. Instead of updating the driver in Device Manager from Portable Devices, I had to update the "BN NookHD+" that was listed with a yellow symbol under "Other devices." Then I got the expected Android Phone -> Android Composite ADB Interface device to show up in the list.
3. ADB at first listed the device as "offline." I had ADB working on stock and didn't realize that the newer version of Android has an extra security check. I actually had to Google it to realize that I just had to unlock the tablet and hit "Accept" on a dialog box on the device! After that, it went from "offline" to "device" and all was well.
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
The bottom line is that I got it to work, thanks to this thread. Nice!
Steve Tack said:
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
Click to expand...
Click to collapse
That's just me being lazy and not gettin around to pass around serial number yet.
Steve Tack said:
Thank you for posting this!!!
I did have to deviate from the instructions a bit to get it working though.
1. In the INF file, I had to use the *second* line from Hardware Id's, not the first. The value that worked for me in the INF file is:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
The first Hardware Id's line has a "REV_02" in it; Windows would not accept the driver with that in it. Took that part out and it worked!
2. Instead of updating the driver in Device Manager from Portable Devices, I had to update the "BN NookHD+" that was listed with a yellow symbol under "Other devices." Then I got the expected Android Phone -> Android Composite ADB Interface device to show up in the list.
3. ADB at first listed the device as "offline." I had ADB working on stock and didn't realize that the newer version of Android has an extra security check. I actually had to Google it to realize that I just had to unlock the tablet and hit "Accept" on a dialog box on the device! After that, it went from "offline" to "device" and all was well.
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
The bottom line is that I got it to work, thanks to this thread. Nice!
Click to expand...
Click to collapse
Made sure that I had updated Google Drivers and tried both strings and Windows showed no erros but when I type adb devices it is blank.
verygreen said:
That's just me being lazy and not gettin around to pass around serial number yet.
Click to expand...
Click to collapse
Hehe, figured it was something like that. Is there any downside to not having the real serial number returned? Doesn't seem to cause any issues that I've seen.
---------- Post added at 01:41 PM ---------- Previous post was at 01:36 PM ----------
dawgpoundfan said:
Made sure that I had updated Google Drivers and tried both strings and Windows showed no erros but when I type adb devices it is blank.
Click to expand...
Click to collapse
Do you see a device category in Device Manager called Android Phone? On my system, I see that and under that is a device called Android Composite ADB. Both times I've set it up, it wouldn't show up in ADB until I got to the point where that device showed up in the list.
If you do see that device, I suppose you could try "adb kill-server" before "adb devices" just for grins.
Steve Tack said:
Hehe, figured it was something like that. Is there any downside to not having the real serial number returned? Doesn't seem to cause any issues that I've seen.
Click to expand...
Click to collapse
Dunno, but 6/30 release added that. I imagine some apps might be using serial number for things like ensuring you don't steal stuff, also google play probably uses that to distinguish between several identical device you might have
If you are running the latest Carbon B11 emmc, and are wondering why you can't get "adb devices" to show your device, you need to insert a line to:
%userprofile%\.android\adb_usb.inf
add: 0x2080
Without this, ADB will not recognize a device with a B&N VID.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
Crap, just realized I skipped step 7 in Leapinlar's thread on setting up ADB...
error
Ardent_V said:
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
2. Enable Android debugging in developer settings.
3. Plug Nook into PC and open Device Manager.
4. Go to Portable Devices/BN Nook HD/HD+ and open properties.
5. Go to the details tab and then hardware ID's in the menu.
6. Leaving that window open, unzip the usb driver. Open the folder, and then open android_winusb.inf in an editor. (I used Notepad++)
7. In the .inf file, scroll through [Google.NTx86] and find your device name. Replace USB\whatever with the first hardware ID in the list from step 5.
8. Do the same in [Google.NTamd64]
9. Save and close the file, and then go back to device manager. Click update driver/browse my computer for software in properties.
10. Navigate through and choose the modified usb_driver_r04-windows folder.
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
Click to expand...
Click to collapse
I followed all the steps. I got the device connected. When I tried to sideload a stock rom zip, I get an error. "failed to write data protocol fault <no status>". What can I do to fix it?
toplist said:
I followed all the steps. I got the device connected. When I tried to sideload a stock rom zip, I get an error. "failed to write data protocol fault <no status>". What can I do to fix it?
Click to expand...
Click to collapse
What do you mean sideload a stock rom zip? Sideloading is for apps.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
What do you mean sideload a stock rom zip? Sideloading is for apps.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I had bokbokan's hybrid running on nook hd+. I saw an experimental version of cm10.2 and wanted to give it a try. I thought that since I can boot to stock and cm, I don't need to go back to my original bn rom. So, I deleted my cm10,1 zip from my internal storage and replaced it with cm10.2. I turned off my tablet, took out my sd card with hybrid and rewrote it with cwm for sd cm10.2. The cm10.2 updates but doesn't work when you reboot. When I turned back on, my nook gets stuck on infinite loop cyanogenmod logo instead of booting to stock . Clockworkmod shows that I have a backup but when I try it says "no files found." I have backups for original bn rom and a cm version on my pc. But since there is only 115 mb space left on my sd card after writing, I can't copy my 1+ GB back up files. I was searching on google and I came across how to update rom using adb sideloading and was trying that. That's where I get this error message. Is there any way for me get out of this mess and go back to cm? :crying::crying::crying:
toplist said:
I had bokbokan's hybrid running on nook hd+. I saw an experimental version of cm10.2 and wanted to give it a try. I thought that since I can boot to stock and cm, I don't need to go back to my original bn rom. So, I deleted my cm10,1 zip from my internal storage and replaced it with cm10.2. I turned off my tablet, took out my sd card with hybrid and rewrote it with cwm for sd cm10.2. The cm10.2 updates but doesn't work when you reboot. When I turned back on, my nook gets stuck on infinite loop cyanogenmod logo instead of booting to stock . Clockworkmod shows that I have a backup but when I try it says "no files found." I have backups for original bn rom and a cm version on my pc. But since there is only 115 mb space left on my sd card after writing, I can't copy my 1+ GB back up files. I was searching on google and I came across how to update rom using adb sideloading and was trying that. That's where I get this error message. Is there any way for me get out of this mess and go back to cm? :crying::crying::crying:
Click to expand...
Click to collapse
See my response in my HD/HD+ Tips thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
See my response in my HD/HD+ Tips thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I read your post and went through 15 pages to see if you wanted me to find anything specific. But I'm not sure what I should look for. I tried step 1 and step 2 from your post. When I tired to sideload app, I get "errors:closed" (attached image). I don't know what to do :crying:. My sdcard has CWM based recovery V6.0.3.2 for hybrid. When it is inserted, I boot to recovery. When I take off the sdcard, I get to cyanogenmod logo with infinite loop (attached image). Did I break my tablet? Is there any solution to fix this?
toplist said:
I read your post and went through 15 pages to see if you wanted me to find anything specific. But I'm not sure what I should look for. I tried step 1 and step 2 from your post. When I tired to sideload app, I get "errors:closed" (attached image). I don't know what to do :crying:. My sdcard has CWM based recovery V6.0.3.2 for hybrid. When it is inserted, I boot to recovery. When I take off the sdcard, I get to cyanogenmod logo with infinite loop (attached image). Did I break my tablet? Is there any solution to fix this?
Click to expand...
Click to collapse
I wanted you to respond on my HD/HD+ Tips thread, that is why I posted the answer there. I don't want to clutter this thread with non ADB things. Continue this discussion on my thread.
It is not broke. Make the CWM SD as detailed in item 1a. Then use that to restore your stock backup.
Sent from my Nook HD+ running CM10.1 on emmc.
Ardent_V said:
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
[Steps 2 to 10 removed for brevity.]
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
Click to expand...
Click to collapse
I recently installed the CM10.2 ROM on my Nook HD (I don't mind living dangerously!) To my surprise, I found that ADB worked out of the box, and the Nook showed up as MyNook in Windows Explorer and in Device Manager (under Portable Devices). However, after I installed the Eclipse+ADT bundle on my PC yesterday, ADB over USB stopped working, although I could still use ADB over wifi and could still open MyNook in Explorer.
So I thought I would try the instructions in the above post to repair ADB over USB. Everything seemed to work fine, there were no error messages, and ADB over USB is indeed working again. BUT, the MyNook Device Manager entry under Portable Devices has disappeared, to be replaced by an Android Composite ADB Interface entry under Android Phones, and the Nook no longer appears in Windows Explorer. In Devices and Printers it appears as a camera icon labelled "MTP" - strangely, as of course the Nook HD doesn't have a camera.
Does anyone have any suggestions for how I might get everything working again? Or would I be best to use System Restore to go back to how things were before?
My PC is running Windows 7 SP1 Home Premium.
UPDATE
=======
I have now solved this. I disconnected the Nook HD, disabled the Android Composite ADB Interface in Device Manager, and reconnected the Nook. Windows 7 installed the drivers, and the Portable Device entry reappeared in Device Manager, this time called "BN Nook HD" rather than "MyNook" (an improvement!). I then re-enabled the Android Composite ADB Interface, and everything is now working. The Nook is visible in Windows Explorer; ADB is working via USB; and the Nook's icon in Devices and Printers is now that of a portable media device - it's still labelled "MTP", but I can live with that.
Android_winusb.inf entry for HD+ running official CM11
FWIW, I just installed ADB on my Win 8.1 PC and found that the entry needed in android_winusb.inf for the HD+ running official CM11 is:
Code:
;Nook HD+
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0005&MI_01
Note the trailing &MI_01, my ADB interface will not come up without it.
Related
Hello, I have CM 7.0.3 encore with the overclocked kernel on my nook. Lately I have not been able to get the thing to connect to my computer in either windows or Linux. (It's XP and "Lucid Lynx" 10.04 Ubuntu if that helps)
If I connect my cable to either the front of back USB ports (because I have tried both under both OSs) at best I get my windows install to see and start to run auto hardware install. This, of course does not work and the machine will inform me that my new hardware (which it correctly ids as a nook until this point) may not work correctly. And, it does not. It displays as 'removable drive' and clicking on it pulls up an 'insert disk please' message.
In Ubuntu the Nook will show up as B&N Ereader. Both SD cards (the internal and the card in slot) show as the same thing. Clicking on them brings up a message that this drive is not a folder and cannot be opened as such.
This thread leads me to think that there should be a notification in windows about the usb being connected...and as soon as I post this I will be restarting to check that... but I really rather do this under Ubuntu. ETA. This does not work for me. Canceling the install software wizard does not work either. (I have been uninstalling the faulty installs each time and rebooting the comp without the nook attached. Oh, and the Nook IS awake too. )
Searches bring up nothing, and I'm a bit lost.
I must be missing something so basic and simple no one has had this issue but me. I mean, Android is a Linux variant, right? They should be able to talk to one another!??
If your trying to accomplish what I think you are then it doesn't matter what your computers says. Plug your Nook into the PC and open your notifications window. There should be a USB icon on the status bar waiting for your input. Just follow the prompts.
Given you have gone through the process of installing the Android SDK, in Linux, from the terminal you need to change to your target folder to
Code:
~/android-sdk-linux_86/platform-tools
then you need to log in as root and kill, then start the server. make sure to exit root when you are done.
Code:
su : enter password
# ./adb kill-server
# ./adb start-server
# exit
then it should pick it up.
I have the same problem as OP and went crazy trying to figure out what I was doing wrong. It's not as simple as everyone suggests.
To be clear I'm using Linux, Ubuntu Natty. I have a Samsung Vibrant also running CM7 nightlies. Start adb, plug in Vibrant, shows up in adb devices list without any problem. Plug in the NC no device in adb. running lsusb there is no android vendorID for the NC but there is for the Vibrant. The NC only shows a vendorID for the mass storage just like the OP says.
The NC is booting with CM7 nightlie on the SD card, not eMMC. Will that make a difference?
IFLATLINE, Thing is, there is no notification popup on my Nook for me to tap.
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
I did manage to brick the nook trying to update the build last night so I'm in the middle of reflashing it. So, as soon as I finish making a boot micro SD (I know, I should just have one I keep for this but I don't) I will be flashing phiremod's version of CM7 on the nook.
digver, I did find somewhere on here that the OC kernel was causing some people grief and that once they removed it they had no issues connecting the the computer... but I think they were windows. I'm not sure if that will fix this very annoying little problem.
katsrevenge said:
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
Click to expand...
Click to collapse
personally i <3 linux. It's the only way to fly esp with dealing with Androids. Android Central has a GREAT write up on how to install the SDK on your Linux unit.
I'll have to look up the link @ home. I'm at work and WebSense blocks 99% of everything.
I have tried to root my kindle with the Kindle Fire v7 and have had no luck, It comes back with The system cannot find the path specified, I have installed the drivers and my kindle shows up as Android Composite ADB Interface. Thanks for any help in advance. I have also tried the burritoRoot with no luck. I am on version 6.2.1 I have never had problems with any android devises before but this seems alittle different.
i have the exact same problem. would really appreciate some help
I had this problem and here are the steps I took to fix it.
Go to Google's website and manually download and install the SDK, at the end when it asks you to open the utility to download images and such, uncheck the box and click finish.
Download the Kindle Fire Utility v.7
Connect your Kindle Fire to your usb port.
Go to Start Menu -> Accessories -> Run and type in "devmgmt.msc" (without quotations)
There should be an "unknown device" with the name of Kindle Fire (or close to it), right click that and click update driver software.
Click "Browse my computer for driver software"
Hit Browse and locate the "drivers" folder in the Kindle Fire Utility folder
Click next and let it install the software
Go into the Kindle Fire Utility folder and run "run.bat"
Everything should work as expected from here on out, or at least it did for me
I think for both us we already have the drivers installed. the problem is in running the actual bat for the utility. unless maybe we did something wrong in installing the drivers, but i don't think so. I actually used the exact same method to install the drivers as you did.
Check your system path for what the program is trying to run. If the path is there, make sure the file its calling is there. Google adding a path to windows for more info.
I think he problem has to do with the program not finding the kindle
claytybob said:
I had this problem and here are the steps I took to fix it.
Go to Google's website and manually download and install the SDK, at the end when it asks you to open the utility to download images and such, uncheck the box and click finish.
Download the Kindle Fire Utility v.7
Connect your Kindle Fire to your usb port.
Go to Start Menu -> Accessories -> Run and type in "devmgmt.msc" (without quotations)
There should be an "unknown device" with the name of Kindle Fire (or close to it), right click that and click update driver software.
Click "Browse my computer for driver software"
Hit Browse and locate the "drivers" folder in the Kindle Fire Utility folder
Click next and let it install the software
Go into the Kindle Fire Utility folder and run "run.bat"
Everything should work as expected from here on out, or at least it did for me
Click to expand...
Click to collapse
I am good all the way to "run.bat" and when i do i get (ADB Status: Online, ADB Rooted: No, Boot Status: Unknown, So i put in #3 and press enter withch is Install Perment Root with Superuser, that is when i get all The system cannot find the path specified.
alright, so i was parusing around, and i think i found a solution. don't know why it works, but i think it will help you
Originally Posted by YourIcarus
Following this, two things happen. If I download the file from this post and attempt to install it, I receive an error stating Windows could not find files. If I install from the driver included in the OP, it's successful. However, ADB still does not recognize the device, and the Kindle Fire Utility returns an error: device not found.
Any help?
try this it may work:
open a cmd windows from your sdk tools folder, not the platform-tools, just tools and run this:
android update adb
then go to your user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close and update driver again, hope it works
credit goes to iluretar btw. make sure that you have the android sdk before doing this. delete whatever driver you had before this. after doing this, install the drivers manually through device manager and browsing to the folder included with the utility. and then...it works...for me at least, not sure why. oh, and...er...not sure where you find the link to android sdk, but i'm sure someone can provide you with that...
Fairtrade128 said:
alright, so i was parusing around, and i think i found a solution. don't know why it works, but i think it will help you
Originally Posted by YourIcarus
Following this, two things happen. If I download the file from this post and attempt to install it, I receive an error stating Windows could not find files. If I install from the driver included in the OP, it's successful. However, ADB still does not recognize the device, and the Kindle Fire Utility returns an error: device not found.
Any help?
try this it may work:
open a cmd windows from your sdk tools folder, not the platform-tools, just tools and run this:
android update adb
then go to your user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close and update driver again, hope it works
credit goes to iluretar btw. make sure that you have the android sdk before doing this. delete whatever driver you had before this. after doing this, install the drivers manually through device manager and browsing to the folder included with the utility. and then...it works...for me at least, not sure why. oh, and...er...not sure where you find the link to android sdk, but i'm sure someone can provide you with that...
Click to expand...
Click to collapse
Well I guess im still not doing it right cause im still getting The devise not found.
I moved my install_drivers.bat file from the drivers folder to the same folder as run.bat and ran it (install_drivers.bat that is). It seemed to install correctly. Now, however, my kindle will not mount. So when I try to use the utility to install TWRP, it stops at "Installing TWRP... If we get stuck here for a while, power the kindle on and off a few times. < waiting for device >"
I have rebooted my device 6 times and it still does not work. My device no longer mounts, I can't even see it in device manager. I tried installing the drivers manually prior to moving install_drivers.bat. This seemed to work but I ran the install_drivers.bat after moving it anyway, maybe that makes me a noob.
Anyway, is there a way to fix this? I want root on my device!
EDIT: Here is the script I am getting in cmd when I run install_drivers.bat. I realize that the problem is I am running Windows 7 x86. But is there a way to run it for x86 instead of x64?
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
This version of C:\Users\Chris\Desktop\Kindle Fire Utility\tools\x64\devcon.exe
is not compatible with the version of Windows you're running. Check your compute
r's system information to see whether you need a x86 (32-bit) or x64 (64-bit) ve
rsion of the program, and then contact the software publisher.
This version of C:\Users\Chris\Desktop\Kindle Fire Utility\tools\x64\devcon.exe
is not compatible with the version of Windows you're running. Check your compute
r's system information to see whether you need a x86 (32-bit) or x64 (64-bit) ve
rsion of the program, and then contact the software publisher.
Click to expand...
Click to collapse
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Clemzon said:
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Click to expand...
Click to collapse
Thank you, this is what finally got it working for me. I had tried everything; installed 3 different USB drivers, edited files, moved files around, all with no signs of progress. Finally this approach made everything work perfectly!
Clemzon said:
Here is what i did. First off, not just any data cable works, i found that lg cable dont like adb. Some samsung cables give me trouble too. But anyways. Click start menu, type device, click and open device manager the go back to start type device again and open device and printers. If the kindle has installed its drivers then you should see "kindle" in DEVICE AND PRINTERS click on kindle go to properties select driver "tab" and hit uninstall. Open device manager and make sure its still sees the kindle as ADB interface. If so then you should be all set. This should be done after editing the adb_usb file and updating the google drivers.
Click to expand...
Click to collapse
THANKS, that worked like a champ. After I did that it work.
Sent from my SAMSUNG-SGH-I997 using XDA App
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
marchingknight11 said:
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
leapinlar said:
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
Click to expand...
Click to collapse
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
marchingknight11 said:
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
Click to expand...
Click to collapse
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
leapinlar said:
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
Click to expand...
Click to collapse
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
marchingknight11 said:
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
Click to expand...
Click to collapse
If you have root explorer working on emmc, yes you can do it that way. You can actually have root explorer just install for you also.
Sent from my Nook Color running ICS and Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Droidatar said:
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Click to expand...
Click to collapse
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
THANK YOU, so very much it has been driving me crazy. I knew where that was to change it to mass storage but I just never guessed to hit menu. After I read your post I saw the tiny 3 dots in top right. I really should just wear my glasses
and Yes I have changed the letters in the past as you have noted. However it seems a mute point Calibre just released a new version that lets me correct that problem. However it's nice to have the mass storage issue fixed.
Thanks again
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
procter said:
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
Click to expand...
Click to collapse
No.. and really you shouldn't be doing these things without a fastboot cable.. What do you mean by the driver does not take effect? It sounds like you need to fix the bootloader. I would head over to the Kindle Fire First Aide thread and talk to Chris and see if he can help you out. Is adb working or have you checked? If adb is working then you will be able to enter fastboot without the cable..
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
procter said:
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
lacoursiere18 said:
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
Click to expand...
Click to collapse
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
procter said:
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
Click to expand...
Click to collapse
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
lacoursiere18 said:
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
Click to expand...
Click to collapse
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
procter said:
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
Click to expand...
Click to collapse
A lot of it is the same I am sure some aspects of the GUIDE do not work but as far as installing ADB drivers it is good. Did you uninstall it and also hit delete all software with driver?
did u recover
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
KFHD 7 Stuck at splash screen
techdeisel said:
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
Click to expand...
Click to collapse
Hey. I am having a terrible time getting my KFHD 7 back to stock. I used KFFirstAide to root it and when I went to restore it back to factory settings it ended up with the holo launcher lock screen and the android start screen. Has no notifier bar at top or menu bar at bottom. Lock screen let's me go online, to the camera, or just unlock. Don't know what happened! It's not recognized in ADB but shows up on computer as Kindle. I just want it back to stock so I can use it again! PLEASE HELP!!
In my situation, when trying to update the "Kindle" driver from Windows device manager, use the option to let you choose install driver from a list of devices instead of pointing to the directory where you have the adb driver (it will always tell you can't install even if u point it to the right directory).
In my case, I had all the drivers installed already, so when I use the option to install from the list of known devices, I can choose so"Android adb" or sth similar in that list. And after that you will be able to restore the adb connection.
Sent from my SPH-L710 using Tapatalk 2
the the reason your kindle cannot communicate properly with your computer is because it is soft-bricked, only way to recover from a soft-brick is with the use of a fastboot cable, if you are partially soft bricked...ie boot is intact and functional but system filesystem is corrupt you may be able to access fastboot with the use of a fastboot command
Like I tell everyone, go here to solve your problem.
Sent from my KFHD using xda premium
The current project I am trying to work on is trying to get USB mode to work on a rooted NST with NookManager. I have found a guide somewhere else, but it requries pushing boot and uimage files from ADB. I have tried everything I could, even using Ubuntu in Vbox but I haven't been successsful yet. For whatever reason, the USB isn't being read in Vbox-Ubuntu correctly and can't be mounted.
I have done everything I could to install the USB drivers on Windows properly, but I haven't had any luck. I have scoured the forums, but I couldn't find anything. What I need help is how to uninstall what I have reinstall correctly. I have tried the uninstall fuction in device manager but if there is a better way of doing this I haven't found anything. Can anyone help? Point me in the right direction at least? I hope if i can at least get the drivers installed correctly and adb devices to read it properly, I can figure out how to do everything else. It's just that one hurdler I'm having issues with.
I am running win 8.1 pro but willing to use ubuntu if necessary.
I should also mention what I have done. I Have altered the android_winusb.inf and the adb_usb.ini files, which sort of worked, but I still have yellow exclamations ove the device names.
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage "Android Devices" (or "Android Phones") with a device listed under it.
If you have yellow, what driver does it say it has loaded?
It should be using WinUSB.sys
What does it say when you try to reload drivers?
If it suggest "Composite USB Device" accept that.
If you are using the latest version of adb.exe (819,200 bytes) it will already have the vendor ID in it for Nook.
You will not have to modify adb_usb.ini (not that it will hurt anything).
The first step is to get the driver installed (obviously).
abd.exe should be able to connect.
If you have a problem you could try omaplink.exe as an independent check of ADB.
Renate NST said:
Well, what do the Yellow Warnings say?
The first step is to get the category in Device Manage...
Click to expand...
Click to collapse
Well to say the least, it's mess
Anyhow, the category is "Other Devices - Nook SimpleTouch"
Driver Provider: Unkown
When I try reinstalling it says:
Windows found driver software for you device but encounterd an error while attempting to install it.
Android Composite ADB InterfaceThe system cannot find the file specifiedI have done the Advance Restart for Win 8 that disables the driver signatures and I still get this message.
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Renate NST said:
The modified .inf file has to be where it was originally.
That is, in the same directory as:
Code:
android_winusb.inf
i386\WdfCoInstaller01009.dll
i386\winusbcoinstaller2.dll
i386\WUDFUpdate_01009.dll
Click to expand...
Click to collapse
It's in the adt-bundle folder under ~sdk/extras/google/usb_driver. Should it be in the i386 folder?
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Renate, your questions helped me figure it out.
Yes all the files are where they are suppose to be in the same relative position that you outlined.
So i did this to get the "Have Disk Button"
I first did a right click "Update Driver software
1. Browse for driver on computer.
2. Clicked "let me pick from a list of device drivers"
3. A windows that says "Select your device type from the list below:"
4. List gives options includes Show all devices, ADB Interface, Android Device
5. I chose Android Device: It gave me a selection of devices and Nook Android Interface was there. I selected that and installed.
6. I then went to the command tutorial and typed in adb devices and I got the serial numbers.
I wrote this out for future refence for myself, and in the hopes it will help someone else.
thank you so much Renate! You were a huge help! I can't wait to start using your USB Host!
Renate NST said:
I just meant that you can't take android_winusb.inf from where it was, edit it, plunk it down somewhere else and try to run it from there.
I don't know about "adt-bundle".
Do those 4 files listed above appear together in the same relative positions?
When you try to update the driver keep saying NO until you get to the "Have disk" button.
Click to expand...
Click to collapse
I'm glad that worked.
I actually meant saying even more Nos until an actual "Have Disk" button appears.
Window caches the driver inf files and you could have had a bad one.