yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ibuprophen:
I had stated the following information on the SuperSU Stable thread and just wanted to pass this along here since it applies to this thread as well.

Regarding the apk (specifically) downloads that was within the AFH link I had previously provided on the following post within the SuperSU Stable thread...

https://xdaforums.com/showthread.php?p=76650463

... there's apk files that are labeled "Beta" and such (that Chainfire had only provided via the flashable zip) were the actual apk files that were located within those zip files and I had just labeled the apk's accordingly.

So all of the apk files for a version that was only available via the flashable zip files were extracted from those said files and just appropriately labeled/renamed accordingly.

Just an FYI... None of the downloads from the AFH link was modified at all and I had only provided the link for those who have been experiencing difficulties with the Chainfire download links (as an alternative).

I hope that I had explained this okay via text... :)

Enjoy! :thumbup:

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] jc1266:
Dear sir

Sorry for my bad English . After installing this magisk , how can update monthly update ?? Or installing monthly ota zip?? At the moment running stock rom 7.1.1 Nexus 6 . I would like flash to Oct 2017 security update. Can I use flashfire pls help

Thnk in advance.
[SuperSU] gothicVI:
Wrong thread.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[SuperSU] kurze12:
From time to time I lose root without having changed anything and have to flash supersu again. Why is that? (Nexus 5X, LineageOS 15.1, ElementalX-N5X-6.06 )
[SuperSU] cnjax:
I believe lineage uses its own root in its builds you should probably seek help in the lineage thread
[SuperSU] Ch3vr0n:
Only if you'll flash their su zip. LOS hasn't had built-in su since the start

Sent from my Nexus 6P with Tapatalk
[SuperSU] GopalKaul:
I think he means flash the SU add-on of LOs
[SuperSU] madbat99:
Probably an incompatibility with Oreo. SuperSU is not, and likely will not be, updated for complete Oreo compatibility across all devices and ROMs. As stated above, use lineage su add-on.
[SuperSU] kurze12:
For LinageOS Root, I do not like the root icon in the bar. Supersu, works fine on my Pixel C with LineageOS without problems, only with the Nexus 5X I lose about once a week root. I then flashing supersu new.
[SuperSU] madbat99:
You can turn off that root icon in the status bar settings.
[SuperSU] kurze12:
The symbol root there unfortunately not listed.

Edit: App SystemUI Tuner (I removed it)
[SuperSU] zrx8:
thanks, but nothing changed, SR5 does the same :(
[SuperSU] DB126:
There are root remnants somewhere. If unsu script didn't resolve the issue you'll likely need to wipe and reload stock or some other ROM (easier than digging for root cause). Probably not worth the effort given device vintage.
[SuperSU] Ibuprophen:
Personally, I haven't seen anything in a while regarding the question of removing the Root Hashtag (#) indicator from the status bar.

I know that I've seen a few threads regarding this as a specific development with this feature and/or within another type of development with some type of reference to removing/clearing this.

Off the top of my head, i do know that members have mentioned success with removing/clearing the Root Hashtag (#) using the following development.

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

The Developer had posted this within a dedicated device specific area of the forum but, the topic does state for All Android Devices.

I'll try to do a little digging around regarding this and this specific indicator has a few variations to it's name/reference for it.

Hopefully, the above is helpful in some way... :)

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] sam 4x:
Ive been using root for all eternity and never faced any issues. But with new discoveries are new potentials and one such is the Uber app. Surprisingly Ive been running it on the Havoc ROM for more than a month but after the latest update its not letting me log in and keeps spinning in circles if i try to log in. Research and suggestions led me to Magisk, i dont know if it will deliver or not but I gotta try all my options. SO, can anyone please tell me how to unroot from Super SU ?
[SuperSU] cnjax:
Search for unsu zip
[SuperSU] ktmom:
The easiest way to unroot is to dirty flash your ROM. I guess I would use the unroot feature in the SuperSU app then dirty flash.

You could also try the suhide zip that can be found in this thread.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] :
Thread cleaned.

Get back on topic please.

:good:
[SuperSU] osm0sis:
Can anybody confirm if there are any A/B slot devices that the final SuperSU build still works on, or were they all broken by subsequent OTAs?
[SuperSU] Ibuprophen:
From what I, personally, can tell, I believe that the latter of your question applies but, i can't state this with a 100% certainty.

