Develop Bugs

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.

ADB not seeing Evo

Sorry if this is a repost. But hopefully someone can help me out. I'm fully rooted, full nandroid unlock.full 100 yeards. Now this morning I was going to do the process for "Permanently replacing your recovery with ClockworkMod Recovery Image"
But for some strange reason, ADB doesn't see my Evo. I tried running "Command prompt" as administrator also and it wasa no go. I typed "adb devices" and my device wasn't listed like it was yesterday before I did a full nandroid Unlock.
Do anyone have any tips on how I can resolve this issue?
If this helps, I running the Bugless Beast Rom.
Thanks

You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.

thanks. I'll give that a try and reply back

Strange thing....before I rooted/flashed a rom I created a Nandroid backup (I think it was stock. It doesn't have Superuser Permission in my list of Apps). Well I reverted back to that nandroid backup and now ADB sees my Evo.
I will flash back to my previous rom and trywhat you posted. Hopefully tat'll work

phatalboom said:
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
Click to expand...
Click to collapse
Yeah, I tried what you suggested and itstill didn't see my Evo. I guess my only option is to revert back, then do the process.

Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.

I'm having same issues and it's not working. My device is not being seen. Do you I have to have the Evo in charging mode or Disk Mode?

chuckhriczko said:
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
Click to expand...
Click to collapse
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.

Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc

timothydonohue said:
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Click to expand...
Click to collapse
Thanks for trying to help me out. But it still didn't work.
toastcfh said:
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
Click to expand...
Click to collapse
What do you mean that I must run adb as root on my pc, i don't know what that mean. Do you mean run it by using the "Command prompt" program?
Also this only happens to me on the Bugless Beast Roms. When I revert back to my 1st nandroid backup that I was using before I flashed any rom, everything worked fine.

Is USB debugging enabled?

CentroniX said:
Is USB debugging enabled?
Click to expand...
Click to collapse
Thanks ...that fixed it! I enabled it typed "adb devices" and it showed up. thanks again!

No problem, glad you got it working! When I first started out I ran in to that trap over-and-over. Now I just make it a rule of thumb to turn it on after flashing and leave it on.
Have fun!

I would have started another thread, but this is basically a similar problem to the one I had at first with adb.
Ok...I was trying to install a rosie.apk that was in a zip format. Long story short, the OP informed me that he made a mistake and provided me the wrong information as to reinstalling the rosie.apk. He was giving me steps to "push it" via adb, instead of flashing it.
No problem to Poster and thanks for help if you reading this . But anyways after all that, When I open up "Cmd" and type anything with adb in front of it...adb devices, adb shell..., i get the message that adb is not recognized as a internal or external command. Before this incident happened i was able to just type "adb devices" and my Evo would show.
Do anyone know how to fix this?
By the way I also tried typing all the commands in the previous posts...and I get the same error message.
**Update** I got it working I had to redo the path. All is good now.
Thanks much!

You need to be in the tools directory of the sdk so cmd can find the adb command.

ADB commands not working

So i rooted my desire using the modaco r6 root.
I'm using defrost 1.0 atm and when I'm entering recovery i cant use any adb command, except for devices which show my desire in recovery mode.
all other commands return an error like:
su:
/sbin/sh: su: not found
logcat:
/sbin/sh: exec: line 1: logcat: not found
install
/sbin/sh: pm: not found
just to name a few.
i just got it so i don't know if they worked before.
however i did get one boot loop due to flashing the circle battery mode.
after which i recovered the nandroid backup.
If you need more info tell me what to do im clueless, im prolly just doing something very stupid.
Thanks in advance.

Go into partitions menu and mount /system then try.

No go doesn't even change the error.

so no ideas? i got no wifi or 3g connectivity atm so you guys are my last resort.
just some updates i flashed mcr 3.1 and it change in addition htc sync doesn't recognize my desire now.

you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?

Can you not boot into fastboot. Volume down and power. Then go to recovery. Then hold volume up and power. Select wipe data and wipe cache. Wouldn't that solve your wifi issues etc?

Wait...if you're using root r6 then your using fake flash aren't you? Try looking for r5 and use pauls recovery or look for amskghs recovery and use that. Pretty sure adb stuff doesn't work easily with fake-flash.

cgrec92 said:
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Click to expand...
Click to collapse
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.

Hash = #
What exact commands are you doing and what are you trying to achieve?
I really want to help

LByte said:
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Click to expand...
Click to collapse
I had your same problems and felt retarded too, but it might be something funky with the dos command prompt in windows. Follow these instructions to make adb commands universal so it doesn't matter what directory the dos command prompt thinks you're in (because obviously it didn't actually move you to the tools folder somehow even though you instructed it too):
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
This was found here: sorry can't post link to give proper credit, but do a google search for adb for dummies or adb commands, it's an xda forum post...

The thread looks dead, but im going to post the possible solution anyway.
PM commands like install and uninstall doesnt work in recovery mode, so if you want to use them, run the commands when the phone had booted normally.

i have same problem? anyone help me
adb error /sbin/sh: exec: line 1: logcat: not found

Having problems rooting

ADB is not friendly to me. I was able to root my g1 with pure ease. I cant get started with adb, I dont know why I cant get $, I've read several guides and I'm just about to give up. I'm running 2.2 on my g2.
I do have a couple of questions:
Are rooting with rage or visionary 14 the only way to root?
Are there any root guides out there that dont require ADB?
ADB is a ****ing pain in the ass to me, especially since I've tried everything and cant get it to work. Also, the drivers that go on Win7 64bit just dont work.
Also when I do have root, can I get android updates?
Any help would be thankfully appreciated. Sorry if I'm a pain in the ass, but I'd like to know if there is an easier way.

I think you need the q&a section
Sent from my HTC Vision using XDA App

This will help u get adb working...
http://forum.xda-developers.com/showthread.php?t=865685

If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.

dictionary said:
If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.
Click to expand...
Click to collapse
while my knowledge of adb isnt stellar, I have run into problems using it. I'm going to try this new link to the guide and see if it works.
Still if anyone knows other solutions, chime in.

Try the guide linked above. The drivers in the HTC Sync package (see the guide) definitely do work on Win 7 64-bit.

Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?

sorry about the ****ty pics

cwis said:
Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?
Click to expand...
Click to collapse
Did you definitely add it to your path as it is suggesting in that window ? If so, I think you may need to reboot to pick that change up.

I did that just in case.
Actually, that path field was empty. So, I added it as is.

look up droid explorer

I made some leeway:
C:\Program Files (x86)\android-sdk-windows\tools>adb shell
$
$ adb push su /sdcard/su
$ adb push su /sdcard/su
$ adb: permission denied
good grief!!!!!!!

I've completely removed visionary before starting this procedure. Did I need temproot before attempting this?
Downloading and installing Droid Explorer. Thanks!
Also, I'm using this guide: http://forum.xda-developers.com/showthread.php?t=834228

No matter what I've done, permission denied.

The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.

ianmcquinn said:
The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.
Click to expand...
Click to collapse
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).

steviewevie said:
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).
Click to expand...
Click to collapse
I did run the commands from my pc. But still permission denied.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
"permission denied" is a message from your phone, not your PC.
The $ prompt that you copied and pasted up shows that you were running the commands on your phone. As soon as you do "adb shell", then any commands you are entering after that are going on your phone, even though they're physically being typed on your PC - because your PC has started a command prompt on your phone, as shown by the $ prompt.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
Basically, don't start by typing adb shell. The instructions you are trying to follow don't even say to do that anywhere. I highly recommend you reread the instructions very carefully and follow them exactly. Rooting this phone is actually pretty simple if you just do exactly as the guide states. If you don't know what you are doing and mistype something in some of the later steps though, you can seriously screw up your phone...

