Database Users

[Q] ADB Driver not installing

Hello everyone,
So I've installed ACER's adb drivers, but when I connect the tablet to my computer it shows up as an MTP device. I've tried updating the driver and manually browsing to the driver's location, but windows says that driver is not compatible with my device? BTW: I am running a fresh install of Windows 7 64-bit.
Any tips would be appreciated.
Thanks!

I'm having the same issue. It seems like everyone else's Iconia "just worked" with adb.
I've tried installing the acer drivers. It puts a folder in my Program Files directory...but I don't see what I'm supposed to do there. There's "EUUDriverInstaller" but when I click on it nothing (seems to) happens.
When I plug the device in it uses some generic Microsoft driver to show the device contents but composite adb doesn't show up at all like it does for my Droid.
I've reboot several times on both device and laptop. I've uninstalled / reinstalled the application that made that driver directory.
I opened an application in the driver directory under the x64 folder and it opened up the windows driver installer and installed some drivers...but still no composite adb when I plug it in.
It was called "dpinst" and installed:
Linux Developer Community Net
Acer, Inc (androidusb) USB
Google, Inc (WindUSB) USB
then a couple others about a modem and ports
It is on usb debugging and I've toggled it on and off.
It's running 3.1 stock and I'm on x64 Windows 7
Both command prompt adb devices is empty under "List of devices attached" and Eclipse devices is empty.
My sdk is fully updated.
Curiously it appears Acer hides the driver if you specify Honeycomb 3.1

If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.

apapousek said:
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
Click to expand...
Click to collapse
I appreciate the suggestion, but I'd rather not install another partition just to adb connect this tablet.
Some additional differences I've noticed.
It seems like the tablet is going straight to mounting if that means anything. Connecting my Droid doesn't bring up the Autoplay menu while connecting the tablet automatically asks me how I want to access the data in the autoplay menu. It does *say* usb debugging is on, but no "ACER composite ADB interface" appears in my device manager.
Edit:
It seems like my situation is comparable to this guy in regards to the device just being treated like a flash drive. forum.xda-developers.com/showthread.php?t=734139 He says the rom was the problem...but I can't see why this stock rom should have an issue.

I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.

I'm too on Windows 7 64bits and for the drivers I go to http://support.acer.com/us/en/product/default.aspx
If you want I have re-upload the drivers on my 4shared
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English

bpivk said:
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
Click to expand...
Click to collapse
I don't seem to have another icon. I have this one referring to the Iconia Tab, but when I right click on it it just treats it like a flash drive.
I can't link the picture yet (need to have 8 posts), but there is on "Acer Iconia Tab" in Devices and Printers, but there's no yellow exclaimation mark and when I right click it it just has the option to browse files, it treats it like a flash drive.
It's under "Unspecified"
EVEALEX62 said:
I'm too on Windows 7 64bits and for the drivers I go to
EDIT : [Had to remove URLS to quote]
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
Click to expand...
Click to collapse
I've downloaded those drivers, unzipping them, and ran the setup several times =/.
EDIT:
I feel like a tool, someone at stack overflow suggested I switch to a different port (not just unplugging / re-plugging it into the same one), I guess that finally told windows to reanalyze it. Should have figured it would have been something silly for such a basic problem, shame on me for keeping all my other ports full.
Thanks for the help everyone!

Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...

EVEALEX62 said:
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
Click to expand...
Click to collapse
That worked! Thanks.

Figured it out
Hey guys,
Thanks for all of your suggestions, but none of them worked. I ended up having to disable automatic driver installation, then went into Windows\System32\DriverStore\FileRepository and deleted the folders corresponding to the drivers that windows kept on insisting I wanted. After that everything worked great!

[Solved] [Q] ADB over USB on 1.1

