Related
Hey, I'm trying to push some stuff onto my mytouch using the included bridge tool, adb, and can't quite get it to work. AKA, I have no effing clue what I'm doing. I'm good with everything else, but when you sit me in front of Terminal I'm useless. Anyway, running Mac OS X, 10.5, I've got the SDK installed, exported, all that, but the internet has been no help with telling me what to do next. Please, someone help? D:
not sure on mac
but on pc i mostly put the files i want to push in to the sdk tools folder which gives you less to type
if you want to push stuff you need to know where to push on phone like
adb remount (makes drive read/write)
adb push xxxx.ogg /system/media/audio/ringtones/
if you want to install something
adb install twitter.apk
so my terminal looks like this (ignore errors phone not in usb)
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\SI>cd s\tools
C:\Users\SI\s\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\Users\SI\s\tools>adb push xxxx.ogg /system/media/audio/ringtones/
error: device not found
C:\Users\SI\s\tools>
sitimber has given some good tips. On a Mac, you have to put "./" in front of adb to get it to execute.
For example, I have the Android SDK installed in /Developer/Android. In order for me to use adb, I open terminal and do the following:
cd /
cd /Developer/Android/Tools
./adb (insert whatever adb command here)
jsnyng said:
cd /
cd /Developer/Android/Tools
./adb (insert whatever adb command here)
Click to expand...
Click to collapse
worked perfectly! all the info i was getting was either for windows or linux and i was getting wicked confused. i have like nooo training with terminal so i was lost. that worked perfectly, thank you :]
do i still have to type "adb (command)" when i'm in the shell? i know that far, that im in the adb shell when there's a # next to my open commandline.
This will make it a step easier. If you want to be able to "adb command" every time you open the shell without changing directories,
Open terminal.
Run:
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder
Click to expand...
Click to collapse
How you will be able to see hidden files.
Download the OSX SDK http://developer.android.com/sdk/download.html?v=android-sdk_r3-mac.zip
Unzip it. Move the entire folder into your root directory "/"
rename it to "android".
Launch TextEdit.app
Hit "Format>Make Plain Text"
Now type (in the document)
export PATH=${PATH}:/android/tools
Click to expand...
Click to collapse
Save is as
.bash_profile
in YOUR HOME DIRECTORY.
Make sure you uncheck "If no extension, use .txt"
Say yes when it asks if you want to make this a system file.
now close terminal (all the way) and relaunch. Type "adb" and whatever you'd like and you're set!
jewishjawsh said:
do i still have to type "adb (command)" when i'm in the shell? i know that far, that im in the adb shell when there's a # next to my open commandline.
Click to expand...
Click to collapse
No, you don't.
chordmasta's directions for creating a .bash_profile are correct, but I'll point out that you don't need to move it to root. I personally prefer not to clutter up root with my personal stuff. You also don't need to rename it if you don't want to.
For example, if you have it in "Documents", you would use this path (replacing my username "softbanksucks" with the name of your home directory.)
Code:
export PATH=${PATH}:/Users/softbanksucks/Documents/android-sdk-mac_x86-1.6_r1/tools
softbanksucks said:
No, you don't.
chordmasta's directions for creating a .bash_profile are correct, but I'll point out that you don't need to move it to root. I personally prefer not to clutter up root with my personal stuff. You also don't need to rename it if you don't want to.
For example, if you have it in "Documents", you would use this path (replacing my username "softbanksucks" with the name of your home directory.)
Code:
export PATH=${PATH}:/Users/softbanksucks/Documents/android-sdk-mac_x86-1.6_r1/tools
Click to expand...
Click to collapse
Thanks for pointing that out. I should have mentioned it. I knew this walkthrough would work without having to change values.
chordmasta said:
Thanks for pointing that out. I should have mentioned it. I knew this walkthrough would work without having to change values.
Click to expand...
Click to collapse
No prob - knew that you knew, just figured I'd point it out for those who don't
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?
ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Do you install the Sync software?
laufine said:
Do you install the Sync software?
Click to expand...
Click to collapse
Yes, I've tried it with and without.
I recently deleted the Sync, should I reinstall it?
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Hero's Hero said:
ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
i was just about to type this up then saw this as the last post. Good work man
laufine said:
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Click to expand...
Click to collapse
I have all the drivers
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
I have them in the path, but no beauno
Hero's Hero said:
I have them in the path, but no beauno
Click to expand...
Click to collapse
Where is your SDK installed to?
DevinXtreme said:
Where is your SDK installed to?
Click to expand...
Click to collapse
It's in C:/
Hero's Hero said:
It's in C:/
Click to expand...
Click to collapse
And you've tried running this before any adb commands, right?
Code:
cd C:\android-sdk-windows*\tools
*Or whatever you named that folder
I've Had this issue. I Had to un-install the sync And sdk. Then install them right back on lol.Reloaded the vista drivers then Im back Tim. That is if its a Driver issue
-------------------------------------
Sent via the XDA Tapatalk App
Do you still need help with this? I can help you out
regaw_leinad said:
Do you still need help with this? I can help you out
Click to expand...
Click to collapse
Yes I do.
Would really appreciate it.
It seems you're on your way to receiving help. However, if you're still in limbo, locate your android folder or adb executable, right click, copy the location, and paste it into a follow-up reply. This is with respect to the diagnosis process.
Either way, I hope you're headed in the right direction to solve your slight dilemma.
Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this
I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.
hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..
Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!
Mod. edit: not dev related, moved to general
Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help
well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3
Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"
Terminal: "adb remount", then push again
damn the next bad message "remount failed: Operation not permitted"
You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927
Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me
You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279
now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to
You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled
Okay thank you very much.
now it was successful
So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??
Was adb remount succesful before you tried?
joeski27 said:
So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??
Click to expand...
Click to collapse
I ran in to this. Make sure your Xoom is not on the lock screen. Should be good to go.
PaulG1488 said:
Was adb remount succesful before you tried?
Click to expand...
Click to collapse
Yes, adb remount was in fact successful.
Edit - now I'm getting "cannot stat 'su': No such file or directory"
just to be clear, is it supposed to be:
adb push su /system/bin/
or
adb shell push su /system/bin/
???
syntax is "adb push ..."
bcgaynor82 said:
syntax is "adb push ..."
Click to expand...
Click to collapse
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message.
I have no idea what's going on here. Its almost as if I dont have the xoomroot files (including su) in the correct place, but they are there in the SDK tools folder as they are supposed to be. UGH!?!!?
joeski27 said:
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message. ?????
Click to expand...
Click to collapse
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.
nindoja said:
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.
Click to expand...
Click to collapse
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.
Is there any chance that the unlock didn't take? Though I can't see how it didn't - I went through the entire procedure, answered all the prompts during fastboot, and it did erase/reset the tablet afterwards, so I'm guessing that isn't it.
joeski27 said:
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.
Click to expand...
Click to collapse
Any chance you can screenshot your sdk tools folder
They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.
PaulG1488 said:
Any chance you can screenshot your sdk tools folder
Click to expand...
Click to collapse
Screenshot of my sdk tools folder:
EDIT: heres the link:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at122552AM.png?t=1299130486
Elysian893 said:
They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.
Click to expand...
Click to collapse
I know, but I had already moved adb into the tools folder earlier on. So they are in the same folder.
send a screenshot of everything in your command prompt if u can please
PaulG1488 said:
send a screenshot of everything in your command prompt if u can please
Click to expand...
Click to collapse
here's the screenshot of my terminal:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at124929AM.png?t=1299131460
Do you have the 3.0 sdk installed
Wait I see the problem after you remounted you have to direct it back into your tools foledr before doing the adb push command
PaulG1488 said:
Do you have the 3.0 sdk installed
Click to expand...
Click to collapse
all I know is that i have the latest sdk installed, but are you referring to something additional to that? such as "SDK Platform Android 3.0, API 11, revision 1" ?
joeski27 said:
all I know is that i have the latest sdk installed, but are you referring to something additional to that?
Click to expand...
Click to collapse
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved
PaulG1488 said:
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved
Click to expand...
Click to collapse
So I just did the remount again (successfully), and now instead of just entering "adb push ...", I would need to do what?
EDIT - just tried this, and got this result:
Joseph-Olesweskis-iMac:~ olesweski$ /Users/olesweski/Desktop/android-sdk-mac_x86/tools adb push su /system/bin/
-bash: /Users/olesweski/Desktop/android-sdk-mac_x86/tools: is a directory