Database Users

Need some adb help...

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

Looking to Learn

Hello I frequent the boards...actually on a daily basis. I dont post a lot as you can see...mainly because the posts are usually thoroughly explained and I usually dont have a lot of problems that I cant already find the answers to.
I want to thank everyone who contributes to the board. I currently have the HTC hero and I have installed all but 1 of the current available roms, I had the Touch Pro before and the Touch prior to that. I have uses custom roms for all so a huge thanks to all the devs.
My reason for posting is I want to learn how to develop myself eventually but for now I have a specific question about getting the most out of my rooted HTC hero. Darchstar posted this:
adb shell remount
adb push e2fsck /system/bin
adb shell
cd /system/bin
chmod a+x e2fsck
a2sd
reboot
Its to enable apps2sd. I want to get a little help of understanding how to apply it. I rooted my phone so I did a lot of edits in cmd promt...but for me it was just a matter of following instructions I want to learn what I am actually doing and how to fully take advantage of rooting my phone. I dont use terminal emulator or SU really for anything because I dont understand how to use them or even the full extent of what they can do. I know theres a wiki...but I really dont know what to search. As of now I have been having devs do everything for me to an extent. I use a kitchen which is pretty much automated and I have just been following instructions on the board.
I am pretty good with computers, i build them and fix them all the time for people...and with phones also. Im a tech in a cellphone store so you can gather I am a tinkerer. I am not looking to be told how to do things and just follow the instructions I want to know what I am doing, even though here I have never been steered wrong. I want to be educated.
I know this post is long winded and I would like to thank everyone in advance for any help offered.

Patb8man said:
Hello I frequent the boards...actually on a daily basis. I dont post a lot as you can see...mainly because the posts are usually thoroughly explained and I usually dont have a lot of problems that I cant already find the answers to.
I want to thank everyone who contributes to the board. I currently have the HTC hero and I have installed all but 1 of the current available roms, I had the Touch Pro before and the Touch prior to that. I have uses custom roms for all so a huge thanks to all the devs.
My reason for posting is I want to learn how to develop myself eventually but for now I have a specific question about getting the most out of my rooted HTC hero. Darchstar posted this:
adb shell remount
adb push e2fsck /system/bin
adb shell
cd /system/bin
chmod a+x e2fsck
a2sd
reboot
Its to enable apps2sd. I want to get a little help of understanding how to apply it. I rooted my phone so I did a lot of edits in cmd promt...but for me it was just a matter of following instructions I want to learn what I am actually doing and how to fully take advantage of rooting my phone. I dont use terminal emulator or SU really for anything because I dont understand how to use them or even the full extent of what they can do. I know theres a wiki...but I really dont know what to search. As of now I have been having devs do everything for me to an extent. I use a kitchen which is pretty much automated and I have just been following instructions on the board.
I am pretty good with computers, i build them and fix them all the time for people...and with phones also. Im a tech in a cellphone store so you can gather I am a tinkerer. I am not looking to be told how to do things and just follow the instructions I want to know what I am doing, even though here I have never been steered wrong. I want to be educated.
I know this post is long winded and I would like to thank everyone in advance for any help offered.
Click to expand...
Click to collapse
The best way to learn about this stuff is to bite the bullet and install a Linux distro on your computer. I've also took up teaching myself to code Java in my spare time which will help you understand Android a lot better.
Also: You need an EXT partition on your SD to enable apps2sd. Is that what you're asking?

Thanks. I do have an ext partition on my card and it I am currently using it with gumbo 1.5c bare. I was just thinking about installing 2.1 and before I did I wanted to make sure I could enable app2sd. I was just using it as an example. I just want to learn in general. Is linus distro a version of the os I would dual boot with or does it emulate in windows? Also how did you just start java? A google search and article research, book or are you in school?

