yashsingh1/xdaforums huggingface dataset:
[SuperSU] DB126:
I skimmed your length post so likely overlooked some details. Thoughts:

- I doubt features were intentionally stripped (certainly not referenced)

- SuperSU 2.79-2.82 SR2 were problematic, especially on Lollipop ROMs

- SuperSU 2.82 SR5 has proven quite stable link

- Any version of SuperSU can be uninstalled using this tool
[SuperSU] Lannig:
Hi folks, sorry to bump my question for a few pages ago... so, no one knows what the

/system/xbin/su --install

command at the end of the SuperSU install script does?

Certainly it can't install files because this has been taken care of by the rest of the script, including permissions and all. So I'm really wondering.
[SuperSU] jcmm11:
This step is only being done if you're running a system install, which is pretty rare nowadays.

There is a comment about this within the install script (taken from SuperSU-SR5)
[SuperSU] Lannig:
Thanks for the reply. Well, as I mentioned in my initial post, I'm working on Lollipop-based devices at this time so I'm still dealing with system installs. My purpose is to have a script I can run from a Linux box on which I have a dump of the Android device's system partition mounted, to root it. So it must mimick what the recovery-based install script does. I'm pretty much done except for this last step. Obviously I can't run su from the Linux machine so I must reproduce what this last step does, if I can figure it out.

As for the comment, I had seen it but it basically says nothing about these "additional installation steps"
[SuperSU] jcmm11:
It also says "may", so it's possible that it does nothing - decides that everything needed is done and simply exits.
[SuperSU] ElConedeTJ:
Good Day To All, I'm (still) using my old HTC Droid DNA with this ROM and the SuperSU app updates OK but if I try to update the binary via the App or install the SuperSU via Flashing it via recovery the phone get's stuck at the boot screen, I'm attaching the Logcat output (look from the bottom up) This is the line that repeats forever:

W/HtcBootAnimation( 408): fcount=1

Could it be a problem with the boot animation? I also see these lines between all of the above lines:

E/DMAgent ( 349): Port open failure. [v6.0.1.20130329]
E/DMAgent ( 349): TTY Port open failure

W/Vold ( 248): Unmount CDROM.ISO if no access

Any suggestions? is it the boot animation? is it the ROM? is this something I could fix or only the developer of the ROM can fix?

Or are the only options I have are to either live with this ROM without updating the binary or change to another ROM?
[SuperSU] AliAbshari7:
Work on android 8.1?
[SuperSU] Ch3vr0n:
SR5 does for me on N6p

Sent from my Nexus 6P with Tapatalk
[SuperSU] bush911:
When will you release the updates for android 8.1? It seems that you had noting to do after finishing acquisition.
[SuperSU] rakshushetty:
can i flash this in my OnePlus 5??
[SuperSU] DB126:
Lol. Read through recent posts and the newer SR5 thread. CCMT is doing nothing with SuperSU nor engaging with the user community. Explicit support for 8.1 does not appear to be in the works given no public test builds or any communication on intentions.
[SuperSU] Giobio:
Maybe who bought Chainfire's project is already into "superuser world" and had its own interests to stop the software developing?
[SuperSU] a g bell:
OR maybe the Chinese company who bought it now realize they can't fill an apk full of crap without us finding out ??
[SuperSU] evildog1:
I had the same problem with optimizing app loop. I flashed the firmware and flashed SuperSU 2.82 SR5 and it solved.
[SuperSU] drewski_1:
works for me with 8.1 on Pixel C & N10-AOSP

. . . that said, I switched to Magisk for better support & updates ;)
[SuperSU] bibikalka:
[MENTION=7678190]SuperSU Release[/MENTION], [MENTION=631273]Chainfire[/MENTION]

Device: Amazon Fire HD 10 (7th gen, 2017), arm64, ~Android 5.1.1 :

[ro.build.mktg.fireos]: [Fire OS 5.5.0.0]
[ro.build.version.incremental]: [40.5.9.1_user_591450020]
[ro.build.version.name]: [Fire OS 5.3.5.1 (591450020)]

The official SuperSu 2.82 zip fails in FlashFire. I did manage to get it to work correctly. To do so I had to hack update-binary a bit ( link).

In META-INF\com\google\android\update-binary I replaced one line forcing SuperSu to install armv7 binaries instead of arm64:

if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=arm64; SYSTEMLIB=/system/lib64; APPPROCESS64=true; fi;

with this one:

if [ "$ABILONG" = "arm64-v8a" ]; then ARCH=armv7; fi;

