yashsingh1/xdaforums huggingface dataset:
[SuperSU] iceman0826:
Apologies for that wording, it's just that SuperSU is synonymous to "Root" and I find others to be less optimized. In this case, what happens if the new Norm is Android P, will SuperSU work on it?
[SuperSU] osm0sis:
Like we said, Magisk is the sure way forward. With SuperSU development ostensibly abandoned, you'll just have to learn to accept Magisk as the new synonym for "root".
[SuperSU] GopalKaul:
But magisk has fingerprint to give root access
[SuperSU] ianmacd:
Yes, but that's a global option, not per app.
[SuperSU] osm0sis:
And it's only to initially grant root to an app in Magisk, then it's granted forever. In SuperSU Pro you can go in and set an app so that every time it requests root it only has root access when the correct PIN is entered (and for a given period of time), in effect locking that app. Then the SuperSU app itself could also be locked via PIN to make sure nobody could go in and change that. Super useful.

I'd love it if Magisk could add something similar to lock both Magisk Manager and root requests per-app using fingerprint. I've pitched it to [MENTION=4470081]topjohnwu[/MENTION] before but I don't think it caught his attention.
[SuperSU] ianmacd:
Magisk does have in its favour that it's GPLed code. Anyone with the requisite skills can add whichever features they want to the system and the app.

Most reassuring of all in the light of recent events is the guarantee given by Magisk's licence that, no matter what happens in the future, its survival and continued development isn't at the mercy of a single individual. No disrespect to Chainfire intended here — his software, his call — but rarely in the world of software is such an important and ubiquitous piece of code neutralised in the prime of its life. Thank goodness Magisk was as well developed as it was when this happened, and that we thus had an alternative to turn to.
[SuperSU] GopalKaul:
True. If SuperSU was open source, anyone with the skill could help us by giving updates.. but magisk is open source and so it is a worthy alternative truly
[SuperSU] yuri76:
But nobody is continuing with the project?

Inviato dal mio SM-G955F utilizzando Tapatalk
[SuperSU] FullWipe:
Supersu is not open source so nobody can continue development if chainfire will not publish the code.

You can use Magisk, really good open source alternative with interesting features.
[SuperSU] Didgeridoohan:
It's not [MENTION=631273]Chainfire[/MENTION]'s code to publish anymore...
[SuperSU] xell75:
Since my phone never see any update after 7.0 more, I stay at SuperSU, I tried Magisk and it was never stable for me. And the modules often causes a bootloop here. And since I don't care safetynet and just want stable root and easy modifications, I keep SuperSU and Xposed.
[SuperSU] yuri76:
Magisk keeps giving me bootloop

Inviato dal mio SM-G955F utilizzando Tapatalk
[SuperSU] FullWipe:
Never had any problem with Magisk and his modules.
[SuperSU] GopalKaul:
Magisk is infact pretty stable and magisk hide is much better that suhide
[SuperSU] yuri76:
Honestly, I did not understand what you wrote

Inviato dal mio SM-G955F utilizzando Tapatalk
[SuperSU] osm0sis:
Chainfire couldn't publish the code even if he wanted to since it's owned by CCMT now.

Then you should take a bit more time to read before you attempt to modify your device to avoid damaging your property.
[SuperSU] GopalKaul:
I'm saying that I don't know how people have problems with magisk. It is flash and go like SuperSU
[SuperSU] cnjax:
Go read the instructions in the Magisk thread
[SuperSU] yuri76:
My device is not damaged

Inviato dal mio SM-G955F utilizzando Tapatalk
[SuperSU] jcsww:
Personally, I prefer SuperSu and SuHide. They work even with the lack of development. I would rather not have my device rooted than be forced into using Magisk. Stealing code from ChainFire's hard work is not acceptable!
[SuperSU] GopalKaul:
Dude wrong quote

---------- Post added at 07:16 PM ---------- Previous post was at 07:14 PM ----------

[MENTION=4544860]osm0sis[/MENTION] could you tell me bout this incident? I still didn't get how [MENTION=4470081]topjohnwu[/MENTION] stole code from chain fire if the code is close-source?

