Good evening!
Today I was a little bored, so I created simple ADB & Fastboot command line procesor.
I'm not really sure that this application is practical.
Description
You don't need to type "adb" or "fastboot" everytime. If CLP shows "ADB >> ", then type command you want to run, for example "shell ls /data/app".
I have no time for descripting this app, just use it and check out.
Works only with Windows.
SourceForge project page: sourceforge.net/projects/adbfastbootclp/
Related
1. Linux(easy)
2. Mac(easy)
3. Windows(medium)
________________________________________________________
1. Linux
You don't need any special drivers for SDK on linux(adb shell), but you don't get fastboot binary in SDK package. To set fastboot for linux follow instructions:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot linux binary
http://www.mediafire.com/?ldlovlzi9mx3pbh
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
if you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it?
Copy this file to /etc/udev/rules.d
EDIT:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Easy?
______________________________________________________________
2. Mac
I don't have Mac, but it should be like for linux:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot Mac binary:
http://www.mediafire.com/?kjozh1q5dyyqhn3
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
(I don't know that this is possible on Mac, try to change nautilus with Mac's default file browser?)If you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it? Easy?
______________________________________________________________
3. Windows
1. Download SDK
http://developer.android.com/sdk/index.html
2. Download Google USB Drivers from SDK Manager
3. After download, there're located in /path_to_your_SDK_directory/extras/google/usb_driver
4. Open android_winusb.inf and add this after [Google.NTx86] or [Google.NTamd64](32 bit or 64bit)
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
(Here is my modificated android_winusb.inf file here, but it's old and an updated version arrived from Google and it's compatible with 32bit and 64bit)
5. Open CMD from Start>Run and type:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
6. Reboot
==========================================================
7. On tablet go to Settings > Applications > Development and enable USB Debugging if it wasn't enabled and connect tablet with computer via USB.
8. Right-click on Computer and click Manage. Identify your device from the list(I think it's Tegra with board icon), right-click it and click Update Driver Software
9. Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer
10. Choose to view all devices and click Have Disk
11. Browse to the google-usb_driver folder inside your Android SDK folder(/path_to_your_SDK_directory/extras/google/usb_driver) and select the android_winusb.inf file
12. If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing
13. Once the drivers have been installed, you should be able to use ADB with your device
14. To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB
For fastboot you need to go to /path_to_your_SDK_directory/platform-tools in terminal(cd /path_to_your_SDK_directory/platform-tools) and type fastboot(.exe) <action> and before it to change ADB Interface to ADB
That's it, if you have some complaints, post them.
Bye!!!
EDIT: Changed android_winusb.inf file due error in it.
EDIT2:Changed android_winusb.inf file due error in it again.
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
shut the cmd say something ? because when i write the command and push enter its just jump to another line and says nothing ???
No. You can go to that file("%USERPROFILE%\.android\adb_usb.ini") and manualy add 0x955 to it.
Sorry!
I cannot connect to this link:http://www.mediafire.com/?kjozh1q5dyyqhn3
Please do me a favor, send fastboot as an attachment to this mail address:
[email protected]
I'll try because I'm not at home, I went to my grand parents and I have really slow internet.
Hello guys I have a problem, the step 5. Open CMD from Start> Run and type:
echo 0x955>> "% USERPROFILE% \. Android \ adb_usb.ini"
I run this step but I open a txt file that says this:
Android # USB Vendor ID 3RD PARTY LIST - DO NOT EDIT.
# USE 'adb Android update' TO GENERATE.
USB Vendor ID # 1 FOR LINE.
0x955
I now do not understand where I write echo 0x955?
/documents_and_settings/[your user name]/.Android(hidden file)/adb_usb.ini
Sent from my Xoom using Tapatalk
Nice guide. Think you forgot the udev rule for Linux:
Create a file called /etc/udev/rules.d/51-android.rules containing:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
Without that Linux won't give you write permission to the device.
Ok, I'll add.
Sent from my IDEOS S7 Slim using XDA App
So when I want to use fastboot, I install the Android Bootloader Interface driver? Not the ADB interface driver?
Needless to say I haven't got fastboot working yet but ADB works. One other thing: If I manage to install a firmware and do a wipe and everything works; can it be that I would experiance better performance if I as well managed to to a full wipe with fastboot? I mean, can it flush things that CWM can't? I'm using the latest cyanogenmod (test version) from DerArtem, but I am a bit interested in trying the latest progress of honeycomb...
I have problems with interfaces. On one computer is ADB interface and on other is something else but I prefer linux for doing any job that's connected with android. In theory wiping should be same with fastboot and recovery but, again, I prefer fastboot because it's JUST erase all on data/cache/system partition and recovery might don't have support for other partition types as well as other problems, but I don't say that it can be different.
Thanks. I hope I continue to have a functioning cwm. If it breaks I will have to install Linux
ı do everything but when ı wrote adb devices nothing
Linux or Windows?
Jon2555 said:
Linux or Windows?
Click to expand...
Click to collapse
windows 7 x64
When the tablet is open in USB Debugging mode I can see my device adb devices list but when ı restart my tablet fastboot mode ı can't find
The best slow to install Linux via VM. It complicated on windows, it's different from computer to computer.
Sent from my IDEOS S7 Slim using XDA App
do i type this exactly with all the " ???
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
????????????????/
HELP PLEASE
No
Sent from my IDEOS S7 Slim using XDA App
When i tipe the echo 0x955 line
It keeps on saying that system cannot find the path specified
can someone please help?
even when i open comand prompt and type adb it says adb is not recognised as an internal or external.........
For the past couple of days I have issues with transferring files over usb as no support is built into to the ics kernel for the usb transfer unless a physical sdcard is detected. I tried the mtp, thing and for some reason that wont show the files. Here is what I found that works best for transferring files rather than installing sketchy Chinese programs.
Note all commands are in quotes, do not type the quotes
Setting up and checking files in directories
1. Install androidsdk
2. open a command prompt and cd to where your adb tools are. They are typically in C:\android-sdk-windows\platform-tools
3. "cd C:\android-sdk-windows\platform-tools" after you download the pack through the platform tools pack through the sdk manager. Yours may be in a different place depending on install. If you have set the system variable for adb skip to step 4.
4. Set your touchpad to go into android debugging mode when plugged in, under developers options
5. Type in "adb devices" to make sure your touchpad is seen by computer
6. Now access your devices by typing "adb shell" (if you have the ghost emulator 5554, use adb -d shell)
7. From there type "cd /sdcard/"
8. Type "ls" to receive a list of all files on your touchpad (note l is an L)
9. From there simply use the cd command to get in and out of directories
Transferring Files
When you want to transfer files to and from the touchpad, open a new command prompt and get back to the location with your adb files.
To copy to touchpad
Use the adb push command, example of adb push:
"adb push C:\users\stephen\downloads\example.apk /sdcard/"
The format is adb push local directory to remote directory.
To pull from touchpad
To pull something from your touchpad use adb pull command. The format is adb pull remote directory to local directory.
Example: "adb pull /sdcard/getjar.apk c:\users\stephen\desktop"
I installed DroidSSHd for root GUI. and for GUI file transfer/install I use AirDriod.
edit: course, all this is done on the air.
Hello,
I just find out why I cannot use adb... AS100 have different VID/PID, so the usb driver just won't install in Windows.
Code:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&MI_01
I've edited android_winusb.inf and repacked a toolkit that should work for both AS100 and folio.
The file size is (slightly) larger than 8MB,so I uploaded it to mediafire:
http://www.mediafire.com/?44gzifauee07u9j
Including adb usb driver, fastboot and adb command.
---
Use fastboot:
boot your toshiba AS100/folio
when you see toshiba logo, press power 3 times and vol+ 1 time to enter fastboot mode.
you should see "Starting Fastboot USB download protocol..." on screen.
connect tablet to PC with USB.
install usb driver in Windows.
open cmd console in Windows
cd to where you put the tools folder, e.g. cd D:\toshiba\folio-toolkit\tools
run "fastboot devices" (without quotes)
if you see "? fastboot" in console, the tablet is connected and you can use fastboot to flash images.
(run "fastboot help" to see a list of usable commands)
---
Use adb:
boot your toshiba AS100/folio into android.
make sure usb debug option is checked.
connect tablet to PC with USB.
install usb driver in Windows.
open cmd console in Windows.
cd to where you put the tools folder, e.g. cd D:\toshiba\folio-toolkit\tools
run "adb start-server" (without quotes)
run "adb devices"
you should see the following in Console:
Code:
List of devices attached
0123456789ABCDEF device
(run "adb help" to see a list of usable commands)
---
Adb troubleshooting:
If you see "0123456789ABCDEF offline" when you run adb devices, try the following:
Code:
adb kill-server
adb start-server
If it still not works, try reboot the tablet again when connected with USB.
---
About AS100: basically it's as same as folio 100, with 1GB on board RAM.
totally lost
Sorry guys, Im totally lost, trying to fastboot my folio and was gonna install a fresh rom. I need thorough instuctions. Not all of us are wizkids, for example, its not enough for me to just write "do this" or "do that", i need to know HOW to do things, like my name says, Im a noobie
Come on you guys, help the clueless ppl
[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
mamba_nz said:
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
Click to expand...
Click to collapse
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
Thank you so much!
For some reason, that zip still reports ADB version 1.0.29.
I found the latest version (1.0.31) from https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/. It has zips for linux, mac and windows adb.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
thanks that works fine 4 me
Hi all,
I am trying to unlock bootloader on my Xperia XZ1 compact. Followed all the exact steps on the "sony developer how to unlock bootloader" website and checked out different guides and tutorials. I installed lineage OS on my previous phone (Lenovo P2), so I made it work at least once in the past.
So:
unlock bootloader is allowed on the phone
USB and OEM debugging are turned on
downloaded and installed the latest firmware and USB drivers
download platform tools with ADB and fastboot
I put my phone into fastboot mode (volume up and power button), the blue led is turned on wich supposedly means that it is in fastboot mode
I open up a powershell (run as administrator) etc. and give the 'fastboot devices' command -> which then returns nothing.
Any suggestions? Am i overlooking something?
thanks for your help!
Meat
note: I use ".\fastboot devices" as the actual command, since i get this error if i do not use ".":
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot devices
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\fastboot".
Hi , if it says fastboot is not recognized means that the path from fastboot terminal is not found .
To fix this you can add path for fastboot or install minimal ADB&Fastboot terminal from here on your PC:
https://androidfilehost.com/?fid=746010030569952951
How to install see here:
https://forum.xda-developers.com/showthread.php?t=2317790
Also instead powershell you can use command prompt .
So Run Command prompt as administrator and directory will be :
C:\Windows\System32 >
change directory to location where you installed ADB &Fastboot terminal for example C:\adb by typing
cd C:\adb
Once you do that your fastboot and adb commands should work fine ...
Good luck