Where Can I learn ADB? - Samsung Galaxy Nexus

This is annoying as heck.
I have had the Droid 1, Droid X, and Charge and have always been able to root the phones and install roms and follow directions with now problem.
I have installed SDK, I have downloaded the adb platform tools. However, I have no idea how to get adb where it needs to be from there.
Does anyone know where I can find an in-depth guide?

try here:
http://developer.android.com/guide/developing/tools/adb.html

To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701

Yeah, I have seen that.
I guess the wall I am hitting is how you actually start adb. I know where the folder is. I might be overlooking something though.

Didn't see your post Mart, ill try that now.

martonikaj said:
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.

Pacifik said:
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Click to expand...
Click to collapse
Even easier is adding the folder to the system path variable.
That allows you to always run adb, no matter what folder you happen to be at.

Ok, I have effectively managed to get to adb and it is installed.
to root the nexus, do I now start at the 1st step in the "lets begin section" listed here:
http://rootzwiki.com/topic/12013-welcome-to-root-editionstep-by-step-oem-unlock-and-root/

http://wiki.cyanogenmod.com/wiki/ADB

Ohai droidstyle good to see you here
Has anyone seen John Connor?

skynet11 said:
Ohai droidstyle good to see you here
Has anyone seen John Connor?
Click to expand...
Click to collapse
Ya you too skynet! I have no gnex yet, but soon...very soon!!

I am now Bootlooped, the bootloader is unlocked, I flashed the recovery image without a problem, but now i am stuck at the constant flashing of the google logo

Did you flash a new ROM?

this is what I was flashing
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
I was just trying to get root and CWM

I have CWM, but all it does bootloop and I can't get it to detect a sd card.

Related

How To Use ADB On Mac With Htc Hero

I've spent hours trying to workout how to use adb
I'm using Amon_RA's recovery image and want to run a BART backup but it forces you to use adb, which i can't workout
help please!!!
Did you download the Android SDK for OS X?
Please give us some more information, such as the steps you've taken and any errors or other information you get from the Terminal.
yes i have downloaded the sdk from the website
but everytime i even check what devices are connected etc it fails
i open terminal, drag the tools folder into it, it then ses its created a directory
when i try to put in the commands "adb devices" or "bart" however, it ses there is no such command
do i need to put my phone into recovery, or mass storage or something
im stumped
You need to add the tools directory to PATH variable on your computer
Here's how you do it (the alternative way is easier):
Run this in Terminal
Code:
cd
nano .bash_profile
a text editor will open. add this:
Code:
export PATH=${PATH}:/path-to-android-sdk/tools
where you replace "path-to-android-sdk" with the real path.
Alternatively you could run this command in the terminal:
Code:
echo -e "\nexport PATH=${PATH}:/path-to-android-sdk/tools" >> .bash_profile
What you have done is to tell the shell to also look inside the tools directory when entering a command
Oh, in addition to Repp's suggestions, I know in Linux (and I dunno about everyone else) I need to be root to run adb properly. So maybe become root on the Mac. To do so, you need to be an Admin user, not a regular user, and at the Terminal, type
Code:
sudo -s
and then enter your user password when prompted.
okay ive done that, i dont know if it came back with the right response tho
i tried the first method and got into the text editor, i then typed what you said and it returned no response, i dont know if this is correct?
if so what do i do next?
Rather than altering your path, you can also navigate to the sdk/tools directory and run adb like so:
Code:
./adb devices
But you have to be inside the directory where the "adb" command lies.
Also, see my note above regarding root users.
Aah sorry. Just save and exit (press Ctrl+X and answer yes to whether or not you want to save). You could also try the alternative way.
craig0r said:
Oh, in addition to Repp's suggestions, I know in Linux (and I dunno about everyone else) I need to be root to run adb properly. So maybe become root on the Mac. To do so, you need to be an Admin user, not a regular user, and at the Terminal, type
Code:
sudo -s
and then enter your user password when prompted.
Click to expand...
Click to collapse
I have always used it as normal user and it has worked. Don't know why you would need to be root
how dyou get into the directory?
i usually just drag the tools folder into terminal.
is this correct?
DaNiEl FrEnCh said:
how dyou get into the directory?
i usually just drag the tools folder into terminal.
is this correct?
Click to expand...
Click to collapse
At the Terminal type
Code:
cd /Users/YourUserName/path/to/android_sdk/tools/
./adb devices
Repp said:
I have always used it as normal user and it has worked. Don't know why you would need to be root
Click to expand...
Click to collapse
Yeah, it's weird, but it works for me.
You change directory in the terminal with the command cd. So if I wanted to go to the Desktop directory I would write:
Code:
cd ~/Desktop
(~ is like a shortcut for your home directory which is the same as the directory /Users/your-username)
Did any of the methods work (they should )?
to repp, ive done that, all i need to know now is how to use the bart backup function from Amon_RA's recovery image, in adb
craig0r said:
Yeah, it's weird, but it works for me.
Click to expand...
Click to collapse
And it doesn't if you're not root?
DaNiEl FrEnCh said:
to repp, ive done that, all i need to know now is how to use the bart backup function from Amon_RA's recovery image, in adb
Click to expand...
Click to collapse
And it worked?
Unfortunately I have never done that so I can't help you there
how can i check if it worked?
Just run adb from any directory which is not the tools directory.
For example:
Code:
cd
adb devices
where the first line (cd) changes directory to your home directory (the command cd without a path does that) and the other one should list connected devices. As long as it doesn't say
Code:
-bash: adb: command not found
or anything like that, you should be fine
EDIT: If you want to use adb, you don't have to do the "cd" part first. This time only
its working now i can seee what devices i have
Code:
Dans-MacBook:tools Dan$ ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT98DL900002 device
but the main reason i want to use it, is to use it with Amon_RA's recovery
i neeed to do a BART backup so i can switch from the 2.1 rom from lox too 3.0 from modaco
I have never used BART, but unless I'm mistaken, it does almost the same thing as a nandroid backup (?). You could try that instead. Don't know about Amon_RA, but it's possible from MoDaCo's fastboot (linked to and explained how to install here)
other than that, there's nothing I can do
Repp said:
And it doesn't if you're not root?
Click to expand...
Click to collapse
That's right. Probably something to do with permissions in /dev/. It doesn't bother me enough to go hunting the problem down.