I think part of the confusion is that the commands listed on the guide all have "$" at the beginning of them, probably because whoever wrote that was using a Linux PC or maybe a Mac. You are actually executing these commands from your Windows command shell so they will look more like:
D:\Android SDK\platform-tools>adb push su /sdcard/su
Click to expand...
Click to collapse
(depending on where you have the SDK installed)
instead of:
$ adb push su /sdcard/su
Click to expand...
Click to collapse
but of course you only need to type:
adb push su /sdcard/su
Click to expand...
Click to collapse
Again these are typed from your windows command shell.

G2 root problem - rage

trying to root using this methods:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
I start doing the temp root as it explains to do first. on the first command (adb push su /sdcard/su) i get "permission denied".
I have the sd card mounted to my phone not the computer. I appreciate your help.

Are you sure that ADB is working in general? What happens when you enter the command "adb devices"?
All that command is doing is copying a file from your computer to the root of the SD card, most of the time the SD card will be formatted with FAT32 and there aren't even any security settings for that.
You could use other methods to get the files from your PC to your phone but I'd be concerned you have an ADB problem.

raitchison said:
Are you sure that ADB is working in general? What happens when you enter the command "adb devices"?
All that command is doing is copying a file from your computer to the root of the SD card, most of the time the SD card will be formatted with FAT32 and there aren't even any security settings for that.
You could use other methods to get the files from your PC to your phone but I'd be concerned you have an ADB problem.
Click to expand...
Click to collapse
I see a device listed there which matches my phones s/n.
I agree, i would like to see ADB working properly. Any suggestions are very welcome. Thanks.

