yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ibuprophen:
The xda-developers information for the SuperSU on the Play Store is just some residual information that was placed when Chainfire had posted the Free and Pro there.

I'm only assuming that Chainfire had left it unchanged, probably, with the understanding that CCMT would be including the xda-developers for support and information. I doubt Chainfire can change it now that it's transferred to them.

I had paid for the Pro version not long after the Pro was placed on the Play Store and the only thing that I'm satisfied with regarding my paying for it is both that it was not a ton of money and also that my purchase went to Chainfire (and including a few donations over time).

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Bobbaloo:
Glad to see I'm not the only one still hanging on lol! And, I paid for pro also....
[SuperSU] a g bell:
Lol no your not uhmm ?
[SuperSU] Mzprx:
I'm sorry guys but after reading this study:

https://www.reddit.com/r/Android/comments/54xdmp/ccmt_who_exactly_are_the_owners_of_supersu/

I got cold feet and switched to Magisk (so far without any problems - at least until the next OTA Google update). Supersu still does not work on my Pixel.

Besides, I don't trust secretive companies to have access to the root of my phone. The fact that the company in question seems to be in secretive country (no offense) and doesn't give a $#1t for the customer base for a month does not help either. Sorry - too many cons to stay even if chainfire comes back and fix SuperSU one last time before walking away for good.

BTW I also have SuperSU Pro for a long time and don't regret paying for it as the money went to chainfire.

Happy New Year everybody!
[SuperSU] Bobbaloo:
You may be right. I might be ready to jump that ship too
[SuperSU] vandyman:
LOL.. Jump ship.

I jumped went I purchased the Pixel 2.

I had no choice. (zero).

Anyway I thought that I was going to be a castaway on my own island.

Hell, it is new country now called Magisk.

And the capital is TWRP.
[SuperSU] wetxxx:
I have HTC 10 S-OFF and locked. When my phone back from service I restore Only Data partition but I root checker give me information that i dont have root. I can't see supersu aplication so I restore all backup (system image, boot, data) but still same situation. Root is present but root checker still give me something wrong, titanium backup report no error, but i don't see Supersu aplication. I try install this last from Shop but instalation process is aborting. What I should do?

"Live long and prosper"
[SuperSU] Mzprx:
Get the superuser.apk from the "common" folder inside the

SuperSU zip file. Install it and you should have SU in your app drawer. However something seems goofy since TB works but root checker says you have no root.
[SuperSU] The Analog Kid:
Hey! Yep, there's a thread, indeed; though funny enough, [MENTION=4544860]osm0sis[/MENTION] informed about his most recent unSU update right in this thread on October 27! Even funnier: I was already subscribed to [MENTION=4544860]osm0sis[/MENTION] thread for sometime now!!!... I guess I need some vacation :rolleyes:
[SuperSU] Ch3vr0n:
Flashfire paid? Then you need to take a closer look. ALL functionality in FF is free. The pay option only is for showing support. There's currently NO DIFFERENCE WHATSOEVER between the free version and pro users.

Sent from my Nexus 6P with Tapatalk
[SuperSU] vandyman:
Support the developer.

Flashfire Pro is version 0.73.

PS. I am a little loopy in the head right now.

I have been in the hospital since Christmas night.

My appendix exploded and I am happy to be a live right now to have a little joy here on XDA... Sorry for the crying...
[SuperSU] Bobbaloo:
Quick and painless!

https://www.androidexplained.com/switch-supersu-magisk

I did the unroot thru SuperSU option
[SuperSU] Ch3vr0n:
I did support, I'm running pro. As with all the other chainfire apps I'm using. Though I wish he hadn't left. Ccmt screwing up Supersu is an understatement.

Sent from my Nexus 6P with Tapatalk
[SuperSU] Ibuprophen:
I believe that you may be misunderstanding what might have happened behind the scenes...

I honestly don't believe that Chainfire's retirement from SuperSU was decided, deliberately, to abandon the development for CCMT to do what they are doing now. I really don't believe that this is how Chainfire operates (nor in his nature to do).

I, personally, believe that CCMT had made assurances (in various ways) to Chainfire that they won't do what their doing now and ONLY stepped aside under the request (or asked to) by CCMT and I truly believe that if Chainfire stepped in at all may cause friction in some way between the two since he no longer owns SuperSU.