---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------

[MENTION=4544860]osm0sis[/MENTION] could you tell me bout this incident? I still didn't get how [MENTION=4470081]topjohnwu[/MENTION] stole code from chain fire if the code is close-source?
[SuperSU] Ibuprophen:
Is it me??? :eek:

I can't believe what's happening on this thread... :confused:

When it comes to what [MENTION=4470081]topjohnwu[/MENTION] did or didn't do (I can't state for sure) but, this is between him and (formerly [MENTION=631273]Chainfire[/MENTION]) [MENTION=7678190]SuperSU Release[/MENTION] (aka CCMT).

My opinion is that topjohnwu has provided an alternative development that works for many individuals who may not be able to use SuperSU for one reason or another.

I may not use topjohnwu's or other Superuser developments but, i respect those other developers for their contributions to so many others.

1 last opinion... Just by stating that another development is better than this or any other one is a personal opinion and, just because it works for you, doesn't make it better. It just makes it a great development that works for you and any other developments that you don't use isn't any worse.

It would be great not to demean another development just because you don't like or can't use it. This reflects very poorly on you and an insult to Developers like my, [MENTION=4470081]topjohnwu[/MENTION], [MENTION=631273]Chainfire[/MENTION], [MENTION=1143630]osmosis[/MENTION] and many others.

I just think that this is a great development and, as the statement goes, "Survival of the Fittest". Thank you [MENTION=631273]Chainfire[/MENTION] for your great contributions and developments through the years. I have a feeling (and faith) that you shall return someday, in some way, and I hope you do!

Okay... Let's all please get back on track with the threads topic at hand... :thumbup:

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] osm0sis:
There was a Reddit thread with the whole story, and Chainfire took the time recently to reply to it. Might be our last big story time with Papa Chainfire (:()... I'll find it and link it...
[SuperSU] osm0sis:
Here we go. Read this and the linked Reddit thread containing John and Jorrit's stories (Jorrit responds throughout so make sure to expand to read all comments), then please never bring it up again. Nobody was totally in the right, nobody was totally in the wrong. There is no bad guy. Nobody is perfect. New developers learn as they go.

https://twitter.com/topjohnwu/status/993476247383560192?s=09

Live. Learn. Let it go.
[SuperSU] GopalKaul:
Thanks
[SuperSU] goister:
Hi,

I'm trying to install this on my rooted Nexus 5 with SuperSU 2.82. I have flashed TWRP recovery, and then successfully installed the SR5-SuperSU-v2.82-SR5-20171001224502.zip with TWRP. I then rebooted and checked the su binary. A "which su" still returned me "/su/bin/su", and a "su -h" returned "SuperSU v2.82 (ndk:armeabi-v7a) - Copyright (C) 2012-2017 - Chainfire & CCMT", which is the same as before.

How do I install SR5?
[SuperSU] DB126:
I get the same string. Navigate to the settings tab in SuperSU manager. Should see something similar to attached screen snip.
[SuperSU] goister:
Thanks! False alarm on my part!
[SuperSU] xell75:
And every Phone/Rom act different.
[SuperSU] FullWipe:
Surely, but those who have difficulty using Magisk, instead of complaining could release feedbacks to the dev by providing logs and useful informations to improve Magisk and increasing its compatibility with more Phone/Rom.
[SuperSU] ktmom:
And elsewhere than this thread [emoji16]

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] DB126:
...but the cat is such an attentive listener. :)
[SuperSU] PRL77:
I just hosed my device and need to flash stock. Which version can I use to ensure your boot-to-root will work?

https://developers.google.com/android/images#sailfish
[SuperSU] GuardianUSMC:
Some assistance please

I was hoping you guys can help me figure something out. I am at a complete loss and searching for it doesn't reveal a solution, although it could just be lost in the vast number of posts, in that case I apologies but I hope that you can lend me a hand.

I have two identical Nexus 6 (shamu) devices, they are configured nearly the same. I have always rooted them exactly the same way and one of them went off without a single hitch after the latest image that was released, working perfectly.

