Database Develop

Root stock Lollipop 5.0.2 with Kingroot & Super-Sume .......no tripping Knox

SM-T700 UK version stock 5.0.2
1. Root using Kingroot 4.5
2. ONLY now !!! install and run Super-Sume
3. Update SuperSu binaries
That's all : you have root, SuperSu and Knox still "O" and Kingroot it's gone...
Would people please post the full build version of the firmware they have success or failure with, so others are aware of which ones work.

has this method been verified by other users?
Share your experience please!

It's brand new...
Verified by myself

Have you maintained root after reboot?

ashyx said:
Already tried it, v4.5 is posted in my kingroot thread, didn't work on lollipop for t805.
Neither did supersu me, binary always fails to update, once it did manage after several tries, but root is lost after reboot.
Supersu me is just the same script as posted in the kingroot thread. Root always lost after reboot.
Have you maintained root after reboot?
Click to expand...
Click to collapse
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent

stefan.pilsu said:
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
Click to expand...
Click to collapse
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?

louiscar said:
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
Click to expand...
Click to collapse
Super-Sume install SuperSu
Update binaries and done

I waiting also others to confirm

stefan.pilsu said:
I waiting also others to confirm
Click to expand...
Click to collapse
Ok Thanks for putting this up, if it's reliable it will save a lot time for many.

..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!

angelshie said:
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
Click to expand...
Click to collapse
Super_Sume make all this "work" with one click !

Ok guys, thanks for confirming, Sweet

Thanks for the tip. This worked perfectly. I installed Kingroot 4.5. When Kingroot runs scroll down and press "Try it" and it rooted. I then immediately installed Busybox from the Google Play store and ran the smart installer. After a successful install of Busybox, I then installed Super-Sume from the Play store. I ran Super-Sume and it installed Super SU and removed Kingroot. After that, I opened Super SU and allowed it to update the binary. Rebooted. I checked root with Root Checker app and checked Knox with an app called Knox Status on the Play store. Root is still active and Knox is still at "0". I powered off, then restarted again. Root has stayed.
I did this on a brand new US region SM-T700 pulled straight from the box and updated to Lolilipop from OTA.
System Version:
SM-T700
LRX22G.T700XXU1BOE3

*ROOT WORKING !! SMT-700 OTA 'lollipop'

Confirmed working on Lollipop NEE-T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.

ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits got to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
I've told you ...

ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
It does not appear to work on T707a with 5.0.2.

Maybe ashyx could help.
What exactly didn't work for you ?

stefan.pilsu said:
I've told you ...
Click to expand...
Click to collapse
Do you think this is likely to work for KitKat ANL1? I already downgraded as part of Ashyx's tutorial to ANF7.
My only reservation to going to Lollipop is that I want to use the Xposed framework which I think is still in it's infancy for 5.x or still not compatible.
So before this my options are to keep the original Kitkat by Flashfire - ANL1 or go directly to Lollipop. For the latter I could just get the OTA and do this method now. But not sure if I go to ANL1 kingroot will work as easily
If not I'll continue in the normal way I guess.

Once you have root with Kingroot install Super Sume and run it.
Kingroot 4.5 from ashyxs tread works for me.
Super-Sume just install busybox, SuperSu and get rid of Kingroot.
Why not use Flashfire to install whatever you want: KK or L ?

[SOLVED] Safe to continue?? or start again? please help

This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance

problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?

I would just start over and try a different root program. busybox is failing to install because the root didn't work.

Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help

xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate

i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb

thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.

Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers

xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it

can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)

Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:

Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed

@thesweeney80 you are welcome have fun

xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:

:good: awesome! don't forget to pay it forward sometime.

Titanium Backup Error After Freezing Unused Apps

I've had the phone rooted last year and haven't really messed with freezing unused apps until recently, bringing my battery life length to normal.
One of the apps I have frozen was Kingroot. Out of all the apps I've frozen, I'd think that one would be the culprit.
Here's a list of the relevant apps I've also frozen:
Root Browser
Root Checker
If there isn't a way around this, could I possibly reinstall or update Kingroot? Thanks in advance.

