daemon not running.starting it now on port 5037 *

安卓开发时，在windows 的cmd 命令中使用 adb 命令时，经常会碰到下图的的情况

adb shell时出现以下信息：

* daemon not running. starting it now on port5037 *

解决方法：

输入下面的命令：netstat -ano | findstr"5037" 可以查询什么占用了5037端口，再通过 taskkill/f
/pid xxxx 把占用5037端口的进程给Kill掉就好，在运行一次netstat-ano | findstr "5037"

上面方法已经通过使用可以成功解决问题。

另有方法：在cmd中进入platform-tool路径下输入 adb kill-server 这是adb就开始重新启动了在Eclipse的control 界面可以看到 attemptconnection.....1..2...3.........11就可以了

时间： 2024-10-13 10:31:01

daemon not running.starting it now on port 5037 *的相关文章

adb命令安装apk，和安装问题daemon not running. starting it now on port 5037解决

通过手机测试手机上的客户端应用,一般需要先安装被测应用apk到手机中,安装步骤如下: [预置条件] 1.通过PC的"开始",在运行框中输入cmd,回车,打开cmd编辑界面: 2.手机已连接PC,PC可以识别出手机,可在cmd编辑界面输入adb devices,回车,查看当前手机是否连接,若显示设备信息这标识已经连接,如下: C:\Users\posuo>adb devices* daemon not running. starting it now on port 5037 **

adb devices 显示 * daemon not running. starting it now on port 5037 * CreateProcess failure, error 2 问题解决

adb devices 显示 * daemon not running. starting it now on port 5037 * CreateProcess failure, error 2 * failed to start daemon * error: cannot connect to daemon 该问题的解决方法: 1.将本机C:\WINDOWS\System32下的adb.exe文件复制到C:\Windows\SysWOW64下. 2.将本机C:\WINDOWS\System

Android 有关于* daemon not running.starting it now on port 5037 *ADB

adb shell时出现以下信息: * daemon not running. starting it now on port5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon ADB SERVER的端口被占用 1.执行下面命令:adb nodaemon server 会出现 cannotbind 'tcp:5037' 2.输入下面的命令:netstat -ano | f

Eclipse daemon not running. starting it now on port ***的

daemon not running. starting it now on port ***的 1) 运行 cmd,进入命令行2) 输入 netstat -ano ,找出占用端口***(port ***)的线程ID(PID)3) Ctrl + Alt + Delete打开任务管理器,在近程分页下选择对相应PID的进程,关掉. 如果没有PID这一列,点击“查看”->“选择列”添加PID列.

android搭建环境错误 daemon not running. starting it now

1.输入cmd进入dos界面,进入android-sdk-windows\platform-tools目录,执行下面命令启动adb start-server 出现下面错误 * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * 2.执行下面命令 adb nodaemon server 出现下面错误 cannot bind 'tcp:5037' 原来

Android ADB 命令链接模拟器出现 daemon not running 解决方法

用adb命令链接远程模拟器有时候会遇到如下问题: C:Documents and SettingsAdministrator>adb connect 192.168.0.183 * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon 解决方法很简单: 在任务管理器中强制结束 adb.

一键结束port 5037占用

输入cmd进入dos界面,进入android-sdk-windows\platform-tools目录,执行下面命令启动adb start-server出现下面错误* daemon not running. starting it now on port 5037 *ADB server didn't ACK* failed to start daemon * 运行下面脚本,一键结束相关进程 # -*- coding: utf-8-*- import subprocess p=subproces

MySQL故障处理一例_Another MySQL daemon already running with the same unix socket

MySQL故障处理一例:"Another MySQL daemon already running with the same unix socket". [[email protected]121 sbin]# service mysqld status mysqld 已停 [[email protected]-121 sbin]# service mysqld start Another MySQL daemon already running with the same unix

Another MySQL daemon already running with the same unix socket.

问题描述: 查看MySQL进程的状态: [[email protected] lib]# service mysqld statusmysqld is stopped 发现是关闭的,但是启动MySQL却报错 [[email protected] lib]# service mysqld startAnother MySQL daemon already running with the same unix socket. 解决方法:将mysql.sock备份一下,然后重新启动 mv /var/l