However, the other, followed the exact same process that I have been for years and it absolutely will not work properly. The SU installed in sbin mode. Will not show up, but using a root checker, it shows that it is NOT rooted but finds the SU in /sbin/ and if I try to "re-install" root again, the setup will state that it has already been patched. I have tried redoing the whole image again, and going through it again in full, still the same result. I for the life of me cannot understand why this is happening, it is completely outside the norm.

Anyone know what's going on? how to fix it? what I should do to resolve it? or what else you might need to help me with this? I would appreciate any assistance, as I am at a complete loss.
[SuperSU] GopalKaul:
Did you try dirty flashing your rom and then flashing SuperSU again?
[SuperSU] jcmm11:
In addition to dirty flashing the ROM I'd also flash osm0sis' unsu zip and then try again
[SuperSU] GuardianUSMC:
Yes, twice. That's when I get the, already patched message in SU installer and Root Checker says it is there (found) but not rooted.

Will give that a try, thank you. Now off to go find the link to the unsu :)

Thank you for the assist, will let you guys know what happens next.
[SuperSU] madbat99:
https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067
[SuperSU] GuardianUSMC:
Thank you, already found it and went through everything, I just came back to update everyone since there is still one bizarre thing I can't figure out. Maybe you can help me with that.

Went through the unsu, did the trick it seems since now after installing it again root checker shows rooted and everything seems fine except a new problem that I can't figure out.

The new problem is that while root checker says it is rooted, passes safety net and all is well in that regard like before. The SuperSU GUI is no where to be seen. It doesn't show up in the launcher like before. It doesn't show up under the apps like before. It doesn't even show up under the Suhide interface. The only thing I see now is the suhide and nothing else. On my other device it shows up just fine on the launcher, apps and suhide.

Can anyone tell me what's happening? How to get it to show the GUI? Why is it playing hide and seek to begin with? It is hard to manage the SuperSU without that. Thank you again for all the help getting me here and would appreciate help with that last hurdle. Thanks in advance.
[SuperSU] ktmom:
Some ROMs don't show the app in the app drawer but rather put it in settings.

In the SuperSu zip file, in the common folder is a copy of the apk. You could try installing that.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Lughnasadh:
Install the app manually. It can be found in the common folder of the SuperSu zip.

Edit: Ninja'd ?
[SuperSU] GuardianUSMC:
That's the odd part, I am using stock rom, it has never hidden it from me and on my other device it shows up just fine without doing anything extra.

I thought about that but wanted to know why before I did it, just to make sure it is not something more benign. I still don't get why it would not show up like it has over that last two years of flashing stock rom and rooting on this device without a single issue until this time. Even then it only happened on this one unit, which identical in configuration to the other one that I had no issue with.

:confused: still scratching my head why this one got so buggered this time.
[SuperSU] jcmm11:
Cosmic rays

Edit: (You really need to download the gif for the full effect, at least with XDA Labs)
[SuperSU] GuardianUSMC:
Cute, but unfortunately still a mystery. Call it a character flaw, if I don't know why something is behaving a certain way, it gnaws at me. 30 years in the industry, you'd think I would just be able to let it roll off me.
[SuperSU] madbat99:
Just a fluke. It happens sometimes and you have to install the apk manually. No biggie.
[SuperSU] GuardianUSMC:
You're right, thank you.
[SuperSU] Sara Cova:
can I modify my system after installing systemless root on GLX note5 marshmallow ?

as stock kernel doesn't allow system modifications ?
[SuperSU] jcmm11:
A stock, unrooted, system does not allow system modifications. By default the /system partition is mounted read only. Even if rooted the system has to be remounted as read-write if you want to modify system - although as soon as you mount it read-write you'll probably lose the ability to apply otas (and if you actually modify it you definitely will)
[SuperSU] alex00006:
hi guys

i have Note8 (N950F) and i want Root and i one quistion..

i read method Root for note8 ( Root with magisk and SU with TWRP )

i before only use SU_TWRP for all device ...

Are there any deep sleep problems after rout?

I recall it was a problem before...At that time I had the Note 5))))

What methods do friends now recommend to their servants according to their experience?

i mean magisk or SU ??

last quistion:

Will the battery be higher after rooting?

Thanks to all the friends
[SuperSU] DB126:
Sleep and battery endurance are unrelated to "root". Follow the guide(s) in your device forum. In the absence of meaningful selection/decision criteria there is no reason to vere off script and/or select one method over the other.
[SuperSU] ashyx:
Deep sleep bug was fixed in SuperSU ages ago.
[SuperSU] zrx8:
Hi, I cannot re-enable SuperSU once I unchecked the "enable superuser" option. Thereafter SuperSU says "binary occupied". Sony xperia e4g, stock Android 4.4.4, SuperSU 2.82 installed from TWRP.
[SuperSU] DB126:
Uninstall (using unsu script linked elsewhere in this thread), reboot, reinstall. Be sure to use SR5 build available here.
[SuperSU] GuardianUSMC:
Well, it seems like it is a bigger deal than it seems, wish it wasn't, but manually trying to install the APK does nothing.

Meaning, you run it, it shows up with the install window but while every part of that is clickable and can be interacted with, the install button is not one of them. Meaning, no matter how much you try to click on install, you can't. You can cancel out, but you can't move forward to install.

So what do we do with this little fluke now? Since clearly can't install the APK manually either, I cannot believe this is being such a pain this time around. :eek:
[SuperSU] Ch3vr0n:
Install it with ADB then. 'adb install <APK file name>'

Sent from my Nexus 7 with Tapatalk
[SuperSU] ktmom:
[MENTION=1650358]GuardianUSMC[/MENTION], what was said ^^ or, dirty flash the ROM (after removing the su keep alive script in /system/addon.d ) and start over.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Wolfcity:
I had this problem once, I just made a shortcut with nova launcher for activities, in the list you'll find superSU. The shortcut works exactly like the GUI.

I don't know if that works with other launchers.
[SuperSU] ashyx:
Why don't you just install it from play?
[SuperSU] madbat99:
Well, then you get the CCMT build and.... Some people just don't want that.
[SuperSU] GuardianUSMC:
To the best of my memory, that simply loads the install but you still have to complete it on screen, but I may be wrong, so I will definitely try that, thank you.

Interesting suggestion, thank you, I will try the above first and then if it persists, will give that a try, thank you for that.

Will keep that in the quiver but since I have the default launcher and not nova, not sure if/how that would work but thank you.

See what madbat99 said.

Exactly, thank you.
[SuperSU] GuardianUSMC:
REPORT

@Ch3vr0n, I was wrong, it doesn't show up the interface for the install. And it completed saying SUCCESS. However, my root is gone. I am no longer rooted, the app shows up under APPS but not on the launcher and suhide will simply say cannot acquire root and root checker goes back to showing root found but not rooted. It was rooted just before this, so this is just killing me. Now off to try the dirty flash @ktmom suggested :(

@ktmom, I am sorry if I am being a complete idiot here, and if so be kind and help me understand where I am going wrong. But there is no /system/addon.d on the device, and I thought maybe I was being dumb and you meant within the supersu.zip so I checked there to make sure, and nothing there either. Am I missing something? Should I still try to dirty flash, and by that I assume you mean the whole thing and not just boot.img right? (system, radio, bootloader, etc, whole kit and caboodle right?) and then go through the root again? (that part I want to make sure).
[SuperSU] GopalKaul:
Dude

First flash the unsu script by [MENTION=4544860]osm0sis[/MENTION] .

Then flash your rom dirty.

Then try the stable version 2.71.

Profit.
[SuperSU] GuardianUSMC:
I appreciate that, but dude, I have done all that, if it worked, then we wouldn't be having issues. This is not my first rodeo, it hasn't had issues in years, and even now on two identical devices, failed only on this one, the other one took me less than 5 minutes to update without issue, like a hundred times before. If it was this easy, which I wish with all my heart it was, it would be done already, it hasn't been the case.