Patb8man said:
My reason for posting is I want to learn how to develop myself eventually but for now I have a specific question about getting the most out of my rooted HTC hero. Darchstar posted this:
adb shell remount
adb push e2fsck /system/bin
adb shell
cd /system/bin
chmod a+x e2fsck
a2sd
reboot
Its to enable apps2sd. I want to get a little help of understanding how to apply it. I rooted my phone so I did a lot of edits in cmd promt...but for me it was just a matter of following instructions I want to learn what I am actually doing and how to fully take advantage of rooting my phone. I dont use terminal emulator or SU really for anything because I dont understand how to use them or even the full extent of what they can do. I know theres a wiki...but I really dont know what to search. As of now I have been having devs do everything for me to an extent. I use a kitchen which is pretty much automated and I have just been following instructions on the board.
Click to expand...
Click to collapse
Basically these commands are installing the e2fsck, a program that formats a partition in the ext2 file system, so that apps2sd can run.
Here is a breakdown:
adb shell remount --remount the file system of your phone so you can write a file to it
adb push e2fsck /system/bin --copy the file/program e2fsck to the directory /system/bin on the phone
adb shell --switch from your computer's shell (cmd) to control the shell environment of the phone
cd /system/bin --change directory to work in /system/bin
chmod a+x e2fsck --change the permissions of e2fsck so that you can actually execute (run) it
a2sd --run apps2sd (a2sd) so that it can set itself up (it will call on e2fsck)
reboot --reboot the phone.
Hope that's what you were looking for.

Patb8man said:
Thanks. I do have an ext partition on my card and it I am currently using it with gumbo 1.5c bare. I was just thinking about installing 2.1 and before I did I wanted to make sure I could enable app2sd. I was just using it as an example. I just want to learn in general. Is linus distro a version of the os I would dual boot with or does it emulate in windows? Also how did you just start java? A google search and article research, book or are you in school?
Click to expand...
Click to collapse
(Sorry for double posting, folks... timing...)
I would highly recommend that you dual boot or install Linux on a spare computer until you are comfortable with it. If you want, you could run VirtualBox to emulate another system (VM) and install Linux there.

Is_907 said:
Basically these commands are installing the e2fsck, a program that formats a partition in the ext2 file system, so that apps2sd can run.
Here is a breakdown:
adb shell remount --remount the file system of your phone so you can write a file to it
adb push e2fsck /system/bin --copy the file/program e2fsck to the directory /system/bin on the phone
adb shell --switch from your computer's shell (cmd) to control the shell environment of the phone
cd /system/bin --change directory to work in /system/bin
chmod a+x e2fsck --change the permissions of e2fsck so that you can actually execute (run) it
a2sd --run apps2sd (a2sd) so that it can set itself up (it will call on e2fsck)
reboot --reboot the phone.
Hope that's what you were looking for.
Click to expand...
Click to collapse
for the adb shell remount part when i hook the phone up to the computer w debugging on when I run a command prompt how do I get to the adb in the first place. I am not familiar with that to begin with. I know I had to edit it when I rooted my phone...but like I said I really didnt understand what I was doing it was just a matter of following instructions. Thank you for the detailed description of whats going on...thats where I want to be where I can just see that and decipher it.

Patb8man said:
Thanks. I do have an ext partition on my card and it I am currently using it with gumbo 1.5c bare. I was just thinking about installing 2.1 and before I did I wanted to make sure I could enable app2sd. I was just using it as an example. I just want to learn in general. Is linus distro a version of the os I would dual boot with or does it emulate in windows? Also how did you just start java? A google search and article research, book or are you in school?
Click to expand...
Click to collapse
Install Ubuntu Linux dual-boot, or short of that install VirtualBox or VMWare with Ubuntu running as a VM. You might also look at Wubi, a way to install Linux within Windows. I've never used it but it looks interesting.
Also, as with darch's post you mention, I'm no dev, learning as I go, but I use my Unix/Linux terminal chops MUCH more than java. Learn java if you want to write apps but if you want to help hack on ROM's, learn to use the shell. Android is Linux, after all.
As with anything, the best way to learn is to dive in.