OK so let's assume that ADB is working then, I wonder if something strange is going on with your SD card, do you have another card you can use for testing, take a card (even an old 1GB card will do), format for FAT32, put in the device and try again.
Can you copy ANY file to your SD card?
Test by copying any file to the SD card, I'd probably create a small text file and then run:
adb push test.txt /sdcard/test.txt
Click to expand...
Click to collapse
Assumes the file you are using is named "test.txt" of course.
Also make sure the folder you run your ADB commands from is the folder that contains the files you want to push, if you have ADB files in your path you can run the ADB commands from whichever folder you downloaded the files to. Otherwise copy the files to the folder where ADB lives.

I think i have a spare card somewhere, i will look for it when i get home.
I know i can copy stuff to my sd card using windows explorer when i "turn on usb storage"
I tried using a test text file i created, no dice. I put the files in the same place as adb, and additionally tried using the absolute path.
Also, i tried running the command: adb push rage /data/local/tmp/rage
which i believe is copying the built in memory and not the sdcard, this also gave me "permission denied"

Did you enable USB debugging on your phone?

ianmcquinn said:
Did you enable USB debugging on your phone?
Click to expand...
Click to collapse
Yes
Sent from my T-Mobile G2 using XDA App

And you typed in no other commands prior (e.g., no "adb shell" or anything like that)? What OS are you using? Also, can you post what all you are seeing on the screen (i.e., what you typed in and what got returned) or even a screenshot?

How did the fresh/formatted MicroSD card change things?
Also can you "ADB Pull" files from your phone to your PC?

ianmcquinn said:
And you typed in no other commands prior (e.g., no "adb shell" or anything like that)? What OS are you using? Also, can you post what all you are seeing on the screen (i.e., what you typed in and what got returned) or even a screenshot?
Click to expand...
Click to collapse
Well i typed in "adb shell" to get into the console

b1ackhawk said:
Well i typed in "adb shell" to get into the console
Click to expand...
Click to collapse
That's the problem then. ADB push/pull commands cannot be done from within the ADB shell command prompt. ADB shell is the equivalent of running Terminal on your phone itself. Do not start with ADB shell and you should be fine (none of the guides say to run the "adb shell" command first either).

raitchison said:
How did the fresh/formatted MicroSD card change things?
Also can you "ADB Pull" files from your phone to your PC?
Click to expand...
Click to collapse
havent found my spare card yet. although i cant push system memory either, which needs to be solved.
adb pull also gives me "permission denied"

ianmcquinn said:
That's the problem then. ADB push/pull commands cannot be done from within the ADB shell command prompt. ADB shell is the equivalent of running Terminal on your phone itself. Do not start with ADB shell and you should be fine (none of the guides say to run the "adb shell" command first either).
Click to expand...
Click to collapse
DOH! I knew it was going to be some stupid step i did wrong. Ive done this before, but obviously too long ago (tmo G1)... Huge thanks for being able to deconstruct my backwards thinking.