yashsingh1/xdaforums huggingface dataset:
[SuperSU] Wolfcity:
I think what [MENTION=4544860]osm0sis[/MENTION] wanted to say is that the whole discussion is absolutely off topic and just handles with assumptions, conspiracy theories and no facts at all as there are none.

That what happens to threads like this when there isn't any development anymore and people just get scared (or bored?) for several reasons. Maybe it would be a good thing to lead the existing SuperSU threads to one thread with a sticky/OP that includes [MENTION=631273]Chainfire[/MENTION]'s latest statement and the known facts that there isn't any development anymore atm and most probably won't be again in the future.

In my devices forum there are still a lot of users who don't know what happened to superSU.

What we need are facts even for newbies.

I think [MENTION=631273]Chainfire[/MENTION] has to do somebof this things by his own but maybe he takes a look in here from time to time.

Just my 2 cents.
[SuperSU] GuardianUSMC:
Wasn't directed at anyone in particular, it was more along lines of what [MENTION=5237901]Wolfcity[/MENTION] said.
[SuperSU] hopecore777:
Is supersu still compatible for oreo?
[SuperSU] jcsww:
That depends on the device you have and what you are running on it.
[SuperSU] GuardianUSMC:
Speaking for myself, not sure. I am still on 7.1.1 which is the last image for my device and it is working fine. I have not had a chance to go ROM "shopping" yet so haven't had a chance to experiment with anything newer, hopefully someone else can comment. But even Chain recommended using something else, a la Magisk et al.
[SuperSU] ktmom:
Could you link me to where Chainfire indicated to use a different root solution please. I'm unaware of that.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] GuardianUSMC:
Navigating this thread has become a bit of a nightmare and he also posted some stuff on Google+ but give me a few minutes to look for it. I need to check here and elsewhere to find it but I know for a fact that he did recommend other projects that are "actively maintained". He named a few but I could only remember Magisk, that's why I didn't mention anything else cause I didn't want to misspeak.
[SuperSU] ktmom:
I think it's highly unlikely that Chainfire referred anyone to Magisk (though many of us have in this thread) for several reasons not the least of which is his contract with CCMT. Any yes, I am subscribed to his G+ page as well as read through his website.

There are devices for which SuperSU continues to work fine on Oreo releases, and at least one where it's a problem. I would guess that's due to the slot A/B configuration.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] GuardianUSMC:
Yes, he has referred to his contract with them and that he feels they will be fine continuing the project but also expressed that those who don't feel comfortable with that have other options. Also note, he is no longer under contract with them and has no constraints on recommending anything he wants.

I am going to reach out to him to see if he can point to where he said that, I remember it clearly but having a hard time finding it, perhaps it was a post removed since or more likely in a discussion comment somewhere which I am not finding. I sent a note, waiting to hear back from him on his personal channel, will share what he says.

I personally have never used anything other than this and per that recommendation was going to educate myself on Magisk in the case I find myself needing to use it and can no longer use this, but as I said, due to where I am at now, I am still using SuperSU and SuHide without issue and have not felt the need to look for another solution as of yet.
[SuperSU] NLBeev:
After some trial/error I am using Screw'd Oreo ROM.

https://xdaforums.com/showthread.php?t=3773277

The ROM includes EX kernel.

Flashed also Opengapps-pico for arm 8.1 and Magisk 1600.

Magisk has the option to add modules like 'Enable doze' and 'Unified Hosts Adblock.

Running smoothly for daily use on my > 4 year old Nexus 6.
[SuperSU] GuardianUSMC:
Excellent, thank you for sharing, I appreciate it. I will look into that.
[SuperSU] ipdev:
[MENTION=1650358]GuardianUSMC[/MENTION]

You might be thinking of FlashFire or one of Chainfire's other projects.

The root required ones, normally support SuperSU of course and built-in root like cm/lineage. Most of the time set to permissive mode.

Some have been updated to work with Magisk. FF-Release

Others have a workaround to make them work with Magisk. LiveBoot for example.

My Two Cents.

I don't think Chainfire will ever recommend using Magisk. Tolerate it yes, recommend or endorse it never.

If you don't remember the drama not quite two years ago, just look back at New Years eve in this thread.
[SuperSU] GuardianUSMC:
As a sincere and honest professional, I will concede that I may be remembering it wrong. I have no dog in the race, I was simply trying to help.

You are probably quite right, I will concede to that because as I said, my intent was to help not misinform. I unfortunately don't remember the "drama" that you are referring to but thank you for providing the context, it is appreciated.
[SuperSU] andrew2432:
Missed out

