Superuser binary missing after OTA update - Motorola Droid 4

I had my phone rooted prior to the update. Using Voodoo OTA Rootkeeper, I selected Temporary Unroot and applied the update. Once the OTA finished installing, I went back to Voodoo OTA Rootkeeper and selected Restore Root. However, it does not appear to have worked properly. Some of the apps that need root access work OK (Root Explorer), but others are unable to find root.
Superuser.apk was already installed, but I reinstalled it and Busy Box. Looking into Superuser settings, I saw "Su binary vnull". When I attempt to update it, I get a message stating "Failed to find currently installed su binary. Update cannot continue".
So - what do I do now?

I had a similar issue when I first updated to one of the ICS leaks. I uninstalled superuser then re-ran the root script using Jsnweitzels ICS Only Utility and that fixed it for me.
Droid 4 - AOKP K1L0

You should run root script again, like kwyrt said, plus I would recommend to install voodoo root keeper from market and protect su binary.

Thanks - root restored.

I had a similar issue and wasn't aware. Titanium Backup fixed something and Ihavent seen any issues since.

Thread has been moved from Development to General because it is a mere help request.

Related

Chainfire's Superuser app error on rooted phone

this is my problem. i have a rooted phone and i get this error
https://bu.mp/tEb2VB
thats supersu, what method did you used for rooting? don't you have installed and earlier superuser app? have you installed busybox?
jpsb said:
thats supersu, what method did you used for rooting? don't you have installed and earlier superuser app? have you installed busybox?
Click to expand...
Click to collapse
i used cmw method. i think it was a busybox installer for root
Binary updater fails to update binary – This usually happens because for Superuser can’t write to the system partition where the binary is installed. This can happen for a couple reasons. First, and most common, is that your device has S-ON which prevents the system partition from being written to at runtime. Even if a remount succeeds, and the system thinks that the partition is mounted as rw, you can’t write to it. There are different solutions for different devices, but the easiest usually involves simply updating Superuser through ROM Manager.The app consists of two parts, Superuser.apk and the su binary.The su binary is what other apps call when they need superuser rights. The binary checks the database maintained by Superuser.apk to determine if you have already granted rights to the requesting app.Superuser comes pre-installed on any rooted ROM. In fact, without it, you don’t have a rooted device at all. You cannot uninstall it, it lives on the system partition with other apps that came pre-installed on your device!http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Sounds like I have the same issue, here's my post on chainfires kernel thread:
http://forum.xda-developers.com/showthread.php?t=1331784&page=186
I don't like using CWM out of fear of the brick bug which probably only happens when wipe is used but have stayed away from the first few warnings we had.

[Q] Superuser/SuperSU issues

Here is a problem I have and I am wondering if anyone else has experienced it and/or solved it:
Phone: Bell SGS i9000
FW: CM9 Nightly (currently May 30) all "stock" (no custom kernels etc)
I installed SuperSU some time ago as it seemed to have more utility than Superuser. I noticed after a flash that Superuser would take back "control" of the su binary and I'd have to manually re-assign it to SuperSU. I decided, after doing some research to see if it was OK, to freeze Superuser in Ti Backup. So far so good.
I noticed today though, that none of my scheduled backups in Ti Backup have taken place for a while, so I launched the app to see what gives. It was at that point I discovered that TB couldn't get su privileges from the system. I launched SuperSU and it attempted to update the su binary - and failed.
Since TB froze the Superuser apk, I can't uninstall it. I also cannot unfreeze it in TB because it cannot get su!
I'm a bit stuck.
I have ROM Toolbox, which appears to work OK, as well as ROM Manager, and both seem to be able to use su commands without issue (I told SuperSU to remember the granting of su permission when I first started using it) I don't have any other apps that regularly use su permissions (not that I know of) so everything else seems fine.
I'd like to fix the updating binary issue with SuperSU though, so I can once again grant TB su and then fix everything.
Anyone have any ideas? I've already tried re-flashing Superuser from recovery, still shows as frozen. I tried unfreezing from ROM Toolbox, but it fails.
I'm stuck and I'm at the limit of my understanding and experience with this. Anyone who can help will receive my eternal gratitude - and a pint if you're ever in my town!
Try to delete tb then reflash the rom without any wipe
Sent from my GT-I9100 using Tapatalk 2

D4 Utility and ICS..........??

