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.
Hello!
I have gone through a lot of threads before posting this here. I am facing an issue with Android device debugging - the device isn't getting listed on Devices tab in Eclipse IDE. (Please refer to screenshots) (To get 'Devices' tab 'Windows -> Show view -> Devices'). So while starting to debug there is no way to choose a device as device listing shows blank. The strange thing is that it used to work fine before and under windows explorer I can browse the files.
I am using Windows Vista Home premium, 32-bit OS
What all I have tried:
In phone:
1. USB debugging is enabled in phone under 'Settings-> Developer options'
2. Disabled and enabled USB debugging
3. Restarted the phone
In Eclipse:
1. Under 'Debug configurations->Target(tab)', 'Always prompt to pick device' is selected. It prompts but doesn't show any device on the device list!
2. Tried resting ADB under Devices tab. (To get 'Devices' tab 'Windows -> Show view -> Devices'
3. Reinstalled latest Android SDK along with ADB
4. Installed Eclipse Juno
In windows CMD under /platform-tools/ directory where the Android SDK Tools is installed, ran the following commands without getting any positive outcome:
Shut down Eclipse, unplugged the device and tried running:
adb kill-server
adb start-server
Plugged it back in and ran
adb devices
Mobile device details:
Model = Galaxy S2 GT-i9100
Rooted = yes
OS Ver. = 4.0.3
Kernel ver. = 3.0.15
[email protected] #k3-27b
Other details can be found in the attached screenshot.
Eclipse version: Indigo Service Release 1
Build id: 20110916-0149
Any help will be appreciated,
Thanks,
Ambar!
Debugging Samsung in Eclipse...
ambar_bs said:
Hello!
I have gone through a lot of threads before posting this here. I am facing an issue with Android device debugging - the device isn't getting listed on Devices tab in Eclipse IDE. (Please refer to screenshots) (To get 'Devices' tab 'Windows -> Show view -> Devices'). So while starting to debug there is no way to choose a device as device listing shows blank. The strange thing is that it used to work fine before and under windows explorer I can browse the files.
Ambar!
Click to expand...
Click to collapse
I ran into a similar problem this evening, though I am not sure if you are having the same issue. In my case eclipse would not recognize my Samsung i9000m when plugged in. This surprised me as I have debugged with this phone in the past but I have recently loaded Cyanogenmod 10.1 on it.
I checked Windows Device Manager (Control Panel) and noted that for some reason, Device Manager was showing an error for my i9000m, no driver had been assigned. I have installed the Samsung drivers in the past and they are still installed but I suspect some difference in naming of the device in CM10.1 which confused Device manager. I selected "Update Driver" option in Properties for the device and then selected the option that had windows go search for the correct driver. To my surprise, Windows 7-64 bit found and installed what appears to be a Generic Android Device named "Android Composite ADB Device". I am not sure if Vista will be the same or if this is even the same problem you are having, but check your Device Manager to see if errors are flagged...
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
Hi guys, I've been tearing my hair out for the past 24hrs trying to get ADB to communicate with my devices (Amazon Fire tablet + Nexus 5x).
I've installed ADB and drivers for my devices. They currently show up as Android Device > Google Nexus ADB Interface (ClockworkMod driver installed) and Android Device > Android Composite ADB Interface (Amazon.com driver installed).
I have enabled ADB on my Amazon Fire tablet (5th Gen - 5.1.3) and USB debugging on my Nexus 5x.
When I run ADB, all it sees is my Fire tablet but says "unauthorized" next to it.
On both devices, when plugged into the computer via USB, I get no message about enabling the computer to access the device etc. They just sit there, charging with "USB Debugging Connected" on both devices.
Could someone point me in the right direction to get ADB communicating properly with both devices? I originally wanted to use it to root my Fire Tablet to load a different OS on to it, so I used my Nexus 5x to see if that could communicate with ADB but it appears that neither do.... properly anyway.
Another flag that I'm wondering is that in Device Manager, I do have an exclamation mark next to a USB controller - I've found drivers for it (Renesas USB 3.0 Host Controller) - but it came up with an error saying the device cannot start (code 10) - I don't think this is anything to do with my issue as the drivers are installed correctly it appears for the Android devices.
Thanks a lot in advance.
I've done it! I had to delete adbkey from .android folder on my PC - god knows why! all fixed though. yay.
Anyone managed to find working USB drivers and get their Mate 20 Pro showing up in ADB? If so could you share the drivers as I can't find any.
Edit: for some reason USB debugging turned itself off. It's showing up now.
@Kipp162 did you finally manage to run adb with the HUAWEI Mate 20 Pro? I was not able to do so. All other devices have been no problem but it seems that the HUAWEI Mate 20 Pro needs an extra trick?!
The thing that finally worked for me was installing HiSuite.
cant see device
saturnspike said:
The thing that finally worked for me was installing HiSuite.
Click to expand...
Click to collapse
Hi, how exactly ? I have installed HiSuite, but anyway "adb devices" cant see any device.
(have mate20pro with latest os and emui)
[email protected]:/home/mato# adb kill-server
[email protected]:/home/mato# adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/home/mato# adb devices -l
List of devices attached
[email protected]:/home/mato#
matolog said:
Hi, how exactly ? I have installed HiSuite, but anyway "adb devices" cant see any device.
(have mate20pro with latest os and emui)
[email protected]:/home/mato# adb kill-server
[email protected]:/home/mato# adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/home/mato# adb devices -l
List of devices attached
[email protected]:/home/mato#
Click to expand...
Click to collapse
I have to make sure usb debugging is enabled and when you plug phone up to computer, make sure you select file transfer.
dwojr said:
I have to make sure usb debugging is enabled and when you plug phone up to computer, make sure you select file transfer.
Click to expand...
Click to collapse
yes, debugging was enabled.
well after many attempts I was able to connect. (the connection was problem, must tried many times restart server, after connection adb shell, connection with phone was stable)