ADB device show empty - Android Q&A, Help & Troubleshooting

Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
But when I reboot my tablet as USB mode and from my laptop I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
I have already unlock and rooted my tablet.
Why I can't see my device id ? Please help

Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.

knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yeah this process is correct. Even I've experienced this.
What I did is:
Removed the USB cable connection and reconnect.
Kill adb.exe
Restart adb.
Then device was shown to be connected.

knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yes, I did that but still the same. Any other suggestions?

If on windows make sure your driver's are installed.
Type in cmd
adb kill-server
adb start-server
If that doesn't work try a different usb slot. You could also try moving adb and it's dependencies to your system32 folder. It's where all your commands are stored for cmd. You won't have to navigate to the android sdk tools.
Sent from my SPH-L710 using Tapatalk 2

Have you enabled Debugging on in your phones Developer settings?

ngaisteve1 said:
Yes, I did that but still the same. Any other suggestions?
Click to expand...
Click to collapse
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.

no need for that.
close any adb process either from task manager or by typing: "adb kill-server" in adb console
close everything and use this customized adb file I attached, it'll show your device.
it also has instructions and necessary files for rooting your device.

Problem
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
I have LG Optimus G (E975) i wipped all from the device and now i can't put cm11 on it, adb sideload do not work, and list of devices attached is empty. what must i do to put CM11 on my phone?:crying:

I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???

I have the same issue on my nexus 4. Yesterday it showed up with adb devices, now it's an empty list. I have USB debugging enabled and tried restarting the server. Nothing works. Any ideas?

ldemon360 said:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
Click to expand...
Click to collapse
unplug the device and adb kill-server then replug the device and try

turn debugging off and then on again
I had the same problem. In my case, i had forgot to enable usb debugging after new rom.
ngaisteve1 said:
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
Click to expand...
Click to collapse
In your case just disable USB debugging and then enable again.

fix the driver
I had this issue.
In my case when I went to device manager I could see the Device and wasn't installed correctly and could not load the drivers even after having installed them on the PC.
SO I clicked update drivers.
Select that will chose the drivers to install and select the Android Devices - ADB driver.
You will get a warning, but just ignore it and load the ADB driver for the phone.
Ensure you are in the sideload option of the recovery
Now
adb devices
it should show up as Sideload
Now sideload
Cheers
Dirk

knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Thanks, this worked for me.

Just add ur device id in adb.ini
Same issue was faced by me on my micromax Q334 and xolo era, I search lot for that and finally just adding hardware id the device are detected under adb.The steps are clearly shown in my video below..
It will definitely going to sort this problem..
For that just right click on adb driver ,navigate to detail tab and search for hardware id then add to adb.INI
I have also uploaded video on that YouTube: Fix adb connection issue(Adb driver installed, but device not listed)

device listed as "? recovery"
hey,
am trying to connect honor 6(h60-L04) but am not able to see the proper name for my device is just showing "? recovery" and am trying to update the android version coz of the device is in reboot-loop so help me out here
if there is any other option to recover device give me link.

knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
not work my friend, the list of devices is empty

Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.

vern.zimm said:
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
Click to expand...
Click to collapse
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.

Related

Does the driver have to show ASUS Android Composite ADB Interface? Mine doesnt. Help.

