I found a solution for rooting my D801 running Android 5.0.2. I used KingRoot to gain root access and then Super-Sume Pro to remove KingRoot and install SuperSU. I have not installed TWRP because I am going to stay on stock. It was difficult to find a one-click solution so I hope this helps someone else.
Kingroot has worked for me, too. Nothing else worked, no matter what I did. But Kingroot works great! Thanks for posting.
I have tried Purple Drake, ioroot, StumpRoot, and LGOneClickRoot. None of these worked. I'm particularly chagrined over the ioroot failure because ioroot is listed in the Cyanomodgen installation instructions.
I have not tried Kingroot and am hopeful it's the answer to my prayers.
Could you please confirm your T-Mobile Lollipop software info with mine to make sure we're on the same page? Many thanks.
Android version: 5.0.2
Build number: LRX22G
Software version: D80130c
Woohoo, Kingroot does indeed root the phone. That's the good news.
Now for the bad news. Super-Sume Pro does NOT remove KingRoot v4.8.0 (latest version). I like having a rooted phone, but I don't like having Spyware running on it that chews up bandwidth. How do I get rid of this thing? Brute force delete of binaries?
UPDATE: I got rid of KingRoot via method 2 at https://www.droidmen.com/remove-replace-kingroot-kinguser-with-supersu/. Unfortunately although RootChecker claims the phone is rooted none of the apps that need root can find the su binary because the SuperSU installation failed. Effectively the phone is un-rooted since apps requiring root are inoperable. So back to square 1. It's a big steaming pile of you-know-what.
UPDATE: I retraced my steps and re-ran the shell script of method 2 above. This time it worked. Kingroot is gone, SuperSU 2.49 is installed, and the phone is rooted according to root checker. The phone seemed strangely unstable for a while, but seems to have settled into normal behavior. Don't know if that was a consequence of this procedure or is possibly a hardware problem (battery?). Will keep a close eye on it, but for now all the apps that need root have it. Contemplating the installation of TWRP via GooManager, but that's not a high priority right now.
If anyone reading this is a bloatware removal expert (especially with regard to LG & T-Mobile) I'd like to hear from you. Tools that I've seen mentioned in this regard are Titanium Backup, System App Remover, and Clean Master.
Guys, just followed nbi1's method and finally got this working! Thanks!
Bageland2000 said:
Guys, just followed nbi1's method and finally got this working! Thanks!
Click to expand...
Click to collapse
Did you by any chance install TWRP? If so, how did you unlock the bootloader? I'm looking for a pain free unlock. Held out hope for FreeGee, but despite claims to the contrary this app doesn't support many G2 variants such as mine, the D801 30c (T-Mobile).
nbi1 said:
Did you by any chance install TWRP? If so, how did you unlock the bootloader? I'm looking for a pain free unlock. Held out hope for FreeGee, but despite claims to the contrary this app doesn't support many G2 variants such as mine, the D801 30c (T-Mobile).
Click to expand...
Click to collapse
Never installed TWRP, sorry...
Bageland2000 said:
Never installed TWRP, sorry...
Click to expand...
Click to collapse
Don't try it with Flashify. It'll destroy your recovery. Before trying any custom recovery make sure you have the stock kdz on hand so you can flash the stock recovery if need be.
UPDATE: I was able to flash the stock recovery.img. Of course that doesn't help as far as TWRP is concerned, but at least you wouldn't have a totally munged recovery on the phone.
UPDATE: Was able to successfully install TWRP using Autorec after figuring out that the SuperSU "Mount Namespace Separation" setting needs to be cleared/unchecked.
nbi1 said:
I have tried Purple Drake, ioroot, StumpRoot, and LGOneClickRoot. None of these worked. I'm particularly chagrined over the ioroot failure because ioroot is listed in the Cyanomodgen installation instructions.
I have not tried Kingroot and am hopeful it's the answer to my prayers.
Could you please confirm your T-Mobile Lollipop software info with mine to make sure we're on the same page? Many thanks.
Android version: 5.0.2
Build number: LRX22G
Software version: D80130c
Woohoo, Kingroot does indeed root the phone. That's the good news.
Now for the bad news. Super-Sume Pro does NOT remove KingRoot v4.8.0 (latest version). I like having a rooted phone, but I don't like having Spyware running on it that chews up bandwidth. How do I get rid of this thing? Brute force delete of binaries?
UPDATE: I got rid of KingRoot via method 2 at https://www.droidmen.com/remove-replace-kingroot-kinguser-with-supersu/. Unfortunately although RootChecker claims the phone is rooted none of the apps that need root can find the su binary because the SuperSU installation failed. Effectively the phone is un-rooted since apps requiring root are inoperable. So back to square 1. It's a big steaming pile of you-know-what.
UPDATE: I retraced my steps and re-ran the shell script of method 2 above. This time it worked. Kingroot is gone, SuperSU 2.49 is installed, and the phone is rooted according to root checker. The phone seemed strangely unstable for a while, but seems to have settled into normal behavior. Don't know if that was a consequence of this procedure or is possibly a hardware problem (battery?). Will keep a close eye on it, but for now all the apps that need root have it. Contemplating the installation of TWRP via GooManager, but that's not a high priority right now.
If anyone reading this is a bloatware removal expert (especially with regard to LG & T-Mobile) I'd like to hear from you. Tools that I've seen mentioned in this regard are Titanium Backup, System App Remover, and Clean Master.
Click to expand...
Click to collapse
Thanks for the info. Did method 1 not work for you though?
So I finally tried to root my phone. Tried the LG One Click Root first and as posted here it did not work right. I have now SuperSU on the phone but I can't grant root to anything. Rootchecker shows no root. Now I tried Kingoroot and SuperSU asks to grant access but I can't confirm it. Looks like I have to first get rid of SuperSU? Stuck here not sure what I need to do the get rid of the butchered SuperSU install. Any tips?
Can someone point me to where I can get the AutoRec version that works on D801 Lollipop?
dant3ch said:
I found a solution for rooting my D801 running Android 5.0.2. I used KingRoot to gain root access and then Super-Sume Pro to remove KingRoot and install SuperSU.
Click to expand...
Click to collapse
I was able to do the same using KingRoot-4.1.0.249-release-nolog-201505211812_105241.apk and Super-Sume-v9.1.9.apk
If KingRoot tells you "Unable to get root strategy" or "Failed to acquire cloud issued Root strategy", try to reboot once or twice before trying anything else!
I rooted my p8 lite with king root. Then I replaced it with super su. But I couldn't instal busy box so I removed super su. Then it messed up. Now I can't uproot it. It's not also properly rooted. If I open king root it says root auth error. Fix now. But it's not fixing. Now what can I do? ? Please help me out
Root auth error
I've got a simillar problem, I once rooted my Honor 6 with Kingroot, then uninstalled the app (unrooting the phone), then I rooted it again and that's when I got this error, saying the root failed. I checked with Root Checker app and it says that the phone's rooted, but KingRoot says to "Fix now" and it is not able to do so. Not sure what to do, I neither can properly root, nor unroot my phone ! :/
I think I have a solution (might not work, please don't kill me!), if you open SuperSU and update the binary, what happens? Also, if you flash the binary via recovery, what happens, I'd like to know if it is a binary issue since (from what I know) kingroot uses an old binary.
I was messing with a bunch of stuff like supersu me, trying to replace kingroot with supersu in terminal emulator, but I don't think that had anything to do with it. I re-ran kingroot today, and now, even if I power it off all the way, or reboot, it still holds root! Permanent root is a big step, but I always want more. lol. I'm hoping there will be a way to replace it with supersu soon, and get flashfire working. On 5.1.1 BOH4 Good luck everyone!
Edit: I have no idea how I was able to keep a permanent root, but alas, I had to go messing with $#!+, and end result was having to flash stock firmware and not be able to get permanent root again. I'm not sure if things I was messing with played a strange part, or if somehow kingroot magically went through that one time, but it sucks to have lost it. I can replace kingroot with supersu using a Replace_Kinguser_with_SuperSU-v2.4 zip file, flashing it in terminal emulator, then using a power menu for root app to soft reboot before kingroot fail errors start to pop up. Sadly, if hard reboot or power off and on are done, root with supersu are wiped. If you do this, don't update the su binary or you'll hang at at&t logo in a softbrick.
whats wrong with twrp?
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
the bootloader is locked
xjimmy said:
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
Click to expand...
Click to collapse
if i remember right theres some files thst you need to delete to prevent "unroot" in boot...... similar to stock recovery flashing back on some devices after installing twrp or cwm
My rooting experience with kingroot has been temp root, with reboots causing soft brick, an update to kingroot making reboots possible without bricking, but causing unroot, and the latest update where it retains root after reboot. So whatever they did, it's working now. It is limited, however, as I doubt cwm or twrp is flashable, and flashfire doesn't work with kingroot.
What I don't want is for people to doubt me. It's easy to download the latest kingroot and try it. The lp fix boot.tar is still available, but you'll see, you won't need it. And the stock firmware .tar is available so you really have nothing to lose. What I'm hoping is, more people do it so we can move forward. I'd like to see a new version of supersu me, and flash fire working. Get to a point where we see some custom roms.
Which version of KingRoot did you use? 5.0.0 or 5.0.1?
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
KGB7 said:
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
Click to expand...
Click to collapse
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
xjimmy said:
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
Click to expand...
Click to collapse
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
KGB7 said:
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
Click to expand...
Click to collapse
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
xjimmy said:
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
Click to expand...
Click to collapse
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
KGB7 said:
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
Click to expand...
Click to collapse
I replied to this comment a while ago, so I thought. lol. You ever reply to something, hit submit, and come back later to find it not posted? grrr. Thank you for at least trying again. It wouldn't seem likely that by simply clearing the cache, root would get wiped. I almost want to try it myself. What I wrote was that I would, if possible, love to do a system dump, or whatever they call it, so a developer could take a look at how and why I have permanent root. That would be to say that a developer would be interested at all. Supersu just froze in the process, and I read it's because kingroot now patched it so it wouldn't remove their root. Would be cool to get supersu on it and maybe get a custom rom or two.
Get bootloader unlocked
toolhas4degrees said:
the bootloader is locked
Click to expand...
Click to collapse
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
nd4400 said:
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
Click to expand...
Click to collapse
Ask at&t nicely.
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
bbc581 said:
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
Click to expand...
Click to collapse
I read that too, but you know what, it still doesn't work. I've found a zip file called Replace_Kinguser_with_SuperSU-v2.4 that works. What you do is install a power menu for root users first, then root with kingroot. Next, you install the replace kinguser zip using terminal emulator, which there are instructions online and on youtube on how to do it. Once you've replaced kingroot with supersu, quickly use the power menu app to do a soft reboot, as to avoid kingroot failure errors. DO NOT update the su binary. Only problem is, if you do regular reboot, or power off the tab, then power it back on, root is lost again. I have no idea how I got permanent root with kingroot, but I've lost it now while messing with things. I wish I would've tried to replace it with supersu this way when I had it just to see if it woul've still retained permanent root as well. Now what?!?! lol
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.[/QUOTE]
Hey man, old stuff, I know, but I thought this was interesting:
http://androidforums.com/threads/tutorial-how-to-root-the-sm-t337a-lollipop-with-kingroot.1100261/:
I'm not sure if he's saying to keep rebooting, and re-rooting until root sticks permanently, or to leave kingroot running without rebooting for a long time, and permanent root will sink in eventually. I think he means the second one, too leave it running without rebooting. On a sidenote, I have been able to use a replace kingroot with superuser 2.74 via terminal emulator with success, even after rooting with latest version kingroot. Updating supersu binary results in softbrick on reboot though. If you don't update user binary, and you reboot, you just lose root, is all. And sometimes the zip doesn't work, and it takes reboot, re-root with kingroot, then re-run terminal emulator. Flashfire doesn't like kingroot, but it opens up with supersu after this method. Not sure if it can actually flash zips though. Just thought I'd share my latest findings.
xjimmy said:
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
Thanks for the info. An interesting discovery! After going back and reading that guy's article again, I noticed that he posted a link to download kingroot. I was curious what version he used. It was 4.8.1 . When I tried downloading 4.8.1 from the xda link you gave me, it kept popping up with a network error. This time I downloaded 4.8.1 somewhere else and tried it. After root, I kept closing kingroot, swiping it clear in task manager, and re-opening it until it gave me the notice that it deployed itself as a system app. I then rebooted (not soft reboot) and it partially kept a permanent root this time. If I went into root checker, it would tell me no root, but other apps were popping up the grant permission tab. I'm sure I'll get root to stick permanently again, then I'll try to install supersu over it again, see if I can't get that as a permanent root. It's not the end of the world to me either, but it just drove me nuts not knowing how the hell I got it. Also, it's just fun to mess with stuff. lol. So in the chain of updates, 4.8.1 is right before 4.9.2, so I'm guessing that I probably got permanent root from 4.8.1 and then updated it, or possibly that I ran 4.8.1, updated, and maybe optimizing or running root again with 4.9.2 finished the job. Anyway, thanks for writing back!
Click to expand...
Click to collapse