yashsingh1/xdaforums huggingface dataset:
[SuperSU] shao2004:
How update binary su

I have the same problem. But I found solution.

What need :

Android Terminal

Files Manager with Root : (Root Browser, Root Explorer or another )

Archive updatesu.zip : drive.google.com/file/d/0B1othcjTtZ2kZGtaWC16c2Rncjg/view

1. Unzip updatesu.zip and copy files:

.has_su_daemon
.installed_su_daemon
install-recovery.sh
in : /system/etc

2. Set the permissions

for file .has_su_daemon : rw-r--r (0644)
for file .installed_su_daemon : rw---- (0600)
for file install-recovery.sh : rwxr-xr-x (0755)

3. In /system/bin create folder ".ext" (without "")

Set the permissions : drwx--x--x (0711)

4.Copy file su from /system/xbin in /system/bin/.ext

Rename su on .su and set the permissions : rwxr-xr-x (0755)

5.Start Android Terminal

6. Type the command:

su
mount -o rw,remount /system
ln -s /system/etc/install-recovery.sh /system/bin/install-recovery.sh
/system/xbin/su --install
reboot

7. After reboot, try to update binary file su by method "Normal" in app SuperSU.

I got a successful result !
[SuperSU] Ch3vr0n:
Nvm
[SuperSU] NaviPR:
Hey,

Yesterday I rooted my Xperia M4 Aqua E2303 with SuperSU and TWRP.

The factory ROM is an Android 6.0.1 26.3.A.1.33. In the process of unlocking the bootloader, rooting and installing recovery, I ended up with SuperSU 2.78 and TWRP 3.0.2-0 on my phone.

When I went back to configuring my phone after the mandatory factory reset, I started to debloat it from apps I didn't need with Titanium Backup, and updating others that I needed through Google Play. After doing that, I looked up the SuperSU app on Google Play and it said there was an update.

Note:

Google Play didn't automatically notify me about this update like it does with other apps, I had to find it by myself.

After updating I opened the SuperSU app and it says that the SU binary needs to be updated.

When I press "Cancel" it says the SuperSU may not work properly without the updated binary. When I press "Continue" it tries to install, but after a minute or so just says that the installation failed and I should reboot my phone and try again. Doing that does not help.

I checked out SuperSU's guide about "How to install". I downloaded the .zip manually from their site and tried using TWRP to manually install the program from the SD card.

Attached you will find a picture of what my phone says during the update.

After rebooting when I open SuperSU it gives me the same message about the binary and that's pretty much it.

Wat do?

Can I still use SuperSU as it is?

Can I go back to 2.78? If so, is it safe to just flash the previous version?

Or do I need to go through a factory reset and rooting + installing recovery all over again via Fastboot?

Thanks in advance for any replies.
[SuperSU] tom_lt25i:
Yep same problem here

stucks at the boot screen from lineage.

No SuperSu previsouly installed

Version:

Installed the SuperSu from Playstore Today.

Os:

lineage-14.1-20170126-UNOFFICIAL-tsubasa

TWRP:

twrp-3.0.2-0-tsubasa
[SuperSU] CaptainPhantom:
Thanks for confirming that the issue still exists. Was wondering if I should try again. Still running an old SuperSU, albeit without issues fortunately.

I really wish this would get sorted out.
[SuperSU] persiomenezes:
About what old version are you talking?
[SuperSU] kennenmain:
didnt work for me either
[SuperSU] dquelal:
I have the same problem, any advice please? thanks
[SuperSU] Lucifer20:
I am using Moto g3 using RR 5.8.1and have similar problem. The SuperSU app tells me to update binary even if I had flashed V2.79. more over after twrp flash I am getting bootloop
[SuperSU] mr.natural:
Try clearing dalvick and cache.
[SuperSU] jamespark:
SuperSU 2.79 SR3 will not survive reboot

Pixel (Google Play version), after the feb update (nof26v), when I flash 2.79 SR3, it will not survive reboot. Initial reboot system works after I flash SU. However, if I reboot it afterwards for any reason, it only boots into recovery unless I flash stock boot.img and sideload the OTA. Please see below link for longer description:

https://xdaforums.com/pixel/help/supersu-2-79-sr3-survive-reboot-t3563228

Thanks in advance for any help you might be able to offer!
[SuperSU] gdude:
Thanks for all your great work.

Like others, I am seeing a softw bootloop (dancing dots) after application of boot-to-root.img

on a Pixel device with a recent security update. This is a 128G Pixel running 7.1.1 with a Feb 5, 2017 security patch.