It looks like Fire HD 10 is not quite arm64 yet, and needs armv7 version of su binaries to work. Here is the diagnostic messages

[OUT] supolicy v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
...
[ERR] mv: can't rename '/system/bin/app_process64': No such file or directory

Perhaps, the scripts could check the existence of '/system/bin/app_process64' for arm64, and if it does not exist, force armv7.
[SuperSU] Crike:
I'm unable to root my Note 5 running Nougat 7.0 (N920CXXS3CQK1), either from Odin or TWRP.

√ USB Debugging and Unlock OEM

√ Odin 3.12.3 from XDA

√ CF-AR N920CXXS3CQK1 from firmware.mobi

√ USB drivers from Smart Switch.

√ Note 5 Added to Odin when I enter download

√ extracted the .tar.md5 from the CF-AR N920CXXS3CQK1 zip

√ .md5 fine, flashing successful, taking about one minute.

But when the phone then auto boots, the phone boots again once after a few seconds and then proceeds to load Nougat, no SuperSu app in the tray. When I run the root.bat same result.

√ Flash latest TWRP from TWRP site

√ Volume Down + Power out of Download, then Volume Up + Menu + Power into TWRP

√ Keep Read Only

√ Install... SuperSu zip (2.82, downloaded from this thread on XDA) in less than a minute.

When I reboot again no SuperSu app.

What may be going on?
[SuperSU] Lughnasadh:
Yeah, it looks like they've posted a total of 7 times on XDA, 3 of which were "reserved" posts, lol. Last active Oct. 5. Such a shame...
[SuperSU] ktmom:
I'm reading between the lines of Chainfire's recent post, and thinking that it's possible CCMT bit off more than they could chew. I'm under an impression CCMT is trying very hard to hire developers with sufficient familiarity with rooting devices. If I remember what Chainfire said correctly, they would have been happy to extend his contract but he wanted a break from all of this.

My /opinion/ is, SuperSu will continue to evolve, if and when CCMT develops the ability to move it forward. Device rooting is getting harder, and talented developers are hard to find.

I also believe that they will be unlikely to return to this site where there is no patience for them. That's just human nature to avoid being bashed. It's amazing Chainfire shows up to post.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Nicky Cheer:
Please any one help urgent

Recently i install su v2.82 on my lineage os 14.1

I want to uninstall.

So in su app if i click full unroot so many options are coming . it is asking me tp restore stock recovery ? I installed twrp recovery. And i am using redminote 3 kenzo
[SuperSU] ghost45:
Hi to [MENTION=371528]Everybody[/MENTION],

i tryed to receive right roots in the Vernee Mix 2 but without success...

Vernee Mix2 with android 7 sdk24

I flashed the version supersu282.zip and also the version SR5-SuperSU-v2.82-SR5-20171001224502.zip but nothing i read an error during the process of installation during the extraction of the ramdisk:

Seems only the magisk are able to receive right root:

I tryed also (after reflash the original firmware) with the boot patched builded from magisk to install supersu ...but nothing happened always the same error!

Any suggestions?

thanks to everybody
[SuperSU] Eures:
SuperSU 2.82 stable

I've found different files of the 2.82 stable version. Are these two files still current or are they useful?

- SuperSU-v2.82-20170528234214-TEST-1.zip 5779k

- UPDATE-SuperSU-v2.82-20170528234214.zip 5779k

On the website the latest stable version is:

- SuperSU-v2.82-201705271822.zip 5776k
[SuperSU] Eures:
I've found this answer:

https://xdaforums.com/showpost.php?p=72497129&postcount=10207

My concern is: if the version with newest timestamp contains a patch, why is it not listed on the Superuser.com site?

Also at the beginning of this thread is clearly written:

*** Xperia users, and others experiencing bootloops ***

Please use this version instead (the May 28 release)

Nevertheless I would also list it on the site because it is more official!

Thanx.
[SuperSU] DB126:
The build from this thread is both the most current (as of the date if this post) and the last with [MENTION=631273]Chainfire[/MENTION]'s involvement. Been out for several months with no notable instability.
[SuperSU] Sakthi berdy:
Moto G4 plus not booting into system after flash supersu zip

