• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Script] Replace KingoRoot with SuperSU

Hi there, do you have any ideas why I'm having troubles with ./step0.sh?

I have a Huawei mt7-L09 and I rooted with Kingoapp. Also since executing ./step0.sh I can't use Kingoapp to uninstall root. If I can't get SuperSU installed I don't want to stay rooted through Kingo Superuser...

Any help would be much appeciated.

Regards,
 

Attachments

  • Screenshot_2016-06-19-13-43-09[1].jpeg
    Screenshot_2016-06-19-13-43-09[1].jpeg
    505.3 KB · Views: 655
Welcome to our AndroidForums, @swr87 :).

Hopefully the good folks in here can assist you and that the script/utility will be able to work on your device.

Cheers!

edit: in looking at your screen shot, it looks like you might have typed-in the mount command string incorrectly (you typed "mount o- rw,remount,rw /system" and I'm pretty sure that should have been "mount -o remount,rw /system" but that even differs from what the scripts use), although I'm not sure you would even have to do that since the step0.sh script will (should) do that for you; have a peek/review of the README.TXT file that came with the .zip and see if that clarifies things for you; the other guys will chime-in with their thoughts, too, I'm sure :)
 
Last edited:
Welcome to our AndroidForums, @swr87 :).

Hopefully the good folks in here can assist you and that the script/utility will be able to work on your device.

Cheers!

edit: in looking at your screen shot, it looks like you might have typed-in the mount command string incorrectly (you typed "mount o- rw,remount,rw /system" and I'm pretty sure that should have been "mount -o remount,rw /system" but that even differs from what the scripts use), although I'm not sure you would even have to do that since the step0.sh script will (should) do that for you; have a peek/review of the README.TXT file that came with the .zip and see if that clarifies things for you; the other guys will chime-in with their thoughts, too, I'm sure :)
Thank you for the quick response. I only tried that mount command as I had tried running step0.sh several times before with same results. I have been doing a bit of reading and think that my system is read only which can't be changed unless I unlock the bootloader; thus the mount error. I did want to manual root my device initially by unlocking bootloader etc. but I was struggling to obtain the unlock code from Huawei. I made a Huawei account and followed the appropriate steps to get the code, but keep getting server busy error message when getting directed to the bootloader unlock page so I gave up and resorted to a oneclick method thinking I had options to remove the default superuser and install superSU. Hopefully I can find a soloution...

Cheers
 
ok so i currently have kingo root 3.1 installed on my LG Leon and it has the installer app and the superuser app which has no settings to disable the root permissions because if i uninstall KingoRoot the phone reboots thus closing the terminal window. Any tips?
 
hey iam using kingroot latest version(4.9.6) in my device Samsung grand duos 4.2.2
will this method works for me ,
to get super su
plz reply me ,i did all the thing but no success that why iam asking ,
sorry for the stupid question ,
plz to reply me .....
 
its is not all working for me

------------------------------------------------step0.sh-----------------------------------------------------------------------
kingotosupersu.v1.3a# sudo sh step0.sh
Mounting /system r/w...
mount: mount point /system does not exist
Copy SuperSU daemon...
cp: cannot create regular file '/system/xbin/daemonsu': No such file or directory
chmod: cannot access '/system/xbin/daemonsu': No such file or directory
Start SuperSU daemon...
........................................................................
If this finished without errors, uninstall KingRoot and install SuperSU.
step0.sh: 9: step0.sh: daemonsu: not found

------------------------------------------------------step1.sh------------------------------------------------------------------

kingotosupersu.v1.3a# sudo sh step1.sh
Restoring SuperSU binary...
cp: cannot create regular file '/system/xbin/su': No such file or directory
chmod: cannot access '/system/xbin/su': No such file or directory
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
step1.sh: 7: step1.sh: ./chattr.pie: Permission denied
step1.sh: 8: step1.sh: ./chattr.pie: Permission denied
rm: cannot remove '/system/xbin/ku.sud': No such file or directory
rm: cannot remove '/system/xbin/supolicy': No such file or directory
rm: cannot remove '/system/bin/rt.sh': No such file or directory
rm: cannot remove '/system/bin/install-recovery.sh': No such file or directory
rm: cannot remove '/system/bin/shipclean': No such file or directory
rm: cannot remove '/system/bin/start-ssh': No such file or directory
step1.sh: 15: step1.sh: ./chattr.pie: Permission denied
step1.sh: 16: step1.sh: ./chattr.pie: Permission denied
rm: cannot remove '/system/etc/install-recovery.sh': No such file or directory
rm: cannot remove '/system/etc/install-recovery.sh-ku.bak': No such file or directory
rm: cannot remove '/system/etc/install_recovery.sh': No such file or directory
rm: cannot remove '/system/usr/icu/icusuflag.conf': No such file or directory
step1.sh: 21: step1.sh: ./chattr.pie: Permission denied
rm: cannot remove '/system/kroot_*': No such file or directory
rm: cannot remove '/sdcard/kr-stock-conf': No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
 
Welcome to AF, Jon :).

