Database Users

[Q] "adb server didn't ack * failed to start daemon"

okay, I devoutly hope someone can help me here, because I'm at my wit's end with this. I'm using windows 7x64. I followed the instructions in THIS thread first(after installing the android sdk directly from the main website ), and got through everything okay, but when I try to do anything with adb(adb devices, for example) I get
"
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
"
Here's what I've tried so far:
1. Killing and restarting the adb.exe process, both with task manager and with adb kill-server(which is the only adb command I've found that does anything other than return an error message)
2. reinstalling both the drivers posted in this thread and those at nookdevs
3. rebooting both the computer and the nook color multiple times.
4. deleting all SDK files and both re-downloading and re-installing.
5. deleting every file I could find and the drivers and following the Nookdevs instructions. same problem
6. using the adb_wireless app, where it tells me to use adb connect <iP address> after running the app. same error message appears. Because of this step I'm less inclined to believe that it's a driver error, since the wifi app bypasses the USB driver, at least as far as I understand. I do, however, believe my drivers are installed correctly, I have ADB Composite android device in the device manager
The only google results I got with this error(for different devices) referred to the port adb needs being locked in to something else, but that doesn't appear to be the case here, I see nothing running on port 5037 in netstat
Thank you for taking the time to read my short novel, and I appreciate the help.

*shameless bump*
seriously though, 65 views and not a single person with even a suggestion? would this be better off in a different portion of the forums? Any advice at all?

dumb question, but with out the NC plugged in, when you type in "adb devices", what get's returned?
if you get that error message, than that's a config symptom.

Hey i'm no pro and got adb to work on accident...What i found is that the android sdk folder needs to be in your user folder. So when i go to start and click my user name my android sdk folder is in there with my downloads folder, desktop folder, and music folder. Makes sense? ALso any thing i push to my device i put into that folder in the tools directory. I found that that fixed most of my problems as i had the folder in the root of my c drive. Let me know if that helps.

No luck there, but thanks for the reply anyway. gives me the same error. I suspect in your case that you were not getting into the c:\android-sdk-windows folder and moving it to your username folder fixed that problem because that's the default path when you open a cmd prompt. Thanks for trying, though

Last thing i can think of is maybe your firewall? Kill it for a few mins and see what happens.

Still happens when the device isn't connected. I agree that its a config error rather than a driver issue. Also, disabling my firewall has no effect. Thanks for the suggestions though
Sent from my NookColor using XDA App

I have the same
nicbennett said:
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.

not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked

nicbennett said:
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
Click to expand...
Click to collapse
Wow... I would hate to have to rebuild my computer just to get ADB back. I will post this in the Evo forum and see if there is some help.
Edit: Started a new thread in Evo forum:
http://forum.xda-developers.com/showthread.php?p=10730809#post10730809

[Q] help for nook touch rooting from China

Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.

I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?

I wonder if you'd be able to use Orbot to be able to gain access to Youtube...

Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.

I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers

Can't get Hello World running

Hi Guys,
I'm trying to start some Android development however I've run into a couple of problems during Dev environment set up. I've been following the adt-bundle install instructions as I opted to use the ADT bundle.
This first problem is that the Android Virtual Device Manager will not run. I get a message saying "Failed to execute tools\android.bat The system cannot find the specified file". No idea what to do about that one.
The second is that I cannot run my app. I'm trying to run it on my phone (HTC Desire C) how I keep getting the message :
Code:
[2013-07-13 07:33:37 - MyFirstApp] ------------------------------
[2013-07-13 07:33:37 - MyFirstApp] Android Launch!
[2013-07-13 07:33:37 - MyFirstApp] The connection to adb is down, and a severe error has occured.
[2013-07-13 07:33:37 - MyFirstApp] You must restart adb and Eclipse.
[2013-07-13 07:33:37 - MyFirstApp] Please ensure that adb is correctly located at 'C:\Program Files\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\adb.exe' and can be executed.
I've tried resetting adb via command prompt using adb kill-server and then restarting using adb devices and checking that a device is connected however it doesn't seem to make a difference.
I've also tried connecting my N7 tablet up and install the usb drives in the sdk and I get the same errors
It's incredibly frustrating and I would really appreciate some guidance.
Thanks in advance
Samishal

[2013-07-13 07:33:37 - MyFirstApp] Please ensure that adb is correctly located at 'C:\Program Files\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\adb.exe' and can be executed.
is your adb there? and is it executable? (are you running as admin?)

I have also got same error AVD error.. ihad solved it by opening this file "C:\android\sdk\tools\android.bat" and updating its component..

How to adb pull files on a phone with a broken touch screen?

Hi there,
I have spent a couple hours trying to figure this out and just can't seem to figure out what to do any further!
I have a rooted Galaxy S4 with CWM 6.0.4.4 and Cyanogenmod 11 with developer debugging options enabled.
I cannot see anything on my phone screen as it is broken, nor touch anything so I cannot authorize the ADB connection from my computer. When I try to look at the connected device in command prompt, it says "0999d838 unauthorized". I assume it is unauthorized because I cannot accept my computer's connection. Therefore I cannot access adb shell and use other commands to pull the files I want.. When I try to "adb kill-server" and restart, it says my
"device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
Is there anyway to work around this? I have searched and the best answer I have found was that I should be able to access my ADB interface without authorization through recovery mode. I can access Download Mode and Odin.
Thanks

Hi,
Thanks for using XDA assist.
Your thread will be moved to the Galaxy S 4 Q&A, Help & Troubleshooting forum so that you can receive specialized help for your device. There are experts there that can help you out. Please note that in order to respond to any posts, you will need to create a XDA account.
Good Luck! - gsstudios

XDA Visitor said:
Hi there,
I have spent a couple hours trying to figure this out and just can't seem to figure out what to do any further!
I have a rooted Galaxy S4 with CWM 6.0.4.4 and Cyanogenmod 11 with developer debugging options enabled.
I cannot see anything on my phone screen as it is broken, nor touch anything so I cannot authorize the ADB connection from my computer. When I try to look at the connected device in command prompt, it says "0999d838 unauthorized". I assume it is unauthorized because I cannot accept my computer's connection. Therefore I cannot access adb shell and use other commands to pull the files I want.. When I try to "adb kill-server" and restart, it says my
"device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
Is there anyway to work around this? I have searched and the best answer I have found was that I should be able to access my ADB interface without authorization through recovery mode. I can access Download Mode and Odin.
Thanks
Click to expand...
Click to collapse
You cannot just access your phone without authorization. Use this thread as a reference.
http://forum.xda-developers.com/galaxy-s4/help/access-samsung-galaxy-s4-screen-t3228141
Maybe you can ask the guy if he figured it out. Basically you have to flash a kernel with these parameters for adb to work without authorization.
ro.secure=0
ro.debuggable=1
ro.adb.secure=0

Motion Sense Radar Bypass

Hello everyone! I'm looking some advice from the wise about bypassing the region restrictions for the Soli Radar (Motion Sense) in my Pixel 4. I am pretty new at running ADB (Android Debug Bridge) from my Windows PC. That said, I'm sure I overlooked something very simple. I can't get the commands to work at all. I followed the XDA YouTube video step by step on how to install and setup the SDK Platform tools on my PC. As well as how to prepare my device to receive commands from my PC. But it fails every time. I'm pretty sure that I'm just running the ADB incorrectly, but I don't know. I have only been able to find instructions on how to install and setup the SDK package. But no clear instructions on how exactly to utilize it. Again, I've never done this before. I am running the latest version on Android 10 on my phone and my PC is running Windows 10. And before running any commands, I verified that the device is in fact attached to the PC by running "adb devices" first. I wish there was an option to attach a screenshot of failure message I'm getting. But it says:
setprop: failed to set property 'pixel.oslo.allowed_override' to 'true'
I get this same failure when I run the alternative command line as well. And I have tried both command prompt and Power Shell and receive the same failure message. Anything advice that can be shot my way would be greatly appreciated. Thanks!

First check the windows 10 device manager to confirm that your device and computer are successfully connected.
Then try to replace with a new data cable, a USB 2.0 cable may be better.

Is the phone bootloader unlocked or have you rooted it yet? Honestly I am not sure if either of those are required for the changes, but I suspect they are. If you haven't rooted the phone yet, then I bet you don't have the correct privileges to make those kind of changes to the phone.