If anyone believes that what negative impacts that are happening now is the fault of Chainfire is really not fair to Chainfire at all.

I just stated the above as a personal perspective because I know that there's more to it behind the scenes.

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] badhabit_wb:
I imagine that there were non-disclosure agreements and non-compete clauses that would keep him from even commenting on what's going on now, or doing anything to fix SuperSU.It's really hard to control something once you sell it.
[SuperSU] Ch3vr0n:
Last time I checked I didn't say CF screwed up selling? it to ccmt. I said ccmt is screwing up with SuperSU, and they're ruining the very good reputation that took CF a long time to build and very well earned. Support doesn't exist, their forum is filled with Chinese fake diploma selling spam, no new builds since they took fully took over...

I'm not blaming his retirement, he earned it. Though unfortunately it seems to have been the end in SuperSU's life for the moment.

I'm not misunderstanding anything

Sent from my Nexus 6P with Tapatalk
[SuperSU] Mzprx:
Well, since SuperSU did not root my phone, I couldn't use "Full Unroot" as the app won't open at all. So I uninstalled SU as any other app, installed Magisk and since Magisk gave me root, cleaned the last remans from SU (in /data/adb/...) manually. RIP SU :(

In addition, the link in step 1 of the Android Explained is broken and won't download unSU. If anybody needs unSU , it can be found here:

https://xdaforums.com/showpost.php?p=63615067
[SuperSU] Ibuprophen:
You never know... Maybe [MENTION=631273]Chainfire[/MENTION] will develop another Superuser app/tool that's severed from SuperSU. :thumbup:

I should have wrote to Santa Claus for this... Darn!!! :eek:

As the song goes, from the Beach Boys, "Wouldn't it Be Nice..." LOL :D

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] gothicVI:
I'd honestly prefer seeing his expertise via contributions to magisk.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Ibuprophen:
Nothing wrong with Magisk and it's an excellent development indeed but, not everyone can/does use Magisk (including myself).

I've got a limited working knowledge of Magisk only because of Magisk users using my other developments and I, personally, just don't find the need for using Magisk (at least at this time).

I believe that the Magisk developer(s) has collaborated with Chainfire previously but, I'm not sure if they still are.

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Spike`:
anyone that dont have bootloop after flashing supersu sr5 but still dont have root after boot and no SuperSU on App drawer try this, i found this for nitrogen 8.1 rom

Download from https://mirrors.ustc.edu.cn/lineageos/su/ the 14.1 addonsu appropriate for your device (addonsu-14.1-arm-signed.zip, addonsu-14.1-arm64-signed.zip, addonsu-14.1-x86-signed.zip)

Open SR5-SuperSU and extract Superuser.apk from the folder common to your device

or

Download latest supersu sr5 apk version from here -> https://www.apkmirror.com/apk/codin...elease/supersu-2-82-sr5-android-apk-download/

Then flash your rom > gapps > supersu > addonsu-14.1 (your appropriate version)

After boot install Superuser.apk. You should have root and supersu now...

Its a little tricky but it worked on that rom and before anyone ask no, addonsu-14.1 alone will not give root

try it for your device/rom
[SuperSU] Bobbaloo:
Redacted
[SuperSU] Mzprx:
It sounds like possible workaround, but also seems to be temporary handicap solution and don't solve the core problem. I don't think that was the spirit behind the SuperSU which was wholesome simple rooting solution with no (possible) strings attached.

Also, it relies on yet another software from CN, which I personally don't trust giving access to my root, especially since looking inside the zip it seems it installs stuff in /system which suggests it is not systemless installation and can bring undesirable consequences down the road.

This is just my personal opinion and is not intended to offend anybody. My apologies.
[SuperSU] Spike`:
y totally get it and also no guarantees that this work on other devices/roms. I'm also hoping for a new version of supersu

isn't the best solution but at least for nexus 4 nitrogen 8.1 was the best one because magisk causes lag on that rom

so i'm just sharing what i found and worked, for many isn't the best solution or even if this work on your device/rom but just sharing for the ones that simply just want to try to have supersu work instead of magisk (again, no guarantees that it will on your rom)
[SuperSU] The Analog Kid:
I have this issue with SuperSU. Reinstalling it didn't helped. Which can be the cause?
[SuperSU] Alxoom33:
Good bye SuperSU I'll miss you! But without [MENTION=631273]Chainfire[/MENTION] at the helm it is not the same!

