Related
I recently set up Ubuntu Karmic on my laptop's second hard drive, and I finished setting up Eclipse and the Android SDK yesterday. I set up ADB to work directly from the terminal without changing to the SDK Tools directory, and it works... kind of. I can get some ADB commands working, but most others won't. The only things that really work are "adb help" and "adb devices" at the moment. "adb install", "adb push" / "adb pull", and other similar commands seem to register, but then nothing happens after that- the terminal freezes, and inputting keys shows other characters. ]]^A and stuff like that. Can anyone help?
Ubuntu 9.10x64 adb works with sudo
$ sudo adb push...
I usually make sure the first adb command I use is sudo'd so it starts the daemon as root.
adb help - does not send any data to your droid. It's internal
adb device - shows which devices are on the USB bus.
The other adb command need to talk to the devices and depending on how your udev protections, device protections, and your personal group memberships are... it may not work.
sudo works for me always.
Ehud
Any way to setup a computer with ADB and Fastboot without admin rights? Can I setup up a flash drive with Fedora or Ubuntu, boot into that and get access? If so how do you set up drivers and adb on a linux distro.
Any help would be appreciated, Thanks!
I'm using Linuxmint 12 and I have ADB setup. Just click on the other platforms option and it gives you a pretty accurate description of how to set it up on linux.
I'm actually having a problem with using "fastboot oem get_identifier_token" on the bootloader unlock process because I get an error in the terminal saying the fastboot command isn't recognized in the terminal.
On Linux, I'm pretty sure all you need is the adb or fastboot executable. However, you must run it as root (either sudo or su into root). You can grab the exectuables by download the Android SDK.
If it's saying it can't find the fastboot executable, you're probably not in the same folder as fastboot. Type 'ls' and see if you see fastboot in the list. If it's not there, it won't work.
Hi,
is it just me or is there no answer to the question of the first post? Is there any way to install adb on a win Pc without admin rights?
regards
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Ironcheeks said:
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Click to expand...
Click to collapse
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Lgrootnoob said:
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Click to expand...
Click to collapse
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Ironcheeks said:
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Click to expand...
Click to collapse
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Lgrootnoob said:
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Click to expand...
Click to collapse
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Ironcheeks said:
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Click to expand...
Click to collapse
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Ironcheeks said:
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Click to expand...
Click to collapse
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Lgrootnoob said:
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Click to expand...
Click to collapse
Thank you for all your help!
There are servel cmds which we can use
But I post only top 10 cmds to help that ones who need
###############
If I make a mistake so please reply with your suggestions
And if you want a cmd in the list .submit your reply with cmd and features ( full detail as you know.).
########cmds###########
For a lot of us, the fact that we can plug our Android phone or tablet into our computer and interact with it is a big plus. Besides the times when we've broken something and need to fix it, there are plenty of reasons why an advanced Android user would want to talk to his or her device. To do that, you need to have a few tools and know a few commands. That's what we're going to talk about today. Granted, this won't be the end-all be-all discussion of adb commands, but there are 10 basic commands everyone should know if they plan to get down and dirty with the command line.
The tools are easy. If you're a Mac or Linux user, you'll want to install the SDK as explained at the Android developers site. It's not hard, and you don't have the whole driver mess that Windows users do. Follow the directions and get things set up while I talk to the Windows using folks for a minute.
If you're using Windows, things are easier and harder at the same time. The tools themselves are the easy part. Download this file. Open the zip file and you'll see a folder named android-tools. Drag that folder somewhere easy to get to. Next, visit the manufacturers page for your device and install the adb and fastboot drivers for Windows. You'll need this so that your computer can talk to your Android device. If you hit a snag, visit the forums and somebody is bound to be able to help you through it.
Now that we're all on the same page, enable USB debugging on your device (see your devices manual if you need help finding it, and remember it was hidden in Android 4.2), and plug it in to your computer. Now skip past the break and let's begin!
1. The adb devices command
The adb devices command is the most important one of the bunch, as it's what is used to make sure your computer and Android device are communicating. That's why we're covering it first.
If you're a pro at the operating system on your computer, you'll want to add the directory with the Android tools to your path. If you're not, no worries. Just start up your terminal or command console and point it at the folder with the tools in it. This will be the file you downloaded earlier if you use Windows, or the platform-tools folder in the fully installed Android SDK. Windows users have another easy shortcut here, and can simply Shift + right click on the folder itself to open a console in the right spot. Mac and Linux users need to navigate there once the terminal is open, or install an extension for your file manager to do the same right click magic that's in Windows by default.
Once you're sure that you are in the right folder, type "adb devices" (without the quotes) at the command prompt. If you get a serial number, you're good to go! If you don't, make sure you're in the right folder and that you have the device driver installed correctly if you're using Windows. And be sure you have USB debugging turned on!
Now that we have everything set up, let's look at a few more commands.
2. The adb push command
If you want to move a file onto your Android device programmatically, you want to use the adb push command. You'll need to know a few parameters, namely the full path of the file you're pushing, and the full path to where you want to put it. Let's practice by placing a short video (in my case it's a poorly done cover of the Rick James tune Superfreak) into the Movies folder on your device storage.
I copied the superfreak.mp4 file into the android-tools folder so I didn't need to type out a long path to my desktop. I suggest you do the same. I jumped back to the command line and typed "adb push superfreak.mp4 /sdcard/Movies/" and the file copied itself to my Nexus 4, right in the Movies folder. If I hadn't dropped the file into my tools folder, I would have had to specify the full path to it -- something like C:\Users\Jerry\Desktop\superfreak.mp4. Either way works, but it's always easier to just drop the file into your tools folder and save the typing.
3. The adb pull command
If adb push sends files to your Android device, it stands to reason the adb pull command gets them out. That's exactly what it does, and it works the same way as the adb push command did. You need to know both the path of the file you want to pull off, as well as the path you want it placed into. You can leave the destination path blank and it will drop the file into your tools folder to make things easy.
In this example, I did it the hard way so you can see what it looks like. The path of the file on the device is "/sdcard/Movies/superfreak.mp4" and I put it on my Windows 8 desktop at "C:\Users\Jerry\Desktop". Again, the easy way it to just let it drop into your tools folder by not giving a destination, which would have been "adb pull /sdcard/Movies/superfreak.mp4". Remember your forwards slash for the Android side, and you'll have no problems here.
5. The adb reboot-bootloader and adb reboot recovery commands
Not only can you reboot your device, you can specify that it reboots to the bootloader. This is awfully handy, as sometimes those button combos are touchy, and if you have a lot of devices you can never remember them all. Some devices (the LG Optimus Black comes to mind) don't even a way to boot to the bootloader without this command. And once again, being able to use this command in a script is priceless. Doing it is easy, just type "adb reboot-bootloader" and hit the enter key.
Most devices can also boot to the recovery directly with the "adb reboot recovery" (note there is no hyphen in this one) and some can't. It won't hurt anything to try, and if yours can't nothing will happen.
6. The fastboot devices command
When you're working in the bootloader, adb no longer works. You're not yet booted into Android, and the debugging tools aren't active to communicate with. We use the fastboot command in it's place.
Fastboot is probably the most powerful tool available, and many devices don't have it enabled. If you're does, you need to be sure things are communicating. That's where the fastboot devices command comes into play. At the prompt, just type in "fastboot devices" and you should see a serial number, just like the adb devices command we looked at earlier.
If things aren't working and you are using Windows, you likely have a driver issue. Hit those forums for the answer.
7. The fastboot oem unlock command
The holy grail of Android commands, fastboot oem unlock does one thing, and one thing only -- unlocks your Nexus device (or an HTC device using their official tool). If you're using a phone from a different manufacturer, you have a different method of unlocking things -- maybe with ODIN or .sbf files -- and this won't apply to you. We're including it because even if you don't need it, it's an important part of Android's openness. Google doesn't care what we do with phones or tablets that we've bought, and include this easy way to crack them open. That's something you usually don't see from any tech company, and a big part of the reason why many of us choose Android.
Using it is easy enough. Once you've used fastboot devices to make sure everything is communicating, just type "fastboot oem unlock" at the prompt and hit enter. Look at your device, read carefully, and choose wisely.
Protip: Using "fastboot oem unlock" will erase everything on your device
8. The adb shell command
The adb shell command confuses a lot of folks. There are two ways to use it, one where you send a command to the device to run in its own command line shell, and one where you actually enter the device's command shell from your terminal. In the image above, I'm inside the device shell, listing the flies and folders on the device. Getting there is easy enough, just type "adb shell" and enter. Once inside, you can escalate yourself to root if you need to. I'll warn you, unless you're familiar with an ash or bash shell, you need to be careful here -- especially if you're root. Things can turn south quickly if you're not careful. If you're not familiar, ash and bash are command shells that a lot of folks use on their Linux or Mac computers. It's nothing like DOS.
The other method of using the adb shell command is in conjunction with one of those Ash commands your Android device can run. You'll often use it for more advanced tasks like changing permissions of files or folders, or running a script. Using it is easy -- "adb shell <command>". An example would be changing permissions on a file like so: "adb shell chmod 666 /data/somefile". As mentioned, be very careful running direct commands using these methods.
9. The adb install command
While adb push can copy files to our Android devices, adb install can actually install .apk files. Using it is similar to use the push command, because we need to provide the path to the file we're installing. That means it's always easier to just drop the app you're installing into your tools folder. Once you've got that path, you tell your device to sideload it like this: "adb install TheAppName.apk".
If you're updating an app, you use the -r switch: "adb install -r TheAppName.apk". There is also a -s switch which tries to install on the SD card if your ROM supports it, and the -l switch will forward lock the app (install it to /data/app-private). there are also some very advanced encryption switches, but those are best left for another article.
And finally, you can uninstall apps by their package name with "adb uninstall TheAppName.apk". Uninstall has a switch, too. The -k switch will uninstall the app but leave all the app data and cache in place.
10. The adb logcat command
The adb logcat command is one of the most useful commands for some folks, but just prints a bunch of gibberish unless you understand what you're seeing. It returns the events written to the various logs in the running Android system, providing invaluable information for app developers and system debuggers. Most of us will only run this one when asked by one of those developers, but it's very important that we know how to use it correctly.
To see the log output on your computer screen, just type "adb logcat" and hit enter. Things can scroll by pretty fast, and chances are you won't find what you're looking for. There are two ways to handle this one -- filters, or text output.
You also have to specify the cmds properly.
Hope it help you .
Like my work hit thanks button.
$$$$$$$$$$$$$$$$$$$$$$$$
Any suggestions most welcome.
$$$$$$$$$$$$$$$$$$$$$$$$$
Hi,
I don't see my device both on 'adb' mode or in 'fastboot' mode.
What can I do to see it or put it in either of these modes?
Thanks!
-ChipX
For ADB you obviously need to enable ADB debugging from the developer settings or to be in a recovery with ADB enabled. For Fastboot you need to be in bootloader mode (fastboot).
If your device is not recognized in either of these, check your drivers/cable/USB port.
Correct.
I have ADB debugging enabled from developer settings.
My device is not being recognized now in either mode (it was earlier).
I was trying to flash a new build/AP on the phone.
fastboot erase misc
fastboot -w
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update xxx.zip
I have done this countless times on multiple phones without any issues. It doesn't work today on this device
Just before the last instruction above, after I issued 'fastboot reboot bootloader', and when I tried check whether the device has come up in 'fastboot' mode by giving 'fastboot devices', I don't see it.
I can try re-installing the USB drivers again.
ChipX8 said:
Correct.
I have ADB debugging enabled from developer settings.
My device is not being recognized now in either mode (it was earlier).
I was trying to flash a new build/AP on the phone.
fastboot erase misc
fastboot -w
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update xxx.zip
I have done this countless times on multiple phones without any issues. It doesn't work today on this device
Just before the last instruction above, after I issued 'fastboot reboot bootloader', and when I tried check whether the device has come up in 'fastboot' mode by giving 'fastboot devices', I don't see it.
I can try re-installing the USB drivers again.
Click to expand...
Click to collapse
Try updating your SDK platform-tools. They may be out of date.
I had this on my previous phone, it wasn't a big deal for me I just needed to add a ./ to each command and it would work. Hope it helps.
OzBoy1 said:
I had this on my previous phone, it wasn't a big deal for me I just needed to add a ./ to each command and it would work. Hope it helps.
Click to expand...
Click to collapse
That's why sometimes it's a better idea to run the adb/fastboot commands from CMD versus PowerShell (CMD shouldn't need "./") -- I'm assuming you're using windows as Linux & Mac OS require the ./ regardless...
I'm sure platform tools needs to be updated (for the OP), but 2 things to keep in mind is to be sure not to be using anything like "minimal adb and fastboot" and there has been reported issues on the updated platform tools (r34), so maybe there's that to consider...
Not to sound silly but have you CD'd to the Android/platform-tools directory
Have you run
adb kill-server
adb start-server
adb devices
and hit OK on the popup that shows up on your phone after start-server?
HipKat said:
Not to sound silly but have you CD'd to the Android/platform-tools directory
Have you run
adb kill-server
adb start-server
adb devices
and hit OK on the popup that shows up on your phone after start-server?
Click to expand...
Click to collapse
Kill server is usually enough. No need for start server. I'm wondering why OP is using fastbootd though.
Also, you don't need to use ./ With PowerShell if you enter "cmd" (without quotation marks of course) as your first command. After entering that, PowerShell works like command prompt.
xunholyx said:
Kill server is usually enough. No need for start server. I'm wondering why OP is using fastbootd though.
Also, you don't need to use ./ With PowerShell if you enter "cmd" (without quotation marks of course) as your first command. After entering that, PowerShell works like command prompt.
Click to expand...
Click to collapse
I can't seem to find where OP is specifically using fastbootd versus regular ol' fastboot mode...
but thanks for the tip of typing "cmd" in powershell! It's good to know! I'm always wary of using powershell and am in a lot of situation counseling other users on it, so this will come in handy versus attempting to get them to switch to cmd and/or with administrative privilages....
simplepinoi177 said:
but thanks for the tip of typing "cmd" in powershell! It's good to know! I'm always wary of using powershell and am in a lot of situation counseling other users on it, so this will come in handy versus attempting to get them to switch to cmd and/or with administrative privilages....
Click to expand...
Click to collapse
In case you didn't know, you can also just type "cmd" in the address bar of your Platform Tools folder and skip PowerShell altogether.
Lughnasadh said:
In case you didn't know, you can also just type "cmd" in the address bar of your Platform Tools folder and skip PowerShell altogether.
Click to expand...
Click to collapse
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
simplepinoi177 said:
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
Click to expand...
Click to collapse
Yeah, I've never needed admin privileges when using command prompt for any flashing I've done so it works fine for me.
simplepinoi177 said:
Thank you...I was aware of this handy tip... but when dealing advice on platform-tools matters, just avoid any potential mishaps or hiccups, I try to get an elevated (administrative privileges) prompt, and I was never sure if going about it in this manner would achieve this...
But thanks for saying this! It might really help someone in a general sense...
Click to expand...
Click to collapse
I do the same, run cmd as administrator. Actually, I toggle every app to run as administrator when I use Windows
HipKat said:
I do the same, run cmd as administrator. Actually, I toggle every app to run as administrator when I use Windows
Click to expand...
Click to collapse
exactly....especially when counseling & troubleshooting others through adb/fastboot related operations...
You never know what set up they have on their (Windows) system, and it's always a headache and a hassle "in the field" when you run down dozens and dozens of troubleshooting steps and it ends up having nothing to do with operations or execution but simple stuff like permissions or attributes. That's why I just like to get it "out of the way" so to speak and have it established at the onset before going down a whole road (dozens of steps taken)...
simplepinoi177 said:
exactly....especially when counseling & troubleshooting others through adb/fastboot related operations...
You never know what set up they have on their (Windows) system, and it's always a headache and a hassle "in the field" when you run down dozens and dozens of troubleshooting steps and it ends up having nothing to do with operations or execution but simple stuff like permissions or attributes. That's why I just like to get it "out of the way" so to speak and have it established at the onset before going down a whole road (dozens of steps taken)...
Click to expand...
Click to collapse
Exactly. Now if Windows stopped making me go in and retoggle Run as Administrator after every update... >: