NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[natemcnutty]

Wirelessly posted (Opera/9.80 (Android; Opera Mini/5.1.22460/23.411; U; en) Presto/2.5.25 Version/10.54)

Originally Posted by [ACL

]

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?

[[ACL]]

Originally Posted by natemcnutty

Wirelessly posted (Opera/9.80 (Android; Opera Mini/5.1.22460/23.411; U; en) Presto/2.5.25 Version/10.54)



Should we remove it from initrd entirely or replace the link with the real su from rootfs?

it should be there at all. But im not sure why its being used. We need to double check the path in the init.rc .. the paths must match xdandroid.

/bin is reallly only for initrd not android.

[[ACL]]

Originally Posted by [ACL]

it should be there at all. But im not sure why its being used. We need to double check the path in the init.rc .. the paths must match xdandroid.

/bin is reallly only for initrd not android.

Yeah we can live without it on the init.rc. We have a full busybox on system/bin so we shouldnt lose any functionality. We need tests now.

just remove "/bin" from the path in sysinit.rc and you should be golden. rootfs has a hack to run su from outside busybox.

[Lmiller1708]

Originally Posted by coolsilver

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.

Ok. I was able to get Titanium backup working correctly with the superuser app.
Steps:
1. Go Here and get the newest Zip for Froyo.
2. Extract to you sdcard.
2.1. Install the included supersuer apk.
3. Mount system as rw: mount -o remount,rw /system
4. Remove the su in system/bin and system/xbin.
5. Copy the su included in the zip above to your system/bin folder.
6. chmod 4755 /system/bin/su
7. ln -s /system/bin/su /system/xbin/su
8. run TitaniumBackup and click on "Problem?" button to install BusyBox from App (Thanks m4f1050)

Run Titanium Backup and you should be prompted by the Superuser app to allow access for Titanium backup. You will also have to update the busybox.

This will work for now until we get full root access.

Originally Posted by [ACL]

Yeah we can live without it on the init.rc. We have a full busybox on system/bin so we shouldnt lose any functionality. We need tests now.

just remove "/bin" from the path in sysinit.rc and you should be golden. rootfs has a hack to run su from outside busybox.

Don't forget when you remove the /bin/su app it will be back there once you reboot your device.

Also I think we should still leave the /bin path in the sysinit.rc, because that's what the xdandroid uses and we do not want to go too far from them...

I'm still looking at not having to use superuser app... But I know the Vogue still uses it... I have not been able to find a su that works without it. I have tried the ones included in the rootfs and system/xbin with no luck.

[coolsilver]

Well that makes sense. I will try that. I didn't realize the initrd had it's own /bin setup.


Titanium backup is still not asking for root in the manner SuperUser app notices. I'll try later tonight. I can get Clocksync and MarketAccess apps to work fine before. I pretty much did all those steps above except the sysinit.rc change. After the sysinit.rc change I didn't notice any difference.

I'll restart and try if not well, I know I'm no expert.

[[ACL]]

Originally Posted by coolsilver

Well that makes sense. I will try that. I didn't realize the initrd had it's own /bin setup.

yeah.. it really shouldnt be there. rootfs on haret uses it to setup all this stuff for android, but since its in the initrd you cant make it go away so might as well use it. Other builds like sense and cyanogen dont use it so im thinking we should just remove it from the path for now and test.

Nate/lmiller: new recovery hopefully tonight. Backup and restore now work, only thing left is the advanced menu for fix permissions (fix userland perms), fix perms (for sys perms that lmiller wrote the script for). Not sure what else we would need but that's a good start right now. I guess if you need more you better learn how to use adb. I might just stub out the advanced features so we dont need to recompile when the scripts are done.

[Lmiller1708]

Originally Posted by [ACL]

yeah.. it really shouldnt be there. rootfs on haret uses it to setup all this stuff for android, but since its in the initrd you cant make it go away so might as well use it. Other builds like sense and cyanogen dont use it so im thinking we should just remove it from the path for now and test.

Nate/lmiller: new recovery hopefully tonight. Backup and restore now work, only thing left is the advanced menu for fix permissions (fix userland perms), fix perms (for sys perms that lmiller wrote the script for). Not sure what else we would need but that's a good start right now. I guess if you need more you better learn how to use adb. I might just stub out the advanced features so we dont need to recompile when the scripts are done.

Sounds good! I will wait to test the new recovery.
Before you commit the permissions stuff I have a updated one for you...

About replimenu if we can just do everything in the recovery that is good enough. No need for two menu systems that do virtually the same thing.

[MassStash]

i vote don't care if we "have"/get to use superuser app, so let's just stick with using the app then. Werd to recovery, no use for replimenu fer sure, RIP replimenu....

[vistazifta]

Originally Posted by MassStash

i vote don't care if we "have"/get to use superuser app, so let's just stick with using the app then. Werd to recovery, no use for replimenu fer sure, RIP replimenu....

lolol

[m4f1050]

Lmiller your instructions worked, but you need to do 2 things, 1 before the instructions (which is mount / as rw and remove /bin/su) and one after the instructions (do the BusyBox update from TitaniumBackup.)

Here is what I did:

1. adb shell
2. mount -o remount,rw /
3. rm /bin/su
4. (your instructions)
5. run TitaniumBackup and click on "Problem?" button to install BusyBox from App

Thanks!