Is there a way I can use SDK Platform Tools with the dex station. I would like to open the command powershell and use it to execute adb and fastboot commands to my other phone.
Related
This is some easy stuff, but I thought I'd share one of my old "tricks" to work faster for the 'lazy' people .
So let's say if you work a lot with adb within the SDK tools folder this might come in handy if you currently cd to the folder each time you open a command prompt window.
Just download and extract the batch file to your desktop or where ever you like and open it with notepad then change the directory in the last line after cd.
The first lines makes sure the command prompt window stays open after you execute the batch file so you can start inputting. So don't worry, it does not include harmful codes for those who don't know batch commands.
Hope you will find this useful.
You could always copy "adb.exe", "AdbWinApi.dll", and "AdbWinUsbApi.dll" to "C:\windows\system32" and then you can use adb from any folder in command prompt. If I'm using any adb commands use them straight from the windows 7 search/run box on the start menu.
So I'm just now installing the SDK on my gf's computer and it puts ADB in /tools and Fastboot in /platform-tools. Fastboot refuses to run.
Code:
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
What's this about?? I downloaded the sdk.zip (the installer exe wanted me to install the java jdk, which I definitely don't need) and extracted it to C:\android-sdk-windows. Then I ran the SDK manager and installed the platform tools. Should I copy the platform-tools contents into tools or the other way around?
I haven't set the environment variable in system properties yet because I'm not sure which directory to use. The computer has the drivers for my phone and adb works fine. I booted into fastboot mode and it installed drivers.
Why would they give me an SDK with a non-working fastboot? Kind of irritated...
Copied contents of \platform-tools into \tools (DID NOT REPLACE ANY FILES!) and now everything works.
I would still like to know what was going on with this, and is there any advantage to adding the environment variable? I'd like to be able to run commands from any directory if possible, instead of having to cd all over the place.
Android Debug Bridge (ADB) and Fastboot utility installer for Windows.
Description:
Lets you designate the directory where you want to install it.
Sets environment variable to access ADB and Fastboot commands on Command Prompt (CMD) as an external command.
Steps:
Enter the path to the directory you want to install it.
Notes:
Program must run with administrator privilege.
Links:
Version 1.0 (x86) — https://goo.gl/nOQaoX
Credits : XDA developers
This is not my work I just make all of them at one place
Procedure for making your computer ready for executing fastboot commands
1 ) Install ADB drivers in windows using below link
https://drive.google.com/file/d/1lZ2pZLne6TV9YJLmS9P_EAteuAZn_BPs/view?usp=drivesdk
2) Download platform tools below link for windows :
https://drive.google.com/file/d/1HUAUNJnlOKUJCxSqVxNVRagV4XBGe-2Q/view?usp=drivesdk
linux and mac users download platform tools from this link :
https://developer.android.com/studio/releases/platform-tools.html
2 ) extract it
3) whenever you want use fastboot commands
Goto platform tools and paste required file in platform tools folder
4) then from platform tools folder open Power shell or command prompt using (shift + right click ) in empty space
Then it will open command promt then you can execute fastboot commands
That's it now your computer can be used for executing fastboot commands
On Linux, you can type "whereis adb" to find the location, and then "sudo cp adb fastboot location(usually /usr/bin)", to replace it and use it system wide. Afterwards, always check "adb version", to make sure you did it right.
Sent from my Mi A1 using Tapatalk
Harris P said:
On Linux, you can type "whereis adb" to find the location, and then "sudo cp adb fastboot location(usually /usr/bin)", to replace it and use it system wide. Afterwards, always check "adb version", to make sure you did it right.
Click to expand...
Click to collapse
Thanks for the information
I only know about windows OS
Easier method for installing adb and fastboot in Ubuntu
For those running recent Ubuntu versions or distributions based on them, there are packages for adb and fastboot available in the default repositories. To install them, execute this command in the terminal:
Code:
sudo apt install android-tools-adb android-tools-fastboot
Addendum: This works on all Ubuntu versions from 16.04 and beyond. I haven't tested this on the 14.10, 15.04, and 15.10 releases. However, I can confirm that this doesn't work on 14.04 and below.
can anyone help? I use platform-tools and it's not connecting I hope there is a solution here
The so-called Platform Tools contain among others the 2 programs/drivers ADB and Fastboot
Only to clarify things:
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Andika_Achmad said:
can anyone help? I use platform-tools and it's not connecting I hope there is a solution here
Click to expand...
Click to collapse
Plateform-tools are command line tools coming with the android sdk. As the build-tools, plateform tools are command line tools, so to use them you shall first know how to use them.
Here's the usage of some command-line tool available in the Android Sdk:
Command-line tools | Android Studio | Android Developers
Find out about the most important command-line tools that are available, organized by the packages in which they're delivered.
developer.android.com
Here's the content of /plateform-tools:
adb
api (a folder)
dmtracedump
e2fsdroid
etc1tool
fastboot
lib64 (a folder)
hprof-conv
make_f2fs
make_f2fs_casefold
mke2fs
mke2fs.conf
NOTICE.txt
package.xml
sload_f2fs
source.properties
sqlite3
systrace (a folder)