The thread title states "Kingoroot" is the focus/topic of this thread and is meant to help folks replace the Kingoroot-specific files with the more mainstream and widespread "SuperSU" files.

I'm sure that the confusion between those two products was surely deliberate, but I don't know which was actually first (or even the "better" utility).
 
Don't know what to tell you other than to carefully read/review the thread (I've not use either of the King* apps/utils...just popped-in this thread a time or two).

It looks like the OP addresses some of your questions in post #5...
 
I had enough of Kingoroots battery saver lock screen :mad: 2 weeks after rooting my phone so I have tried your method.

I followed the instructions line by line, the last step.sh generated over 10 errors, which apparently was not good.


After reboot my LG D802 got bricked and I spent over 8 hours :mad: to recover it in normal flash mode and save all my data. It was a major pain. I needed root to do some routing/firewall mods on the phone but after this it's better not to use KingoRoot at the first place!

And the worse of the story is that after my normal reflash my phone remained unrooted with the wonderful Kingo Battery Saving lockscreen which is impossible to remove through the google playstore app manager externally or from the phone's applist (due to the fact that it is not in the list).

**** KingoRoot, if you here already for the same thing it is better to backup all your stuff from the phone and do a complete factory reset (before you get bricked) and then find other way to root your phone.
 
Hello,
First of all: thanks for your great modding work! There should be more people like you developing in their spare time and sharing with us.

Now my problem: I probably soft-bricked my Amazon Fire HD 8 (6th Gen) when I tried rooting it. Recovery is available, also fastboot, but I don't know how to use them to restore the system...
I used KingoRoot to gain root access and installed SuperSU. As it turned out, it was not the best decision to make. Now I'm stuck in a bootloop.

Is your tool made to fix my device?

Many thanks!

Patrick
 
Hi,

Thank you so much for this script!
I have successfully replaced Kingo SuperUser with SuperSU!

I will detail here how I did it on the S3(SHV-E210K) running 4.2.1. I got it working because of pure luck, however, the following steps may help people having a hard time replacing the default Kingo Root SuperUser. Just to clarify, the Kingo Root SuperUser I'm talking about has a blue shield and lines for an icon.

Don't forget to make a backup of your files before attempting the following steps! I cannot guarantee success, so do it at your own risk.

Steps

1. Download the zip provided by OP on the first page then extract the contents to your specified folder.

2. I used Terminal Emulator for Android to access the command line shell.

On your terminal type:

su

then hit enter. Grant root permission if it asks. Change directory to where you extracted the downloaded zip file. In my case, I downloaded the zip, extracted it on "sdcard" and renamed it "K2SU". Therefore, on the terminal I typed:

cd sdcard/K2SU

3. Execute step0.sh. On the terminal, type:

./step0.sh

If successful, proceed to step 4.
In my case, after executing the script, it said that I didn't have permission or something. Instead, I tried typing:

su ./step0.sh

Hit enter. Typing this did not return any errors (as in nothing at all), therefore, I assumed it was successful. I have to admit that I was confused during this step. I have spent hours making sense of it all, being an Android noob lol.

