Currently I'm trying this guide:
Nook Tablet "One Click Root" + gapps ADB script
but I've been trying various guides all day. The drivers are there, debugging enabled, auto mount disabled, robot in the bottom corner but when I run ADB Devices, no dice. Anyone have any clues what the problem could be or atleast anyone else having this problem? At first I thought it might be because I was using a different USB cord but it still doesn't work even with the Nook cord
The problem you describe is almost guaranteed to be a problem on your computer and the driver installation.
For the folks here to help, they will need to know platform (PC or mac) and version of operating system.
If Windows, they will need to know how the device appears to Device manager. If it shows up as a disk drive - you will have to disconnect from the Nook side. ADB Composite should be good.
For either platform, confirm that adb_usb.ini is in the right place and modified correctly.
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
You need to have your nook tablet unplugged when you run that then you would see nook tablet in the device manager when you plug it back in.
Indirect said:
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
Click to expand...
Click to collapse
"Cannot find the path specified." But I can locate the file myself in that directory??
I'm running Windows 7 64-bit, device shows up as android phone>androud ADB interface.
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Check, still nothing in ADB, i did restart the server too. To be clear, the .ini file only has the "0x2080" line in it now, nothing else. I'm assuming that's ok because the other stuff was commented out anyway, am I right?
(thanks for your help! )
1) look in device manager now though, you need to install the drivers.
I still see it listed under android phone > android ADB interface and not mass storage or anything like that, you think that's still the problem though?
*Edit*
SUCCESS!! I uninstalled the "Android ADB Interface" and "Android Composite ADB Interface" appeared in its place!!(??) Whatever happened the device show up now. Thanks for the help and keep up the good work Indirect!
Indirect said:
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Click to expand...
Click to collapse
I was having problems seeing the Nook Tablet in adb devices, but this fixed it for me.
I was having the same issue for a bit, restarted my nook and it worked haha.
Sent from my BNTV250 using xda premium
This worked for me. Hopefully it helps.
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.
Now unplug and replug your NT, and you should now see an Android Composite device with the "!" next to it. You should now be able to install the custom drivers described in the other posts.
Essentially it seems windows is trying to "help" you by guessing at the drivers you want to use.
If this doesn't work, you can try to remove ALL android devices using the USBDeview Application that you can find http://www.androidsim.net/2009/08/how-to-1-how-to-install-usb-driver-on.html
I used USBDeview for the removal part just because I had a Kindle fire, HTC device, samsung device, all installed and I think they were fighting a little bit. I now have results from adb devices, and dare I say ROOT!?!?!
Hope this helps some of you!
Good post - Windows Vista especially, and Windows 7 somewhat, really think they know better than the user when it comes to drivers. Especially unsigned drivers in preference to signed ones...
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
tsubus said:
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
Click to expand...
Click to collapse
I just joined the forum to thank you! I spent hours looking for a solution and yours worked!
brices21 said:
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.!
Click to expand...
Click to collapse
Well I am stumped here, seriously. I can't get rid of the above mentioned 2 instances of "B&N NOOK Tablet USB Device" no matter what I do. Auto mount is off on the device and the device installation setting is already set to "No, let me choose what to do." Yet every time I plug the NT in- the computer kindly tells me it's "ready for use" and those two "B&N NOOK Tablet USB Device" listings are back. At this point I'm not sure I'm ever gonna be able to get the device to show up under ADB. The computer just won't seem to let it.
Any advice anyone might on this would be greatly, greatly appreciated.
maybe try what Indirect did here: http://forum.xda-developers.com/showthread.php?t=1363652
The website is below what I did to completely disable Windows from installing the Nook drivers every time it is plugged in. I also had the "Never install driver software from Windows Update" checked from Brices21's post but the drivers would still install everytime it is plugged in.
xxxx = http - still a noob, can't post links
yyy = www
xxxx://yyy.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
I never actually installed the USB drivers that indirect provided, but "adb devices" still detected the NT when plugged in.
This was my whole process to get "adb devices" to detect the NT:
With the NT plugged in and device manager detecting the 2 Nook devices as drives and 2 Nook devices in "other devices" and with automount disabled and USB debugging enabled
I also ran the runmefirst.bat at some point in time previously, so the necessary files were created already
***** Pulled this from the website above******
* Go to Start–>Search type in gpedit.msc
* Click the file to open the Local Group Policy Editor and show Windows who is in control!!
* You want to go here: Computer Configuration->Administrative Templates->System->Device Installation. Click on the subfolder Device Installation on the left and on the right side you will see the possible restrictions.
* Right Click on Prevent Installation of Devices not described by other policy settings and edit this option, set it on ENABLED.
*************************************
From here the website says to reboot and set the option back to default. I did not reboot or set the option back.
* Going back into device manager, I uninstalled the drivers for the 2 Nook drive devices.
* Unplugged the NT
* Plugged the NT back in
Then I got the B&N NOOK Tablet USB Device with the broken symbol under "Other devices" in Device Manager
* Open cmd and run "abd devices" from the ntroot directory
The service should start and list the NT device as a bunch of numbers.
* From here you can run NookandZergy.bat to root the NT.
After rooting you can set the options in the gpedit.msc back to defaults.
I also tried installing the Indirect provided drivers as the USB mass storage device. Windows then detected the device as an Android ADB Composite device but "adb devices" from cmd prompt would not detect the NT. I ended up removing all of the drivers and repeating my steps to get "adb devices" to detect it again.
Hope this helps! It may not be the best solution but it was a workaround for me to get the NT rooted.
****Update*****
Just got home and tried to install the drivers and it worked this time. I was able to see the NT with "adb devices"
With the gpedit.msc edit intact, I plugged in the NT and Windows detected 2 broken Nook devices under "other devices" and a mass storage device under USB controllers.
* I uninstalled the driver for the mass storage device
* set the gpedit.msc back to "not configured"
* unplugged NT
* made sure debug mode was set and automount disabled
* plugged NT back in
Device manager showed a Mass Storage device under "Other devices"
* Update drivers for that device with the Indirect usb driver
* ran "adb devices" in cmd prompt and NT is detected.
So if there's anything to take away from my post...hopefully you can use the gpedit.msc to completely disable the autoloading of drivers.
Drivers Fixed!
Rooted! Got past driver issues (Android Composite ADB Interface appeared in Device Manager, adb still couldn't detect Nook). Thanks to all who have worked so many hours on this.
Here's what worked for me (using Windows XP 32 bit):
1. make sure "adb_ini" file contains "0x2080" and is located at "%USERPROFILE%\.android"
2. I had to manually edit my "path=" environment variable to include the above location - both in Control Panel->System->Advanced->Environment Variables and in cmd window.
3. carefully followed instructions on proper installation of drivers for "Android Composite ADB Interface". At this point, cmd window use of adb was able to detect Nook (as well as runmefirst.bat).
4. Continued with root process (i.e. NookandZergy.bat)
Hope this helps anyone still having driver issues.
Never had this issue using the trick mac method.
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
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.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
Hello everybody!
I have a problem related to connectivity between my desktop (Windows) and tablet (Android 4.1). I bought a new device (Colorovo City Tab Vision 7) and now I want to use it for testing of my applications, because emulation of android is very slow on my computer, although I forced it to create snapshot every run.
I have downloaded SDK with Google drivers and also some unofficial drivers I found on web. When I connect my device, it first appears 'Other device' (label is CTVision7) and it's marked as unknown. I tried to install drivers (Google) for it, but windows said that they aren't suitable for my device, as it's not able to find them in specified directory.
After these attempts I tried unofficial drivers. Their installation worked and now my device appears as Android phone, what seems to be good.
But when I run
Code:
adb devices
or launch application in eclipse, there's not avaible device.
I have turned USB debugging on, so it should work.
Am I missing some step to make my device avaible for debugging, or are my drivers wrong? Is there any way to get drivers which surely work?
Hello,
I've a problem since I changed my Rom : I take the CyanogenMod 10.3 for my Alcatel OT995, it works fine on my device, but I can't use adb command line neither other features using adb.exe ! I can only access to storage mass device, so I think I have a problem with the USB drivers which connect ADB command to my phone.
I can add that before I've installed this Rom on the device, I've installed many drivers on the PC : Firstely I installed the owner's driver provided by Alcatel in the AlcatelAndroidManager.exe package, secondly I installed the Google USB drivers provided because I'm using Android Virtual Devices (AVD Manager) to do some developping works.
I used to launch adb with "adb start-server" so it's still working, I don't obtain any device in the list with "adb devices", why don't I get it ?
I've realized some cleaning actions : I uninstalled the USB drivers of Alcatel's software, I uninstall the Google USB driver , to finish I reboot the PC but it don't changed anything !
Moreover, I tryed to apply this (well explained) post without any success :http://forum.xda-developers.com/google-nexus-5/help/diagnosing-usb-driver-adb-issues-windows-t2514396 ; I see finely in the list, I can't find "Android devices" category, neither "Usb Adb" entry... so my device is not recognized in the "Settings Panel". However the storage mass device appears as a volume named "F:".
Help me please.
The post #4 published by Incubus 26jc saved me at http://forum.xda-developers.com/showthread.php?t=735937
Anybody else got problems with connecting to the PC with the USB cable?
What "problems" are you having?
The Windows Explorer does not start, though there is the sound when connecting the USB. Tried uninstalling the driver and letting the system reinstall upon connecting, but still cannot see Nexus 9 in Windows explorer. In Linux get the the notification and clicking on the "open with File Manager" gives a quick error message - too quick to read. So I am wondering if anyone got this problem??
Sent from my Nexus 9 using Tapatalk
Same here
I updated my SDK files, but that didn't seem to work either. It does show up as a camera when I change from MTP, so I just started sideloading apps, files, and books to the picture folder, then using a file explorer to move them to the correct folder.
+chuckie59 So I am not alone with this problem! Have used AirDroid to copy things over.
Sent from my Nexus 9 using Tapatalk
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Same for me. Only ptp working. Google USB ADB drivers instaled
mkygod said:
Mine was able to be detected at my work computer (windows 2000 in MTP mode), but it shows up as "Android" in Explorer instead of a drive letter like I'm used to with my phone.
Click to expand...
Click to collapse
You'll never get it to show up as a driver letter. Android gave up on mass storage a couple of versions ago.
Sent from my Nexus 9 using XDA Free mobile app
If you are on W8.1 then you may have the "ACER Composite ADB Interface" - A Microsoft upgrade fault.
A search for "ACER Composite ADB Interface remove error delete" should give plenty of hits. Here's the first post from http://forums.androidcentral.com/google-nexus-7-tablet-2012/362325-nexus-7-not-recognized-computer-2.html :
Would you happen to know if any Acer drivers are installed on your computer? Here recently there was a Windows Update that installed the wrong driver and made it so that I had the exact same problems as you're having. Here's how I fixed it.
Go To> Control Panel>Hardware and Devices>Device Manager. In Device manager look for something along the lines of "ACER Composite ADB Interface", at least in my case I had the wrong ADB interface installed. You'll know if you have the wrong drivers if you go to Devices and Printers and right click your Nexus 7 and go to it's properties. It should be under the hardware tab where it lists it. If it doesn't just say Nexus 7 then follow these instructions. Once you find it in the Device Manager (once again in my case it was the ACER Composite ADB Interface causing the issue) right click and and uninstall it. There should be a dialogue box that pops up right after which will ask you if you want to delete the drivers. Check this box and proceed with the uninstall. After successfully uninstalling the drivers plug in or unlplug and plug back in your Nexus 7. It should show up now with the correct drivers installed.
Thanks, but I am on Windows 7. Driver is ClockworkMod Ver 7.0.0.1 dated 2012-08-27, which Windows reports as up to date (?). Works for PTP but not MTP.
I have had problems with other devices including the nexus 5 and nexus 10 to connect over mtp. Previously i used the nexus root toolkit which has some wizard to guide you to install proper drivers for mtp and adb. The toolkit is yet to support nexus 9 but you can still use the wizard to uninstall the old drivers and reinstall correct ones
Updating sdk. Uninstall and installing again driver did the trick for me
SORTED!! (sort of) Updated sdk and uninstalled and installed the driver again, but it did not do the trick for me. Gave up on Win7.
Instead had a go on XP. Initially everything the same. Noticed two choices of compatible hardware given: "Google Nexus ADB Interface" (the one I had installed already) and "USB Composite Device". Tried the latter one, and yes it did install. In the device manager it turns up as "Portable Device/Nexus 9" (and not as "Android Phone/Google Nexus ADB Interface" as before).
In Windows Explorer it is shown as "Nexus 9/Internal storage" with all the directories, and actually when inserting the USB I do get auto start. By the way, was having the USB debugging disabled. The driver is Microsoft dated 2006-02-22 version 5.2.5326.4762 - which is not what I would have expected. But it works!
Will try to get something similar to work on Windows 7
SORTED! Yes also Win 7 - and it was easy. Uninstalled the driver, plugged in the USB and it installed! Also got the auto start to choose action. It now turns up as "Portable Devices/Nexus 9" in the device manager and as "Nexus 9/Internal storage/etc" in Windows Explorer. The driver is now Microsoft ver 6.1.7600.16385 dated 2006-06-21. Strange. As long as it is working!