yashsingh1/xdaforums huggingface dataset:
[SuperSU] seven21075:
Hi,

ive just found out that SuperSu has a new owner. Now im looking for an older SuperSu.zip version.

Im using a Moto G4 Play XT1602 with Android 6.0.1. Wich version runs well? -and can you maybe post a link to download it?

I want to install it via TWRP.

Edit:

I found this

https://s3-us-west-2.amazonaws.com/supersu/download/zip/UPDATE-SuperSU-v2.76-20160630161323.zip

Is this safe and 100% from Chainfire?
[SuperSU] permutations:
What do you mean? Peek at what? Deposit what? I'll try anything at this point.

Yes, I was deleting the SuperSU folder from TWRP. I don't see it anywhere else. When I look at the folder from my PC, it's not there. Is that not the installation? How come it's invisible everywhere but TWRP?
[SuperSU] egingell:
It's inside TWRP. It has nothing to do with flashing SuperSU or any other zip.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] permutations:
I found unSU and read about it. What you say about it patching the ramdisk - i.e. only patching a version loaded in temporary memory and not the version in permanent storage - is clearly untrue based on what UnSU actually DOES.

I've also learned that this "systemless" approach is a nightmare that has meant the end of root access for many more people than just me. There are posts all over the internet from people who tried to install either Magisk or the systemless version of SuperSU and now can't root at all, no matter how often they try to undo, wipe, start again.

I'm against this systemless thing, very much against. It's too intrusive into the OS. The risk is too high for features I have no need for. I don't use Android Pay on my Nexus 10.

I'm betting I will have to completely wipe my device to get rid of this mess. Maybe as long as I'm at it, I'll try installing Android 6. And then I'll install SuperSU 2.65. I don't want to go near this systemless stuff. It's a mess.
[SuperSU] Ch3vr0n:
Too intrusive? Systemless doesn't intrude in system AT ALL! That's why it's called systemless. The previous method which used system was 'intrusive', why? Because it modified system, systemless doesn't. If a root app doesn't work with systemless then the app dev needs to update the app, not SuperSU.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] permutations:
Bottom line: I had root access through the "system" method for years - easily and with no aggravation. Now I have lost root and can't get it back. And I'm not alone. Google it. So on that basis alone, this "systemless" method is not superior.

My understanding is that "systemless" means that no files are written to the system folder. What the "systemless" method does instead is to patch the actual OS files, which is far more intrusive and risky - as evidenced by the many people who have now lost root completely. Want some links to other reports?

If my understanding of this is wrong and you can tell me clearly how to fix my "no root no matter what I do" problem, please do!

---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------

The "systemless" method hides itself by patching the OS itself. You can't get more intrusive than that. You also can't get riskier than that. I don't need my root access to be so well hidden. I have no problem with it being right out there in the system folder - safely.

---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------

If Chainfire REALLY wants to compete with Magisk, rather than copying him, he should make this systemless nightmare an OPTION at installation.
[SuperSU] KaMyKaSii:
http://xdaforums.com/showthread.php?t=1538053&p=66360462

If you want the SuperSU fully compiled by Chainfire, it's best to go to the SuperSU BETA thread

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post70213242
[SuperSU] egingell:
Who's copying whom?

Also, Magisk is not a superuser app.

Lastly, systemless *is* optional unless it's required by the phone/Android. You just have to set the variable in /data/.supersu.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] jcmm11:
You clearly have no concept of what a ramdisk is or does as opposed to a zimage (which is the actual kernel binary).

The method I gave you is pretty much guaranteed to get you back to a stable state without needing to wipe everything.

You can always force SuperSU to install in system mode, but that's not exactly non-intrusive either.

As for unSU you do realize that it's going through multiple gyrations to uninstall any possible version or flavor of su? It's not limited just to Chainfire's version. So don't assume everything in there is just for this particular flavor.

And now I'm done with this thread. Anymore uninformed ramblings somebody else can deal with.
[SuperSU] vampirefo:
[MENTION=999935]permutations[/MENTION]

Just use the system version rather than systemless version, there are two versions.

You are using a systemless version and complaining cause it's systemless.

Use the one below, and stay out of systemless version thread, you don't want this version to begin with.

