[TOOL] Android ADB and Fastboot MSI installer with PATH variable - Android Software/Hacking General [Developers Only]

Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21

Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app

Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.

Installer updated to version 1.3 based on the Android SDK 24.0.2.

no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.

Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.

ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.

Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.

Related

No need for AndroidSDK

Hey guys
i´ve got something for the lazy ones of you
if you don't want to install the whole android sdk to use adb or fastboot you can just install this file.
it´s a package which extracts
fastboot.exe
AdbWinUsbApi.dll
AdbWinApi.dll
adb.exe
to your Windows directory.
so - extract the file
then just doubleclick it, press install and you´re done.
you even don't have to reboot your computer
​
here´s the proof that it works.
alutastisch said:
Hey guys
i´ve got something for the lazy ones of you
if you don't want to install the whole android sdk to use adb or fastboot you can just install this file.
it´s a package which extracts
fastboot.exe
AdbWinUsbApi.dll
AdbWinApi.dll
adb.exe
to your Windows directory.
so - extract the file
then just doubleclick it, press install and you´re done.
you even don't have to reboot your computer
Click to expand...
Click to collapse
will this work with windows 7? i already have adb running on my vista but i need it on the 7. Windows 7 has a sync problem, will this cut that out of the way?
Doesn't work for me.. When I run adb.exe just a random command showed and then closed. How can I use this?
d1srupt3r said:
Doesn't work for me.. When I run adb.exe just a random command showed and then closed. How can I use this?
Click to expand...
Click to collapse
Open cmd. Then use the command "adb whatever".
Edit: Just saw this extracts them to the Windows directory.
d1srupt3r said:
Doesn't work for me.. When I run adb.exe just a random command showed and then closed. How can I use this?
Click to expand...
Click to collapse
Start -> Run -> cmd
then in the black window that pops up, type adb
It will show you all the possible options to use with the adb command.
Like:
adb shell
adb reboot
adb logcat
So does this work?
Thanks for all the input. So all I have to do is connect my phone and everything follows or should I configure something in my phone like turning on the Debug? Sorry I am not familiar with ADB, I was just about to read its FAQ.
that just extracts the adb binaries into the windows folder + usb driver + fastboot binaries. if you run it the nothing will happen, you have to run it via cmd.
for example adb shell.
i'm using this on windows 7 and it´s working for me.
JUST EXTRACT, INSTALL AND YOU CAN RUN ADB + FASTBOOT VIA CMD
DON´T FORGET TO ACTIVATE USB DEBUGGING IN YOUR DEVICE
works great!!!!!
Couple of suggestions for the op, look up stericsons autosign script and incorporate its's making the tools folder path of ur system $path. Also write the fact that u gotta install adb drivers for ur phone to work.
@Daneshm90
you don't have to install anything, just install and you are good to go
alutastisch said:
@Daneshm90
you don't have to install anything, just install and you are good to go
Click to expand...
Click to collapse
Hmm, u sure ? Cuz i always download the sdk -> add tools to my path -> run the sdk and select to download usb drivers package -> then give windows those drivers to install.
Anyway, u seem to be a installing adb expert, help this guy out will ya
Link
​
here´s the proof that it works.
Ok, then u should clarify to extract to C:\Windows. If u extract it anywhere else it wont work, reason it works from C:\windows is because by default windows will look for in that folder for a command. Also can u go in device manager and check ur device's drivers, u have probably previously installed them as i have not heard of adb working w/o installing the device drivers.
it´s a package which extracts
fastboot.exe
AdbWinUsbApi.dll
AdbWinApi.dll
adb.exe
to your Windows directory.
Click to expand...
Click to collapse
AdbWinUsbApi.dll
questions? read the thread carefully.
alutastisch said:
AdbWinUsbApi.dll
questions? read the thread carefully.
Click to expand...
Click to collapse
Ill counter that with a proof that it doesnt
Its still processing.
then tell me why it works on my computer?
i guess cuz i got win7?
another user here in this thread said it´s working well, too?!
alutastisch said:
then tell me why it works on my computer?
i guess cuz i got win7?
another user here in this thread said it´s working well, too?!
Click to expand...
Click to collapse
Theres only one explanation i can fathom, u had installed the drivers previously, just hadnt setup adb. They're 2 different things.
I mean if getting adb to work was as simple as extracting it and cd'in to that directory and running adb shell, why wud google make us install drivers ? Btw AdbWinUsbApi.dll is not the driver, its the dll that adb uses to communicate with the usb drivers of windows, then windows redirects it to ur phone. Here are the contents of usb_driver which u get when u download the sdk.
amd64 (64 bit drivers)
androidwinusb86.cat
androidwinusba64.cat
android_winusb.inf (part of the driver that guides windows depending on ur os (64/32) to the appropriate folder)
i386 (32 bit drivers)
source.properties
but tell my why is it working for me and others?
Hmm it could be possible that he has windows setup to automatically find and install drivers
Sent from my iPhone using Tapatalk