Patb8man said:
for the adb shell remount part when i hook the phone up to the computer w debugging on when I run a command prompt how do I get to the adb in the first place. I am not familiar with that to begin with. I know I had to edit it when I rooted my phone...but like I said I really didnt understand what I was doing it was just a matter of following instructions. Thank you for the detailed description of whats going on...thats where I want to be where I can just see that and decipher it.
Click to expand...
Click to collapse
adb is a utility that is in the tools folder of the android sdk, which you probably already have somewhere, because it is used to root the phone. Then you'll open up a command prompt, and navigate to the tools folder of the sdk. You'll 'navigate' using the 'cd' command. Once you're navigated the command prompt to the tools folder, you can run the adb program that is in it.
Edit: in general, it can be really helpful to know both DOS and UNIX commands, even if it's just the basic ones pertaining to copying, deleting, moving, renaming, etc. Here are two good cheat sheets: http://www.computerhope.com/overview.htm http://www.computerhope.com/unix/overview.htm

Yeah, just go Start > Run > cmd (or if you're on Vista/Win7 do Start > cmd > Enter)
I do this once I have cmd running:
cd D:\Downloads\android-sdk-windows\tools
D:
adb devices
adb remount

5tr4t4 said:
Install Ubuntu Linux dual-boot, or short of that install VirtualBox or VMWare with Ubuntu running as a VM. You might also look at Wubi, a way to install Linux within Windows. I've never used it but it looks interesting.
Also, as with darch's post you mention, I'm no dev, learning as I go, but I use my Unix/Linux terminal chops MUCH more than java. Learn java if you want to write apps but if you want to help hack on ROM's, learn to use the shell. Android is Linux, after all.
As with anything, the best way to learn is to dive in.
Click to expand...
Click to collapse
Thanks very good stuff. I will check it out.
Thanks to everyone who posted so far I can see I will be up late tonight LOL.

illogic6 said:
The best way to learn about this stuff is to bite the bullet and install a Linux distro on your computer. I've also took up teaching myself to code Java in my spare time which will help you understand Android a lot better.
Also: You need an EXT partition on your SD to enable apps2sd. Is that what you're asking?
Click to expand...
Click to collapse
To expand on what illogic6 said about installing a distro on your computer, if you're just learning, it's not totally necessary to do that!
If you're a nerd like me, then you've got an old PC lying around that you can cannibalize for an Ubuntu box (a GREAT first distro to try!) btw, I think I have about 5 extra pcs laying around, which makes me an uber nerd, surely outdone though by others on this board.
However, if you DON'T have an extra pc lying around, no need to fret or worry about Dual Booting. While those are the most optimal, you can certainly try some live CD/DVDs which will boot from optical media, and not harm your existing install of your OS that's currently on the PC you're trying it on.
I did that a lot before I got into having a main Linux box at home. I tried Ubuntu (still one of my faves) Knoppix, Mandriva, Mint, and some others. I was really big at the time in getting Compiz fusion and Beryl to run (basically a badass window manager with 3d effects similar to Mac but with some cool extras.) Getting into that came with a huge price...LOTS and LOTS of command line work. It forced me to learn a lot about the Command line. And now, I feel completely comfortable doing those commands that folks share. It's essentially understanding the command line. Immerse yourself, and you'll learn a ton!!
Btw, to try ubuntu, just download the install CD. Now they offer as part of the start up menu the live cd option. It will say something to the effect of "Try Ubuntu without changing your computer's configuration" or something like that.
As always, if you have any questions or want me to clarify anything, feel free to respond to this or PM me, I'd be happy to steer you in the right direction!

kmartburrito said:
To expand on what illogic6 said about installing a distro on your computer, if you're just learning, it's not totally necessary to do that!
If you're a nerd like me, then you've got an old PC lying around that you can cannibalize for an Ubuntu box (a GREAT first distro to try!) btw, I think I have about 5 extra pcs laying around, which makes me an uber nerd, surely outdone though by others on this board.
However, if you DON'T have an extra pc lying around, no need to fret or worry about Dual Booting. While those are the most optimal, you can certainly try some live CD/DVDs which will boot from optical media, and not harm your existing install of your OS that's currently on the PC you're trying it on.
I did that a lot before I got into having a main Linux box at home. I tried Ubuntu (still one of my faves) Knoppix, Mandriva, Mint, and some others. I was really big at the time in getting Compiz fusion and Beryl to run (basically a badass window manager with 3d effects similar to Mac but with some cool extras.) Getting into that came with a huge price...LOTS and LOTS of command line work. It forced me to learn a lot about the Command line. And now, I feel completely comfortable doing those commands that folks share. It's essentially understanding the command line. Immerse yourself, and you'll learn a ton!!
Btw, to try ubuntu, just download the install CD. Now they offer as part of the start up menu the live cd option. It will say something to the effect of "Try Ubuntu without changing your computer's configuration" or something like that.
As always, if you have any questions or want me to clarify anything, feel free to respond to this or PM me, I'd be happy to steer you in the right direction!
Click to expand...
Click to collapse
Thanks I just downloaded wubi...any thoughts on that. I havent installed it yet. But it seems harmless based on the faq.

illogic6 said:
The best way to learn about this stuff is to bite the bullet and install a Linux distro on your computer.
Click to expand...
Click to collapse
You make Linux sound so bad, lol.
edit:
From the description, Wubi seems safe, but personally, I think playing with a shell to familiarize yourself with Command lines in terminal is jsut as good as a learning experience.
I, also, don't know how Wubi would be since it seems to run on Windows as an application. I'm not sure it'll provide such the necessary environment or tools that Linux has.

WUBI is a great way to get started with Linux. First, it WILL NOT damage any of your data, so it is 100% safe. Basically what is does is install Ubuntu Linux to a file, and then the file is added to the Windows bootloader. Now when you boot the Ubuntu Linux file, you will be in a non-emulated version of Ubuntu Linux, except for the fact it is running inside of a Windows partition.

Patb8man said:
Thanks I just downloaded wubi...any thoughts on that. I havent installed it yet. But it seems harmless based on the faq.
Click to expand...
Click to collapse
Oh yeah, I forgot about Wubi! It's pretty badass if I remember correctly. I'm still a little old-school and have a cd case full of live cds and dvds
That should be perfect for you!
My advice though, FORCE yourself to use the command line, as that's really where the power of Linux (and Android for that matter as you're seeing firsthand) lies.
Here's a link to a page that has some command line primers to get you started.
http://linux.byexamples.com/archives/319/command-line-tutorial-for-beginners/
I'd find something though that gets you to use the command line. Ubuntu is REALLY user friendly, and you can do a ton without touching the terminal application (where the command line lies) So find something, like Compiz Fusion for example, where you'll have to do some command line work to get it running.
once you find yourself going to the ubuntuforums.org to find out how to get something to work, you'll be on the right track

