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.........
Code:
Galaxy Ace Android Kitchen
1.- Download the kitchen from here.
2.- Copy system.rfs and CF-Root-S5830's boot.img (for ext4 filesystem support) to the kitchen's original_update folder, rename system.rfs to system.img.
3.- Open up a terminal window, change to the folder containing the kitchen.
4.- Start up the kitchen by typing: ./menu
I want to start creating a rom using the manual Ketut, but I have a doubt over 3, indicates that you have to open a terminal window, but refers to the normal window of win7 or cygwin? win7 on the window did not recognize the command ./menu, which is not a valid file and cygwin does not allow me to enter the kitchen folder, and if anyone can guide me what are the right steps in this option were very grateful thank you!
tazlooney89 said:
Code:
Galaxy Ace Android Kitchen
1.- Download the kitchen from here.
2.- Copy system.rfs and CF-Root-S5830's boot.img (for ext4 filesystem support) to the kitchen's original_update folder, rename system.rfs to system.img.
3.- Open up a terminal window, change to the folder containing the kitchen.
4.- Start up the kitchen by typing: ./menu
I want to start creating a rom using the manual Ketut, but I have a doubt over 3, indicates that you have to open a terminal window, but refers to the normal window of win7 or cygwin? win7 on the window did not recognize the command ./menu, which is not a valid file and cygwin does not allow me to enter the kitchen folder, and if anyone can guide me what are the right steps in this option were very grateful thank you!
Click to expand...
Click to collapse
You need to use cygwin and change to the kitchen folder. For ex - if your kitchen folder is in F:/ drive, then you need to give this command
cd F:/Kitchen
And then type ./menu
Sent from my GT-S5830 using iOS ROM
thanks, now I have another problem to make the switch from system to ext4 file opens I system.img, cygwin is in admin mode but even if I fail to convert the system
tazlooney89 said:
thanks, now I have another problem to make the switch from system to ext4 file opens I system.img, cygwin is in admin mode but even if I fail to convert the system
Click to expand...
Click to collapse
Ketut's binary file can format to ext4
Herpderp Adreno + Tegra.
This is mainly for the users of my animations who were asking! - Have fun guys!
If you are rooted:
1. Download a root explorer app (ES File Explorer is suggested and free)
2. Enable root directory (in ES File Explorer hit menu, go to settings, and check "Up to Root", then go farther down and check "Root Explorer". Accept any Superuser requests.
3. Go back to your explorer and navigate to where you downloaded the "bootanimation.zip" file. Copy (or cut) it.
4. Navigate as far up as you can into your root directory, and then to /data/local/
5. Paste your "bootanimation.zip" file into /data/local/ (it MUST be named bootanimation.zip)
6. Reboot and enjoy!
Alternatively, you can put it in /system/media, HOWEVER, make sure you back up your stock bootanimation.zip (rename it to bootanimation.zip.bak or move it to your sdcard somewhere) in case something goes wrong.
If you are not rooted (or rooted, this method works with both)
**PC only! I'm not sure how to set the Max OSX terminal to accept "adb" commands by default!**
Setup:
1. Download the newest Android SDK
2. Click the start menu, right click "Computer", and click "Properties"
3. Click "Advanced System Settings" on the left (On Win7)
4. In the advanced tab, click "Environment Variables"
5. In the system variables window, find "Path", select it and click "edit"
6. At the end of the bottom line, paste:
For 64-bit users:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
For 32-bit users:
Code:
;C:\Program Files\Android\android-sdk\platform-tools
7. Click OK.
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device)
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe"
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code:
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
4. Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
NOTE: Alternatively for part 2 you can type "adb push ", open windows explorer, and drag the file infront of the command which will give you the path without having to type it in or navigate to it.
5. Be patient, when it is done it will say something like "X kb/s (X bytes) in X seconds"
6. You can test to see if you did it correctly by rebooting manually or entering
Code:
adb reboot
7. If you no longer want a custom bootanimation, just enter
Code:
adb pull /data/local/bootanimation.zip C:\
Remember to look in your main HDD directory and delete the bootanimation.zip file if it in fact did show up there for some reason.
Note: if it STILL does not revert to the stock boot animation after doing this step, type
Code:
adb shell
cd /data/local
rm bootanimation.zip
**If you have adb problems or questions, I'm not the one to ask, Google is
Thank you for thanking me!
I was completely unaware you could change your boot animation unrooted, thanks
Sent from my Transformer Prime TF201 using Tapatalk 2 Beta-5
Thanks for this.
I thought it could not be done without a un-rooted Prime.
Thanks for this! Wasn't planning on rooting my Prime just yet and it's great that I can change the boot animation!
If you do copy a bootanimation.zip to the data/local directory do you have to do anything to the Original bootanimation.zip in the system/media Directory?
Sent from my Transformer Prime TF201 using Tapatalk
RonH54 said:
If you do copy a bootanimation.zip to the data/local directory do you have to do anything to the Original bootanimation.zip in the system/media Directory?
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
Nope! It stays there safe and sound and will start playing again as soon as you remove the one from /data/local!
Nolam20 said:
Nope! It stays there safe and sound and will start playing again as soon as you remove the one from /data/local!
Click to expand...
Click to collapse
Thanks. I had always just renamed my bootanimation.zip file and copied new one to the system/media directory but with these Bigger File size bootanimation.zip I was getting error that there not enough room to copy some of these bootanimation.zip files to the system/media directory.
Thanks
lovit
Awesome Workaround, but I have a little problem
I'm trying to get this working, but when I type in the commands in cmd, it says the adb is not recognized as a command. Help?
theManchur said:
I'm trying to get this working, but when I type in the commands in cmd, it says the adb is not recognized as a command. Help?
Click to expand...
Click to collapse
Make sure you've correctly done steps 3-7 of setup, otherwise cmd.exe will not know what to do with adb commands.
i always put my bootanimations in system/media and make sure your permissions are set like this
Uploaded with ImageShack.us
blaxican25 said:
i always put my bootanimations in system/media and make sure your permissions are set like this
Uploaded with ImageShack.us
Click to expand...
Click to collapse
His problem appears to be something different.
Can't get past the CMD command section. more detail help for us no bodies
Nolam20 said:
This is mainly for the users of my animations who were asking! - Have fun guys!
If you are rooted:
1. Download a root explorer app (ES File Explorer is suggested and free)
2. Enable root directory (in ES File Explorer hit menu, go to settings, and check "Up to Root", then go farther down and check "Root Explorer". Accept any Superuser requests.
3. Go back to your explorer and navigate to where you downloaded the "bootanimation.zip" file. Copy (or cut) it.
4. Navigate as far up as you can into your root directory, and then to /data/local/
5. Paste your "bootanimation.zip" file into /data/local/ (it MUST be named bootanimation.zip)
6. Reboot and enjoy!
Alternatively, you can put it in /system/media, HOWEVER, make sure you back up your stock bootanimation.zip (rename it to bootanimation.zip.bak or move it to your sdcard somewhere) in case something goes wrong.
If you are not rooted (or rooted, this method works with both)
**PC only! I'm not sure how to set the Max OSX terminal to accept "adb" commands by default!**
Setup:
1. Download the newest Android SDK
2. Click the start menu, right click "Computer", and click "Properties"
3. Click "Advanced System Settings" on the left (On Win7)
4. In the advanced tab, click "Environment Variables"
5. In the system variables window, find "Path", select it and click "edit"
6. At the end of the bottom line, paste:
For 64-bit users:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
For 32-bit users:
Code:
;C:\Program Files\Android\android-sdk\platform-tools
7. Click OK.
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device)
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe"
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code:
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
4. Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
NOTE: Alternatively for part 2 you can type "adb push ", open windows explorer, and drag the file infront of the command which will give you the path without having to type it in or navigate to it.
5. Be patient, when it is done it will say something like "X kb/s (X bytes) in X seconds"
6. You can test to see if you did it correctly by rebooting manually or entering
Code:
adb reboot
7. If you no longer want a custom bootanimation, just enter
Code:
adb pull /data/local/bootanimation.zip C:\
Remember to look in your main HDD directory and delete the bootanimation.zip file if it in fact did show up there for some reason.
Note: if it STILL does not revert to the stock boot animation after doing this step, type
Code:
adb shell
cd /data/local
rm bootanimation.zip
**If you have adb problems or questions, I'm not the one to ask, Google is
Thank you for thanking me!
Click to expand...
Click to collapse
riorancho said:
Can't get past the CMD command section. more detail help for us no bodies
Click to expand...
Click to collapse
What specifically are you having trouble with?
Section 7 and down. I am not that dos smart to understand what you substitute in the cmd screen and I don't even know if my zip file is correct. I had it on my desktop then in c: adk\tool folder but I can't get any further than completing line 6 set up. Compressed with no compression using winzip.
And I really don't know if my txt file is correct?? My image size is 960 x 540
Using a Razr Maxx. site won't let me download the win zip file
Nolam20 said:
What specifically are you having trouble with?
Click to expand...
Click to collapse
riorancho said:
Section 7 and down. I am not that dos smart to understand what you substitute in the cmd screen and I don't even know if my zip file is correct. I had it on my desktop then in c: adk\tool folder but I can't get any further than completing line 6 set up. Compressed with no compression using winzip.
And I really don't know if my txt file is correct?? My image size is 960 x 540
Using a Razr Maxx. site won't let me download the win zip file
Click to expand...
Click to collapse
I'm not really sure how exactly I can help you, I'd go over the guide a few more times and google your problem.
I need specific problems like errors or what you don't understand.
Also, I don't know the size for a Droid Razr, but you can probably find it via a quick search.
I get lost here
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device) OK
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe" OK
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code: LOST RIGHT HERE WITH THE PROPER COMMAND
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
what command do I put in in cmd at this point?
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
and then:
Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
what is this command above??
Where do I save my boot zip file to??
Nolam20 said:
I'm not really sure how exactly I can help you, I'd go over the guide a few more times and google your problem.
I need specific problems like errors or what you don't understand.
Also, I don't know the size for a Droid Razr, but you can probably find it via a quick search.
Click to expand...
Click to collapse
riorancho said:
I get lost here
Process:
1. Plug in your device using a USB cable and enable USB Debugging (in the settings menu under development on your device) OK
2. Click the start menu, and either search for "cmd" or click run, and type "cmd.exe" OK
3. Navigate to the folder that you downloaded the bootanimation.zip file to using the following commands:
Code: LOST RIGHT HERE WITH THE PROPER COMMAND
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
what command do I put in in cmd at this point?
dir - lists all files in the directory stated
cd - changes directory to the given path. If "cd ..", it will navigate one folder backwards.
and then:
Use the following commands (your file must be named bootanimation.zip)
Code:
adb pull /data/local/bootanimation.zip C:\
adb push bootanimation.zip /data/local
what is this command above??
Where do I save my boot zip file to??
Click to expand...
Click to collapse
Ok, so, for example, if your file is in user/Fred/Documents and named bootanimation.zip, then you need to type:
Code:
cd users
then
Code:
cd Fred
then
Code:
documents
then type
Code:
adb pull /data/local/bootanimation.zip
Then
Code:
adb push bootanimation.zip /data/local
part of the problem may be that I have a mac and use windows under parellas so the files are not the same
in c: Users\DT\Documents DOCUMENTS IS WHERE ZIP FILE IS LOCATED
get error message: "adb" is not reconized as an internal or external command operabtle program or batch file
Nolam20 said:
Ok, so, for example, if your file is in user/Fred/Documents and named bootanimation.zip, then you need to type:
Code:
cd users
then
Code:
cd Fred
then
Code:
documents
then type
Code:
adb pull /data/local/bootanimation.zip
Then
Code:
adb push bootanimation.zip /data/local
Click to expand...
Click to collapse
riorancho said:
part of the problem may be that I have a mac and use windows under parellas so the files are not the same
in c: Users\DT\Documents DOCUMENTS IS WHERE ZIP FILE IS LOCATED
get error message: "adb" is not reconized as an internal or external command operabtle program or batch file
Click to expand...
Click to collapse
Then you didn't follow steps 2-7 correctly.
2. Click the start menu, right click "Computer", and click "Properties"
3. Click "Advanced System Settings" on the left (On Win7)
4. In the advanced tab, click "Environment Variables"
5. In the system variables window, find "Path", select it and click "edit"
6. At the end of the bottom line, paste:
For 64-bit users:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
For 32-bit users:
Code:
;C:\Program Files\Android\android-sdk\platform-tools
7. Click OK.
This guide is for windows, if you're having problems getting it to work on Mac or a virtual Windows machine, I'm sorry but I can't help you.
my ADB will not work at all in command prompt i get this message 'adb' is not recognized as an internal or external command,
operable program or batch file.
thats what i get when i enter adb devices in the command prompt whether i have a device plugged in or not
I'm assuming that since you're asking about adb, you already have the Android SDK installed (or) you have a folder that you downloaded from somewhere with adb.exe, fastboot.exe and some other exe's in it. The reason you're getting that message is because your computer doesn't know where to look for adb.exe, unless you open command prompt in the folder itself. To be able to use the command universally in cmd, you need to add it to the Windows PATH system variable.
1. Control Panel->Search 'environment variables'->Click on 'Edit the system environment variables' with the administrator icon.
2. Click on 'Environment Variables' at the bottom, find Path (or) PATH under 'System variables', and click Edit.
3. Here, you need to provide the path to where the tools and platform-tools folders of the Android SDK are located, or to the location of the folder which contains adb.exe (if you have it that way instead of the SDK). There will already be some paths here for other stuff, each separated by a semicolon. Make sure that the previous path has a semicolon at the end before putting in your path. For example, the end of my path variable is - <previous paths>;F:\Programs\adt-bundle-windows-x86_64\sdk\tools;F:\Programs\adt-bundle-windows-x86_64\sdk\platform-tools
4. That's it. Now adb and fastboot will work in cmd anywhere from your computer (no need to be in the adb folder).
sashank said:
I'm assuming that since you're asking about adb, you already have the Android SDK installed (or) you have a folder that you downloaded from somewhere with adb.exe, fastboot.exe and some other exe's in it. The reason you're getting that message is because your computer doesn't know where to look for adb.exe, unless you open command prompt in the folder itself. To be able to use the command universally in cmd, you need to add it to the Windows PATH system variable.
1. Control Panel->Search 'environment variables'->Click on 'Edit the system environment variables' with the administrator icon.
2. Click on 'Environment Variables' at the bottom, find Path (or) PATH under 'System variables', and click Edit.
3. Here, you need to provide the path to where the tools and platform-tools folders of the Android SDK are located, or to the location of the folder which contains adb.exe (if you have it that way instead of the SDK). There will already be some paths here for other stuff, each separated by a semicolon. Make sure that the previous path has a semicolon at the end before putting in your path. For example, the end of my path variable is - <previous paths>;F:\Programs\adt-bundle-windows-x86_64\sdk\tools;F:\Programs\adt-bundle-windows-x86_64\sdk\platform-tools
4. That's it. Now adb and fastboot will work in cmd anywhere from your computer (no need to be in the adb folder).
Click to expand...
Click to collapse
ive done all that im just going to erase everything and run usbdeview and start over
you need to add the location of adb.exe to the path in your windows. with a default android sdk install, I added ";C:\Users\pat\AppData\Local\Android\android-sdk\platform-tools" to the end of my system path. then you need to reboot. (change the pat part to whatever your username is)
[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