Hey guys, so I'm trying to install BusyBox on my new Nexus 6 running stock 6.0, rooted. When I try to install via Stericson's installer I got from the Play store, I get:
"We could not verify the integrity of the binary selected..." flashes for a moment, then:
"BusyBox installer was not allowed root access. This may be an issue with Superuser, open Superuser and make sure that you are allowing root access. This application will not work without root access."
I've made sure that the app is allowed root access, and have also tried deleting it from SuperSu so it would prompt me and I could grant it access again, but still the same issue. I'm not sure what the deal is, it seems like I could be having root issues? I appear to have root since I am able to use TiBu, but something seems funky. For example usually when I open FKUpdater it says "FKUpdater has been granted super user access..." and then "Unable to acquire ROOT access." Other times it only says "Unable to acquire ROOT access." I haven't tried flashing a kernel with it because I don't want to at the moment while I figure this other issue out, so I'm not sure if it's falsely reporting the root error.
So, I looked into things further and it seems like I may have some sort of permissions issue. I tried using JRummy's BusyBox installer, but that fails also and just tells me to try installing a different version of BusyBox. It also includes a script for fixing permissions, and when I run it I get "error: only position independent executables (PIE) are supported" and "/data/user/0/com.crummy.busybox.installer/files/temp.sh[118]: sync: can't be executed: permission denied."
Permissions for /data/user/0/com.crummy.busybox.installer are set to drwxr-x--x, as is /system. Also /system is only showing 58 MB free but I don't think that's a problem...
Any ideas? I'm totally stumped...
set your SElinux to be permissive(via app or terminal command)
Related
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.
Hello all,
A friend gave me his Droid 3 which was successfully rooted (Superuser version 3.13 is installed). When I look at the log I can see many past "Allowed" entries. However, I attempted to install Safestrap (version 3.05), and it was denied Superuser access (can see the denial in the log). I then attempted to grant other apps Superuser permissions and I get a "[App Name] has been denied Superuser permissions" message (and it shows "Denied" in the Superuser Log).
The really odd things are that (1) it doesn't prompt to allow or deny (despite the setting saying to prompt), and (2) if I select Superuser funcitons within the Superuser App, it will allow them. For example, if I select "temp unroot", it says "Superuser has been granted Superuser permissions".
I know I can SBF the phone and start over, but there are lots of paid Apps on the phone and I just assume try to work on getting Superuser working again if it's possible.
Please help!
Try setting to always allow
Sent from my DROIDX using XDA Free mobile app
Solved! Ok, with the device connected to my computer and playing around in adb, I noticed that the permissions for the SU binary were all goofed up. So I issued the command: adb shell "chmod 6755 /system/bin/su" and that solved the problem. Hope this helps someone else.
Shadow: Thank you sir for your reply. I should have mentioned in my original that I did try "always allow" in addition to prompting and it didn't make a difference. However, I solved it by changing the su binary's permissions (see above). Thanks again for takinig the time to reply.
***UPDATE***
I removed Kingroot through their app and unrooted my phone. I tried another one click root, Kingoroot (I know, quite similar names.) The SU which this one installs, isn't restricting me and I successfully set read/write to /system.
I still would prefer to be using superSU but I get a binary occupied message, and the kingouser app doesn't have an option to switch SU app.
For anyone else struggling with kingroot not letting apps work properly, try kingo, who knows.
-----------------------------------------------------------------------------
I have the Z3 Compact, and I HAVE NO ACCESS to a PC, and thus have rooted my phone with King root (which was a terrible idea but any root is better than no root)
I have this issue, where King root in some way shape or form is not allowing anything that requires write permission to /storage access to it.
This is not allowing me to install/use things like busybox, lucky patcher, freedom, and is also, stopping me from using terminal emulator to do things such as mount -o rw,remount,/system or anything else. I tried to use a system I found on XDA to replace Kingroots superuser to SuperSU to get around this, however, the replace_kinguser method, fails with no write permission, and also, fails to remove kinguser from /system/apps/kinguser because that doesn't exist as a directory and I think Kingroot may have made changes to their superuser handler.
I really, really need help getting Kingroot out, and superSU in. Without the use of a PC. Considering I do, have root, there must be something I can do.
I also can't set system to write with ES file explorer or pretty much any other method on the first ten pages of Google.
Any time I try to set /system to r/w I get permission denied.
I'm running, android 5.0.2
Also, BOOTLOADER UNLOCK ALLOWED? NO
So I don't think I can flash a custom recovery of any kind.
Like I said, if the default action is prompt, an app seeks root access and there is no prompt to grant it. If I change to grant as default, everything works. Root Checker, for instance, will fail to detect root in prompt mode but does so in grant mode. Same for Root Browser and, most importantly, Xposed.
I've tried reinstalling SuperSU. Didn't help. I have systemless root on a Moto X Pure and SuperSU 2.82.
I really don't want to leave it with grant as the default action. Not safe. I've been able to find a few other posts with a similar problem but they don't lead to solutions. This is a new behavior. Prompt used to work. About a week ago, I installed the latest version of Sensible Android Auto in Xposed. It worked twice and then stopped. My guess is that is the time when SuperSU stopped granting root. Everything that needs root can get root but ONLY if root is granted automatically to anything that asks for it.
Just rooted my Kyocera Event and deduced it to have the same problem. SuperSU 2.8.2 was not providing prompts and thus not granting root access, however changing to grant default did provide root. I tried installing SuperSU 2.7.9 rc4 but had the same result. I'm now just waiting for a definitive fix while looking for an alternative solution.
I just installed magisk succesfully(?) on my xperia 5 ii following this guide:
https://forum.xda-developers.com/sony-xperia-5-ii/how-to/guide-magisk-twrp-recovery-t4177209/page7
Using the beta channel (stable simply doesn't even boot), magisk manager shows v21 installed. However none of the root apps I tried so far (busybox, adaway, system app remover) works. All of them give some kind of error. The root privileges are being granted (I get the promt to grant/deny and the popup that root was granted). This is very weird and the first time it happens to me on any device. The root browser file managers shows the "root directory" with 0 free space incorrectly (1.6GB used - 1.72 total) I tried copying a file inside the /system directory and it just didn't do anything. I tried reinstalling magisk from the manager, but its still the same. Any help will be appreciated, I really have no idea what to try at this point.
Hard to say... What's "some kind of error"? Maybe the Magisk logs show something (although you'd likely have to switch to the Canary channel to get any useful logs).
I think it's best to wait for a reply to your query in the thread you linked. That's likely to be the best place to get help, since that's where you find other users of the same device...