Hello,
I've an installed clockworkmod recovery v2.5.1.2.
when I'm trying to install the new one from ROM Manager, I get the following message:
"an error occurred while trying to run privileged commands". any ideas?
p.s. my DHD is rooted, but I've done factory reset a week ago, does it means it has to be rooted again?
You should root again.
Sent from my Desire HD using Tapatalk
If jkoljo's reply didn't work????
Did you give SU rights to SuperUser, could also try "forget" (Edit: within SuperUser), run ROM Manager again and "allow" SU rights when prompted.
Related
Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Are you s-off? If so not sure what the problem is. If you're not s-off, that's your problem
Sent from my HTC Desire using XDA App
pspuser007 said:
Hello,
I have stock rooted rom 2.29.405.5 (with Apps2SD).
Recently superuser app has been updated to the newest version.
After that I am getting a notification about "su binary not updated".
Clicked on it and got the "Updating Binary" which informs me about an update of the su binary.
The problem is that when I click "update" the whole procedure fails when it tries this "Remounting /system as rw".
What is wrong?
Thank you!
Click to expand...
Click to collapse
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this zip
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
pspuser007 said:
Thank you both for your replies.
I am still s-on but planning to change that.
But for now, I copy the zip to the sd card. Reboot into recovery and use flash zip from sd? Are there any other things I have to do before flashing the zip?
Click to expand...
Click to collapse
If u updated super user through the market, uninstall the update..after that flash the zip in recovery
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
pspuser007 said:
I haven't done any actions to update it, more likely, it was automatically updated via market.
Unistall the update? How? If I unistall something, this would be the application itself (I mean I only know unistalling applications - is there any way to unistall updates?)
Click to expand...
Click to collapse
u never looked in settings/applications?
super user i guess is a system app (like gmails, gmaps, gtalk, etc)..so u can't uninstall those applications..but u can uninstall updates for those applications..mean for system apps u can only uninstall updates
so go in settings/applications, select super user app and u should see uninstall updates, if yes do uninstall updates, if not then its ok and flash the zip
do a nandroid backup in recovery before touch something, just to be sure
I hadn't checked system applications so far.
Unistalled the update, did a nandroid backup and flashed the zip!
Everything OK now!
Thanks a lot for your help!
Many many thanks!!!
what does the zip need to be named?
Does the zip need to be named update or does it stayed named like it is?
Name it whatever makes you happy. Remember its whats on the inside that counts.
Sent from my PG86100 using XDA Premium App
I'm getting the same warning message with my market updated su, when I open Titanium Backup but it hasn't affected anything. I just ignore the message and everything still seems to work. Am I missing something?
Problem Updating
andQlimax said:
the problem is that without s-off, an app cant write on /system while the phone is booted
u have 2 options:
-uninstall the super user update, and continue to use the old one
-install the super user update (apk + su binary) flashing from the recovery this "goo-inside.me/superuser/su-3.0-efgh-signed.zip"
Click to expand...
Click to collapse
I have uninstalled SU and installed the super user update and I get the following error when I update the binary updater:
"Failed to find currently installed su binary. Update cannot continue"
UPDATE:
I downloaded and installed the binary file (su-3.0-bin-efgh-signed.zip) from androidsu.com and now get FC error "The application Superuser has stopped unexpectedly. Please try again"
Thanks for your help.
When this issue occurred for I found that just by simply reflashing the SU zip in recovery and then running the update fix it seemed to fix it. I think for me it may have had to do with using an outdated version though.
su binary update failed..
Hi, I'm using CyanogenMod 7.1.0 RLS3 for Kaiser.. Today I got a "su binary outdated" I try to update it.. Going ok until "Moving su to it's final location - Fail" how to solve this? guide me please.. I'm newbie..
Hi, I had rooted my Garmin-Asus A50 about a year ago with help from these fora. Also installed Titanium backup and other related apps.
My question: upon waking thisr morning and waking the phone, a message said "SU binary outdated - tap to update" I let it update without thinking -but immediately had doubts about some trojan doing this to gain access.
So I switched off the phone and am trying to gather some info here and on WP. From your post I see that this 'update' message may be legit - or am I wrong?
Thanks ffor any further tips.
.-.
I have rooted my Gnex 4.2.2 after receiving the OTA from VZ. I have CWM 5.5.2.3 and SuperUser Elite 3.1.3 installed. Running SU it doesn't complain about anything. As far as I can tell it thinks things are fine. But trying to run Root Explorer or Titanium backup both complain about not being able to get root access. And opening a terminal and attempting cd /root fails due to permissions. I went into CMW and found it didn't think it was installed so I tried it again and it fails while flashing.
Booting into recovery it shows CMW image 6.0.2.3 which matches the image I pushed via fastboot flash recovery. I tried the "fix permissions" option but it didn't make any difference.
It seems like it isn't really rooted even though I went through the steps. I've done this before successfully on previous Android versions.
Maybe the old su.zip I am using no longer works?
I uninstalled/reinstalled Root Explorer, Titanium Backup, and CMW apps. I could not find a way to uninstall the SU app -- very weird... Hmm.....
Use a new su app and make sure the updated binaries are installed.
Further research showed attempting an update of SU indicated it isn't rooted. Noticed, also, that uninstall of SU isn't an option. Hmmm...
AdvApp said:
I have rooted my Gnex 4.2.2 after receiving the OTA from VZ. I have CWM 5.5.2.3 and SuperUser Elite 3.1.3 installed. Running SU it doesn't complain about anything. As far as I can tell it thinks things are fine. But trying to run Root Explorer or Titanium backup both complain about not being able to get root access. And opening a terminal and attempting cd /root fails due to permissions. I went into CMW and found it didn't think it was installed so I tried it again and it fails while flashing.
Booting into recovery it shows CMW image 6.0.2.3 which matches the image I pushed via fastboot flash recovery. I tried the "fix permissions" option but it didn't make any difference.
It seems like it isn't really rooted even though I went through the steps. I've done this before successfully on previous Android versions.
Maybe the old su.zip I am using no longer works?
I uninstalled/reinstalled Root Explorer, Titanium Backup, and CMW apps. I could not find a way to uninstall the SU app -- very weird... Hmm.....
Click to expand...
Click to collapse
Update CWM to 6.0.2.3 (http://www.clockworkmod.com/rommanager)
Flash SuperSU to 1.25 (http://forum.xda-developers.com/showthread.php?t=1538053)
Hi, got a problem which I cannot solve and I do not find a solution.. So I have Android Revolution HD 9.0 installed, and few days ago Superuser updated itself. It's the one from Clockworkmod. Now it says that su binary needs to be updated, but the install always fails and says to send a log. Same thing happens if I select the "Recovery install".
Where is this log, and what I could do? I am using 4EXT Recovery.
910263 said:
Hi, got a problem which I cannot solve and I do not find a solution.. So I have Android Revolution HD 9.0 installed, and few days ago Superuser updated itself. It's the one from Clockworkmod. Now it says that su binary needs to be updated, but the install always fails and says to send a log. Same thing happens if I select the "Recovery install".
Where is this log, and what I could do? I am using 4EXT Recovery.
Click to expand...
Click to collapse
Yeah I have the same problem.
Hey there
Have you tried re-flashing the ROM? Is the superuser update causing any issues (ie not giving out root access?)
You can always try using SuperSU (alternative to SuoerUser) although you'll have to look in the SuoerUser settings in order to find the option to change SU granting programs
- Sent from Guy's Super Duper S3
My phone is a Huawei u8160 (AKA Vodafone 858) and I rooted it a long time ago with z4root and have had no problems eversince.... until recently when my mate got hold of my phone and accidently flashed an experimental/beta (possibly a binary for x86 systems) SU binary through CWM recovery. I thought I could fix this quite easily by using z4root to uninstall root and then do a fresh reinstall, but it would force close on me after a few seconds. I tried this method with both temporary and permanent root options but nothing worked. The button that pops up saying ''unroot'' wasn't there even though there is still a SU file in /system/xbin as it showed in Rom toolbox. I soon realised that the version of android i was running on my custom rom was not compatible with z4root, so i searched for how to root android version 2.3.9 pro. I dont know the name for that version and it must have been a bit of a flop because google didnt know it either. I dont know how akiro-E (the developer that cooked up the rom) got his hands on version 2.3.9 pro but i recommend to other devs reading this to not use it as there is not much compatibility.
Anyway, i found this apk made by chainsDD called gingerbreak and decided to give it a go. It said that it needed debugging on and that it might take a while, so i did that and pressed the root button. I left it to do its business, but 15 minutes later it was still trying to run the exploit so I stopped and removed it. When i got home later on i searched up how to root any phone and it came up with the pc program 'superoneclick'. I got it, opened it and clicked unroot. It did its thing but failed to remove su and the superuser app like it was meant to. So then i clicked on root and shell root but it did not reinstall properly and got the same error as in unroot error. I did all the steps multiple times but it still wouldnt remove/replace su from the xbin folder. I then reinstalled superuser 3.1.3 and tried using the binary updater on there. I noticed that the su installed was called 'legacy'. The updater was having a spaz and didnt want to update so i tried manually removing su with the root explorer in rom toolbox butvrealised that you needed root (a working one) to do that. Then i found an app on my sd called root cleaner. I tried quick and full cleaning but to no results except for a force close multiple times. I tried to fi the foce close issue by running the script for this in rom toolbox but you need root (surprise surprise) Then i tried flashing cwm recovery through fastboot as i have done lots of succesful times before. It flashed after putting my phone in download/debug mode (power and volume down) but i cant boot to it as you need proper root rights to do that.
I am going to use total commander to check if the permissions are set to 644 for the su binary, if not ill attempt to change them.
I know this a long desciption and technical question but does anyone know any ways to delete the retarded root from my phone and help me restore root as normal? This is a question for the more experienced users and devs on this forum but any help will be appreciated, cheers.
If you've got recovery, you can install one of these zips in recovery mode.
Google "superuser 3.1.3 arm signed zip" and click the first link that comes up - the androidsu one. Then download the superuser zip package that suits your device to your phones internal storage, reboot into recovery, install the zip and there you go! Your root is fixed.
Sent from my LG-E400 using xda app-developers app
Thanks
@odigITECH thanks for the help. I fixed the problem using your method. . . kind of. I flashed recovery via fastboot and then just flashed another rom from my sd card via cwm after I rebooted. Thanks for the help anyway, much appreciated!
No probs
Sent from my LG-E400 using xda app-developers app
I've been toying around with my new Verizon HTC One (m8) and decided to permroot earlier today (I've had temproot via weaksauce for a month). This took me forever because the only s-off and bootloader unlocker that would work (after hours of trying firewater and HTCdev) was Sunshine. I eventually paid for it and tried to root. I installed CWM at first but didn't realize that Supersu had to be present on my sd-card, so I rebooted. I then flashed TWRP over CWM and tried to root with it instead. Unfortunately, I had downloaded Supersu off the Play Store and (of course) didn't achieve root from the bootloader. That was a few hours ago.
Now I'm stuck with TWRP and no matter what I do, I cannot figure out how to root. I've flashed 3 different versions of Supersu from recovery and none of the zips I install offer me the option to root. I've tried to flash Supersu through adb sideload. I've even tried using ROM manager to reboot and install a copy of Supersu downloaded off my phone's Chrome (probably didn't work because I'm not rooted - it tells me "an error occurred while trying to run privileged commands").
I was under the impression that after installing the Supersu zip from recovery, you would be asked to root either directly after installation or upon rebooting. However, when I reboot, TWRP warns me that "There is no OS installed, are you sure you wish to reboot?" From what I've read, that normally indicates a soft-brick, but my phone is definitely not bricked (yet).
How can I flash Supersu in a way that gives me root?
I'm fairly competent with adb, but nowhere on the internet have I found a problem even remotely similar to mine....
Are you able to boot into twrp and which version do you have? Twrp will automatically ask if you want to install the su binary the first time you reboot from within twrp.
When you reboot you should see the supersu app. All you need do is update it via play store.
harper3663 said:
I've been toying around with my new Verizon HTC One (m8) and decided to permroot earlier today (I've had temproot via weaksauce for a month). This took me forever because the only s-off and bootloader unlocker that would work (after hours of trying
I'm fairly competent with adb, but nowhere on the internet have I found a problem even remotely similar to mine....
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2265618 this is for m7 but works for m8 as well like a charm!
Jyotirdeb said:
Read this: http://forum.xda-developers.com/showthread.php?t=2265618 this is for m7 but works for m8 as well like a charm!
Click to expand...
Click to collapse
I downloaded and installed the Root Kit from recovery. It said install successful, but below that it said "Unable to mount /system." When I rebooted, I still didn't have root and Supersu hadn't downloaded. Do I need to do an ruu and just retry everything?
ashyx said:
Are you able to boot into twrp and which version do you have? Twrp will automatically ask if you want to install the su binary the first time you reboot from within twrp.
When you reboot you should see the supersu app. All you need do is update it via play store.
Click to expand...
Click to collapse
I can boot into twrp, and it's the most recent version from their website (for the Verizon HTC One). For some reason, it didn't ask me to install the su binary the first time I rebooted, and now I don't know how to do it.
harper3663 said:
I downloaded and installed the Root Kit from recovery. It said install successful, but below that it said "Unable to mount /system." When I rebooted, I still didn't have root and Supersu hadn't downloaded. Do I need to do an ruu and just retry everything?
Click to expand...
Click to collapse
Thats why u shouldnt use toolkit.Try an ruu then follow the link i have posted