"superuser binary is out of date" but wont update - Sprint Samsung Galaxy S6

i just rooted my s6, and i DO have root access, but when i try to open superuser (that was installed along with the root) it says "superuser binary out of date" and asks how i want to update it. The only options it gives me is Cancel and Recovery. If i choose recovery it boots into recovery then does nothing. I found the updated version of superuser online and transeferred it to my phone and flashed it thorug TWRP. Still says it. I tried installing supersu and when i open it it says "su binary is occupied" so i used an uninstaller to uninstall superuser, and supersu still says binary is occupied. So i reinstalled superuser but now i dont know what else to do to get my superuser app to work? Any ideas? TIA

I don't know how comfortable you would feel about this, but a lot of us have moved on to using Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
There are two parts, Magisk itself and the Magisk Manager.
Recommended path is to return to Stock, install TWRP via Odin but don't reboot. Instead shut down, reboot directly to Recovery and flash Magisk. Usually on first boot you will get a prompt to install Magisk Manager, do that and you are set.
Before you do that, take some time to read about Magisk. It is similiar to SusperSu, but allows you to conceal that you are rooted. (A feature that you enable within the manager.) I find it a great improvement.

ohhhh. i get it now. the method i used to root was with magisk. it prompted me to install it when it booted up so i did but didnt really go look at the magisk manager. i didnt realize that was what handles the su. thats why it says its occupied

Related

[Q] Find 7: "no su binary installed and supersu cannot install it"

Hi folks,
I've follow ParotZ's Recovery Installer process to root and am having SuperSu issues.
I install recovery (option 5), then reboot to recovery (option 0), system > reboot > swipe to install > and then once it loads I'm greeted with
"no su binary installed and supersu cannot install it"
I've put UPDATE-SuperSU-v2.16 on internal storage and tried earlier versions and flashed, with the same result.
The SuperSu app is installed. I attempted a manual update on the Play store, but the 'no su binary' message is still there.
I can't uninstall supersu, either with an uninstaller app or through Play (it does not show 'uninstall', just shows 'open')
It persisted after I factory reset and wiped (not through recovery).
Any help? Keen to get on Cyanogen.
My phone specs.
Model
Oppo x9076
ColorOS
v2.0.0i
Android version
4.4.2
Build number
FIND7WX_12_141017
Kernel
3.4.0-S3753
Baseband
Q_V1_P14
I've seen others with the question, but none with answers for the Find 7 :/
Cheers!!
solved
Hi folks,
I've solved the issue. I could not root using that method because I had updated the OS and there was some form of conflict that stuffed the SuperSu binary.
So I downgraded back to stock (the earlier ColorOS) and reapplied the root process.
For those with the same issue follow these steps http://theunlockr.com/2014/08/22/how-to-unroot-the-oppo-find-7-video/
Then reattempt the root.
Note that step 6. "Using the volume buttons to navigate and the power button to select the option you want, select Wipe Data and Cache." will erase the OS you just copied over, so do this prior to copying the OS or you'll just need to do it again.
When the OS loads and you come to the update SuperSu step, my Play store wouldn't load due to I think a delay in the accept terms of use popup. So I used the TWRP method and it worked fine.
Good luck.
Darren.

[Q] Unable to gain root access in all Lollipop ROMs

Hi, I have serious problem with root access. It does not matter which version of SuperSU (latest or older) if it is built-in Superuser or if I flash it via cwm or philz with fixing supersu or without that or TWRP. Still the same result (for example Titanium Backup), shortened error message is:
"I could not acquire root privilegies. This attempt was made using the "/system/xbin/su" command".
When I open the SuperSU app, everything is just fine, no error message explaining failure in installing SuperSU script.
What should I do to gain (how to call it) full root access? Thanks for any help.

[ROOT][10.6.A.0.454][5.0.2][LB] Get SuperSU

Finally, we can get our loved supersu following this steps:
1) Root with KingRoot.- Download KingRoot's apk, install it and root your device.
2) Install SuperSU, open it and allow root permission.
3) Install ZL-lockeddualrecovery.
4) Download Flashable BusyBox, boot into recovery and flash it. (I recomend Stericson's Busybox)
5) Download Flashable SuperSU, boot into recovery and flash it.
6) Get this app anywhere you want --> SUPER-SUME PlayStore Link Works v7.3 & v7.8. Run it and touch big blue button.
7) Go to SuperSu app and normal update SuperSu binary. if doesn´t work, do the step 5 again.
Reboot and DONE!
Hi, i can't run this method. i checked everything and it's all right, i rooted with kingroot , installed supersu and granted root acces, installed the adb drivers and run xzlockeddualrecovery installer, i tried all the options and none works, it stucks at waiting for device in first step

can't install Magisk

tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?
Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.
Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?

Magisk Root for January 2019 Update

I've seen people speaking about boot loops after flashing TWRP and Magisk on the January 2019 update.
I haven't had any issues, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!
bendrum30 said:
Has anyone been able to root the January update with Magisk?
My bootloader is unlocked.
I flashed the January factory image (saving data), flashed TWRP, and flashed Magisk 18.0. Rebooted and Magisk appears installed and passes Safety Net check, but I'm not able to grant root privileges for apps.
If I open Titanium Backup, it tries to obtain root, but I never get the prompt and eventually, I just get the toast that Titanium Backup has been denied root privileges.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Did you try opening Magisk Manager > Tap Menu > Tap Superuser > Enable Titanium Backup Root?
Homeboy76 said:
Did you try opening Magisk Manager > Tap Menu > Tap Superuser > Enable Titanium Backup Root?
Click to expand...
Click to collapse
Yes. Thanks @Homeboy76 for your suggestion! It wasn't listed in there a after trying 3 times. However, eventually (after 5 minutes or so), I got the prompt.
Strange... I just updated the OP. This thread can probably be deleted.

Categories

Resources