Thread: NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery
View Single Post
  #1751 (permalink)  
Old 03-15-2011, 12:59 AM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter 		 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Wirelessly posted (Opera/9.80 (Android; Opera Mini/5.1.22460/23.411; U; en) Presto/2.5.25 Version/10.54)

Quote:
Originally Posted by [ACL
]
Quote:
Originally Posted by coolsilver View Post
I have installed SU binary via ADB to /system/xbin. Installed SuperUser App

I can't update BusyBox via Titanium Backup or the BusyBox installer.

Busybox installer app complains about not being able to remount rw for /system even if it is rw via adb.

Titanium just fails never calls up Superuser app, Same with Busybox.

I have a feeling it is looking for the /etc/fstab for mount and unmount as well as some back end permission issues with busybox.

Mainly the "Must be suid on order to work properly" message.

I am thinking whatever user android is running as needs to belong to the correct root group.

Whoami under phone shows unknown id 10049. I am tracking down to see how to set it correctly.


Also looks as if /system/xbin has everything as user root and userid as 2000 except busybox which is root

Android UIDs and GIDs - Android Wiki

This shows userid is adb/shell user id. Copying su over sets permissions for root root.
notin to do with fstab.. actually you are way off.

Issue is on our end. Our initrd includes /bin/su which doesnt give anyone any rights. So we will need to remove the link on our next build. Or remove /bin from the PATH variable.

So if you want to test this out. Mount / as rw and remove /bin/su. Then when you type su, the other version in /system/bin will run.

also make sure su has permissions 4755
Should we remove it from initrd entirely or replace the link with the real su from rootfs?
__________________
Reply With Quote