yashsingh1/xdaforums huggingface dataset:
[SuperSU] xell75:
Yeah honestly I don't really like that Magisk is the one and only solution to have root on newer devices, there is nothing to choose from anymore. On my side, Magisk was Never Stable, most of the times I easily got bootloop just for installing random modules or I randomly lost root. With SuperSU I never lost root, I installed it and it worked. Magisk is one of the reason why I keep my new main phone Redmi Note 5 AI unrooted and locked. (My S4 is just for testing the new Pie Roms how they perform on such an old device)
[SuperSU] Ch3vr0n:
I'd drop it in a heartbeat if I could. But I need root for certain things (like call recording), and on my new phone (pixel 3 xl) it's the only option. So far it's working, but I don't like the fact that now there's only 1 root option in general. Although it being open source, kind of eases the worry of someone adding 'bad code' to it and it going unnoticed.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] madbat99:
For a long time SuperSU was the only choice. So, it happens. But it's not so much magisk that is unstable, as it is rooting Android has become much more difficult.

I would actually like to see a magisk version that just handles root without any module functionality at all. I think that would squash alot of instability issues. 2 versions would be harder to maintain of course. But having one for root only for those devices we don't need modules for (or safetynet for that matter) would be a great addition.

SuperSU definitely wouldn't pass safetynet on a modern device anyhow.
[SuperSU] Strephon Alkhalikoi:
The entire reason Koush open-sourced Clockworkmod Superuser was because SuperSU wasn't open source and he wanted to be sure an alternative could be built. topjohnwu used a fork of that code along with snippets of code from other sources to create Magisk. Point being if you have the skills and the code, you could build that alternative to both Magisk and SuperSU and everyone will be happy.
[SuperSU] ashyx:
I was under the impression the underlying root was actually PHH super user?
[SuperSU] habylab:
It was originally, but I think it has been changed beyond recognition. I think. There has been a lot of conversation back and forth over copying code.
[SuperSU] ashyx:
Well I expect it has. At the end of the day root is root and how it's achieved is pretty much going to be the same.

Root should never be closed source anyway, but I understand why Chainfire made supersu closed source.

The only way to keep unwanted prying eyes away.
[SuperSU] Strephon Alkhalikoi:
Phh was forked from Clockworkmod Superuser.
[SuperSU] mattgyver:
A little bit of thread cleaning..

Rather than feed those who post like he did (though it could have been some foreign language, as Indonesian was detected by browser extensions) report it and move on.
[SuperSU] mattgyver:
More thread cleaning...

Keep the off-topic stuff in the Off-Topic forum. Hijacking threads, even temporarily, to complain about past moderator actions doesn't do anything but make more work for people trying to find help.

If you have issues with moderator actions, PM the mod that took said action. Find out why that choice was made, if it wasn't publicly stated why when the thread was closed. Clearly there must have been a reason for the mod to close the thread, rather than just clean it.