http://xdaforums.com/showthread.php?p=64648982
[SuperSU] Ch3vr0n:
This isn't the 'systemless' thread either. This thread is about SuperSU, period. SuperSU as compiled supports BOTH. It depends on the ROM if it installs in system or systemless mode.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] culiacanazo:
Preferably, get yourself a boot.img, and recovery bound, take a look at any possible ".img" residue in >>> /data <<< such as supersu.img, xposed.img, magisk.img (something along those lines; haven't encountered that error in ages, but when I did, it did prevent booting up); afterwards, handle the usual (that's what worked for me when in similar symptoms)

---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------

Oh don't mind me, i was just stopping to say hi, I'm on my way.

(I started replying to the previous immediately but drafted it since i got busy over here, and just picked it up where i left it off, unaware of all the drama that had unfolded in the meantime)
[SuperSU] permutations:
Where is documentation for this? The last time I installed SuperSU, all that was involved was flashing it from TWRP. What variable? What is it set to?

Blah blah. Gee, I wonder why UnSU (and you?) say all the operating system files need to be replaced if nothing is touched. Maybe someone else will explain that to me since you're above it all.

I wouldn't still be here if it had worked.

We have different definitions of "intrusive". I don't care. I don't care about anything but getting root back by any means possible at this point.

I didn't know there were two versions.

I was just innocently using my Nexus 10. SuperSU asked me to perform an update. I did as instructed. And whammo - I was in a bootloop. I got out of that only to find that I'd lost root and couldn't get it back. I came and here and discovered this whole systemless thing. I don't keep close tabs on SuperSU development. I just enjoy the use of my device, and come here for help when something goes wrong. So shoot me.

Thank you. Though honestly, I don't care what version I install, as long as I can get root back. What do you think are my best odds with a Nexus 10 running 5.1.1 (or maybe 6.0, if I decide to try to finagle that onto it)? All I know is that I never had this problem until this brilliant "systemless" thing came on the scene, and I've been rooting my devices for a LONG time.
[SuperSU] egingell:
There are numerous posts in this thread and the beta thread, including ones by Chainfire himself, on how to force system/systemless.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Goliath27:
Is 2.79 ok for the HTC 10, or should I be installing one that has Force Encryption?
[SuperSU] Ibuprophen:
To be honest, that question should be posted somewhere within the HTC 10 portion of the XDA Forums. I believe that you will have a better chance for an answer specific to your device.

Please don't feel that I'm implying that your question doesn't matter here because it does matter.

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).

---------- Post added at 09:08 PM ---------- Previous post was at 08:55 PM ----------

This is a general statement of my opinion regarding many posts that I've seen...

I feel that there are too many postings in here that i would honestly categorize as either a "Lecturing", "Demeaning" and just plain "Rudeness" towards others. This type of feedback reflects on an individuals credibility and result in doubt as to someone's professionalism.

It really just looks to me that [MENTION=631273]Chainfire[/MENTION] sees this and i really don't want him discouraged in answering a question that can be supportive to myself and others.

I am not being specific to anyone but, can those who are doing this please stop with the "i know more than you" attitude.

Thank you all for your time and understanding with this.

Happy Holidays to Everyone!

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] culiacanazo:
That long?
[SuperSU] egingell:
Eh?

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] culiacanazo:
Sorry, i meant to quote what you quoted, namely this

"Where is documentation for this? The last time I installed SuperSU, all that was involved was flashing it from TWRP. What variable? What is it set to?"
[SuperSU] jcmm11:
The following is taken from the install script.

Just create the appropriate file eg. /data/.supersu

With the appropriate entries. eg.

SYSTEMLESS=false

# Overridable variables (shell, /system/.supersu, /cache/.supersu,

# /data/.supersu):

# SYSTEMLESS - Do a system-less install? (true/false, 6.0+ only)

# PATCHBOOTIMAGE - Automatically patch boot image? (true/false,

# SYSTEMLESS only)

# BOOTIMAGE - Boot image location (PATCHBOOTIMAGE only)

# STOCKBOOTIMAGE - Stock boot image location (PATCHBOOTIMAGE only)

# BINDSYSTEMXBIN - Poor man's overlay on /system/xbin (true/false,

# SYSTEMLESS only)

# PERMISSIVE - Set sepolicy to fake-permissive (true/false, PATCHBOOTIMAGE

# only)

# KEEPVERITY - Do not remove dm-verity (true/false, PATCHBOOTIMAGE only)

# KEEPFORCEENCRYPT - Do not replace forceencrypt with encryptable (true/

