So ive been trying to figure out how to push files onto my eris for like a week now and im not smart enough with computer to so it. Ive downloaded the mac ADB, and have a 2.2 emulator up and running. But when i plug my phone in i cant ever find it using terminal. Im pretty sure its just cause im using the wrong commands so if anyone knows them for a mac that would be awesome. Any info would help me, Thanks.
No emulator is involved. Find the adb executable, and cmd+c to copy it. Fire up terminal and cmd+v to paste it, then type a space, then "push" (without the quotes), then a space, then drag the file you want to copy onto the terminal window, then type the location on your phone you plan on pushing to (like /system/app/ for example). And that's it! But you should do an adb remount before pushing. Again, to do a remount, paste the adb file into terminal or drag it in, then type a space, then "remount" (without the quotes).
It's been a while since I did the initial install steps, but the main difference to the commands is having to use a dot and a slash before the command "./" to specify the command you want to run is in the directory you're working in. Other than that, the PC steps are the same.
For example, my files are in a sub-directory under my user profile: /Users/<user_name>/Phone/android-sdk-mac_86/tools/ which can also be typed as ~/<user_name>/Phone/android-sdk-mac_86/tools/
So, in Finder, I go to that directory and double click the android file. That starts terminal which also starts the Android app. I go back to Terminal, press Command+T to open a new tab in Terminal (just so I won't have a ton of windows open), change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/ then I run the adb command typed as ./adb
So, to re-cap step by step:
My adb files are located in ~/<user_name>/Phone/android-sdk-mac_86/tools/
Make sure your phone is connected in USB debugging mode
In Finder, go to the above directory and double click android
Switch back to Terminal, press Command+T to open a new tab and change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/
Type: ./adb remount
Type ./adb shell (or whatever adb commands you want to run)
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!
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 ☺
I am trying to fastboot flash a dtb battery.zip. I am brand new to linux. Only been using it about a week. I did manage to get adb installed from the software manager. I have the battery.zip saved in Downloads. I have USB debugging enabled. However, I never get a prompt to allow the computer. When I run adb devices though there is a device listed. I must have did a thousand google searching trying everything I find and I cannot get this file on my tablet Can someone please help me out?
0
Seppppx said:
Did you follow these Linux ADB guides? How to Install ADB on Linux
1. Download the ADB ZIP file for Linux
2. Extract the ZIP to an easily-accessible location (like the Desktop for example).
3. Open a Terminal window.
4. Enter the following command: cd /path/to/extracted/folder/
5. This will change the directory to where you extracted the ADB files.
6. So for example:cd /Users/Doug/Desktop/platform-tools/
7. Connect your device to your Linux machine with your USB cable. Change the connection mode to “file transfer (MTP)” mode. This is not always necessary for every device, but it’s recommended so you don’t run into any issues.
8. Once the Terminal is in the same folder your ADB tools are in, you can execute the following command to launch the ADB daemon: adb devices
9. Back on your smartphone or tablet device, you’ll see a prompt asking you to allow USB debugging. Go ahead and grant it.install adb
10. Finally, re-enter the command from step #8. If everything was successful, you should now see your device’s serial number in the Terminal window output. Congrats! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
Source https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
Yes I have all that taken care of. The device is recognized. However, I never got a prompt to accept the computer connection. I'm wondering if you get one when your using Linux? Anyways, adb devices shows one device and serial number. I then enter adb fastboot reboot fastboot. Once rebooted I tried fastboot flash battery.zip. This did not work. I must have the wrong command or something but I cannot find directions from where I left off above.
Found instruction but their not working. The proper command was abd reboot bootloader. Once there when I run adb devices I get nothing. Why does it show a device in android but not in the bootloader? I also tried just running the command fastboot flash battery.zip I got the fallowing bash: fastboot: command not found. Also, tried unzipping the battery folder first and flashing battery.dtb. Still no go. It is because it is not being found in fastboot. I have no clue why.
I figured it out.
In software manager install.
android-tools-adb
android-tools-fastboot
Download unzip it in your downloads folder.
Download your battery dtb file unzip and pit it in the platform-tools folder.
Enable USB debugging on your phone or tablet.
In terminal type sudo cd /home/rocky/Downloads/platform-tools
Type sudo adb devices. You should see a device number.
Type sudo adb fastboot reboot bootloader
Type sudo fastboot devices
Type sudo fastboot flash dtb xxxxx.zip. xxxxx.zup is the name of your batty dtb file.
You should see your file being transferred.
Once complete type exit and reboot phone or tablet.