[ROOT] Universal root method for all variants.
- Thread starter Ricky Divjakovski
- Start date
- Status
Doesn't the fact that the At&t S5 has a locked bootloader mean that you can't use Odin to flash a recovery?
Ah! That could be the case
If theres a custom recovery for your device yes!
LOL. this will root any ARM device with a working custom recovery, so i think ill keep the thread just the way it is.
From what I see, it seems that AT&T is not working?
all the updates are for all cariers but AT&T..
im working on devices with locked bootloaders..
This does not work with the Verizon variant since the philztouch recovery cannot be flashed due to the locked bootloader. The title of the topic should be modified.
your right in ways, only works for devices with unlocked bootloaders, working on a way around that but seems merely impossible without the abillity to ever chmod a file :/
Nothing prevents the use of the chmod command on s5, can you be more specific?
chmod 775 /sdcard/busybox : permission denied
/sdcard/busybox --help : permission denied
/sdcard/chmod 775 /sdcard/busybox : permission denied
cant do anything without the abillity to set permissions :/
at the moment the only root method I can hope for is using a factory system image, unpacking, rooting, repacking and flashing with odin...
other then that the only solution is looking for a bootloader unlock, and im unable to do that as I dont have the device and needs ALLOOOOT of testing
if you have any suggestions/advice feel free to let me know, its got me wrapped in a ball :/
Last edited:
/sdcard/ is not a normal file system, setting such permissions won't work. Place the giles on a normally mounted ext file system, like /data/local/tmp not one mounted using fuse
Repacking won't work due to signature validation during the flashing stage.
"only solution is looking for a bootloader unlock" What, how do you come to such a conclusion? It isn't a valid conclusion.
Please adjust your thread title, it is inaccurate and likely to cause confusion for those that don't know any better.
Am I missing something here? This is just SuperSu's update.zip with a couple minor additions, it isn't a root kit and roots nothings. the majority of the entire package is straight out of Chainfire's update.zip, which accomplishes the same thing. It certainly won't "root any ARM device", it will certainly install SuperSu on some of them with a custom recovery (but no it will not work on all, even with a custom recovery.
Code:
ui_print("******************************************");
ui_print(" Installing S5Tools");
ui_print("******************************************");
ui_print(" BROUGHT TO YOU BY RICKYS KITCHEN");
ui_print(" BY RICKY310711");
unmount("/system");
ui_print("Mounting System");
run_program("/sbin/mount", "-t", "auto", "/system");
ui_print("Executing checkpart");
package_extract_file("tmp/chechpartroot", "/tmp/chechpartroot.sh");
set_perm(0, 0, 0777, "/tmp/chechpartroot.sh");
run_program("/tmp/chechpartroot.sh");
ui_print("Extracting data");
package_extract_dir("system", "/system");
ui_print("Setting permissions");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 06755, "/system/xbin/daemonsu");
set_perm(0, 0, 06755, "/system/bin/.ext/.su");
run_program("/system/xbin/su", "--install");
ui_print("******************************************");
ui_print(" Successfully Installed");
ui_print("******************************************");
set_progress(1.0);
Code:
./system/app:
total 4456
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:27 .
drwxr-xr-x@ 7 jcase staff 238 Apr 16 21:30 ..
-rwxr-xr-x@ 1 jcase staff 2278361 Apr 4 04:04 Superuser.apk
./system/bin:
total 0
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:30 .
drwxr-xr-x@ 7 jcase staff 238 Apr 16 21:30 ..
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:27 .ext
./system/bin/.ext:
total 224
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:27 .
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:30 ..
-rwxr-xr-x@ 1 jcase staff 113036 Feb 14 18:34 .su
./system/etc:
total 8
drwxr-xr-x@ 5 jcase staff 170 Apr 13 20:27 .
drwxr-xr-x@ 7 jcase staff 238 Apr 16 21:30 ..
-rwxr-xr-x@ 1 jcase staff 0 Feb 14 18:34 .installed_su_daemon
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:30 init.d
-rwxr-xr-x@ 1 jcase staff 629 Feb 14 18:34 install-recovery.sh
./system/etc/init.d:
total 8
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:30 .
drwxr-xr-x@ 5 jcase staff 170 Apr 13 20:27 ..
-rwxr-xr-x@ 1 jcase staff 55 Feb 14 18:34 99SuperSUDaemon
./system/xbin:
total 448
drwxr-xr-x@ 4 jcase staff 136 Apr 13 20:27 .
drwxr-xr-x@ 7 jcase staff 238 Apr 16 21:30 ..
-rwxr-xr-x@ 1 jcase staff 113036 Feb 14 18:34 daemonsu
-rwxr-xr-x@ 1 jcase staff 113036 Feb 14 18:34 su
./tmp:
total 8
drwxr-xr-x@ 3 jcase staff 102 Apr 13 20:37 .
drwx------@ 6 jcase staff 204 Apr 16 21:30 ..
-rwxr-xr-x@ 1 jcase staff 264 Apr 13 20:39 checkpartroot- Status
Similar threads
- Poll
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
27hey guys, this is just a package made with my "Rickys Rom Kitchen", will root any android device with a working custom recovery!
Note: all i did was make this universal and make it a flashable zip.
So, you know the drill, your warranty is now viod, flash at your own risk blah blah.
How to root?
1. Flash philztouch recovery or any supported recovery for your device with odin - INSTRUCTIONS AND DOWNLOAD HERE
2. Make a nandroid backup from within philztouch recovery
3. Flash my universal S5 rootkit INSIDE PHILZTOUCH recovery - DOWNLOAD FROM HERE(PhilzTouch)
4. (OPTIONAL) install busybox from playstore and download my Samsung Tool app and backup EFS! - DOWNLOAD HERE
Thats all.
Credits - Chainfire (for SuperSu and binaries)9Since this update zip requires a custom recovery, and you need an unlocked device before you can install a custom recovery, it is misleading to advertise this as a way to root a device. It's also unnecessary since the update Chainfire created does the exact same thing.
The only thing I can find that you created is your "checkpartroot" script that doesn't serve any purpose.
Thread closed.52@ricky310711
May also want to look at /mnt/extSdCard directory (if you happen to have a microSD card you can format as exFAT).
This directory worked on the S4 for one kernel-based exploit (perf_event) where /data/local/tmp did not actually (details).
Not sure if anything changed with KitKat as far as that directory is concerned but worth a try.2