Hi i flashed my moto g4 plus with this zip : STABLE 2017.05.27 SuperSU v2.82 . After the process completed i just clicked reboot. The device got turned off but it is not rebooting to the system. Even if i press power button to Turn on it is not working. Im able to enter into bootloader mode. But not able to boot into the system normally. Please Help its very urgent.. 1000 Thanks in advance
[SuperSU] Eures:
But the build from that thread is the October 01 one. What about the May 28 build for Xperia users, which is linked for download at the beginning of the present thread?...
[SuperSU] DB126:
Have no experience with the build you reference. Suspect it was a temporary fix to addressee boot loops which was subsequently rolled out in one of the 2.82 SRx releases.
[SuperSU] BillGoss:
Use osm0sis unSU from https://xdaforums.com/showthread.php?t=2239421&p=40409356
[SuperSU] partcyborg:
I am having a serious problem with supersu. Every time I go to clean up to reinstall from google play the app is not removed because the app is trying to link toolbox against 32bit libs in /lib instead of the correct 64bit /lib64. How can I fix this?
[SuperSU] madbat99:
Obviously you don't need stock recovery, that's for people on stock system to fully unroot to stock. Just remove the su script in addon.d or wherever it is and reflash your rom (dirty flash). Not exactly urgent dude. Or as previously posted, use unSU
[SuperSU] Sachin ET:
Which version should i choose for Oreo 8.1 ?
[SuperSU] drewski_1:
Sr5?
[SuperSU] tejasrao1996:
I don't think SuperSU is updated to work with Oreo. Use magisk instead.
[SuperSU] Ch3vr0n:
You think wrong. On my N6p SR5 works just fine on 8.1 januari security patch
[SuperSU] drbabusaha:
There r 3 main versions of supersu 2.82, dated 27/05, 28/05, SR5....

which one is to use to avoid any errors???
[SuperSU] Ch3vr0n:
The only way to avoid errors is not rooting at all. Rooting inheritely brings risk. Backups, backups, backups...

That said, I use the one from the SR5 beta thread first post. https://xdaforums.com/showthread.php?p=55256620

Sent from my Nexus 6P with Tapatalk
[SuperSU] jekyll530:
SR5 from beta thread is newer and more stable than this so called stable one, but on some devices it doesn't work on Oreo, e.g. my OnePlus 5.
[SuperSU] CrackGod:
A very big bug!

The multiopened apps can not get root permission.
[SuperSU] deloj:
After I dirty flashed Nougat and Odined TWRP, I still cant get root. I Odined SuperSu but after that I got this message: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."

I then dirty flashed Nougat and everything is ok. But I still dont have root. I used this SuperSu: "SR5-SuperSU-v2.82-SR5-20171001224502. "

What do you suggest to get root?﻿

.
[SuperSU] ktmom:
You are replied to in the beta thread where you also posted.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] deloj:
Ok you noticed that. Cool. So what do you suggest? The supersu I tried was beta. Do you think I should try the stable version?:
[SuperSU] youbakmaster:
I got bootloop on htc one m7 after flashing the zip and the apk.

s-off . unlocked bootloader . super CID . Android 5.0.2 . TWRP latest.

i tried so many time and with a different firmware.
[SuperSU] arnax1:
I am trying to root Nexus 6P on Oreo angler-opm3.171019.013.

After installing TWRP and flashing the zip SuperSU-v2.82-201705271822, phone just hangs on booting (shows Google) for eternity.

Why is that? How can i fix it? Any other methods of rooting?
[SuperSU] Badger50:
This is the one that always worked for me on my 6p. Reboot back into twrp and flash it.

http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

You may want to look here for more helpful tips as well.

https://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
[SuperSU] arnax1:
Oh man thanks it finally boots up. You are a life saver.
[SuperSU] arnax1:
Ok i ran into one more problem. After installing this SU, its does not install the application. I have to download it, then click to install it normaly, then phone reboots and hangs.. Do you know why it does not install the application?
[SuperSU] ktmom:
Try extracting the apk from the common folder in the zip that you flashed and install that. The flag log should give you an idea what happened during the flash.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] youbakmaster:
no one !!!:confused:
[SuperSU] jcmm11:
Try SR5
[SuperSU] youbakmaster:
SR5??
[SuperSU] jcmm11:
https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] youbakmaster:
thanks man for your help.

i flash it and it works like a charm :good:
[SuperSU] flaxx187:
What should one pay attention to find the right supersu version ?

i have sony z5, so is supersu the newest evertytime compatibilty with new phones ?
[SuperSU] DB126:
You want this. Messing around with other builds is just silliness based on speculation and/or outdated information.

