Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...
Go into rom manager. Download SU and flash it in clockwork. Should fix ya.
Sent from my ADR6400L using XDA Premium App
ethanwinkley said:
Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...
Click to expand...
Click to collapse
You could search market for busybox and install busybox and install busybox 1.18.3 then try
Just click Problems? in the bottom right of Titanium and let it install busybox for you. I was able to do that and restore all my apps.
Seems like you solved it for you, but for future reference for others, if you're having issues with Titanium only, it could be a the busybox problem, but if other root apps give issues (like Root Explorer can't mount /system as r/w), then the issue is with su or SuperUser not being installed properly.
I had to reboot twice after rooting before SuperUser apk got the notification requests to allow Titanium and RE to get su rights. After that, no problems.
In a nutshell, if you're not getting the SuperUser pop-up request on apps the first time you run them, your su isn't working right yet.
Delete please.
I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
[Solved]: Seems it was a result of trying to upgrade Superuser that I lost root. See the last post below and the solution Almighty1 offers. It worked and I have root back......
Sent from my Xoom using XDA Premium App
tangiers said:
I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
There is a problem with the latest recovery version in Rom Manager. The recovery from solarnz is probably not at fault, but maybe the interaction of the two. You wil lneed someone with more knowledge than me to help you get root back, but this issue really needs attention. There are several updates to apps that seem to be breaking our Xooms, and there should be pinned warnings or the developers should be making everyone aware of these conflicts as soon as they find out. I had problems and I'm sure a lot of other folks have have problems with these incompatible app updates as well.
Thanks for that. It almost seems like Superuser is "degrading" in the sense that I had a number of apps reflected in the Superuser app as having been granted root (but not Rom Manager). However, I couldn't add new apps to it. And when I cleared Superuser data and reinstalled it, none of the apps that required root (and which had worked before) would work.
I also think that the writing of a 0 byte zip update file by the Superuser app indicates a problem.
I suspect the solution may lie with fastboot and re-pushing Superuser and CHMOD(?) file permissions but like you, I am nervous to play with these sort of things. My Xoom is working and until I have the need to change the ROM, root doesn't matter to me....
after reading this I checked and also had lost root. I had not checked after after flashing 4.0 in rom manger. Superuser was still there but my apps did not have access. I tried flash a new recovery, reflashing Tiamat nether worked. Anyway from adb
adb remount
adb push su /system/bin/
adb shell
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app/
I then rebooted and had root... updated Superuser as I had an older one in my platform-tools and all is well I then flashed the lastest recovery in rom manger and still have root.
Hope this helps
Thanks. I will give it a try this evening when I get back from work.
Also found this: http://forum.xda-developers.com/showpost.php?p=14643716&postcount=340 which seems similar to your solution.
This is why I hate CWR. I wish we had Amon RA recovery.
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...
Hello everyone!
I would like to ask you something and i REALLY HOPE someone will be able to help me out.
I have a samsung s5 sm-g900f with Android 6.0.1 and i'm trying to root it.
Actually it was supposed to be rooted when i got it -it's my bf's phone. And...aaam i don't know if it's called "rooted" when it just have custom recovery and rom? I just call it that way-. Yesterday i installed root checker and Super SU and the Super SU keeps saying that "There is no SU binary installed and SuperSU cannot install it" and that if i have Android 5 i should re root manually and stuff.
I have tried like everything i have found on the net since yesterday, flashing with Odin, changing recovery from twrp to cwm, and all the time the steps are made by letter, all seems fine, i see the red pirate android after the recovery reboot and all that, have tried to install the UPDATE-zip and the BETA-zip and all i could find. I tried to install Kingroot but i couldn't figure out how. My recovery nor Odin can see the file to install it and then i try to do it manually, like all apps, it says could not be installed. :crying:
I got really tired and i cave in to ask for help here. I hope the post is in the right place and if it's not please move it where it should be!
Thank you in advance!
CloeNi said:
Hello everyone!
I would like to ask you something and i REALLY HOPE someone will be able to help me out.
I have a samsung s5 sm-g900f with Android 6.0.1 and i'm trying to root it.
Actually it was supposed to be rooted when i got it -it's my bf's phone. And...aaam i don't know if it's called "rooted" when it just have custom recovery and rom? I just call it that way-. Yesterday i installed root checker and Super SU and the Super SU keeps saying that "There is no SU binary installed and SuperSU cannot install it" and that if i have Android 5 i should re root manually and stuff.
I have tried like everything i have found on the net since yesterday, flashing with Odin, changing recovery from twrp to cwm, and all the time the steps are made by letter, all seems fine, i see the red pirate android after the recovery reboot and all that, have tried to install the UPDATE-zip and the BETA-zip and all i could find. I tried to install Kingroot but i couldn't figure out how. My recovery nor Odin can see the file to install it and then i try to do it manually, like all apps, it says could not be installed. :crying:
I got really tired and i cave in to ask for help here. I hope the post is in the right place and if it's not please move it where it should be! Thank you in advance!
Click to expand...
Click to collapse
Since you can flash custom recovery then your bootloader is already unlocked so....
Do a search for "flashing SuperSU.zip Galaxy S5" or you might need to search for "flashing SuperSU.zip in systemless mode galaxy s5". Flashing one of those should give you root and su binaries, after flashing, boot the device and open the SuperSU app and update the su binaries then reboot the device. Then after rebooting, you need to go to system settings>developer options>root access and set it to "apps and adb", then install a file manager that has a root explorer such as ES File Explorer, then open it, tap the menu button, go to the "TOOLS" tab, find "Root Explorer" and turn it on, then when you see the next menu, tap "Mount R/W", then set all listed partitions to "rw".
If you can access your SELinux profile, make sure it's set to "permissive" mode.
If you can get all of that set then you'll have access to modify and control pretty much anything you want about the device.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
thank you!!!
i wont be able to try it for a few days but i'll try it as soon as i can and give you feedback on this!
So i'm trying to follow your instructions right now. I guess it's ok if i install recovery upon recovery and SU upon SU without first removing the "faulty" one?
Cause i have done the first steps a lot these days
edit: i flashed again aaaaaand nothing new happened. The SU binary is nowhere to be found :/
some say it could be a problem of the cable or the computer?
Should i try from a different pc and cable? I do not really understand it but i'll give it a try later
edit 2: i retried from another pc and another usb cable, the same happens. Does not install the SU through the recovery
I installed the SuperSU (actually enebled it again and updated it) from playstore and opened it and it says the sme thing again. Can't find su binaries and stuff.
What should i do? Is format a solution or can avoid it?