I occasionally get a message stating "cannot update supersu binary. This is a problem" (something to that nature). I usually fix this problem by going into philz recovery and fixing root or manually flashing an older version of supersu. However, every time I reboot the phone I get the same "cannot update supersu binary". I am wondering if this could be a recovery issue. Every time I reboot through recovery or just reboot I have to update binary again. Is there a setting on philz that I am unaware of? I recently downloaded twrp manager and cleared cache and dalvik through that and when the phone rebooted I had no binary update issues.
Another thing I was wondering is could this be a Knox problem? I actually tried ota update to 4.3 ( i was rooted in 4.1.2) and it failed. Some time after manually upgrading to 4.3 I received a android security upgrade request. I did not accept the ota update. Is there any way to check if I have knox on my phone? Thank you
Sent from my SPH-L710 using Tapatalk
One thing I noticed. I dl a previous version of super su in recovery. I will have root access and all my apps that require root will work but there is no super su app. Once I dl supersu from playstore I will not be able to use apps that require root after rebooting
Sent from my SPH-L710 using Tapatalk
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 S4 with the motochopper and it keeps on telling me to update the Superuser from clockworkmod and i updated thru the plays store and it still asks for an update how can i fix this? and if i install the other superuser by chainfire it doesnt have the SU binary installed.... please help
re: SuperSU
MrDiaz said:
I have rooted my S4 with the motochopper and it keeps on telling me to update the Superuser from clockworkmod and i updated thru the plays store and it still asks for an update how can i fix this? and if i install the other superuser by chainfire it doesnt have the SU binary installed.... please help
Click to expand...
Click to collapse
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Misterjunky said:
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Click to expand...
Click to collapse
It still says it doesnt have the binary installed but it still grants any rooted applications lol.... ill keep messing around with it maybe i did a mistake when i did it on the motochopper
The latest version of superuser does not play well with twrp... Titanium Backup, CPU Sleeper, etc..still have superuser access... After flashing I just chose ignore but if you select 'fix' it will restore the old version of superuser. To update binary, I flashed Phantom kernel v1 from Infamous S4 thread. That fixed me up.
Your are the BEST news you have gave me how to fix the problem on t-mobile binary problem to root the galaxy s4 .IT DID WORK THANK YOU VERY MUCH the other top dogs that they root their phones dont know about this fix in you tube.. thank u again.
Misterjunky said:
Your problem is almost fixed, here is what you need: http://batakang.com/ftp/SGH-M919/MDB-SetUIDOff.zip
Flash it using CWM or TWRP recovery and reboot the phone and you will see the magic!
After doing this go to the play store and see if there is an update of SuperSU if there is then install it and reboot the computer.
(do not install superuser).
Good luck!
Click to expand...
Click to collapse
Sir, I love you. I searched for hours trying to figure this out.
sent from my jelly bean droid (SGH-M919)
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
Okay be gentle...
After the last update to JSSR15R I lost root and SU, doing the rebbot into recovery (vol down + power button) TWRP launches but when I select to go to recovery via the vol buttons and select it with the power button, all I get is the exclamation point android.
While I'm not a total idiot (debatable of course), is there a way to re-establish root and su without wiping off 15gigs of music and playlists and starting from scratch? Rooting the Nexus 7 (flo) the first time (at least for me) was a fight I eventually won, but for me it was a fight. tia Tutor
Same thing happened to me. I installed TWRP via goomanager. Then, I flashed SU update. Now I'm back rooted and going strong.
Like previous poster mentioned, just reinstall twrp and su.
Your bootloader should already be unlocked. Unlocking the bootloader is the only step that causes you to lose data.
Reinstalling twrp and su will not cause you to lose data, unless you had locked after installing them last time, and now need to unlock again to reinstall.
I reinstalled TWRP via the playstore but while it shows my directory file structure it won't install my copy of Update SuperSU 1.5.1.zip also I went to install goomanager but the descrription says you have to have root prior to installing.
As a sidenote while in TWRP if I go into rebooting the device none of the actions work except when I hit the "Bootloader" option the a error box pops up stating the option isn't available on your device. Tutor
Only way I know of to install TWRP is go to the TWRP web site and download it from there to your PC. You will find flash instructions on the web site.
Sent from my Nexus 7 using xda app-developers app
Download Goo manager from Playstore. Choose Flash Roms, It will tell you that you need a custom recovery to do this and ask if you have one or would like Goo to find one. Choose find one for me and it will download and install TWRP 2.6.3.0. After said process is complete flash SU update. Profit..
Same happened to me, but I reflashed TWRP and root access... Just curious how come that never happened with Clockwork Mod recovery being lost after applying an update to the system on the old N7.
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU 1.55 update.zip (Prior to reboot, use 1.55 as 1.65 has issues)
You will maintain root and keep twrp if you do it in this exact order.
sfhub said:
If you don't want to lose root or recovery, it is very simple.
Boot to twrp
Install OTA update.zip
Install SuperSU update.zip (Prior to reboot)
You will maintain root and keep twrp if you do it in this exact order.
Click to expand...
Click to collapse
Can TWRP generally find the latest OTA update.zip on it's own?
Lastb0isct said:
Can TWRP generally find the latest OTA update.zip on it's own?
Click to expand...
Click to collapse
Nope, download the ota manually and place on your virtual sdcard, then boot to twrp and select the file for install
installing through goomanager didn't work for me. It would say it installed but wouldn't really install. I did it using the fastboot method instead and that seemed to work fine.
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
CallMeTut said:
Well nothing I seemed to do would allow me to re-root the Nexus 7 after the 15R update, I finally went as re-rooted from scratch using the sticky post at the beginning of this subdivision forum for the Nexus. Back up and running in root and su... thx to all those that attempted to help me thru this
Click to expand...
Click to collapse
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
jyams said:
I used Wugfresh tool. Everything worked until I flashed the updated SU 1.65. I could never get root. I read earlier that others were using SU 1.5, so I manually went back into TWRP and flashed SU 1.5 and bam, had root! Then SU upgraded itself via the play store to the newer version. Go figure!
Click to expand...
Click to collapse
The update.zip for SU 1.65 is broken. A "placeholder" install script was included that does nothing.
IMO SuperSU 1.55 is the best version to use right now. The install script works, it doesn't mess with a bunch of file permissions for your *other* files in /system to support the new ota survival mode, and it has the fix for the problem that used to break the OTA installs.
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
cv91913 said:
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
Click to expand...
Click to collapse
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Will that work if the tablet is already rooted and SuperSU is already installed? SuperSU is working as long as I don't run the UI. Sorry, I am new to this rooting stuff. Thanks for the response.
I have P5210 Tab3 10 Wifi
We used chainfire=> http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
And in our model yes we even write over old not working su. KK 4.4.2 does not like to be rooted and kills it. As gr8nole said. we too are force to install UPDATE-SuperSU-v2.02.zip on recovery. This one does survive KK attacks. Clearly this one, you installed from Recovery. But you can go to
http://forum.xda-developers.com/showthread.php?t=1538053
For other installation methods