yashsingh1/xdaforums huggingface dataset:
[SuperSU] DannyR49:
Xiaomi Redmi 3 w/- CM14.1 Nougat 7.1.1

Working again from .AU with test version.

v2.82 fixed loss of root (SuperSU-v2.82-CCMT-GooglePlay.zip) after going back to 2.79sr3 first to confirm regain of root.

PS: I wish someone could address this SAMBA issue for Nougat:

http://goo.gl/ZThzfm
[SuperSU] wptski:
Installed LineageOS-14.1 Nougat 7.1.1 and SuperSU v2.82. No problems so far with a newer ROM than the three year old that I was using before.
[SuperSU] WiggleCat:
I uninstalled SuperSU and SuperSU Pro 2.8.2. Using ADB and the unzipped 2.8.1 package I deleted the su file out of /system/xbin/ because my ROM itself is permanently rooted so ADB still has root access. I then pushed the su file from the arm64 folder in the unpacked 2.8.1 archive to replace the previous one in /system/xbin and pushed superuser.apk from the common folder to /system/app and rebooted.

When I opened SuperSU it said root wasn't detected but once again advanced root checker says that root access is properly configured for the binary and can be executed to grant root access. For some reason it also says the binary version is 2.8.2 despite having been pushed from the 2.8.1 unpacked zip file. After I'd deleted the su binary file using ADB I rebooted and checked with advanced root checker and the binary was in fact gone so I don't understand how the updated binary was replaced. Every time I pushed or deleted any files I did so while in recovery mode to avoid the remounting nightmare.

If I'm supposed to delete more files than just the one su file, or I'm supposed to push others to different locations please let me know. The phone boots up just fine, I'm actually using it to write this.

Edit: I don't have a custom recovery and the bootloader just boots into download mode so there's also no fastboot. That's why I haven't just flashed the zip.
[SuperSU] droseofc:
In terminal emulator I entered su and granted permissions from Magisk, then I did "echo SYSTEMLESS=false>>/data/.supersu" and then entered reboot in terminal emulator. After it rebooted I went to supersu, and it had the option to install to system. I installed it to system, and when it closed I rebooted, once it rebooted it now says SuperSU is already a system app. So that part is OK. But, I also have Magisk through all of this, and when I open supersu now it says that the binary is occupied (assuming by Magisk) and I may try in a min to flash the magisk uninstaller and see if supersu gets the binary and remains system. The steps I took before I did the commands were downloaded the systemmode 2.82 zip from the supersu systemmode thread found on this su forum. Unzipped it, installed the apk from the common folder, and then the commands.
[SuperSU] erfandl:
Google play 2.81 worked on XPERIA Z Ultra Android 5.1.1
[SuperSU] crisis_trustee:
UPDATE-SuperSU-v2.82-20170526223454.zip

Link - https://www.androidfilehost.com/?fid=889764386195902173

UPDATE-SuperSU-v2.82-20170526223454.zip.md5

Link - https://www.androidfilehost.com/?fid=889764386195902172

I have flashed this UPDATE-SuperSU-v2.82 on my Nexus 5 via TWRP 3.1.1-0
[SuperSU] Adarsh balu:
So v2.82 is not working for moto g4 plus...

I was just looking to flash it .Since there is a problem it can wait
[SuperSU] droseofc:
got myself in quite the pickle. How do you reverse the echo SYSTEMLESS=false>>/data/.supersu in the terminal in TWRP? I tried doing =true but it continues to do system mode as it shows it mounting /system and installing system mode on TWRP, even with systemless zips. And it bootloops. Only way I can get I to boot is by flashing magisk. I even tried wiping and reflashing rom, and it still did the system mode. Fricknfrack

---------- Post added at 02:07 AM ---------- Previous post was at 02:06 AM ----------

CPU about to catch on fire and everything
[SuperSU] veez21:
delete .supersu

here's how in terminal (just for fun :laugh:)

rm -f /data/.supersu
[SuperSU] ashyx:
I mean it will boot loop if you attempt to use system mode on nougat firmware.

It's not compatible yet. Ask Chainfire.

Also just for confirmation:

https://xdaforums.com/showpost.php?p=72457981&postcount=10049

---------- Post added at 08:59 AM ---------- Previous post was at 08:29 AM ----------

I did warn about this. I'm not sure why you didn't use the compatibility mode as posted previously. It would have solved your issue.

Unfortunately you have now installed Supersu to system and compromised your system partition.

Delete /data/.supersu and /data/su.img then reflash your stock firmware.