Trying to sideload, error message. Help!

Says my phone is connected fine and everything, but when I click on install (android central sideloader app) I get this:
adb is not recognized as an internal or external command, operable program or batch file.
How do I fix this?
download sdk from google place the apk in the tools folder shift+right click on tools open command prompt.
adb devices (make sure your phone is connected with charge only and debugging on)
adb remount
adb push ./(apk name) (space)/system/app
mudknot2005 said:
download sdk from google place the apk in the tools folder shift+right click on tools open command prompt.
adb devices (make sure your phone is connected with charge only and debugging on)
adb remount
adb push ./(apk name) (space)/system/app
Click to expand...
Click to collapse
Can you put that in noob wording? lol
brian85 said:
Can you put that in noob wording? lol
Click to expand...
Click to collapse
Download Android SDK from here: http://developer.android.com/sdk/index.html
Extract it
Find Tools Folder in SDK Directory - copy/paste apk file in this folder.
click tools folder - press shift + Right to open command prompt
in command prompt type: adb devices then enter (this will make sure your phone is recognized and in the right state so you can continue)
in command prompt type: adb remount then enter (for lack of better terms...this prepares your phone)
in command prompt type: adb push ./(apk name) (space)/system/app then enter (this will transfer the apk to your phone.)
Ok I think that's right...I'm still learning adb and all involved. If I'm wrong, one of you more experienced guys correct me.
the phone also needs to be in charge only and go to settings>applications>debugging, debugging will have to be on.
mudknot2005 said:
the phone also needs to be in charge only and go to settings>applications>debugging, debugging will have to be on.
Click to expand...
Click to collapse
Already did that.
brian85 said:
Says my phone is connected fine and everything, but when I click on install (android central sideloader app) I get this:
adb is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
let me guess: Is the Ac_SWM folder on your desktop?
It needs to be in the root directory of your C: drive since the batch files are looking there.
In other words, it needs to be c:\AC_SWM, not "c:\documents and settings\<yourname>\desktop\ac_swm"

Super Noob question

I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?
I just made a folder in my c drive called ADB, and placed the entire folder with adb and the dll files required in it, along with superuser, busybox, etc.
Right click on command prompt and run as administrator.
once at system32 type: cd C:\ADB
then you will have navigated to the folder containing your ADB files.
your command prompt should now read: C:\ADB
then you can type: adb devices
it will say something about starting daemon services, and then list attached devices.
you are free to proceed with whatever instruction or operation you are doing after that.
also, make sure you have the drivers for the phone installed, or your computer wont recognize the android debugging bridge.
LowRentTechGuy said:
I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?
Click to expand...
Click to collapse
Android Development is not for questions or Problems
Please post in the correct Forums
Moving to General
Well thanks for moving it, I will keep a closer eye on which forum I am browsing when I post.
Sent from my SCH-I510 using Tapatalk

[Q] Noob Root Walkthru