It's probably more of a hit and miss without a real pattern of certainty.

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] GuardianUSMC:
I had no problem on my device where I have SuperSU and SuHide installed and was working just fine and a couple of Google App updates ago, the GUI just disappeared, the icon and everything disappeared. Now here is the bizarre part. Under Apps it shows both installed, but you can't run them even using commandline. Rootchecker says everything is rooted and passes safety net and root apps who already have permission work fine, but nothing new works because no GUI, and when I dumped the packages list, it shows up nowhere, dump it with the -u option and voila it shows there. This suggests the package is uninstalled, but here the thing, it isn't, still shows up under installed apps on the device and the device is rooted, just the GUI for both has completely disappeared. I have been totally scratching my head trying to figure this out. It seems the last build is very unstable with the newer images, before the last "OTA" if you will, which I don't install that way, I flash like I always do and applied the root like before just fine, but later it breaks very easily, on another device, I was never ever able to get it to show up despite the device showing as rooted.
[SuperSU] corkiejp:
[MENTION=1650358]GuardianUSMC[/MENTION] Did you hide the supersu and suhide with volume trick?

Repeat that again and they might show up?

https://xdaforums.com/apps/supersu/suhide-lite-t3653855/post73404014#post73404014

If not try installing the supersu app from inside common folder of the zip.

Can not believe, i'm actually posting in this thread. It should be dead by now. :(
[SuperSU] osm0sis:
Hey, congrats on the RC! :)
[SuperSU] Ibuprophen:
Oh! Thank you very much! :)

View attachment 4564997

LMAO!

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] ashyx:
[MENTION=4828250]Ibuprophen[/MENTION] well done buddy. ;)
[SuperSU] GuardianUSMC:
No I did not, and I have tried it to see if it comes back, but nothing happens. Can you confirm for me that I am using the right combination? I can try again.

Looks like I did it correctly, and no it did not make a difference. Just to make sure, I do this while on the launcher right? Or anywhere? Making sure I am doing it right.

Tried that already, no luck. The install button is never active and if I try to force install using ADB it will install it but the interface still won't show up and the root disappears altogether.

Something is not right with it under the new conditions and I don't know what it is but it is making it effectively unusable.
[SuperSU] GuardianUSMC:
Just a little update to my issue of the GUI disappearing that I reported earlier, as if things couldn't possibly get weirder, this morning I had another Google App update and after applying that, lo and behold, both icons for SuperSU and SuHide reappeared on the launcher and the GUI were back, makes ZERO sense to me but given that a couple of Google App updates ago made them disappear, it feels fitting that another update brought it back, but I still can't figure out why and that headscratcher is driving me nuts. Anyway, just wanted to report that however it happened, it seems resolved for the moment. Thanks for everyone who tried to help.
[SuperSU] Ibuprophen:
I'm just curious as to the app that was updated...

Is this app tied to anything remotely close to your System and such (You don't have to state the specific app if you don't want to)?

This update may not be tied to anything but, maybe the app or even the installation of the app had kindled something.

This is a weird coincidence but, it's not the first time I've seen odd stuff happen and I'm sure that it will be the last. LMAO! :)

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] Chakib96:
Thank you so much finally I rooted my A8 2018 Samsung With Twrp really succsifull Thanks XDA and Chainfire youare the best
[SuperSU] GuardianUSMC:
As stated, the Google App

Oh I have nothing to hide, that's why I said it was the Google App in each of my posts. I don't know but I assume it does have system modification permissions so it probably is doing "something", just don't know what that would affect this. Unless something it is doing is triggering the hiding behavior somehow but then if that was the case, then the volume button shortcut should have brought it back, reasonably assuming that is.

I hear ya my friend, I have experienced all kinds, so I am with you on that but this was so bizarre that it just make me scratch my head in complete bafflement. I honestly thought that as Chain had said before, that maybe Google wised up and chose to not "allow" it anymore and started messing with it and that was as good an assumption as any but the fact that it came back, either they changed course, or they didn't intentionally do anything to begin with and as the saying goes "sh!t happens" (if you'll excuse me saying it).
[SuperSU] Ibuprophen:
I assure you that the Flashable Zip is all Chainfire...