Then reroot.
[SuperSU] flroots:
Actually I'm not sure what caused me to loose root. All I can say with certainty is that re-installing 2.79 restored it. I'm just speculating that an auto update may have caused it. I was hoping someone could tell me what the issue was?
[SuperSU] droseofc:
lol. I know, its just that it was installed as system mode, only magisk was screwing things up I thought/think. SO. I wiped data/system/cache, reflashed rom, selected the instal with supersu option instead of magisk this time, now going to run the same command that I did before in terminal emulator to get it to say sytem mode and hopefully that binary occupied does not come up again. While I was in a nightmare, I flashed magisk uninstaller, reflashed su and back and forth like 3 times, then finally got it to boot by flashing magisk, then going into flashfire and flashing the magisk uninstaller and injecting root. But when it rebooted supersu kept asking for root permissions for itself from itself. I was never able to click grant or deny, as it basically froze when I tried, not the phone, just su. Anyways, round two DING DING..

---------- Post added at 03:05 AM ---------- Previous post was at 03:03 AM ----------

But the thing is I was almost there....
[SuperSU] Ps24u:
So 2.82 is now live on Play and there isn't even a warning for Xperia users, I'm sorry but this is irresponsible.

2.82 on Xperia WILL bootloop with 100% certainty, all owners will be screwed if they don't have a TWRP backup and a way to flash it.

Imagine you're on a trip far from home, you install this update which renders your phone useless, not good at all.

Imho no update past "fake" 2.81 should have been pushed until ALL issues were resolved. This is a debacle of epic proportions.

I understand Chainfire is doing all he can to resolve this issue, i'm sure working around the clock.

But to the new owner, what exactly the **** are you doing..
[SuperSU] DEVILOPS 007:
You clearly didn't pay much attention to the app. The app that updated was supersu Pro which is simply the unlocked for Pro features and not the app itself. Pay more attention to what updated before posting a rant that isn't just.
[SuperSU] Chainfire:
I understand your frustration, but this resolution is the lesser of two evils.

Not all Xperia users are affected, there are only a handful here in this thread, and I don't see anyone scrambling to actually help find and fix the problem. Apparently the Xperia problem has been around for a few beta releases as well, and was never reported.

As I stated before, I need an Xperia user who is actually experiencing the problem to be available for live testing for a few hours. Without that, this problem will not get solved. It is not reproducable on my or CCMT's units.

In the mean-time, the root-loos issue affects probably a hundred times as many users or more... it's a simple matter of inconveniencing the least amount of users possible, and Xperia users are far in the minority.
[SuperSU] Ps24u:
bull****.

View attachment 4163875
[SuperSU] DEVILOPS 007:
:eek:
[SuperSU] Adarsh balu:
So ur using Xt1644

Im XT 1643

I will try to do on v2.82... Busy right now...I will test and get back to you:)
[SuperSU] CyberZeus1977:
Here in Italy, Play Store shows 2.81.

No 2.82 yet...

Sent from Enterprise bridge
[SuperSU] Ps24u:
Yeah not all servers are updated exactly at the same time. Sometimes rebooting the device also forces some kind of refresh. Anyway, at least for some people 2.82 IS live.

Chainfire, I understand it's the lesser of 2 evils, but at least in the What's New section of the app, it certainly wouldn't hurt to emphasize that "Xperia users should withhold from installing the update now, until further testing is done", or something..
[SuperSU] samhhmobil:
Bootloop on HTC One(M7) still happens even with 2.82

At first again thanks to the great work of the SuperSU team, and greetings from Germany.

Nevertheless, the hanging boot screen (bootloop??) happens even with the last update 2.82, on HTC One-M7 (HTC Stock ROM Android 5.0.2, TWRP 3.0.2-0)

So you see, this bootloop does not affect only Xperia users, but even HTC One's.

Now I found out not to crash the whole system again, but from TWRP I could install

via adb sideload the ZIP "unSU", and it uninstalls the complete SuperSU. After that the system boots

cleanly, and installing the 2.79 is clean and the system runs well.

But it seems, there is much more work to do to find that awful bug. I just won't think about, that this would have been happen to me, when travelling with my "main" phone anywhere in Russia, and nobody's there to help me with the necessary computer equipment...

How can I help you?

Thank you again,

"samhhmobil"
[SuperSU] Rebel2k:
[MENTION=787050]samh[/MENTION]mobile where can we get the unSU zip file?