I am new to the ASUS family of tablets, and j just can't figure out how to root. I have rooted many tablets and installed custom roms before but the i cannot follow the how tos listed here. For one fastboot doesnt work on my computer. It opens and closes immediately. What i would like is a detailed step by step guide with a trouble shooting guide. I mean now i reading about downgrading, blob files and a few other things i never dealt with on my galaxy. Someone help......would love to root this thing. Email me if u want [email protected]
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Check this thread, it has videos about rooting and whatnot, hope it helps:
http://forum.xda-developers.com/showthread.php?t=1663244
Northern-Loop said:
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Click to expand...
Click to collapse
Yes, Bootloader is unlocked. Ok, so I tried the flashboot command, so now what? I typed the command from the walkthru "fastboot -i 0x0B05 flash recovery recovery.img " but get an errorcannot load recovery.img. So what am I missing. I have the recovery image on my desktop.....
Put the recovery image in the same folder as your fastboot application and it should work.
xAshxMoneyx said:
Put the recovery image in the same folder as your fastboot application and it should work.
Click to expand...
Click to collapse
....what fastboot folder? I installed the ADK per the instructions, I downloaded the root and recovery image. I looked in the system for a fastboot folder and do not see it. Plus when I try to type in the fastboot command now, it says it is not a recognized command. I am sure this is something simple, but I am just not getting it. Is there a more detailed step by step somewhere that will actually walk you thru the steps without assuming you know what they are talking about? I can root my phone, my galaxy tab all day long and install and change ROMS, but this one has me upside down.
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
xAshxMoneyx said:
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
Click to expand...
Click to collapse
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
xAshxMoneyx said:
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
Click to expand...
Click to collapse
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
tccc143 said:
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
Click to expand...
Click to collapse
Ok, so reinstalled everything.....did a quick refresher on CMD directions and had it rooted with CWM in 10 minutes. I have been working in Android so long without the use of a PC that I forgot how to use the PC. Thanks for the help....now we wait for some nice roms.
Sweet, glad you got it, I've done this stuff a few times but I always have to refresh myself and take it slow on each different device.
tccc143 said:
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
Click to expand...
Click to collapse
You should not move the folder. This can cause all kinds of problems. in the cmd prompt just type
cd \folder\folder\etc.
The cd means change directory and you start off with a backslash to set the initial path to the root of your drive. if folder names include spaces then wrap the path with quotes, cd "\folder one\folder two\etc". the prompt should change from C:\windows or whatever to what you typed in.
if you've installed on a drive other than C: then first change to that drive by typing the drive letter followed by a colon, ie D:
Good old DOS will never die.
Sent from my SCH-I510 using XDA

windows 8.1 won't recognize fastboot

running windows 8.1. Adb & fastboot don't work anyone got drivers and instructions on how to install them plz.
thanks
download android sdk, open command prompt inside directory with adb and fastboot, and run it. Should work, as nothing drastic changed in 8.1
ethantarheels123 said:
download android sdk, open command prompt inside directory with adb and fastboot, and run it. Should work, as nothing drastic changed in 8.1
Click to expand...
Click to collapse
That info does not work for me. Opens the prompt, screen scrolls ultra fast with some words, then closes. Been reading and trying to figure this out.
I've heard that there's a compatibility issue between fastboot and Windows 8.1, I'm not sure it's been resolved yet.
Sent from my Evita
Did you update your SDK Tools? That might help, it installed a lot of missing folders for me and fixed a lot of probems.
Go into the sdk directory and open the "SDK Manager" program, then press the update/install button.
If that doesn't help, then hopefully you can get your issue resolved some other way.
Goodluck
mentalityx said:
That info does not work for me. Opens the prompt, screen scrolls ultra fast with some words, then closes. Been reading and trying to figure this out.
Click to expand...
Click to collapse
You have to hold shift and right click, opening a command window. Then type fastboot, then fastboot devices and you should see HTC folowed by some numbers.Or did you get it working?

Categories

Resources