It worked for me without SU. I didn't use gscript either.Test it in a Terminal but it shouldnt work without root... otherwise it is a security issue on android/your ROM.
Billy
It worked for me without SU. I didn't use gscript either.Test it in a Terminal but it shouldnt work without root... otherwise it is a security issue on android/your ROM.
Nope... couldn't route from public to private network... well perhaps if you did some reverse proxy magic but that's going to be a lot of effort and routing config.Is it possible to use adb over a cell network with a method similar to this?
C:\adb\android-sdk-windows\tools>adb shell ls -al
drwxr-xr-x 14 0 0 0 Jun 9 12:26 ←[1;34m.←[0m
drwxr-xr-x 14 0 0 0 Jun 9 12:26 ←[1;34m..←[0m
drwxr-xr-x 3 0 0 0 Jun 9 12:26 ←[1;34macct←[0m
drwxrwx--x 1 1000 2001 2048 Jun 9 09:15 ←[1;34mcache←[0m
dr-x------ 2 0 0 0 Jun 9 12:26 ←[1;34mconfig←[0m
lrwxrwxrwx 1 0 0 17 Jun 9 12:26 ←[1;36md←[0m -> ←[1;34m/sys/kernel/debug←[0m
Small upate: I noticed that I actually only have the problems with ls -al when the phone is fully booted. When I use adb booted in Recovery (CWM) the file listings are fine.I think messing around with this screwed up my adb output somehow, because now I'm having this problem
....
I never had this problem before. I'm using Win7 (64-bit)
alias ls='ls --color=never'
C:\android>adb tcpip 5555
restarting in TCP mode port: 5555
C:\android>adb connect 192.168.0.115
unable to connect to 192.168.0.115:5555
Just get the wireless ADB app from Play Store. It had work on all my rooted app.Unfortunately, it does not work for me on rooted Samsung Galaxy Ace (Android 2.3.6):
Couldn't you help me with this problem?Code:C:\android>adb tcpip 5555 restarting in TCP mode port: 5555 C:\android>adb connect 192.168.0.115 unable to connect to 192.168.0.115:5555
Thanks, but I'd like to make it working without any 3rd party apps and, besides that, to have an opportunity to use ADB on Wi-Fi on unrooted phones also.Just get the wireless ADB app from Play Store. It had work on all my rooted app.