Develop Bugs

[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.

updating rooted phone

So if I download the most current factory images to updated a rooted phone...is this the correct method?
I will NOT wipe date, will wipe cache though and flash:
vendor
system
recovery (optional only if you want stock recovery)
boot (if you want stock kernel)
I dont flash userdata unless I want to lose everything right?
I want to keep my phone the same, but update to current security patches.
and then obviously re-root after all of this if you want to be back rooted.
Does this sound right?
thanks

Ok that doesnt work. So I am doing something wrong and not knowing something...I would appreciate if someone can help.
I have nexus 5x with 7.0...but not the most recent, I am on Octobers updated version.
I have TWRP installed and rooted.
I booted to fastboot and flashed newest:
vendor.img
bootloader.img
system.img
radio.img
erased cache with "fastboot erase cache"
and it just boots to google screen.
I had to restore backup to get phone to work right.
how can I update my system?
thanks

I also like to keep a rooted phone up to date with the newest builds/security updates of stock Android...here's what I do:
Download the OTA zip from Google, and get the Flashfire app (by developer Chainfire) to install it.
After opening Flashfire...
- Tap the + symbol and select "Flash Zip or OTA"
- navigate to and select the OTA zip file
- Check "Restore boot and recovery images" option (I first tried to install without this, but it's necessary for OTAs). The "Mount /system read/write" option is always checked by default for me.
- Under the EverRoot setting, check "Inject SuperSU" so you'll stay rooted after the update.
- Under the Reboot setting, check the "Preserve recovery" option...this backs up TWRP and restores it after the OTA is installed.
Hit the Flash button and away you go...takes a few minutes for the process to finish...and you're all set :good:

IcedDog said:
I also like to keep a rooted phone up to date with the newest builds/security updates of stock Android...here's what I do:
Download the OTA zip from Google, and get the Flashfire app (by developer Chainfire) to install it.
After opening Flashfire...
- Tap the + symbol and select "Flash Zip or OTA"
- navigate to and select the OTA zip file
- Check "Restore boot and recovery images" option (I first tried to install without this, but it's necessary for OTAs). The "Mount /system read/write" option is always checked by default for me.
- Under the EverRoot setting, check "Inject SuperSU" so you'll stay rooted after the update.
- Under the Reboot setting, check the "Preserve recovery" option...this backs up TWRP and restores it after the OTA is installed.
Hit the Flash button and away you go...takes a few minutes for the process to finish...and you're all set :good:
Click to expand...
Click to collapse
just for future reference, i want to update when stable 7.x hits
can i skip from 6.0.1 (march probably?) all the way to 7.1.x?
i have xposed and tons of modifying modules (probably on system) installed, are those going to be wiped?

IcedDog said:
I also like to keep a rooted phone up to date with the newest builds/security updates of stock Android...here's what I do:
Download the OTA zip from Google, and get the Flashfire app (by developer Chainfire) to install it.
After opening Flashfire...
- Tap the + symbol and select "Flash Zip or OTA"
- navigate to and select the OTA zip file
- Check "Restore boot and recovery images" option (I first tried to install without this, but it's necessary for OTAs). The "Mount /system read/write" option is always checked by default for me.
- Under the EverRoot setting, check "Inject SuperSU" so you'll stay rooted after the update.
- Under the Reboot setting, check the "Preserve recovery" option...this backs up TWRP and restores it after the OTA is installed.
Hit the Flash button and away you go...takes a few minutes for the process to finish...and you're all set :good:
Click to expand...
Click to collapse
Have you done this with a non-stock kernel like elemental-x?
I dont mind having to reflash the kernel after the update, but I am just trying to avoid bootloops after restoring.

"superuser binary is out of date" but wont update

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

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?

Question OTA update while retaining magisk

I would like to install the latest Google OTA update but also keep root.
I heard you can do the following to retain root:
Open magisk
Click on "uninstall magisk"
You will then be asked if you want to "completely uninstall" or (restore image). You will choose to restore image
This restored image allows you to update your phone and you still retain root AS LONG AS YOU DON'T RESTART. So you do just that, you update and DON'T restart
After the update go back to magisk manager and press install. You will be asked how you want to install it (patch boot image, direct install etc). Select inactive slot.
Reset phone and enjoy!
But I walk against a wall against at step 3
Magisk never backed up my original boot image as I flashed it through fastboot. Where do I place the original image for magisk to find it? And what will my file have to be called? Magisk is probably looking for a certain file name
Then I also have a problem with step 5. I only get the option to direct install and patch boot image. I am not given the option to install it in an inactive slot.
What do you guys do to update your phone? Install it manually through fastboot? I would just prefer to skip the fastboot part going on. I just the commands so rarely that I always forget them and always have to look them up xD. Just seeing if this community know something I don't