View Single Post
Old October 27th, 2009, 04:17 PM   #28 (permalink)
kam187
Senior Member
 
kam187's Avatar
 
Join Date: Aug 2009
Location: UK
Posts: 1,320
 
Device(s): Nexus One
Thanks: 3
Thanked 46 Times in 28 Posts
Default

Yeah those are anoying for us windows users! The best thing to do is use putty to a redicrected local port.

I'm sure, like me, you dont like to keep ssh running all the time, nor wifi, so do this:

- Turn on ssh in galaxoconfig and reboot - this will generate the ssh keys
- Turn off ssh in galaxoconfig and reboot.

You only need to do that once and never again.

Now make two .bat files in the adb tools directory:

SSH_ON.bat and put this inside it:

adb forward tcp:9999 tcp:2222
adb shell "/system/xbin/dropbear -E -A -N root -U 0 -G 0 -C password -p 2222"

and also SSH_OFF.bat and put this inside it
adb shell "kill `ps | grep dropbear | awk '{print $1}'`"

You can change 'password' to anything you like. The SSH_OFF just finds the dropbear pid and kills it.

After running SSH_ON just putty to 127.0.0.1 and port 9999, make sure to select ssh as the protocol. And hey presto a nice colour shell, and stuff like vim also works!

As soon as you're in type bash to switch to bash shell, and get history to work.

So save a profile in putty, and every time you want to connect, double click SSH_ON, and the windows will stay open showing u ssh connections. Use putty to connect.

When you're done run SSH_OFF, and the SSH_ON windows should dissapear as dropbear was killed.
kam187 is offline  
Last edited by kam187; October 27th, 2009 at 04:19 PM.
Reply With Quote