# false, PATCHBOOTIMAGE only)

# FRP - Place files in boot image that allow root to survive a factory

# reset (true/false, PATCHBOOTIMAGE only). Reverts to su binaries

# from the time the ZIP was originall flashed, updates are lost. # Shell overrides all, /data/.supersu overrides /cache/.supersu overrides

# /system/.supersu
[SuperSU] culiacanazo:
That's cool and all, but now YOU got the wrong guy ?
[SuperSU] mielletseed:
So things have changed over the years. Google included SE Linux into android an that's the main reason why the boot image has to be altered (to patch the policies to allow root). Chainfire decided that it's better to alter only one thing (the boot image) than two things (boot image and /system) that's why he created the systemless mode. Beside that systemless mode has advantaged for OTA aupdates. The system (only) mode was not longer possible due to changes of android itself so don't blame Chainfire for providing root access to so many devices for free just because you have a problem. Blame google or even better blame no one and find a better solution on your own ;)

seasonal greetings :)
[SuperSU] grep_i:
That's why you should read at least the OP and the changelogs and while your at it the rules of the forum.

Maybe that's too much for you but such are the rules in this forum and you accepted to follow them by creating an account in here.

In a shell in custom recovery or adb shell before flashing SuperSU do.

To enforce SYSTEMLESS:

echo "SYSTEMLESS=true" > /data/.supersu

Now flash SuperSU as usual.

To enforce SYSTEMMODE:

echo "SYSTEMLESS=false" > /data/.supersu

Now flash SuperSU as usual.

But in your case you would probably get stuck with older version, as for SYSTEMLESS it's there since SuperSU v2.56.

How long have you been out of the game ?

I don't know why you read it different than nothing in /system is touched and why your tone is somewhat condescended to someone who's trying to help you out with your problem.

With that kind of attitude it is almost impossible to learn anything as you overthrown everything as non important and you don't care about it.

Why your definition differs is probably because you did not follow forum rules and study and read up before asking questions.

I guess you will probably argue against that too although you agreed to do this things by creating an account on this forum.

Because you did not follow forum rules and study and read up before asking questions.

It is this way since v2.56.

How long have you been out of this game ?

I guess you will probably argue against that too although you agreed to do this things by creating an account on this forum.

You want it the easy way, we must study and do all the work for you and you only hold up your hand and slap us with it if we do not answer fast enough or not to your liking or understanding.

You only gave us a story of what happened but never some log files or maybe I missed that post where you posted your recovery log, if possible please upload your recovery log so we could take a look at that what happens during flashing supersu v2.79 on your device.

Again SYSTEMLESS is here since v2.56 is you ROM custom or stock ?

If there is a 6.0 ROM for your device I would definitely upgrade to it unless your in love with 5.1.1

After all it's your choice stay on old and deprecated and have problems you can't fix alone and probably not even with others as there are few with the same setup or stay updated and have a community at your side that can help you with any problem as it is quite possible that one of the members had it already and fixed it.

But that's my opinion.
[SuperSU] andrew2432:
[MENTION=999935]permutations[/MENTION]

In twrp terminal:

Echo systemless=false>>/data/.supersu

?

If not king root or towel root and have all your info sold to Chinese adverts
[SuperSU] Mesmurized:
Be aware: upper/lower case matters!

systemless is NOT equal to SYSTEMLESS
[SuperSU] pkelly517:
Not to worry.

Echo != echo.
[SuperSU] Urban-xxx:
Why is clean master not requesting root access with super su
[SuperSU] Strephon Alkhalikoi:
Because CleanMaster is a piece of crap software from a piece of crap company (Cheetah Mobile). In your position I'd find another app, but if you really want to use it, contact Cheetah Mobile and have them update it.
[SuperSU] Urban-xxx:
I use the app for auto start manager only and the app won't even request root permission. It's like the app is not aware my phone is rooted. I have contacted them like 3 time in 3months but got zero response.

I would love to know any other app that can totally kill some app from starting unless I launch them like clean master. Thanks.
[SuperSU] Strephon Alkhalikoi:
Of course the app isn't aware you're rooted. It probably uses hard-coded root paths like ES File Explorer and doesn't have the systemless paths in the app. If they're not interested in updating the app, change apps.