Has anyone gotten ADB over USB working with the NST 1.1 firmware? There seem to be guides all over the place, but they're either for the 1.0 firmware or for the original Nook, and every set of instructions I've followed doesn't do anything for me.
I'm trying to figure out why when I connect the NST to my computer via USB, adb can't see the device, no matter what I do. Looking at the ramdisk and the init.rc, it seems I have everything set up correctly. Of course, I could just use adb wireless that came with touchnooter, but I'd really like to get the USB version working again.
So, has anyone had any luck?

Not sure what ramdisk you're using but these are the ones used by most rooting methods around here.
The USB one works just fine, but I must say that getting the drivers set up on Windows 7 was a bit of a pita..
After trying several pre-packaged drivers I ended up editing the inf file in the android usb driver pack manually and got it working both at home and at work now, no problems.

Runs good on 1.1. here. I also tried a lot of drivers and the working one only after 3 installs. I think it was the driver of the forum here (but Im not sure anymore after that mess).

Gogolo2 said:
Runs good on 1.1. here. I also tried a lot of drivers and the working one only after 3 installs. I think it was the driver of the forum here (but Im not sure anymore after that mess).
Click to expand...
Click to collapse
Well, it's important to know that all those driver packages are actually based on the one you get with the Android SDK.
So people should save themselves the hassle and just get that one, and edit the android_winusb.inf manually.
Just add this to both the [Google.NTx86] and [Google.NTamd64] sections:
Code:
;B&N Nook Simple Touch
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0003&MI_01
---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
Ah, and ofc you need to add/edit %USER/.android/adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080