If your bootloader is unlocked and you have TWRP installed, you can use SuperSU instead of Kingroot.
Kingroot has issues and should only be used when absolutely necessary. Someone said it sends data back to China for no good reason.
Here's a post that details how to completely remove Kingroot and use SuperSu instead. I've only posted the relevant parts.
TheSt33v said:
However, if you absolutely cannot use a computer, you can do this, although I do not recommend it:
1. Google Kingroot, download, install it onto your phone and use it to root your phone. Be aware that Kingroot is developed by a Chinese company, and part of their rooting process involves sending lots of personal info to them for reasons that aren't entirely clear. There is some debate over how legit they are, but their root method should work on a phone with an unlocked bootloader.
5. Uninstall Kingroot.
6. Download this to your phone and install it using TWRP:
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041.
This will remove all of the Kingroot files from your phone that probably were left on it after you uninstalled it.
7. Download this to your phone and install it using TWRP:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
You should now have a rooted, TWRP-equipped phone.
Click to expand...
Click to collapse

Thanks for the tip on KingRoot, Chazz.
I've just figured out the solution; Settings/Apps/Menu option in upper right-hand corner/Reset app preferences :good::good::good:

coconutt said:
Thanks for the tip on KingRoot, Chazz.
I've just figured out the solution; Settings/Apps/Menu option in upper right-hand corner/Reset app preferences :good::good::good:
Click to expand...
Click to collapse
I edited my post to incluede @TheSt33v instructions on how to completely remove Kingroot. There is no valid reason for keeping it on your phone.

Fire 7" 5gen: No root in CM12

I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?

Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".

Make sure you did reboot after root activation in dev options

Yes, as I said, I already rebooted. Any other idea?

ulysseh said:
I just got a new Fire 7" 5gen, with Fire OS 5.3.1. I immediately used Supertool to root it and install the CM ROM.
So far so good.
But not realising how CM deals with root access, I manually installed SuperSU. SuperSU wanted to update the binary, which I accepted. It also wanted to remove the existing root manager, which I also accepted... And then the binary update failed.
It's only then I realised that I somehow ended up with a custom ROM but no root. Neither SuperSU nor Superuser can get root access (both failing binary update), and Kingroot can't root it either. I'd have just flash CM again, but FlashFire also doesn't work without root. So I'm kind of stuck now...
Any idea how I can get root?
Click to expand...
Click to collapse
ulysseh said:
Just realised that I had to turn on root in Dev options. I did that and rebooted, but Super SU still fails to update the binary. FlashFire now says "Root was found but access could not be acquired".
Click to expand...
Click to collapse
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.

Davey126 said:
At this point your best/only option is to reload FireOS via Amazon's stock recovery (same version as before) and redo root, Flashfire, etc. There is no reliable way to secure root on a custom rom as device lacks access to a 'real' recovery environment. Don't bother with KingRoot on CM - likely won't work.
Click to expand...
Click to collapse
Yeah, I did the whole thing from zero again. Happily it worked this time. Thanks!

Amazon Fire 7 (CM 12.1-20160710-UNOFFICIAL-ford) -- Lost Root and SuperSU Binary Busy

Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?

Blastyrant said:
Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?
Click to expand...
Click to collapse
Lol. Unlock bootloader and flash latest lineage:
UNLOCK: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
LINEAGE: https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-12-1-t3639447

Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?

From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.

Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
If you have lost root your only practical options are: 1) restore FireOS and start from scratch; or 2) follow the links suggested by @Rortiz2 (here).

MontysEvilTwin said:
From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.
Click to expand...
Click to collapse
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?

Blastyrant said:
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?
Click to expand...
Click to collapse
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.

Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
No need to install linux. Just use VirtualBox or bootable USB!

Rortiz2 said:
No need to install linux. Just use VirtualBox or bootable USB!
Click to expand...
Click to collapse
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?

MontysEvilTwin said:
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.
Click to expand...
Click to collapse
Thank you! I bookmarked it and grabbed the file. I've just reinstalled it and am being told "no root detected". =(
Still, it was worth a try!

Blastyrant said:
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?
Click to expand...
Click to collapse
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Enviado desde mi Mi A2 mediante Tapatalk

Rortiz2 said:
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Click to expand...
Click to collapse
That said, you have to decide if the benefit is worth the effort/hassle. In the US $64 scores a very serviceable 8" tablet at Walmart running the latest version of Android that runs circles around all Amazon offerings except the HD10.