Greetings,
I am attempting to run Tasker with AutoApps on my Note 10.
I get the following message when I run ADB from my MacBook.
adb: no devices/emulators found
I have USB Debugging enabled, and I installed Android File Transfer and also tested with Samsung Smart Switch. Both applications make successful connections with my Note 10, but I am confused as to why ADB does not detect my device. Any help is greatly appreciated.
I also ran...
/adb kill-server
./adb devices
and receive the following...
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
There is no device listed.
Any assistance would be greatly appreciated.
Did you try ./adb devices again after daemon had started?
Related
Hello! I want to connect Kindle Fire and Raspberry Pi (ARM debian) via USB.
I build adb for ARM.
Code:
[email protected]:~$ sudo adb kill-server
[email protected]:~$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
0123456789ABCDEF device
Now i want to get network Raspbery <-> Kindle.
I use gedeROM but I tried other ICS's roms.
I can't find usb tethering in menu, and apps from android market did not want to work.
How can i get network Raspbery <-> Kindle via USB?
What exactly are u trying to do.I don't understand
Sent from my Galaxy Nexus using xda app-developers app
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
stevetrooper said:
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
Click to expand...
Click to collapse
regular should work. That is just the data transfer speed.
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2247471
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
stevetrooper said:
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
Click to expand...
Click to collapse
Yeah, the new adb(d) (6 months back, iirc) added some security where you have to confirm the rsa fingerprint of each machine you connect to. It's a little annoying, because you HAVE to connect adb via USB first, and only then can you use adb via wireless, which is all I ever use anymore.
(edit: adb security added in 4.2.2, which was released in february)
I have been following the same steps that works on my Samsung S4 but I cannot get it to wotk on Nexus 7 (2013). I have also tried various applications and non of them seem to work.
Android version: 4.4.4
Build: KTU84P
Code:
☁ / adb kill-server
☁ / adb tcpip 5555
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
ViperZ28 said:
I have been following the same steps that works on my Samsung S4 but I cannot get it to wotk on Nexus 7 (2013). I have also tried various applications and non of them seem to work.
Android version: 4.4.4
Build: KTU84P
Code:
[emoji297] / adb kill-server
[emoji297] / adb tcpip 5555
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Click to expand...
Click to collapse
Try a different cable .. Make sure that you accept the screen that says do you want to allow
Adb kill-server
Adb remount
Adb devices
Sent from my iPod touch using Tapatalk
jcbjoe said:
Try a different cable .. Make sure that you accept the screen that says do you want to allow
Adb kill-server
Adb remount
Adb devices
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I have tried several different cables, the exact same setup works on S4. I do not see the accept screen.
ViperZ28 said:
I have tried several different cables, the exact same setup works on S4. I do not see the accept screen.
Click to expand...
Click to collapse
Have you tried adb over wifi?
https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect
Sent from my SCH-I535 using XDA Free mobile app
jcbjoe said:
Have you tried adb over wifi?
https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I see in the logs
Code:
checking wireless status
changing status
adb connection max retries exceeded
adb connection max retries exceeded
I am going to go stock and see if the problem is in the rooted rom
ViperZ28 said:
Yes, I see in the logs
Code:
checking wireless status
changing status
adb connection max retries exceeded
adb connection max retries exceeded
I am going to go stock and see if the problem is in the rooted rom
Click to expand...
Click to collapse
I just flashed stock and it works fine, I will post to the custom rom thread about the issue.
I am having a problem while trying to root my . When I try to make sure that my device is connected by typing 'adb.exe devices' through command prompt I get the error message:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Please help!!!
Command is adb devices. Then once device is shown adb reboot-bootloader to enter fastboot.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Also make sure adb and fastboot are in root folder of their own eg c:\adb
passion8059 said:
Command is adb devices. Then once device is shown adb reboot-bootloader to enter fastboot.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Also make sure adb and fastboot are in root folder of their own eg c:\adb
Click to expand...
Click to collapse
still not working I still get the same error, I don't know what I' m doing wrong. I followed the LG G4 "Low Effort Root" guide but as stated earlier I still cant get the command window to recognise my phone
Use twrp and ensure you have supersu 2.49.zip on phone storage.
use this guide to assist hope it helps: http://www.theandroidsoul.com/how-to-install-lg-g4-twrp-recovery-easily-79553/
While following the steps on how to install twrp recovery on lg g4 I still get the same error above. I don't know what I'm doing wrong that my computer is not recognising my device.
If you happen to have a Dell PC, uninstall the Dell PC Suite. Many users report issues with Dell PC Suite and ADB. Various AntiVirus Software, Samsung's Kies (3), Norton and McAffee Safe Filter services are known to cause issues with ADB. Also, make sure you're not using a USB 3.0, which isn't your problem but could be once you establish a functioning connection via adb.
Just to let you know I am trying this on a samsung laptop, after uninstalling Samsung kies I get the error:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
My guess is that there are software on the laptop that are conflicting with the process so I'll uninstall all the programs that I don't use but if anyone has anymore solutions please contribute
Hello
my android tv box is detected as android device by my pc, and it cause me problem with adb command
I've disabled usb debugging and close developpement settings but it still connected by adb via wifi
F:\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
192.168.100.7:5555 device
Click to expand...
Click to collapse
can you help me please to resolve this problem please ?
Go to dev option and click on revoke.