Has ccmt said anything at all on development
[SuperSU] Wolfcity:
No.
[SuperSU] Ch3vr0n:
Not a damn thing since they bought it, and no more updates either

Sent from my Nexus 6P with Tapatalk
[SuperSU] shaggyskunk:
It's probably been posted here before - but I'll just link this again if it has....

Questions in my own mind are mostly around the fact that Chainfire was updating SuperSU fairly frequently and since CCMT there's been nothing - Chainfire had people's trust & trust is something that is earned (so I've been told). While I felt a degree of loyalty towards Chainfire - I feel absolutely none towards CCMT ?

https://www.google.com/amp/s/amp.re...p/ccmt_who_exactly_are_the_owners_of_supersu/

Sent from my SM-G955W ??
[SuperSU] zelendel:
Yes all of that is well known and the fact that they invested alot in XDA is also known to the point that it is thought that XDA has been sold to the same company but after this issue no one is saying anything.

But who knows. SuperSU is dead now and no one will trust it ever again so Chains pretty much made sure this thing died after he left.
[SuperSU] jcsww:
Have you flashed your S9 Plus to the U1 firmware yet?
[SuperSU] shaggyskunk:
U1?

Sent from my SM-G955W ??
[SuperSU] Ibuprophen:
Just an FYI for those who may have missed this information but, the following thread posts were made by myself within the "[STABLE][2017.05.27] SuperSU v2.82" thread and I just wanted to share this with you.

Enjoy and Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] jcsww:
It's a US non-carrier firmware that allows you to flash to other carrier firmware, if needed. It also makes it easier to get rid of all of the bloatware that gets downloaded or comes pre-installed with the W.
[SuperSU] shaggyskunk:
Yeah I thought that it was US Firmware - And no obviously ?

I'm using BK Manager to disable the Bloat - This is the first Android that I've ever had without Root - Yikes ?

But I've got to say that I'm pretty surprised that I can live with Stock Unrooted Samsung - It's way better than previous versions of TW - Between adb commands for apps that I've always used & Substratum it's quite good. The app that I do miss is TB and of course TWRP Recovery ?
[SuperSU] flipmode_11:
Hi Osmosis!

What is "1.34 2" inside the script?

Is this the version number?

Also, does it need to be updated to handle other versions of LineageOS?

Thanks mate
[SuperSU] osm0sis:
[DEV][TEMPLATE] Complete Shell Script Flashable Zip Replacement + Signing [SCRIPT]:

https://xdaforums.com/android/software-hacking/dev-complete-shell-script-flashable-zip-t2934449
[SuperSU] koolkunz:
su.d does not work for me for some reason.. I want to run this script at each boot

#! /system/bin/sh
swapoff /dev/block/vnswap0

i placed this script in sbin/supersu/su.d and set permissions to 0700 but it didnt work..

does anyone know what I am doing wrong ? using s7 edge on samsung oreo
[SuperSU] ktmom:
Is /system/su.d 0700? Has another script run ahead of yours and didn't finish?

I think a better place for these questions might be Working with su.d. You'll find ideas there to explore.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] koolkunz:
As i am on oreo ... I am in systemless sbin mode this there is no /system/su.d but /sbin/supersu/su.d

and i have read that thread but still struggling :/
[SuperSU] jcmm11:
Does the command work from a terminal emulator? Place a command 'touch /data/local/testscript' in your script. If the file is created you know the script is running (just make sure you delete the file after checking if you want to check again, or precede the command with an appropriate rm -f command)
[SuperSU] koolkunz:
Yes I have tested the command in terminal and it works and also using init.d through kernel aduitor but I want to do it without using a seperate app..
[SuperSU] tetakpatak:
All versions of CWM recovery until 6.0.5.0 had a bug that regardless of your response on that prompt on exiting from the recovery mode nothing would happen.

PhilZ recovery solved that just recently, I think after 6.48.6

tetakpatalked from P5110
[SuperSU] cbeckstein:
Well, what I reported happened with (latest) Philz 6.57.9 and supersu 2.09 and did not happen with Philz 6.57.9 and supersu 2.02...
[SuperSU] DesertEagleSlim:
Every time I download 2.09 beta the zip is corrupt or empty. Anyone have a alternate link?
[SuperSU] maksimus0021:
DEL...
[SuperSU] Frank Westlake:
Some download URLs (i.e. supersu.zip) are actually another HTML document which does an immediate refresh on the file to be downloaded, and some browsers will download that HTML document instead of the target file. Usually you can overcome this by selecting something like "open" or "open in new tab" instead of just selecting the download link.

