[General Questions and Answers] freestilesteve:
Cool

NIce. I outta give that a try. I used kingroot 3.3.1 so not sure if it varies from version to version. When you say "Froze it through terminal emulator" I'm not quite getting that. Like actually freeze it through the terminal. I've never looked at superSU correctly. So do you actually mean freezing from within superSU ( does superSU have a terminal), or actually freezing it with a terminal outside superSU? And was it kingroot.apk or kinguser.apk you froze? And whats pm disable (package name)?? I'm still new new to all this droid stuff but I think I can manage with a few directions. I imagine the last part in which you manually removed the kingroot.apk was done with a root file explorer right like es file explorer or something like that? Or did you remove it though the systems-package manger in android? And in the end how did youactually get superSU on there. Did you have to flash it after you removed all the kinguser/kingroot stuff?? Just cant see why its not working for me when I swear I done that stuff. Maybe it comes down to the freezing part which keeps root long enough so that you can switch/upgrade the binaries from kingroot to superSU. I have TiBU could I freeze it with that? I did notice theres freeze option in TiBU. Just not sure I'm clear on the whole "Freeze" thing. ALso when you say manually uninstalled it was that through kingroot/kinguser the app itself, uninstall through PM or unistalled through TiBU. Sorry

for allthe questions but I think with the steps you took I might actually be able to make this happen.

Basically if I can somehow get it to freeze through terminal emulator su or ( TiBU not sure if theres a difference in the "Freeze" you mention), pm disable(package name) then manually uninstall the king root apk. So that SuperSU can handlesall the requests and the binary will update properly I'll be good to go. Any clear cut instuctions will be much appreciated by me and probably the others who might be want to do this as well. Just didnt think there was any other way. Maybe I'll go real slow this time and try to do what user mtnlion stated. Dont want any of my long ass post to offend anyone. I just try to describe things in detail so I can get good answers that lead me to a solution. Glad I can do this instead of having to do a full

system restore, although I dont mind doing that as it should wipe off the remnants of whatever junk has been

left on my system. Everyone gave me great answers and suggestions but from what mtnlion said and someone else that responded to me, it seems like the problem for me was/is keeping root long enough to

remove kingroot and replace with superSU. What I think is/was happening in my situation is that I was/is removing root too soon so thats why I'm not able to install or upgrade to superSU. mtnlion hit it on the nail

when he mentioned "Freeze" thats exactly what I think I have to do is "Freeze" the app before I remove it so that it will give me time to istall/replace with superSU and then remove kingroot/kinguser and go from there. Any order in which to remove kingroot/kinguser? Sorry I sounded like I answered myself but sometimes it helps me to try and get to an answer somehow. And I come from more ios background although I've had a crappy Android phone for the last two years. My contracts up in june so I can get something else.

Not neessarily saying I'll get an Iphone but I'm more used to IOS/OS X. Then again it seems like a majority of the apps I been testing or mostly Android based so I might have to just get another Android phone. Oh well. Have to make the best of it I guess. If you have any suggestions or diections or step by step on how to do this, heck even if you wanna post if for other heads to follow, as I've seen it asked more then once that would be great.

Thanks again though mtnlion. I might give it a shot here soon. I have a vacation from work so I'm gonna mess

with my phone and this tab. Try to learn this Android stuff more, although I've only had my Air2 for like two weeks and I love it. I did like the fact the rca tab was rather easy to root with that kingroot. Thats the

first device I've ever rooted that had kinguser. All the other devices have already had superSU or the other superuser which never gave me problems switching to superSU. Being in chinese dont make kingroot any easier. lol!! Thanks guys.

P.S. I got to where it granted superSU root permissions, was able to remove kinguser, lost root after that and had to reroot with kingroot, restarted and I still had root and it didnt install kinguser binaries but I still got the fail in superSU to install binaries, but it kept giving superSU root permissions with the circle spinning so after I thought I might try to flash superSU in recovery and see what comes about it since after I removed kinguser it didnt install the kinguser binaries like before and still had root and was asking superSU for permissions so I think I'm getting close.