Keep posts on-topic.
[SuperSU] THIELE13:
:confused:
[SuperSU] osm0sis:
You should probably close this thread too, honestly, considering it was Chainfire's unofficial beta build thread and he's completely done with SuperSU. That will force any discussion about the corpse of SuperSU over to the official CCMT threads where it belongs. :(
[SuperSU] Ibuprophen:
I had asked [MENTION=335322]MikeChannon[/MENTION], [MENTION=2235607]svetius[/MENTION] & [MENTION=631273]Chainfire[/MENTION] about a similar question regarding this topic last September.

I had suggested that the primary threads be closed but, one of the existing threads kept open and have its title changed OR create a new one, with a more unified thread title for members to have a place to discuss the SuperSU development itself.

Maybe a basic/general title like "[UNIFIED] SuperSU Discussion" or similar...

I only suggested that so members who still use SuperSU could have a place for discussing, guidance, support, etc...

I just feel that closing them all down could, potentially, result in a slew of new threads throughout the forum and keeping in mind that there's members who still use SuperSU on devices with older Android Versions and such who would feel Cut-off otherwise.

Just a little suggestion/recommendation My Friend! :thumbup:

Though I'm just a little RC... :eek:

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[SuperSU] tsongming:
I agree, this thread should stay, and SuperSU is still very useful.
[SuperSU] LukeSlovian:
I am asking for your support, what should I do? I am asking for technical advice, omitting the manufacturer's service, etc. ... because I spent so much time to unlock the boootlader, download TWRP Recovery, upload Root by SuperSU, and how to send to the service of the manufacturer LG, they will erase LineageOS and will upload the original Android, which is smelled not needed applications that make the phone silent.

When charging Lineage bootanimation, the LG G4 H815 smartphone does not want to load completely. I am asking for support. Before updating binary files, LineageOS 15.1 Oreo 8.1.0 was running smoothly and without any technical problems. I have this condition since updating binary files from the smartphone in the Super SU 2.82 Pro.
[SuperSU] laupuy:
Maybe ask in the thread of your rom what others use for root.

For LOS 15.1, maybe try the official LineageOS Su here: https://download.lineageos.org/extras

Start from scratch, wipe data, cache, dalvik, system

Flash rom, gapps, su (from LOS).

Reboot and activate Su from developer options.
[SuperSU] madbat99:
Conspiracy theory: LoL. Maybe CCM is greasing someone, who is greasing someone to keep these threads open. To keep the questions contained. Just a thought.
[SuperSU] ROO3VER:
I'm not sure if this wil help solve your problem but i remember being on LOS 15.1 (or any LOS) and having to flash the UnSU-script by [MENTION=1143630]osmosis[/MENTION] before flashing SuperSU:

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067

It has something to do with removing all traces of the built in LOS-root before being able to use SuperSU.

If the SuperSU-icon doesn't appear after flashing SuperSU look for SuperSU in your settings, if it doesn't appear there eigther try installing SuperSU from the playstore.
[SuperSU] LukeSlovian:
Hello my friend ROO3VER, I have now released the flashing Supers 2.82 standard version by the zip package.

Immediately, the icon does not appear to me, but I think I solved this problem. I downloaded two apk Super SU files

Interestingly, flashing a zip pack from SR5-SuperSU-v2.82-SR5-20171001224502

I am informing you that I have root privileges, given by flashing a Super SU packet,

because when I try to run a reboot recovery in the official TWRP Recovery application, this reboot to recovery TWRP starts running for me

However, in order to have the Super SU icon, I must manually flash the apk Super SU file from the system level already.

So, therefore, I am asking you with a very heartfelt request for your technical support, because I can not update binary files correctly, as I flash by TWRP Recovery, this recovery after I finish binary flashing does not reboot my device to Android Desktop. And when it's flashing from the system level, then when the message about restarting appears, LineageOS stops me on the Animation Boot. I am asking you for support.
[SuperSU] ROO3VER:
I'm not sure what your problem is, you say you have root and just want the SuperSU-icon to appear?

If so just manually install SuperSU from the playstore or another source you trust.
[SuperSU] DB126:
Reload and stablize stock before flashing Lineage. Don't change the boot animation; always dangerous if you don't have a backup or other fallback plan.
[SuperSU] LukeSlovian:
Hello, I am addressing you with a very sincere request for your support. Due to the fact that in LineageOS 15.1 I had complications with the correct launch of the GSM module - despite the correct insertion of the sim card, to the SIM card slot, when the LineageOS 15.1 is activated, the icon from the range is not active for a long time. Therefore, I decided to return to LineageOS 14.1 Android 7.1.2 Nougat.

Dear Forum Users, as recommended by one person from the forum, I tried to flash the Root application in LineageOS 14.1 with the Magisk Mask application in LineageOS 14.1 Android Nugat 7.1.2, however, TWRP recovery tells me that the flashing process from the zip package is not possible to run, details on the video>

https://photos.app.goo.gl/fYJ7d2dx77QQaVjE9

Dear users, I am currently using LineageOS 14.1 Android Nougat 7.1.2 but as I would like to go step by step to LineageOS 15.1Android Oreo 8.1.0 then I will be very happy. However, currently I have here in Android Nugat 7.1.2 trouble with running Flashing Magisk Mask v19 zip

Due to the fact that currently I have trouble with the correct start of flashing the zip package Magisk Mask v19 I am asking you with a very hearty request for your support.

It informs that after the restoration of LineageOS 14.1 Android Nougat 7.1.2 by TWRP recovery I removed the Super SU application manually from the desktop, thinking that I could replace the problematic Super SU on Magisk MasTWRP

Flashing the Magisk Mask v19 zip application works successfully on LineageOS 15.1 Android Oreo 8.1.0. Yes, if I manually remove Super SU in Oreo 8.1.0, flashing Magisk Mask v19 zip works successfully through recovery TWRP

In connection with the problem described above, I am asking you with a very cordial request for your support in the subject.

I am asking for your technical support. Sincerley, Luke
[SuperSU] Ch3vr0n:
Double post and wrong topic, good luck. https://xdaforums.com/showthread.php?p=79307430

You're not going to get any/much magisk help in a superSU topic, and superSU itself is dead.
[SuperSU] LukeSlovian:
Ok, thank you for Your support

I am asking you very warmly for your support. Since I currently have Root made by Super SU, in LineageOS 14.1, I did not know that the Super SU is dead and that support has been given. But I do not have icons with the application, because I manually uninstalled Super SU, including LineageOS 14.1, please help me. I currently have LineageOS 14.1 in LG G4 H815 and is rooted by Super SU. Due to the support for Super SU, I would like to receive support in this section, which partition should I clear? Which partition is associated with the root, and specifically on which partition the files and permissions of root files are saved, if we are flashing a Super SU zip package via Recovery TWRP?

I really want to change the root method, i.e. ... through Magisk Mask, do root in LineageOS 14.1, but first I should clean up - delete and clean these files after Super SU on partitions.

Ok, I understand that support for Supers has been given. In connection with this, I am sorry that I wrote in the appropriate section of the forum.

Ok, thanks for your support. I am asking you with a very cordial request for your technical support, if at the moment if I made root flashing, a packet of SuperSU zip, through TWRP Recovery, I think it would be good to remove the root, made by SuperSU.
[SuperSU] Wolfcity:
You must have one thing clear: You can only use one root method, as there are:

SuperSU (deprecated)

Magisk (developed)

Lineage root

If you have used one of those and want to switch to another all traces of the former root solution has to be erased.

Your video shows that your boot.img has been tampered by some other rooting app.

So I recommend:

Flash unSu.zip (removes all traces of former root apps): https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067

Or do a

clean

flash of your preferred custom ROM.

After setting up your ROM (and gapps) flash the current stable 18.1 magisk.zip:https://drive.google.com/file/d/1AwJ-YsXsE4A6dD3l0PSEOpRVMGuhJti4/view?usp=sharing

If any problems occur move to the magisk support thread:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3261
[SuperSU] Gold_Phenix:
Where i find latest stable updated version Super Su ? From first post links don't work ...

Wysłane z mojego LG-H850 przy użyciu Tapatalka
[SuperSU] firefds:
This is it.

If it doesn't work, switch to Magisk
[SuperSU] devsk:
A request to OP please: when you change the version, either leave a link to the older version or use the same folder for storing various versions...e.g. 2.42 BETA is: http://download.chainfire.eu/644/SuperSU/BETA-SuperSU-v2.42.zip but 2.41 is not accessible from the same page: http://download.chainfire.eu/644/SuperSU/BETA-SuperSU-v2.41.zip. That's because that "/644/" in the path changes from version to version.

I would suggest a flat structure: http://download.chainfire.eu/SuperSU/[BETA]-SuperSU-v<version>.zip. Version is already encoded in the file name, so additional folder is not needed at the top level.

OR

provide all links in a post somewhere for archival.

Having said all that, what is the URI for 2.41 please? It looks like that version seems to work with Moto G without boot loops.
[SuperSU] FtaWolf:
Seems to be working fine on S5A.

Samsung unlock Bootloader on SM-870A.

That's ok looks like different Phone my be way go.
[SuperSU] Arturiuz!:
I noticed after flashing this is that my YouTube app disappeared..but everything works good,as usual. Thank you!

Xperia M Single C1905

UBL-TWRP v2.8.0.0

CM12 Unofficial-beta2
[SuperSU] occtec:
[MENTION=631273]Chainfire[/MENTION] bought the pro version last night to support your outstanding effort. Thanks mate ?
[SuperSU] AtomicPlayboy:
Is anyone else having problems reaching chainfire.eu? isup.me/chainfire.eu says its down.
[SuperSU] jakhan12:
Yeah. Im trying too,. its down
[SuperSU] archbox:
Mirror?

Sent from my One M8
[SuperSU] fgl27:
I have this mirror

there are the last 6 versions...
[SuperSU] fmc000:
Just FYI, 2.42 working perfectly on One Plus One - CM12 alpha - Dec27 build.
[SuperSU] :
cm12 alpha?
[SuperSU] fmc000:
This ROM.
[SuperSU] :
Aaah, OK, understood. I'm using the same. Thx
[SuperSU] shoiby:
[MENTION=631273]Chainfire[/MENTION] thanx for your enormous efforts but there is a bug i want to report since the 2.40 & in 2.42 also, it seems supersu doesn't grant permissions to du battery saver pro.

there is no pop up shows up when you chose the option lower cpu frequency in the smart settings of DU BS please if you can help fix this or if there is a manual method to grant these permissions to the app

Thanx and merry christmas

---------- Post added at 01:13 PM ---------- Previous post was at 01:08 PM ----------

BTW i have

note 3 n-900

lollipop 5.0

supersu pro 2.42

DU Battery saver pro 3.9.6.5
[SuperSU] AutomationLab:
How do I manually install 2.42? I can't find a how-to anywhere.

I have CF-Auto-Root and SuperSU 2.40.

Thanks
[SuperSU] kingvortex:
If you have a custom recovery, then flash the zip available in the first post.

If you don't, simply extract the zip and install the SuperSU apk, then open SuperSU and let it update the binaries if needed. It's in the directory named common.

Sent from my C6603
[SuperSU] AutomationLab:
Thanks for your reply.

But if I open SuperSU, I only see this PopUp, and the App will close immediately, so I can't do anything.
[SuperSU] kingvortex:
I assumed you were already rooted, because you said you had SuperSU 2.40. Is that not the case?

If not, you need to root first. Check your device forum to find out how. :)

