2.0.5, 2.0.6 don't work on Motorola Milestone XT720

[GoogleCodeExporter]

I'm running the Motorola Milestone XT720, Android 2.1, rooted.

Neither 2.0.5 nor 2.0.6 work, however 2.0.2 does.

What steps will reproduce the problem?
1. Press the start tethering button
2. See the "Unable to start tethering. Is your device rooted?" message.
3.

Please provide any additional information below.

It looks like 'iwconfig tiwlan0 commit' doesn't work:

(paulv@schrodinger) (02:49 AM) [1] (~)$ adb shell
$ su 
# /data/data/android.tether/bin/tether start 1
about to run: [/data/data/android.tether/bin/ifconfig tiwlan0 192.168.2.254 
netmask 255.255.255.0]
about to run: [/data/data/android.tether/bin/ifconfig tiwlan0 up]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 mode ad-hoc]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 essid 
AndroidTether]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 channel 1]
about to run: [/data/data/android.tether/bin/iwconfig tiwlan0 commit]
Error for wireless request "Commit changes" (8B00) :
    SET failed on device tiwlan0 ; Operation not supported on transport endpoint.
about to run: [/data/data/android.tether/bin/fixpersist.sh tiwlan0 
AndroidTether 1 & echo $! > /data/data/android.tether/var/fixpersist.pid]
about to run: [/data/data/android.tether/bin/iptables -N wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -F PREROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F POSTROUTING]
about to run: [/data/data/android.tether/bin/iptables -t nat -F]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -m 
state --state ESTABLISHED,RELATED -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -s 
192.168.2.0/24 -j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -p 47 
-j ACCEPT]
about to run: [/data/data/android.tether/bin/iptables -A wireless-tether -j 
DROP]
about to run: [/data/data/android.tether/bin/iptables -A FORWARD -j 
wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -t nat -I POSTROUTING -s 
192.168.2.0/24 -j MASQUERADE]
about to run: [/data/data/android.tether/bin/dnsmasq -i tiwlan0 
--resolv-file=/data/data/android.tether/conf/resolv.conf 
--conf-file=/data/data/android.tether/conf/dnsmasq.conf]
script result was []
# 

Please let me know if there's anything else I can do help. I'm very comfortable 
getting my hands dirty with linux.

Original issue reported on code.google.com by pa...@canonical.org on 6 Jan 2011 at 8:01

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i have the save problem with you.
but starting by adb shell is Ok in fact,our output msg is same.

it looks like a problem about "rooted".

Original comment by wangqion...@gmail.com on 6 Jan 2011 at 9:12

[GoogleCodeExporter]

Mmmmh. If you get a "Unable to start tethering. Is your device rooted?"-error 
message your phone is most likely not rooted correctly.

Check permissions for /system/bin/su or the "Superuser"-app blocks the 
su-request.

The output when starting via adb shell looks ok. The "commit" fails on most 
devices and is not mandatory.

And ... you have the access-control enabled, right? Try to disable it. Access 
control needs the "CONFIG_NETFILTER_XT_MATCH_MAC"-option compiled into the 
kernel. The app tries to check that but motorola is so kind to disable another 
kernel-option which dumps the current config to /proc/config.gz - so the app 
can't detect that.

So, please make sure your device is correctly rooted and the "Superuser"-app is 
configured right ... disable access-control and try again.

Thx.

Original comment by harald....@gmail.com on 6 Jan 2011 at 12:41

[GoogleCodeExporter]

i check the rooted (permissions for /system/bin/su) again,it looks like ok.

ls -l /system/bin/ | busybox grep su
-rwxr-xr-x root     shell        5448 2010-03-04 18:33 surfaceflinger
lrwxrwxrwx root     shell             2010-10-16 16:44 md5sum -> motobox
-rwsr-xr-x root     root        76232 2000-01-01 08:01 su
-rwxr-xr-x root     shell      197000 2010-03-04 18:33 wpa_supplicant

tether is work fine when i start/stop it via adb shell,but the normal starting 
is fail.

supersuer is not installed and access-control is disable.

Original comment by wangqion...@gmail.com on 6 Jan 2011 at 2:42

[GoogleCodeExporter]

When I reset Wireless Tether's remembered permissions from the Superuser 
whitelist, here's what I see:

Start Wireless Tether
Press to Start Tethering
Please wait while starting...
Superuser request:
  App: Wireless Tether
  Package: android.tether
  Requested UID: root(0)
  Command: /data/data/an...tether start 1

I uncheck 'Remember' and select Allow
Wireless Tether has been granted superuser permissions
Unable to start tethering. Is your device rooted?

(paulv@schrodinger) (05:31 AM) [1] (~)$ adb shell
$ ls -l /system/bin/su
lrwxrwxrwx root     root              2010-12-19 18:44 su -> /system/xbin/su
$ ls -l /system/xbin/su
-rwsr-xr-x root     root        26264 2010-12-19 18:44 su

I don't have access control enabled.

Original comment by pa...@canonical.org on 6 Jan 2011 at 7:18

[GoogleCodeExporter]

If you are able to start tethering via adb but not via GUI there is something 
wrong with "su" and/or the "Superuser"-app.

The app checks if /system/bin/su and/or /system/xbin/su exists ... it takes the 
one which is in "$PATH".

A very simple method to get a proper su-environment:

adb root
adb remount
adb shell
cd /system/bin
cat sh > su
chmod 4755 su

"adb root" restarts adb in superuser-mode. "adb remount" mounts the 
/system-partition writable. 

Original comment by harald....@gmail.com on 7 Jan 2011 at 7:59

[GoogleCodeExporter]

I am not a programmer, but a user on the other end of this issue.  Is there a 
one click "reroot" that will correct the issue.  If so, please email me a link 
mindsnag@gmail.com

Was rooted with Z4root and then tried with superoneclick via my windows7 
machine and did both exploits and shell.
one hint is that the test of rooting doesn't yeild an alert in super user and 
the log is empty.

Many thanks,

David

Original comment by dav...@econet.com on 25 Feb 2011 at 11:17