Thanks for the replies folks. Good to know that those ramdisks work well with 1.1 (those are the ones I've been using too)...so I must be doing something wrong, or my computer must be set up incorrectly. I'm on a Mac, so AFAIK, I don't need to install any extra usb drivers or anything.
I can connect fine to my phone with adb over usb, so I'm not sure why the nook is failing.

michaelwill said:
Thanks for the replies folks. Good to know that those ramdisks work well with 1.1 (those are the ones I've been using too)...so I must be doing something wrong, or my computer must be set up incorrectly. I'm on a Mac, so AFAIK, I don't need to install any extra usb drivers or anything.
I can connect fine to my phone with adb over usb, so I'm not sure why the nook is failing.
Click to expand...
Click to collapse
Well the ramdisks are nothing but a copy of the 1.1.0 ramdisk with adb enabled.
I have zero experience with OSx, but you might want to look at the Linux adb threads..

Yeah - there must be something wrong with my machine. I just reverted to the 1.0 version of the firmware, and went through the rooting procedure again, but my machine still can't see the device over ADB. I swear I had this working some weeks ago.
By the way, when you guys plug in the nook, and it shows the "USB mode" screen, do you first eject it from your PC, and then ADB works? Or does ADB work for you regardless of whether the NOOK drive is ejected or not?

Answering my own question here:
It turned out to be a fairly trivial solution - here's to not checking over your setup carefully enough.
It all came down to adding 0x2080 (the nook touch vendor id - which happens to be the same as the nook color vendor id - you can verify by using lsusb on linux) to the ~/.android/adb_usb.ini file, which basically just tells adb to look at additional vendor ids. This is stated clearly in the nook color docs, and I could have sworn that I did that hours ago, but when I re-looked at the file, I found mine was blank . As soon as I added 0x2080 back, everything started working perfectly.
Note, this is necessary for both mac and linux.
And, it doesn't matter if your NST is on the "Usb mode" screen or not; I got it to work both ways.

MTP on Ubuntu/Mint/Debian

With many devices not supporting mass storage anymore Android seemed to have moved from mass storage to PTP and MTP
With Windows supporting MTP by default and Mac OSX with an application there isn't any native support in Linux.
There are a few work arounds like gMTP but that didn't really work for me.
There also is another work around that requires you to edit some files.
To make it easier for others I wrote a little bash script, that does most for you.
Step 1 : sudo apt-get install mtp-tools mtpfs
Step 2 : Plugin your device
Step 3 : Open up a terminal
Step 4 : Type in : “mtp-detect”
Step 5 : Write the PID and VID down, you will need this later
Step 6 : disconnect your device
Step 7 : Download the script and execute it by sudo ./mtp (don't forget to make it an executable first)
Step 8: Follow the instructions on screen and after it's done reboot and plugin your device
Step 9: Use the command "android-connect" to mount your device and "android-disconnect" to dismount
It's not much, but I hope it helped someone.
Please let me know if it worked for your device/distro.
Original post
Tested and working on the P3110 and P5110.
EDIT 1:
(First) time mount can take up to 1-2 minutes, have had where it would mount in a few seconds, others half a minute. Be patient.

mussieonlinux said:
With many devices not supporting mass storage anymore Android seemed to have moved from mass storage to PTP and MTP
Tested and working on the P3110 and P5110.
Click to expand...
Click to collapse
Thanks for this. I think I have tried all this before and it has not worked, but will try again. A few things come to mind though. First, I think you have to turn USB debugging off, right? There is another thread where several of us are able to see the tablet, but not really get any files. Also there is a way to get the tablet to share PTP or MTP and that changes things too (PTP lets me see the top level but no subdirectories).
Will report back if this works or not.

I think USB debugging has to be on, at least for my phone. Mine is always on on all my devices.
Yeah you can see it in the file manager (1 for each SD card) with MTP but you can't access the files.
I am not sure about the PTP.. However for the MTP I just made a new folder in on my other SD card named extSD since MTP shows all directories of both sdcards in one directory.

mussieonlinux said:
I think USB debugging has to be on, at least for my phone. Mine is always on on all my devices.
Yeah you can see it in the file manager (1 for each SD card) with MTP but you can't access the files.
I am not sure about the PTP.. However for the MTP I just made a new folder in on my other SD card named extSD since MTP shows all directories of both sdcards in one directory.
Click to expand...
Click to collapse
Nope doesn't work with or without USB debug. I think the issue may be due to some problem with mtp-tools on 64 bit Linux. Are you running 32?
The mtpfs mounts but any attempt to list the mounted directory just hangs.

I am using 64bit, did you do the reboot and android-connect? If you are using nautilus you wont see your device under "Devices". You will see it above your filesystem.
Can you tell me what isn't working?

mussieonlinux said:
I am using 64bit, did you do the reboot and android-connect? If you are using nautilus you wont see your device under "Devices". You will see it above your filesystem.
Can you tell me what isn't working?
Click to expand...
Click to collapse
Well I'm using Kubuntu so no Nautilus. And I'm just looking at the mount point. My udev rules already have an entry for the mtd device. I also grabbed the latest libmtd and built it from source.
The fuse mount seems to work but any ls on the mount point just hangs forever.
Very strange.

At times like this I miss ubuntu
On my Arch (+XFCE), I use gMTP (uses mtpfs ofcourse). Most of the times it works, and then there are times when it is a pain in the a##. Gets stuck, does not respond, fails to copy what not.
I find the only reliable way is using adb.
Gosh! I push and pull everytime! :silly:

yeah, after a couple of days I found it not very stable at all, so I too switched over to ADB, it's not the fastest method. But we gotta get around, don't we?

I am also waiting for a permanent fix... Just switched back to Ubuntu from Windows 8 Preview, and I love it!!!
The only issue I have at the moment is the fact that I cannot connect directly to the PC from the Tab, although transfer speeds are better by removing the memory card and inserting it into the computer directly. Would be nice to use Rhythmbox to manage my MP3s.
I've tried a few solutions and nothing seems to work fully. I'll give the ideas mentioned above a try.

I have found my peace finally with qtADB.
By far the fastest, and most efficient app for this job.
qtadb[dot]wordpress[dot]com

Worked on my Galaxy S2 (i9100G) with cm10 nightly TY!

Worked only once! i get this...

Hello, this worked greatly on my ubuntu machine. Would this work on an ArchLinux headless PC? I'm willing to try it out if this doesn't mess anything up.

I can confirm this does not work on virtual box not sure on vmware as i dont have it so idk.

[email protected]:~$ android-connect
fuse: bad mount point `/media/GT-P3100': Transport endpoint is not connected
[email protected]:~$
As you can see above, i tried this for P3100. Can someone tell me what am i doing wrong here? I really want to handle my device from Ubuntu 12.04.

hi there,
in newer kernel - at this thime for example debain testing jessie - is kio-mtp implemented. this compinent load your nexus 4 mtp device autmotically like in windows. can access device via filemenager without doing steps in console before. in long time support distribution - example debian stable wheezy - this is not implemented yet. you can compile own your own to get this working
kio-mtp is for kde
gnome-vfs with mtp is for gnome

Works on Kali Linux with 3.14 kernel - HTC One with 4.4.3. Thanks a lot

Guide: adb on Nook HD/HD+ with CM10.1 emmc

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.

[NST/G] USB debugging issue

What fun! Windows 10 and the NST
I find that I cannot negotiate ADB access via USB any longer. I don't know when that started, but it looks like maybe sometime in June. These events are displayed in the Device Manager when accessing "Portable Devices":
Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_B&N&PROD_NOOK_SIMPLETOUCH&REV_0100#7&22272E47&0&3012440020143004&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0.
Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} was not migrated due to partial or ambiguous match.
Last Device Instance Id: SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#3014760074133009&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Class Guid: {eec5ad98-8080-425f-922a-dabf3de3f69a}
Location Path:
Migration Rank: 0xF000FFFF0000F102
Present: false
Status: 0xC0000719
Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} requires further installation.
It's not beyond belief that the spate of major updates to Windows 10 recently trashed my ability to access the device via ADB/USB. The question is: how to fix it?
On the NST I have the following:
service.adb.tcp.port -1
persist.adb.tcp.port 0

All that stuff indicates that the NST is presenting as UMS.
Have you used UsbView.exe to see what interfaces are being presented?
Have you looked at sys.usb.config, sys.usb.config?
That stuff with adb.tcp is only for ADB over TCP (WiFi).

Renate said:
Have you used UsbView.exe to see what interfaces are being presented?
Click to expand...
Click to collapse
Mmm....is that in your signature (NOT)?
Renate said:
Have you looked at sys.usb.config, sys.usb.config?
Click to expand...
Click to collapse
And this is where?
I should have added that none of my three NST/G devices is connecting properly now (other than as USB file transfer devices) whereas all were formerly able to negotiate USB debugging and ADB.

UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)

Renate said:
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Click to expand...
Click to collapse
This is the result from omaplink (green dot for ADB, black for UMS):
Code:
Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)
In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.
And I've attached a screencap from usbview.

Well, OmapLink/ImxLink found your rooted device.
You do have only one Android plugged in?
What part of ADB is not working?
What version adb.exe are you using?
If the version is stone age it goes by VID/PID and it doesn't know about B&N.
Code:
C:\>adb version
Android Debug Bridge version 1.0.41
C:\>adb devices
12345678
Version is not that critical, but should at least be in the high 30's.
(For UsbView you want to click on the device so that you see interesting things in the right panel. But we're past that step.)

Wait, are you talking about UMS not working, not ADB?
Oh, don't tell me that you use UMS?
The NST presents two drives but there may not be anything mounted.
Run Disk Manager (diskmgmt.msc) and see if there are drive letters but nothing inside them.

Renate said:
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Click to expand...
Click to collapse
This is the result from omaplink (green dot for ADB, black for UMS):
Code:
Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)
In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.
And I've attached a screencap from usbview.
Renate said:
Wait, are you talking about UMS not working, not ADB?
Oh, don't tell me that you use UMS?
The NST presents two drives but there may not be anything mounted.
Run Disk Manager (diskmgmt.msc) and see if there are drive letters but nothing inside them.
Click to expand...
Click to collapse
Unless I am transferring a library book with ADE I like to keep UMS turned off since it locks you out of interacting with the screen while debugging...which now isn't happening for some unknown reason.
I try to do most file transfers wirelessly to save wear and tear on the USB jack.
So, yes, I am talking about ADB. "Device not found" is all I get now. I'll check on the version later today but I don't see why a version which was working just fine before should suddenly stop. Unless its Windows' fault.

nmyshkin said:
"Device not found" is all I get now.
Click to expand...
Click to collapse
Ah, ok.
It's definitely a problem with your adb.exe
OmapLink/ImxLink can find your device, connect and even do shell commands (id).
Those programs, unlike AdbSync, do not go through the ADB port 5037 of adb.exe like a normal ADB client does.
If you actually have adb.exe connected OmapLink/ImxLink won't be able to connect to the already connected device.
So this all means tht your WIndows drivers are fine.
You might have had a few copies of adb.exe and one of them got deleted or the PATH changed or a backup restored the wrong one or...
Also, there was that old C:\Users\Person\.android\usb_adb.ini file which was used by old versions of adb.exe
But you don't want/need that anymore, so forget that I mentioned it!

Renate said:
Ah, ok.
It's definitely a problem with your adb.exe
OmapLink/ImxLink can find your device, connect and even do shell commands (id).
Those programs, unlike AdbSync, do not go through the ADB port 5037 of adb.exe like a normal ADB client does.
If you actually have adb.exe connected OmapLink/ImxLink won't be able to connect to the already connected device.
So this all means tht your WIndows drivers are fine.
You might have had a few copies of adb.exe and one of them got deleted or the PATH changed or a backup restored the wrong one or...
Also, there was that old C:\Users\Person\.android\usb_adb.ini file which was used by old versions of adb.exe
But you don't want/need that anymore, so forget that I mentioned it!
Click to expand...
Click to collapse
ADB version is 1.0.31 (Minimal ADB and Fastboot)
Just to see, I connected up my regular non-Nook tablet and ADB saw the device right away. So the issue is definitely with the NST or the interface of the NST with Windows.
I actually do have that usb_adb.ini file, but again, why work with everything else and "suddenly" stop working with the NST?
When UMS is turned off, I do see the two "empty" drives (internal and sdcard) in Windows when I connect via USB.

Marshmallow came out in October 2, 2015.
That had ADB version 1.0.32
That was the first public release that eliminated vendor white-listing that was changed in November 21, 2014.
I could tell you how to fix the adb_usb.ini, but you really should just update a half decade or so.

Renate said:
Marshmallow came out in October 2, 2015.
That had ADB version 1.0.32
That was the first public release that eliminated vendor white-listing that was changed in November 21, 2014.
I could tell you how to fix the adb_usb.ini, but you really should just update a half decade or so.
Click to expand...
Click to collapse
Huh.
So I updated Minimal ADB and Fastboot to v.1.43 which is ADB version 1.0.39. And it worked right away. I still don't see why the previous version just stopped working with the NST. Like so much else in life, it makes no sense.
Anyway now I have another issue, for this version came with a genuine Windows installer and my previous version was a "dump into the folder of your choice and set up the paths". I'm wondering if it's safe to just delete that entire folder now (probably have to clean up the path statement too...). Ugh.

Once upon a time, adb.exe and fastboot.exe were completely standalone.
Now they require AdbWinApi.dll, AdbWinUsbApi.dll
They also require:
Code:
api-ms-win-crt-private-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-utility-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-multibyte-l1-1-0.dll
But these should already be found in the Windows "downlevel" directories.
There's no need to be adding to PATH for every little thing.
If you are invoking adb/fastboot from the command line, you might consider using doskey:
Regedit HKCU\Software\Microsoft\Command Processor AutoRun=\wherever\my-autorun.bat
Code:
doskey /macrofile=\wherever\my-aliases.txt
Code:
adb=C:\some-sort-of-path\adb.exe $*
fastboot=C:\some-sort-of-path\fastboot.exe $*
Edit: I forgot the arguments ($*).
If you are invoking adb/fastboot from a bat or makefile just put the full path in some define.