New 100% reliable "temp root" for Titanium Backup (won't stop working until reboot!)
Hi all,
I grew frustrated by the annoyance of losing root access randomly, when modified files on /system suddenly become inaccessible because of the S-ON lock.
But here's some good news: I came up with a way to get a 100% reliable "temp root" for Titanium Backup.
Advantages:
Drawbacks:
Tested with Titanium Backup only (for now).
Requirements:
Initial (one-time) setup:
After every reboot:
The advantage of this method is that /system is not modified, therefore the rooting will be totally stable and will persist until the next reboot
Q&A:
Will it work with other root apps?
This is a minimalistic approach which installs no busybox and does not touch /system, in order to be perfectly reliable. The drawback of this is that it will work only with root apps that are able to find "su" at /data/bin/su, and that don't need a busybox in $PATH. Fortunately, Titanium Backup fulfills both of these criteria. If you know other apps that do, please post about them.
Status:
Greetings go to #teamwin for the exploit, of course.
Have fun !
Hi all,
I grew frustrated by the annoyance of losing root access randomly, when modified files on /system suddenly become inaccessible because of the S-ON lock.
But here's some good news: I came up with a way to get a 100% reliable "temp root" for Titanium Backup.
Advantages:
- You will not lose root access until next reboot!
- 100% reliable, does not modify /system at all.
Drawbacks:
- Minimalistic approach with no BusyBox.
- Will only work with select root apps.
Tested with Titanium Backup only (for now).
Requirements:
- Original "out of the box" Sensation or EVO 3D (untested).
- Android SDK tools ("adb" command) on a computer.
- USB connection between computer and phone.
- Installed Superuser app from the Market.
Initial (one-time) setup:
- unzip better-temp-root.zip
- adb push fre3vo /data/local/tmp/
- adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
- adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
- adb push su /data/bin/
- adb push root.sh /data/bin/
- adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
- adb shell "/data/bin/root.sh"
After every reboot:
- adb shell "/data/bin/fre3vo"
- adb shell "/data/bin/root.sh"
The advantage of this method is that /system is not modified, therefore the rooting will be totally stable and will persist until the next reboot
Q&A:
Will it work with other root apps?
This is a minimalistic approach which installs no busybox and does not touch /system, in order to be perfectly reliable. The drawback of this is that it will work only with root apps that are able to find "su" at /data/bin/su, and that don't need a busybox in $PATH. Fortunately, Titanium Backup fulfills both of these criteria. If you know other apps that do, please post about them.
Status:
- Titanium Backup (free & pro): works
- Root Explorer: works
- MyBackup pro: works?
- SetCPU: FC
- Wireless tether: needs system modification
Greetings go to #teamwin for the exploit, of course.
Have fun !
Attachments
-
9.8 KB Views: 4,666
Last edited: