FORUMS
Remove All Ads from XDA

Replace KingoRoot with SuperSU manually without Terminal (2017)

1,296 posts
Thanks Meter: 388
 
By evildog1, Senior Member on 15th March 2017, 12:39 PM
Post Reply Email Thread
KingoRoot is annoying. No landscape support and battery lock screen cause my device to freeze. Support took 6 months to reply. I finally found a way to manually replace Replace KingoRoot with SuperSU without a script.

Before you get started, make sure you backup everything. I'm not responsible for any damages in your device.

Tip: You can use root without Kingouser but your device will be in high risk as any apps can grant permissions without your permission. I'd strongly recommended you to follow these steps for SuperSU replacement, or keep Kingouser

What you need?
- CPU-Z app
- X-plore file manager app or other root explorer apps
- SuperSU flashable zip
- SuperSU app from playstore

Let's get started

Step by step:
There is an easy way to switch to SuperSU but the change is low. Please go to page 2 or 3 for more infomation.
1. Delete/Uninstall Kingouser, but keep Kingoroot. DON'T reboot your device
3. Install SuperSU apk from flashable zip v2.79
4. Launch it, press "continue" and "normal" wait until the update is successful.
5. Reboot and uninstall Kingoroot

Thanks MarshisnotMellow for this trick

If automatic switching fails, do manual switching
-------------------

1. This is very IMPORTANT: Check your Kernel Architecture of your device using CPU-Z app. I bricked my device by placing wrong binaries for armv6 on a armv7 device by a mistake

In my example, my Kernel Architecture is armv7 so i'm gonna extract armv7 folder later


2. Download Recovery Flashable.zip of SuperSU: http://www.supersu.com/download

In the zip, there are 9 folders. I will list the folder below

META-INF = Signature and script for custom recovery
common = required files for SuperSU/rooting. init scripts are not needed

arm = arm11 / armv6. Devices like HTC Wildfire, Wildfire S, Galaxy Y etc
arm64 = armv8 / armv8l / arm 64-bit. Sony Xperia M5 etc.
armv7 = armv7l. For all popular devices, you know, Samsung S3 mini, HTC, Sony, LG, etc
mips = Unknown. Don't know which device is using mips
mips64 = Unknown. Don't know which device is using mips64
x64 = Unknown. Don't know which device is using x64
x86 = Any Intel CPU. Asus Zenfone, Bluestacks, Android emulator etc.

3. Open X-plore, open confuguraion and enable root access as Superuser + mount writable

4. Extract <Your architecture> and common folder in your device

5.
Navigate to extracted folder on left pane and navigate to /system on right pane



6. Now we gonna replace and delete some files in the ROM very carefully! Do the following:

Tip: Press and hold on the file and select permission to change the permission



Skip step 6.1 if you already have SuperSU app installed

6.1. Install SuperSU as system app
Android 4.4.x and below: Copy: /common/Superuser.apk => /system/app
Android 4.4.x and below: Change permission to 644 (-rw-rw-r--)

Android 5.0.x and above: Create a folder named "Superuser" or whatever
Android 5.0.x and above: Change permission to 755 (drwxrwxr-x)
Android 5.0.x and above: Copy: /common/Superuser.apk => /system/app/Superuser
Android 5.0.x and above: Change permission to 644 (-rw-rw-r--)

6.2. Replace: /common/install-recovery.sh => /system/etc
6.3. Delete: /system/etc/install_recovery.sh

6.4. Replace: /<Your architecture>/libsupol.so => /system/lib

6.5. Rename "su" to "daemonsu"

6.6. Replace: /<Your architecture>/daemonsu => /system/xbin
6.7. Replace: /<Your architecture>/supolicy => /system/xbin

6.8. Delete: /system/app/kingouser.apk and uninstall it from Settings -> App (if it was installed as user app)

After you replace any files, make sure the new file still has the same permissions as the old file. X-plore does this automatically, that's why X-plore is the best file manager. Root Browser doesn't, and you will lost root or get bootloop after reboot. But, you can re-root with KingoRoot and do it again.

There is no need to replace "su" binaries since they are write protected, but SuperSU can replace them once you update it in STEP 8


7. That's all. Reboot your device

8. SuperSU will appear on app drawer. Open it and it will ask you to update the binary. Press "continue" and "normal". The update should be successful.



9. Reboot your device one more time

Now you have a working SuperSU

Tested devices
https://docs.google.com/spreadsheets...it?usp=sharing

Most ARMv7 devices are tested and working. If you have a device with ARM64/v8 or x86, i need you to tell me the system files that Kingoroot have modified so i can find out which files to replace. PM me for more info
The Following 33 Users Say Thank You to evildog1 For This Useful Post: [ View ] Gift evildog1 Ad-Free
 
 
15th March 2017, 02:47 PM |#2  
Rahul98076's Avatar
Member
Flag thane
Thanks Meter: 1
 
More
Thanks Op for this thread.
I personally use super su but some devices make it hard to so I have to use king root(cough-lenovo-cough)
This is a good idea to do what you have told over flashing the zip as sometimes that can be complicated.
Can't wait to get home and try it out.
Will surely get back to you with device names
15th March 2017, 05:23 PM |#3  
evildog1's Avatar
OP Senior Member
Thanks Meter: 388
 
More
Quote:
Originally Posted by Rahul98076

Thanks Op for this thread.
I personally use super su but some devices make it hard to so I have to use king root(cough-lenovo-cough)
This is a good idea to do what you have told over flashing the zip as sometimes that can be complicated.
Can't wait to get home and try it out.
Will surely get back to you with device names

This thread is for Kingoroot with o, not Kingroot
Btw, replacing Kingroot with SuperSU failed. I have tried it.
15th March 2017, 05:52 PM |#4  
Rahul98076's Avatar
Member
Flag thane
Thanks Meter: 1
 
More
Quote:
Originally Posted by evildog1

This thread is for Kingoroot with o, not Kingroot
Btw, replacing Kingroot with SuperSU failed. I have tried it.

Typo😛
15th March 2017, 07:01 PM |#5  
sohamsen's Avatar
Senior Member
Flag Kolkata
Thanks Meter: 1,042
 
More
working in galaxy ace s5830i
Armv6 arch
running cm11

---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------

OK here is a working list!
ROM:CyanogenMod11 Arch:Armv6
1.Samsung Galaxy Ace-i(S5830i) Code Name=Cooperve
2.Samsung Galaxy Ace(S5830i) Code Name=Cooper
3.Samsung Galaxy Y(S5360) Code Name=Totoro
4. 1.Samsung Galaxy Mini Code Name=Tassave
The Following User Says Thank You to sohamsen For This Useful Post: [ View ] Gift sohamsen Ad-Free
16th March 2017, 07:12 AM |#6  
evildog1's Avatar
OP Senior Member
Thanks Meter: 388
 
More
Quote:
Originally Posted by sohamsen

working in galaxy ace s5830i
Armv6 arch
running cm11

---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------

OK here is a working list!
ROM:CyanogenMod11 Arch:Armv6
1.Samsung Galaxy Ace-i(S5830i) Code Name=Cooperve
2.Samsung Galaxy Ace(S5830i) Code Name=Cooper
3.Samsung Galaxy Y(S5360) Code Name=Totoro
4. 1.Samsung Galaxy Mini Code Name=Tassave

Err... are you using CM11 with Kingoroot?
CM11 is already pre-rooted.
16th March 2017, 07:24 AM |#7  
sohamsen's Avatar
Senior Member
Flag Kolkata
Thanks Meter: 1,042
 
More
Quote:
Originally Posted by evildog1

Err... are you using CM11 with Kingoroot?
CM11 is already pre-rooted.

i used kinguser for root management
tried this vulnerability
it works
16th March 2017, 08:33 AM |#8  
evildog1's Avatar
OP Senior Member
Thanks Meter: 388
 
More
Quote:
Originally Posted by sohamsen

i used kinguser for root management
tried this vulnerability
it works

Kingouser or Kinguser?
16th March 2017, 12:11 PM |#9  
Padly's Avatar
Junior Member
Thanks Meter: 2
 
More
Work perfectly with my experia e4 dual.

Im just write cat /proc/cpuinfo in terminal for check my kernel architecture. 😁

Sent from my E2115 using XDA Forums Pro.
16th March 2017, 03:15 PM |#10  
Senior Member
Flag Yangon, Myanmar
Thanks Meter: 163
 
More
My Kernel Architecture is armv8I. Which one should I select in zip file because there is no armv8I?
16th March 2017, 04:21 PM |#11  
aarick's Avatar
Senior Member
Thanks Meter: 48
 
More
Won't this work instead?
Install SuperSU (I used SuperSU Pro) from the play store and grant it superuser access. When prompted, install updated su binary with the normal mode. Once installed successfully, uninstall Kingoroot and Superuser app. Reboot.

That's what I did on an android 6.0 headunit I have and seems to work. But maybe there is a benefit of avoiding kingoroot completely?
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes