If we knew then we could possibly figure it out ..... Why do you think you have an idea to fix it , we are open to ideas
Sent from my SCH-I510 using Tapatalk
Looking at the ED2 update file META-INF/com/google/android/updater-script these lines will kill the suid for both su and the superuser.apk:
ui_print("Symlinks and permissions...");
set_perm_recursive(0, 0, 0755, 0644, "/system");
. . .
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
If that's what's killing it there are a few possibilities for allowing ED1 rooted devices to migrate to ED2:
If the package is downloaded to the phone and requires user action before the update is applied, we could just patch out those lines. Or can we put a patched version on the phone and trigger it manually?
EDIT: It looks like we might be able to patch out those lines in the update file in /cache and then allow the update.
EDIT 2: Since those lines might be needed to actually set some other permissions correctly, we could add:
set_perm(0, 0, 6755, "/system/xbin/su");
set_perm(0, 0, 6755, "/system/xbin/Superuser.apk");
Failing that can we get a version of su that does not reside in /system to work? I've played around with it for a few minutes and cannot get a copy elsewhere to work. I'm not very familiar with the Android security model, but I'm assuming that's what I'm running into problems with here.