As to apps that can prevent an app from starting, there are a ton of them in the Play Store. BootManager is one, and while it can work with Xposed, doesn't need it.
[SuperSU] Urban-xxx:
tHanks a bunch
[SuperSU] Mesmurized:
Thanks. Boot manager requires Xposed. I'd rather not install just for this app. The others have not been updated since 2014/2015.

Can you suggest a native app for N? (I really miss App Ops :) )
[SuperSU] Strephon Alkhalikoi:
Greenify is about the only other app I know of, but I'm out of my depth. I don't use such apps.
[SuperSU] KOLIOSIS:
SD MAID PRO has the option,among others.

It's not reliant on Xposed & available in the Google Play Store.

There's a thread here in XDA dedicated to the app.

if you have any questions regarding the use of the app,the developer maintains the thread & app on a constant basis.
[SuperSU] Strephon Alkhalikoi:
That's ironic. I use SD Maid Pro for its cleaning features. I don't use it for the startup feature.
[SuperSU] egingell:
There's also ROM Toolbox for disabling startup apps.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] doppelhelix:
Clean master is as useful as one of those flashlight apps. To control the autostart, go to Settings>Memory>Apps started on boot.
[SuperSU] jcmm11:
I don't see that option there
[SuperSU] doppelhelix:
Oh. I'm sorry. Maybe it's a cm feature.
[SuperSU] culiacanazo:
I can't believe someone with root will be needing those "cleaners" and "boosters"... (Not that it's difficult nowadays to acquire root with most "unupgraded" devices.... - love making up speech as-I-go!!)... But the fact that he is in here actually asking in a non-noob way is what caught my attention...

Hey, nothing wrong with the likes of SD Maid and such (where it doesn't "suggest" what to look for, but you actually feed the target folders to it)... But Clean Master? Cheetah should be enough indicative to get away from it faster than a cheetah!
[SuperSU] culiacanazo:
Must be, my eyes popped out when i saw his screenshots!
[SuperSU] oldslowdiver:
My apologies if this is not that related, but, Whatsapp just asked to be granted root permissions on SuperSu.. is it normal? This is the first time it asks for it. TY!
[SuperSU] chavocarlos:
I only see this issue in a phone with virus, it isn't normal.
[SuperSU] Einwod:
And what do you have to backup that statement? What virus? Why would whatsapp not ask for root permissions?
[SuperSU] culiacanazo:
?

Wtf!

I guess i should go to sleep already. I'm seeing things!

5am my side of the pond.

WhatsApp? Root? Really?
[SuperSU] chavocarlos:
WhatsApp don't need root permission, neither other chat app, the infected phone is from my work, it creates shortcuts itself, open webpages, ask root permissions for other fake apps, download apps automatically, cannot erase with factory reset, the virus is in its system, I have to flash clean firmware again to clean up.

If your whatsapp ask root permissions is a fake app
[SuperSU] egingell:
Why *would* it need root? Please elaborate.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] DodoGTA:
Because it's fake WhatsApp app
[SuperSU] egingell:
Clearly, you misread my intention. I'm aware of that, thanks.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] grep_i:
Sarcasm is difficult in written words only isn't it
[SuperSU] KaMyKaSii:
I was also stumped when I saw this post...

http://xdaforums.com/xposed/modules/mod-whatsapp-extensions-add-extra-t3452784/post70286371
[SuperSU] grep_i:
If you want the apps from auto starting at boot you can use something like assistant for Android from AA mobile, 3c toolbox from 3c or ROM toolbox from JRummy.

If you want that the app can not function you could freeze the app with something like root uninstaller.
[SuperSU] oldslowdiver:
How can be a fake Whatsapp if it's been downloaded directly from Google Play? TY.

OKAY, here's the culprit: http://xdaforums.com/xposed/modules/mod-whatsapp-extensions-add-extra-t3452784/post70289695
[SuperSU] culiacanazo:
Having a hard time taming WhatsApp as it is... ?

---------- Post added at 04:11 PM ---------- Previous post was at 04:08 PM ----------

Malicious apps can and do sometimes go through the store (albeit shortly) although i don't think that's the case here... Strange Xp module dragging the actual WA app into the fight
[SuperSU] :
Thread cleaned.

:good:
[SuperSU] Einwod:
http://xdaforums.com/xposed/modules/mod-whatsapp-extensions-add-extra-t3452784/page59
[SuperSU] egingell:
That's an Xposed module and it counts as extenuating circumstances and the user would knowingly install that.

