Related
Ok there are some other guides here on the forums for this but they all require you to download the Android SDK. That can be very time consuming and confusing if you run into issues. I have been looking at a way to have the capability to push and pull files using my laptop but i really didnt want to go through downloading and setting up the whole SDK just to use adb.
If anyone has followed any of my threads, you know I am all about trying to get things done in the easiest way possable to help the people that are new to Android. This method has worked for me but there is no guarentee that it will work for you and I am no way responsable for anything that happens to anything unless it works great for you. Then I will take all credit j/k. With that being said:
The first method is for Windows based OS. I have tested it on XP but I would imagine it will work on any Windows OS. If I am informed of something different I will update it here. The Mac version is in post #2 and takes less than 1 minute to do. Much thanks to kwbdc and stlouie65 for the help on this.
Instructions for setting up Adb/Fastboot (windows)
1. On your phone go to Settings/Applications/Development and make sure USB debugging is ON and plug it in via the usb..
2. Install drivers on your PC. This is done on the MT4G/HTC devices by going onto your sd card and clicking on the HtcDrivers.exe file while viewing the files on your PC. It should automaticly install them to your PC. If you are using another phone or have trouble installing the ones from your sd card you can try pda.net or HTC Sync for the drivers. Here are links for pda.net 32-bit Windows 7/Vista/XP and for 64-bit Windows 7/Vista. Install the program by hitting "Run" and follow the instructions. You can remove it at a later time.
3. Download the file at the bottom of these instructions to your desktop and extract the contents. There is 1 folder and a install note (these instructions) that should extract. You can use a program called 7-ZIP (google it, its free and a great tool).
4. Open your "Start" menu and click on "My Computer". Then choose "Local Disk C:".(You can now click and drag the adb folder you extracted to the C: drive.
5.Open a command prompt and type cd\adb and hit enter. You should now see something that looks like this C:\adb>
6.Type adb devices then hit enter in the command prompt and it should list your device.
7. You can also type fastboot devices then hit enter in the command prompt an it should list your device. (you must be in the bootloader for fastboot to recognize your device)( adb command= adb reboot bootloader )
You should now be ready to send commands to your phone via ADB or Fastboot. You will need to repeat steps 5-6 anytime you want to use ADB/Fastboot. To send a file using Adb or fastboot make sure to put the file in your "adb" folder before giving the command to send it to your device.
If this helped you please use the "Thanks" button to show your gratitude.
____________________________________________________________________
Please feel free to ask any questions you want and I will help in any way I can.
DOWNLOAD MIRROR
Here are some commands for Adb/Fastboot.
DO NOT USE ANY COMMANDS THAT YOU ARENT SURE OF OR DONT KNOW WHAT THEY DO. I AM NOT RESPONSABLE FOR ANYTHING THAT YOU DO TO YOUR PHONE.
ADB Commands
adb devices - list all connected devices
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections forward specs are one of: tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed
Click to expand...
Click to collapse
.
Fastboot Commands
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Click to expand...
Click to collapse
Mac Instructions
Download THIS FILE Extract the 2 files inside it and place them on your Macintosh HD root. Plug in your phone to the usb, open terminal and type /adb devices.
It should now give u a serial #
To send a file using adb/fastboot the file must be placed in your mac HD Root or you must give the location in your command path.
Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again
92drls said:
Wow this is so easy, thanks man. Only thing is, you said download the contents at the bottom of the post. where'd it go?
Edit: Oh the big Download spinning button.. I don't know how I missed it. Thanks again
Click to expand...
Click to collapse
Not a prob...Please let me know if this works good for you.
Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?
92drls said:
Just got back home and tried it. I'm prolly doing it wrong but it says exactly: c:\adb> push c: \adb\480x800_animationparticles1_blue.zip / data/local/bootanimation.zip hit anter and its done, gives me the size and seconds it took to transfer. I type adb reboot and it does but no go on the boot animation, same ol htc stuff
Rom: eViL-4g HD v.0.2.3
Sounds like I have adb successfully setup I just cant seem to figure out how to change the bootanimation. Know of a sure fire ways on the 4g? I could find several through other builds but not for the 4g specifically. I also tried through root explorer and emulator but no luck. Still boots the same, any help?
Click to expand...
Click to collapse
Put the file you are trying to push in the same folder you created.
ReName it bootanimation.zip
To push your file use this command after you cd into the folder you created.
You also need to be in recovery with your system mounted.
adb push bootanimation.zip system/customize/resource/bootanimation.zip
That is the location of the bootanimation on that rom.
Hope this helped
Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again
92drls said:
Worked great thank you, know how to do the splash screen image too??!
Back on topic, your adb method was very easy and well instructed. I'll be thanking you on payday
Edit: I found the thread about the splash screen by iriscience.. Thanks again
Click to expand...
Click to collapse
I do know how to change it but would rather you have the fulfillment of learning how to do it yourself You can find a great guide and splashscreens in the thread by Iriscience. Make sure to thank him for it.
Back on topic, I'm glad this worked good for you. It really is pretty simple. I dont have have a donation link (I do this for the love of helping people mod their phone) but I would appreciate it if you hit the "Thanks" button at the bottom of any post that have helped you.
Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.
@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.
30Glock said:
@trueblew, Thank you for this I follow all your threads and your always posting good Information, Your Instructions are simple and usefull. I am now ready to use adb, something I thought I would never venture In, Again Thanks.
Click to expand...
Click to collapse
geoffott said:
Thanks for this... after two years owning android phones you finally got me to jump into adb instead of relying on the terminal emulator. I had tried before, but my PC never downloaded the SDK correctly, and I could never get it set up. Your download and instructions worked flawlessly.
Question: What is everyone's favorite mod using adb/fastboot? I already changed my splash screen, but I am hooked on trying out my new tool.
Click to expand...
Click to collapse
Thanks Guys, I appreciate the kind comments! My whole intention of this thread is to help people that couldnt or didn't want to set up the Android SDK have a good solid way of pushing and pulling files to their phone.
Great guide Drew! I'll finally be giving adb a shot! I've always been intimidated by it.
This helps for sure.
Sent from my HTC Glacier using XDA App
thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?
dominicanman912 said:
thank you! i hate the sdk tools! this works much quicker for me! my only question is that when i type in "adb devices" it lists my device but when i type in "fastboot devices" it doesnt list or do anything. it just basically drops to another line for me to enter another command. does that mean that i cant fastboot?
Click to expand...
Click to collapse
You must be in fastboot (bootloader) for fastboot to recognize your device. You can get there by by turning off your phone then holding down the volume down button and the power button at the same time. Our you can use this command via adb (usb plugged in):
adb reboot bootloader
Your device should automatically go into fastboot from the bootloader. If it doesn't you can scroll to fastboot using the volume button and hit the power button.
Thank you for answering my question! I have been reading a lot about adb over the past few days and I feel more comfortable with this way than the pain in the ass sdk method! When I get back on the pc, I will be sure to hit that thanks button because you have been a great help.
Sent From my ICE COLD HTC Glacier aka MyTORCH4G!
How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153
koolkid09 said:
How do I flash a recovery using fastboot.
I have an Evo Shift and I was told I could use this method.
The recovery is here along with the vague directions. 2nd Post. http://forum.xda-developers.com/showthread.php?t=932153
Click to expand...
Click to collapse
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img
TrueBlue_Drew said:
Set up adb/fastboot using the instructions in the first post. put your recovery in the folder you created and make sure it is namesd recovery.img . When you have done that and adb will recognize your device you can type these commands pressing enter after each one:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you so much!! I have been trying to do this for the past hour now! lol
Awesome post! Saved me a (potentially painful) convo with a friend who's just getting into modding his MT4G.
error
I feel like an idiot, idk what im doing wrong, in command prompt i get this message, 'adb' is not recognized as an internal or external command, operable program or batch file......what am I doing wrong?
You've probably seen about a million threads saying "use ADB to x, y or z." You might have no idea how to do this, which is what I am going to help you with.
First, download the android sdk for either Mac, Windows, or Linux from here. I don't know much about Linux, so this guide will be based on Mac and Windows. Unzip the file to a place you can easily remember (i.e., Desktop or root of the HD). On Windows, download the platform-tools add-on from SDK manager. Let's start with how to "push" a file to your phone.
To start, plug your phone into the computer and select charge only mode. Turn on USB debugging in menu/settings/applications/development. Place the file you want to push in the platform tools folder in the android sdk. Open up Terminal on Mac or a command prompt on Windows. Type:
Code:
cd [insert path of android sdk here]
cd platform-tools
adb devices
adb remount
adb push [name of file] [path where you want it to go, such as "/sdcard/" or "system/app"]
That's it. You successfully pushed a file! Next, we will tackle how to pull a file from your phone for purposes such as uploading it to the UOT kitchen to theme it. Open up your command prompt or Terminal. Type:
Code:
cd [insert path of android sdk here]
cd platform-tools
adb devices
adb pull [insert path of file here, such as "system/app"]
Your apk should now be in your platform-tools folder. Now you can upload away! Here's a very simple one. This is how you reboot your phone so you don't have to take off your case and pull the battery! Just plug your phone in and type:
Code:
cd [insert path of android sdk here]
cd platform-tools
adb devices
adb reboot recovery
Now, you can restore your backup easily. You never had to pull your battery. You've probably heard a dev say something like "Hmmmm, that's weird that your phone isn't booting. Can you get me a logcat?" Well, now you will be able to. Type:
Code:
cd [insert path of android sdk here]
cd platform-tools
adb devices
adb logcat
Just copy it and paste it into a text document. You are done!
If there is anything else that people want me to include in the guide, feel free to reply and let me know. I hope that this clears some stuff up for people.
You write very good tutorials, so I have a suggestion if you have time. We are getting all the random threads with people having problems after using HTC unlock. It may help if they had a quick tutorial for installing CWM and how to flash a ROM.
I will write that up! Thanks for the suggestion.
Well, it's done! That's one long guide!
AgalychnisCallidryas said:
Well, it's done! That's one long guide!
Click to expand...
Click to collapse
I just read it, very good write up. It's a lot better than I would've been able to do. I have a hard time explaining how to do stuff lol. Now we have a thread to link to!!
Awesome guide bro thanks. Is there a possible way you can write a detail guide on how to decompile and compile apk's I believe this would help out a ton around the community
Sent from my Incredible 2 using XDA App
hi guys,,
love your forum....
simple NOOB question plzzzzzzzzzzzzz...
how do i get into fastboot,,,,
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1668159
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
My Kindle is never recognized by KFU . Here's what you need:
Android SDK
Working adb and fastboot
KFU
On windows 7 shift+right click in your KFU tools directory and click "open command window here"
Here are the commands:
adb devices (your device should be listed)
adb shell (make sure it shows up as root, there will be a #, if not su)
idme bootmode 0x4002
reboot
Then your device should be booted into fastboot mode
He could be having the same problem I had, no /system/bin/sh so the adb technique will not work. I had to make a factory cable, which got me into fastboot mode (but ROMS still are not applying right, that question is in another thread).
gdjy said:
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
Click to expand...
Click to collapse
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
SLOmtb said:
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
Click to expand...
Click to collapse
Thanks for the KFFB plug. Just as an FYI, fastboot doesn't look at the adb_usb.ini file... adb is the only thing that looks at it.
gdjy said:
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
Click to expand...
Click to collapse
I just updated my fastboot guide (the second link I gave you) with details on how to get the hardware IDs and identify whether or not you are in fastboot mode. Take a look again and see what your hardware IDs are. If that doesn't help you, post a more detailed description of what you are doing, what the device is doing, what errors you get, etc. The more details you can provide, the easier it will be for your helpers to determine what's happening. Look at the sticky post at the top of this section.
i know this is also a stupid question, but how do i issue the "fastboot oem format" command? i tried partitioning my kf but it failed....
Ive been trying to flash CWM for 2 days with no luck so finally i am asking for help.
first off i bought a VZW GNEX (toro) w/ 4.2.2 from a buddy for $20
ive tried the nexus toolkit and tried flashing manually with fastboot/adb
i can unlock bootloader no problem but everytime i try to flash CWM, toolkit or manually, it just stays on
adb devices will show my device but fastboot devices wont
i have the .img in the correct folder of platform-tools
im running linux mint 13 and id prefer to do it manually just cause im not a big fan of 1-click methods
Do I need to use the Universal Naked drivers?
any advice would be greatly appreciated and thanx in advance
Drivers do not apply in this situation.
if your device is in FASTBOOT mode, then ADB should not see it at all. Fastboot and ADB are 2 completely different modes.
if you can unlock the bootloader, then your fastboot should be working properly, since thats what is required to unlock.
boot to fastboot and give the output of
fastboot devices
Pirateghost said:
boot to fastboot and give the output of
fastboot devices
Click to expand...
Click to collapse
no output at all i hit enter and it goes right back to the command line
[email protected] ~/droid_****/android-sdk-linux/platform-tools $ fastboot devices
[email protected] ~/droid_****/android-sdk-linux/platform-tools $
DowneyJM said:
no output at all i hit enter and it goes right back to the command line
[email protected] ~/droid_****/android-sdk-linux/platform-tools $ fastboot devices
[email protected] ~/droid_****/android-sdk-linux/platform-tools $
Click to expand...
Click to collapse
do you have fastboot in your path and all is configured properly?
if you dont have your udev rules and paths set straight, it can cause issues.
try sudo ./fastboot devices
Pirateghost said:
do you have fastboot in your path and all is configured properly?
if you dont have your udev rules and paths set straight, it can cause issues.
try sudo ./fastboot devices
Click to expand...
Click to collapse
no difference with sudo
i followed a post somewhere that had me create a file /etc/udev/rules.d/51-android.rules
and add the following line to it
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
lemme guess i gotta add my device id ?????
is this my problem?
Curious to know how you unlocked the boot loader if fast boot really doesn't see the device. Can you fastboot OEM lock it back?
Sent from my Galaxy Nexus
Code:
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="username"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="username"
Change username to your own normal user, reconnect the device. Does Mint use systemd already? Then check 'journalctl -b -f' and see if its recognising the device, also check 'lsusb'.
I believe fastboot is in his path because he doesn't get a 404 and also, if he just 'chmod +x fastboot' and try to run it from any location, he would have to './fastboot command partition filename'.
Sent from my Nexus
Pirateghost said:
Curious to know how you unlocked the boot loader if fast boot really doesn't see the device. Can you fastboot OEM lock it back?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i was able to manually lock and unlock bootloader
bk201doesntexist said:
Code:
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="username"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="username"
Change username to your own normal user, reconnect the device. Does Mint use systemd already? Then check 'journalctl -b -f' and see if its recognising the device, also check 'lsusb'.
I believe fastboot is in his path because he doesn't get a 404 and also, if he just 'chmod +x fastboot' and try to run it from any location, he would have to './fastboot command partition filename'.
Sent from my Nexus
Click to expand...
Click to collapse
no systemd for mint but lsusb shows device connected
after edititng 51-android.rules problem was solved!
thanx to both of you for taking the time to help me get squared away
that is the beauty of an open source community
what ROM do you guise recommend?
DowneyJM said:
i was able to manually lock and unlock bootloader
no systemd for mint but lsusb shows device connected
after edititng 51-android.rules problem was solved!
thanx to both of you for taking the time to help me get squared away
that is the beauty of an open source community
what ROM do you guise recommend?
Click to expand...
Click to collapse
Plenty of roms here, you choose your own fate
This thread is solved, please report it to the mod team for closing, thanks.
edit: reported for closing
Thread closed
[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
I've used a mac with with all three of me nexus devices so ime pretty familiar but..is anyone else having probs with fastboot trying to flash a system.img ...I kept getting a error everytime. Boot.img would go through but not system img...? Any help would be great. If not no worries...adb seems to work fine if u need to push something ... But this is the first device I couldn't use fastboot flash system with...??
Candy Painted
matthew0776 said:
I've used a mac with with all three of me nexus devices so ime pretty familiar but..is anyone else having probs with fastboot trying to flash a system.img ...I kept getting a error everytime. Boot.img would go through but not system img...? Any help would be great. If not no worries...adb seems to work fine if u need to push something ... But this is the first device I couldn't use fastboot flash system with...??
Candy Painted
Click to expand...
Click to collapse
Did you have ADB previously installed before download this .zip? This is not the full Android SDK, but the updated version of ADB and doesn't include fastboot.
wad3g said:
...and doesn't include fastboot.
Click to expand...
Click to collapse
Perhaps all references to fastboot should be deleted, right now this thread still says "adb + fastboot...". Thanks for providing it all the same. Save me the 400mb download
Chatperdu said:
Perhaps all references to fastboot should be deleted, right now this thread still says "adb + fastboot...". Thanks for providing it all the same. Save me the 400mb download
Click to expand...
Click to collapse
You're right. I can't believe that never crossed my mind, I guess I was assuming everyone previously had ADB on their machine.
Anyway, I've updated the download links and attachments so now everything includes ADB & Fastboot files. Hopefully this will clear up any confusing in the future and I apologize to all of you who had issues due to this.
wad3g said:
You're right. I can't believe that never crossed my mind, I guess I was assuming everyone previously had ADB on their machine.
Click to expand...
Click to collapse
I have a previous installation. I am assuming fastboot doesn't have to match the adb version. Will try it out soon. My previous solution is to boot into bootloader, than adb will find the device, an inefficient work around.
Chatperdu said:
I have a previous installation. I am assuming fastboot doesn't have to match the adb version. Will try it out soon. My previous solution is to boot into bootloader, than adb will find the device, an inefficient work around.
Click to expand...
Click to collapse
Yes a previous version of fastboot should work fine. I don't believe fastboot was updated. I still use the the fastboot version that came with 1.0.29.
i followed these instructions, including creating .profile, but still neither my nexus 4 or new nexus 7 running 4.3 are recognized. Nothing is listed when I do adb devices, just an emtpy list