He had to add CCMT to it only for "Legal" reasons because CCMT owned it at the time Chainfire had released the Flashable zip.

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[SuperSU] folusmile:
[MENTION=1143630]osmosis[/MENTION] with due respect I believe with your experience in android development u can continue with SuperSu. Jst a thought
[SuperSU] Badger50:
Just give him the money to buy the rights from CCMT.....and I'm sure he would! ??
[SuperSU] mrrocketdog:
[MENTION=4544860]osm0sis[/MENTION] if final was 2.82-SR5, just flashed to a Moto X4 with success.

err on the side of kindness
[SuperSU] folusmile:
In that case it apply to you also and everyone that benefited from SuperSu;)
[SuperSU] osm0sis:
Hmm, so that's one A/B device? :p
[SuperSU] mrrocketdog:
[MENTION=4544860]osm0sis[/MENTION] , i'm pretty sure. but double check me please. at least i had to flash twrp.img and twrp.zip to retain twrp. excuse my noobness please. [emoji3]

err on the side of kindness
[SuperSU] TonikJDK:
It is.

What version of Android are you running on it?
[SuperSU] mrrocketdog:
8.1.0

err on the side of kindness
[SuperSU] xell75:
Seems like that error only relates to newer devices, older phones like Galaxy S4 with Android 8.1.0 custom Rom LineageOS 15.1 and newest Security Patch from August, SuperSU flashes just fine and works without any problems.
[SuperSU] Arsinn:
Hi. I would like to root my htc10 oreo (8.0.0) please guide me which supe su version is suitable for me
[SuperSU] Ibuprophen:
Try looking at the following thread that's specific to your device.

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

This type of "Device Specific" question is more likely answered by someone who has this specific device. Especially with the (apparent) discontinued development of the SuperSU.

SuperSU wasn't really developed to cater to a "which version is for which device" but, was Originally meant to be more of a universal use. Originally...

When developing stopped, this affected devices with Android Oreo and above with more devices unable to use SuperSU as the Android technology progresses.

Questions like this becomes harder to answer within the SuperSU threads and more of a device specific question for the hopes that a member with the same device had figured it out with a guide and such.

I hope I had explained this okay via text... :)

Good Luck!

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[SuperSU] corkiejp:
SuperSU has been removed from the Play Store!

:(
[SuperSU] Spaceboy60:
Flashed on my lg g4 but supersu app doesn't show up on my ROM.
[SuperSU] sash11:
Extract Superuser.apk from the common folder and install manually.

Better yet - switch to Magisk)
[SuperSU] A.lemane:
Not everything out there is Magisk compatible
[SuperSU] habylab:
Majority of apps are. If you're experiencing an issue with an app or something else, contact the developer. Any issues I had >1 year ago and decent dev easily updated the app. Haven't had issues for a while now.
[SuperSU] DB126:
Much prefer the maturity of SuperSU 2.82 SR5 to the ever evolving and occasionally unstable Magisk for simple root management. Those who need more capability and/or find the terminal releases of SuperSU incompatible with newer ROMs are better off with Magisk which remains in active development.
[SuperSU] ldeveraux:
You mean the recently undeveloped and mostly abandoned SuperSU? The one whose app isn't on the Play Store anymore?
[SuperSU] habylab:
Let's not go off topic and aggressive here. They're both valuable and should be respected. Let's hope Super SU stays alive somehow, competition is always good.
[SuperSU] TonikJDK:
The pro version of SU is still in the play store.
[SuperSU] mielletseed:
It's not the "pro version", it's only the key to enable pro features in an existing installation ...
[SuperSU] DB126:
Yep - that's the one for the reasons previously outlined. Don't need Play Store visibility nor flavor of the day updates if they do not satisfy a need. Ignorance is such a wonderful thing. Yum.
[SuperSU] Thapalil:
I need supersu for moto g4 plus and when i click on the above link it says the page is not working.

Can anybody help me to root moto g4 plus android 7
[SuperSU] jcmm11:
Thanks to [MENTION=4828250]Ibuprophen[/MENTION] you can find all the releases

https://androidfilehost.com/?w=files&flid=149034

Look in the zip files folder for 2.82-sr5
[SuperSU] DB126:
Best path is to consult your device forum for recommended tools and techniques. SuperSU is likely not the right answer for your device.