Uninstalled SuperSU and updated to Magisk 15.1.

Will keep an eye on this thread to see if there is any reason to return. So long..... :..-(
[SuperSU] Bobbaloo:
Congrats! Farewell to a boy named Su
[SuperSU] Badger50:
Bwahahahahaha...Nice one Bobba. Gotta love Johnny Cash! :good:
[SuperSU] osm0sis:
No.. If you read that link and/or look in the script, it's for all root types.
[SuperSU] Mzprx:
Hmm... I see... You are right. I apologize - the first time around I missed this. I will edit my previous post.
[SuperSU] wetxxx:
I have a problem with restore my previous twrp backup. I backuped boot, data and system image partition. When my phone was back from service I do restore RUU from zip 2.41.401.41 than do Bootloader unlock, twrp, susu 2.82 sr5 than sunshine locked/soff. Now I try to restore my data, system image and boot partition and when android was started I can't see supersu aplication and root checker shows me that I don't have full root permission. I try install supersu from play shop and manualy from susu.zip archive and nothing. What is wrong? Maybe when I first time in twrp I don't care about system read only?

"Live long and prosper"
[SuperSU] Chainfire:
Thanks for the kind words. I can't go into your statements but some of them are pretty close to the truth.

However I do want to clarify that CCMT did not ask or force me to step aside - in fact I think they would've extended my employment given the chance. But life happens, and I would probably have had to (at least temporarily) step back even if CCMT didn't exist.

I know everyone likes to vilify CCMT, but the truth is that their people have never been anything but supportive towards me and my work. Regardless of your opinion on their current performance, I know them only as well-intentioned and friendly people. And finding skilled people in this market is very hard...

I am sorry that some of those who voluntarily (they could've used the freeload button instead) paid 2 or 3 dollars for 5 years of almost 24/7 support feel cheated, but there is nothing I can do about that now.

It is pretty safe to say that I will never (again) contribute to anything that guy had a hand in.

For the good of the community I have repeatedly refrained from taking action (and have asked other mods to refrain as well), but some things that happened were even potentially perm-ban worthy. There's plenty of icky stuff to go around with the rise of that package. But the community has chosen their bad guy, and it is apparently me: so be it.

---

Perhaps I will return to (serious) Android development around March, perhaps not. In the mean time it will be very rare for me to drop in on XDA at all.

Either way, happy new year to all, I hope 2017 was good to you and 2018 will be even better!
[SuperSU] gothicVI:
I'm hearing such accusations for the first time now. Could you please clarify your criticism?

I think you

completely

misunderstood my point. Let me clarify it: I don't think you're a/the bad guy in any way! (How would you even infer this from my post?)

I - not knowing anything about your aforementioned criticism w.r.t. Magisk - only wanted to suggest your contribution to that project because I value open source development from an ethical point of view. Furthermore I don't see the point in having basically two solutions to the same problem. Bundling expertise and resources sounds more reasonable to me. Please feel free to comment on that.

Also a happy new year to you and all the best for your future. Thanks for your contribution to the community!
[SuperSU] Ch3vr0n:
For the record, I don't regret spending anything on any of your apps. Worth every damn penny, every single app. Support has always been excellent. Personally I don't blame you for anything at all, rather I just wish ccmt would get their act together I suppose. Little to no communication at all, no new builds and even their own forum is mess of spam.

As long as it works I'll stay with SuperSU. Hasn't let me down a single day yet since I started using it.

Enjoy your well deserved time off and hope to welcome you back into the development world sooner rather than later.

Happy New Year!

Sent from my Nexus 6P with Tapatalk
[SuperSU] vandyman:
Thank you Chainfire for posting.

I am fan of your work and always will be.

See yah in the near....
[SuperSU] veez21:
?

I wonder what happened..
[SuperSU] TonikJDK:
I am not sure I understand. I have seen nothing but praise for [MENTION=631273]Chainfire[/MENTION] in this and other threads. Nothing but thanks and well wishes on his future endeavors. People are disappointed but I have not seen a thing that implies people have labeled him a bad guy.
[SuperSU] xdarkstar:
August 2016:crying:
[SuperSU] veez21:
So, what happened?
[SuperSU] KaMyKaSii:
The only public conflict I know related to both was when topjohnwu was developing Xposed Systemless (before Magisk) and was using some SuperSU binaries (sukernel if I remember correctly) without Chainfire's permission. Both are great developers and I hope they solve their disagreements. If Chainfire plans to continue developing root apps but not a new superuser manager or even with small contributions to SuperSU, it would be great to see him helping to make Magisk better. Anyway, we can only thank him for everything he has done for this community. Chainfire, you're the man! :highfive:
[SuperSU] Chainfire:
I might rehash the whole thing once I am legally completely free to comment some months from now. But it won't change anything, so what'd be the point really? I'm just saying I won't be contributing there.

Besides if I would return to root dev it would be bad form to not offer my services to CCMT first.

Sorry I did not mean to imply this was you specifically, it was a general statement. I have also seen others comment they have not seen it. But it is a thing. You don't really see it in these threads because it is moderated away, and the same is also true for my G+ as long as I read the comments to a specific post.

However there have been quite a few awful comments here (and in other threads), on my G+, Twitter, etc. I can hardly be mentioned or post on /r/android without trolls coming out detailing my evil ways. Admittedly the latter are only a very vocal few, but that is enough to sway to average reader's opinion. Actually fascinating how that works. Not to mention the abuse (and the rare actual threat I do my best to ignore) I receive by email/dm/pm sometimes.

This has died down a lot since I posted my retirement though. And it's probably ultimately not more than a few hundred people in total (out of millions of users), but over time it wears you down.

Well all I can say about that is that if you're looking for ethical purity you will find it neither here nor there. Ultimately that makes little difference for the end-result though. It just amuses me if people bring forth the ethical argument.

I'm not against open source though. SuperSU just didn't originally go that way. It was considered multiple times over the years though, long story.

It wasn't me who decided to split the community. It could have been a successful longterm co-op...

That being said I think there are a lot of pro's and con's to having multiple solutions.

-----

Heh actually I just came here this morning to wish everyone a happy new year, not sure how I managed to turn it into this drama again. Sorry :)
[SuperSU] Locura18:
Happy New year [MENTION=631273]Chainfire[/MENTION]. Happy New year everyone
[SuperSU] Bobbaloo:
Su was the best. I Don't regret having had the pro version. Thanks for all your work and years of root!
[SuperSU] Alxoom33:
Thank you [MENTION=631273]Chainfire[/MENTION]! Happy New year and much success in your future endeavors! Thank you for enriching our experience with Android and our lives with your brilliant contribution. No, I never for a second regret purchasing the Pro versions of your apps. I always considered it a Contribution for the wonderful work that you did, not a payment for future support!

Hope to read that you are back on XDA in some capacity. Best wishes my friend!
[SuperSU] mielletseed:
No, it was the first version of magisk where he used Chainfire's work without permission, not systemless xposed. And after all in my opinion the core idea of magisk is the systemless su concept of Chainfire transferred to more use cases ...

Thank you a lot [MENTION=631273]Chainfire[/MENTION], I always used and use your root solution from the first days on.
[SuperSU] Sneakyghost:
:laugh: The force is strong with you, Sir.

Happy new year and good luck with your new path. I have been watching your work from a distance and not been vocal in your threads. Now that you decided to walk a different way, let me just say thanks and goodbye!
[SuperSU] Ibuprophen:
This is why I had tried to make it as clear as I could with keeping an open mind since we don't know what may or may not have happened behind the scenes [MENTION=631273]Chainfire[/MENTION] since you have a long and outstanding history for providing support and can't control what CCMT does since its theirs now.

Happy Holidays to you, your Family and Friends!!! :)

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Boriar:
I bought nearly all your apps (even someone's I don't need anymore) only like a 'little' payment for all your efforts, and never for future support. And now that you decided your retirement I only can give you the best of wishes.