I wish I could help for the Xperia issue, so sad my own Xperia died a couple of months ago... :(
[SuperSU] Chainfire:
This sometimes happens when you downgrade through zip. Uninstall SuperSU (adb uninstall eu.chainfire.supersu, or possibly through Settings->Apps or Play Store, I always use the adb variant), reboot, reinstall the APK (easiest to find Superuser.apk in the ZIP I guess?)

See my comment above.

I'm reading your posts but I'm at a loss about how to fix the mess you are currently in. I'd recommend re-flashing stock firmware and starting from scratch.

I have an N7100 around here somewhere, I'll see about testing this. Do you have a download link for the exact ROM you are using?

Is there anything else of note? Are you running any specific root apps?

If there is a crash, please provide a logcat of that crash.

ODP2 is not officially supported yet. It sort of works on some of the devices.

I have better working code in a different branch that will become the next BETA/SR version, but it has to wait for the Play version to be fixed first.

Not officially. See my note above.

It is precisely sukernel that is limited, the rest of SuperSU really doesn't care about which compression is used. LZMA is not currently supported, LZ4 support (new format only; at least for the kernel, not sure yet for ramdisk) is coming next BETA/SR version, because it is used in ODP2.

The problem is that the SuperSU ZIP supports 7 different CPU architectures. Due to several conflicting licenses, it is not possible to produce a single lean binary (1 per architecture) that supports all of these compression algorithms. I do have builds for most of them, but it would at least double the size of the ZIP, which is already too large for my tastes.

I have several possible solutions for this, and it's on my list, but other things have higher priority.

You're going to need to patch both the boot image and /system both on Nougat on any stock firmware. This was of course already the case in Marshmallow, and the system use case really now is just for custom ROMs that are specifically built to support it. And that hasn't been tested/fixed yet for Nougat. Again, it's one of those things on my list, but not with the highest priority.

It's a staged roll-out. It will probably be another day or so before it is widely available. I've asked those who control Play to add a note about this.
[SuperSU] samhhmobil:
You can get in from another thread in this forum, user Halifax did post it here:

https://xdaforums.com/showpost.php?p=63615067

This is the direct link to UPDATE-unSU-signed.zip:

https://xdaforums.com/attachment.php?attachmentid=3931994&d=1478779893
[SuperSU] Idebutterpiep:
UPDATE-SuperSU-v2.82-20170526223454.zip.md5 seemed to be corrupted when I use it in Odin.
[SuperSU] Wolfcity:
Compare with the md5 file and if necessary download again.
[SuperSU] Idebutterpiep:
I tried all the servers and all were only 74 bytes
[SuperSU] Wolfcity:
Download with es explorer from the above link.

No problem. Maybe you are downloading the hash file?
[SuperSU] dahawthorne:
74 bytes looks correct to me. In any case you don't need the MD5 file, since it contains the same string that appears beside the file download and it's therefore simple to use an MD5 checker to validate the file before using it.

The MD5 contents:

ebdb9fbe365cd77f2281a5b9a598cfb4 UPDATE-SuperSU-v2.82-20170526223454.zip
[SuperSU] Wolfcity:
I thought he wants to download the superSu file itself. For the md5 74 bytes seem to be correct.
[SuperSU] jcmm11:
It's an md5 file. Which means it contains an md5 check value. Open the file in text format.
[SuperSU] dahawthorne:
I guess so - the md5 isn't much use by itself. :)

In fact the md5 contains something over 80 characters, which is interesting, but given that it's clearly legible there's no point in sweating about it. As I said, if the poster is concerned about the integrity of the md5, he can use the value beside the SuperSU file to validate in a simple md5 checker app. Not worth losing sleep over the apparent inconsistency of the file description of 74 bytes when it's clearly not corrupt.
[SuperSU] ashyx:
Thanks for the info. I should have made it clear that I meant the script in the update binary only supports gzip not supersu itself.
[SuperSU] Chainfire:
I have an M7 around here somewhere. I will try to reproduce the problem.
[SuperSU] immi803:
2.82 Stable, wow

It was fast
[SuperSU] flroots:
Could someone provide an update on which versions of SuperSU caused loss of root and which version is now being recommended? I have the Moto G4 Plus (xt144). Thanks
[SuperSU] veez21:
v2.82, it seems. You can still explore the thread and find the answer yourself
[SuperSU] flroots:
Thanks. I've spent quite a bit of time exploring the thread, but was still confused :(

I lost root out of the blue. I then flashed 2.79 and recovered root. I then flashed 2.82 and kept root. I'm now speculating that maybe 2.80 or 2.81 caused the issue?
[SuperSU] WiggleCat:
I'm stuck with Busybox On Rails binaries I can't remove now. Should I just purge /system/xbin?
[SuperSU] ktmom:
Try looking for only Chainfire's recent posts.
[SuperSU] ianmacd:
I used FlashFire to install the CCMT ZIP of 2.82 on my S8+ and can report that all is well here.
[SuperSU] bemagrp:
2.81 caused the issue, 2.82 is fixed version of 2.80 as per [MENTION=631273]Chainfire[/MENTION].

Unselect automatic updates in the play store and you not going to loose root out of blue.
[SuperSU] Grassinator:
Just flashed latest BETA SuperSU-v2.82-CCMT-GooglePlay via The Flash's new twrp-3.1.1-10-angler-f2fs successfully on my Nexus 6P

ROOT LIKE A CHAMP.... SUPPORT CHAINFIRE AND GO PRO!!!
[SuperSU] tetrabyt:
Same here on my HTC 10.
[SuperSU] milocj:
Supersu 2.82 apk works perfectly on Nexus 6 7.1.2 Pure Nexus with BL4CKB1RD kernel and Nexus 5 7.1.1 fake rom with francoKernel and upgrade binaries correctly. Works perfect too on Galaxy S5 6.0.1 and Sony Xperia Z3 6.0.1

Thanks [MENTION=631273]Chainfire[/MENTION]

Enviado desde mi Nexus 6 mediante Tapatalk
[SuperSU] rgraville:
You don't flash MD5 files. The content of an MD5 file is a hash of the file it represents. You can use an MD5 checker to validate that you did not get download errors in the .ZIP file or otherwise acquire a corrupted version.

Only flash the .ZIP not the .ZIP.MD5
[SuperSU] tdunham:
And don't forget, zip files cannot be flashed with odin anyway. ;)
[SuperSU] fresnogamer:
Nexus 6P

Installed 2.80 via the play Store and also via flashing the zip. Both gave an error in SuperSU saying I did not have root. Also did the same for 2.81. Same error.

Flashed 2.79 via TWRP with zip and it is working correctly now. So glad I didn't have to wipe my phone.

AdAway is now updating again also.

Happy to share any logs. Feel free to reach out. Thanks.

---------- Post added at 06:20 PM ---------- Previous post was at 06:06 PM ----------

Just found the 2.82 Play Store zip. APK version did not work. Said can't open file. Installed 2.82 via TWRP and its working.

Thanks Chainfire.
[SuperSU] tdunham:
Neither of those versions apply any longer. Version 2.82 is the latest, read back.

Edit: Sorry, I see you found it. :)
[SuperSU] corkiejp:
Old news, Versions 2.80 and 2.81 are already know to cause problems. 2.82 is the latest version that should have resolved problems with supersu.

