[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] DeepPurple72:
I have the 903vl unlockable, locked bootloader, MM 6.01 with the 2016 security stuff....

( I dont think you can downgrade android when the bootloader is locked, to the factory test version mentioned )

messing around, i managed to use ADB to push the "su' binary from latest supersu.zip to /data/local/tmp like so:

I extracted the .zip to a folder, in terminal, changed into that folder and did this:

adb push *.* /data/local/tmp/

adb shell chmod 4755 /data/local/tmp/*.*

then do a "adb shell" command, then "/data/local/temp/su"

which resulted in a PIE code error....

doing some serious googling for an android su binary with pie support, i found this:

https://superuser.phh.me/ and downloaded the superuser.zip from there, extracted it, pushed it to /data/local/tmp & chmod'd the permissions.

in adb shell, I can execute it's "su-arm" binary without any errors ( but in android terminal, it gives permission denied )

in the shell, the root fs is read-only mounted. So I cant put stuff is /system/xbin.

if i type "mount" in the shell, it shows alot of mounted stuff similar to "mount" in linux.

Is it possible to use this "su-arm" to gain temp root via adb shell, and mount the filesystem RW ?

Then perhaps use this temp-root method to gain perm-root?

(I know I'm probably wasting my time, but yet, really would like to know)

(btw, i dont give a d@@m about KNOX / WARRANTY bits - just want ROOT!!!!)

any help would be great!

here's a copy and paste of the commands in terminal from linux:

--------------------------------------------------------------------------------------

main@main-Latitude-E6420:~/Downloads/su$ adb push *.* /data/local/tmp/

main@main-Latitude-E6420:~/Downloads/su$ adb shell chmod 4755 /data/local/tmp/*

main@main-Latitude-E6420:~/Downloads/su$ adb shell

shell@kltetfnvzw:/ $

shell@kltetfnvzw:/ $ cd /data/local/tmp

shell@kltetfnvzw:/data/local/tmp $ ls

chattr

chattr.pie

libsupol.so

su

su-arm

sukernel

supolicy

shell@kltetfnvzw:/data/local/tmp $ ./su

1|shell@kltetfnvzw:/data/local/tmp $ ./su-arm

255|shell@kltetfnvzw:/data/local/tmp $

255|shell@kltetfnvzw:/data/local/tmp $ exit

main@main-Latitude-E6420:~/Downloads/su$

( Looks like the supersu 'su' ran this time, but the 'su-arm' always works )

( after the 'su' it put 1| before shell, and 'su-arm' put a 255| - what does that mean???? )

I want to use VIPER-4-ANDROID on this S5 ( it kicks [MENTION=237736]SS[/MENTION] on my SG2 Skyrocket rooted CM 10.2 4.22 and Rooted Tablet SM-t550 rooted deodexed stock touchwiz 5.02 + XPOSED ) v4a link = https://xdaforums.com/sho....php?t=2191223

also, straight-talk disabled the wifi tether ( those f@@kers!!! ). I can only use usb-tether thru an app + client on computer to achieve internet. would like to be able to use root to force wifi-tethering hotspots to work too.

maybe someone more experienced could take this and run with it...

im thinking if we can somehow get the 'su' binary into the /system/xbin folder, then supersu might work and we can have root on the 903vl MM 6.01 security update 2016. With bootloader locked, cant install custom recoveries/roms but maybe we can at least have root.

I have the odin flashable 6.01 stock firmware also. using simg2img to convert the system.img.ext4 to system.img, its possible to modify the system.img file by mounting it in linux, and use HEIMDALL, ODIN, or someother method to flash just the system.img back to phone. Again, i dont care about warranty / knox..... just want that ROOT!

could the 'su' be added to the system.img ( and chmod permission to 4755 ? ) or does the kernel / se policies ****-block 'su' ?

*** UPDATE: Yep, kernel / SE LINUX policies / Security Patches are blocking 'su' and 'su-arm'. crap!