• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root How-to Thread For ADB SHELL

Is the Thread Helpful enough to sticky it?

  • Yes

    Votes: 48 96.0%
  • No

    Votes: 2 4.0%

  • Total voters
    50
I'm having the same issue. Can someone help out or go into a little more detail.

I installed the SDK and everything. All the drivers were installed fine (3 Drivers)
 
I was trying to use proxoid, so I simply followed following instructions.

First, plug in your Android phone via usb. Then, create a file
/etc/udev/rules.d/09-android.rules containing the two lines
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666", GROUP="plugdev"

Then, restart udev by issuing the command
sudo /etc/init.d/udev restart

./adb forward tcp:8080 tcp:8080

------------------
the last part tells me that device is not found
also, when I run ./adb devices,
it doesn't show me anything.

Can anyone give me a clue?
 
I'm having trouble getting Proxoid to work on my Ubuntu netbook also. Very curious if anyone can chime in here.
 
khunny7@khunny7-x60s:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

khunny7@khunny7-x60s:~$ lsusb
Bus 001 Device 013: ID 04e8:6603 Samsung Electronics Co., Ltd
Bus 001 Device 012: ID 0c45:62f0 Microdia
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
khunny7@khunny7-x60s:~$

I think I did pretty much everything that some of the references told me to do.
I wonder what my problem is.
Can anybody help me?
 
No fix yet, but I did try a live boot version of 10.04, it looks so cool! But going to wait until general release at the end of the month.
 
I've been working on this problem the past few nights... I'm running out of Ideas on the rules files...
 
I just installed BH_Man's (Port) Behold 2 1.6 Factory w/ Busybox & Rooted Kernel and am trying to get the Camera fix to work. However when I type in
adb push C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix /system/app
I get
Android Debug Bridge version 1.0.25

-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port

networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be updated.

- If it is "system" or "data", only the corresponding partition is updated.
Which I'm assuming is the 'user manual'. What am I typing wrong?
 
did you do adb devices to makes sure your device is "online"

if you want to get onto the irc chat, i can hop on to help you out really quick.
 
Because of the way your are placing the command in the box you have 2 choices:

a) adb push "C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix" /system/app

OR

b) copy the Camer_16_Fix to the same folder where ADB is and then run the command this way:
adb push Camer_16_Fix /system/app

The problem:

Because of the C:\Documents and Settings\Compaq_Owner\Desktop path, DOS will interpret that each word is a command, that's why you have to include the "" at the star and end because its the only way you cant tell the OS that you are dealing with one full string.

Choose what works for you best, and let us know.
 
Heh! Welcome to Windows 95! :D

Because of the way your are placing the command in the box you have 2 choices:

a) adb push "C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix" /system/app

OR

b) copy the Camer_16_Fix to the same folder where ADB is and then run the command this way:
adb push Camer_16_Fix /system/app

The problem:

Because of the C:\Documents and Settings\Compaq_Owner\Desktop path, DOS will interpret that each word is a command, that's why you have to include the "" at the star and end because its the only way you cant tell the OS that you are dealing with one full string.

Choose what works for you best, and let us know.
 
Because of the way your are placing the command in the box you have 2 choices:

a) adb push "C:\Documents and Settings\Compaq_Owner\Desktop\Camer_16_Fix" /system/app

OR

b) copy the Camer_16_Fix to the same folder where ADB is and then run the command this way:
adb push Camer_16_Fix /system/app

The problem:

Because of the C:\Documents and Settings\Compaq_Owner\Desktop path, DOS will interpret that each word is a command, that's why you have to include the "" at the star and end because its the only way you cant tell the OS that you are dealing with one full string.

Choose what works for you best, and let us know.
The quotes worked perfectly. thank you.
 
no adb shell!

just do this

cd c:\androidSDK\tools (only if you didn't set this up by editing PATH in environment variables)
adb push c:\Mms.apk /system/app

thats it you're done :)
 
no prob at all!

just an fyi if you want to thank someone when folks help ya out just click the "thanks" button in the post you found helpful .:D
 
I removed TwMms.apk fine from the bh_mans behold 2 1.6 no touchtiz. But I could not get the Mms.apk to install until I followed behold_this's rules. It seemed to install just fine, but now everytime I open it, it immediately closes. I don't even get a force close screen. It just shuts down before the page even comes together. I'm not sure what the problem is. On a side note I seem to have been having texting problems all weekend. (I just removed TWMms.apk today), but apparantly people say they have been sending messages to me, and I got a total of ZERO all weekend.
Any suggestions?
 
Back
Top Bottom