See Chainfire's posts for more information and download links.

I'm still using 2.79-SR3 on my devices, while I wait for chainfire's changelogs and info that he is due to post!
[SuperSU] Idebutterpiep:
Thanks for the answer.
[SuperSU] foosion:
I got a notification to update SuperSU (# in the notification bar). I checked and saw that I had 2.82 installed. I went ahead from clicked to install the update, after which I still had 2.82.

???
[SuperSU] crisis_trustee:
This file is only md5 signature of zip-file. :cool:
[SuperSU] CyberZeus1977:
The update you went through was binary update, not app version.

It's all ok!

Sent from Enterprise bridge
[SuperSU] samhhmobil:
Hello Chainfire,

I have two M7, one is free yet for testing purposes, the other one is for daily use.

Both are the international GSM-Version "801n", not any US-adapted ones.

So if I can assist in testing, please let me know.

Best regards,

Stefan (samhhmobil)
[SuperSU] Ibuprophen:
To perform a member callout, that provides that specific member a notification of it, you need to place an "@" (without quotes) at the beginning of the member name.

For example, if i were to perform a callout, to myself, i would just type [MENTION=4828250]Ibuprophen[/MENTION] and I'll receive a notification of this.

Just a friendly FYI in case you didn't know... :)

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] foosion:
Much as I hate to ask stupid questions, what's the difference between the binary and the app? Shouldn't a change in either be reflected in a different version number?
[SuperSU] zelendel:
If I recall right I think Chains has the notification disabled like most of the devs and mod team. I could be wrong but I think I recall him saying he turned it off.
[SuperSU] ktmom:
The binary is the actual root executable. The app is a manager of access to the binary.
[SuperSU] Ibuprophen:
You may be right though I don't believe that Callout's can be disabled...

I know that PM's can be disabled and i thought that Chainfire had disabled that.

To quote Billy Joel... "You may be wrong, for all i know, you may be right!"...

LMAO!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] amitroutray:
Don't worry the thread owner is always get a notification when there is a new post posted :)