https://xdaforums.com/moto-g4-plus
[SuperSU] Austcool:
[MENTION=631273]Chainfire[/MENTION] I've desperately tried to get supersu to work on the SM-T380 Galaxy Tab A (2017) but it doesn't work... I've even tried cf-auto root but that also fails. My old Galaxy Tab A SM-T350 worked with it. But my new Samsung isn't supported It's current efused firmware is Android 8.1.0
[SuperSU] Ch3vr0n:
What do you expect him to help you with. He's no longer involved with SuperSU since CCMT bought it and killed it by not giving it any update since then

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] andreoide:
I don't get it either. SU is abandoned for such a long time and not updated either that I do not consider it a safe way to root any more too.

Why people cling to this piece of history puzzles me
[SuperSU] Austcool:
Magisk isn't working properly for me either so
[SuperSU] Ch3vr0n:
That may be the case, but at least magisk gets constant development, so whatever your problem is with it, post there's so it at least can get fixed. It has a chance at least with magisk, with SuperSU that chance is 0.0%

It's up to you.

Verstuurd vanaf mijn Nexus 6P met Tapatalk

---------- Post added at 06:51 PM ---------- Previous post was at 06:49 PM ----------

For my 6p it still works. But I have to move ROM since it no longer gets security updates. Now I already have the ROM scouted, and if SU works with it I'll still use it, if it doesn't, only then I'll move to magisk.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] xell75:
Maybe cause it's a piece of good history? Magisk came out of nowhere and is now the only option to root (Nothing there to choose from anymore) and honestly it was never stable for me, cause of that I leave my new device unrooted since I use it.
[SuperSU] DB126:
Because it works (and works well) on most devices rocking Android 7.x and below. I use both tools and prefer SuperSU when the option exists no other considerations drive the decision. There are no safety concerns associated with using SuperSU (beyond those associated with root in general) provided the source is genuine which applies to any app/utility.
[SuperSU] ashyx:
It wouldn't make any difference whether you used supersu, magisk or any other root method you would still have issues.

It's not root that is causing your issues, it's Samsungs root restrictions, in particular the new Defex security. This is what is blocking your root apps.

This can only currently be bypassed by disabling it.

Magisk has the Defex hex patch, but Samsung have cobbled this also lately, so for your device it has to be done at a kernel source level.
[SuperSU] Austcool:
[MENTION=4899305]ashyx[/MENTION] you mind telling me how to properly patch defex?

I mean I figured out how to make selinux optional but the defex thing would be nice to know how to do that myself
[SuperSU] ashyx:
What do you mean you figured out how to make selinux optional?

You built the kernel from source?
[SuperSU] Austcool:
Yes ever since the sm-t350 I've been requesting Samsung for soucecode and building kernels for Samsung tablets

---------- Post added 28th January 2019 at 12:01 AM ---------- Previous post was 27th January 2019 at 11:54 PM ----------

@ashyx shall we continue to talk about Samsung tablets under Galaxy Tab A kernels and development. Also if your willing and you have time a guide of how to build kernels for Samsung tablets would be very helpful to many of us including patching defex and selinux. It's not just me that would appreciate it there are many people that are in my discord servers that want help building kernels with less Samsung security so that we can fully enjoy root
[SuperSU] ashyx:
If that's the case then it's teaching granny to suck eggs.

If you can already build the kernel from source, then you're already there.

Defex can be disabled in the defconfig.

Tbh I don't have time (nor the inclination) to make such guides.

It's not a one stop shop and requires more than a basic knowledge to build successfully.
[SuperSU] Austcool:
[MENTION=4899305]ashyx[/MENTION] at the very least give me the defconfig flag for me to try please
[SuperSU] ashyx:
It's under security in the config. Just disable it.
[SuperSU] Austcool:
Thanks will try it and share it
[SuperSU] matz_92:
Hi [MENTION=631273]Chainfire[/MENTION],

I'm disperatly trying to get root access on my board. I'm working on a single board i.MX7D with Android Things 1.0.8.

There are not custom recovery for this system, thus I have tried to install necessary files following the system-less install as described in your update-binary script (SR5-SuperSU-v2.82). This is my script:

#!/bin/bash

adb root
adb remount

adb push common/Superuser.apk data/SuperSU.apk
adb shell "chmod 0644 data/SuperSU.apk"
adb shell "chcon u:object_r:system_file:s0 data/SuperSU.apk"

adb push common/Superuser.apk cache/SuperSU.apk
adb shell "chmod 0644 cache/SuperSU.apk"
adb shell "chcon u:object_r:system_file:s0 cache/SuperSU.apk"