Happy new year [MENTION=631273]Chainfire[/MENTION]! You are the best!
[SuperSU] Ibuprophen:
Just an FYI in case you weren't aware...

Chainfire only Retired from the SuperSU. He will still be continuing his other developments... :thumbup:

Happy New Year!!! ;)

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] Boriar:
Thanks, I know. Love his cf. Lumen and Flashfire, but for example I don't need anymore triangle away.

And also love your Selinux Switch ;)

Happy new year for you also!

... And all the people on xda, of course!
[SuperSU] ashyx:
Whatever happened to ChainsDD?
[SuperSU] mobileman88:
Happy new year [MENTION=631273]Chainfire[/MENTION] I am so glad to have supersu and will always have fond memories of you about it. Forget about all few naysayers here and elsewhere
[SuperSU] DB126:
Best wishes to [MENTION=631273]Chainfire[/MENTION] in 2018 and beyond. A selfless contributor to XDA and the larger Android community while maintaining the highest level of integrity.

Happy New Year to all.
[SuperSU] jcmm11:
[MENTION=631273]Chainfire[/MENTION] Just want to add my best wishes and say thanks for all your work. Happy New Year, and hope to see you back on XDA in the near future.

Just ignore the naysayers - they're most likely clueless.
[SuperSU] Mzprx:
Man, nobody on this forum ever said anything against you - only a great respect. We (maybe I should say "I") felt left by CCMT after the release of 8.1 and the problems it created with SuperSU. They did not provide any response.

