yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] torsitch:
Thank you for the great tutorial and careful attention to details!

As others have noted, the new SuperSU 2.82 did not work for me, and it led to the "SU is already occupied" or something to that effect. That time I also had installed root directly from the PC version of KingoRoot and what I noticed was that KingoUser did not exist -> it was Superuser and KingoLink.

You will definitely have the best luck with SuperSU 2.79 stable. I installed SuperSU manually in 6.1, though the time before I installed it in Google Play as it was the newer 2.82. I think it's critical to root with KingoRoot's APK and *not* the PC version, though that's just my suspicion.

Do note that I deleted the KingoUser app under /system/app. THEN uninstalled KingoRoot (user apk) from App Manager. The writing in that step is slightly misleading because it mentions "if" KingoUser (in context) is a user apk you have to uninstall it that way instead of through /system/app. You in fact have to delete both the system and the user app I believe.

Thanks again for your great work! It works on an extremely obscure AMLogic Nextbook 7 NX700QC16G (board nxm7100lvd_wm). There's no support on the lone support forum freaktab.com for this particular model, and the other Su options there haven't worked for me. Hopefully this post will get picked up by the google crawlers. Cheers :)
[Android Software/Hacking General [Developers Only]] WaltA:
I would rather switch to SuperSU, but when I tried that, I permanently lost root (re-running Kingoroot to attempt to regain root, results in Kingoroot now hanging at 90%).

So, I am a bit "gun shy" now.
[Android Software/Hacking General [Developers Only]] evildog1:
It's normal that it hangs at 90% for a while

Try reinstall Kingoroot and make sure your internet connection is fast. It is required to have internet connenction to download additional data
[Android Software/Hacking General [Developers Only]] mribraqdbra:
Awesome! great job thanks you :)
[Android Software/Hacking General [Developers Only]] Ponozka:
works for me - using SuperSU-v2.79 on smartwatch DM98 - thanks a lot!
[Android Software/Hacking General [Developers Only]] viperx888:
Perfect, this worked flawlessly! Now running SuperSU on my android headunit, Eonon GA2154 (Rk3188, MTCD-KLD, 5.1.1)
[Android Software/Hacking General [Developers Only]] snowleopardmike:
want to try this process on an asus zenfone go arm7. is this a permanent root? if i do factory reset, will i lose root?

i tried this today using the easy method first. my fone is 5.1.1 asus zb500kg

kingoroot installed just fine, however, after i was not able to update supersu 2.79. i tried to install supersu from kingoroot again, but kingo is no longer responding.

i rebooted after removing kingo, then tried to install again, but kingo doesn't want to work anymore, just a blank screen and message saying that it's not responding. some apps detect that my fone has root, but i can't open any root explorer software so i can just copy the supersu as mentioned on the longer step.

i just don't know what to do next. may i'll try to root using kingroot this time.
[Android Software/Hacking General [Developers Only]] forcedv:
Want to try this because I had no choice but to root the ZTE Spro2 using Kingoroot.

Problem is, I can't find Kingouser.

Where is it located, so i can delete it?
[Android Software/Hacking General [Developers Only]] snowleopardmike:
i managed to install supersu, but by using supersume.

do i need to update to the supersu latest version? the installed supersu is v2.46
[Android Software/Hacking General [Developers Only]] evildog1:
yes you need to update it
[Android Software/Hacking General [Developers Only]] evildog1:
It sounds like some of binaries in your system is corrupted. You need to reflash firmware. I had this problem 2 times and flashing firmware is only the solution.

But you can't switch to SuperSU if you rooted with Kingroot. They tried hard to stop us from switching to SuperSU

Uninstall Kingouser from Settings -> Apps
[Android Software/Hacking General [Developers Only]] Braaainz:
I was using an LG G3 running stock rooted. I lost root thru a stupid mistake, only way I could find to regain root was using kingoroot.

I flashed an older TWRP, then restored an older full NANDROID (had boot, EFS, etc) that had root. I got a message that it couldn't find 'firmware's, but the restore continued. Everything seemed okay.

I then went back into TWRP and flashed a new ROM that had Magisk. Everything seems great.

My question is, could Kingoroot have left anything behind? Like creating a new partition to hide anything?
[Android Software/Hacking General [Developers Only]] Mitch.sc:
I've had no luck with the methods listed in this thread, unfortunately. Binaries were occupied on 2.82, and simply no success with 2.79

