i don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "adbwinapi.dll" to windows' path under environment variables, so windows know where to look for the necessary files when you enter commands in the shell.
For this exercise i'm going to assume that you have installed the android sdk in the directory called "android-sdk-windows" on your c: Hard drive. If you have it installed somewhere else, change the path i'm mentioning below accordingly.
Go to the windows "control panel".
Click on "system and security".
Click on "system".
Click on "advanced system settings" in the left column of the window you're in.
Find the button called "environment variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "system variables" box until you find "path".
Select "path" and click the "edit" button.
At the very beginning of the input field called "variable value" enter the following:
"c:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary dll's and whatnot.
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
i coppied everything to my c drive folder itself the fastboot.exe adb.exe winapi.dll and the winusbapi.dll from the sdk tools and bingo adb accessTry this.
Shift + Right Click on folder C:\android-sdk-windows\tools, go to command mode option from there, and you should see it coming up with a command screen, type in adb devices with your phone plugged into the computer. If it shows your daemon is killing server, don't kill the window yet. Just wait...
It was meant to do this someway or whatever since I have a custom built PC for gaming and other purposes. I just didn't get the tech nerd answer right away for every problem solved, but it was all from you guys in XDA-developers, so I had this same error from trying to run 'adb' from start panel, and it didn't work because it was telling me my adb was needed to be re-installed and my AdbWinUsbApi.dll was missing from my folder, and It didn't tell me what folder, so I remembered my old way of learning how to run adb for the first time with my device.
Shift + Right Click tools folder from C:\android-sdk-windows as in C:\android-sdk-windows - Shift + Right Click RUN COMMAND PROMPT MODE. It should be fine after running this commands for your devices to show in the list.
type:
adb devices
adb remount - This is if your connected to a device already after.
adb install C:\android-sdk-windows\tools\setcpu.apk - example of your first apk file install.
Running the daemon killing server isn't gonna do anything to your phone like technically ruin it or trash it but its not, honestly, I never seen my phone ruined from this daemon killing server part, so if anyone cared to explained?
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
i don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "adbwinapi.dll" to windows' path under environment variables, so windows know where to look for the necessary files when you enter commands in the shell.
For this exercise i'm going to assume that you have installed the android sdk in the directory called "android-sdk-windows" on your c: Hard drive. If you have it installed somewhere else, change the path i'm mentioning below accordingly.
Go to the windows "control panel".
Click on "system and security".
Click on "system".
Click on "advanced system settings" in the left column of the window you're in.
Find the button called "environment variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "system variables" box until you find "path".
Select "path" and click the "edit" button.
At the very beginning of the input field called "variable value" enter the following:
"c:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary dll's and whatnot.
I've tried everything on this forum.
I really need to get this to work.
I don't have a folder called "Android" in Program Files.
The default file name for the folder isn't "android-sdk-windows". It is "adt-bundle-windows-x86-20140321" and I downloaded it from "developer.android." (won't let me type dot com) and unpacked it with WinRAR and saved it to the desktop.
"fastboot-win" was also saved to the desktop and unpackaged in the same manner. I have the .dll in the platform-tools folder but after everything I have tried on this forum, nothing. please help.