I managed to root my Verizon Samsung Galaxy Note 10.1 tablet with Kingroot, but I'd like to remove it and switch to using SuperSU (because of KingRoot's aggressive practices and somewhat shady reputation). Even after uninstalling it and deleting everything labelled kingroot or superuser in /system, I still get Binary Occupied from the SuperSU app.

I believe there is a hidden process somewhere monitoring attempts to delete it and replacing the binary. For example, in system/usr there is a directory called iku (kinguser?) which replaces itself immediately after being deleted. Similarly, in system/xbin there is ku.sud and start_kusud.sh, which I can delete but instantly reappear.

This may be a quirk of the Samsung system, or some kind of hidden or inaccessible process. I've followed numerous online tutorials, and tried to run the Replace_Kingroot_With_SuperSU.zip method, but to no avail. Anybody know of a workaround?

Edit: here is part of the stdout form a script I ran. Note where it says operation not permitted:

rm failed for /system/xbin/ku.sud, Operation not permitted
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.kinguser, Directory not empty
rm failed for /data/data/com.kingroot.master, No such file or directory
rm failed for /system/bin/.usr/.ku, Operation not permitted
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/ddexe, Operation not permitted
  • you may need busybox for files and folder that persist to get romoved. also rm alone can't delete a folder that isn't empty – esQmo_ Nov 18 '18 at 13:38
  • Do you have stock/custom ROM for your device? Is unlocking bootloader possible for your device? – Irfan Latif Nov 18 '18 at 13:55
  • I don't think so, it's a pretty tough device to root. – Josh Friedlander Nov 18 '18 at 18:16
  • 1
    I believe it is showing operation not permitted because of immutable bit set on those files (protects the files from modification and deletion). You can remove that immutable bit but it requires busybox binary. The command is busybox chattr -i FILE_PATH. You can also try logcat command to see if anything shows up when you successfully delete those files (just to know what might be reinstalling them). // Also, you need to do rm -rf, not just rm if the target is in a directory and you're not running the command within that directory. – Firelord Nov 19 '18 at 16:10

You did it wrong I guess. Despite all the tutorials you found online, I wonder how you missed the right one : There's a "safe" uninstall feature within Kingoroot app. This removes completely the app and the binaries from your device.

  • Open the app
  • Click three dots upper right, find settings menu.
  • Click "Remove Root".

Your device will be rebooted and root should be removed.

  • Thanks. This does completely remove root, however this way I'm unable to replace it with the SuperSU binary. Is there any way to insert the superuser binary before removing root, so I can still have root access after removing Kingroot? – Josh Friedlander Nov 18 '18 at 10:39
  • @JoshFriedlander which model number is your device – esQmo_ Nov 18 '18 at 11:04
  • SCH-I925 Samsung Galaxy Note 10.1 (Verizon 4G LTE), Android 4.1.2 – Josh Friedlander Nov 18 '18 at 11:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.