SuperSU binary needs to be updated failure - ZTE Axon 7 Questions & Answers

I'm pretty sure I have root now, but I can't actually run some apps that needs root access (like Ap Ops). Everytime I start up SuperSU, it says the binary needs to be updated. However, it never does it. How do I force it to install? Is there anyway to do it? Thanks.

Flash the most up to date SuperSU zip using TWRP.

Related

Unable to root after 4.3 Security

So I installed the 4.3 security update, and half way through I got "Error!" and "No command.". I waited, and eventually it rebooted and my root was lost, as usual. Anyway, I tried reinstalling SuperSU from temporary recovery and now whever I open SuperSU it just tells me that I have no SU binary installed.
Can anyone advise me on what to do? I'm using the flashable zip from Chainfire's site.
Edit: Fixed. I'm dumb, I was flashing an old, non-4.3 compatible zip.

This shouldn't be frustrating - binary update.

I tried a couple of root apps, they didn't work. F***. Adaway and Music2SD. Both tell me that my rooted S4 isn't rooted. I have prerooted MF9, flashed via TWRP. It included SuperSU, with 1.1.3 binary (I think). Okay, after no search results I decided to do something on my own.
First, I opened SuperSU and told it to install itself as a system app. Then, I installed ChainsDD Superuser. That's when I found out my binary was out of date. I chose to update it via Superuser. For some reason or another, it said it didn't update. I went to app manager, cleared data and uninstalled updates for SuperSU. I updated it in the play store and opened it. Then, it told me my binary was out of date - woo! Wait.. normal method didn't work - "Installation Failed!" Okay, try TWRP/CWM method. It rebooted into recovery, flashed some stuff before I could read it, and restarted. Booted right back up. I opened Superuser and it said I was on v0. Went to ChainsDD's site and downloaded the 3.1.3 ARM to flash in recovery. I did that, still nothing. Now SuperSU and Superuser are permanently installed apps (I now have no root to delete them). Whatever. I ran CF-Auto-Root in Odin. After that, both SuperSU and Superuser were removed. I have nothing now.
My question is, what's the best way to get the latest binary on MF9? If i restore from Nandroid, how should I update? If I start from scratch, what binary will I get from CF-Auto-Root?
UPDATE: I'm back to rooted, with SuperSU. I got the update binary notice and chose the normal method. It updated just fine, but I still can't use Adaway or Music2SD. Superuser by ChainsDD still shows v0.. all of my normal apps have root access just fine.
FIX!: My ignorance is to blame here - XPrivacy blocks root access by default on Adaway and Music2SD... I didn't realize it did that!

Trouble rooting on 4.4.2

I've had trouble rooting since I updated to stock 4.4.2. Device has been unlocked & rooted before the update. It still is unlocked, of course.
I've tried using WugFresh's toolkit but that doesn't work. I've tried manually flashing TWRP (v2.6.3.1) and SuperSU (v1.8.5). They install without any errors but when I boot to system and open SuperSU I get the "There is no SU binary installed, and SuperSU cannot install it." error.
Help? Suggestions?
Quit using tool kits.(better yet never start using them!) you don't need tool kits for nexus devices and learning command line replace and repair commands will save you much heartache and heartburn.
Check and validate you see the unlocked lock on the screen at boot time.
Go to the Google play store and install the Chainfire SuperSU binary from there it will prompt you to select either stock or custom recovery reboot.
If after that you are still un-rooted re-download the root patch and re-apply.
planet_x69 said:
Quit using tool kits.(better yet never start using them!) you don't need tool kits for nexus devices and learning command line replace and repair commands will save you much heartache and heartburn.
Check and validate you see the unlocked lock on the screen at boot time.
Go to the Google play store and install the Chainfire SuperSU binary from there it will prompt you to select either stock or custom recovery reboot.
If after that you are still un-rooted re-download the root patch and re-apply.
Click to expand...
Click to collapse
I stopped using the toolkit after it wouldn't work. I already have the latest SuperSU installed and am using TWRP as my custom recovery. When I open SuperSU it says, "There is no su binary installed" and then closes. That's it. I can't even remove SuperSU because it's installed as a system app and while not rooted I cannot uninstall system apps.

PHH's Root Disappeared

Hi Guys.
As the title suggests root access suddenly disappeared from my nexus 6p yesterday.
DigitalHigh rom 7.0 was flashed through the latest twrp (3.0.2-2) and everything was running fine. I got the notification that the SU binary is out of date from PHH's SuperUser. Opened it but nothing really happened. So I downloaded superSU and suddenly it prompted me that the device isn't rooted. Being unfamiliar with PHH's SU I decided to flash the latest SuperSu through TWRP but the phone wouldn't boot.
Right now it has been restored to a backup taken just before flashing SuperSU which means everything is running fine and even android pay works however there's no root access. Is there something specific that might have caused this?
Are there any ways to re-gain root?
Haven't gone through the process of a clean flash yet as the phone is needed for work however even if all of that is done the SU binary will still need to be updated. Is there a different method for updating PHH's root?
So far I have tried clearing cache etc. but noting worked.
apostol96t said:
Are there any ways to re-gain root?
Click to expand...
Click to collapse
Phhusson's superuser and SuperSU don't mix. If you're back to booted, but not rooted with Phh, you'll need to either flash one of the Nougat boot images from the nexus/angler folder or the latest superuser.zip (I think the latest is r229) from http://superuser.phh.me

Help to root so far unsuccessful Telstra SM-G900I

G'day,
I have followed the instruction using the download on this page for SM-G900I without success. https://forum.xda-developers.com/showthread.php?t=2696537
I found another Telstra user who used the kltezt version, so I tried with the version from https://autoroot.chainfire.eu/ even though the build version is different. This time SuperSU asked to disable knox, I did so, verify with Root Checker, doesn't work. Reinstalled using Odin without auto reboot, SuperSU asked for New user or expert, I chose New User, nothing.
EDIT---
When using Root Checker it would ask for permission to verify, I would try and click button which would not work.
I have just uninstalled SuperSU and Root Checker worked. I have reinstalled SuperSU updated binary and restarted and now Root Checker fails.
Android: 6.0.1
AP: G900IDVU1CQD1
Any suggestions?
Samuel
G'day sir.
CF-Autoroot is the old method of rooting the S5 and it will fail in some cases because it is no longer updated. The current method of rooting the S5 is to use either the SuperSU zip from the SuperSU XDA thread or magisk from the Magisk thread. What's the difference? Magisk allows to hide root, superSU works better with some apps and with xposed.
Go to the TWRP website, locate the files for the G900F (klte) and download the latest version to your PC. Then flash the .tar file in ODIN under AP/PDA.
Immediately after flashing, you must reboot to recovery (hold power button, home button, volume up button) until you see "rebooting to recovery". Once in TWRP, flash the SuperSU or magisk zip then reboot.
All the best, Saber
Thanks for your reply. Though had to go do some hard Googling to fill in the gaps of the installation process, like adding the SuperSU zip to the memory card.
I was about to say it didn't work again, but then it clicked why I may not have been able to grant access in the past. I use the night overlay app "Twilight" and I know the system doesn't like it running when doing certain tasks and asks you to disable the overlay. I disabled Twilight and it worked. Double checked and it is definitely the problem. All that for probably nothing.
Now I can install apps to the external SD, well that's the plan anyway. I've had enough manually moving them over manually to make space.
Thanks once again for your assistance!
Samuel

Categories

Resources