Hi!
I keep reading that the driver shows ASUS Android Composite ADB Interface but mine shows Transformer Prime TF201 instead.
I have been able to root, unlock and flashed TWRP.
Before flashing Roms I want to install NVFLASH but I am worried that my driver is not showing that ASUS Android Composite ADB Interface name.
I tried updating as I have read but whenever I select the folder with the drivers I want I get the message that Windows has determined that my software is up to date...
Every time I try to select the folder with the drivers I get "the folder you specified doesn't contain a compatible driver"
Any idea?
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash?
This is Windows 7 64bit
shaolin95 said:
UPDATE: I used the other option to install drivers and selected the ASUS Android Composite ADB Interface from a list and it installed it. I am able to access my files on the phone.
Is there a way to test fastboot and adb to make sure I am good to try nvflash
Click to expand...
Click to collapse
I always test the connection using the commands "adb devices" or "fastboot devices", it will tell you if any devices are connected.
You could also push a small file to the tab (eg. baba.txt with "adb push baba.txt /sdcard/") and find it on your tab, just to make certain.
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Striatum_bdr said:
Are you using Universal Naked Drivers? Asus ones suck...
http://forum.xda-developers.com/showthread.php?p=20995229
Click to expand...
Click to collapse
I am not but I can sure try those.
But before I do, if the test passes then it I should be fine with the current drivers?
I am done with nvflash!
I followed this video to do it in case someone has the same issues
http://www.youtube.com/watch?v=J3ypzUaKxvo
CODE 10 on all 5 naked adb drivers
No matter which I choose i get told that they cannot start. I have tried all 5 options in the naked set to no avail. this is a windows 7 ultimate pc. I am trying to fix my tf201 as it just keeps looping to a TWRP screen and gives me the key driver missing message

[Q] Drivers & adb troubles, a little help

I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
pda net
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
One thing that worked for me was to install pda nets drivers (google pdanet and it should be the first thing that comes up) it will ask you if you want to replace current android usb drivers and you tell it yes. Hope this helps!
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
Remove HTC sync, this should solve your problem. Also try a different port and reboot your computer.
If neither of these works then resinstall ADB you might have a dated version allthough that would NOT prevent it from functioning entirely
http://dl.google.com/android/installer_r21-windows.exe then choose download platform tools once the sdk opens.
I am on win7 x64 and have had 0 problems.
Good luck!
make sure the usb port you're using is 2.0 and not 3.0
it may be something as simple as that as well.
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
Thank you guys.
It was both using PdaNet to reset the drivers and also switching to USB2.0 ports that did the trick. Thank you for the help.
adb now sees my device Yay!
jayba420 said:
Thank you guys.
It was both using PdaNet to reset the drivers and also switching to USB2.0 ports that did the trick. Thank you for the help.
adb now sees my device Yay!
Click to expand...
Click to collapse
I am having the same issue. Which manufacturer did you select when you installed pdanet. I am stuck on the skip usb driver installation dialog. Have enabled usb debugging n all but it still can't detect my device.

Windows 7 not detecting Nexus 9 in recovery mode