That said, SuperSU is no longer being maintained in the manner it once was. You may have to go the Magisk route if your device and/or needs do not respond well to SuperSU. Good luck.
[SuperSU] flaxx187:
done
[SuperSU] DB126:
If you are going to flash (install) SuperSU you should go with v2.82 SR5 as it contains many bug fixes that have yet to be migrated into the "stable" build - and may never given complete disengagement by the current owners of the product.

You'll need to read up on the particulars (if any) of rooting your device. Some work better with SuperSU; others with Magisk. Your device forum is the best resource for this information.
[SuperSU] flaxx187:
i install v2.82 SR5 with TWRP 3.1.1-0 but nothing works

1 flash .54

2 flash recovery

3 flash kryptonian rom

4 flash supersu

restart normaly (without an app named supersu)
[SuperSU] jcmm11:
Do you have root? (Do apps that need root work?) If yes then extract the SuperSU app from the common folder inside the install zip and install it.
[SuperSU] flaxx187:
I thought i get root if i install supersu via twrp

But nothing happend if i install it
[SuperSU] Badger50:
Did you get an error flashing it in twrp? If no, then read the post just before yours, or download SU app from from the play store.
[SuperSU] flaxx187:
I don't have root.

I installed supersu from playstore but i haven't root rights told me the root checker.

Sorry i don't understand the part with the extract the supersu in the commonfolder

Should i search the supersu.apk and add it to supersu v2.82 and install it via twrp?

Ps: i don't think i got an error while flashing supersu

Pss: i think it got an error, bc the ramdisk couldn't restore (picture)

Psss: maybe because i don't flash a new kernel?

Thanks for you help :)
[SuperSU] janedoesmith:
I can't recall exactly how long it took but at the time it did take long enough where I though I was in a bootloop. Iirc, it may even have bootlooped once before completely booting up.
[SuperSU] grep_i:
Try to be more specific and give us version numbers instead of latest, nobody knows what latest is to you, thanks in advance please.
[SuperSU] meleelord:
TWRP v3.0.2-1 (tried -2 and unofficial -3 as well), SuperSu v2.78, Nexus 6P, Nougat 7.0 September factory image.
[SuperSU] facemob:
about how long? i think i let it sit at the boot animation in excess of 15 minutes with no luck
[SuperSU] janedoesmith:
15 minutes is sorta in a grey area. Can't say for sure. However, I can definitely say it did not exceed 30 minutes. Sorry, I can't be of better help.
[SuperSU] grep_i:
Can you provide logcat or recovery.log.

Also can you try Supersu 2.77 just to be sure.
[SuperSU] Einwod:
You're quite correct. Reading the output after flashing SuperSU 2.78 clearly states that the first boot could take some time and NOT TO INTERRUPT the process. Then again, some people are "clickaholics" and do not read what is clearly written for them.
[SuperSU] egingell:
15 minutes is an unreasonable length of time for even an extra long boot process.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] meleelord:
I've tried reinstalling boot and everything else, only leaving data. Then trying again, I'm just not getting anywhere. I'll come back to it another day, with hopefully more luck!

This post is sent to you with the power of the Nexus 6P!
[SuperSU] nodz13:
Up
[SuperSU] benjaminclaw:
Maybe try Kernel Adiutor? SetCPU hasn't been updated in 3 years so it could be an app issue.
[SuperSU] Didgeridoohan:
Have you tried redownloading the SuperSU zip? Might be a bad download.
[SuperSU] DryEagle:
https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip link to 2.78 zip since chainfire forgot to put it in the OP for some reason
[SuperSU] Pkt_Lnt:
It is there, but this is not Chainfires thread any more.
[SuperSU] DryEagle:
for some reason i read that as a link to flashfire zip, not flashfire-installable supersu zip. i have no idea why...
[SuperSU] ulxerker:
So, what are the differences between chainfire's version and the one of the OP? for any reason they have different dates and numbers in their file names (UPDATE-SuperSU-v2.78-20160905010000.zip / SuperSU-v2.78-201609011115.zip)
[SuperSU] egingell:
The answer to that question is contained within the walls of this thread. There is no difference other than who compiled it.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] Adi!@#:
Hello , can I flash it to obtain root on miui 8 global stable ? I'm using a Redmi Note 3 Snapdragon version
[SuperSU] corkiejp:
Yes!

More question about that device should go here: - http://xdaforums.com/redmi-note-3
[SuperSU] Chainfire:
v2.78 SR1 (aka beta) has been released. Release notes here: https://plus.google.com/+Chainfire/posts/8mPirmjhgqT
[SuperSU] Wolfcity:
Your picture is hardly readable, you can do screenshots in TWRP just the way you do while in system (power+ vol down).

