Related
There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary
Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.
I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...
Try this fix.
To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.
Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium
Already answered, see post above.
Deleted
Sent from my GT-P6800 using xda premium
Too late for me to try it, but thanks the same
ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!
Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.
Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.
Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though
No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.
I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.
DISCLAIMER: I am NOT RESPONSIBLE on anything that will happen on your device such as getting bricked or malfunctioning. I only posted this little trick I found out to help others who are also in the same boat. This method MAY or MAY NOT WORK on your device, so proceed at your own risk.
=====================================
Maybe some of you have not seen any Superuser prompt that appears whenever you run apps that needs root (example are Link2SD, Titanium Backup) and etc. Out of frustration last night, I tried to find a way to fix this and I have indeed found it.
But before that here are some of the prerequisites needed:
-Phone/Tablet must be ROOTED
-Has access to system using File Explorers such as Mi(UI) File Explorer, Root Explorer and other explorer that DO NOT prompts Superuser. What I mean here is that you can see /data, /mnt, /etc folders and the like.
..and here are the little steps in fixing it:
1. Download and install BusyBox from Google Play Store.
2. Open BusyBox, select 1.20.2.
3. Click install, and wait for it and it's done.
4. After BusyBox has been installed, download SuperSU from Play Store.
5. Install and let it load.
6. After loading, press YES when asked to update SU Binary.
7. When it's done, press back and try apps that needs root like Titanium Backup.
And there, notification prompt would appear again!
NOTE: UNINSTALL, take note UNINSTALL previous Superuser app through Root Uninstaller. Main reason why that should be uninstalled so that there would be no conflicts with the SU app.
OPTIONAL: you MAY UNINSTALL BusyBox app but I recommend not so to avoid any problems.
I have also applied this method to my tablet that's already rooted but doesn't have Superuser app yet. A simple press of thanks is highly appreciated. :3
hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.
ellynepain said:
hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.
Click to expand...
Click to collapse
It's not working for me neither, i can't fix this superuse thing
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
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!!