• 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

Sorry for the slow reply, holiday weekend. Are you using adb's shell or a terminal app? If a terminal app, which one? Not that it should matter, but are you on a 7040T or 7040N? Can you type this command into terminal and paste / screenshot the results?

Code: 
ls -la
 
ITZMERY4N said:
I tried using different terminal apps and I'm on 7040N
Click to expand...

I added some basic status text to the scripts, grab the latest version and let's see what it spits out.

bakageta said:
Version 1.3
Click to expand...

If all goes well, you should see something like this after running the scripts.

step0.sh
Code: 
Mounting /system r/w...
Copy SuperSU daemon...
Start SuperSU daemon...
........................................................................
If this finished without errors, uninstall KingRoot and install SuperSU.

step1.sh
Code: 
Restoring SuperSU binary...
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.

If you get anything different, take a screenshot of it and post it, or copy/paste the exact text, and I'll see what went wrong.
 
this is what happened after step0.sh
 

Attachments

  • Screenshot_2015-05-25-18-40-38.png
    Screenshot_2015-05-25-18-40-38.png
    84.2 KB · Views: 622
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.
 
Was SuperSU installed when you tried to run step0? That'd probably cause those errors. If you've uninstalled SuperSU, you should be set to reboot and start fresh, with no daemonsu loaded. From there you should be able to just follow the steps, step0, use KingUser to revoke root, uninstall the other two king apps, install SuperSU from the play store, step1, and then run SuperSU - assuming no errors. If you get errors, screw it, we'll just do it manually and kill them both... :P Just leave a rooted terminal up.
 
Have you rebooted since then? If not, the daemon was probably still loaded. Other than daemonsu already running, the first script didn't throw errors, so the rest should work fine. If rebooting still throws a daemonsu error in step0, we'll just manually kill the existing one and replace it with ours, and be on our way.
 
Well apperintly super su is installed as a system applies and won't delete. It only has update and when I do it says uninstall then goes back to update
 
Ignore that, typing a new answer... :p

(edit)
That should be less of a problem then. Is system still writeable? We're going to skip step0, since that's just there to make system writeable and let SuperSU's daemon stay running. If you've rebooted or aren't sure if system is writeable, get a root shell and just type:
Code: 
mount -w -o remount /system

Keep the terminal open, and pretend like you just finished step0. Open KingUser, go to settings, and uncheck options then revoke root privs. Ignore SuperSU for now, go back to the terminal, and run step1. If it's mostly successful, open SuperSU and see if it can update now. If it can't, try running step0 one last time, then trying SuperSU. If that still fails, we'll install it manually.

If you're curious about what's going on and why this is a pain for you, it's because KingRoot doesn't like SuperSU and is fighting it. This is why we normally wouldn't install SuperSU until after KingRoot is gone, but it's not the end of the world, just something the script doesn't account for. As long as that root shell is open, you could completely remove SuperSU, KingRoot, and all su binaries and still get root back fairly easily - I goofed when experimenting and did this.
 
Last edited:
This is what happened
 

Attachments

  • Screenshot_2015-05-25-20-40-36.png
    Screenshot_2015-05-25-20-40-36.png
    154.1 KB · Views: 548
  • Screenshot_2015-05-25-20-41-39.png
    Screenshot_2015-05-25-20-41-39.png
    70.4 KB · Views: 476
Step1 looks good, a few errors happen because I was overzealous with what it removes. Annoying that SuperSU doesn't want to update, but no matter. Run manualsucopy.sh, and check SuperSU again.
 
Check the filesize on su, let's see if it's the right one.
Code: 
ll /system/xbin/su
It should be 75364 bytes. If so, great, try SuperSU. If not, guess we'll have to kill it and replace it.
 
I rebooted but it says superuser has not biary installed and terminal won't load any commands. But super user asks to grant permissions
 
I just want to thanks to bakageta for the script (Kingo.to.SuperSU.v1.2) this vesion works great on my 7040N rooted w/www.kingroot.net I have try it a few times already, thru my computer and terminal emulator w/no problems. thanks once again for you good work.:)
 
chanoc said:
I just want to thanks to bakageta for the script (Kingo.to.SuperSU.v1.2) this vesion works great on my 7040N rooted w/www.kingroot.net I have try it a few times already, thru my computer and terminal emulator w/no problems. thanks once again for you good work.:)
Click to expand...
How exactly did you do it. It isn't working for me and a have the same phone.
 
You must log in or register to reply here.
Back
Top Bottom