Frank
[SuperSU] DesertEagleSlim:
Nevermind fixed issue
[SuperSU] nov.six@qq.com:
Beta 2.09 doesn't work on SAMSUNG GT-I9500 Android 4.2.2, it tell me no SU, and can not get the root.
[SuperSU] edzamber:
Works just fine on i9505 with Custom ROM Pyrana based GNH7 stock.

Posté via Pyrana v46 by Alan-B

http://xdaforums.com/showthread.php?p=53646684
[SuperSU] Flerou:
Download link to Beta not working -timeout

I have been trying since yesterday but the site seems to be down - always get a timeout error. Same thing when I try to open the main chainfire page. Opening links in new tab does not work either.

=>> DesertEagleSlim, how did you get that fixed?

---------- Post added at 01:40 PM ---------- Previous post was at 01:11 PM ----------

I am really getting pissed with that now.... I installed SuperSu, but cannot use it because it tells me "There is no SU binary installed, and SuperSU cannot install it. .... blabla" I even paid for it but cannot use it....

The suggested solution from the forum is to install the .ZIP version via recovery. The chainfire website, however, is unreachable, and I am not aware of any mirrors / alternative download locations. Can someone pls. help? Thanks.
[SuperSU] Conte Mascetti:
zip attached
[SuperSU] Flerou:
Thanks a million, that solved it!
[SuperSU] xanaxdroid:
I'm sure you already know but 2.09 works with no problems on hammerhead. At least for what I use it for.

Sent from my Nexus 5
[SuperSU] Fivesack622:
I know I've never posted here but I am on this forum alot reading and searching for solutions to my problems that arise. I've been holding off posting this but I think it may help based on some of the problems I have read that others are having (or I'm completely wrong and it won't, which is why I haven't posted til now, afraid of being ridiculed) . Either way, here is the situation...

I have a Samsung Galaxy S3 Mini (SM-G730V) running 4.4.2. It's a Verizon model and has a locked bootloader so I can't flash any custom recoveries. I just updated it from 4.2.2 a couple weeks ago and never had any issues with SuperSU til after the update. I rooted 4.4.2 with towelroot as the old method no longer worked. It rooted with no problem according to towelroot so I installed SuperSU. (I believe the current version at the time was 2.01 from the play store). I was told installation failed, to reboot and try again. After 2 or 3 times, it installed (even though it said it failed before I rebooted) and I was allowed to use SuperSU as normal. After rebooting later in the day, however, I was prompted to update the binary, which in turn would always fail. At the same time, I was still allowed to use my root apps. Now here is the interesting part....

I have the xposed module Wanam kit for TouchWiz installed and if I check the option to set SeLinux to permissive and then reboot, there are no more prompts to update the binary, even though the last binary update was said to have failed. If I uncheck the option to make SeLinux permissive and reboot , I get the prompts to update the binary again which will fail everytime until I set it to permissive again. I have tried every beta from 2.02 through 2.09 and everyone of them has this issue.

If this information is helpful and I can do some testing or provide any logs, please let me know what you need from me and I will do my best to provide whatever you need....
[SuperSU] Chainfire:
Any luck?
[SuperSU] Chainfire:
2.10 beta posted !
[SuperSU] madmack:
maybe provide a Changelog so we know what to look for? ;)
[SuperSU] Chainfire:
First line of the first post should point you where you want to go ...
[SuperSU] shekinahsmoke:
these two things are very helpful in my experience:

- Fix root access being forgotten for apps interested in overlay hide notifications

- Check for removed apps at boot, and forget their settings if re-authentication is enabled
[SuperSU] 78Staff:
No issues i337 and cm11 9.23 :good:
[SuperSU] Fivesack622:
On my Samsung Galaxy S3 Mini with Beta 2.10, I still am having the same issue with SuperSU asking to update the binary if the option to set SeLinux to permissive in Wanam Kit is not checked. Something I forgot to mention before was that after I unchecked the option to set SeLinux to permissive and reboot, I also get a toast from SuperSU saying that it has restored Superuser access right before it prompts me to update the binary, which as I said earlier fails everytime. But again, at no point do I lose any functionality of any of my root apps. Also, for what it's worth, I have had no issue with any of the betas on my Nexus 7 2013 running CyanogenMod.
[SuperSU] Megaflop666:
Delete
[SuperSU] JulianJenner:
2.42 OK with 5.0.2. RESURRECTION REMIX by Rammar515 on LGE-P760