4. Hope you did not brick your device. Seriously. I did not have any backups for mine (I'm a noob) so I was nervous.

In this step, you may be tempted to open the Kingo SuperUser app to remove or uninstall the root. DO NOT DO THIS because obviously, you will remove the root.
What I did next was to leave the terminal running in the background, opened my file explorer (I use MiXplorer), went to the "root" folder, then to "system", and finally to "apps".
So, it's like this on your file explorer:

Root/system/app

then find the apk named:

com.kingouser.apk

or

KingoUser.apk

or whatever apk with a "kingo" in it. To be safe, move the apk to another folder (preferably, away from your root folder) so you have a backup of the apk before deleting it. Rename the apk whatever you want so it will not be detected by the system (this may be unnecessary though).

5. Download the supersu app from the Play Store then open it. If it asks to update the binary, update it then choose Normal. Pray for a miracle and be patient.

6. If step 5 was successful, congratulations! You have replaced Kingo SuperUser with SuperSU!

Negative result for 6:
In my case, success was not immediate. The app was stuck into "Installing update" for more than 10 minutes. I did not reboot my device for fear that I may have bricked it. What I did was to go to Task Manager and End the process. I went to the file manager and copied the backup KingoUser.apk back to root/system/app, then clicked the app to install it. After clicking the app, the installer said that it will replace an existing app. I clicked Install because yolo. After install, what I noticed was that com.kingouser.apk was now in root/data/app folder. This means that it is now a "user" app and not a "system" app, therefore I can now Uninstall it using the Application Manager in Settings. Long story short, I uninstalled com.kingouser.apk through Application manager, opened supersu app to update binary, and a miracle happened. The binary successfully updated!

End of my ordeals.

Thank you for reading and I hope this helps you. I would like to thank OP for his awesome script and guide and to Kingo Root for rooting my device in the first place.

Ciao
 
I had enough of Kingoroots battery saver lock screen :mad:
Well, Icedove. For about a week I have been looking for some answer how to get rid of your favourite Kingo Battery Saving lock-screen appearing in the system - have not found it anywhere but got some good hints for the direction where to dig up :) Testing my solution today, if no probs comes up within the next 2-3 days I will reveal it as tested here - it works ok on my Huawei Honor 6 all day long today :) Remind me after this period if I forget.
 
Last edited:
Well, Icedove. For about a week I have been looking for some answer how to get rid of your favourite Kingo Battery Saving lock-screen appearing in the system - have not found it anywhere but got some good hints for the direction where to dig up :) Testing my solution today, if no probs comes up within the next 2-3 days I will reveal it as tested here - it works ok on my Huawei Honor 6 all day long today :) Remind me after this period if I forget.
I had removed the lock screen from previous versions before. It requires APK modding skill. I will try to mod it and PM you, since posting modded APK is not allowed here i guess...
 
I had removed the lock screen from previous versions before. It requires APK modding skill. I will try to mod it and PM you, since posting modded APK is not allowed here i guess...
Thanks, it would be great! My solution is simplier: all you have to do is to turn off LockScreenActivity in SuperUser activities list via Activity menu in My Android Tools. Works ok on my phone for the second day today so I can open this solution to public, I think.
 
Thanks, it would be great! My solution is simplier: all you have to do is to turn off LockScreenActivity in SuperUser activities list via Activity menu in My Android Tools. Works ok on my phone for the second day today so I can open this solution to public, I think.
Thanks for the tip but i prefer removing it for more lightweight. no 3rd party app are required
 
Well, that's a new one. Text file busy says that daemonsu is currently running, and after the "If this finished without errors" line, I don't see you launched another script, so I'm not sure where that's coming from, it's not part of any of my scripts.

Let's step back. You currently have the KingUser app, plus the two other random related apps installed, right?. Do you also have SuperSU or any other superuser app installed? Did you try to install SuperSU after step0, before you uninstalled KingUser? It seems like two su's are fighting it out. Either way, we can nuke it all from orbit and just manually push SuperSU if things don't want to play nice.

hi I've read the whole thread but im still locked to kingo because of the DAEMONSU: text file busy error, i dont have supersu anymore, i tried killing the process but ps listed 4 of them and only allowed me to kill 1, but when I killed that one then my /system was no longer R/W, seems like I killed the process that is allowing terminal to hace su privs.

Help please.
 
Back
Top Bottom