kmartburrito said:
Oh yeah, I forgot about Wubi! It's pretty badass if I remember correctly. I'm still a little old-school and have a cd case full of live cds and dvds
That should be perfect for you!
My advice though, FORCE yourself to use the command line, as that's really where the power of Linux (and Android for that matter as you're seeing firsthand) lies.
Here's a link to a page that has some command line primers to get you started.
http://linux.byexamples.com/archives/319/command-line-tutorial-for-beginners/
I'd find something though that gets you to use the command line. Ubuntu is REALLY user friendly, and you can do a ton without touching the terminal application (where the command line lies) So find something, like Compiz Fusion for example, where you'll have to do some command line work to get it running.
once you find yourself going to the ubuntuforums.org to find out how to get something to work, you'll be on the right track
Click to expand...
Click to collapse
ool yeah I added that to the bookmarks. I cant wait to get started...Im gonna install Wubi later tonight.

mrinehart93 said:
WUBI is a great way to get started with Linux. First, it WILL NOT damage any of your data, so it is 100% safe. Basically what is does is install Ubuntu Linux to a file, and then the file is added to the Windows bootloader. Now when you boot the Ubuntu Linux file, you will be in a non-emulated version of Ubuntu Linux, except for the fact it is running inside of a Windows partition.
Click to expand...
Click to collapse
Sounds extremely less complicating than setting up Grub, will definitely look into Wubi for my netbook