Sent from my C6603
[SuperSU] AutomationLab:
Yes, i rooted it with CF-Auto-Root, but I can't update SuperSU because I don't know why.

This captcha is really annoying. I need 10 times because I can't read it. Please turn this off. Or why do I have to do this every time?
[SuperSU] kingvortex:
I don't know why it wouldn't update. I never have any problems, but roms/devices vary. Try rooting again, verify you have root and update to 2.42 again. If that doesn't work, I'm out of ideas.

Sent from my C6603
[SuperSU] AutomationLab:
Well, that's my problem. I don't know how to manually update to 2.42. :confused:

Or could it be possible that it doesn't work because I use CF-Auto-Root for Android 4.4.2?
[SuperSU] jcmm11:
If you insist on SuperSU use sr5. Those links work and it's beta in name only.
[SuperSU] xanthrax:
enjoy the forums! :)

thread cleaned
[SuperSU] phonesrepair99:
G4 Plus

hello fiend,

Can Use for moto g4 plus?

thnaks
[SuperSU] Wolfcity:
You can try. This app is abandoned for a long time now. It may work up to android 7.0 and in some cases up to Oreo. The actual and developed rooting solution is magisk
[SuperSU] mrrocketdog:
working on Viper N build (7.1.2) , moto g4 play.:good:

err on the side of kindness
[SuperSU] andreoide:
True. I use it on my S2 which I use for play music to my BOOM2 Bluetooth speakers. Not for phoning or anything else, I used this just to see if it works. Still does though I would not recommend...

But really in rare cases it might still work on today's phones, though not recommended because it never has been updated since the project was abandoned by the dev for more than 2years ago, so you might have security breach?

Use magisk as you can read above, it works great.
[SuperSU] zputnyq:
Hi,

I use SBIN mode SuperSU 2.82 SR5 with systemless busybox.

Recently I made a simple su.d script to change swappiness "echo 50 > /proc/sys/vm/swappiness" , but it never executed.

I have tried all possible headers from #!/su/bin/sush , #!/sbin/sush to #!/system/bin/sh, tried some permission also 700 & 755, owner & group set to root, change file extension to sh and following Chainfire's script format by giving ()& still give no luck.

However, adaway systemless hosts script is able to execute.

Is there something wrong ?

Does the SR5's su.d for bindmount only ?

Xperia M4 stock rom & kernel 6.0.1
[SuperSU] dahawthorne:
I'm going to risk being flamed by asking why people are still using SuperSU given that it's now approaching two years (1st October 2017) since its last update, and therefore two generations of Android with all its new underlying features.

I appreciate that it's bad form to mention another app in a specific thread, but do people not realise that Magisk is being actively maintained and regularly updated and (importantly) is every bit as simple as SuperSU to install with a simple flash?
[SuperSU] cnjax:
The main reason is a lot of people are using older phones and Android os versions that magisk doesn't support and prefer the supersu interface
[SuperSU] DB126:
Because it works with zero (none, nada, zip) side effects on the target platforms which are typically Android 7.x based or below. Flash and forget. I prefer to use my gizmos vs manage them. Newer stuff gets the Magisk treatment ... if I bother to root at all.
[SuperSU] palmbeach05:
I have a Moto Atrix 4G, a phone originally from 2011. Its running kitkat (4.4.4). I have magisk installed and its providing me with su support. That feature works all the way back to there. Also, topjohnwu clearly states "Magisk is a suite of open source tools for customizing Android, supporting devices higher than Android 4.2 (API 17). " https://github.com/topjohnwu/Magisk/blob/master/README.MD