I'm lost. Need rooting help.

I'm lost as hell. I found this thread:
http://www.androidpolice.com/2010/06...credible-next/
I did the unrevoked thing and I see this icon called SuperUser Permissions in my app list.
Am I able to proceed and fully root or do I have to re-do the root with the Toast method? This looks too complicated and by the way I tried the ./adb thing on my mac and I get errors saying "No such file or directory".
gqstatus0685 said:
This looks too complicated and by the way I tried the ./adb thing on my mac and I get errors saying "No such file or directory".
Click to expand...
Click to collapse
adb isn't installed on a Mac out of the box; You'll need to go download the Android SDK. Untar it somewhere (I put it in ~/), then open a term, do:
Code:
cents-macbook-pro:~ $ cd android-sdk-mac_86/tools/
cents-macbook-pro:~/android-sdk-mac_86/tools $ ./adb
CentroniX said:
adb isn't installed on a Mac out of the box; You'll need to go download the Android SDK. Untar it somewhere (I put it in ~/), then open a term, do:
Code:
cents-macbook-pro:~ $ cd android-sdk-mac_86/tools/
cents-macbook-pro:~/android-sdk-mac_86/tools $ ./adb
Click to expand...
Click to collapse
Massive Brain Freeze.. What do you mean by "(I put it in ~/)"?
I downloaded the Android SDK already. I understand what terminal is so when I download the Android SDK where do I place it?
Am I pointing terminal to the directory? Android SDK is currently in a folder on my desktop.
gqstatus0685 said:
Massive Brain Freeze.. What do you mean by "(I put it in ~/)"?
I downloaded the Android SDK already. I understand what terminal is so when I download the Android SDK where do I place it?
Am I pointing terminal to the directory? Android SDK is currently in a folder on my desktop.
Click to expand...
Click to collapse
~ in most flavors of Unix/Linux is short for your home directory. In MacOS, ~ is /Users/<username>. *nix pro-tip:
Code:
cents-macbook-pro:~ $ echo ~
/Users/cent
So in my case, ~ is short for /Users/cent.
If it's on your desktop, open a terminal and type:
Code:
cd ~/Desktop/android-sdk-mac_86/tools
-OR-
Code:
cd /Users/cent/Desktop/android-sdk-mac_86/tools
And then you can proceed to issue your adb commands. Just remember to prefix it with "./", which tells MacOS to look in the current directory for the adb command.
Code:
cents-macbook-pro:~/android-sdk-mac_86/tools $ ./adb devices
List of devices attached
HT05RHL1XXXX device
Ok. I think I'm just going to pay someone to do this for me. I'm getting a migraine.
So I'm basically typing the below:
~/android-sdk-mac_86/tools $ ./adb devices (Do I type this in one line)
List of devices attached
HT05RHL1XXXX device
I ran the thing and it doesn't show my phone listed.
I've got the time, if you have the money!
1. Make sure USB debugging is enabled. On your phone, go to Settings -> Applications -> Development, and make sure "USB debugging" is checked.
2. Make sure your USB cable is connected to your phone and computer.
3. Open a terminal
4. Type "cd ~/Desktop/android-sdk-mac_86/tools" and press enter.
5. Type "./adb devices" and press enter.
If it lists your device, you're then good to go to start following the rooting instructions!
You're the best dude. It was the USB debugging that was giving me the problem.
Good deal man, glad you got that part worked out! Have fun getting your root on!
this is the easiest way to do it....it worked for me
http://forum.xda-developers.com/showthread.php?t=701152
Do i have to keep dubugging mode on or can I turn it off before I root it. I did the command:
"cd ~/Desktop/android-sdk-mac_86/tools"
and then
adb push PC36IMG.zip /sdcard (Doesn't do anything. I tried without the space and some stuff popped up. Can I just manually put it on my SDcard?
gqstatus0685 said:
Do i have to keep dubugging mode on or can I turn it off before I root it. I did the command:
"cd ~/Desktop/android-sdk-mac_86/tools"
and then
adb push PC36IMG.zip /sdcard (Doesn't do anything. I tried without the space and some stuff popped up. Can I just manually put it on my SDcard?
Click to expand...
Click to collapse
Debugging mode needs to stay on if you want to use adb. You can turn it off once you root, but it won't hurt to leave it on.
The push command should tell you the number of bytes transfered. You need to make sure that the file you are pushing is in the current directory you're in (tools), or manually enter the path, like "./adb push ~/Downloads/PC36IMG.zip /sdcard"
But yes, you can mount the card as a disk drive and copy the file there in Finder.

[GUIDE] Noob's Guide #5: How to use ADB...

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

Stuck in recovery with no Rom

To make it short, I got downloaded a corrupted ROM (only one on the phone), and with no nandroid. Is there any other way to access my "sd" card on my phone to put another ROM in? Is flashing a stock img the only way to get it back to work without losing my pictures? Thanks..
If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.
martonikaj said:
If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.
Click to expand...
Click to collapse
This.
Problem sorted.
Thanks for the suggestion, but can you provide some commands to push this file through adb?
if you are not familiar with adb commands, use Android Commander. Saves alot of time.
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
Is your ROM file in the Android>Platform Tools folder?
adb push rom.zip /sdcard/
You need the extension (.zip) as well.
Edit: does adb devices indicate you're connected?
Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.
Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.
Nevermind.
martonikaj said:
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.
Click to expand...
Click to collapse
Yes I did that, and now for some reason my sdk is not recognizing my phone (funny cause i tried flashing a new recovery.img). Now i'm re-installing sdk tools.
adrynalyne said:
Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.
Click to expand...
Click to collapse
Thanks, gotta fix the first problem though.

[Q] how to root htc one?

What is the easiest method to root HTC one that is on 4.2.2?
cis314 said:
What is the easiest method to root HTC one that is on 4.2.2?
Click to expand...
Click to collapse
Here's what you're looking for...it's your only option if you don't want to mail it anywhere:
http://forum.xda-developers.com/showthread.php?t=2473644
Sent from my HTC6500LVW using XDA Premium 4 mobile app
cis314 said:
What is the easiest method to root HTC one that is on 4.2.2?
Click to expand...
Click to collapse
I finally got my htc one rooted and flashed plenty of roms so far I had a lot of stupid issues with rooting but guys on here were very helpful even tho I had to ask questions over and over again to troubleshoot problems. Easiest way was to dl rumrunner and get s-off and bootlader loaded. Them just flash a recovery. My buggiest prob was getting all files on my comp into a separate folder and opening a cmd from that folder. Also remember to always run stuff on ur comp as an administrator!
how did you flash recovery? I am having such a hard time flashing recovery!
cis314 said:
how did you flash recovery? I am having such a hard time flashing recovery!
Click to expand...
Click to collapse
put recovery.img in adb folder
open cmd prompt
type fastboot flash recovery nameofrecvovery.img
andybones said:
put recovery.img in adb folder
open cmd prompt
type fastboot flash recovery nameofrecvovery.img
Click to expand...
Click to collapse
Easier to just type "fastboot flash recovery (drag recovery.img here)"
that way you can save the recovery on your desktop or wherever. I wish adb/fastboot could be ran from anywhere and not just the adb folder though.
exzacklyright said:
Easier to just type "fastboot flash recovery (drag recovery.img here)"
that way you can save the recovery on your desktop or wherever. I wish adb/fastboot could be ran from anywhere and not just the adb folder though.
Click to expand...
Click to collapse
if you set it up correctly it can be, I can put the .img in my C folder, open a cmd and run commands, but it would still need the adb file.
so put the recovery whereevere your adb.exe is..
you can even make a folder called apktool in c: (thats what I have, that has adb.exe, fastboot, smali, baksmali, etc)
andybones said:
if you set it up correctly it can be, I can put the .img in my C folder, open a cmd and run commands, but it would still need the adb file.
so put the recovery whereevere your adb.exe is..
you can even make a folder called apktool in c: (thats what I have, that has adb.exe, fastboot, smali, baksmali, etc)
Click to expand...
Click to collapse
Adding the path to the adb.exe (and fastboot.exe) directory, to the environment variables, allows you to run ADB and Fastboot from any directory.
In Windows, right+click "Computer", select "Properties", click on "Advanced System Settings". On the "Advanced" tab select "Environment Variables" . In the bottom window find the "Path" string and add the path to ADB directory to the end.
The Paths in the string are separated by a semi-colon, so for example, I've added the path to my platform-tools directory like such:
;c:\android-sdk\platform-tools
This can also be done in Linux and Mac OS X, environment variables are stored in a hidden text file in the home folder. You can also adde it by typing the the PATH command in a terminal. Just Google it. Only takes a minute and saves time by not having to "CD" to your ADB directory every time.
EDIT: This Tut. has nice screen shots
http://forum.xda-developers.com/showthread.php?t=757233

Categories

Resources