Database Info

ClockworkMod not working?

Okay so I updated my Nexus S to 2.3.2 through ROM Manager, and when I tried to flash the Trinity kernel after I updated I ROM Manager said it was gonna shut down my phone to flash it, but it just sat there. Then I tried different functions in ROM manager, but I got "Error running privileged commands" (or something like that) I then checked Superuser and ROM Manager was simply not in the list. It did not say that it was declining access, but it also didn't say it was allowing. I decided that I would restore to my backup, but when I went into the recovery it was not the ClockworkMod recovery. It was the stock recovery, but I didn't have any options. At that point I decided to uninstall ROM Manager and install it again hoping it would ask for privileges. It did not.
Any ideas?

open ROM manager and flash clockwork recovery (the first thing on the menu)

When I try to do that I get "An error occurred while attempting to run privileged commands!"

Taquitoz said:
When I try to do that I get "An error occurred while attempting to run privileged commands!"
Click to expand...
Click to collapse
Sounds like you're not rooted.
If you're not rooted, the only way you're going to get into clockwork is to use fastboot.

I'm pretty sure that I'm rooted. I was running on Trinity prior to the update. And I still have Superuser.

Superuser apk doesn't necessarily mean you're still rooted with proper permissions.
At least check your /system/bin directory for the su binary (different than the superuser app) and that it has executable permissions.
You could also open a terminal app on the phone and just type su and hit return.

Okay so I downloaded a terminal emulator and typed 'su'
I got permission denied. Does this mean I have to root my phone again? If I will will I have to delete all data?

Taquitoz said:
Okay so I downloaded a terminal emulator and typed 'su'
I got permission denied. Does this mean I have to root my phone again? If I will will I have to delete all data?
Click to expand...
Click to collapse
Yes, it means you must root again.
No, you won't lose everything again if you follow these instructions: http://forum.xda-developers.com/showthread.php?t=931865
Good luck.
edit: you just need to get into clockwork (via fastboot) and then re-run the su update zip file, it will reinstall the su binary and fix any bad permissions.

Sorry for asking for the specifics, but could you explain how one could go about doing that?

Boot into fastboot.
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Boot to recovery.
Mount system.
Flash a zip from the SD card and select the superuser .zip.

Taquitoz said:
Sorry for asking for the specifics, but could you explain how one could go about doing that?
Click to expand...
Click to collapse
The link I provided gives step-by-step instructions on how to do it, and links to more complicated steps if you're not too sure about them.
The post just above this does give the basic steps, though.

I lost root- perhaps thru flashing new recovery?

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.

[Q] Rooted 2.3.4 Mesmerize; Now what...?

I'll try to keep this as short and simple as possible:
I am a total newb to the touchscreen, smart-phone, I just got a USCC Samsung Mesmerize SCH-i500, came installed w/ 2.3.4 Gingerbread & I just had to reflash it w/ USCC EH09 root using Odin 3 v1.85, now, everything I have "hacked" in the past (PSP (both fat & slim), iPod Touch, etc) I've always had to use step-by-step instructions (I am not a dev & know absolutely nothing about programming) & the same applies here.
So, it has root access & BusyBox (I don't even know what that is) installed, so my question is what was the point?
What exactly can/should I do from here? Any suggestions?

well, with a rooted android device you can
*remove bloatware (you're wasting your root if you don't do this)
*system-wide adblock (my personal fav)
*change boot animations
*flash custom ROM
*free wifi tethering
*overclock the CPU
and more!

Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....

Xeno Templar said:
Thank you for the answer, I'll look into these things but on a side note: my su app keeps saying that theres an update available for my su binary & every time I tap update it goes through the process & less than half-way through it pops up a message saying: "This updater cannot update the su binary on phones that have some kind of write protection on the system partition like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM Manager."
I have tried to use ROM Manager, I even bought the Premium version, either way it gives me the same message, even after doing the Fix Permissions option, is there a way to manually allow su access to the files it needs to overwrite/update?
Oh, and, yes, I have allowed it when su asked, so now I'm at a loss....
Click to expand...
Click to collapse
I had the same issue today, couldn't update SU.
but after I had updated the terminal emulator, I was able to update SU.

Fixed the Problem with updating SU Binary
Recently updated my device with a new rom and was unpleasantly surprised to not be able to update my SU binary with either the application itself or CWM. I am not sure that this is the best way to handle the problem, but I found a solution that worked for me.
1. Open "System/XBin" in RootExplorer (or a similar app)
2. Mount the drive as R/W using the button up at the top left
3. Open the superuser app and update the binary from within the app
4. There may be an error in the log about the device not being able to remount the drive properly, but the update WILL occur.
5. Use RootExplorer to open the directory again and mount as R/O.
I hope this helps!

[Resolved] [Q]Need Help with Xperia Miro lost root access

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.

Help with Samsung s5 root!

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?