seems to be a windows/putty problem because adb shell works wonderful on ubuntu with the default shell ...

btw. you can also easily get a sshd (dropbear) running. then you can ssh onto the device over wifi ... i can provide the binary+explanation if anybody is interested.

I'm very interested in that !

Sent from my GT-I9000 using XDA App

virus found

Originally Posted by mathieumeuh

I'm very interested in that !

Sent from my GT-I9000 using XDA App

here is the explanation how to set it up (cyanogenmod wiki):
http://wiki.cyanogenmod.com/index.ph...evice_with_SSH

basically you have to create the keys on your pc and copy them onto the device. then you can connect via key-auth. if you want dropbear to autostart @boot you could add it to playlogos1 ...

and here are the binary's you need (including the missing dropbear-keygen) and a bash binary:
http://www.multiupload.com/B0L9FDQHPB

bash is optional of course but it's very nice to have tab-completion and the other improvements bash offers over sh. to replace sh with bash do the following:

cp bash /system/bin/
chmod 0755 /system/bin/bash
mv /system/bin/sh /system/bin/sh_OLD
ln -s /system/bin/bash /system/bin/sh

the chmod is really important. i forgot it once and then was unable to get shell access even over adb. was a pain in the ass to fix it again

Originally Posted by jodue

seems to be a windows/putty problem because adb shell works wonderful on ubuntu with the default shell ...

btw. you can also easily get a sshd (dropbear) running. then you can ssh onto the device over wifi ... i can provide the binary+explanation if anybody is interested.

You seem to miss the point of this development. First, your method is mentioned as one of the possible workarounds in the first post. Second you need to have some kind of telnet/ssh server running on the phone, which you don't need, if using adb.

Meanwhile you don't even need a rooted phone or busybox or anything to get this thing working.

The main problem with adb shell under windows, that it uses the standard cmd.exe to run, and uses the standard cmd.exe's "readline" support, which only supports the up and down keys for history (and even that it only supports that within one session).

Putty is mainly the only good (xterm compatible) terminal emulator for windows (msys's or cygwin's rxvt is good too, but "adb shell" was programmed in a way that makes it kinda useless under rxvt too). There are two ways to fix this. One is to make adb.exe more comptible with rxvt, the other is to skip adb.exe entirelly and communicate with the adb server without it. This project utilises the latter.

But what is the advantage compared to "normal" ABD

But what is the advantage compared to "normal" ADB ?

Thank you!

Originally Posted by DirkStorck

But what is the advantage compared to "normal" ABD

It has a real xterm compatible terminal emulator. Is you use busybox >= 1.17.1 you've got coloring, tab completion, resize events, keyboard events (applicatios like vi is working), etc.

This is the reason I recommend a faulty device: without the problems with the SGS the developments would go much slower Thank you for this putty, i have it connecting to the bash. Color coding and keys work perfectly.

Thanks for this Sztupy!

I hated using windows cmd.exe to access a linux shell