If your ramdisk couldn't be restored it's definitely an error. What's your device? Some devices work better with magisk as root solution.
[SuperSU] DB126:
Sigh - pretty much what I told him here and in prior posts.
[SuperSU] sandstones:
super su app hanging on Lenovo Tab 4 10 plus

I installed supersu via TWRP and that ran OK. (SuperSU-v2.82-201705271822.zip)

The supersu app is there, and google play thinks it is up to date.

However the supersu app hangs - black screen.

And when a rooted app runs it requests root access, goes away for a few seconds and then reports that the device does not appear to be rooted.

Any suggestions on what to look at?

Model is a Lenovo TB-X704L, running Android 7.1.1
[SuperSU] jcmm11:
Try SR5 from the beta thread https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] dekraan:
binary update fail on Huawei Mate 9

Hey everyone,

Yesterday, I rooted my Huawei Mate 9 using this guide: root huawei mate 9

I unlocked my bootloader, installed TWRP-3.0.2-2-hi3660 and then I flashed SuperSU-v2.79-MATE9-init.d_support.zip. Things went fine yesterday and my phone was rooted.

After rebooting today, about half an hour ago, I get a prompt to update my binary, which fails every time. According to Titanium Backup, my phone is still rooted.

I think the problem is this: when I look at my updates in the playstore, SuperSU was updated 4 hours ago, probably to version 2.82?

After I noticed a problem with the binary, I upgraded SuperSU to Pro, simply because I bought that a long time ago and hey, why not? But that did nothing to solve the binary problem.

Does anyone know what to do? Should I flash the v2.79 again in TWRP? Can I simply do that, or do I need to uninstall something? Or rollback?
[SuperSU] jcmm11:
Flash the zip of the latest (and probably last ever) version of supersu. SR5 can be found at https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] corkiejp:
Edit: - Never-mind, you flashed an old version, hence why you got an update.

Flash the version from this thread or the SR5 release.

SuperSU was last updated on May 28, 2017.

https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en

Are you sure you are using the correct version and not some hacked version of it.

Or maybe it is a device you haven't update apps in awhile?
[SuperSU] dekraan:
Can I do this without removing the current version of supersu?

---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------

Hey! :) it's my everyday phone, but I managed to hold out on rooting for a long time. Don't know that much about the version I used, it seemed to be tailored to my device and it is suggested on xda to use. I'll flash the SR5 release and see if I can update my binary after that.

Is it ok to update it to the PRO version through the supersu app itself?

EDIT:

I tried to flash the SR5 file, and maybe it worked, maybe it did not. In TWRP, it went a bit fast, and after it ran some blue lines of code, my phone rebooted. I am now running SuperSU Pro v2.82. So, I am not so sure, that anything actually happened.
[SuperSU] corkiejp:
[MENTION=1334717]dekraan[/MENTION] Check your device threads for an updated version or alternatively use a supported magisk version.

If you need a specific version for your device, that latest (last) version of SuperSU maybe not compatible

The pro version, just installs a license file for pro, available here.

If your stuck on the old version, don't update/install SuperSU from playstore.

If you on the odd chance you don't have a SuperSU app, after flashing, install the version in the common folder of the zip file.
[SuperSU] dekraan:
I've asked around in my devices forum as you suggested, reflashed the 2.79 version and excluded this from auto-updating! So I think I'm good for now.

About the pro version: can I install this from the playstore, without it becoming v2.82 or something else?
[SuperSU] corkiejp:
If it was working, why did you change? You probably had SR5 binaries, with an older app version. Installing the app from the common folder of the zip, would probably have resolved the mismatch.

As I already said it is just a license file and won't effect the version been used.
[SuperSU] febry_valdy:
Can I have SuperSU for treble ROM? Cos I tried latest stable and it failed to install.
[SuperSU] corkiejp:
[MENTION=6244335]febry_valdy[/MENTION] As treble roms are only recently release feature, and SuperSU development has stalled since the last 6 Months. Do not expect a support version for treble. Look at Magisk thread or your device/rom for root methods.

Edit: - If using RN4(Mido) see this thread : - https://xdaforums.com/redmi-note-4/...other-development/rom-lineageos-15-0-t3690465
[SuperSU] febry_valdy:
Yes I use magisk that is designed for treble, just wanna know that possibility SuperSU has treble support. Thank you.