From the above, you should be able to see that you can send adb commands from your machine to your Droid using the following:

Code:

adb -s [yourdeviceserialnumberhere] shell

The above will start an interactive shell from your machine, but running on your device. So if you "cd" to a directory, it will be on your device. Use "ls" or "ls -l" to see what is in the directory that your are currently in. NOTE: Runing the adb shell directly has gotten me nowhere as far as rooting the device, but its a good place to start learning.

Now for the fun part!! You can "pull" some data from your device using:

This will try and write all the files and folders from the "/system" directory on your Droid, to wherever you decide you want it on you machine.

I did the "pull" on a mac and I was able to get about 140mb of the data from the following directories on my Droid:

/dev
/proc
/sys
/system​

I did it both as an admin and a super user on the mac and I got about the same results. My Droid was in the regular boot mode. I have not tried booting into the restore or safe modes and tried a "pull" ... yet.

One last thing. I noticed the "adb root" command too, but I get an error back saying that you can not root on a production build of android. Perhaps there is a way to fool adb into thinking you have a developer device/build, maybe by altering the "build.properties" file. I haven't looked into that, nor do I really know if it would work. I'm really not an android developer, but if anyone out there is, maybe they could tell us what lets the adb shell know that a device is a production build, rather than a development build.

From the above, you should be able to see that you can send adb commands from your machine to your Droid using the following:

Code:

adb -s [yourdeviceserialnumberhere] shell

The above will start an interactive shell from your machine, but running on your device. So if you "cd" to a directory, it will be on your device. Use "ls" or "ls -l" to see what is in the directory that your are currently in. NOTE: Runing the adb shell directly has gotten me nowhere as far as rooting the device, but its a good place to start learning.

Now for the fun part!! You can "pull" some data from your device using:

This will try and write all the files and folders from the "/system" directory on your Droid, to wherever you decide you want it on you machine.

I did the "pull" on a mac and I was able to get about 140mb of the data from the following directories on my Droid:

/dev
/proc
/sys
/system​

I did it both as an admin and a super user on the mac and I got about the same results. My Droid was in the regular boot mode. I have not tried booting into the restore or safe modes and tried a "pull" ... yet.

One last thing. I noticed the "adb root" command too, but I get an error back saying that you can not root on a production build of android. Perhaps there is a way to fool adb into thinking you have a developer device/build, maybe by altering the "build.properties" file. I haven't looked into that, nor do I really know if it would work. I'm really not an android developer, but if anyone out there is, maybe they could tell us what lets the adb shell know that a device is a production build, rather than a development build.

I better get going now. Have fun hacking your Droid!! :icon_ banana:

Click to expand...

omg lol if i didn't feel dumb before i sure do now!!!! wowzers!! lol are you rich too?

Good post. People please be CAREFUL while experimenting with these commands. You shouldn't really be able to mux things up too bad without root, but that doesn't mean to just start randomly rm'ing files and such.

so my problem is that now that adb is up in the DOS window, i can't get ride of the C:\ to the far left right by where you would type the commands, so i can't get any of the commands to work, like the one to see if i could send adb commands to my phone. what am i missing here?

well here's my current situation. if it helps you to know, my adb directory is C:\Android\android-sdk-windows\tools\adb. Here's what i put into the msdos window (black is what was there, red is what i typed):

well here's my current situation. if it helps you to know, my adb directory is C:\Android\android-sdk-windows\tools\adb. Here's what i put into the msdos window (black is what was there, red is what i typed):

so how do i get permission allowed? i tried it a couple times, change things up, added or removed the [ ] on either end of the serial number, tried the super user (su) command. nothing!

Click to expand...

Here is what works for me. make sure that you have usb debugging enabled in your settings on the phone, and my phone is unmounted. I have changed my directory structure to match yours.

at the c:\, type

cd \Android\android-sdk-windows\tools\

this should give you

c:\android\android-sdk-windows\tools>

at this point I just type: adb shell (no switches)

This is what I see after: adb shell
* daemon not running. starting it now*
* daemon started successfully *
$

then I type: su

this should give you the #

Then you should be in.

Not sure if you need to physically be in the tools subdirectory when invoking the shell, or it is the switch, or perhaps the debugging switch on the phone, but the above always works for me. Sorry man, I'm trying.

you don't have to apologize, you been a fantastic help actually! i'm alot farther than when i started, thanks to you.

so i tried this a few times, and the first time i did it, it didn't give me the #, so i tried it again, and now it is displaying it, but that code to see if i can send commands to my phone stopped, and i didn't get anything about the daemon not running then starting up. but the pop up window came up on my phone to confirm superuser access, so i guess that's good. now to try something to confirm this...

the daemon thing is likley a new thing on my computer likley indicating that sdk/adb is starting the communication with my phone as to the comlink being properly established when I plug in my phone. You may not see this.

If you are getting the "#" in your command line, then methinks you are off to the pony races. Now whip them ponies, and try not to brick anything.

hahaha. i got the # in my command line, and my ponies are staying put until i see some more feedback! :reddroid:

i don't know what i did, but i looked at my phone and it said something like % e yadda yadda < (i know that's all very important, but anyway) mms. stopped. had to force close. so i tried to open messaging and it kept force closing..so for some brilliant reason i chose to reboot the phone. now i'm stuck at the Motorola logo, (stuck in boot loader) any help?

You need to use forward slashes for navigating your directory structure, backslash is the escape character, you use it before spaces or other special character to make sure they are interpreted correctly.

Useful Searches

About DroidForums.net

DroidForums.net was founded in 2009 originally dedicated for the Motorola Droid, the first Verizon Android Phone. We have since expanded our community to cover all Android Phones, Android Tablets, and Android Wearables. We discuss various topics including Android Help, Android Device Reviews, Android Apps, Phone Accessories, Android Games and more. Our ultimate goal is to be the Internet's best and largest Android Forum.