ro.boot.hardware : sailfish

ro.boot.hardware.color : GRA00

ro.boot.hardware.ddr : 4096MB,Hynix,LPDDR4

ro.boot.hardware.revision : PVT

ro.boot.hardware.ufs : 128GB,Toshiba

ro.boot.htc.hrdump : detected

ro.boot.keymaster : 1

ro.boot.oem_unlock_support : 1

ro.boot.qf.st : 2

ro.boot.ramdump.opt : mem@2g:2g,mem@4g:2g

ro.boot.ramdump_enable : 0

ro.boot.slot_suffix : _a

ro.boot.verifiedbootstate : orange

ro.boot.veritymode : enforcing

ro.boot.wificountrycode : US

ro.bootimage.build.date : Fri Jan 13 15:26:59 UTC 2017

ro.bootimage.build.date.utc : 1484321219

ro.bootimage.build.fingerprint : google/sailfish/sailfish:7.1.1/NOF26W/3637559:user/release-keys

[ after the problem it seems that I reflashed with the NOF26W OTA by accident, instead of NOF26V, but this is a phone from Google that is on Fi, not Rogers ]
[SuperSU] morgan1985:
yeah i had same problem, sgs5 using twrp latest, reserection remix naugat, i understand it comes with su but i want the supersu app, so i fupdated then got bootloop is there any way to make it work ? and which supersu file should i flash from recovery ?
[SuperSU] FebryRamahdana:
how to update supersu binary S7 edge qualcomm

i have follow the instruction to root and i made it

but when i open superSU, it says that i have to update the binary, i click the normal option but always failed.

what should i do?
[SuperSU] akemon:
Access the :victory:
[SuperSU] rezaeee:
I don't know where to ask my question?

Hi

I just wanted to root my galaxy note 5 (sm-n920c (dual sim)). I used

SpaceX-Kernel-v0.1_N920CD(official).tar.md5

and

SpaceX-Kernel-v0.1_N920T(official).tar.md5

and

Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5

but they didn't work an gave me an error about seandroid with red line above the startup page.

So I searched again and found this tutorial galaxynote5root.com/galaxy-note-5-root/how-to-root-galaxy-note-5-on-android-7-0-nougat-w-magisk/2

everything was ok but in last step I got this error:

Updater process ended with ERROR: 1
Error installing zip file'/sdcard/samsung-antiroot-removal-2.4.zip'

Also I have 6.4G free space on my phone!

What's the problem and how can I fix it?
[SuperSU] j_moreno91:
Hi Guys, please help me. I flashed my moto g peregrine with the latest lineage os version. After that, i enable the the root option via TWRP with the addonsu.

After that, i downloaded via google store the SuperSU app i it asks to update the binary. I choosed the option via "TWRP" since the other option didn't work. After that, my phone is on bootloop (the symbol of lineage os is moving) and i can't acess to recovery mode.

What i can do?
[SuperSU] Ch3vr0n:
"enable root via twrp with addonsu". Should have tried SU directly first. What can you do? Fastboot BOOT the recovery and flash the rom again
[SuperSU] j_moreno91:
Thanks for the answer. I already flashed the ROM.
[SuperSU] Panic84:
hello, I installed supersu pro on miui 7 (android 5.1.1) and there is some modules that are not supported. For example intelli3g app from play store. Maybe is a noob question but I dont know how to enable this app in superSU.
[SuperSU] Ch3vr0n:
You don't enable an app in SuperSU, when an app checks for / requests root permission you get a popup. Then you either approve or deny. That's it.
[SuperSU] chwiejak:
Hello Guys,

Can you help me?

Device: onyx

Os: cm13 rooted

I have problem with binary update, normal way failed, twrp way causing boot problem (freze on cm13 boot logo)

It is still possible to update binary?

Thanks
[SuperSU] ProfEngr:
Just updated Note 2 via Play Store. Chose Normal method when prompted by SSU. Process failed. Not SSU tells me there's no root. Hopefully I can find a zip to flash in TWRP that won't bootloop or freeze.
[SuperSU] outlawman007:
Same here on the Nexus 5X, did a factory reset and it did not help
[SuperSU] A.lemane:
is it compatible with Emui 5 ?
[SuperSU] mikeandjaimie:
Same deal.. PureNexus on 6P, got notification of an update from Play Store, after which is told me the binary needed updating. Went through as usual and it said that it failed, now I no longer have root and it keeps telling me where I can find the info to root it. I have an old SR3 release from last time I flashed my phone, so attempting to re-flash that to fix.
[SuperSU] ktmom:
There is a hiccup with the newest release. Unfortunately, Google Play doesn't allow the developer to roll back. Please see [MENTION=631273]Chainfire[/MENTION]'s post in the stable thread.
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION] had stated that the v2.81, from the Play Store, was only a "Staged Rollout" as he explained it, even further, within the following post:

https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/post72428986

Just an FYI... :)

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] wilsonhlacerda:
But It is always possible for developers to publish a new release on Google Play, no matter if it is really a new piece of code or just a copy of an old one. Don't want to put a copy? Ok, just change 1 bit.

In simple words: yes, can roll back by releasing a new "fake version" that in fact is the good old proven version.

But that was not the option taken by developer on current SU case, even as a temporary quick fix, a stop bleeding strategy. And thus the current problematic v2.81 is continuously spreading worldwide through Google Play, every minute, more and more users loosing root and even getting bootloop (sometimes without possibility to recover without losing data).
[SuperSU] ktmom:
2.81 was a roll back. Still broke stuff.

IMHO, a larger part of the problem are blind updates of invasive apps like this. At a minimum, checking the stable thread would have shown that problems were developing. To blindly install or update a root app of all things is asking for trouble. It's hard to feel badly for people when the information has been out there for hours before their trouble began.

If it was simply a calendar app or a music player then I'd understand the frustration.
[SuperSU] Ibuprophen:
Please read the first thread that also refers to the second thread.

Both are from Chainfire...

https://xdaforums.com/showpost.php?p=72430541&postcount=9844

https://xdaforums.com/showpost.php?p=72429329&postcount=9810

Please note the reference to the BindFix file within the second link (above).

It's also encouraged for users to disregard/ignore the Play Store SuperSU update for v2.81 as it has issues too.

I, personally, am forced to reflash the Stable v2.79 until the issues can be resolved by Chainfire.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] wilsonhlacerda:
No, it was not. As far as was written it was some kind of a mixed v2.79 and v2. 80. And people updating from v2.79 to current v2. 81 today on Google Play are having problems (see comments there), what prooves that's the case.

A good "roll back" would be a pure copy of v2.79....thus new people updating would not have any problems.

---------- Post added at 07:38 PM ---------- Previous post was at 07:33 PM ----------

Cool. Now just tell this to everyone, worldwide, all languages, that even don't know about xda. :) Got it? That's the problem.

By the way I didn't have any problem. I always set manual updates for critical apps, like su. And when taking risks I be sure to have nandroid backups.
[SuperSU] xxxtncxxx:
So I understand there are issues with 2.81 it fails for me on the SePolicy patch on recovery zip and Play Store update binary fails and root is lost after. I am not posting looking for help just thought you could use the info, if you need me to do anything else just let me know. I rolled back to 2.79 so building an su.log via adb shell as instructed is only gonna show my good SuperSU install info (I think). Here is my recovery log hope it helps.

BUY SuperSU PRO!!!

Pixel XL

Android 7.1.2 LineageOS base

Latest build 05/26/2017 of https://xdaforums.com/pixel-xl/development/rom-team-octos-oct-n-t3533511
[SuperSU] iandsteve-xda:
Possible repair method when unable to flash (e.g. locked bootloader)

