After connecting the phone via usb cable, "adb devices" command lists :
$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA3BSWG00401 offline
1) First time it asked whether to trust this computer and I checked 'always trust this computer'. Is there a way to untrust a specific computer / make it ask again ?
2) plugging the cable to my older SGS3 works fine :
$ adb devices
List of devices attached
4df1d4650790afdf device
Has anybody encountered this before ?
Additional info :
$ adb version
Android Debug Bridge version 1.0.32
Revision 57224c5cff69-android
I'm using Linux Mint 17.2, NuSense 6 (Lolipop)
Related
Howdy.
I've done the HTC unlock and am trying to flash recovery.img via adb. I've downloaded sync, sdk, and java. Set path for sdk, java...etc.
When I go to fastboot and try....adb push recovery.img /sdcard/ it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
What am I missing?
nineandtwo3rds said:
Howdy.
I've done the HTC unlock and am trying to flash recovery.img via adb. I've downloaded sync, sdk, and java. Set path for sdk, java...etc.
When I go to fastboot and try....adb push recovery.img /sdcard/ it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
What am I missing?
Click to expand...
Click to collapse
Make sure its charge only and using a good cable and a good USB port then open CMD in platform tools folder and type adb devices...it should start the daemon and list the device try that and see if it find it
Sent from my PG86100 using xda premium
ok i have showing device in recovery and fastboot but when the rom starts booting
i issue adb logcat i still get
Code:
c:\logcat>adb logcat -d > logcat.txt
adb kill server
adb start server deamon running on port 5037
waiting on devices
error protocol fault <no status>
adb kill server
adb start server deamon running on port 5037
waiting on devices
error protocol fault <no status>
c:\logcat>
any help would be lovely at this point. i have taken the liberty of uninstalling everything from path to sdk and htc drivers and reinstalling everything one at a time on both linux and windows.....yet still same results... erm im very mad at this thing lol.....oh yeah almost forgot i went through and double checked all the id's and those are correct everything should be configured right
better question what esle can i debug with instead of just logcat?
this has been a problem after problem situation the whole way through trying to knock my HTC one out of this softbrick state it is currently trapped in.
long story short. currently at point where trying to sideload rom to phone... past flashing twrp.img... and if its not one error its the next.
1) adb will refuse to start.. it will just stick on:
C:\adb>adb start-server
* daemon not running. starting it now on port 5037
2) C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
3) last error type, everything will be running smoothly then as after the 'adb sideload ROM.zip' or should it be this,'adb sideload Desktop/ROM.zip' dont know but it shoots back "error: closed"
FIX THIS PLEASEEEEEEEEEEEE!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Hi friends ,
I just cannot get rid of the issue with the 8 things I tried (see below). I need your help pls, it has taken me alot of time and still unsolve.
I am running on window7, 64bits. I am building the "hello world" program and follow the instruction from Andriod developer website. At first, everything went well including the installation. I even manage to run the program on my Samsung S5. However, in a while, I notice something is wrong after I edited the code, so I delete and re-install the SDK and ADT package, objective is to bring the code back to the same factory state. I had tried installing both version of 32bits and 64bits Eclipse package but encounter the following problem when i click RUN as Android application:
******************** Return the following txt: ************************
The connection to adb is down, and a severe error has occured.
You must restart adb and Eclipse.
Please ensure that adb is correctly located at 'D:\ADT\sdk\platform-tools\adb.exe' and can be executed.
**********************************************************************
I did the following troubleshooting:
1) Restart the computer and my phone (samsung S5)
2) Check that there is a connection icon on my PC (USB connected between phone and PC)
3) Update adb in the SDK using the SDK manager
4) Make sure i go to the "help-->Install new software" in the Eclipse and key in the dl-ssl weblink every time i re-install the Elipsce package.
5) Make sure I click "help-->check for update" in the Eclipse every time i re-install the Elipsce package.
6) Checked that I am the adminstrator of my PC
7) Run command at command prompt. I did the follwoing steps:
a. Close the Eclipse if running
b. Go to the Android SDK platform-tools directory in Command Prompt
c. type adb kill-server
************************* Return the following txt ************************
* server not running *
--> adb server is out of date. killing...
ADB server didn't ACK
* fail to start daemon *
**********************************************************************
d.then type adb start-server
Return the same txt as above.
8) I suspect some other process is occupying the port 5037 which the adb access. So I attempt to find the PID (process id) of the process which occupied the port 5037 by giving the command "D:\Android\sdk\platform-tools>netstat -aon|findstr 5037"
************************ Return the following txt *****************************
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 3640
TCP 127.0.0.1:5037 127.0.0.1:50506 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50507 TIME_WAIT 0
**********************************************************************
Then I go to PC Task Manager, but there is no PID with 3640.
I also type at command prompt the below:
tasklist /fi "pid eq m3640
************************* Return the following txt ************************
No task are running which match the specified criteria
**********************************************************************
Seems that the adb is not responding to any re-installation, or restarting of PC and device. The task manager shows PID 3640 but couldn't see any process related to it.
I am a electronics engineer and much a novice in this field of computer.
pls help
From starting Android 11 we can use ADB wirelessly by pairing the device wirelessly using,
Code:
adb pair ipaddr:port
When I try the same in an Android 10- device,
Code:
./adb pair 192.168.8.120:5555
Code:
Enter pairing code: 123456
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
Failed: Unable to start pairing client.
The problem seems that a pairing code cannot be provided by the device. I think if we could have a method (hack) to provide a pairing code from the device, we could succeed.
Have anyone tried to do it on Android 10- ?
Isn't that possible at all?
Code:
adb pair
only available on Android 11 and up.
Look inside here.