Further, check the chart (info comes from google even if its on wiki) before you claim what you just claimed. Most peope are 4.2 or higher.

https://en.m.wikipedia.org/wiki/Android_version_history
[SuperSU] guest4711:
There are good phones in the real world which are able to run even Android Pie but are not able to use Magisk. E. g. the i9100 (Sammy S ii) is well maintained - I'm running LOS 16 on it- but needs an old kernel (which does not support Namespace) and has a non standard boot image Magisk can not patch...
[SuperSU] GopalKaul:
Sure? That's not true exactly, it just means the devs are using a hacky implementation rather than using the correct and latest standards.
[SuperSU] guest4711:
No, the blobs needed for the proprietary hardware require the use of old kernel support. You may call it "hacky" but a lot of proprietary drivers have neither open sources nor a reliable documentation - they work with kernels 3.x (x<=2) but not with newer ones. Not the devs are to blame, to blame are the manufacturers and people making money with closed sources.
[SuperSU] palmbeach05:
I'm wondering if the main su files from magisk can be used on one of these devices without actually having magisk. From the sounds of what you describe, the device you have is similar to the moto droid x and moto defy when it comes to flashing a rom. Is a bootstrap involved?
[SuperSU] AndDiSa:
... but you can always backport namespace support to 3.x (which isn't even too difficult) and then Magisk supports even suhide.
[SuperSU] guest4711:
See the discussion at https://xdaforums.com/galaxy-s2/development-derivatives/pie-i9100-t3850588/post79894994 e.g. It's not an easy way to go...

And AFAIK on i9100 recovery and ROM share the same kernel - so replacing the kernel could also make the recovery useless (hardbrick your device).
[SuperSU] AndDiSa:
Especially for the s2 there are already kernels out which have namespace support enabled (I know as I had a look at those when I ported it to the 3.1.10 kernel for the Nexus 7). If I remember correctly [MENTION=799465]bauner[/MENTION] did it in his kernel.
[SuperSU] janii:
To me supersu is a spot on clear and real root solution.

Magisk has been more of a limited root for me so far. Stuff has to be compatible with magisk, sort of. Most apps I used werent compatible so they couldnt find root.

I mean it started with installing simple root deleter. These dont work because they dont have real access to the phone.

Also installing stuff like viper4android has been way harder. In my case, it doesnt work at all compared to supersu & xposed.
[SuperSU] ashyx:
What you're stating there is simply apps that do not follow proper root protocol.

Even Supersu moved to systemless root, it had to. Many times Chain fire and topjonwu have warned the authors of these apps to keep up.

Any app that doesn't work with systemless root needs to be corrected by the author not the root solution.

Root needs to evolve with Android and apps need to evolve with root not the other way around.

Magisk has moved with the times and is far superior, it would be impossible for Supersu to work with the latest android releases.

Supersu did what it did successfully for years, but it is now well and truly a dead project.
[SuperSU] GopalKaul:
But it was the best while it lasted!
[SuperSU] DB126:
And still is (or can be) on older devices/ROMs. All things being equal my preference leans toward SuperSU on 7.1 and below; for everything else it's Magisk.
[SuperSU] GopalKaul:
I agree but k use magisk on all devices. I love the systemless modules!
[SuperSU] mrrocketdog:
was v.2.76 the last that chainfire built?
[SuperSU] palmbeach05:
No, 2.82 v5 was
[SuperSU] ashyx:
Certainly and in reality Magisk was borne from SuperSU. Without chainfires extensive documentation on root Magisk may not be what it is today.

I hope one day CF will rise again with more of his trail blazing apps.
[SuperSU] GopalKaul:
Love all his apps like live boot and flashify( or the app to flash OTA with root) and CF.lumen and others!

But I feel that it wasn't exactly born. It caused Magisk to start but topjohnwu faced issues as SuperSU was close souced and I heard CF didn't provide answers to his questions.

PS- I know he couldn't release source code as he was tied by a contract
[SuperSU] ashyx:
A few parts of Super su were used by Magisk initially, such as supolicy. This is where the disagreements came from.

Also not all was closed source, much was human readable. Mainly sukernel and supolicy were the closed source bits.

Also CF extensively documented his work for which even topjonwu acknowledges helped with creating Magisk root.

https://su.chainfire.eu/
[SuperSU] mrrocketdog:
ok , was 2.76 the last v. by chainfire 'alone'. without ccmt?