I can't update my Nexus 9 because Windows 7 is not detecting my Nexus 9 during recovery mode. In non-recovery/normal mode Windows easily detects it as an "Android Device" -> "Android Composite ADB Interface".
I already tried:
-Using a different USB cable
-Uninstalling and reinstalling during recovery mode from Device Manager
-Installing latest driver from Google
Keep seeing "Error: Device not found" when I try to sideload 5.1.1 zip during recovery mode and an exclamation point next to "Nexus 9" in my Device Manager (No longer "Android Device" -> "Android Composite ADB Interface"".
Any ideas what I can try to do?
livinginavacuum said:
I can't update my Nexus 9 because Windows 7 is not detecting my Nexus 9 during recovery mode. In non-recovery/normal mode Windows easily detects it as an "Android Device" -> "Android Composite ADB Interface".
I already tried:
-Using a different USB cable
-Uninstalling and reinstalling during recovery mode from Device Manager
-Installing latest driver from Google
Keep seeing "Error: Device not found" when I try to sideload 5.1.1 zip during recovery mode and an exclamation point next to "Nexus 9" in my Device Manager (No longer "Android Device" -> "Android Composite ADB Interface"".
Any ideas what I can try to do?
Click to expand...
Click to collapse
What command are you typing?
cam30era said:
What command are you typing?
Click to expand...
Click to collapse
Typing the commands described here:
http://www.droidviews.com/manually-install-lollipop-5-1-1-ota-update-on-nexus-9/
livinginavacuum said:
Typing the commands described here:
http://www.droidviews.com/manually-install-lollipop-5-1-1-ota-update-on-nexus-9/
Click to expand...
Click to collapse
When you are in Recovery mode, hold Power button plus press and release volume up. This will get you into recovery menu where you can select sideload update via ADB. Then unplug your USB cable and plug it back in. Now your PC should recognize your device.
cam30era said:
When you are in Recovery mode, hold Power button plus press and release volume up. This will get you into recovery menu where you can select sideload update via ADB. Then unplug your USB cable and plug it back in. Now your PC should recognize your device.
Click to expand...
Click to collapse
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
livinginavacuum said:
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
Click to expand...
Click to collapse
You might try rebooting your PC.
livinginavacuum said:
I've tried that already. Unfortunately, the Nexus 9 shows up on my device manager with an exclamation point because it doesn't recognize it in recovery mode. And I've even tried updating and reinstalling the drivers. Still nothing...
Click to expand...
Click to collapse
Have you enabled USB debugging?
Usually means you don't have the drivers for the device.
If your device doesn't show up when you execute "adb devices", then it won't follow any commands.
http://developer.android.com/sdk/win-usb.html
Download that, and rclick the device with the exclamation, and point it to the android_winusb.inf when selecting the choose my own path.
After that, adb commands should work.
Alternatively, download the Nexus Root Toolkit, and go through the full driver installation.
That toolkit will make you clear all existing google drivers, and give you a fresh Nexus specific set of drivers.
AjunNg said:
Have you enabled USB debugging?
Usually means you don't have the drivers for the device.
If your device doesn't show up when you execute "adb devices", then it won't follow any commands.
http://developer.android.com/sdk/win-usb.html
Download that, and rclick the device with the exclamation, and point it to the android_winusb.inf when selecting the choose my own path.
After that, adb commands should work.
Alternatively, download the Nexus Root Toolkit, and go through the full driver installation.
That toolkit will make you clear all existing google drivers, and give you a fresh Nexus specific set of drivers.
Click to expand...
Click to collapse
I tried upgrading the driver to the android_winusb.inf path (from the same link as you provided).
Where can I download the Nexus Root Toolkit?
And wouldn't this still give me the same driver as from this link: http://developer.android.com/sdk/win-usb.html
livinginavacuum said:
Where can I download the Nexus Root Toolkit?
Click to expand...
Click to collapse
Anyone?
AjunNg said:
Have you enabled USB debugging?
.
Click to expand...
Click to collapse
Don't need USB debugging enabled to use ADB when in recovery.
livinginavacuum said:
Anyone?
Click to expand...
Click to collapse
http://bfy.tw/EcS

[Q] [LG VS930] Unable to get ADB commands to work

Alright, I've tried installing the drivers from Verizion and also using the drivers from the Android SDK and either way I have the same problem. ADB devices shows my phone, however whenever I try to push, pull, or reboot (the only commands I have any use for atm) the command prompt hangs like it's trying to access the device but no matter how long I leave it the device will not reboot, nor will any files appear in the correct folders on either the device or my computer.
I'm trying to root my phone and this is a pretty major roadblock.
Note:
USB Debugging enabled
ADB drivers installed
Phone shows up on "adb devices"
There is no error or any other output in the console. The best way to describe this problem is that ADB hangs.
I'm running Windows 8.1 and my phone is running Android 4.1.2
Also, I don't know if this is normal but, In order to get the notification that "USB debugging connecting" I have to use the internet connection option on the phone. When using MTP, Charge only and PTP that message doesn't appear and I don't see an ADB device show up in device man.
Things I've Tried
Uninstalling all Android drivers and redownloading/installing them after restart
Restarting my phone multiple times
Running adb kill-server / adb start-server
Changing USB ports7
Thanks!
Try installing drivers from LG. This seems the right one but double check:
http://www.lg.com/us/support-mobile/lg-LGVS930

Question DN2103_11_A.17 and ADB

Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?

Categories

Resources