7" Tablet Android 2.2 -could not acquire root access (last issue n.182)

[GoogleCodeExporter]

Hello Rodrigo ,

thank you very much for your project - I have a 7" Android 2.2 China tablet 
rooted whith 1_5_7 version of droidwall and have the same problem above : 
"Could not acquire root access".I have checked permission and UID-GID via TERM 
as root# in "/data/data/com.googlecode.droidwall/app_bin" of file droidwall.sh 
and changed various permission (chmod 6755/775/777) but it do not work when 
enable firewall via GUI (on better terminal : sh -xv droidwall.sh run ok $user 
uid == 10060:10060).
I have also tryed autostarts.apk to force Superuser.apk to promote droidwall as 
"root application" but unsucessfull , idem for any system help information 
whith "logcat" command : do you have suggestions ?

At this time I'am study your java (api.java)code to find a solution...

Regards
Giuseppe - Italy

Original issue reported on code.google.com by GZicchin...@webgateit.zzn.com on 16 Dec 2011 at 9:27

[GoogleCodeExporter]

For developer

I think that on various HW rooted systems this Java (api.java) function: 

'exec = Runtime.getruntime().exec ("su -c " +abspath); 

cannot run because 'SU' command is invoked as "(/system/bin/./su)" and not only 
"su"(Z4root mode); in this case Driodwall do not have possibility to check 
superuser permission and it's impossible promote via superuser.apk . I suggest 
to use,in this  case,a simple file (ie: root.txt) that 'root user' can write in 
<\data\data\com.googlecode.droidwall\app_bin\> for bypass this limitation and 
grant full Droidwall functionality.

regards Giuseppe

Original comment by GZicchin...@webgateit.zzn.com on 19 Dec 2011 at 10:39

[GoogleCodeExporter]

*** Warning: For Linux Experts only ->| rooted via Z4root| <- :

You can bypass manually : as Root# rename link under "/bin/su ->busybox" whith 
other name (ie: mv su   su_last) and reboot tablet , on login new SU# 
(/system/bin/./su)is
active and droidwall work now .

** Do not assume responsability for this internal modification : it's at your 
risk .

Giuseppe. Italy

Original comment by GZicchin...@webgateit.zzn.com on 19 Dec 2011 at 12:53

[GoogleCodeExporter]

Hi, were you able to run other root applications BEFORE the "fix"?
As far as I know, all root apps expect that you have a good "su" binary on the 
system PATH - so if you have a bad one at "/bin/su", root access will not work.

Original comment by rodrigo...@gmail.com on 21 Dec 2011 at 11:56