I never regret paying for SU Pro.

I installed Flashfire I will pay for Pro as soon as I'm sure I will be using it. Enjoy the free time an hope to see many new great things from you in the time to come.

Happy New Year to you and all other folks on XDA. Cheers!
[SuperSU] badhabit_wb:
Happy New Year Chainfire! Hope 2018 brings you the best. Thanks for all you have done. I've purchased all of your apps and they were a bargain. Anyone that gets upset about your retirement is acting like a spoiled brat.
[SuperSU] chudy_85:
Happy new year for all user supersu.

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[SuperSU] NLBeev:
Wish you happy 2018 and the power to ignore dissatisfied chatter. Hope to hear from you once in a while.
[SuperSU] ante0:
Anyone know how SuperSU installwr mounts su.img? I get the losetup help text in recovery.log so not sure if the syntax is incorrect, or if my losetup is too old/new.

It looks like the syntax is correct in the util script... Maybe one of the variables isn't set...
[SuperSU] ashyx:
It's mounted at every boot by the init.supersu.rc script.
[SuperSU] ante0:
That I know. But since it can't mount or make a loop device using losetup it never creates the su.img and installs to /sbin instead.

I just want to know what syntax it's using for losetup.
[SuperSU] jcmm11:
Osm0sis has a mountsu zip. Check that script for how-to.

Note that if you're running Oreo you should be using SR5, and that it no longer uses su.img, defaulting to sbin mode.
[SuperSU] ante0:
OH. That makes sense then xD

Well. It probably is "system-less" then, I was wondering why it was in /data/adb (like magisk).
[SuperSU] kenshinxl:
Failing to install SR5 on the latest January binaries for the Pixel XL. Attached is the twrp recovery log.
[SuperSU] jcsww:
Everything is good on the latest Nexus 6P stock image with 2.82 SR5 and suhide.
[SuperSU] BigThunder:
I have the same issue.
[SuperSU] Ric G:
SR5, January update

Failure patching sepolicy, aborting.
[SuperSU] Ch3vr0n:
failure providing (twrp) install log, aborting.
[SuperSU] Ibuprophen:
More information is needed...

Try attempting this again in TWRP. Then after the failure happens, go back to the main TWRP screen and select Advanced --> copy Log [check off the "Include Kernel Log" if you see that option] then swipe (at the bottom) to copy the log to the SD Card and then reboot your device.

Return here and provide that log file along with a little more information regarding your device, ROM installed, etc...

It may be that you don't have a custom/modified kernel that allows for SEPolicy changes/modifications but, I'm not 100% certain of this either.

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] Ric G:
Pixel XL - January update issue
[SuperSU] jsbeagle:
Looks to be same problem here:

Verizon Pixel XL

unlocked bootloader

Sideloaded January 8.1 Factory Image, let apps reinstall, installed TWRP 3.2.1, tried flashing SuperSU and it didn't work.

TWRP log attached
[SuperSU] osm0sis:
Looks like libsepol needs an update. Magisk recently had to do the same.

[MENTION=7678190]SuperSU Release[/MENTION] [MENTION=631273]Chainfire[/MENTION]