[General Questions and Answers] freestilesteve:
@ N_psycho_PD_uh?

Thanks for the help bro. I could just leave kinguser. Recovery works fine. I was just a little worried in the last post and jumped to conclusions. It just wasn't working with quick boot because I wasn't rooted. Manually getting into recovery worked fine and once rerooted quic boot worked as should. I'm not a superuser by far, and use root Mainly for some touch apps that require it for gaming that I do. I can't even get past installing/upgrading the superSU binaries, but yet its telling me to update superSU in notifications drop down. If I try that I get the same failed error msgs as before. When I flash su.zip it unroots me after flash and upon login asks me to update the superSU binaries, and if I try that its the same failed error msg as before. I don't like having superSU prompt me to update if its not going to install properly. When flashing, it seems like the flash takes because superSU is in my apps and asks me to update but once again I get that same error msg of failed installation when trying to install the binaries. If I try to remove king user it removes root, and if I try to install/update the binaries in superSU it gives me the error in reference to "4.3 android and not being rooted to re-root and consult the relevant forums for your device, " in which afterwards it doesn't allow me to install/update the binaries from superSU. I can't even get superSU binaries to install/update no matter what, and even when it installs side by side with kinguser as shown in /device/system/app from es file explorer I still can't fully install/update the binaries in superSU even though it prompts me to. It gives me the same failed msg even if there both installed and I go to superSU to try to install/update those binaries. Once the original (king user) is removed roots gone. The only way I've noticed that root comes back is by actually trying to reroot again with kingroot in which I don't think king user is fully removed anyway, because even though its not in the apps tray it still must be in the system, because after trying to reroot with kingroot and if it roots successfully king user will just pop up in my apps. Even after that the only way I get root back is to actually go into king user and let it update/install the binaries, or vice versa the other way around but its one of the two. Could be that I have t install/update the binaries first in king user and then reroot. Not sure but one of those ways is the way I get root back. After rooting that way with Kingroot I tried to go into superSU before I even went to king user to update/install the binaries in which it fails. Any kind of flashing I've done just unroots me and prompts me for the superSU binaries to update in which once again I get the "Installing Please wait..." and then after it fails it says "Installation Failed! . It seems like I need higher permissions maybe to fully remove kinguser to let superSU binaries. Maybe a es file explorer play around but I'm not sure. I would assume thats why superSU binaries can't install because kinguser can't fully be removed without needing to reroot which seems to rely on king user to reroot. I could always wait till a custom rom comes up or just leave it as is. I'm not a super user, but use root for few things. I got the lookout security premium so I think I'm good on the antivirus side of things. I think I already did a full/factory restore/wipe everything and still when I do the process with kingroot to root its the same issues. Although I'm not sure on the full restore/reset thing , but I think I did do one of those and ended up in this same situation. I could be jumping hoops, but do you think maybe even though I'm rooted correctly somehow my bootloader got locked by king user and thats why I'm not allowed to remove king user with removing root and install the binaries through superSU?

Not sure whats up. In the end I might do a full/factory/restore/wipe and just try again and see what happens. I always could just leave things the way they are now. Maybe in the future someone will work on a custom rom or something. We finally got root and recovery for this tab so its probably a matter of time really. If nothing after I try again( which I might not) I might just end up leaving things rooted as they are. Lookout seems to work good so I don't think I got any viruses from kingroot/kinguser. Not to mention I scanned the apk on my computer before actually even putting it on my tab so it was double checked. Not that I'm worried about that. Anyway thanks for the help yo, and you have any more suggestions let me know. Other then a full/factory/restore/wipe I don't think I can do anything else.

I tried adb, but it didn't recognize my device, but thats a question for that thread. It was the 1 click installer adb somewhere on this site. So no go with that, but I think thats an issue on its end with the drivers are something, as I ve used adb before and it worked fine. Of course that was when I set it up the long way. The 1 click installer might not fully be working yet, are maybe I'll have to try it again. Once again thanks for the help. If you have any other ideas,suggestions, or think I should just leave things as is let me know.