Triggered from rn4
[SuperSU] foosion:
How do I know which binary version is installed?
[SuperSU] Ibuprophen:
Just to add to ktmom's correct response...

If you were to update only the binary but not the app, you will not see that binaries correct version within the app itself because the app not only manages the root access but, also manages the binary in making sure that the correct one is installed.

Though I've never installed only the binary, i do believe that if the binary size and/or the version doesn't match what the app thinks it should be, then the app will, more than likely, notify you to update the binary.

Just a friendly, and helpful, FYI... :)

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

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

---------- Post added at 03:36 PM ---------- Previous post was at 03:30 PM ----------

Open SuperSU and select the Settings tab (the far right one) and, at the top, you'll see SuperSU Free(or Pro) (CM) then the Version #.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] zelendel:
You can as I have mine disabled as do most of the people I know. Well at least the notifications for it. its under the mention setting to the point that you would never know if someone mentioned you.

It just maybe a lunatic your looking for.
[SuperSU] jcmm11:
For the binary version, in a terminal emulator:

su -v
[SuperSU] foosion:
Now I'm confused.

Earlier I asked why app 2.82 wanted to update and after the update I was still on 2.82. I was told "The update you went through was binary update, not app version. " https://xdaforums.com/showpost.php?p=72464747&postcount=10095

However, when I check the binary version number by either of the methods quoted above, I get 2.82. The first method was the one I looked at to determine I'd gone from 2.82 to 2.82.

So this brings me back to my original question - why did I get a notice to update to 2.82 when I was already on 2.82? FWIW, this happened on two devices.
[SuperSU] Ch3vr0n:
The app didn't want to update, the app needed to update the su binaries. Root has 2 components, the binaries that do the su actions and the app that (dis)allows an su requesting permission to rights to access those binaries. And that's exactly what that message told you.

'# binaries need an update', you tap on the notification. SuperSu opens and prompts to update them, 'normal or twrp'. You picked normal, binaries updated. That's it, the app did NOT ask to update itself.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Chainfire:
[MENTION=7487527]Ps24u[/MENTION] [MENTION=393455]tobbbie[/MENTION] [MENTION=644756]xalaros10[/MENTION] [MENTION=4888288]junk031[/MENTION] [MENTION=488914]Rebel2k[/MENTION] [MENTION=2514812]erfandl[/MENTION] [MENTION=8300892]samhhmobil[/MENTION] [MENTION=4899305]ashyx[/MENTION] [MENTION=7172205]droseofc[/MENTION]

I've attached a new test version (SuperSU-v2.82-20170528234214-TEST-1.zip) to this week's releases post here: https://xdaforums.com/showpost.php?p=72429329&postcount=9810

It fixes the bootloop issue on my HTC One M7, and I hope it will fix the same issue on your Xperia's.

It might even be the fix for system mode on Nougat, though of course you would still need to be running a compatible boot image.

Please let me know if this fixes any of the problems you are seeing.
[SuperSU] habylab:
Weirdly, clean installed, and now 2.82 does not work with Ad Away. Tried a reboot, reflash, won't budge.
[SuperSU] Ibuprophen:
Reporting that i had flashed the "SuperSU v2.82 Test 1" and installed without error or incident (so far) in my Galaxy S3 d2vzw with CM13.

Thank you [MENTION=631273]Chainfire[/MENTION]!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] WiggleCat:
If you look at my third screenshot in my previous post Advanced Root Checker reports a Java pipe error in the root user account.
[SuperSU] WiggleCat:
I'm confused as heck right now. I used ADB to remove the binaries and purged /system/xbin. Root checker advanced reported no binaries and no superuser app. I then booted into recovery and unpacked the 2.79 ZIP on my computer. I pushed su and supolicy from the arm64 folder to /system/xbin and system/bin and su to /system/xbin/daemonsu then chmod them all to 755. I put the libsupol.io in the lib64 folder and chmod it 644. Set the daemon to --auto-daemon.

I booted it up because installing the application with ADB gives me the error 'CANNOT LINK EXECUTABLE: library "libqc-opt.so" not found' and installed the SuperSU 2.79 APK manually. Didn't install the pro APK too just the regular one. Now it says there's no binaries installed and it can't install them, and when I checked advance root checker it says the 2.82 binaries are installed and configured properly. What's going on?
[SuperSU] Sr. Zé Alguém:
[MENTION=7539361]WiggleCat[/MENTION]

Chainfire already answered you...

In synthesis, it's better you clean up your own mess, start from scratch, and don't try doing everything manually like copying files; instead, use the installers (flash using the zip).