Database Develop

[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

Superuser binary missing after OTA update

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.

[Q] Rookie mistakes with backup and busybox?

I have a rooted, nonDE, vzw Moto X on 4.2.2 with the hotspot entitlement hack enabled. I would like to install the Xposed framework and have been reading up on it. Everything that I have read states the I should make a backup first. I installed online nandroid backup. Upon opening, the app stated that it required busybox to be installed. After failing several times to install BB, I learned that I have to change the /system dir from r/o to r/w. I rebooted into recovery, checked for r/w and attempted to install BB. This time it progressed a little further but still failed. I am clueless at this point. Also, every time I reboot, r/w is enabled. I've since installed es file explorer to switch back to r/o.
Whee did I screw up and how do I fix it?
TIA

Just install GravityBox and stop worrying about the backups.

slingblade01 said:
I have a rooted, nonDE, vzw Moto X on 4.2.2 with the hotspot entitlement hack enabled. I would like to install the Xposed framework and have been reading up on it. Everything that I have read states the I should make a backup first. I installed online nandroid backup. Upon opening, the app stated that it required busybox to be installed. After failing several times to install BB, I learned that I have to change the /system dir from r/o to r/w. I rebooted into recovery, checked for r/w and attempted to install BB. This time it progressed a little further but still failed. I am clueless at this point. Also, every time I reboot, r/w is enabled. I've since installed es file explorer to switch back to r/o.
Whee did I screw up and how do I fix it?
TIA
Click to expand...
Click to collapse
you have a verizon so locked bootloader so you option for backup are two things
install Safestrap(this is a recovery for locked bootloader) this will allow you to do nandroid backups
or install Titainum backup(this is a app) this will allow you to back up user and system apps

[Q] Busybox installed but not recognised

Hello, I'm sorry to ask but I checked all 31 posts about busybox in here and even in other phones, and nothing helps.
I've a Moto X with unlocked bootloader, and I installed twrp 2.8.4.0-ghost, installed last SuperSU and busybox from stericson.
I'm running Android 4.4.3 from stock (came that way when I bought it).
Titanium Backup works, it says Root Access Ok and BusyBox 1.19.4 (also have SQLite, i don't know if it's relevant)
With ADB i can access shell and su, but when typing "busybox" it says it doesn't recognise the command.
I'm trying to use a pc software that needs busybox, when connecting the phone it doesn't recognise busybox.
I tried installing busybox manually, using this and this, but at some I always get the error that data/local/busybox is read-only
Any help greatly appreciated, thanks

Try to update Busybox. I'm on 1.23.0 and was on 1.21.x for a long time. I think you are using a very old busybox.

Data recovery app doesn't recognize Root (Samsung Note 5) Please Help!

Hello everyone,
I am facing an issue and will be eternally grateful if someone helped me with it. I recently lost some very important audio recordings from my phone. These are very important and I want to run a data recovery tool to help retrieve them but all such tools require root access. I then rooted my phone using magisk and checked the status via those root check apps and they show the status as rooted. However, the problem is that none of the data recovery tools recognize the root and hence cannot run a scan. Perhaps I am overlooking something here. Model of my phone is SM-N920I. I flashed the magisk via twrp and have also installed the Magisk manager. Everything is up to date. Again, when I check the root status of my phone via the app "Root checker basic" it says "Root access is properly installed". Also, when I am using the data recovery tool i.e. Fonelab my phone does not prompt me for root access. Nothing is shown on the screen.
I am sorry if this thread is in the wrong section. Mods can feel free to move it or notify me. Thanks

If other root apps are functioning properly it's an issue with the app you're trying to use. You should contact the developers of the apps in question...