I lost root when the binary update failed with v2.80. I spent almost a whole day attempting to get back to working SuperSU using a number of different versions. I was able to re-root the device via various non-SuperSU methods including both apk and adb based solutions BUT on attempting to switch back to SuperSU and update the su binary (e.g. using Super-sume etc.), I was always met with either a binary occupied or an installation failed error message. I finally found a method that worked for me (Huawei Y360, Android 4.4.2, locked bootloader.) (I'm not sure whether all these steps were completely necessary or not but better safe than sorry):

Installed the LATEST version of the KingRoot apk.

Rooted the device with KingRoot.

Used SuperRoot to check that the binary is showing as KingRoot (3.48 or 3.78 I think, I can't quite remember, but that's not important.)

Rebooted.

Fully unrooted with KingRoot.

(Some earlier versions of KingRoot did NOT unroot correctly so be sure to have downloaded the latest version. I think this may have been the vital step that cleaned up whatever the issue was with updating the su binary.)

Rebooted.

Used SuperRoot to check that there was now NO su binary present at all.

Re-installed KingRoot.

Rooted the device AGAIN with KingRoot.

Installed SuperSU 2.79 SR3 alongside KingRoot (so that SuperSU could use KingRoot to get root authorisation.)

Updated the su binary in SuperSU. (This MIGHT still have given me an error message but be sure to check with SuperRoot afterwards anyway because it seemed to have worked despite the error message.) (SuperSU also failed to uninstall KingRoot afterwards when it offered to uninstall conflicting apps.)

Used SuperRoot to check that the su binary is now showing as SuperSU 2.79.

Manually uninstalled KingRoot (and any other apps it has installed, such as Purify) (WITHOUT unrooting in KingRoot!)

Re-opened SuperSU after uninstalling KingRoot and was prompted to update the su binary AGAIN. This time it said that it WAS successful.

Rebooted and tested: I could now get root authorisation via SuperSU again!

No promises, obviously! But it worked for me so I hope it helps someone else too!
[SuperSU] truelies1:
I am using HTC M7, the twrp is 3.0.0. I tried 2.79 sr3, but it can't boot, just stay at animation when updating binary. Only install 2.46 can boot my phone. Certainly 2.80 and 2.81 not work. What's the reason for this? Does new edition of SuperSU can only work on newest twrp?
[SuperSU] Lone Stranger:
Install Causes Unrecoverable Bootloop on Moto X (xt1058)

Phone: Moto X 2013, xt1058, US- ATT, unlocked

Version: 5.1, rooted via SuperSU, TWRP installed and functioning.

No other Superusery apps, Xposed or BusyBox installed, ever.

There's a few threads about SuperSU update failures, so if there's a better one to post in please let me know.

A few days ago I took an update to SuperSU (I can't find out which version) and mistakenly selected to install via TWRP instead of "normal." As I recall it rebooted to TWRP and I don't remember doing anything except rebooting normally. Everything seemed to be working as usual.

Sunday night it asked to be updated again, and again without looking at which version, I selected to install via the "normal" method, it rebooted to the Android splash screen and stays there. It will reboot using the power button, but again it stays on the splash screen. I left it all night like this. In this state it discharges the full battery in a few hours. In normal use the battery lasts 2 days.

It won't boot into recovery, and with the splash screen displaying, the usb connection won't work for adb. RSD Lite doesn't see it either. I've checked the drivers and there doesn't seem to be any problems. It appears the phone is stuck at a point where the usb isn't active except for battery charging.

Any help is greatly appreciated.
[SuperSU] shadow2797:
I have an HTC One m7, originally T-Mobile, but rooted S-Off and changed to International. I have a stock 5.0.2 (or whatever the latest possible version for my phone is) ROM.

SuperSU prompted me to update the binaries about a week ago, which I've done before and it went smoothly then. I got tired of the notification, so I decided to do it this morning. I selected the CWM/TWRP method. It booted into recovery flashed update.zip and rebooted. It appeared to hang at the HTC One boot screen. I left it like that for about 15 minutes and then tried rebooting. It appears I'm in a boot loop and I'm not sure how to proceed. I tried installing update.zip again from /cache/recovery but no dice, same thing.

How do I get back to a previous version? I have 2.65 on my phone still from originally rooting it, but I don't know how to uninstall the current version, nor do I know which version it is. I'm also not sure if 2.65 is compatible with Android 5.0.2. So if I need 2.79, how do I get that on my phone without boot? ADB?

Info Dump:

M7_UL PVT SHIP S-OFF RH

CID-BS_US001

HBOOT - 1.61.0000

OS 7.17.1540.51

TWRP 3.0.M0-0
[SuperSU] Lone Stranger:
Fixed It

On my Moto X, I was eventually able to boot into fastboot by repeatedly pressing the volume down button at a rate of about twice per second. (Holding it down or any other method would not lead to fastboot.)

Once in fastboot I booted into TWRP and restored a full backup from a few months ago and it worked.

I updated everything except SuperSU, used it for a few days to make sure it was the way I wanted it, then backed up through TWRP.
[SuperSU] shadow2797:
I was able to fix my problem by using unSU. I haven't rerooted yet, but that part is pretty straightforward. Hopefully, this helps someone else.
[SuperSU] rizla2:
Please help me.... I assume I have installed updated to that infamous 2.80 few days ago...installed a binary and all that. Today, I rebooted my phone and got stuck in bootloop....only advice I found on thread was to flash 2.79 zip...so I went into recovery, cleared cache and dalvik and flashed it, but the phone is still bootlooping. I disabled xposed, assuming it might help(used a zip for disabling it which apparently makes a disabled file in xposed's folder...) but that didn't help either. I really need to fix this... Anyways, I am using Sony Xperia Z1 Compact with dual recovery(PhilZ Touch 6.59.0, ClockworkMod v6.0.5.1 an TWRP v.2.8.7.0), locked bootloader cause I can't unlock it on this one... I hope somebody can guide me through this and help soon....
[SuperSU] ktmom:
Try osm0sis' unsu script. If that fixes your bootloop, you'll be unrooted. Then go back to what had worked. I'd suggest you turn off auto update in the play store for SuperSu.

Edit: You need to flash that file I linked to in recovery. I usually link to the thread [emoji4]

I would also suggest you search the stable and beta threads for your device.
[SuperSU] rizla2:
Actually, I have managed to fix it and the solution was a lot simpler than expected, I simply flashed THIS version of 2.79. [MENTION=631273]Chainfire[/MENTION] linked this version in official post: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip and it seems to be different, I've seen other people reporting that this one does not fix the issue while the one on the official supersu site does...Might help some other people too...
[SuperSU] spencermathews:
Moto X 2013 Optimizing

I'm currently running SuperSU 2.79 since all of my attempts to upgrade binary and APK to 2.82 resulted in all apps optimizing at every boot.

I'm curious what the status is on this bug, which has already been reported by others.

Until this is fixed I intend to stay with 2.79, but on I every boot I get "The SU binary needs to be updated!" message. Is there a way to suppress this message?

Thanks!

Spencer

Moto X 2013 / XT1060 32GB / 5.1 LPAS23.12-39.7.1
[SuperSU] ianfebay:
Sony Z5 E5823 Android 7.0 was rooted fine. Playstore updated SuperSu to 2.82 and now I keep getting message 'The SU Binary needs to be updated'. The binary update fails. Is this possibly going to be fixed?
[SuperSU] ktmom:
The 2.82 SR1 in the beta thread will probably fix it. You'll have to flash in recovery. Search that thread for your Z5 device, and you'll see there were problems. There was a "test" release that would be incorporated into the SR 1 release.
[SuperSU] cyb3rphr33k:
gpd xd (gaming tablet)

4.4.4 custom rom legacy 1.8

http://boards.dingoonity.org/gpd-android-devices/(rom)-legacyrom-kitkat-for-gpd-xd/

2.82 free

after updating su binary from notification, my home and recent button doesnt work. recent works if i long press it but shows the option menu as expected.

i tested twice becayse first time i didnt know what caused it but today i reflashed the rom and install my apps one at a time.

im convinced that su caused this error.

is there a way to go to previous version or some kind of fix?

thank you
[SuperSU] Dave_247:
I'm not sure in which topic to post this, but I guess this would be the best place.

My Xperia X gets stuck in an endless bootloop if I try flashing 2.8.2 SR3 with systemless SBIN mode using the aroma configurator, and changing nothing but the install method. I'm running the stock Sony firmware 34.3.A.0.194 with the Vodaphone AU carrier, which is Android 7.1.1. I have also used ta_poc to patch my bootloader and disable Sony RIC before installing SuperSU as otherwise it would fail to install.

I am able to root and boot successfully in regular systemless mode however with no issues however.

Attached my kernel crash log after over 5 consecutive reboots.
[SuperSU] ktmom:
[MENTION=4925991]Dave_247[/MENTION], I'd read through and post in the beta thread.
[SuperSU] Munib2:
Plz help "How would you like to install the binary".

Hi,

Sorry if this is in the wrong thread, I found posts with the same message regarding the above prompt. But elsewhere I am struggling to find the same problem as mine where I cannot do anything on my phone apart from go into CWM recovery.

I opened SuperSU ( a very old version, installed ages ago) on my Samsung galaxy S4 I9505 (UK unlocked) after a long time and it said:

"If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?"

Out of the options, Normal and TWRP/CWM, I clicked TWRP/CWM as when I rooted my phone a long time ago, I used Odin to flash CWM.

It restarted and now after the samsung logo, it gets stuck and it says "unfortunately app/service has stopped" and I cannot do anything else, it loops through all the apps/services and says they have stopped.

I don't have a recent backup of my phone so I am really stuck and lost as to what to do. I have managed to flash again the same CWM recovery I used the last time, can I use CWM to create a backup? And how can I fix this issue please.

I also don't know what firmware version, SuperSu version etc as I dabbled in rooting my phone around two years ago and have not opened superSu since.

Any help would be greatly appreciated. Could I get android back the way it was working before I opened SuperSU and clicked TWRP/CWM without losing any data?

I would be forever grateful for any help. This is my only phone and at the moment I am stuck, I cannot do anything to fix the issue.

Thanks in advance.