One correction to add, I have not used the stable because I need to be sbin mode, and this has worked flawlessly until this particular instance. I can get the root with the unsu as the added step but the GUI will not show up, no matter what and if I force it through ADB it kills the root for some bizarre reason and I can't install it og either because the install button won't respond. But if you have something of a solution that none of has thought of already, by all means I would be immensely grateful for the assist.
[SuperSU] GopalKaul:
Um... Is your system partition full?
[SuperSU] Ch3vr0n:
All that command does is install the APK directly (as user app I think). That there's no gui is normal, that command bypasses that option. Though I can't see how it would possibly cause the device to be unrooted. All it does is install the app, nothing more.

Sent from my Nexus 6P with Tapatalk
[SuperSU] ktmom:
[MENTION=1650358]GuardianUSMC[/MENTION], you're on a stock ROM? It's system and boot that I would reflash. It's the boot.img specifically that systemless root modifies, but since you are having trouble with the APK install, I'd do system as well. I'd also wipe cache (not data).

On a stock ROM you don't need to worry about the survival scripts in addon.d, they don't exist and even if they did, the stock ROM flash process would not back them up prior to the flash.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] GopalKaul:
[MENTION=1650358]GuardianUSMC[/MENTION] are you on a custom kernel?
[SuperSU] ktmom:
BTW, [MENTION=1650358]GuardianUSMC[/MENTION], just in case, make sure to save the TWRP logs after flashing SuperSU but before rebooting. If the problem occurs again, you may get some insight as to what is happening.

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

Exactly, I know, that's what threw me for a loop.

Yes, I am. Got it, that's what I did. I have been re-flashing everything except userdata.img (I know a bit excessive but figure why not). I even clear the cache/dalvik on twrp afterwards as a matter of practice.

Got it, thank you, now I know.

No, stock.

I will go ahead and do that but watching it on the screen, there is absolutely no error or any complaints at all, or anything showing different than any other time, but I can share that, in case I am missing something somehow. The only time it says something different is if I try to reflash it over itself again and it says already patched, but otherwise nada.

PLAN: Going to give the adb install another shot, see if it messes with the root again. And then go through the process of unsu and reflash again to get the root back and then save the log and see if it gives any insight. I can't believe this device is making my life so difficult when it has never been such a pain before, ever.
[SuperSU] Didgeridoohan:
[MENTION=1650358]GuardianUSMC[/MENTION] Long-shot, but you're using suhide-lite as well, right? Have you checked if you've accidentally hidden the SuperSU GUI? It's a volume button combination, I believe. Can't remember what... It's in the suhide-lite thread somewhere.
[SuperSU] GuardianUSMC:
Well now that brings me a ray of hope, no I did not know that and while I don't see how I would have done that, by all means I am willing to consider it. If you know where, would appreciate the link but since you mentioned in the suhide thread I will begin digging for it, thank you.

UPDATE: Found it and did it, but all it did was hide and unhide suhide itself but not supersu.
[SuperSU] Locura18:
I was having the same issue with supersu not being found and root there. The same issue you described. It all started after I moved to unofficial Lineage 15.1 from Pblock.

What fixed it for me was what someone suggested in a previous post. I extracted the APK and installed it. I opened it right away and got it going. And then I restarted the phone and everything seems normal now
[SuperSU] GuardianUSMC:
I am on stock though, that's the kicker. But willing to try what you suggested, who knows it might still apply.

Forgive the ignorance, but I am not quite certain what you mean by extracted the APK and installed? You mean the APK from the zip file and then install manually? If so, that's already been done and each time it actually kills the root. Funny thing is that looking at the SU script, I see that it copies it to the base.apk and that is present, so it should be working fine. In fact, I compared this device to the other that had no issues, and all files, permissions and locations are the same, so that makes it even more frustrating. If that's not what you mean, can you elaborate please? Thanks.
[SuperSU] Locura18:
Yes. I extracted the APK from the zip file.

I had flashed the zip file. And I kept it there. It was showing root, but couldn't find the app anywhere. So I then extracted the APK and installed it. And things went back to normal after doing that.
[SuperSU] GuardianUSMC:
Ok, that's what I thought, no I have done that already to no avail.
[SuperSU] jazzruby:
Have you tried starting the UI with Activity Manager and then go to settings and set launcher icon?

Open a terminal and type:

am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity