I installed the SDK and have run my ADB scripts for my samsung Vibrant before, I got home today and got a "The Program can't stat because AdbWinApi.dll is missing from your computer" error. I uninstalled the SDK and reinstalled it rebooting my computer after each just to make sure. I also tried moving the AdbWinApi.dll file to my Windows/System32 folder along with the Adb.exe.
I am running windows 7 64bit
Core I7 920 @2.67 GHz
6 GB ram
ATI 5750 Vid card
Any help would be great.
Cheers,
i figured it out
download daemon tools. install the free version. close cmd
open cmd
re type your path. and your computer should stop complaining about a missing driver.
This worked for me and i now have full access. hope this helps
Try 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?
alekosy said:
Try 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?
Click to expand...
Click to collapse
Sorry guys
Its been about a week since I have been trying on google, unlockr as well as xda forums for unlocking bootloader for nexus S, and I STILL am stuck at my device not showing up when I type 'adb devices' even though I have tried SDK drivers, PDAnet drivers, etc...countless restarts, countless uninstalls, following each and every method to the letter. The closest I have come is to alekosy's issue above where daemon kills the process as he describes and then, nothing. I keep waiting. Every time once daemon starts, whenever I type adb devices, I only get this 'list of devices attached'...and nothing else. in device manager, device driver shows installed correctly...
I would be heavily indebted to anyone who could show me the light (get my device show up in adb devices and then allow me to root).
Thanks a bunch!
(Frustrated beyond belief!! )
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.
Thanks espentan. That worked for me.
An easier way
[fastboot does not work, adb works]
No need to fiddle with environment variables. This should do it:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
..\tools\fastboot.exe devices
etc.
Explanation: the dll's (along with adb) were moved to platform-tools. Issuing fastboot from this directory, using '..', which means "up one directory level", with 'tools' then picks up the dll's.
Thank you very,very much....that worked like a charm..after hours of head aches...
twistadias said:
Thanks espentan. That worked for me.
Click to expand...
Click to collapse
espentan said:
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.
Click to expand...
Click to collapse
That worked for me too. Very easy explanation...!!! Thanks
Alot easier fix, go to google type in adbwinapi.dll and download it.
Put it in sdk/tools
Done
Sent from my SGH-T959 using Tapatalk
alekosy said:
Try 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?
Click to expand...
Click to collapse
Thanks!!!! This helped me after hours of trying to use adb, now it finally works! I just have to right click that folder and use the command prompt that way every time in order to use adb, weird but it works so i'm fine with that. Thanks
Thanks espentan
espentan said:
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.
Click to expand...
Click to collapse
It worked perfectly for me.
Thanks
espentan said:
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.
Click to expand...
Click to collapse
nice!
it seems only win7 users have to do the steps while xp do not
espentan said:
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.
Click to expand...
Click to collapse
This solved it for me
sgtmedeiros said:
Alot easier fix, go to google type in adbwinapi.dll and download it.
Put it in sdk/tools
Done
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
I have done this. It worked perfect. thank you mate!
sgtmedeiros said:
Alot easier fix, go to google type in adbwinapi.dll and download it.
Put it in sdk/tools
Done
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Much easier thanks. Xp here
You don't need to google for it, it's in platform-tools, along with adb.exe
help pls
Guys,
I am getting the same error about the missing .dll file when I try toi install the exe from revolution.
I tried changing the environmental variables, no luck
tried just downloading the .dll from google and dropped it into sdk/tools, no dice!
Can someone please help me to get this to work, have a brand new Sensation sitting here and I can't deal with Sense. Thanks
the error I get when trying to install is of course:
Adbwinapi.dll is missing
GreatWall2 said:
It worked perfectly for me.
Thanks
Click to expand...
Click to collapse
Thanks a lot, this worked for me too... The only thing i changed was the name of the directory from 'platform-tools' to 'tools' cause the file was in there.
I know that sounds like a very stupid question, but seriously - I don't know what it's supposed to do when I open it.
I downloaded and installed the Android SDK Installer with HTC Sync and Java from this thread: http://forum.xda-developers.com/showthread.php?t=1009419
Then, I opened the folder and double-clicked "SDK Manager", and a black window flashes once for a millisecond and disappears. This happens each time I open SDK Manager. I assume it is not supposed to behave like that.
Then, I went to the "platform tools" folder and opened "adb". Same thing. A brief black window pops up and scrolls a bunch of jibberish at hyper-speed and disappears within literally - a millisecond.
Now, I had nothing hooked up at this point - not my T-Bolt - nothing. I just wanted to peruse.
But now I'm afraid to go any further by hooking up my T-Bolt because I'm not sure what to expect. Can anybody offer any friendly guidance? I have rooted every single Android phone I've ever had, and many other phones belonging to friends and family, and I want to do this right by rooting the long way and learning as much as I can. I just need to be pointed in the right direction.
Thanks guys.
David
You need to go to your cmd prompt, and type "cd\" the cmd prompt should be c:\. Then type in "cd (whatever folder you placed sdk in)\platform-tools". Yes, leave a space between cd and the folder, no (). Then just type adb
Have your phone connected when you type adb, then type adb devices, and it should lust your phone with serial number.
jmiller98 said:
You need to go to your cmd prompt, and type "cd\" the cmd prompt should be c:\. Then type in "cd (whatever folder you placed sdk in)\platform-tools". Yes, leave a space between cd and the folder, no (). Then just type adb
Have your phone connected when you type adb, then type adb devices, and it should lust your phone with serial number.
Click to expand...
Click to collapse
Okay... when you say cmd prompt, I'm assuming that you're referring to START>RUN, and then the command.
Unfortunately, I'm not able get anything but, "Windows cannot find 'cd'. Make sure you typed the name correctly, adn then try again. To search for a file, click the Start button, and then click Search."
In the "Run" window where it says "Open", I've typed:
cd\ C:\Thunderbolt_Root_Files\platform-tools\adb
I've tried a myriad of combinations, and I'm not able to get any other result.
I feel like an idiot, and I don't know what I'm doing wrong.
start>run>type in 'cmd' then press enter then do what you have to do at the command prompt
magneticzero said:
start>run>type in 'cmd' then press enter then do what you have to do at the command prompt
Click to expand...
Click to collapse
Thank you!! That got me there!
sorry, but i need help, all day i have been trying to install android sdk and run on my windows 7 laptop. I went to youtube and followed everything but still can't get it. I installed 3 things. and I placed them in the c drive. now i have a file c:\android-sdk\tools.....now when I go into cmd and type that in it says invalid path...I tried d drive says device not ready....my evo is on debugged. someone please help me out.
In cmd try typing cd\
That will take u to root directory, now try c:\android-sdk\tools and assuming that is the valid path you should now be in that folder. If that does not work you may have an extra folder like android\android-sdk\tools.
I am assuming in the files u installed included were the drivers for the evo. These need to be installed otherwise once in tools dir u will get device not found when trying an adb command.
i tried cd then c:\android-sdk\tools....it says invalid internal external command. also I did download the driver for evo 3d but what do I do with it....where do i put it.....thanks for help in advance......im getting very frustrated.
"Cd\" without quotes then press enter. Then try specifying path for the tools folder which you say is c:\android-sdk\tools.
If that doesnt work you can type dir\w and that will show you all the folders in the directory. Make sure you type folder names exact.
As for the drivers just run the install and make sure u get right version. U msentioned windows 7 but 32 bit or 64 bit? If your phone has debugging on and the drivers are installed correctly you should be able to plug you phone in without being prompted to install new device.
Typed in c:/dir/w. It said volume in drive c has no label. Volume serial number is eore-14a9...also when I put my usb cable in laptop sees it.
OK, I'm trying to unlock the bootloader. Was successful at the RSD Lite part. However, when trying this part
Open a command prompt window I've extracted fastboot to the desktop
On Windows, press Start and type “cmd” then press the enter button I have no problems opening the cmd box
Type the following command. Your directory will be the folder where you extracted the Fastboot package. I click the space bar, type in "cd" click the space bar and past in my location
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
cd your directory here
Power down your Atrix device Powers down fine
Hold the power button and the downward volume button until you see “Fastboot”I see the fastboot text
Let go of the buttons and press the upward volume button once I do this
You will now see “Starting Fastboot protocol support” I see this
Plug your device into a USB port in the back slot of your computer Plug it in
Front slots sometimes do not have enough power to stay connected to the device.
Type the following command:
fastboot oem unlock I am told that this is not an execution command
What should I do at this point? I'm stuck. I tried this half a dozen times. I tried hitting enter after typing the location, I tried hitting enter after typing fast boot, tried hitting enter after OEM .... and nothing works. Ideas?
OK so I downloaded the moto-fastboot32 and here's what i'm getting now from the cmd window
"fastboot is not recognizeable as an internal or external command, operable program or batch file"
the executable name of moto-fastboot should be similar as moto-fastboot.exe. Make sure that you are on the directory that contains this executable. Suppose you installed it in c:\fastboot
then from a command prompt you would type:
cd c:\fastboot <enter>
dir <enter>
you should see the .exe file.
then you can run the moto-fastboot oem unlock command.
If you can't do such a simple thing as doing cd to a proper directory, may i respectfully suggest that you don't unlock your device? You will probably brick it.
Newbs are totally underrated here...This is the first thing that I've had a hard time with and I've messed with androids as well as iphones. Thanks for the warning, but I'm not afraid to brick it, and I dont think that my difficulty with a "simple thing as doing cd to a proper directory" would run that risk.
I'm attempting to follow the directions given, however, nothing seems to work. I'm fairly comfortable typing in commands, however, it just doesn't seem to be working. I've tried every trick imaginable.
However, since I'm not the only one having problems with this I would say that it's safe to assume that it's not me but the people writing the tutorials who are not giving detailed information.
No, I'm not a computer person at all, however, thus far I've been able to figure out most thing. I've tried all variations of the commands that are stated in this forum. Since it's not a sure fire thing (even those who seem to know what they are doing are having a hard time) I'll wait till a working version comes out.
If you're getting an error telling you that the command is not an executable command, then the fastboot.exe is not in a directory that is being accessed. In the command window, you need to change the directory to where fastboot.exe is located. For simplicity, I put the file in my root directory (c:/) and in the command window, type cd\ -- that brings me to c:\ and I can then type in the commands for fastboot. If you prefer to leave fastboot.exe in a different directory, you simply have to change the directory to that directory so that it is seen.
I had this problem too, but simple solution.
The file I downloaded from the tutorial thread was named moto-fastboot instead of fastboot, which changes the command
Change to that directory and make sure the file name matches what you are typing.
I followed the directions here
http://www.htcdev.com/bootloader
on 2 different computer. Installed the 3 links
Google Android SDK zip:
Java Runtime Environment:
HTC Sync (Windows Only):
Made sure fast boot off.
Tried with/without USB debugging on (even tho there is no directions for that)
Typed in Command Prompt: fastboot oem get_identifier_token.
I get same message "fastboot is not recognized as an internal or external command, program or batch file"
Tried to do the rumrunner thing as well but it says i need to get past bootloader 1st.
arrrggg
What do I do I have tried googling with no help.
All my phones in the past i could find rather easy "how to" instructions but not this phone.
crap
Put your device to fastboot mode ( switch off the device volume down and power together)
Else
Usb debugging on and type the command in cmd (adb reboot bootloader)
Sent from my SM-N7505 using XDA Free mobile app
saeroner said:
I followed the directions here
http://www.htcdev.com/bootloader
on 2 different computer. Installed the 3 links
Google Android SDK zip:
Java Runtime Environment:
HTC Sync (Windows Only):
Made sure fast boot off.
Tried with/without USB debugging on (even tho there is no directions for that)
Typed in Command Prompt: fastboot oem get_identifier_token.
I get same message "fastboot is not recognized as an internal or external command, program or batch file"
Tried to do the rumrunner thing as well but it says i need to get past bootloader 1st.
arrrggg
What do I do I have tried googling with no help.
All my phones in the past i could find rather easy "how to" instructions but not this phone.
crap
Click to expand...
Click to collapse
You aren't running the cmd from th correct folder. Browse to the folder where fastboot is. Hold shift key and right click. Select open cmd prompt here. Then run your commands.
dottat said:
You aren't running the cmd from th correct folder. Browse to the folder where fastboot is. Hold shift key and right click. Select open cmd prompt here. Then run your commands.
Click to expand...
Click to collapse
Ok i did that but get this message
"program can't start because AdbWinApi.dll is missing from your computer. Try re-installing"
I reinstalled/downloaded "Google Android SDK zip:"twiceusing to different extraction programs. I placed the folder in the same android folder as the fastboot.
still stuck. any help?
thanks
saeroner said:
Ok i did that but get this message
"program can't start because AdbWinApi.dll is missing from your computer. Try re-installing"
I reinstalled/downloaded "Google Android SDK zip:"twiceusing to different extraction programs. I placed the folder in the same android folder as the fastboot.
still stuck. any help?
thanks
Click to expand...
Click to collapse
Download this. Extract it. Run your command prompt and commands here.
https://www.androidfilehost.com/?fid=23501681358559711
^ Thanks that worked!
saeroner said:
^ Thanks that worked!
Click to expand...
Click to collapse
You are welcome ☺