Working in htc TATTOO root only from CLI

[GoogleCodeExporter]

Which device (manufacturer, type)?
HTC Tattoo [rooted] 

Which firmware is installed?
donut 1.6 original HTC firmware

What version of wireless tether are you using?
wireless_tether_2_0_1.apk

What steps will reproduce the problem?
1. start wireless tether from apps 
2. try to start clicking
3. a message appear saying "Unable to start tethering. Please try again"

What is the expected output? What do you see instead?
Apps should start tethering while it only display a message

Please provide any additional information below.
If I start the app from the command line script it works. I am able to see SSID 
and 
to start and stop the app, while from the GUI it does not run.

# getprop        
[ro.secure]: [1]
[ro.allow.mock.location]: [0]
[ro.debuggable]: [0]
[persist.service.adb.enable]: [1]
[ro.factorytest]: [0]

[....]a lot of lines[....]

[tether.status]: [stopped]
[tether.mode]: [wifi]

# ./tether stop 1
about to run: [/data/data/android.tether/bin/ifconfig tiwlan0 down]
error: SIOCGIFFLAGS (No such device)
about to run: [/data/data/android.tether/bin/iptables -D FORWARD -j wireless-
tether]
iptables v1.3.7: Couldn't find target `wireless-tether'

Try `iptables -h' or 'iptables --help' for more information.
script result was []

# ./tether start 1
about to run: [/system/bin/ip route delete table gprs]
RTNETLINK answers: No such process
about to run: [/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e 
/proc/calibration -i /data/data/android.tether/conf/tiwlan.ini]
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/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 -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 []

# getprop
[ro.secure]: [1]
[ro.allow.mock.location]: [0]
[ro.debuggable]: [0]
[persist.service.adb.enable]: [1]
[ro.factorytest]: [0]

[....]a lot of lines[....]

[init.svc.wlan_loader]: [stopped]
[wlan.driver.status]: [ok]
[init.svc.wpa_supplicant]: [stopped]
[net.dnschange]: [354]
[dhcp.tiwlan0.result]: [failed]
[init.svc.dhcpcd]: [stopped]
[dhcp.tiwlan0.pid]: [12822]
[dhcp.tiwlan0.reason]: [BOUND]
[dev.bootcomplete]: [1]
[sys.settings_system_version]: [1562]
[ro.runtime.started]: [1275343922002]
[gsm.version.ril-impl]: [HTC-RIL 1.6.1002HM (Sep 22 2009,11:44:43)]
[gsm.sim.types]: []
[gsm.sim.operator.numeric]: [22210]
[gsm.sim.operator.alpha]: [PosteMobile]
[gsm.sim.operator.iso-country]: [it]
[gsm.sim.cbmi.channel]: [0,1]
[gsm.sim.state]: [READY]
[dhcp.tiwlan0.dns1]: [8.8.8.8]
[dhcp.tiwlan0.dns2]: [8.8.4.4]
[dhcp.tiwlan0.dns3]: []
[dhcp.tiwlan0.dns4]: []
[dhcp.tiwlan0.ipaddress]: [192.168.0.103]
[dhcp.tiwlan0.gateway]: [192.168.0.1]
[dhcp.tiwlan0.mask]: [255.255.255.0]
[dhcp.tiwlan0.leasetime]: [86400]
[dhcp.tiwlan0.server]: [192.168.0.1]
[net.dns1]: [8.8.8.8]
[net.dns2]: [8.8.4.4]
[gsm.current.phone-type]: [1]
[gsm.operator.numeric]: [22210]
[gsm.operator.alpha]: [vodafone IT]
[gsm.operator.iso-country]: [it]
[gsm.operator.isroaming]: [false]
[gsm.version.baseband]: [13.29.55.13H_3.35.07.20]
[EXTERNAL_STORAGE_STATE]: [mounted]
[gsm.network.type]: [UMTS]
[gsm.data.network.type]: [UMTS]
[gsm.sim.change]: [false]
[gsm.cb.max.channel]: [15]

[...] now I am able to see the SSID from my tattoo too. While from the gui I 
cant 
do nothig but then click. If I click it says it is running and if I click to 
stop, 
it does not return any result. Of course, from the command line I can stop.

# ./tether stop 1
about to run: [/data/data/android.tether/bin/ifconfig tiwlan0 down]
about to run: [/data/data/android.tether/bin/iptables -D FORWARD -j wireless-
tether]
about to run: [/data/data/android.tether/bin/iptables -F wireless-tether]
about to run: [/data/data/android.tether/bin/iptables -X 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]
script result was []

Thanks in advantage for any tip you could provide.

Original issue reported on code.google.com by jokerulez on 2 Jun 2010 at 4:30

[GoogleCodeExporter]

Is there an app installed called "Superuser Permission"? Do you have 
"USB-debugging" 
(Settings -> Application -> Development) enabled which is mandatory for most 
versions 
of "Superuser Permission"?

This doesn't seem to be an app-related (wireless tether) issue.

Original comment by harald....@gmail.com on 3 Jun 2010 at 3:27

[GoogleCodeExporter]

Hi harald.mue, thanks for your answer.
I haven't any "Superuser Permission" app installed. I have su as required to 
root my 
phone. What about usb-debugging? Should usb-debugging be enabled even if I'm 
not 
connected with a usb cable to my PC?
Any further help will be appreciated.

Original comment by jokerulez on 4 Jun 2010 at 6:59

[GoogleCodeExporter]

Anyway, turning on usb-debugging does not affect in any way the result: "Unable 
to 
start tethering. Please try again".

Original comment by jokerulez on 4 Jun 2010 at 7:02

[GoogleCodeExporter]

USB-debugging is only required if that "Superuser Permission"-app is installed.

Try to do the following:
adb remount
adb shell
su (only if you are not root already)
cd /system/bin
cat sh > su
chmod 4755 su

What does this do: It remount the system-partition for read/write. Creates the 
su-
binary and sets permissions.

Original comment by harald....@gmail.com on 4 Jun 2010 at 8:56

[GoogleCodeExporter]

Of course I already did this to be root. Is there any chance that doing that 
again can 
solve something?

Original comment by jokerulez on 4 Jun 2010 at 10:17

[GoogleCodeExporter]

I don't know what you did and if you did it the right way. What I see and what 
I can 
say ... there is something wrong with your su-environment.

Original comment by harald....@gmail.com on 4 Jun 2010 at 10:25