I have the XOOM wifi and not ready to root it yet. But I did want to get adb listening over tcp ip. I suspect this is where I'm failing.
I already tried this on my XOOM. Not getting any verbose feedback saying if anything failed or succeeded.
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
I just want to be able to run some adb commands locally from my terminal app on my XOOM.
Bump. Somewhere where I don't have PC access atm.
Related
Whipped this up last night, because I wanted to be able get root commands on my phone, from my phone. This is a safe/benign way to get root access (ie, you don't have to have a suroot or su laying around, potentially opening a security hole).
I'll throw this up on the Market tonight too.
This is a raw telnet client, so don't expect any fancy!
Terminal Emulator and Busybox
Nice. That makes it even easier No adb or wifi required.
You can also download the Terminal Emulator program from the market, and then install the busybox binary, which has a telnet command.
If you don't have root on your phone yet, use adb to push busybox to /data/local, which is owned by the shell user, so you can chmod it from an adb shell and make it executable.
It still requires adb, but no wifi.
Hello,
First off, let me say, this is my first android device. I have some experience with linux and previously owned a rooted Palm Pre.
I have an HTC EVO, and have rooted it (at least I think it's rooted), with a program called unrEVOked. It flashed a NAND called ClockworkMod Recovery (2.5.0.1), and I can get to the shell using the adb shell command when it is in recovery mode.
However, even with the SuperUser app installed, I'm having trouble running sudo or any command at the terminal (on the phone), and the apps appear to also be having trouble executing any commands that are within /sbin/ (such as killall for the Shark capture packet sniffer). This is persistent while in USB Debugging Mode and running adb shell.
I didn't have to interact with the system at all during unrEVOked, including creating a user, which struck me as odd. Also, never set up an SSH server daemon, but that's okay. I'd be a happy guy if 1) I could actually use commands in /sbin/ and programs could also do this. Note that at a terminal, when I run aname, it tells me that I don't have permission. sudo su does the same.
Alright... I can get su root via the adb shell and terminal emulator.
androidpolice com/2010/05/24/that-was-quick-evo-4gs-already-been-rooted/
It still doesn't appear that apps like a file manager, and Shark packet sniffer can get root though; even with granting them SuperUser access. Any ideas?
Any help is appreciated.
Thanks,
Matt
Hello all,
As per my previous thread, I now have a rooted nonsense free Android.
Now I'm trying to connect to it via adb which is proving tricky.
The device is rooted (unrevoked/clockwork mod) and in recovery mode it'll adb just like that. However, when the device is running, I can't pick it up. I get:
Code:
$ adb devices
List of devices attached
???????????? no permissions
Now I have the old superuser skull and crossbones app thingy on my phone running. I've also tried to connect locally using connectbot and this works, I get sh running just fine. I can also su and get root.
However, even if I stop and restart adbd it changes nothing from the pov of the host... in other words it's not letting me connect.
Specifically, I can see:
Code:
sh-3.2# ps
...
root 1978 1 3142 200 ffffffff 0000f474 /sbin/adbd
...
$ whoami
whoami: unknown uid 0
from connectbot on the device
A pointer in the right direction would be wonderful!
_glokta.
Hi,
I have a Verizon Samsung Galaxy S3 SCH-I535.
I have rooted it using this guide. I realize there was probably an easier way to root it, but regardless it worked fine, I have root access.
The phone is returned to factory condition, pretty much, but I need to recover data from it. There is no microSD card.
I have tried to follow this guide for recovering the internal memory without being able to transfer the internal memory to my computer. I'm stuck at the data transfer point.
I've followed the guide to the letter, except I'm trying to recover memory block /dev/block/mmcblk0p23 (and I've also tried simply /dev/block/mmcblk0), so I've modified the commands to the following:
Code:
adb forward tcp:5555 tcp:5555
adb shell
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p23
And in the other Cygwin terminal:
Code:
adb forward tcp:5555 tcp:5555
cd /nexus
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p23.raw
Screenshots attached. I'm not sure why, but the data stays at 0 B/s no matter how long I let it run.
Am I missing something? Am I doing something wrong? I've installed Busybox on the phone (it's in xbin, not bin, hence the modified syntax). Cygwin (with pv and util-linux), Netcat, and ADB on the computer. USB debugging mode is enabled on the phone (ADB connection works).
I really need to pull the internal data off of this phone soon... can anyone help me get this figured out please? Thanks.
mastercsmc said:
Hi,
I have a Verizon Samsung Galaxy S3 SCH-I535.
I have rooted it using this guide. I realize there was probably an easier way to root it, but regardless it worked fine, I have root access.
The phone is returned to factory condition, pretty much, but I need to recover data from it. There is no microSD card.
I have tried to follow this guide for recovering the internal memory without being able to transfer the internal memory to my computer. I'm stuck at the data transfer point.
I've followed the guide to the letter, except I'm trying to recover memory block /dev/block/mmcblk0p23 (and I've also tried simply /dev/block/mmcblk0), so I've modified the commands to the following:
Code:
adb forward tcp:5555 tcp:5555
adb shell
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0p23
And in the other Cygwin terminal:
Code:
adb forward tcp:5555 tcp:5555
cd /nexus
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p23.raw
Screenshots attached. I'm not sure why, but the data stays at 0 B/s no matter how long I let it run.
Am I missing something? Am I doing something wrong? I've installed Busybox on the phone (it's in xbin, not bin, hence the modified syntax). Cygwin (with pv and util-linux), Netcat, and ADB on the computer. USB debugging mode is enabled on the phone (ADB connection works).
I really need to pull the internal data off of this phone soon... can anyone help me get this figured out please? Thanks.
Click to expand...
Click to collapse
Are you running cygwin as an administrator? Are you requesting superuser access by typing su after adb shell?
billard412 said:
Are you running cygwin as an administrator? Are you requesting superuser access by typing su after adb shell?
Click to expand...
Click to collapse
Hi billard, thank you for the response.
I have tried using su (# prompt instead of $ appears, so yes it is working) after adb shell, with no change in results.
I hadn't tried running Cygwin as administrator, but just made that change as well to see if it would make a difference. Still no dice.
I've also ensured NTFS permissions in the /nexus folder (C:\Cygwin\nexus) are "full access", and there are no issues there, either. Screen shot attached of latest attempt (Cygwin is "run as administrator"/su command used).
mastercsmc said:
Hi billard, thank you for the response.
I have tried using su (# prompt instead of $ appears, so yes it is working) after adb shell, with no change in results.
I hadn't tried running Cygwin as administrator, but just made that change as well to see if it would make a difference. Still no dice.
I've also ensured NTFS permissions in the /nexus folder (C:\Cygwin\nexus) are "full access", and there are no issues there, either. Screen shot attached of latest attempt (Cygwin is "run as administrator"/su command used).
Click to expand...
Click to collapse
Don't know why I didn't catch this sooner. But what lead you to believe it was mmcblk0p23 you needed to use? I'm not sure exactly what that partition is(if it exists) but the data partition is mmcblk0p15 I believe on the US S3's. Try that
billard412 said:
Don't know why I didn't catch this sooner. But what lead you to believe it was mmcblk0p23 you needed to use? I'm not sure exactly what that partition is(if it exists) but the data partition is mmcblk0p15 I believe on the US S3's. Try that
Click to expand...
Click to collapse
I was guessing it was the highest numerical memory block, and /system/dev/block ls lists 23 as the highest number.
I just tried with mmcblk0p15 and have the same exact frustrating 0 B/s indefinite results. -_-
I'm trying to send runtime commands like:
adb.exe -s 127.0.0.1:5555 shell screencap /sdcard/ss.png
To the adb server running, using SendMessage / Windows Message, does adb even support it? If so I wonder how it needs to be sent.
I know I could pass runtime commands using cmd or running directly to the adb.exe.
My goal is to keep just one running and avoid spamming a new ADB for each command sent. Is it even possible?
Any other suggestion is welcome.
When command
Code:
adb start-server
is run then one ADB ( server ) session gets established.
This session lasts untill command
Code:
adb kill-server
is run.
Look into Windows Task Manager.
The question is how to communicate with this window using sendmessage or any other option that does involve you manually typing in the console.
ADB isn't a Windows executable you can send messages to, it only offers a CLI.