Thanks [MENTION=631273]Chainfire[/MENTION]! Again and again and again…

Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
[SuperSU] elxufas:
Is great. :good::good:
[SuperSU] occtec:
2.42 All Good with 5.01 Stock Lollipop on Nexus 5 with Franco Kernel r69 + TWRP 2.8.2.0 Thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] PsychoPhreak:
Because sadly I didn't know, I just didn't want OTA update to fail, so I put the phone back to as stock as I could. I couldn't find anything at the time that broke down what could and couldn't be done so that the OTA would still work. Hindsight and all that. Oh well, thanks for the clarification!
[SuperSU] 0.0:
I don't know if beta v2.42 causes it, but my phone freezes randomly throughout the day and have to force shut it down. If I recall, it did not happen with v2.41. I'll keep testing

Edit: my device is a Moto X 2014 Pure edition

edit 2: Never mind, it froze again on v2.41. It is an app. Disregard this post

sent from my Moto X Pure Edition
[SuperSU] schwem:
2.42, best version yet! LG G2; liquid smooth 4.0 alpha 5.0.1; render R5 kernel
[SuperSU] benji14410:
Great ! working on my I9305 , android 5.0.1 .
[SuperSU] humphries09:
Working fine sm-g900a extreme debload 3.2 tether

from g900a extreme debloat 3.1 SuperSU 2.42 and way to much ect to type with gloves on in this cold
[SuperSU] willy1521:
Hi all...me and other people are on CM12 for HTC Sensation by Ivanich.

We have problems with superuser so we have tryed ho install SuperSU (2.40 or 2.42)...but it fails.

Ivanich says that: "main problem is that SElinux in cm12 uses very strict rules so apps with sysinit scripts like m2sd and superuser just can't work"

So, is it only a SElinux problem?

Thanks a lot
[SuperSU] fgl27:
boot loop on moto g 2014 su2.42

After first boot (4-5 min) all good.

after greenify some apps and a reboot, boot loop for ever....

wipe data/cache, flash su 2.42.... instal back all my app back.. greenify some app... reboot...

It reboot but takes 5+ min... tries 1,2,3 in the 4 or 5 it boot...

it's a working in progress... I hope to improve with time...
[SuperSU] Chainfire:
I have several CM12 devices with SELinux set to enforcing rooted with SuperSU here. Probably just doing it wrong. Make sure you're using the latest TWRP, and flash the latest ZIP. I was working on this very recently so a patch in 2.43 (not out yet) may have been relevant, in which case you'll have to wait a bit. Bit still 2.42 really should work.
[SuperSU] ciano865:
I am using CM12 21 dec. unofficial on my N4 mako, Selinux is set to "App", I've disabled Superuser in dev. options and after flashed SuperSU 2.40.

Using some root app like kernel managers, file manager, wakelock detector etc, all work fine. and i did not change SElinux in any way.
[SuperSU] willy1521:
Thanks for reply...I attach a log during installation of the script (v2.42).

https://dl.dropboxusercontent.com/u/63887949/SuperSU_242.txt

Merry Christmas!
[SuperSU] Master of Wizard:
Same problem in XT1069, the combination of TWRP 2.7.1.1 and SuperSu v2.38 worked best with me.
[SuperSU] fgl27:
Tks... I have the last TWRP 2.8.3.0 believe TWRP does not affect root.

Did some test.

Flashed su, did a first complete boot and turn it off.

turned it back on and counted time and bootloop's before completed the boot...

results

Device Moto G XT1069 android 5.0.0

2.38

bootloop 1 time

Total time to boot 3 min

2.40

bootloop 4

Total time to boot 7 min 30 sec

2.41

bootloop 0

Total time to boot 1 min 34 sec

2.42

bootloop 3

Total time to boot 5 min 45 sec

to be 100%, after it test, i did verify the root version and check root state with root checker.

will stay at 2.41 for now.

I will do more extensive tests, after a day or more using this version i will add the results.
[SuperSU] esrevinu:
In update-binary script, 'Youtube' should be 'YouTube', I think.
[SuperSU] devsk:
Was the test done only with one reboot? What about 2nd, 3rd and so on reboots? Did 2.41 stick with 0 bootloops on those as well?

Has anybody tried to debug this boot loop issue on Moto G phones? like add a set of debugs and see where we are failing? anybody got any clues as to why it happens? I mean the root does work on Moto G on Lollipop, so why does it fail some of the times?
[SuperSU] fgl27:
here is systematic, i tested a fill reboots and always the same.