This link did work: but it is SU 2.4

I have not tried updating it yet.
[Android Software/Hacking General [Developers Only]] Bushido1992:
another Methode that workd for me is (phone without twrp, rootet via kingoroot) install magisk and flash / install root over boot img. then after reboot DON'T allow kingoroot superuser permissions!! or kingoroot will remove the magisk su
[Android Software/Hacking General [Developers Only]] evildog1:
So you flashed it using FlashFire right?
[Android Software/Hacking General [Developers Only]] evildog1:
I have no idea. It shouldn't hide anything. Also creating a new partition can cause device brick.

Can you try root with kingoroot again and do manual steps to switch to SuperSU 2.79?

If it does not help, then you need to reflash your firmware. Reflash the firmware solves most superuser switching issues
[Android Software/Hacking General [Developers Only]] Bushido1992:
No, i root my Phone with Kingoroot first. After Root i installed Magisk Manager and he ask me to Patch the Boot image file to work with Magisk Root. After reboot Magisk SuperUser is active^^
[Android Software/Hacking General [Developers Only]] evildog1:
Didn't know what. I will try it out
[Android Software/Hacking General [Developers Only]] Mitch.sc:
I updated Binaries, checked info, now running 2.82 so looks like all is good. Everything is working nicely, Xposed included, so there's no incentive to mess with it.

Thanks for the help all the same.
[Android Software/Hacking General [Developers Only]] io2345:
Works on Lenovo Yoga B8000

Works on Lenovo Yoga B8000 (ArmV7). I didn't do 6.3, just replaced the existing file.
[Android Software/Hacking General [Developers Only]] triadwarfare:
Context here please? Where? Following 6.4, I'm currently at System\lib

When I searched for "su", I can find them on system\xbin and system\bin

Where should I be renaming it? and doesn't it 'remove' the su from the system? I'm concerned about bootloops occurring if I follow disjointed instructions blindly.

Also another thing,

I wish I could use X-Plore, but the device that I'm trying to root doesn't even have a Play store, and the reason why I'm trying to root it is to insert the play store there.

The app isn't available in APKmirror; Checking for other sources might cause me to inject malware on the device. I resorted to using ES File Explorer as I'm most familiar with this application (and other file explorers in APKMirror seems to be not working in the tablet)... probably except converting the 644 permissions to what I can understand.

Don't worry, I'm aware of the concepts. However, I checked what permission matches what and as per this link, 644 is supposed to be rw-r--r--; But on 6.1, it says "Change permission to 644 (-rw-rw-r--)". I will have to follow my gut and use the -rw-rw-r-- despite other sources telling me that it's supposed to be -rw-r--r--.

I'm currently trying to root the Leapfrog Epic (v2). As of right now, I'm checking if 2.82 will work or I will have to resort to downgrading to 2.79 since I only read the comments pretty late in the middle, so I will have to use whatever I have installed right now.
[Android Software/Hacking General [Developers Only]] evildog1:
On the directory where you extracted files, rename su to daemonsu and copy it to /system/xbin

Use SuperSU 2.79 for installing binaries because 2.82 no longer have ability to force install binaries, getting SU occupied error instead. After that, update 2.82 sr5 beta to avoid "Android is starting" loop.

You can download X-plore from apkpure.com instead, 100% clean. It have many apps than APKmirror
[Android Software/Hacking General [Developers Only]] czarphanguye:
Followed this guide to convert Kingoroot to SuperSU on a Leapfrog Epic. Worked as expected. Thanks.

Used Recovery V2.79 Flashable.zip MD5:f4ecbf5814215bf569ff3324fc1c91f5
[Android Software/Hacking General [Developers Only]] jdapp:
So on asus PadFone 4.3 used kingo root and then gave titanium backup root. Added supersu + pro and removed kingo and super user with titanium. I appear to still have root but the supersu says SU binary occupied when I start it. When I try to make it a system app it either thinks for a long time or it thinks and then closes out with the app disappearing and needing to be reinstalled