+1 for forcing yourself to use CLI (command line interface.)
When I first learned Linux KDE and Gnome were almost the only options and they were very immature... so most of us had to learn everything the old fashioned way first
@kniteshift: GRUB is way easier to set up now than it used to be. GRUB 1.x was horrid. 2.x is super simple, IMO. And way more versatile than LILO. [end aside]

^
I haven't touched my netbook in ages, I'll check it out. Thanks!

You can also look into setting up a persistent installation of Ubuntu on a USB drive.
I use that on my netbook a lot.
Persistent meaning it has a partition to keep track of changes you make. You can basically use it like a normal full install of Ubuntu. Plus you can move it from PC to PC if necessary too. Here's some links for info if you wanted to try it sometime:
https://wiki.ubuntu.com/LiveUsbPendrivePersistent
And the site that made this option famous:
http://www.pendrivelinux.com/
Plus, this makes you look like a Badass. Or a huge dork. I prefer the former.

Kindle Fire Root so HARD !!!!!!

hello
i just see how to root KF and it's so hard !!
i don't know how to use ADB

This seems pretty helpful in figuring out adb
http://forum.xda-developers.com/showthread.php?t=502010

When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.

http://rootkindlefire.com
Watch the YouTube video or do the step by step method. You do need to download Android SDK and install an USB driver as well. Took maybe 15 minutes all together

Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)

I just did it following this guys video. Quality is great and so are the instructions.
Shows:
-how to install adb
-how to edit the appropriate files
-how to root KF with superoneclick
http://www.youtube.com/watch?v=f409qNgpzSA&feature=related

mewshi said:
When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.
Click to expand...
Click to collapse
I'll second this. It's extremely simple and straight forward. Much simpler than the Windows method if you're at all comfortable with the command line. And as the OP said you don't even need Linux installed you can use a live CD.
Sent from my HTC Flyer P512 using Tapatalk

sum182 said:
Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)
Click to expand...
Click to collapse
This is what I had to do basically.
I created a folder android, and wouldnt let me name it .android
So in command prompt i renamed it, then I put an empty txt file, renamed it to the necessary ini, pasted that line they tell you and it worked first try.

[Q] Installing TWRP/FFF on mac, having issues

For anyone having an issue with installing TWRP and FFF on a mac here's my two cents on how to help.
Make sure you have the sdk, as well as platform-tools downloaded.
Once you've downloaded these things, you're going to need the correct fastboot.exe for macs (rename this fastboot.exe, will probably come as fastboot-mac.exe), I don't remember where I downloaded it, nor do i want to break any rules or piss any people off, but find the correct mac fastboot.exe.
Once you've done all of this, here's what you need to do.
Go to the rootzwiki, or the XDA threads for doing TWRP and FFF on linux. Once you get there, follow ALL of the directions. HOWEVER if you haven't set ADB up with directories( i think this is what it's called) you'll do a little difference.
instead of doing cd Path to ~/androidsdk/platform-tools (or whatever you have your SDK named as) you are simply going to remove the Path to and run it as
cd ~/androidsdk/platform-tools
followed by that you can start using ADB. Instead of running things as
adb root, or adb reboot, you need to include
./ before the commands, IE: ./adb root, or ./adb push
I honestly have NO idea why I have to do everything this way, from what I remember it has to do with directories or something, but either way it's what fixed everything for me.
Don't consider this a guide or anything, as I don't want to be someone who people blame if it didn't work for them, as I'm simply doing what works for me.
I hope this helps the other mac users I'm sure are here that are struggling, cause I had to remember how to do all this stuff before I realized why I was ****ing up doing all this stuff.
Good luck!