Edit: At any rate, it still proves that WhatsApp isn't doing it.

Edit edit: P.S. My name is Eric and your email was completely blank; although, I appreciate the effort.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] keil.:
Hi

Have someone else issues with the Pin Code option ?

I enter the Pin, - confirm the Pin, - but nothing happens -> [ No Pin code configured ] ?

Testet with v2.79 and v2.79-SR1

Device : OnePlus 3 Firmware+Modem OpenBeta 10

ROM : Resurrection Remix N v5.8.0 [29/12]

TWRP : 3.0.2-1.28

Installed with TWRP : Rom - Gapps - SU
[SuperSU] jdegreef:
No problem here with 2.79-SR1.

Moto G 4G (xt1039/peregrine) RR 5.8.0 11/12

Why do I never have problem with Supersu :confused:
[SuperSU] seos83:
No issue here

Device : Xiaomi Redmi 3

ROM : Resurrection Remix N v5.8.0 Beta 3

TWRP : 3.0.2
[SuperSU] permutations:
Thanks - so very grateful for an informative and civil reply!!

I just finished putting a brand new battery into my Nexus 10, so it's like a new tablet. Woo hoo!! I bought the tablet the day it was released in November 2012, and the original battery was holding a charge for approximately 10 minutes, so this is a great relief.

I understand now why Chainfire made this change to SuperSU. I still don't understand why - if the systemless option was in the version I was running (2.65) - upgrading to 2.79 caused a bootloop and then an irreversible loss of root. But in any case, I've decided it is more fun to install Android 6.0 on my Nexus 10 than to continue to wrestle with this problem. I'm going with this implementation:

http://xdaforums.com/nexus-10/development/rom-marshmallow-nexus-10-t3222477

It's a userdebug image so in adb I have root. That's enough to put iOS emojis on my Nexus 10, which was all I wanted root for right now.

Maybe next week I'll want to do something I need real root for, but for now this is enough. And I'm curious about Android 6.

Thanks for your help and insights.
[SuperSU] ridobe:
Well, that's a new one, lol.
[SuperSU] arifincaesar:
it's not

u don't know my trouble bro..

if u have this phone u may also can't rooting this phone..
[SuperSU] permutations:
Yeah, well, unfortunately, I was wrong about that. I installed Android 6 on my Nexus 10 along with a new battery, but I don't have root access from ADB or anywhere else, so I'm back to the SuperSU problem.

I updated TWRP to the latest version. When I attempted to flash the SuperSU 2.79 zip, TWRP warned it might make my system unusable. Huh? Why?

So now SuperSU is no longer installed by flashing from within Recovery?

Generally when I ask a question here some snarky person says GO LOOK IT UP!!!! But I'd really be grateful if someone would give me a link to the documentation for installing SuperSU 2.79. Don't think I haven't looked - I have. There seems to be multiple versions of it in multiple places, and it would take me hours to figure out which source to believe. Could the nasty snarky people just ignore me and someone with grace please post some basic guidance and a link? I'd be very grateful. Thank you.
[SuperSU] permutations:
P.S. For the people here who have already called me a moron... In the last 24 hours, I have replaced the battery in my Nexus 10 (not consumer-replaceable), installed an OS that Google did not release for this device, and upgraded the custom recovery. I think that qualifies me as not-a-moron. See the photo in the previous message for proof.
[SuperSU] maximusmullivan:
Umm flash it in recovery
[SuperSU] permutations:
I started to do that, but I got a dire warning from TWRP that it may make my device unusable. Should I just ignore that? Why does it even say that?
[SuperSU] permutations:
Here's the warning I get from TWRP. Should I pull the trigger anyway? Why does it say it's incompatible? Maybe it's just surprised to see Android 6 on a Nexus 10? Does SuperSU work on Android 6?
[SuperSU] permutations:
I've been using the Nexus 10 for hours and the battery is still at 77%! Wow. It was going from 100% to 0 in 10 minutes before.
[SuperSU] maximusmullivan:
It's a Nexus device, swipe and you're set

---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------

Nothing to do with supersu...
[SuperSU] permutations:
Hooray, it worked!! I'm rooted!! I'm rooted on Android 6 with a new battery (which, yes, has nothing to do with SuperSU, but makes me very happy). Thank you for your help! :)

At one point I paid for SuperSU Pro, but it's not recognized. Maybe I fix that in the Play Store?