I used the D4 utility to root my Motorola Droid 4 running, at the time, GB. I then DL'd Titaninum Backup and Voodoo root keeper. I have recently gotten the OTA ICS and believe I preserved my root with voodoo. I did have some issues that root keeper seemed to resolve. My question is; do I need to factory reset and reroot with a different utility or am I good? The only issues I seem to have now is 1. My wallpaper seems to "zoom" in going from landscape view to normal portrait view 2. 4g/3g freezing and not opening websites without backing out and/or rebooting 3. My sound is sometimes off when going from muted to any volume (seems only with videos and or streaming music ie: youtube, iheart, etc)
A lot of people experience issues when upgrading to ICS. While the update is supposed to bring you to 4.x from 2.x as seamlessly as possible, the reality is there will always be issues.
Do a factory reset to give your ICS a "fresh" start and you'll find it should run much more smoothly. If you kept root via RootKeeper you should be good, but you can always re-root using the 4.0.4 root tool found here:
http://forum.xda-developers.com/showthread.php?t=1707214
Sent from my DROID4 using Tapatalk 2
DISCLAIMER: I have no clue so everything below is speculation. Hopefully I don't make someone's informed answer more difficult...
When you root you're going to get a su binary (or did I install Superuser?).
Voodoo OTA Rootkeeper lets you backup/protect the root (binary). Then you can temp un-root and subsequently restore root.
Before going to ICS one should:
- in Voodoo OTA RootKeeper: Delete su backup (delete the backed up su binary)
- in Superuser: check for updates and update to latest binary (updates su to the latest binary)
- in Voodoo OTA RootKeeper: Protect root (saves the updated su binary)
- in Voodoo OTA RootKeeper: temp un-root and then restore root (refreshes loaded/running copy to current binary?)
Since it worked for you after the upgrade I'm guessing you already had the latest su binary. and you don't need to do anything further with respect to root?
There are 2 versions of the D4 utility. One for GB and one for ICS. You want to be using the ICS one now
Apparently you did not have safestrap installed before the update to ICS.
My understanding for safestrap is that you have to completely uninstall it first or the update fails.
- in safestrap: uninstall recovery
- in Settings->Applications->Manage Applicaions: uninstall safestrap
- in a file explorer with root capabilities: delete /system/bin/logwrapper
- in a file explorer with root capabilities: rename /system/bin/logwrapper.bin -> /system/bin/logwrapper
...not real clear on that last one. I gather that installing or using safestrap moves logwrapper to logwrapper.bin and uses a modified logwrapper in it's place? So you need to restore the original one? Maybe because otherwise the updater's check for system files fails?
[Sorry about sort of hijacking your thread to verify my understanding of this but I'm getting ready to make the leap myself and it appears I have a similar setup to yours]
You don't really have to worry about updating the su binary as long as there is a back-up in voodoo. The ICS only utility should re-root without any trouble if you lost it in the update. You can also use RSD Lite and the ICS fastboot file to start over fresh if you like.
The Magician Type 0 said:
A lot of people experience issues when upgrading to ICS. While the update is supposed to bring you to 4.x from 2.x as seamlessly as possible, the reality is there will always be issues.
Do a factory reset to give your ICS a "fresh" start and you'll find it should run much more smoothly. If you kept root via RootKeeper you should be good, but you can always re-root using the 4.0.4 root tool found here:
http://forum.xda-developers.com/showthread.php?t=1707214
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Sorry for my ignorance, but when I do a factory reset I will lose everything correct and will have to dl my apps and root again? or should I 1.unroot, 2.factory reset, 3.then root again?
You shouldn't loose root and will not lose superuser if it was installed as a system app. You will have reinstall any app you downloaded from the market or sideloaded. Otherwise your phone will be like the day you got it, without any user data.
jsnweitzel said:
You don't really have to worry about updating the su binary as long as there is a back-up in voodoo. The ICS only utility should re-root without any trouble if you lost it in the update. You can also use RSD Lite and the ICS fastboot file to start over fresh if you like.
Click to expand...
Click to collapse
If I were to root my droid with ICS only tool, will I be able to unroot and go to stock if needed, ie: warranty, etc.

Uninstall as system app

The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.

How to unroot when SuperSU says su binary needs to be updated

In my 5th gen fire hd7 I tried to root using rootjunky supertool.
I don't know what went wrong during the process but the SuperSU app always says su binary needs to be updated and when I select normal it fails. I'm very much disappointed and annoyed and decided to unroot.I tried the universal unroot app but it fails .nRoot checker says root access is not proper and root explorer can't edit root files.
Is there any way to unroot without updating su binary?

Categories

Resources