Hi there... totally new to the Andriod world and am stuck on trying to upgrade the firmware. I am running Windows 7 64 bit and the devices says that it is installed correctly yet when I run "adb devices" it gives me and error stating "command not recognized....? any idea's?
Rogers device....
do you have your sdk setup correctly? do you have the sdk tools folder in your path?
you can find out by typing path
you should see
C:\android\tools as one of the entries....
windows is telling you that the adb command is not found.
i have the same issue. running windows 7 64bit and adb doesnt find the device. the phone doesnt show up in the device manager either, but it told me that it installed correctly when i first plugged it in.
hi again. I am a mac osx user and I was trying to install androidscreencast following the steps from http://code.google.com/p/androidscreencast/ , but it doesn't worked for me. can somebody to give some more details? I got this message...
At which step did you get this message? What happens if you click on the "Details" button from your picture?
Perhaps you need Java Web Start.
this error happens to me as well, before running the screencast. You need to make sure "daemon" is running (what ever that is) by simply running an adb command, such as "adb devices"
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
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..
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
jhs39 said:
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
Click to expand...
Click to collapse
Hello,
What's the output of:
adb devices
Also, can you paste the exact error displayed on the command prompt?
You could try:
adb kill-server
Which kill the adb.exe process
Then:
adb start-server
Cheers...
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
jhs39 said:
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
Click to expand...
Click to collapse
Hello,
By "rename" you meant "remain" ?
I don't think so... But you can right click on your windows taskbar and open task manager.
Look at processes and see if ADB.exe is still running. You can also tic:
"Show processes for all users" and see here...
Cheers...