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.
Ok hopefully this helps someone. After flashing the amazing AOKP ROM (literally best ROM I've ever flashed...Holy stable batman) I noticed that on Win7 x86 or x64 that USB file transfer to/from SD card worked fine...as did Odin but Windows could not find a driver for my phone anymore. This creeped me out because this meant adb would not be able to connect. Running the adb devices command would not show anything.
I tried 3 different Win 7 machines and a WinXP machine all of them used to work but now they didn't I read the FAQ, I goggle searched xda and droid forums and tried everything, cables, switching USB ports, phone settings, dev settings, new usb drivers but, I could no longer get adb to connect.
So I started looking closely at the Samsung USB drivers I have on my machines which worked fine on stock ROMs, and a few other custom ROMs (not blaming AOKP no disrespect) and I found that the hardware id for my device changed and the device string wasn't referenced in any of the USB drivers files. So I forced the correct driver to install and it worked! So if that is all you need to know cool, if you some of you need the steps here they are:
I'm assuming you already have Samsung USB drivers and adb from the SDK installed (if not there's tons of info on this site to get both)
I'm also assuming you installed the USB drivers so they are in the default location, if you extracted a zip file or something you will need the path to the USB drivers
Last assumption... I tried 3 different versions of Samsung USB drivers and for each one the ssadadb2.inf that has the ADB driver was in the USB Drivers\16_Shrewsbury folder...If you don't find it there do a search in the USB Drivers folder and reference that location for step 13
Click Start button, then right-click Computer, then click Manage
Click Device Manager
Expand Other devices, you should see SCH-I500 with the yellow exclaimation point
Right-click it then click Update Driver Software
Click Browse my computer for driver software
Click Let me pick from a list of drivers
Scroll up, highlight Show All Devices, click Next
Click Have Disk
Click Browse
Browse to C:\Program Files\SAMSUNG\USB Drivers\16_Shrewsbury
Double-click ssadadb2.inf, click Open, Click OK
Highlight SAMSUNG Android Composite ADB Interface, click Next
You will get an "Update Driver Warning" saying cannot verify compatibility with your hardware, click Yes
You should see Windows has successfully updated your driver software, click Close
Back in device manager under ADB Interface you should see the driver name you just added....the entry under Other devices should be gone
Connect your data USB cable (not a charging only cable...if you can't tell the difference just be sure you used this cable for data before)
Open a cmd prompt (start>run>cmd enter if you didn't know)
browse to where you installed adb and type "adb devices"
You should see your device and a serial number again....back in business
Like I said no disrespect to AOKP I rock my B31 (soon to be 32) Pink Unicorn proudly This hopefully applies to anyone who had a hardware id change from any ROM.
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
I was unable to find help elsewhere, so I was recommended to come here. No rooting, hacking, reprogramming, or anything else. Just a basic connection problem.
I recently bought a new Solid-State hard drive, and re-installed Windows 7 on it. Everything is great, and it's fully updated.
My problem is that while my LG Optimus G E980 phone will charge via the USB cable, I can't "open" it in My Computer, to transfer pictures, music, etc.
I have tried downloading the driver from LG's Website (LGMobileDriver_WHQL_Ver_4.1.1), but when I run it, I get the following message:
"The Microsoft MTP driver is not found on your system. Please install Windows Media Format Feature Pack using Download Link for your media device to work correctly."
It then provided me with a link to download this. However, when I do that and run the update, I get told the update is not applicable to my computer.
Whether I try to install this update or not, it doesn't matter, because the driver installation tells me it was installed successfully. However, judging by the icon in my Taskbar with the red/white "X" and the fact that my phone still won't connect, it hasn't.
Yes, my phone is set up to ask me what I want to do when connected to the PC, and Media sync (MTP) is selected. Here's the kicker... remember, I have two hard drives. When I boot using the other hard drive, the phone connects with no problem. Same USB cable and port. Therefore, this is DEFINITELY software-related.
Is there something preventing this driver from installing? Why is the phone not installing the driver itself? Thoughts would be appreciated! Thanks.
Have you Manually installing the driver from Devices manager?
In the Device Manager locate your Android device. Then right-click on it and select "Update Driver Software".
Select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer".
Select "Show All Devices".
Press the "Have Disk" button.
Enter the path to the Google USB driver. Normally it is located in the following directory: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Select "Android ADB Interface" from the list of device types.
langithitam said:
Have you Manually installing the driver from Devices manager?
Enter the path to the Google USB driver. Normally it is located in the following directory: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Select "Android ADB Interface" from the list of device types.
Click to expand...
Click to collapse
Thanks for the quick reply.
I searched, and do not have a folder called "Android".
I did, however, find a folder called "LG United Mobile Drivers", however there are about 30 different drivers in there. I picked a few, including "Lgandadb" and "Lgnetandadb", but I get told "Windows encountered a problem", and "This device cannot start (Code 10)"
Anyone?
Ok, I'll try to put it another way. When you first connect an Android phone to a PC, drivers are installed automatically. I'm willing to bet there was an error when I installed them on my new hard drive.
Are the drivers already a part of Windows? If so, perhaps I need to do a Repair of Windows?
Are they located in an Auto-Run file on the phone, and maybe I need to re-run that program?
Perhaps there's something I need to delete or flag so that my phone thinks it's the "first time" again?
I just switched to a new Win 10x64 PC, and can't get the correct drivers to load, when I plug in my MOT Droid Mini.
I downloaded and installed "Motorola_Mobile_Drivers_v6.4.0_64bit.msi". Didn't seem to make much of a difference (though I guess it still good to have it installed).
When I plug my phone into my USB port, I notice in Device Manager, I get "Other devices" and under that is an "MTP" with a yellow "/!". I assume that is my phone.
I tried various ways of getting it to find the right driver, but it doesn't seem to be successful.
I read that a potential fix was to select "pick from list of device drivers on my computer", and do look for a category of "Portable Devices". I don't have that, or anything with a category name remotely like that. I did look at the category of "Android Devices", but those are for the ADB interface, and doesn't provide me access to my phone's memory.
Yes, I have my phone set for "Connect as a Media Device", aka MTP. That matches the "MTP" device I mentioned above.
When I open up the newly installed "Motorola Device Manager", all it seems to want to do is check if I need newer drivers, finds I don't need such, and automatically closes.
Does anyone have any ideas what to do?