SOLVED: SafeRoot works for VRUCML1, and SuperSU binary update issue resolved.
Originally Posted by nook2hd
Followed all the steps of Saferoot, everything else seems ok except SuperSU failed to update su binary.
The weird thing is that steps after SuperSU update (disabling KNOX and installing busybox) seem ok, and while SuperSU's popup window asking for SU binary needs to be updated, I can see in the grayed out back showing ADB Shell as the only apps gained root access.
More detail on SuperSU binary update, I chose update su normal way (instead CWM/TWRP) and next popup will report "Installation failed. Please reboot and try again." I tried many reboots and results were all the same.
From Terminal emulator, su -v command shows su is at version 3.1.1 (that's the latest already). If I cancel binary update, SuperSU app will exit too. I tried to install superuser app and use it to update su binary as someone suggested, it will fail in gaining root access.
Any way to overcome this issue and gain root on this OTA 4.3? Please help.
Device Name: SCH-I535
Baseband Version: I535VRUCML1
Build Number: JSS15J.I535VRUCML1
Hardware Version: I535.10
SOLVED: SafeRoot works for VRUCML1, and SuperSU binary update issue resolved. Hope this will be helpful to others who has similar problems.
Background, I was rooted in JB 4.1.2 before took the 4.3 OTA (can't remember which method I used to root though.)
It's the weird thing that ADB Shell was granted root access as was shown in the SuperSU grayed out background prompted me to dig deeper. I noticed that SafeRoot script installs su binary into /system/xbin, so while phone connected to PC, run "adb shell" command, I see $ prompt, then run "/system/xbin/su", I see root's # prompt. So ADB Shell can indeed gain root access.
From there, run "which su' which tells me the default su being used is /system/bin/su (apparently not from SafeRoot). Removing /system/bin/su resolved the SuperSU binary update failure issue.
Since you'll need root access to remove files from /system, here are the steps I used to do that.
While still with root access in the above mentioned adb shell, do the following:
mount -o remount,rw /system
cp /system/bin/su out_of_system_folder_for_backup (optional)
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot. Voila! you have root working now.
Hope this will be helpful to others.
Now, I am wondering how to enable the feature to add new APN in 4.3. Adding the following 2 lines:
to build.prop file does not work anymore.