Last night I successfully unlocked and rooted my phone, but I've been having some issues getting SuperSU to work completely. When I install SuperSU and open it, it gives a popup saying the binary needs to be updated. I click on normal update, and it says "Installation failed! Please reboot and try again." After reboot, I get the same error. The app itself seems to be working as my ad blockers and whatnot are calling up the root checker, but It just doesn't want to update to the latest binaries. Any suggestions? Thanks!
*update* I fixed the issue. I installed CWM, and was able to update the supersu binaries through recovery.
Related
I am running Timat 2.2.2. My market asked me to update superuser which I did and it worked. However I keep getting a message that my su binary is out of date. It's on v2.3.1-ef. I check for updates and it finds 3.0 however when I go to update it fails on "Gaining root access... fail!"
Why would this be happening if root is working fine on all other apps? I tried the SU Update Fixer app but that didn't help.
I forgot to mention that I also tried to have SuperUser automatically approve new su requests; still no go.
uninstall the update and re update it again and then try...should work
LPHS said:
uninstall the update and re update it again and then try...should work
Click to expand...
Click to collapse
this worked, thanks.
Somehow, I managed to lose root access. Supersu always gives me the message error saying "There is no SU binary installed, and SuperSU cannot install it." Now applications that requires root access do not work and F/Cs..
Anyone got some information about this problem?
insanehadi said:
Somehow, I managed to lose root access. Supersu always gives me the message error saying "There is no SU binary installed, and SuperSU cannot install it." Now applications that requires root access do not work and F/Cs..
Anyone got some information about this problem?
Click to expand...
Click to collapse
have you tried re rooting?
smaw51 said:
have you tried re rooting?
Click to expand...
Click to collapse
Not yet. Will try flashing the jb rooted rom first
Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.
DWDahlinger said:
Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.
Click to expand...
Click to collapse
Since you have TWRP installed do a android backup and install one of the rooted ROMs. Most will install SuperSu and BusyBox in the installation process.
DWDahlinger said:
Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.
Click to expand...
Click to collapse
You need to flash the latest version of supersu. My hunch tells me you aren't using the latest version. Also, when you post for help once please don't continue making similar posts and threads. It makes it very hard for you to get the help you are looking for. You never responded to the last post I made to you last night about to unlock your bootloader either.
Es file explorer is crashing because of the webview for Android update. Uninstall that update and it will work again.
dottat said:
You need to flash the latest version of supersu. My hunch tells me you aren't using the latest version. Also, when you post for help once please don't continue making similar posts and threads. It makes it very hard for you to get the help you are looking for. You never responded to the last post I made to you last night about to unlock your bootloader either.
Es file explorer is crashing because of the webview for Android update. Uninstall that update and it will work again.
Click to expand...
Click to collapse
Sorry I didn't see your response to my post. I only saw the others. Been trying to figure this stuff out since.
I think I flashed the latest version (2.46)? I used windroid. Pushed the file to the phone and installed it from the internal memory. Not sure of what the webview in Android update is or how to uninstall it. I will try the method you gave me in the other post. Thanks!
Update: Disabled webview for Android. Working now. Thanks!
So I'm currently trying to install the latest (v86) version of the Xposed framework on my Samsung S7 g930w8. I am able to install TWRP (3.0.0) using Odin 3.11.1 just fine and also no-verity-opt-encrypt. My current version of SuperSU is v 2.68. The issue arises when I try to install the Xposed framework after installing these two. I used the app Hardware Info to determine that my processor is an arm64 one so I downloaded the according version of Xposed Framework. I've installed the Xposed Installer but I am currently unable to use it because it states that I don't have any version the Xposed framework installed so I should flash it using a recovery mode. Before attempting to use TWRP to do that, I figured I'd give Flashfire a shot. Everything went perfectly fine up until the point where my device rebooted after installation. At that point, my screen froze at the "Samsung Galaxy S7" logo and refused to go any further. In the top left corner "Kernel is not seandroid enforcing" can be seen much like whenever I boot into recovery mode. I tried rebooting to recovery and then doing a restart, but the problem continued to occur. I eventually gave up on Flashfire and instead opted to do it manually so I flashed back to default, reinstalled TWRP and this time did the installation of Xposed directly through there. To the same effect, the process completed and after rebooting to the Samsung logo screen, the process and froze and refused to go any further.
Any ideas as to how I can get Xposed working on my phone?
Any help is appreciated.
Have you tried installing systemless Xposed? If not go to Here
Leeum said:
Have you tried installing systemless Xposed? If not go to Here
Click to expand...
Click to collapse
I just found out about this and proceeded to return to stock flash and then install SuperSU followed by the systemless version of Xposed. Thankfully, it worked, however I'm having another problem. On the Xposed installer, there is a yellow warning sign and in yellow text under it, it reads "Xposed Framework version 86.2 (Systemless by topjohnwu) is installed, but not active. Please check the logs for details.". This is preventing me from installing any modules because every module says that I require a newer XposedBridge version and thus can't be activated. The log message is:
"Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)"
Any help is appreciated, thanks.
avinashpillay said:
I just found out about this and proceeded to return to stock flash and then install SuperSU followed by the systemless version of Xposed. Thankfully, it worked, however I'm having another problem. On the Xposed installer, there is a yellow warning sign and in yellow text under it, it reads "Xposed Framework version 86.2 (Systemless by topjohnwu) is installed, but not active. Please check the logs for details.". This is preventing me from installing any modules because every module says that I require a newer XposedBridge version and thus can't be activated. The log message is:
"Cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT (No such file or directory)"
Any help is appreciated, thanks.
Click to expand...
Click to collapse
Do you have a custom Kernel installed?
Leeum said:
Do you have a custom Kernel installed?
Click to expand...
Click to collapse
I'm not exactly sure in all honesty. If you're referring to TWRP then yes but aside from that, I didn't install anything else (unless that's what the no-verity-opt-encrypt.zip image is). I do have some apps to install images (Rom Manager by CWM and Flashfire, both of which I tried to install the Systemless Xposed with but got the same error.
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Crav3 said:
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Click to expand...
Click to collapse
Its been a while since I used Magisk. But at that time, PHH superuser had to be used?? Not sure if that is still the case though. Sorry I could not be more help
Yes it does need to be used and it was already installed. But after rebooting the app was not in my app drawer and i had a notification to install SU through play store. But when i go to play store it says it is installed and needs an update. After updating it tells me su binary occupied and takes me to a page to help fix it but i already tried flashing superuser zip file through recovery and nothing changes
Similar Problem
Have you fixed it already because I am havibf the same problem here. I am usibg Samsung J7 Core
You can do what you said you would do (reinstall stock ROM) and then you can try again. Looks like thats the only thing you can do, unless you can somehow remove the root binary and the app using something like ES File Explorer (but again, it requires root) or you can try another root provider.