The root works perfect on G 2014 in any version of SU that i tested, but the number of boot loops is different so i tested and informed if someone wants to test or use and already have my opinion...

The way it happens? because is a beta.

I do not expect to be perfect. Because the L was released a short time ago on G, will still take a while until it be perfect. :good:
[SuperSU] rickriego:
running validus 5.0.2 on d850 and getting this error after flashing supersu 2.4.2..
[SuperSU] laupuy:
Hi,

Just for information: Chainfire EOL-ing all my root-related things

https://plus.google.com/+Chainfire/posts/ZVDG2SnmgM5

:(
[SuperSU] Dead-neM:
Put "(YOUR CODE) &" or "{YOUR CODE} &" for you script to work without the quotes

#! /system/bin/sh
(swapoff /dev/block/vnswap0) &

this will work as intended
[SuperSU] rsndetre:
I can't wait for EU to trample into the ground all these abusive companies that made us beggars.

Yes, I want to rule my phone. I'm tired of loosing battery for no reason with each forced patch. Or of being a product under the pretense of personalizing offers. Or of the idiotic permissions and triggers systems.

Latest problem. I bought some Broadlink home devices. For some reason my phone (note4) is loosing the internet conection when using the Broadlink controling app, while idle. Rooted my device to stop the app from running in background because restricting background data doesn't solve anything (why would a setting actually work? Absurd)

Side effect, my bank app doesn't work. Suhide is bugged. So I use unSu, banking app is happy although rootchecker has no problem detecting the phone to have been rooted and the dam Broadlink app is back to crashing my connection although I used everything on it before reverting the root(permissio s revoked, triggers disabled, greenified).

So yeah, big middle finger !
[SuperSU] osm0sis:
Probably just needed to add your banking app to the suhide list. I had to add mine to MagiskHide.
[SuperSU] rsndetre:
I tried but suhide won't install (I get the folder but the app is missing).

I'll try the Magisk rooting solution. Thanks.
[SuperSU] andrew2432:
Was SuperSU installed in sbin mode? Did you flash suhide from recovery? Did you use the gui available with SuperSU suhide? I believe you can run command line commands to add things to the suhide list.

Make sure to unroot with either, or both to be certain, @0smosis unsu as well as: rm -f /system/bin/su and rm -f /system/xbin/su from terminal
[SuperSU] folusmile:
I think the end to Chainfire works has finally come, EOL, I salute you Bro for all the wonderful thing you hv done to Android community .May God bless you
[SuperSU] pointbob:
Dumb question..but will the SuperSU.zip on page 1 in this formum work with my sm-t713. Are there wrong variations is the su.zip that won't work my processor..I think it's arm8 ..64 but thank you!!
[SuperSU] Ibuprophen:
You may also find the following thread to be helpful for your specific device as well as obtaining some member guidance within it too.

https://xdaforums.com/showthread.php?t=3390627

.

I understand what you just stated and I do agree with you regarding the SuperSU EOL but, that is technically not true.

I know that I'm being overly technical here... LMAO! :)

I feel that SuperSU is technically not EOL in regards to the project itself because the project is just under new ownership.

I would honestly suggest that SuperSU is really an "Abandoned" development but, NOT by [MENTION=631273]Chainfire[/MENTION]. It's Abandoned by its current owner/developer [MENTION=7678190]SuperSU Release[/MENTION] (aka CCMT). LEGALLY Chainfire cannot do anything about this development unless approved/authorized by CCMT (though, based upon the recent announcement, this won't be happening anytime soon).

My opinion regarding Chainfire's mentioning of his pondering the release of one or more of his Source Code for his remaining developments... I just hope that he releases them to certain developers who are more familiarized with the development in one fashion or another.

This is just my opinion regarding this... :)

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] iceman0826:
So right there's no alternative to SuperSU? Aside from the mediocre Magisk?
[SuperSU] DB126:
There are a few others but none mainstream. While my preference remains SuperSU I would be hard pressed to mischaracterize Magisk as "mediocre".
[SuperSU] osm0sis:
SuperSU still works on plenty of devices. SuperSU v2.82 SR5, as the final release from Chainfire, is very stable and can continue to be used with no issue.

Also, there is absolutely no need to mud sling; Magisk is far from mediocre at this point and it's been excellent on my newer devices which SuperSU does not support. The only things I find myself missing are the PIN-code locking of root per-app and FlashFire support.