Im trying to get to the tools in the sdk folder from the command line.i went to path ;c:\android\tools.I go to the command line i put in that path and it say that its not recognived as a internal or external command what am i doing wrong.and when its done wright how should it look. Im doing the 1.5 to 2.1 walkthrough. im new to all this i wanna get it right.
skd05 said:
Im trying to get to the tools in the sdk folder from the command line.i went to path ;c:\android\tools.I go to the command line i put in that path and it say that its not recognived as a internal or external command what am i doing wrong.and when its done wright how should it look. Im doing the 1.5 to 2.1 walkthrough. im new to all this i wanna get it right.
Click to expand...
Click to collapse
you are headed in the right direction but it needs too look like this
cd C:\android\tools
Click to expand...
Click to collapse
Hope this helps you out.Btw what are you trying to do push a bootanimation or something
rooting the eris im trying to enter these codes in the command promt..
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
I do:
cd C:\AndroidSDK\tools
that was after I moved the tools folder otherwise it was:
cd C:\AndroidSDK\android-sdk-windows\tools
im try to get to command prompt and go to your tools directory am i typing the right thing ;C:\android\tools or is it cd c:\android\tools in trying to Flashing a Custom Recovery so i can flash the 2.1 rom
have you made it to the tools directory? if you actually go to the tools file on your computer, on the address bar you will see what you need to type.... either (red font)
cd C:\AndroidSDK\tools
that was after I moved the tools folder otherwise it was:
cd C:\AndroidSDK\android-sdk-windows\tools
type one or the other exactly how I have it up top....cd and all....
Is there an ADB push nautilus script out there?
That'll be handy, but i'm no scripting expert. I suspect it'll be bit tricky since adb is terminal only, I'm sure someone will have to figure out a way to pipe the output from terminal to GUI pop up dialog box to display progress bar, with success or failure message.
this one seem to work but no progress bar or success/fail message tho. YMMV
Code:
#/bin/sh
adb push $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS /sdcard
save this as adb_push.sh
be sure to set this file with permission:
Code:
chmod a+x adb_push.sh
think of this as rough draft, not perfect. Above code will push straight to sdcard. Suppose you could create few scripts like this..
ADB - Push to System APP
Code:
#/bin/sh
adb remount
adb push $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS /system/app
ADB - Install APK
Code:
#/bin/sh
adb install $NAUTILUS_SCRIPT_SELECTED_FILE_PATHS
EDIT: Forgot to mention this, it'll work only if you've already set path to Android's SDK tools folder in .bashrc
awesome, thanks! I'll test it in a minute
Simple scrip to push files to your android device.
Just put it in your Nautilus script dir (HOME/.gnome2/nautilus-scripts) and make it executable (chmod +x Push\ sdcard). also set path for ADB inside script (ADB=...)
I did something similar a while back for both Konqueror and Dolphin in KDE, but I realized, I just don't use a file manager since I prefer the command line instead. I had a working ADB zsh completion script, but somehow forgot to back it up before my previous hard drive failure.
https://code.google.com/p/send-to-android/
this is interesting
Adapted from pokey9000's original instructions and the instructions of macndroid along with many others posts and just expand on some areas for the inexperienced like myself. Some was also lifted from the nookdevs site too. This was just my detailed step by step process that worked.
1. Get any sized microsd card that you don't mind trashing the data on.
2. Download pokey9000's micro sd .img files from here:
http://www.mediafire.com/?cfddu9wt9d8dunl
3. To install .img onto sd card, put micro sd card into a reader into your usb port (not sure the steps if you are just using your Nook Color to write the image onto the micro sd.
4. To write images to disk on mac osx, you need to do the following:
-Find which drive the sd card is mapped to: type in the terminal this:
diskutil list
-Now unmount that drive typing this:
diskutil unmountDisk /dev/disk<#> (My computer is was disk2)
-It should say: Unmount of all volumes on disk<#> was successful
-Type: dd if= nooter_sdcard_40mb.img of=/dev/disk<#>
-Everything needed should copy right over to the card.
3. Plug the usb cable from your NC (Nook Color) into your computer. Make sure your NC is powered on and you see the drive mounted normally.
4. Take card out of the sd reader and put it into your NC.
5. Hold down the power button for 15 seconds.
6. Let go and wait 2 seconds then hold the power button for 2 more seconds. Let go.
7. After a little bit you will get a window that says, "New network interfaces have been detected". The image is as follows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Hit Cancel.
9. Once the devices show up, wait 30 seconds and remove the card from the NC device.
10. Hold down the power button for 15 seconds again, let go, wait 2 seconds and then hold the power button for 2 more seconds, then let go again.
11. Everything should now be installed and you should be at your normal screen and your NC volume will be mounted normally.
12. Now you need to install android SDK onto you mac if you don't already have it.
13. Download it from the following site: http://developer.android.com/sdk/index.html
14. To get adb working on my terminal, I just went to the directory android-sdk-mac_x86/tools I double clicked android and it opened the terminal and seemed to install what I needed. (somebody more experienced can edit this area if there is a better way to install what is needed for the computer to run adb commands)
15. I was now able to use adb commands in the terminal.
16. For the computer to recognize my NC as a device I typed the following into the terminal:
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"
17. To verify if I was now connected, I typed in: adb devices and it showed me a number for the device.
18. Now that the device is recognized, I installed an .apk file.
19. I typed:
adb install /<full directory to file>/<file name>.apk
20. I ejected the mounted disk like I normally would from finder.
21. I rebooted my nook once unplugged.
22. Check the extras area of NC and the program was now installed.
23. To remove a program first plug your NC in like normal until disk mounts
24. I first had to find out the exact name of the .apk file installed.
-Type: adb shell ls /data/app (This gives a list of all .apk files installed and their exact names)
25. Once I had the exact name I could remove the file.
-Type: adb shell rm -r /data/app/<full name of file>.apk
26. The file should now be gone. I didn't have to reboot, I just unmounted the drive and checked the extras section of the NC. It was gone. Some suggestions were to reboot to make sure the file was gone. Might be required but I didn't have to)
27. I now feel fully confident to install and uninstall .apk files as I like.
This all worked for me and everything is running smooth. It took me a few hours to get all this together as I have very little experience with this and had to seek out info for every little step. I tried to keep it as dumb as possible so people like myself would be able to do this.
Thanks for putting everyhing together. Anyway to cut the complication of uninstall apps through ADB out, I would recommend doing in through Astro File Manager. It's capable of Application Management too.
Great tutorial. I am a total noob and you have helped me successfully root my nook...so big ups. Next question I have is that there is a thread on how to install apk's without ADB. I believe it can be done simply through the browser. They have posted how to do it but not for Mac. Can someone post how to do that via OSX in a very detailed manner as done above for the root process? Thank you soooo much!
This was going great until I had to install the Android SDK. My only computer is a PPC, & apparently the SDK only works on an Intel machine.
Wow. I had no idea that it didn't work with PPC and only with Intel.
so my issue...
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"
when I type this into terminal it asks for my password
and then comes back and says that
sh: adb: command not found
sh :adb: command not found
Am I supposed to edit that command with some paths? I can't tell if I'm being daft. Thanks!
lanfearl said:
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"
when I type this into terminal it asks for my password
and then comes back and says that
sh: adb: command not found
sh :adb: command not found
Am I supposed to edit that command with some paths? I can't tell if I'm being daft. Thanks!
Click to expand...
Click to collapse
You can go into the AndroidSDK/tools directory and replace "adb" with "./adb" in the commands listed. This is if you don't have the path added already which seems like what's happening.
thanks for the step by step!
scratchfury said:
You can go into the AndroidSDK/tools directory and replace "adb" with "./adb" in the commands listed. This is if you don't have the path added already which seems like what's happening.
Click to expand...
Click to collapse
I'm having the same problem. Cannot get past the ADB step (step 16 listed above).
What on earth am I doing wrong? (BTW, I'm not a terminal kind of guy, so cardboard book-type direction is appreciated)...
http://i51.tinypic.com/2vtuuxi.png
ericshmerick said:
I'm having the same problem. Cannot get past the ADB step (step 16 listed above).
What on earth am I doing wrong? (BTW, I'm not a terminal kind of guy, so cardboard book-type direction is appreciated)...
http://i51.tinypic.com/2vtuuxi.png
Click to expand...
Click to collapse
so here was my way around the adb step.
you type in the sudo sh command as normal untill you get to the adb kill-server and adb devices part.
in your finder navigate to the folder that the adb file is in. it supposed to be where ever you extracted the android sdk.
android/tools/
Instead of typing adb kill-server you are going to drag and drop the adb file it self from the finder to the terminal window. in my case it looks something like this.
/Users/<my home folder>/android/tools/adb
your path will look different depending on where in the drive you have it located.
so now step 16 is going to look something like this.
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; /Users/<my home folder>/android/tools/adb kill-server; /Users/<my home folder>/android/tools/adb devices"
so every time you use the adb command you have to link it to the path on your hard drive. i know theres a way to change directories so that you just type adb and it finds it. but im not that knowledgeable with linux. and im sure someone that is could help us out with that.
rluzania said:
so here was my way around the adb step.
you type in the sudo sh command as normal untill you get to the adb kill-server and adb devices part.
in your finder navigate to the folder that the adb file is in. it supposed to be where ever you extracted the android sdk.
android/tools/
Instead of typing adb kill-server you are going to drag and drop the adb file it self from the finder to the terminal window. in my case it looks something like this.
/Users/<my home folder>/android/tools/adb
your path will look different depending on where in the drive you have it located.
so now step 16 is going to look something like this.
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; /Users/<my home folder>/android/tools/adb kill-server; /Users/<my home folder>/android/tools/adb devices"
so every time you use the adb command you have to link it to the path on your hard drive. i know theres a way to change directories so that you just type adb and it finds it. but im not that knowledgeable with linux. and im sure someone that is could help us out with that.
Click to expand...
Click to collapse
hmmm im stuck on the same step too... it seems when i do that it doesn't respond at all. and when i type in adb devices to check whether it's connect, it won't do anything.... sry..im a total noob ~_~
i would love to help you but if nothing is coming up i have no idea where to begin. i almost want to say that maybe the sd card didnt work on the nook. but im not sure if thats it either. or do you have the android sdk app launched? i know that opens up another terminal window that when you type in to doesn't do anything. umm let me know what you find.
r8? no adb
sdk is now at r8, not sure if that has anything to do with it. But in tools folder there is no adb.
newton1666 said:
sdk is now at r8, not sure if that has anything to do with it. But in tools folder there is no adb.
Click to expand...
Click to collapse
It has been moved to a new folder named "platform-tools" instead of "tools".
scratchfury said:
It has been moved to a new folder named "platform-tools" instead of "tools".
Click to expand...
Click to collapse
Thanks for that, I feel very silly.
rluzania said:
so here was my way around the adb step.
you type in the sudo sh command as normal untill you get to the adb kill-server and adb devices part.
in your finder navigate to the folder that the adb file is in. it supposed to be where ever you extracted the android sdk.
android/tools/
Instead of typing adb kill-server you are going to drag and drop the adb file it self from the finder to the terminal window. in my case it looks something like this.
/Users/<my home folder>/android/tools/adb
your path will look different depending on where in the drive you have it located.
so now step 16 is going to look something like this.
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; /Users/<my home folder>/android/tools/adb kill-server; /Users/<my home folder>/android/tools/adb devices"
so every time you use the adb command you have to link it to the path on your hard drive. i know theres a way to change directories so that you just type adb and it finds it. but im not that knowledgeable with linux. and im sure someone that is could help us out with that.
Click to expand...
Click to collapse
I wanted to thank you for this, as I was getting frustrated changing my bash profile. Anyone else in this boat don't forget you need to drill down (cd) to where the adb is, in my case downloaded sdk just recently it's in platform-tools folder, to do the adb install.
If you just upgraded from an earlier version of the sdk and don't see adb, even in platform-tools, just run an Update All... under Installed packages. Hopes this helps others.
hey people. I really appreciate the work that has been done so far.
I'm trying to format a micro SD card with dd. Here's the problem: I was able to unmount the SD card in terminal but then it won't find the nooter disk img:
Code:
sh-3.2# diskutil unmountDisk /dev/disk1
Unmount of all volumes on disk1 was successful
sh-3.2# dd if=nooter_sdcard_40mb.img of=/dev/disk1
dd: nooter_sdcard_40mb.img: No such file or directory
what am I doing wrong? I have the file in question, and this isn't a complicated step. Thanks for any help.
plariers said:
what am I doing wrong? I have the file in question, and this isn't a complicated step. Thanks for any help.
Click to expand...
Click to collapse
My bad, figured it out. In case anyone else runs into this, in OSX you can drag and drop files into terminal to insert accurate file paths
worked perfectly
You are my hero!!!!!!!
I've been banging my head against a wall for HOURS UPON HOURS trying to get the adb to work. And you fixed me up in a few minutes. I love you so much right now. Seriously.
It lists my device # after step 16, but I can't install the packages then.
I got this far, and then when I try the command to adb install the app, I get
-bash:adb: command not found
any tips?
Hello
Like some other guys i use linux on my PC. If you want to change your x10mini via shell you can do it but its not very confortable.
I made a few tools so it's easier to use.
Note: This "tricks" are only usefol to you if you are a little advanced with linux and want to "work" with your x10i via shell. I tested it all on a Debian 64bit but think most parts are universal.
1. Putting adb to /etc/bin
First of all you should put the adb-binary in /etc/bin/ so you can access it like every other cmd. You can use the binary in my attached tar or the one from SDK. use "sudo cp adb /system/bin/adb" (if you have a system with sudo, eg debian & ubuntu)
2. adb: error insufficient permissions for device
If you plug in the phone and want to connect via "adb shell" it may says that you don't have permissions for device. There is a workaround:
- Create file /etc/udev/rules.d/51-android.rules
- Put the following in the file:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="2137", MODE="0666"
- restart udev "sudo service udev restart" (again this is debian&ubuntu-only)
if you still got "insufficient permissions", i made a little shell-script "adb-fix-permissions" attached in tar-file
3. bash-completition for adb
Bash is really annoying whitout completion. That means you can just start to type a word, then press [tab] and bash complets it for you. For example you type "adb ki[tab]" and bash complets it to "adb kill server"
To get this you need "adb_completition" from my attached zip or from here. Put this file in /etc/bash_completion.d/ and you got it.
example command to copy it:
"sudo cp adb_completition /etc/bash_completion.d/adb_completition"
4. Some keys not work in adb shell
This is a known and annoying bug. Eg in nano text editor you cant use the [enter]-key. There is a (little unclean) workaround for it: start a telnet-service on the phone, forward ports via adb and connetc to your phone via telnet. You will need telnetd from the attached tar. And your phone needs to be rooted.
- Remount system writable:
Code:
adb remount
- Put telnetd on your phone
Code:
adb push telnetd /system/bin/telnetd
- Make it executable:
Code:
adb shell chmod +x /system/bin/telnetd
for usage i have a little made a little script (in attached tar) "adb-shell".
Or you can do it manual:
Code:
adb telnetd &
adb forward tcp:9999 tcp:23
telnet localhost 9999
.. to be continued...
if you have one, please share your linux-android-tricks with me
thanks
[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
mamba_nz said:
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
Click to expand...
Click to collapse
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
Thank you so much!
For some reason, that zip still reports ADB version 1.0.29.
I found the latest version (1.0.31) from https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/. It has zips for linux, mac and windows adb.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
thanks that works fine 4 me