Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
flaav8r said:
Somebody please help me out of my misery. I followed the rooting directions to the letter, but when I type "adb devices" I get the following error:
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
I'm in the right directory ( AndroidSDK\tools\ ), I have the android driver installed, I have USB debugging checked, I don't understand why this is not working.
Please help me out here.
I had no problem rooting my palm pre, which was infinately more complicated than this.
Thank you in advance.
Click to expand...
Click to collapse
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
johnsongrantr said:
had a pre and "rooted" it as well..... using putty is more complicated that this but this is a little more like hacking... whereas on the pre you are just accessing root rather than breaking into it.
anyway... try these
nstall htc sync from htc's website, can you sync?
run cmd as administrator
cd untill you are in the same directory as your adb
type "adb devices"
does it display your hero?
type "adb shell"
does is display "$" ?
Click to expand...
Click to collapse
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
flaav8r said:
Yes, I can sync with HTC Sync. When I do the adb devices I get the error I described above and I cannot do adb shell because I cannot communicate via android sdk.
Click to expand...
Click to collapse
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
johnsongrantr said:
windows 7? VISTA? XP?
restart phone/computer
unplug/plugin usb
also find another copy of adb.exe i heard there's a old copy floating out there that doesn't reccognize the hero for some reason but if you got it from a guide you shouldn't have a problem.
download sprint RUU and wipe your phone (if it will connect) also if you want to dig down the ruu has a working adb.exe twisted into their install they dump in your %TEMP% folder
Click to expand...
Click to collapse
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
flaav8r said:
Windows XP, and I got the files from this site and androidsdk from the google site linked from theunlockr.com.
Click to expand...
Click to collapse
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
johnsongrantr said:
try this known good version
http://forum.xda-developers.com/attachment.php?attachmentid=244916&stc=1&d=1257827184
Click to expand...
Click to collapse
I tried the new files, and still got the exact same error.
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
johnsongrantr said:
well i'm out of ideas.... and i'm tired.... anyone else throw a little help this guy's way?
if by tomorrow you/they haven't figured it out I'll see if I can't think of something else for ya
Click to expand...
Click to collapse
Thank you for your help. Greatly appreciated.
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
I'm gonna give it a shot right now.
simplyphp said:
The ADB server binds and listen to port 5037. If that port is taken and/or if the daemon is already running, you'll see that error message.
Start task manager and kill adb.exe (all the instances of it).
If that don't work, try rebooting your computer and your phone, and trying again.
If it still don't work, try this:
http://groups.google.com/group/android-developers/msg/dfae5da4a3c80aa8
Click to expand...
Click to collapse
Haha, success. I'm gonna try and root it now.
Thank you so much.
flaav8r said:
Haha, success. I'm gonna try and root it now.
Thank you so much.
Click to expand...
Click to collapse
Np glad to help
simplyphp said:
Np glad to help
Click to expand...
Click to collapse
Sucussfully rooted, thanks again.
Sorry for reviving an ancient post, but I just wanted to say that I ran into the same issue and opening up "taskmgr" and killing the active instance of "adb.exe" resolved the issue.
Just for help :
I had the same issue and it was my Firewall which blocked the starting of deamon.
Turn off your Firewall can fix the problem
cheers guys, followed the instructions and flashed rec. radio
This solved it for me: edit adb_usb.ini
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
After killing ADB.exe run netstat (just "netstat", no parameters) and
see if port 5037 is opened. It probably will be. Wait a while. Run
netstat again, now there are less connections on the port. After a
port 5037 is no longer opened. Only then it's OK to run ADB again.
Please note that this worked for when I killed the ADB.exe process &
process tree from Sysintenal's Process Explorer.
Also, I still don't know why running ADB again before all connection
are closed led to the port never being freed (albeit netstat didn't
show any open connections anymore). Moreover, the problem that forced
me to kill ADB in the first place needs to be solved and there's
enough on that in the forum.
AsafR.
Click to expand...
Click to collapse
Problem is HTC Sync
lucbloom said:
This solved it for me:
Edit ~/.android/adb_usb.ini file to make sure that there is no extra empty line after the 0x0006 line entry
For other users: I also found this:
Click to expand...
Click to collapse
HTC Sync Manager has adb.exe at location C:\Program Files\htc\htc sync manager\htc sync\adb.exe
You have 2 options now:-
1) Delete this adb.exe
2) Copy latest adb.exe from android sdk to this path.
Note: You need to make the 2 copies of adb.exe in sync always(when android sdk is updated) else this problem will come up again.
On windows 7, you can make a link of adb.exe from android sdk to this folder, which will avoid copying manually.
C:\> cd "C:\Program Files\htc\htc sync manager\htc sync"
C:\Program Files\htc\htc sync manager\htc sync\> mklink adb.exe C:\<path to your sdk>\platform-tools\adb.exe
kill htc sync
nevermind someone already posted
Hey guys im new here and new to android too. my android sdk doesnt seem to work anymore. when i typed adb shell, it will show daemon starts successfully. it worked flawlessly previously. however when i tried using adb command like adb devices all these, it will shows "adb not found" what does this mean? i open the command prompt at the tools folder and have tried to reinstall my samsung I9000 driver but still it doesnt work. Is it cos of the path i set is wrong or wad? Im using window 7 and the folder name of tat android sdk is called "android" on my desktop. can anyone help me with this??? thanks. i need the adb to work in order to install some game and root. thanks in advance
Reinstall SDK
i tried reinstalling driver and sdk and the result is still the same. any other suggestion?
Not sure if it helps, but I had problems installing i9000 drivers until I installed Kies. Kies installed all the drivers perfectly.
you have to restart the adb daemon as root, eg:
sudo ./adb kill-server
sudo ./adb start-server
edit: just read that you are using windows ... so run the command without he "sudo" but under the admin-user ...
Hello, I recently got Ubuntu installed on my computer. I got the Android SDK set up on it, but I cannot get adb shell to work, everytime I try it this happens:
[email protected]:~$ adb shell
* daemon not running. starting it now *
* daemon started successfully *
error: insufficient permissions for device
Click to expand...
Click to collapse
This never used to happen on windows, does anyone have any idea on how to fix it?
Have you tried running it as root? It tells you in the error message that you've got insufficient permissions...
Sent from my Droid using XDA App
I accidentally deleted my data and it says "No OS installed". When I plug in the phone to the PC and I check devices it only displays "Android Phone" and I cannot access the phone itself from the PC.
How am I suppose to sideload if I cannot access it in the first place? :[
eXileris said:
I accidentally deleted my data and it says "No OS installed". When I plug in the phone to the PC and I check devices it only displays "Android Phone" and I cannot access the phone itself from the PC.
How am I suppose to sideload if I cannot access it in the first place? :[
Click to expand...
Click to collapse
From recovery. Look for adb push or adb sideload commands
SaHiLzZ said:
From recovery. Look for adb push or adb sideload commands
Click to expand...
Click to collapse
I see ADB Sideload in TWRP.
eXileris said:
I see ADB Sideload in TWRP.
Click to expand...
Click to collapse
this is from the AT&T forum, but the procedure is the same:
http://forum.xda-developers.com/showthread.php?t=2318497
you need adb 1.0.31 to use sideload
you can check your adb version with this command:
Code:
adb version
alray said:
this is from the AT&T forum, but the procedure is the same:
http://forum.xda-developers.com/showthread.php?t=2318497
you need adb 1.0.31 to use sideload
you can check your adb version with this command:
Code:
adb version
Click to expand...
Click to collapse
Yeah I have that exact version. However, I just tried to sideload the zip and it gave me an
Code:
* daemon not running. starting it now on port 5037
* daemon started successfully *
error: device not found
What do I do from here?
2137
eXileris said:
Yeah I have that exact version. However, I just tried to sideload the zip and it gave me an
Code:
* daemon not running. starting it now on port 5037
* daemon started successfully *
error: device not found
What do I do from here?
Click to expand...
Click to collapse
Update: Fixed it. Turns out I did not have the HTC drivers installed on my PC. Thank you everyone that replied. :laugh::highfive:
Hello everyone
I was wondering if someone can help me. I've been trying for a week to get my device recognized by the my Windows 10 PC, but it keeps coming up as unauthorized. I've seen all the posts:
https://forum.xda-developers.com/amazon-fire/help/help-thread-7th-gen-2017ask-question-t3636919
https://stackoverflow.com/questions/16256790/cannot-install-adb-for-kindle-fire-hd
https://theunlockr.com/how-to-unroot-the-amazon-kindle-fire/
https://www.howtodroid.com/2014/02/how-to-add-adb-command-prompt-windows.html
https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937
https://forum.xda-developers.com/showthread.php?t=1552547
Even the official Amazon website instructions
https://developer.amazon.com/docs/f...ice.html#install-the-usb-driver-windows-users
Sorry for all the links, just trying to prevent people saying i haven't tried everything. Even going to a new computer where i never plugged in the Fire 7 in said it was unauthorized. Here is the errors i get (i ran this in the folder itself using powershell and cmd as admin)
D:\Fire 7\3rd attempt\platform-tools>adb devices
List of devices attached
serial number unauthorized
D:\Fire 7\3rd attempt\platform-tools>adb kill-server
D:\Fire 7\3rd attempt\platform-tools>adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
D:\Fire 7\3rd attempt\platform-tools>adb devices
List of devices attached
serial number unauthorized
D:\Fire 7\3rd attempt\platform-tools>adb usb
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I'm at a loss, i know it works sicne i've seen a bunch of people do it online, but for some reason i can't do it. Please help! Anything would be helpful! Thank you in advance!
Did you find a workarround? I'm stuck in the same place as you. Tried everything you mention and fail...
srok.desarrollos said:
Did you find a workarround? I'm stuck in the same place as you. Tried everything you mention and fail...
Click to expand...
Click to collapse
i had this on ubuntu from a command line, but abdlink said authorized (but nothing would install). I went to windows10 and i get the prompt on the tablet and no issues. I don't know if the ubuntu adb drivers don't work right or what. It seems to work fine in ADB on windows...
I have had to turn off adb usb on the fire before and remove authorizations to get it to prompt for adb.
I fixed it in Ubuntu by changing it to media device instead of charging only.
Edit - worked one time, then back to unauthorized....
next edit -
sudo adb kill-server
sudo adb devices
that prompted the authorization for me