adb shell "mkdir data/adb/su"
adb shell "mkdir data/adb/su/bin"
adb shell "mkdir data/adb/su/lib"

#adb push armv7/su data/adb/su/bin/su
adb shell "cp system/xbin/su data/adb/su/bin/su"
adb shell "chmod 0755 data/adb/su/bin/su"
adb shell "chcon u:object_r:system_file:s0 data/adb/su/bin/su"

#adb push armv7/su data/adb/su/bin/daemonsu
adb shell "cp system/xbin/su data/adb/su/bin/daemonsu"
adb shell "chmod 0755 data/adb/su/bin/daemonsu"
adb shell "chcon u:object_r:system_file:s0 data/adb/su/bin/daemonsu"

adb push armv7/supolicy data/adb/su/bin/supolicy_wrapped
adb shell "chmod 0755 data/adb/su/bin/supolicy_wrapped"
adb shell "chcon u:object_r:system_file:s0 data/adb/su/bin/supolicy_wrapped"

adb shell "ln -s /data/adb/su/bin/su /data/adb/su/bin/supolicy"
adb shell "chmod 0755 /data/adb/su/bin/supolicy"
adb shell "chcon u:object_r:system_file:s0 /data/adb/su/bin/supolicy"

adb push armv7/libsupol.so data/adb/su/lib/libsupol.so
adb shell "chmod 0644 data/adb/su/lib/libsupol.so"
adb shell "chcon u:object_r:system_file:s0 data/adb/su/lib/libsupol.so"

adb push armv7/sukernel data/adb/su/bin/sukernel
adb shell "chmod 0755 data/adb/su/bin/sukernel"
adb shell "chcon u:object_r:system_file:s0 data/adb/su/bin/sukernel"

I don't know if it is correct, but I have made some changes compared to your original script. Seeing as the su binary already exists in my stock system (/system/xbin/su), I copy its in:

data/adb/su/bin/su

data/adb/su/bin/daemonsu

I have doubts also about my interpretation about this line:

# 22+ /su/bin/su (symlink) *2 /su/bin/supolicy 0755 u:object_r:system_file:s0 required

and I "tanslate" it to this one:

adb shell "ln -s /data/adb/su/bin/su /data/adb/su/bin/supolicy"

When the script has finished, I unpacked boot.img and I pushed launch_daemonsu.sh into the boot image ramdisk (precisly in the sbin directory), next I repacked the new image and I flashed it into boot_a, boot_b partitions and reboot the system.

The system boots correctly but, It doesn't install SuperSU app, and launch_daemonsu.sh script doesn't create data/adb/su/bin/sush and data/adb/su/bin/app_process , namely nothing happens!! :crying:

Could you tell me what i am wrong?

Thanks a lot.
[SuperSU] cnjax:
Chainfire sold supersu a long time ago and he no longer supports it. New owners have abandoned it
[SuperSU] matz_92:
Thanks for the tip.:good::good:

I hope there is someone that can suggest me how to reach this aim.
[SuperSU] cnjax:
You may want to look into magisk as it's actively being developed and supported
[SuperSU] matz_92:
Thank you, I think that I'll try with Magisk. :D
[SuperSU] Sagunflo:
how to install supersu on my j7 pro j730f with twrp recovery.
[SuperSU] Wolfcity:
As you have TWRP: Just flash it.

Use latest SuperSU 2.82SR5 (links inside this thread, use search function).

Be aware that SuperSU isn't supported anymore as the developer is retired and the new owner doesn't do anything. So this build is pretty old.
[SuperSU] Sagunflo:
Thank you mch
[SuperSU] Athif445:
Nice
[SuperSU] octavio095:
I am using Android pie, without any bug or problem, but when opening SuperSu it accuses me that I am without root. But I've already zipped the file via TWRP and yet SuperSu does not recognize root.

:confused:
[SuperSU] Ch3vr0n:
That's because SuperSU doesn't work with (all?) Android pie ROMs. CCMT bought it and subsequently abandoned any and all development on it. If you're on Pie, you'll have to use magisk.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] xell75:
On older devices with less security overall like an Galaxy S4 with Custom Rom Android 9 Pie, SuperSU still works perfectly.
[SuperSU] Ch3vr0n:
Precisely why i put the "all" between brackets ;). Doesn't work on my N6P with "Pixel Experience" either. Guess it's "too new".