It is supersu 2.82, where do I find 2.79? Do I need to use that one? Anything else I am doing wrong?
[Android Software/Hacking General [Developers Only]] masterx1234:
I just wanna chime in, this method actually failed for me for some weird reason, However, I uninstalled SuperUser and manually installed the APK provided here and chose "expert" mode and it let me update the binaries and i reboot my phone and viola! SuperSU has officially replaced Kingo superuser. I am using a LG device and I hear these are a little iffy when it comes to this stuff, Im still getting used to my new tablet since I always had a samsung devices.
[Android Software/Hacking General [Developers Only]] nikiDUA:
1 try and success..on my OPPO A51w. Thank you. ?
[Android Software/Hacking General [Developers Only]] jabu:
I had the binary occupied error as well. I went to settings and selected reinstall to clean it up. Then reinstalled SuperSu from Play store and it worked.

So my method on Android 5.0 was:

1. Root with Kingoroot apk

2. Install SuperSu from Play store

3. Uninstall Kingoroot

4. In SuperSu settings, click reinstall

5. Reinstall SuperSu from Play store

6. Let SuperSu update the binary
[Android Software/Hacking General [Developers Only]] madman67:
Can my Samsung j3 be rooted
[Android Software/Hacking General [Developers Only]] mmortal03:
I followed the above process but have started running into an issue on every reboot where "Android is starting", and it takes 10 minutes optimizing *all the apps* every single time. I read somewhere that it might be an issue with Android 5.1 and/or Motorola Moto phones and SuperSU (possibly versions greater than 2.79 -- but I also haven't had the chance to test that by downgrading to SuperSU 2.79 yet as "Recovery V2.79 Flashable.zip", actually, all apks and zip files seem to be down right now on the SuperSU website.).

So, I decided to just try removing SuperSU, to reverse the above process and go back to Kingo's SuperUser. To do this, I uninstalled SuperSU, then connected the phone to a computer with USB to re-root it with KingoRoot (which put SuperUser back on the phone), and on reboot I'm back to having Kingo's SuperUser -- however, removing SuperSU didn't fix the issue with optimizing all the apps every single time. :(

I also read somewhere that only rebooting with it not plugged in might work, but that also doesn't solve it -- it still does it even when not plugged in.

I found the following app that might help, but I'd rather not try something that could cause a boot loop unless it's a last resort: https://play.google.com/store/apps/details?id=in.co.giis.optimisingappfixer

Any ideas on what could be causing this and how to fix it?
[Android Software/Hacking General [Developers Only]] Casper Young:
Which J3?

Can you be a little more specific? J3 (2016 or 7) The J3 Achieve, Luna, Eclipse, J3 V, Emerge or Luna Pro... And I'll just bet the answer is yes.
[Android Software/Hacking General [Developers Only]] :
A few posts removed.

We don't discuss warez and how to get paid apps for free, on xda. Ever.

No more please. This is a site created for developers, and talking about how to steal from them is not at all OK. :good:

Thanks,

Darth

Senior Moderator
[Android Software/Hacking General [Developers Only]] :
Cleaned again.

Please don't sidetrack the thread with other matters. And please contact moderators privately if you have an issue with an action of theirs.

Thanks!

Back on topic please. :good:
[Android Software/Hacking General [Developers Only]] AbdulMajid11:
Replace kingroot with supersu

The best and most easy way to replace kingroot with supersu in android in mentioned in the link given below;

Replace kingroot with supersu

Each step is mentioned with related screenshots.
[Android Software/Hacking General [Developers Only]] bardell3600:
Good Download link

https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip
[Android Software/Hacking General [Developers Only]] evildog1:
Hi

I'm very sorry for late reply. Long time no see this thread

I had the same issue. That because you are using SuperSU 2.82 which have this issue. Upgrade to 2.82 r5 or downgrade to 2.79

Hope it helps
[Android Software/Hacking General [Developers Only]] evildog1:
Thread updated with more infomation

Use 2.79 which have ability to update/replace binaries, 2.82 doesn't (Occupied error) and it have "Android is starting" bug

This method still working with the latest version of Kingoroot
[Android Software/Hacking General [Developers Only]] HemanthJabalpuri:
Any idea to remove KingRoot new versions?
[Android Software/Hacking General [Developers Only]] Casper Young:
Occupied Binaries

[QOUTE: Use 2.79 which have ability to update/replace binaries, 2.82 doesn't (Occupied error). QOUTE]

As far as I know, usually binaries are occupied whenever something like kingoroot is still in the system. That's what is "Occupying" the binaries. I've never had a problem with SuperSu 2.82. I replace the Kingoroot slightly different than described here. Sometimes I need to use ES App Manager to freeze then I remove one part going through systems to apps (all runnig). ES File Explorer gets Root access and I use it to dig the rest of Kingoroot out of the system settings so I can install SuperSu as a system setting. But I've done this about a hundred times.
[Android Software/Hacking General [Developers Only]] evildog1:
I don't know unfortunately

That sounds more complicated. As I said, 2.79 had the ability to try hard like forcing to install with its binaries even some other binaries are installed that 2.82 no longer have. After Install 2.79, you can upgrade to 2.82 just fine.

If you can do this all the time, maybe try Kingroot which does hard locked all its binaries XD
[Android Software/Hacking General [Developers Only]] Aalesund:
It's ture. If you try SuperSu 2.82 you got an error "SU binary occupied" but you can fix it doing this trick: Go to SuperSU -> Settings -> Reinstall the app from store. Then open again SuperSU and update SU binary normaly. That's all.

But if you want all step without any errors just use version 2.78 -> https://androidfilehost.com/?fid=24686681827314977

2.78 works great and then you can update to 2.82 from Google Store without any errors!

========================================================

But if you have Android 5+ and you have root via KingoRoot or KingRoot just do this:

1. Install MagiskManager.apk

2. Give root privileges to MagiskManager

3. Install latest Magisk via "Direct Install" (will flash your boot partition) or manually via Modify the boot.img (then flash "patched_boot.img" in SPFlash Tool for MTK or Flash boot partition in TWRP or another)

4. Once you got a message that flash has been successful DO NOT restart the phone/tablet

5. Open KingoRoot/KIngRoot and go to Settings -> Unroot (unroot the device and uninstall KingoRoot/KingRoot)

6. Restart the device and you will have root via Magisk!

Tested and works on Android 5+! Magisk uses boot partition to install SU and you just need to give root privileges to MagiskManager.

This method DO NOT works on Android 4.2. even with latest Magisk that supports Android 4.2 and 4.4!

If you have Android 4.2 just root it with KingoRoot and then use SuperSU 2.78 and the tutorial from the first post!
[Android Software/Hacking General [Developers Only]] AndroPhobia:
Excuse sir!

So you say that you can install Magisk without a custom recovery?

Just install Magisk Manager and tap on install, delete Kingroot and reboot and done?

Please answer me I'm so tired of trying to root

My device:

M4 SS4452

5.1.1 Lollipop

armv7
[Android Software/Hacking General [Developers Only]] Aalesund:
Yes.

Install Latest Magisk Manager, open Magisk Manager, authorize root privileges to MagiskManager via KingRoot, Press on Install, Select Direct Install.

Once Boot partition has been successfully flashed press Close.

Go to KingRoot -> UNroot

Restart the phone and check Magisk Manager
[Android Software/Hacking General [Developers Only]] evildog1:
[MENTION=5957794]Aalesund[/MENTION]

I got it now, thanks for sharing your tricks

About Magisk, wow that's amazing! good find hehe!
[Android Software/Hacking General [Developers Only]] timmytimtimbuktu:
Thanks to the OP. I've been a long time user of Kingo. Haven't tried any alternatives ever since I've found out about it. I'd love to give it a go.
[Android Software/Hacking General [Developers Only]] HemanthJabalpuri:
[MENTION=4623971]evildog1[/MENTION]

Can you please help me at https://xdaforums.com/android/software/2019-replace-kingroot-v5-x-supersu-t3904880 I didn't tested kingo root but added script ..

is Android is updating bug is for all devices?

Please make a note in your post that device bootloader need to unlocked if locked...

and latest canary build of magisk can work in 4.4 or 18.1 with terminal installation will also work...
[Android Software/Hacking General [Developers Only]] Casper Young:
It does somewhat. The process at the beginning of this thread slightly worked for me but not completely, so I improvised a bit.
[Android Software/Hacking General [Developers Only]] Fusseldieb:
Confirmed working with "Kingo ROOT" 1.5.8

BUT there's a small caveat: You must first install SuperSU v2.79 and only then the latest SuperSU available.

Worked as following here:

- Let Kingo ROOT install root on the device as usual (In my case it's a DJI P4P+ Crystalsky)

- After successful rooting, delete the SuperUser application which Kingo has installed on your device.

EDIT: - Use "Titanium Backup" to delete the App, if you can't via the launcher.

- Do NOT reboot now, important! (If you did, you must start all over again).

- Install SuperSU v2.79. In my case I installed it over adb with

adb install <apk file location>

.

- Open SuperSU on your device, choose to update the binary and then wait until it succeeds (or fails). In my case it says it failed, but it shouldn't matter, because it likely hasn't.

- Reboot your device and SuperSU should then work normally. You can confirm this if you open SuperSU and no popup shows up, just the normal Log screen. Congratulations!

- Now you can install the latest SuperSU (I did it with

adb install -r <apk file location>

. The "-r" is to replace the existing App).

- Open it up, let it update its binary, it will now succeed and then reboot.

- Hoorayy!

Thanks for the tip [MENTION=4623971]evildog1[/MENTION]
[Android Software/Hacking General [Developers Only]] jerryspring:
great guide. works flawless
[Android Software/Hacking General [Developers Only]] jerryspring:
for some odd reason kingo superuser didnt delete. i cant even delete it with settings. any advice?
[Android Software/Hacking General [Developers Only]] Fusseldieb:
Oh sorry, it might be a system App. Install Titanium Backup [root] and delete the SuperUser App with it. Then proceed as usual.

I don't remember if I had to do this, but you can try it. Please report back if it worked (or not). You might get some "force closes" on the App by removing it via Titanium Backup, and if you did, just ignore.

I'll update the guide above. Thanks for letting me know!
[Android Software/Hacking General [Developers Only]] jerryspring:
I rooted five Kindle fires this exact same way and this is the only one where I could not delete the kingoroot superuser
[Android Software/Hacking General [Developers Only]] Casper Young:
There are two parts to kingoroot that must be removed. One is found in the app section and can be easily removed. The second one is in the system and if you do not remove this one it replaces the app again. Follow the post at the beginning to see how to use the ES File Eplorer to get into the system and remove the Kingoroot completely from the bin section of the system. The way I did it was to stop the process at number 3 (of the first page of this post) where you enable write capability to ES File Explorer. From there I just went into the system data and entered "Kingo" in the search bar. It'll pull it right up and you can delete it from there. You should already have the "normal" Supersu app from Google play installed beforehand. Once you remove both parts of Kingoroot you can install Supersu Pro (Supersu 2.79 or 2.80).
[Android Software/Hacking General [Developers Only]] jerryspring:
yeah when I uninstalled it via titanium backup I looked in the / system and found that the kingosuperuser.apk was missing in priv app. Thanks
[Android Software/Hacking General [Developers Only]] 920Rocky:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-20161205182033.

https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-20161205182033.apk

Download does not start for some reason?
[Android Software/Hacking General [Developers Only]] mortemonline:
Thanks

Thanks man. you removed a lot of pain and stress off my back and shulders.

to EVERYONE: do this exactly step by step, and you are good to go.

and, Thanks again.
[Android Software/Hacking General [Developers Only]] Sands207:
That's because supersu is DEAD. As in not used anymore. Even a simple Google search would have told you that.
[Android Software/Hacking General [Developers Only]] fil3s:
Try this link

For SuperSU zip: click :good:
[Android Software/Hacking General [Developers Only]] evildog1:
Updated links and devices spreadsheet. download.chainfire.eu still working and are saved to web.archive.org just in case
[Android Software/Hacking General [Developers Only]] GoldenFire36:
Hey evildog1, will your method work with a locked bootloader?
[Android Software/Hacking General [Developers Only]] GoldenFire36:
so on step 6.1 at the part where you copy the superuser.apk for android 5.0.x it says to change the permission to 644 are we supposed to do this to the folder or the apk?:confused:
[Android Software/Hacking General [Developers Only]] evildog1:
Sorry for late reply, didn't checked this thread

Folder = 755

APK file = 644

Hope it's clear

Yes, it will work since you only change in system partition.

Write permission in boot, recovery and ramdisk partition will require unlocked bootloader afaik
[Android Software/Hacking General [Developers Only]] Glenn_aneld:
https://seotank.ru/