Hi!
I have tried SSHDroid, QuickSSHD and also Dropbear directly from the command line with logging to STD_ERR, but I am not able to connect to my GalaxyTab 10.1. Using nmap from WinXP I see the port, but it is filtered:
PORT STATE SERVICE
22/tcp filtered ssh
Using netstat on the tab shows that the connection has begun, but it stops with syn_recv and never get established. Using DropBear with logging it seems like no traffic is passed on to the server as no new log appears at the connection moment (or later).
The problem occured after rooting the device and has been persistent even though I have changed back to stock ROM and manager. Now I am using "recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5" and "Task650&Phantom_V5_Final.zip".
Using netcat I am able to send traffic both ways on the same ports.
I would really appreciate any suggestions on how to solve this as I have I feel lost without SSH
BR,
Henrik
It works okay for me with stock rom, rooted and SSHDroid. Set the superuser to grant automatic root permissions. Launch the SSHDroid and set - require wifi and password to yes.Check the port and make sure its 22 in the SSHDroid settings. Then start the server, you should see a confirmation saying the process is listening in port 22. You would also see a prompt stating the SSHDroid has been granted SU permissions. LEt me know if this helps!
SOLVED
Thanks for suggestions mango1122! I have for sure tried all those things too many times already But I got a breakthrough today by using the Overcome ROM and kernel (see galaxytabhacks).
Using this ROM, SSHDroid worked out of the box. I have unfortunately no clue why this works, but what made me try this ROM was this comment:
"For Custom roms: Be aware, I’ve put the wifi module right in the ramdisk (which is where it is on 10.1 stock). Please move over the modules folder in /system/lib prior to flashing, if this applies to you."
BR,
Henrik
Solved...again...
Update...had to take a long break as it didn't work when I got home from work that day in Nov...it was my home router that caused the problem, I guess combined with something in the Dropbear/SSHDroid application for Android 3.0 as there is no problem using SSHDroid on my smartphone with Android 2.3.3 on the same router. I assume it has something to do with the fact that it listens on tcp6?
Using another router solved the problem.
BR,
Henrik
Hello!
I am trying to print UIDs under which the currently running apps/processes run and i am having problems since android doesn't have files like /etc/passwd. I want to know if it is possible to get UID(number) from "system","radio","root", ... in adb shell.
Thanks!
Any recommendations for a good ssh server to run on the phone? It's easier to me to run a shell, vi, scp via something like putty that works well as a real terminal than 'adb shell' via the command prompt where vi is all messed up, etc. I tried Android Commander as an alternative but it's too buggy at least against our phone.
So what is *the* ssh server to run on the phone with the option to keep it disabled most of the time, except when I need to use it?
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
Hi. Im using Ubuntu Touch 13.10 pre-installed version on GNex
I don't know when is but ubuntu touch img file included openssh-server
after that ssh server doesn't automatically start
so I always have to type 'service ssh start' manually ( /etc/init.d/ssh start doesn't work )
I have tried update-rc.d ssh defaults, checked /etc/init/ssh.conf, and installed sysv-rc-conf and set run level for ssh
what's wrong? And is there anyway without adding my own script?
Try to put the command in /etc/rc.local. I can't test it because I don't have the device with me.