somebody could teach me the easiest way to replace kinguser with supersu please?
dewagame said:
somebody could teach me the easiest way to replace kinguser with supersu please?
Click to expand...
Click to collapse
Follow these simple steps:
1. Go to the Play Store and install SuperSU.
2. When SuperSU is installed, give it permission as Super User.
3. Uninstall KingUser.
4. Done.
ИΘΘK¡€ said:
Follow these simple steps:
1. Go to the Play Store and install SuperSU.
2. When SuperSU is installed, give it permission as Super User.
3. Uninstall KingUser.
4. Done.
Click to expand...
Click to collapse
hI! I try on my HUAWEI ASCEND G6 and... dont work ... is possibel that an update that Kinguser had done make it impossibel?????
I root with RootGenius_en, was ok, kinguser ask for a update, done. But Now i whant to change do SuperSu and dont work. I had permissions and every thing...
Help! :crying:
Me too
I'm trying to do this too, but I aint sure how to do it. I mean I guess if its not super necessary I can leave it the way it is. Tried this method and its a no go. I don't think the KingUser SU is letting superSU update its binaries. I already have twrp, but not sure what next. If its not necessary I'll leave it alone, but I was just wondering if theres any reason to change over or if it could even be done.
P.S This way never worked for me as superSU can't get past trying to install the binaries. I got twrp so I'm wondering if I'd have to flash it. Nothings wrong on my end are anything, but I just assumed having superSU would be better then kinguser but not really sure.
many people have this problem.
first of all, kinguser is great to root the G6, and in most cases the only working method without custom recovery,
but because it flashes kinguser.apk as system app you can't uninstall it the normal way.
the solution is to flash supersu.zip and then uninstall kinguser. this way supersu will be your systemapp.
find the files and tutorials you need on our facebook group,
we have 1500+ members, CWM + TWRP, android 4.3 + 4.4, we can root your g6 and unlock your bootloader.
but we still don't have a subforum on XDA....
https://www.facebook.com/groups/328261053999820
Must vary from device to device cause I've did all that, and it gives the message "Installing Please wait..." and then after it fails it says " Installation Failed! Please reboot and try again" and if kinguser is removed in superSU when trying to update/install the binaries it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If just upgraded to Android 4.3 you need to manually re-root- consult the relevant forums for your device."
This aint the g6 though but this thread is the kinguser replace with superSU thread. So I thought I'd post in it.
washichi said:
many people have this problem.
first of all, kinguser is great to root the G6, and in most cases the only working method without custom recovery,
but because it flashes kinguser.apk as system app you can't uninstall it the normal way.
the solution is to flash supersu.zip and then uninstall kinguser. this way supersu will be your systemapp.
find the files and tutorials you need on our facebook group,
we have 1500+ members, CWM + TWRP, android 4.3 + 4.4, we can root your g6 and unlock your bootloader.
but we still don't have a subforum on XDA....
https://www.facebook.com/groups/328261053999820
Click to expand...
Click to collapse
Install SuperSu rom magazin play.
Then instal rom lite box.
Open the app, and uninstall kinguser
easy, and it`s working.I just deleted kinguser 2 mins ago
Hum
@andruala Never worked for me that way, anytime I remove king user root gets removed. Never was able to flash superSU rom correctly because binaries couldn't get updated from superSU because root was removed once king user was uninstalled. I've heard people mention it working the way you suggested, but I've also read posts where people have a hard time getting it replaced with superSU because root gets removed when king user is replaced, which doesn't allow superSU to install the binaries correctly. Most people probably can't get the binaries installed correctly from superSU which is the same problem I had so they end up just leaving it king user. I could try whats suggested here but I very much doubt its going to work as explained from my conflict that when king user is removed, root is removed and whether you flash a SU zip or not root still aint enabled because SU binaries are nt installed correctly. So until I actually can confirm this works myself I'm gonna prob say its a no-go for me. Could be device specific but I did all this to a tee and still had problems. There was a post on freak tab where someone had the same problem. I might still try this, I just dont see it working like as said.
freestilesteve said:
@andruala Never worked for me that way, anytime I remove king user root gets removed. Never was able to flash superSU rom correctly because binaries couldn't get updated from superSU because root was removed once king user was uninstalled. I've heard people mention it working the way you suggested, but I've also read posts where people have a hard time getting it replaced with superSU because root gets removed when king user is replaced, which doesn't allow superSU to install the binaries correctly. Most people probably can't get the binaries installed correctly from superSU which is the same problem I had so they end up just leaving it king user. I could try whats suggested here but I very much doubt its going to work as explained from my conflict that when king user is removed, root is removed and whether you flash a SU zip or not root still aint enabled because SU binaries are nt installed correctly. So until I actually can confirm this works myself I'm gonna prob say its a no-go for me. Could be device specific but I did all this to a tee and still had problems. There was a post on freak tab where someone had the same problem. I might still try this, I just dont see it working like as said.
Click to expand...
Click to collapse
Yes...i`m really sorry.For me wit worked before i restarted the phone...
After de restart i`ve seen that the root is not working anymore...
Sorry for my bad.
No worries bro. Probably varies depending on how you root from device to device.
Its not your fault. No worries. I'm just thinking it varies from device to device and how you actually go about rooting . I'm also thinking that maybe if I rooted with another app/prog that it would have been easier to switch from king user to superSU. I use lookout premium security on my phone and kingroot and king user have never been flagged with any viruses so I've just left it on and running the way it is and so far so good. Other then the two errors I mentioned in the previous post king user/kingroot has been working good. I'm sure if I did a whole restore/wipe/clean and root with another program there might be a possibility to remove king user and replace with superSU but in the end I just decided to roll with king user/kingroot as I didn't feel like doing al that and its been doing its job fine.
QUOTE=andruala;58880236]Yes...i`m really sorry.For me wit worked before i restarted the phone...
After de restart i`ve seen that the root is not working anymore...
Sorry for my bad.[/QUOTE]
Well I thought about leaving kinguser sitting there on my system too until one day I installed network monitor stuff and noticed kinguser sure likes to make HTTP connections every time the Internet is available. Imagine that. Also have a look, there are /system/bin/.usr/.ku etc. hiding all over your system.
The earlier versions of Kingo Root were much better
jidanni said:
Well I thought about leaving kinguser sitting there on my system too until one day I installed network monitor stuff and noticed kinguser sure likes to make HTTP connections every time the Internet is available. Imagine that. Also have a look, there are /system/bin/.usr/.ku etc. hiding all over your system.
Click to expand...
Click to collapse
Those earlier versions were putting SuperSU binaries into the root. But now they are putting on this King User crap. Reason I say it's crap is exactly what you mentioned. As soon as I root a phone with Kingo Root, Google Search immediately tells me that it will not allow me to search for anything because "your computer or network may be sending automated queries. To protect our users, we can't process your request right now"
Good God! What the heck is Kingo Root putting onto these phones now? It sure isn't putting just su binaries in there.
Indeed. What is needed is for someone to take a vanilla phone into a cleanroom, install the mess, and report back on exactly what ended up getting put where, in order for somebody to make a "kinguser detox/.antidote" APP and/or shell scripts that would clean the mess totally back off.
don't know if it's gonna help you ( have alcatel onetouch idol 2 mini s):
i also couldn't update binaries su and had kinguser.
then i downloaded the beta version of supersu (on xda) and flashed it with my cwm. after that when supersu asked if i wanted to update, i said yes and choose normal update (not the cwm/t... one) it than updates and asked if i wanted to remove the external root apps (ie: kinguser) and voila!
(sorry English isn't my language, so don't know if i explained myself well^^)
satine01black said:
don't know if it's gonna help you ( have alcatel onetouch idol 2 mini s):
i also couldn't update binaries su and had kinguser.
then i downloaded the beta version of supersu (on xda) and flashed it with my cwm. after that when supersu asked if i wanted to update, i said yes and choose normal update (not the cwm/t... one) it than updates and asked if i wanted to remove the external root apps (ie: kinguser) and voila!
(sorry English isn't my language, so don't know if i explained myself well^^)
Click to expand...
Click to collapse
Why did you need to root with kingo if you have custom recovery?!
I rooted first then found the cwm for my phone?
satine01black said:
I rooted first then found the cwm for my phone?
Click to expand...
Click to collapse
Oh. I wasn't angry at you Was just asking.
it took me like a year to root my phone then i couldn't make it work well with kinguser, and i wanted supersu anyway, so i found that i could install manually the app with cwm .
anyway, i don't now if you can use cwm without a root?
satine01black said:
it took me like a year to root my phone then i couldn't make it work well with kinguser, and i wanted supersu anyway, so i found that i could install manually the app with cwm .
anyway, i don't now if you can use cwm without a root?
Click to expand...
Click to collapse
You can, but it doesn't really make much sense to.
Use Eroot, then try superSU installation
CVAngelo said:
Those earlier versions were putting SuperSU binaries into the root. But now they are putting on this King User crap. Reason I say it's crap is exactly what you mentioned. As soon as I root a phone with Kingo Root, Google Search immediately tells me that it will not allow me to search for anything because "your computer or network may be sending automated queries. To protect our users, we can't process your request right now"
Good God! What the heck is Kingo Root putting onto these phones now? It sure isn't putting just su binaries in there.
Click to expand...
Click to collapse
I had the same issue with my mobile, (Sony Ericsson Xperia Ray (ST18i)), I then rooted my phone with EROOT Software which installed a superuser app, then i got the .apk file of SuperSU via Bluetooth from a friend and installed it. one has to grant permission when it asks for superuser rights, then updating binary files is no longer a problem. It also asks for removal of the Superuser-app that was pushed through the EROOT software, you do that. Then I installed link2SD and link2sd pro key from google play store and converted the SuperSU app into a system-app. Now SuperSU is working perfectly again.
You both should try it!!
Related
i just rooted my phone using motochopper. and am trying to use ltm launcher. every time i open it, it says root context not able to get permission.
and then when i go to the superuser, it says the superuser binary (su) must be updated. and it ask if i want to recovery install or just install, but none of it works. i even downloaded supersu from chainfire and it says there is no su binary installed. so i need help getting root permission to apps so i can get lmt launcher to work.
i read an old post with they guy with the same problem and u told him to flash it with something but i am not really sure how to do that. so if u can kind of explain how to do that.
thanks
wrestling103 said:
i just rooted my phone using motochopper. and am trying to use ltm launcher. every time i open it, it says root context not able to get permission.
and then when i go to the superuser, it says the superuser binary (su) must be updated. and it ask if i want to recovery install or just install, but none of it works. i even downloaded supersu from chainfire and it says there is no su binary installed. so i need help getting root permission to apps so i can get lmt launcher to work.
i read an old post with they guy with the same problem and u told him to flash it with something but i am not really sure how to do that. so if u can kind of explain how to do that.
thanks
Click to expand...
Click to collapse
Just installing the super user app from play store doesn't root your phone.
SuperUser app only manages root permissions. It itself does not root the phone. Head over to your xda section and read there how to root your phone .
omerjerk said:
Just installing the super user app from play store doesn't root your phone.
SuperUser app only manages root permissions. It itself does not root the phone. Head over to your xda section and read there how to root your phone .
Click to expand...
Click to collapse
Like I've said I have already rooted my phone using motochopper. That's not the problem. The problem is not getting super user updated
wrestling103 said:
Like I've said I have already rooted my phone using motochopper. That's not the problem. The problem is not getting super user updated
Click to expand...
Click to collapse
Did you follow the official rooting procedure as given in your xda forum? Because if your phone is rooted then you won't face any problem related to SuperUser app and updating binary and all these stuffs.
I've had the same problem as listed above.
Help. Looking for root method for Hannspree SN14T71 on 4.2.2.
Please any help is appreciated.
Sent from my SCH-I605 using XDA Premium 4 mobile app
I'm in the same boat
tennisjunkie said:
Help. Looking for root method for Hannspree SN14T71 on 4.2.2.
Please any help is appreciated.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi! I bought the Hanspree 13.3 and noted that when I bought it one of the reviews said that it came rooted from the factory. Sure enough, I downloaded Root Checker and it says that I have Root. Unfortunately when I went to install Superuser Pro it installed but then says I need to update the binary (and I've done this multiple times on my Android phones or other tablets, it's a hobby what can I say?) it fails to update. I tried getting the binary direct from Sterickson and installing it through Recovery but that failed too. Busybox won't install because it says SU is screwed-up or I don't have root..
I was just hoping to find some ROM that could take advantage of this large screen, out of the box it boots and looks like a tablet for the sight-impaired (no offense) because all it does is display these huge icons and huge text (even after reducing text size to small). From all that I have seen today it looks like nobody is developing for this device. I guess we should be happy that we got 4.2.2 out of the box, at least we're ahead of most others..
Anyone have any ideas???
Chris R.
Ok. I have had the same experience and I found out the "solution" I believe. Did you try superSU? Because I tried to install superuser and it failed also but supersu did not. Try that and let me know.
Sent from my SCH-I605 using XDA Premium 4 mobile app
same wish here
Mine doesn't seem to be rooted. Any fail safe way to check if it is rooted or not? Want to speed this thing up and get the programs off of the RAM. I end up with only 300-400 mb available.
crodgers79 said:
Hi! I bought the Hanspree 13.3 and noted that when I bought it one of the reviews said that it came rooted from the factory. Sure enough, I downloaded Root Checker and it says that I have Root. Unfortunately when I went to install Superuser Pro it installed but then says I need to update the binary (and I've done this multiple times on my Android phones or other tablets, it's a hobby what can I say?) it fails to update. I tried getting the binary direct from Sterickson and installing it through Recovery but that failed too. Busybox won't install because it says SU is screwed-up or I don't have root..
I was just hoping to find some ROM that could take advantage of this large screen, out of the box it boots and looks like a tablet for the sight-impaired (no offense) because all it does is display these huge icons and huge text (even after reducing text size to small). From all that I have seen today it looks like nobody is developing for this device. I guess we should be happy that we got 4.2.2 out of the box, at least we're ahead of most others..
Anyone have any ideas???
Chris R.
Click to expand...
Click to collapse
It has a version of SU in xbin, but that doesn't mean that it is rooted really....
I have tried to get ADB to work, but so far no luck with that. I believe that I could get root to work if I could get ADB to work, but that is just a circular argument.
As to the screen, I use an alternate launcher. Apex in my case. It allows me to set the grid size and scales the icons to fit. Others like other launchers better, but I prefer Apex and purchased the pro version.
All around I like it, even without root. Still, I would like to be able to use GL to SD, Titanium Backup, and the host of other root reliant apps I normally install to get around certain deficiencies.
I'm also trying to root this device.
After a lot of digging, it looks like the su in xbin has different permissions (at least as far as I can tell), when comparing it to the su in my rooted s3. I used root checker pro. The permission of su on my s3 is -rwsr-sr-x root root 113036, while the permission for su on my SN14T71 is -rwsr-sr-x root root 67080.
The funny thing is root checker pro says that root ownership is present and is properly configured. The only thing I can think of is the permission isn't set right.
Now without adb (which I can't seem to get to work either, even though there is a debugging option in the android settings), I don't see a way to change the permissions. Anyone have any ideas?
My usb file transfer doesn't even work on this device. When I try to use usb to transfer files it remounts the internal memory and crashes the tablet, and I have to shut down and reboot to fix it.
I think that they messed up remote usb access period, and that might be why adb doesn't work.
I can use usb file transfer just fine. It only works through the OTG port, not the "regular" port, or whatever you want to call it. In fact, I have no idea what the regular port is even there for, if file transfer only works through OTG. My computer (running ubuntu 12.04) doesn't even detect the tablet using lsusb when connected to the non-OTG (regular) port.
And yet, ADB doesn't work with either port. They definitely did something wrong here, I just can't figure out what.
I can only transfer files via the OTG port and a flash drive. Connecting to a computer, and I have tried windows 7/8/8.1, only causes it to crash. We may only be able to hope that it is fixed in the next update...
Both external usb storage (OTG) and my computer work fine using the OTG port. Still can't figure out what the other port even does right now.
Are they still going to release updates? Hannspree's "news" section hasn't even been updated since 2012.
Ha. Your guess is as good as mine...
It is still my favorite tablet though. The Price/Performance ratio is good, and I love the huge screen even if I have to use the upside down tablet trick for better viewing angles. Mine does have the overheating bug though, which is primarily what causes crashes and wifi failure...
Rooting Hanspree SN14T71
I hope this helps.
I am usually a lurker and don't post but I wanted to pass this info along.
I was able to root my Hanspree SN14T71 by installing Mobogenie.
Install the Mobogenie PC App from mobogenie.com/en-us/download.html
then download the ADB drivers from here mobogenie.com/drivers-download.html
Put tablet into debugging mode.
Connect to pc then run the Mobogenie PC app click on the My Phone Icon in the upper left and from there you should be able to click the OneClick Root icon and root your SN14T71.
I have verified root access and have installed and run apps that require the tablet to be rooted.
Try at your own risk but this did work for me.
Good luck.
I've only had it for a few days actually, so I really haven't had enough time to figure out what all of it's quirks are. I actually got it to hang up on my fridge for the calender, shopping list, recipes, pandora, etc. It's attached using velcro so I can take it off if I need to.
Well I guess I'll work on getting it rooted occasionally when I feel like it, unless someone cracks it before me.
EDIT: I'll try that out wcbellaz. I'll report back if it works.
So I tried the one click root with mobogenie, and while it definitely did something, it didn't give me root access. Using the one click root, it actually moved the su from /system/xbin to /system/bin, but still doesn't give me permission to use su. Setuid attribute is there, and the root ownership is there, so theoretically, I should be able to use su. Then again, I should have been able to with the original su file, which also has setuid and root ownership.
One thing that is strange when comparing it to my rooted galaxy s3 is under the "root user is and group id status" in root checker pro, the contents are different. On the hannspad, it says the su binary isn't found or isn't operating properly. On my GS3, it says the uid and gid are both root.
When I unroot it with the one click root, it removes the su file entirely.
So I know this mobogenie app can in fact get root privileges, as it did mess with the su file. I just wish I knew how it was doing it so I can do it myself.
Masterjuggler said:
So I tried the one click root with mobogenie, and while it definitely did something, it didn't give me root access. Using the one click root, it actually moved the su from /system/xbin to /system/bin, but still doesn't give me permission to use su. Setuid attribute is there, and the root ownership is there, so theoretically, I should be able to use su. Then again, I should have been able to with the original su file, which also has setuid and root ownership.
One thing that is strange when comparing it to my rooted galaxy s3 is under the "root user is and group id status" in root checker pro, the contents are different. On the hannspad, it says the su binary isn't found or isn't operating properly. On my GS3, it says the uid and gid are both root.
When I unroot it with the one click root, it removes the su file entirely.
So I know this mobogenie app can in fact get root privileges, as it did mess with the su file. I just wish I knew how it was doing it so I can do it myself.
Click to expand...
Click to collapse
That is really odd. I just got my Hannspad in the last 3 weeks. When I would run Root Checker it said the device was not rooted. I have heard some say that the device would report as rooted but in fact was not.
If there is anything I can do to help let me know.
I am pretty much a novice at this but I had to root my Hannspad because I did have enough space in memory left for apps, and needed to install Link2SD. In my opinion the only major drawback to this device is the 1GB memory. But for the $226 that this tablet was offered on Amazon was too good a deal to pass up.
Tried Mobogenie, and it seemed to install the correct driver and the driver pack was not needed - I had already started the install on the drivers though...
Sigh...
Got root, it uses a root app that I have never heard of - Kinguser - so I mistakenly installed SuperSU, which then asked me to update the superuser binary...
I am now in the process of restarting to find out if I messed up my root access.
Sigh...
Update:
Apparently I didn't lose root, so I have installed some of my root requiring favorites to see how they work.
The oneclick seems to update the su in xbin, and they put a link to it in bin with full permissions.
I have tried three apps that successfully report gaining su permissions, Root Explorer, Titanium Backup, and GL to SD.
I want to try the move updates to system option in TB, to free up some space, but I am currently too chicken.
Sigh...
Whelp, Titanium Backup works anyway...
Update 2:
I installed SuperSU ( re-installed it actually ) and did the normal binary update. Then I uninstalled Kinguser manually by using Root Explorer to delete its apk in SYSTEM ( superuser ). Then I restarted and deleted all traces of Mobogenie and its daemon as they were slowing down my tablet, and the daemon died hard ( I can imagine that it was tied into all sorts of things ).
I have confirmed that I still have root access, and I just didn't like all that Mobogenie stuff on my tablet.
Happy now
RageAgain said:
Tried Mobogenie, and it seemed to install the correct driver and the driver pack was not needed - I had already started the install on the drivers though...
Sigh...
Got root, it uses a root app that I have never heard of - Kinguser - so I mistakenly installed SuperSU, which then asked me to update the superuser binary...
I am now in the process of restarting to find out if I messed up my root access.
Sigh...
Update:
Apparently I didn't lose root, so I have installed some of my root requiring favorites to see how they work.
The oneclick seems to update the su in xbin, and they put a link to it in bin with full permissions.
I have tried three apps that successfully report gaining su permissions, Root Explorer, Titanium Backup, and GL to SD.
I want to try the move updates to system option in TB, to free up some space, but I am currently too chicken.
Sigh...
Whelp, Titanium Backup works anyway...
Update 2:
I installed SuperSU ( re-installed it actually ) and did the normal binary update. Then I uninstalled Kinguser manually by using Root Explorer to delete its apk in SYSTEM ( superuser ). Then I restarted and deleted all traces of Mobogenie and its daemon as they were slowing down my tablet, and the daemon died hard ( I can imagine that it was tied into all sorts of things ).
I have confirmed that I still have root access, and I just didn't like all that Mobogenie stuff on my tablet.
Happy now
Click to expand...
Click to collapse
Awesome.
You lost me on the binary stuff.
In your opinion should I uninstall the Kinguser as you did and install SuperSu. there seems to be no difference to me in performance after the Mobogenie root. I really don't want anything on this tablet other than the stuff I have to have.
wcbellaz said:
Awesome.
You lost me on the binary stuff.
In your opinion should I uninstall the Kinguser as you did and install SuperSu. there seems to be no difference to me in performance after the Mobogenie root. I really don't want anything on this tablet other than the stuff I have to have.
Click to expand...
Click to collapse
The Kinguser seems to work fine, I just like using what I am used to and I couldn't find much info on Kinguser superuser app ( in english anyway ) so...
It does have a lot more configuration options than SuperSU, which could be a good thing. Your guess is as good as mine...
Hold the phone. Kinguser? I have never heard of this, nor has it been installed on my tablet by the one click root.
I did install SuperSU and tried updating the binary (without success) before trying mobogenie to see if I could get it to work. This wouldn't have screwed me over in any way, would it?
EDIT: Just to be sure, you both are running the latest OTA update, right?
Masterjuggler said:
Hold the phone. Kinguser? I have never heard of this, nor has it been installed on my tablet by the one click root.
I did install SuperSU and tried updating the binary (without success) before trying mobogenie to see if I could get it to work. This wouldn't have screwed me over in any way, would it?
EDIT: Just to be sure, you both are running the latest OTA update, right?
Click to expand...
Click to collapse
Version 1.1.4 dated 11/23/2013
I used a laptop running windows 7, and installed Mobogenie ( I also, perhaps unnecessarily, installed the adb driver pack ). I then connected my tablet and Mobogenie reported a connection - it reported the available memory both internally and on the sd card and it could see my installed applications, after which I used the one click root. The Mobogenie app and daemon were installed along with an updated su and the Kinguser superuser app.
As far as I know trying to install SuperSU previously shouldn't have any effect on the process since I did that too.
Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!
VROOT installs a app "Superuser.apk" not Kingroot
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!
abmx7 said:
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!
Click to expand...
Click to collapse
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810
pflatlyne said:
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810
Click to expand...
Click to collapse
anything i can help with getting a recovery working?
ultravioletnanokitty said:
Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!
Click to expand...
Click to collapse
Edit: was able to root with kingoroot my bad.
i need a custom recovery for it please
****EDIT****
Please see http://forum.xda-developers.com/showpost.php?p=56539897&postcount=9 for the Answer
*************
Hi all ,
I'm wanting to use NowTV (like SkyGo) on my OnePlus , however they are using a type of Root check that most root hiders cannot bypass.
Therefore I'm looking for a way to temp unroot and then root back again with ease.
just wondering if there are any tools or easy to follow guides?
thanks
Disable Superuser in SuperSU settings.
zoro25 said:
Hi all ,
I'm wanting to use NowTV (like SkyGo) on my OnePlus , however they are using a type of Root check that most root hiders cannot bypass.
Therefore I'm looking for a way to temp unroot and then root back again with ease.
just wondering if there are any tools or easy to follow guides?
thanks
Click to expand...
Click to collapse
Or if you are on a Cm nightly you can turn them off in the developer option
Disabling super user doesn't work, their detection method is unknown and they check more than the su binary.
I might try the nightlies, however I need stability.
Thanks for the responses so far
Outside of the nightly wing if you want stability use the M releases, they are designed to be more stable than the nightly branch
zoro25 said:
Disabling super user doesn't work, their detection method is unknown and they check more than the su binary.
I might try the nightlies, however I need stability.
Thanks for the responses so far
Click to expand...
Click to collapse
The problem isn't really the SuperSU as such, it's CM. They flag CM as a rooted ROM, it'll even happen if you're on stock un-rooted CM11S.
Transmitted via Bacon
I'm pretty sure that I saw an xposed module that could hide superuser completely. Might want to give that a try
skyguy126 said:
I'm pretty sure that I saw an xposed module that could hide superuser completely. Might want to give that a try
Click to expand...
Click to collapse
As per my post right above yours, it isn't SU that's the problem, it's that the ROM is CM.
Transmitted via Bacon
Timmaaa is correct and that's the info I wanted, I had tried the xposed modules but none worked and now I know why.
I'll contact sky and see if I get anywhere
****EDIT****
So it seems that Timmaaa is NOT correct as there is NO CyanogenMod or any ROM check, it's all to do with the the name of your Root App
Short Version is unroot and uninstall SU app for this to work (removing SU Binary or removing Root alone is not enough)
So we need to have a new Root app with a new AppID and name , and also the SU binary to be identified as something else for this to possibly work.
I now have NOWTV working , and it's on an Unrooted One+One with no SU App installed after running full Unroot (however my SUPro app is still installed)
Note that SUPro does nothing really and just gives extra functionality when the main SU app is installed.
Thanks for everyone help and input on this.
So it seems that you would have to
1)Full UnRoot (Which also uninstalls the main SuperUser app)
2) Watch what ever you wanted to on NowTV or SkyGO
3)Go through the Rooting process again as if it were a new device. (which will again stop NOWTV/SkyGo) from working.
Do steps 1 and 2 again to watch.
This would have to be done everytime you want to watch NowTV
zoro25 said:
Timmaaa is correct and that's the info I wanted, I had tried the xposed modules but none worked and now I know why.
I'll contact sky and see if I get anywhere
****EDIT****
So it seems that Timmaaa is NOT correct as there is NO CyanogenMod or any ROM check, it's all to do with the the name of your Root App
Short Version is unroot and uninstall SU app for this to work (removing SU Binary or removing Root alone is not enough)
So we need to have a new Root app with a new AppID and name , and also the SU binary to be identified as something else for this to possibly work.
I now have NOWTV working , and it's on an Unrooted One+One with no SU App installed after running full Unroot (however my SUPro app is still installed)
Note that SUPro does nothing really and just gives extra functionality when the main SU app is installed.
Thanks for everyone help and input on this.
So it seems that you would have to
1)Full UnRoot (Which also uninstalls the main SuperUser app)
2) Watch what ever you wanted to on NowTV or SkyGO
3)Go through the Rooting process again as if it were a new device. (which will again stop NOWTV/SkyGo) from working.
Do steps 1 and 2 again to watch.
This would have to be done everytime you want to watch NowTV
Click to expand...
Click to collapse
This is just a theory... may be wrong:
Can't you move the SuperSU app into /system/app instead of /data/app. Or does the NOWTV app have perms to check the integrity of /system also. Or can you change the app id of the SuperSU app with a simple decompile tool.
I did that while using cm11s. But still had problems trying to watch skygo. In the end I had alter my buildprop to a phone which supports skygo as at the time it didn't support oneplus one. Then full unroot etc to watch then root back to get root access again.
Ways to root your Samsung Galaxy Tab 4 7.0All of the guys on the list is tested by me and it's working
For those guys who can't root their tablet, this thread is the right place for you
1. This is the Easiest Way to Root your tablet
KingRoot App Download it here
http://www.appsandroidapk.com/apk/kingroot-v4-6-2-apk-file-for-android/
Download the app
Before installing it Go to Settings > General Tab > Security > and Enable "Unknown Sources"
Install the app and Root your phone.
You might wanting to have a SuperSU instead of kingroot's SU
Google it SuperSU Me Download the latest version or you can find it here in this link
http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Update the SUBinary
Reboot
2. KingoRoot App apk version
Download Link
https://root-apk.kingoapp.com/
Download the app
Before installing it Go to Settings > General Tab > Security > and Enable "Unknown Sources"
Set your device atleast 10 minutes before sleep due to inactivity
Install and Root your Device
Do nothing while rooting "Like tapping or bringing down the notification bar" this is why i make you set the 10minute-sleep
1st/2nd attempt might fail but on the other hand it will succeed
You might wanting to have a SuperSU instead of kingoroot's SU
Google it SuperSU Me Download the latest version or you can find the link here
http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Update the SUBinary
Reboot
3. Root Using TWRP (old)
Requirements
TWRP link is here
http://forum.xda-developers.com/attachment.php?attachmentid=3128455&d=1421957427
Important: Odin3 v1.85 Direct download Link
http://forum.xda-developers.com/attachment.php?attachmentid=581913
PC
On your pc Open Odin3 v1.85
Click PDA and choose the tar file that you've downloaded
Tick Auto Reboot and F. Reset time
Now go to your device, Boot into download mode ( Power it off wait until it vibrates then press Home,Power and Volume Down Simultaneously)
Plug your device into your Computer (Install drivers here's the link http://www.mediafire.com/download/o3exocwabcxax3b/SAMSUNG_USB_Driver.exe)/ Some Pc install drivers automatically just wait them to install or if you already install the drivers skip driver installation procedure)
Click Start if the Odin detects your phone, your phone will automatically reboot
Now Boot your phone into Recovery Mode by (Turning it off and Press Power + Home + Volume up)
It will boot into TWRP
Press Reboot > System and it will ask you if you want to get root and swipe it to install
Update SuperSU and make another reboot
You can also update your TWRP using this zip file
https://www.androidfilehost.com/?fid=24052804347818249
Now if you really can't root your tablet and you're desperate, try another version of your stock firmware, you can find your stock firmware on Google, after that do this procedure again
Done.
Other Links to make your tab Rooted
http://forum.xda-developers.com/showthread.php?t=3111934
http://forum.xda-developers.com/tab-4/help/twrp-install-twrp-root-samsung-galaxy-t3095736
Developers that has credit on all of this
@BRoy_98
@pinksworld
@gatesjunior
and sorry if i haven't mentioned the others, i dont know who to give credits
SORRY SOME OF MY ENGLISH IS REALLY BAD
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Just imagine that I just put all those threads together ahaha: )
thisisapoorusernamechoice said:
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Click to expand...
Click to collapse
I dunno if that issue is real, but no worries we have supersu me
thisisapoorusernamechoice said:
Yay another one, I think this is the fourth of this same exact thread
You might want to mention how kingroot/kingoroot send your personal data to Chinese servers and the twrp builds you linked to only work fur the SM-T230, SM-T230NU, and SM-T231, and will not work for any of the several other Tab 4 7" variants
Click to expand...
Click to collapse
I dont think that if you install first supersu me and then kingroot your tab, after root turn wifi off and use supersu me, no data sent to anyone........ anyways it doesnt send your passowords etc to china, just like browser data and few app datas.... but theres no way to get passwords.... all are crypted or hidden well in smali
thelous said:
I dont think that if you install first supersu me and then kingroot your tab, after root turn wifi off and use supersu me, no data sent to anyone........ anyways it doesnt send your passowords etc to china, just like browser data and few app datas.... but theres no way to get passwords.... all are crypted or hidden well in smali
Click to expand...
Click to collapse
I wouldn't be sure about that. If you type in your password, once rooted, anything can easily capture the keyboard input and log it or send it out. Let me elaborate. It's like the guys who say, "Hey I have a firewall installed so it cannot communicate out." Yeah, o.k., so all the firewalls do is manage IPTABLES, so if I am an application and have root access, I can do what I want to avoid your firewall rules quite easily. Just a thought.
Hmm, updating the binary will remove the @#$%&* thing , we're just going to use the app to root our phone, and I guess wiping cache and dalvik is necessary
BTW tab 4 is best for gaming because of it looks and size but due to a stupid Samsung company, 1.2ghz + vivante gc1000 expect lagging, I hope some kind hearted will make a custom kernel for overclocking this tab.
BTW There's no Tex plugin on gltools, installing default will not work, so you have to find a cracked version of gltools, well if you do that... R.I.P expect force closes
gatesjunior said:
I wouldn't be sure about that. If you type in your password, once rooted, anything can easily capture the keyboard input and log it or send it out. Let me elaborate. It's like the guys who say, "Hey I have a firewall installed so it cannot communicate out." Yeah, o.k., so all the firewalls do is manage IPTABLES, so if I am an application and have root access, I can do what I want to avoid your firewall rules quite easily. Just a thought.
Click to expand...
Click to collapse
Well i didnt say anything about firewalls i was daying if you manually disable wifi and use king root, it wont be able to connect anywhere to send any data.... also you can search by date and time files made during root session and remove everything to prevent any keyloger to work
Have ODIN and a stock image ready!!!
Be careful with this root process! The sm-t237p 5.1.1 OH7 boot loops and won't hold the root or Philz recovery... Yet!:cyclops:
thelous said:
Well i didnt say anything about firewalls i was daying if you manually disable wifi and use king root, it wont be able to connect anywhere to send any data.... also you can search by date and time files made during root session and remove everything to prevent any keyloger to work
Click to expand...
Click to collapse
No. I can easily change the file and date stamp to match any given system file you already have so that it is not easy to find. Also, Kingroot will not run correctly and root your device properly if it cannot contact it's servers to download the proper exploit for your device. Now, if you are talking about disabling wifi only so that Kingroot cannot contact it's servers after you are rooted, well, if you use any data what so ever, it can use that same data connection. As an example, I have to have data of some type to login to my bank site, etc..
SM-T237P Specific maybe others with PhilZ recovery...
Root Success! Check this out... http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
gatesjunior said:
No. I can easily change the file and date stamp to match any given system file you already have so that it is not easy to find. Also, Kingroot will not run correctly and root your device properly if it cannot contact it's servers to download the proper exploit for your device. Now, if you are talking about disabling wifi only so that Kingroot cannot contact it's servers after you are rooted, well, if you use any data what so ever, it can use that same data connection. As an example, I have to have data of some type to login to my bank site, etc..
Click to expand...
Click to collapse
Well, atleast my bank account cant be logged with different ip and if its tried i recice message wheres code that you need write to bank website to access account.... however i havent lodt any accounts yet after rooting with kingroot, it has so manynusers that they cant check all information they recive, just like facebook and whatsapp... (they're spying watnu do but they have too many users so it would take like unlimited time to check all accounts and keybindings thru.....
K94U said:
Root Success! Check this out... http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
Click to expand...
Click to collapse
You can use any kind of cwm to flash a zip file that can root your device, This was an alternative way, just find a cwm to flash hehe
Siegharf said:
You can use any kind of cwm to flash a zip file that can root your device, This was an alternative way, just find a cwm to flash hehe
Click to expand...
Click to collapse
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
K94U said:
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
Click to expand...
Click to collapse
There's kies or custom ota flashing
K94U said:
Flashing recovery trips KNOX (no warranty or OTA updates) and the other method sometimes doesn't... Also, the recovery/zip method stopped working on lollipop and marshmallow with the older SuperSU builds but... Chainfire has a new BETA SuperSU 2.6X that is a systemless root and now working on the newer Android builds using the recovery/zip method. This seems to work for mostly ALL Samsung and Nexus devices... Read about it here:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
I restored my nandroid backup in recovery just to try this on my sm-t237p lollipop and it worked the first time!!! All apps get root access OK except es file explorer(now bloatware anyway)... You might need to install busybox for things to work... :good: :laugh:
Click to expand...
Click to collapse
235 LTE 5.1.1 rooted as well
http://forum.xda-developers.com/showpost.php?p=64255121&postcount=1
(not spamming in case anyone got the idea)