Related
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.
buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!
buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge
I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does it...
Hi All,
I have screwed up my android which was perfectly fine with a perfect root. Please help me to restore the root access !!!
Here is my problem description:
I have a Sony Xperia Miro which was perfectly rooted.
Model : ST23i
Android : 4.0.4 ICS
Build : 11.0.A.5.5
The root verification using app 'root checker basic' was successful.
Now I had few of my company apps and bank apps which wouldn't work in rooted device. But I never wished to lose my root status. So I was searching for the ways to hide root access from these apps. I even came across apps exclusively built for this purpose (hidemyroot/OTA root keeper) But due to some bad comments about these apps, I decided to try manually
The idea was to fool the apps when checking the root access.
At first I renamed the super user apps at the location /system/apps. to some invalid file(super.txt)
This did the trick for couple of apps which weren't working before in my mobile. However couple of apps were still failing.
The next thing I did was renaming .su to ku in the below location /system/bin/.ext
Then I verified Root Checker Status, still it displayed "u have root access"
Then I went to /system/xbin and renamed the following.
.su to ku
.busybox to busyboxk
.dexdump to dexdumpk
Then I tried Root Checker Basic again. And got the message "device don't have proper root"
But still my apps were not working. Then I did the most foolish thing which was restarting the device.
BAM.. !!!! I lost my root access permanently. Now I don't have superuser app. And I m not able to use 'Root explorer', to rename back the files to its original state.!!! And most ironic thing is my company app still saying I have root access. I tried after deleting its cache and data. The result was same !!
How can I restore my root access ? Please help
one update
Since I renamed the superuser and superSu applications, I couldn't use them.
Today I installed both of them using package installer.
But they doesn't seem to work as they can't find su binary installed
See the attached
appviz said:
See the attached
Click to expand...
Click to collapse
Do you have a Custom Recovery setup and if so did you make a backup after root?.
keifus.rahn said:
Do you have a Custom Recovery setup and if so did you make a backup after root?.
Click to expand...
Click to collapse
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
appviz said:
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
Click to expand...
Click to collapse
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your device. The same thing happend to me awhile back :/ If you want to save your apps use titanium back up or app backup & restore and add a custom recovery like cwmr so if this happens agen you wont have to reroot. if you are still having problems with your apps for work boot your phone into recovery and go to advanced then fix permisions if you have any other questions or any problems just let me know.
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
keifus.rahn said:
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
Click to expand...
Click to collapse
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
appviz said:
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
Click to expand...
Click to collapse
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
keifus.rahn said:
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
Click to expand...
Click to collapse
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
appviz said:
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
Click to expand...
Click to collapse
That's Awesome :highfive: I'm glad the hear that you got everything working correctly and with your company apps too. :victory:
Thank you for sharing with me and everyone. You never know if some one out there is having the same problem and this could really help them out one day.
Hi guys android newbie here! My friend rooted my Nexus 5 and it was working fine for a couple of weeks. Yesterday I tried to open SuperSU and it didn't work! Other apps that required root didn't work either.
I have been looking around and it seems OTA updates may have screwed up my root. Every time I try to open SuperSU it says: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" If you just upgraded to Android 4.3 (I have 4.4), you need to manual re-root. Consult the relevant forums for your device!" I have used root checker by joeykrim and it says "Sorry! this device does not have proper root access" (to confirm my root is busted).
My question is, is there any way to fix this without re-rooting? If I have to re-root, can I just directly re-root it again using something like Wugs rootkit?
Thank you very much in advance!
Just flash the newest version of supersu and you'll be good to go..... http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
simms22 said:
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
Click to expand...
Click to collapse
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
seyba said:
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
Click to expand...
Click to collapse
cant even get into it?
Yea it says there is no SU binary installed. I think I've lost root access
seyba said:
Yea it says there is no SU binary installed. I think I've lost root access
Click to expand...
Click to collapse
flash this with your custom recovery, its the latest supersu http://download.chainfire.eu/supersu
bodooo said:
Just flash the newest version of supersu and you'll be good to go.....
Click to expand...
Click to collapse
I can install/update to v1.8! I just can't open it. Gives me a "SU binary not installed" when I do!
Did you install/update from the playstore or flashed the new update?
simms22 said:
flash this with your custom recovery, its the latest supersu
Click to expand...
Click to collapse
Sorry if this is a stupid question .. but how/ do I flash this or what program do i use?
My friend helped me root it so i have no idea on how to do this @@ Very sorry.
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
bodooo said:
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
Click to expand...
Click to collapse
Ok so I can't open flashify either. It also says I have lost root access and my superuser is busted. I have attached a screenshot!
http://i42.tinypic.com/2mgw0v6.png
Of course, you don't have root access, silly me lol Well guess we'll have to do it the hard way (it's not really that complicated) ok read carefully. Power off your phone, afterward hold the power and volume down buttons which should get you into the bootloader, cycle trough the options with the volume buttons and when you see recovery mode select it with the power button, now depending on which Recovery you have you'll have to choose the option that says install or install from sd card, again, depending on which one you have this will be slightly different. After doing i believe the paths will be the same, chose 0/ then look for the download/ folder which you should have that supersu.zip file, if you're using twrp recover it should be touch screen and you simply select it and swipe to install, if you're using cwm (which i do) you'' have to scroll with the volume buttons and select the file with the power button to install. I hope I was as clear as i could be, good luck
after going into recovery mode, there is just a android robot with his chest open and an exclamation mark! can't proceed after that.
Ouhhh you don't have a recovery then, do you have adb or any kind of toolkit?
I have wugs toolkit. but every time i try to do anything at all on it. It says ADB device not found? That seems to be preventing me from doing anything as well.
Do you have the adb drivers installed or/and usb debug turned on in developer settings?
how/where do i install adb drivers? I have not done so, and i doubt my friend did it when he rooted.
I do turn on usb debugging when i tried to unroot/root on wugs toolkit
In wugs toolkit it has a walk-through on how to do so, i suggest you use the RAW drivers option
I must be blind to not have seen this before. Thank you very much for your help I'll let you know how it goes!
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!!
Hi guys. I need your help.
I'm using a rooted Huawei G730-T00 with built number V100R001CHNC01B132.
I have supersu installed but it works even okay without it. I don't remember how I rooted it.
The problems are
1- I can't update supersu binary. It shows me two options, Normal and CWM Or TRWM mode, which are not installed. As soon as I press normal mode, my phone restarts. It still asks for update
2- After installing the Busybox apk, it says "Busybox not installed." whenever I choose Normal or smart install again my phone restarts and still says Busybox not installed.
3- when I mount my system to read write my phone restarts and when It starts it goes back to read only. I tried es explorer and Terminal emulator.
4- and at last but not least, whenever I try to open freedom, my phone restarts. I can't make an inapp purchase.
I tried unrooting and rerooting but no of these seems to work at all.
I really need your help. Sorry for my English. I can't help it.
Thank you,