It's not a mac thing, you just aren't getting the directories right. Find where you put in in Finder, note how you got there. Once you get a terminal prompt, you need to go to that directory or add it to your PATH.
The easiest place to put the SDK directory is your user directory. In Finder, on the left side, find your username. Copy the SDK directory there. Then your terminal prompt should open to your user directory. Do an "ls" and you should see it listed. "cd" into it, then into platform-tools. Now you should be ready to go.
Once in platform-tools, do "./adb" and it should spit out a bunch of help text. If not, something is still missing. Note that the "./" is required.

[Q] ADB pull problem on linux

Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!

smokewagon said:
Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!
Click to expand...
Click to collapse
Maybe this will help?
http://www.herongyang.com/Android/adb-push-and-pull-Command.html
Not a big fan of the CLI.
Sent from my Nexus 7 (2013)

Your problem (almost certainly) is that you don't have a /sdcard directory (folder) on your computer unless you created one (there certainly is no default /sdcard in a linux desktop system).
I also don't know how you installed ADB on your computer.
(This should work, otherwise I'll have to change what I wrote below).
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
A little extra basic info for you, and welcome to linux. Soon you have the power to take over the world (ha ha ha... no, actually I'm not kidding at all).
As a basic rule, you should pretty much always be working inside of your home directory, for dealing with your personal files. Your home directory is /home/yourname. On my computers, my home is /home/kirk. My wife's home directory is /home/amy.
"~" is a shortcut for the home directory, for whomever is logged in at that moment.
If you wanted something that is on your desktop, it would be in the directory: /home/yourname/Desktop (~/Desktop). If you wanted to use your documents directory, it is : /home/yourname/Documents(~/Documents).
/home/yourname is where you usually where want to do your stuff.
"/" is the very root directory of the whole system, so you would be better off not creating and doing things like making directories like "/sdcard". That's a bad move. Leave root for system files. Not that you are necessarily going to destroy something by creating a /sdcard directory. But it'll cause you a few hassles.
So, use /home/yourname/sdcard (~/sdcard). Or if you want it on your desktop, (like I did above) use /home/yourname/Desktop/sdcard (~/Desktop/sdcard). Doing things inside of /home/yourname(~) means that you are the owner of that folder and everything in it, not root.
Otherwise you will just be causing headaches for yourself and having to grant yourself root permissions to work with those files (hassle). There's no good reason to do that to yourself. And if you did give yourself root permissions, and screwed up other stuff in the root directory like in: /etc or /dev or /bin, then you will REALLY be irritated.
Stick to your home for your personal files. /home/yourname (~)
Leave "/" or the "root" directory for system files.

You could check my little bash program for adb for Linux too. It's a program to be used in the terminal and it'll pull data off the sdcard etc. You can find it here
Sent from my Nexus 4 running Android 4.4

Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk

smokewagon said:
Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Try it without any installation of drivers just install adb tools and try the command line or my little tool. If it's not working, check the guides how to set up the usb-rules for adb
Sent from my Nexus 4 running Android 4.4

Thanks, will do.
Sent from my Nexus 4 using Tapatalk

iowabeakster said:
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
Click to expand...
Click to collapse
BAM INDEED! It worked! I am pulling the contents now. Thanks a ton, and thanks for the other basic linux info, I will put it to good use.
Any other tips on using Linux to root android?

Shooooot....
So after the pull command finished, i opened the sdcard directory I created on my desktop, and it was empty....the pull command said this when it was done...
1733 files pulled. 0 files skipped.
2129 KB/s (995292697 bytes in 456.480s)
Any ideas?

Ok, I played with some settings and got it to work, though I don't know why it worked.
USB Debugged is enabled.
The first time I tried to 'pull' i had my USB computer connection set to "Camera (PTP)" - it didn't work.
I tried again changing the USB computer connection to "Media device (MTP)" - it didn't work.
I changed it back to "Camera (PTP)" and my computer recognized it in a different way than the first time (a dialog box popped up asking me what I wanted to do with the pictures that were on the device I had connected, this didn't happen the first time).
I am glad the pull command finally worked, I just wish I knew why.
I guess it's a tough road being a linux NOOB and a (near) Android NOOB. It's good to learn something new and keep my brain young.