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.
Hello XDA-Developers,
I have a problem
I have an android phone Jelly Bean 4.1.2
I already installed the drivers of my phone to my computer, when i plugged the cable i enable USB DEBUGGING.
after that i checked device manager and my phone is listed under Android Phone
After that i go the console and type adb devices it starts the server and returns an empty list
i tried everything
i also try kill-server and start-server still the same
PLEASE HELP
then
Maybe try a different usb slot. One directly on the motherboard, it sometimes helps.
As the title suggests, bootloader unlocked no problem, tablet was connecting to ADB at the time, tried to flash recovery which as far as I can tell was not successful (I can't boot to recovery, get the injured Android icon), now I can't connect to ADB (get the "List of devices attached" result). So I'm completely stuck, can't move forward, can't go back to stock, what do I do?
Edit: Apparently it's an issue with my PC, my wife's PC worked fine, why it worked to unlock the bootloader and then stopped I have no idea. Can anyone link me to a solution to get ADB working on my PC again? I tried removing/re-installing drivers, rebooting, you name it, no luck.
With your device booted into recovery or the system do you get anything in device manager? If you get a device with a yellow exclamation mark, right click it. Go to where it allows you to choose a driver from a list on your computer. Select adb android composite (or something like that)
Sent from my Nexus 5 using XDA Free mobile app
Thanks for replying.
So before unlocking the bootloader, with USB debugging enabled I could get the tablet to connect using the ADB driver and could access it with ADB but could not access storage for file transfer, with USB debugging disabled and switching the driver manually to the MTP driver I could access storage but not ADB. I have had other device drivers installed on this PC for my Galaxy phones, I had issues initially with the tablet connecting but showing a yellow exclamation mark, then I removed all of the Android USB devices using USBDeview and installed the 15 second ADB tool to get it working, I'm on Windows 8.1 BTW.
After unlocking the bootloader, with USB debugging enabled I cannot get the tablet to connect using the ADB driver and but it does show as an ADB device with no yellow exclamation mark, I just get the "List of devices attached" result and anything that tries to access the device via ADB hangs or fails. I can still switch the driver to MTP and access the storage just fine.
My wife's PC is a Win7 box and has never had android drivers or ADB installed, I used the 15 Second ADB installer on her PC and the tablet works for ADB and storage access with USB debugging turned on, so there's something I'm missing that needs to be wiped out or reset on my box.
I'm trying to root my Verizon LG G3 on 5.0.1 VS98524B, but now ADB wont recognize my device. Yesterday I was trying to root it using a one click root tool but it would fail (it would say successful, but would not achieve root). today I decided to use the LG flash tool to restore my phone and try again. then I saw that the tool (which claims to support all g3 models on all firmwares above kitkat) did not support VS98524B, but there is another that does, but surprise surprise, adb no longer finds my phone.
update... I have found that ADB on Ubuntu does find and recognize my device, and the security prompt comes up on my device. (does not come up for any window computer)
I have tried; restoring my phone again, installing and reinstalling the drivers, use different computers (2 win 7, one win 10), use different cables, on different ports, change between ptp and mtp, toggling and untoggling usb debugging, restarting my computer, etc.
adb doesn't find the phone while running a root tool, or just doing the adb devices command in cmd....
looked at many threads, and not many (if any) seem to have this problem, and all who did were able to solve using one of the steps I mentioned above....\\
any help?
update... Using Ubuntu adb does recognize my device, and prompts the security pop-up on my phone. (the pop-up does NOT come up for any windows pc)... but I cant figure out how to root the device using Ubuntu)
RESOLVED-- I uninstalled (again) the drivers, and grabbed new updated ones from the LG webpage (which ARE different than the suggested drivers on the root tool page.) then installed the android studio on my computer, and redownloaded adb... not sure which of these steps made the difference, but it worked! now rooted.
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
hawkswind1 said:
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
Click to expand...
Click to collapse
I don't think there's been an Internet/Ethernet option since before 12B, or at least before 23C.
@Coltonbyu, choose MTP for your connection type.
hawkswind1 said:
You should get a RSA fingerprint window that you have to accept on the G3 when connecting. If you're not receiving it, look in
(C:\Users\*username*\.android)
(C:\android)
(C:\Windows\System32\config\systemprofile\.android)
Delete adbkey and adbkey.pub in those 3 locations. Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options. Set connection to internet>ethernet. Restart the adb server in command prompt (adb start-server) and plug your phone in while looking for the RSA fingerprint window to popup on your phone.
Click to expand...
Click to collapse
I did as you said, but the prompt never appears on my phone, which is odd, as it appeared before the factory reset, but will no longer appear for any windows pc. (it does appear on Ubuntu though)
Hello All,
I have strange problem with ADB debugging on my Smartwatch ASUS ZenWatch 3.
I´m on AW2.0 and I tryed custom AW2.0 kernel from here:
https://forum.xda-developers.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340
and all working fine except ADB debuging and ADB commands.
If I enable ADB debuging in developer option and plug my watch to the computer I not see any confirmation dialog about allow ADB. And I see only unauthorized device after ´adb devices´.
With stock kernel all worked fine.
For now I´m on stock recovery and I can´t use ADB commands in recovery. It´s totally..........
I need working ADB commands and main problem is missing confirmation dialog... not pop up....
I tryed everything.... Enable/disable ADB, rewoke ADB, restart computer and watch, new ADB drivers, start and kill ADB server, factory reset, delete RSA key... Nothing works for me
I tryed debugging over wifi and Bluetooth and same problem... Allow ADB dialog not pop up
And my watch is unauthorized...
I tryed also another computer and same situation...
Maybe some problem in kernel? Because ADB is enabled by default... I don't know...
Is there any other way to get working ADB commands?
Maybe some bypass?
Please could you help me? Thank you very much