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.
Related
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.
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)
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Click to expand...
Click to collapse
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
optimumpro said:
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
Click to expand...
Click to collapse
I am using Kingo SuperUser to grant the apps root permission. Had some trouble replacing Kingo SuperUser with Chainfire SuperUser but I figured Kingo should've done the trick as well. When I mount Kingo did prompt me for permission and I allowed it, somehow I think the root is incomplete ?
Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc.
...
...
somehow I think the root is incomplete ?
Click to expand...
Click to collapse
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
kentexcitebot said:
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
Click to expand...
Click to collapse
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Steven90 said:
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Click to expand...
Click to collapse
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
optimumpro said:
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
Click to expand...
Click to collapse
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Steven90 said:
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
Click to expand...
Click to collapse
Ulvgrim said:
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Click to expand...
Click to collapse
Try this, it's almost a one-click tool
http://forum.xda-developers.com/showthread.php?t=2784900
Exploit maybe works with 5.1.1, but if not, downgrade your firmware to 5.0.2, use Easyroot to exploit, then upgrade back.
The "classic" root I was referring to requires downgrading from Sony's Lollipop/Kitkat FW to Jellybean due to Sony patching the exploits in the newer FW used for rooting. The steps are outdated now and is replaced by Easyroot. http://forum.xda-developers.com/showthread.php?t=2688933
***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.
Hi all!
I might be asking a stupid question, so forgive me if I do.
The situation is the following... I have a TVBOX Q96 HOME 4K (cheap Chinese one based on RK3229) that is pre-rooted. All applications using root work fine. However, there is no "superuser" manager installed on it in order to disallow certain apps to gain root access. In the past I already had a similar situation with some other box and when I installed SuperSU apk the device hasn't boot anymore. I that case I got a stock firmware and could unbrick it, but now I can't find any ROM for this device in order to play with it.
So, the question is... is it possible to install Magisk Manager in order to manage access to the built-in su? Older version I tried correctly identify the device as rooted (with SuperSU 2.76), but do not offer me a Superuser menu where I could manage access to the su of the apps. Neither I get a prompt when an app is requesting access to su.
Any solution to my problem?
No, you will not be able to use the Magisk Manager to manage superuser access for SuperSU.
Any idea what might cause the device to not boot anymore after installing SuperSU.apk?
I compared the installed su binary with the one from chainfire's UPDATE-SuperSU-v2.76-20160630161323.zip (arm7), and they are identical. What does installing an apk alone to the system beside managing the access for the apps?
I have to admit I don't know exactly what happens "behind the scene".
I have absolutely no idea why installing the SuperSU apk would cause your device not to boot... Sorry.
Edit: Wait... You write "installing an apk alone to the system". You're not installing it as a regular app, but to the /system partition? If so, that's what might be causing issues.
Sorry to mislead you... I wrongly expressed myself.
I'm not installing it as a system app - I have installed it (on previous box) as an ordinary user app and as I said the system couldn't boot anymore afterwards (I had to reflash the ROM to unbrick it).
BTW... this is a known issue with these Chinese TVBOXes. There are couple of posts also here in XDA about it and nobody knows AFAIK what is the root cause.