yashsingh1/xdaforums huggingface dataset:
[SuperSU] ZRK_NanDRD:
I had issues when trying obtain systemless & here's the simple solution I did.

S3 I9300 + S5 G900F RR-6.0.1_r66 (5.7.4)

I used Philz Recovery 6.59.0 & reverted back to TWRP when done with the steps below.

-Flash SuperSU-v2.62-2.zip then reboot device

-Open SuperSU app & go to Settings

Tick •Enable su during boot•

Tick •Mount namespace separation• Reboot device

-Boot to recovery & flash SuperSU+Aroma+2.78-SR1+v3.zip by RatchetPanda over the SU-v2.62.2 while doing this you will be able to choose between 'Systemless' or 'System' root & 'Su-hide' or 'Su' then start & reboot device when done. That's it
[SuperSU] hshah:
I've managed to get as far as removing Xposed and installing SuperSU 2.78 SR1 as systemless. The phone boots fine at this stage, but as soon as I install suhide 0.53 the phone gets stuck trying to boot. It has been on the Samsung logo for about 30 minutes now (on my Note 7) :(
[SuperSU] -Happy Feet-:
Custom Kernel?
[SuperSU] hshah:
Yep, running Hydra ROM on the Note 7 with its kernel. I had a feeling it was that based on the stuff I had read but ideally needed someone to confirm.

I've heard that it could be the SELinux Permissive/Enforcing thing, so I am going to try and change that and see what happens :)
[SuperSU] -Happy Feet-:
For me it works only with advanced stock kernel. With custom kernel the phone won't start.
[SuperSU] Superfebs:
Hello, the installer can't find my boot image so it can't patch it.

I do have the boot.img file though and I can flash it otherwise. Can I patch it manually? How?

Many thanks!
[SuperSU] hshah:
If by "advanced stock" you mean the stock kernel tweaked to make it slightly better then that is what I am running. The developer (@Tkkg1994) currently doesn't have his phone due to the Samsung recall (Note 7) so hopefully when he does he can take a look at any issues :)
[SuperSU] yash92duster:
SuperSU v2.78 SR1 works great on my Samsung Galaxy A500G (INU) running MM 6.0.1 Custom OS

Thank you Chainfire:):good::good::victory:
[SuperSU] marchrius:
Is there a way to flash systemless supersu without tripping Knox and without a custom recovery? I was thinking about flashfire but afaik you need to fully unroot your device before doing systemless root and ofc flashfire requires root.. My phone is rooted with kingroot.
[SuperSU] ashyx:
You cant have system less root without tripping knox.

Systemless root requires the boot.img image to be patched.

This will trip knox.
[SuperSU] Murshad007:
Lols..

I just installed 2.26

Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted

using XDA mobile app
[SuperSU] tylerdurden83:
I have a question. Chainfire stated:

I have flashed the stock factory image wiping everything, then used CFAR to root with the first available SUPERSU for 5.0 version. After that I flashed Franco Kernel. Now, if I flash 2.27 from TWRP, am I properly testing the new 2.27 or not? I guess not...

Also, assume that I flash the stock kernel and system image now, then this root but also Franco, will I still not be properly testing this 2.27 because Franco has to revert the patched kernel changes in his kernel?

Cheers
[SuperSU] mbirth:
I think you don't need this anymore as CFAR is what's patching the SELinux mode. And the new version should work without that.
[SuperSU] Srandista:
You shouldn't use CFAR, neither franco kernel (which is already patched). Just install factory image, then TWRP and install SuperSU 2.27 from it.
[SuperSU] SamuriHL:
Nexus 6:

o) Restored boot img from factory img

o) Rebooted to verify supersu was indeed no longer finding su binary

o) Fastboot booted twrp

o) Sideloaded 2.2.7

I have root working. Thanks for this! Very impressive. I'll update my 4.4.4 S4 soon.
[SuperSU] heanseng:
I just flashed Lollipop into my Nexus 5 today. I was able to flash v2.27 through TWRP recovery and it works fine with the stock kernel.

Thanks.
[SuperSU] buffal0b1ll:
I got the toasts to come back when I disabled and re-enable SuperSu in SuperSu settings on Nexus 9 running Lollipopolooza;)
[SuperSU] the_house:
Nexus 5.

Background: CFAR never worked for me on Lollipop, whether from a cleanly-flashed factory image or from an OTA update of Kit Kat. I had to flash CF's modified kernel and then flash SuperSU from TWRP. Everything worked fine after that.

To test SuperSU v2.27, 1) I flashed back to the stock boot.img from the factory image, and then 2) flashed SuperSU v2.27 from TWRP. This worked without any problems (no bootloops or anything) and everything seems to be working fine.
[SuperSU] Travisdroidx2:
First gen N7 running stock lollipop. Once I updated binaries via TWRP it bootlooped. Restored back up but thought I would let you know.

Edit: was my fault. First time I used the apk and tried to update binaries with TWRP. Second time I just flashed the 2.27 zip and it went fine. Thanks again!
[SuperSU] rskyline:
I was rooted by CF AutoRoot on Nexus 4 Lollipop official. Then i flashed back system partition and boot from factory image, the flashed beta 2.27 only on recovery and now root seems to works very well!
[SuperSU] buffal0b1ll:
Disabling and enabling supersu in settings on 2.25 also allowed me to install Stericson busy box free and apply Adaway 2.9.2 on nexus 9 lollipopolooza
[SuperSU] virklov:
Flashed Bixie factory image Lollipop zip in Nexus 5 from TWRP no root. After BOOTLOADER - RECOVERY TWRP and flash SuperSu 2.27. Root ok. Perfect. Thanks [MENTION=631273]Chainfire[/MENTION]

Enviado desde mi Nexus 5 mediante Tapatalk
[SuperSU] xxRAMOTHxx:
Quick Post on 2.27.

Nexus 7 Wifi Edition (Grouper) -

Fastboot flashed Factory Lollipop images.

Fastboot flashed TWRP 2.8.1 recovery

Recovery flashed SuperSU 2.2.7

Reboot - SUCCESS!

Thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] Blac Caesar:
[MENTION=631273]Chainfire[/MENTION].. v2.27 working perfectly. Nexus 5, RastaPop 5.0.0_r7 AOSP build, Elemental X v2.03. All root apps working correctly, SuperSU Pro recognized
[SuperSU] pincher65:
nexus 4. I flashing 2.27 on a pure stock 5.0 - worked perfectly. thanks.
[SuperSU] *child:
Helium is working, but I'm getting a weird toast notification. Nexus 5 Android 5.0 LRX210. Versions 2.19, 2.25 and now 2.27 all showed this.
[SuperSU] jefferai:
v2.27 on SHIELD Tablet is working well -- flashed through CWM recovery. BBS, Wakelock Detector, and GSAM are all reporting success.

However, I do have the issue with SuperSU Pro not being recognized.
[SuperSU] vukis:
Thank you. CF-Auto-Root helped out. So now lollipop is so agresive, that you cannot root without patching kernel? Or I misunderstood something?

Is that kernel patch has done anything with setting SELinux mode permissive? I am using skvalex call recorder. It is noted in there that it will work if SELinux mode is set to permissive. After finally getting root I tested call recorder and it works! :)
[SuperSU] JulianJenner:
Works correctly with LGE-P760 Android 5.0 Lollipop ? by Artas182x. [MENTION=631273]Chainfire[/MENTION] you are great!
[SuperSU] Srandista:
Yeah, that was valid, when I was writing that post. In the mean time, Chainfire release SuperSU 2.27, which is working without patching a kernel.
[SuperSU] corsicanu:
If you want supersu without tripping knox, replace kingroot with su - system mode.

Follow this tutorial. It will work if you follow the instructions. Don't flash anything with FlashFire, just update SuperSU from playstore. Cheers!
[SuperSU] ashyx:
He specifically said systemless.
[SuperSU] marchrius:
Yes :) thanks anyway but I need systemless and suhide
[SuperSU] Ericarthurc:
Hey so I need help!! I have a nexus 6p and I am running Team OctOs android 7.0 rom and whenever I flash supersu it always installs as "system-less". I want my supersu to be in "system-mode". I have my reasons for wanting system mode, and for the life of me can't figure out how to install it in system mode or switch it over.

Thanks in advance!
[SuperSU] ashyx:
http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] photolarry:
Okay I am not a junior member

Let me first state that I am an advanced member and have a master's degree in comp sci. I have been rooting and modifying android phones since froyo on a crappy HTC device. So just to get that out of the way before people claim I am some moron.

Next, I currently own a Nexus 6 and finally have the Nougat build (released today actually) placed onto it. I have not rooted the phone for over a year now because I wanted Android Pay, badly. And I was willing to deal without having root (I basically settled for having a custom kernel and a custom hosts file that blocks all the flashing ads in my apps so that I could stop my epileptic fits LOL. ) Ok seriously tho, now that I am considering root again, because it does not need all the extra crap in order to fool Android Pay like XPosed etc which make the phone slow and suck. So yes I looked at the OP. And I looked at many many pages in this 740 page posting. It is tough to read ALL of that and glean much. So I am asking here, what are the simple steps to root and still have Android Pay / Safetynet work since the systemless method no longer works due to the ramdisk of the kernel? From what I have read so far....and I have tried....it seems this can be done pretty simply by :

Flashing SU-2.78SR1

Then SUhude 0.53

and then adding any apps that might independantly use Android Pay outside of Play Services (like a coffee shop app I have lets you load money by using APay and I assume I would need to add that to the blacklist)

If a kind person would simply tell me if I either have the steps wrong or it cannot be done at this time, I would be grateful.

I do not HAVE to do all this in order to keep using the phone (obviously). It would just be nice if I had root again so that I can easily use Titanium and backup app data and other things which I used to like to do.
[SuperSU] jesssiii:
Yes, I believe so. I've got the 6P and that works for me with Android Pay. I do add the terminal command within twrp to be safe. (after mounting system)

echo SYSTEMLESS=true>>/data/.supersu

Nexus 6P
[SuperSU] habylab:
This actually breaks SafetyNet for me. I flashed my Stock ROM, safety net passed of course, then I flashed the latest zip and SafetyNet gives a "CTS profile match: false" error.

Edit: I've been silly, ignore me. Still, something is breaking SafetyNet...
[SuperSU] JimSmith94:
I have paid for and used SuperSU for a long time, but strayed and tried Magisk and PHH Superuser for a while. Now that suhide and Nougat are out, I'm trying to come back, but get bootloops after installing SR1. This is on a Nexus 6 that I manually installed the OTA of Nougat on, and thankfully made a nandroid backup of before installing this.

The phone boots and runs fine until I try to flash SR1, so I think there must be some traces of the other root somewhere. Could someone please provide a list of what files need to be deleted and/or apps uninstalled to get my Nexus 6 to boot after installing SR1?
[SuperSU] RandomPooka:
Also running on a Nexus 6/Shamu, and trying to use this with the final N release that just dropped yesterday.

No matter what I've tried so far, 2.78 SR1 always installs in System mode.

I've tried installing it:

without the /data/.supersu file and the stock boot.img

with the /data/.suspersu file and the stock boot.img

without and with /data/.supersu with ElementalX 4.07

Obviously, this prevents suhide from being able to install, which is frustrating. I rather wanted to Catch 'Em All.

No luck on all counts. Anyone else have this problem and have a solutiong to get systemless working on Shamu with google official N image?
[SuperSU] RandomPooka:
On further inspection,, it doesn't even install system root or the apk. Perhaps I need to boot into the OS one time first before flashing supersu? Will try that tonight after work
[SuperSU] theisborg:
Detection and use of systemless root

I have an app that helps locate your lost android phone (https://www.androidlost.com) and for rooted phones I have a one click convert to system app feature.

Now some of my users complains and say it no longer works on devices that uses systemless root. So questions of the day are:

1. how do I detect if a user has systemless installed programmatically?

2. how do I use systemless? I guess it is not through the normal SU command

BR. Theis
[SuperSU] mitchdickson:
Does the app have the SU path hardcoded?
[SuperSU] theisborg:
No I just use su:

localProcess = Runtime.getRuntime().exec("su");

However I use three different techniques to detect if SU is present and they do not detect the systemless.
[SuperSU] Captain_Throwback:
1. Just look for the su binary in /system/bin & /system/xbin - if it's not found, but you can still call su, then root is systemelss ;)

2. Calling su is no different with systemless root.
[SuperSU] theisborg:
Well, that is exactly what I am trying to do: detect if su is available without calling it. That way I only show the su features for those who have access to it. Is there no way to detect if su is there without calling it?

Like a fixed path or something like this:

public boolean checkRootMethod2() {
try {
String[] paths = { "/system/app/Superuser.apk", "/sbin/su", "/system/bin/su", "/system/xbin/su", "/data/local/xbin/su", "/data/local/bin/su", "/system/sd/xbin/su",
"/system/bin/failsafe/su", "/data/local/su" };
for (String path : paths) {
if (new File(path).exists()) return true;
}
return false;
} catch (Exception e) {
}

return false;
}
[SuperSU] Captain_Throwback:
Probing a bunch of locations for the su binary is really not an efficient way to determine whether a device is rooted. The su binary can be in any number of places. See here for Chainfire's article on this. What's wrong with calling it?
[SuperSU] theisborg:
Thanks for the link. I'll have a look at it.

The reason why I do not call su:

If I call su there will pop up a page asking the user if he wants to grant su rights. And I think that is a bad user experience just to show a button. Only when the user clicks the "convert to system app" button should he be annoyed by pop up windows :)
[SuperSU] bezeek:
Users who are never prompted to grant permission and who later notice that you're bypassing security features of their device may not feel too warm and fuzzy when you try explaining that you simply didn't want to bother them. ;)
[SuperSU] theisborg:
I think you misunderstand. The user clicks my advanced menu. A lot of items appear. But I do not wish to show stuff that the user cannot do. Only if he has root access do I want to display these items to him.

_If_ the user has rooted his phone and clicks the "Create system app" then of course he will be prompted.

Anyway I found the solution to my question by calling "which su" and reading the result. That also works on android 7 where my users had the problem.
[SuperSU] bezeek:
Aha- I stand corrected. I presume you'll be pretty safe relying on `which` to be in users' PATHs, (and thanks for including the solution you chose! :good:)
[SuperSU] egingell:
'which' only works if busybox is installed.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] nicolap8:
Superuser doen't trigger the request if executed with -h or -v switch. Maybe also SuperSU...
[SuperSU] Sc4ryB3ar:
Does SuperSU have an EULA? If so, does someone have a link to it?
[SuperSU] corkiejp:
The new owners have released a Privacy Policy.
[SuperSU] Ch3vr0n:
An EULA isn't a privacy policy
[SuperSU] CronoTr:
Hi all,

Recently I've changed my Rom to a cm13 nightly version for my HTC m7. I've been trying to get SuperSU + suhide to work but SuperSU is not getting installed in systemless mode and suhide is reporting that xbin/su exists. I've gone to terminal in TWRP and did the echo command for systemless=true but that didn't work also. Can anyone tell me what I'm doing wrong?

Thank you
[SuperSU] EViollet:
In TWRP, manually delete the xbin/su file and try again.

It should work.

Alternatively, you can also flash the unsu zip file. I wanted to give you the link but I can't seem to find it again. :(

Regards
[SuperSU] CronoTr:
Thank you, I was able to manually delete those files, and install suhide, but I stil don't pass safetynet validation unfortunately.

Guess I'll have to recheck what I'm doing wrong.
[SuperSU] EViollet:
Yes, exactly.

Thanks.
[SuperSU] swallowingled:
Check the suhide thread, it seems that everyone is now failing as Google has apparently updated Safetynet again.
[SuperSU] luigidk:
That is the case.

The good news is it is very easy to remove suhide and unroot from within SuperSU. So to keep android pay, took 3 mins.
[SuperSU] CronoTr:
Ok I see. Then I can rest :fingers-crossed:
[SuperSU] Dalamar666:
I want to full unrot due to CTS verification fail... but in TWRP i can see that there is a folder (/supersu) that persists...

I unrooted with supersu apk, the phone reboots and now, if i reinstall supersu apk, it said that I haven't root

If I deleted the folder, the net reboot still here...

Any ideas? Thanks
[SuperSU] egingell:
Oy. That folder belongs to TWRP. It does not exist except when booted into recovery.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Dalamar666:
Thanks...

Any ideas about cts verification fails?
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=69008643&postcount=7430
[SuperSU] Bsanborn:
Just tried this /data in f2fs and /cache in ext4 and it didn't work. However, I do have /system in f2fs though as well. I'm assuming that's what is causing the issues?

Next time I switch ROMs (which will most likely require me to switch system back to ext4) I'll test again and report back.
[SuperSU] hatchet13rydin69:
Works great on SM-G360T with trap kernel and stock rom
[SuperSU] ameel:
Trying to figure out why SuperSu works VERY poorly on Zenfone 2 stock rom? Other people have flashed CM13 and can run suhide just fine on Zenfone 2. Can anyone please help?
[SuperSU] Sehwag:
Really nice app.

I loved it.

But earlier when i istaller super su v2.76. It says that update super su binary. But when Clicked on update then my phone it soft bricked..

I hardly managed to review my phone by flashing the complete rom again.

My device is Yu Yureka.
[SuperSU] cba1986:
little detail that i forgot to mention. i have all f2fs formatted.
[SuperSU] ericotena:
Supersu 2.78sr1 bootloops my honor 4x device. Any way to successfully flash this?
[SuperSU] Vishal Vignesh:
How many times did you let it loop?

Let it loop a few times....
[SuperSU] ericotena:
I had it booting for 30 mins but still no luck
[SuperSU] ashyx:
Do previous versions of supersu work?
[SuperSU] ericotena:
Yes but i was on system root before
[SuperSU] ashyx:
Did you make sure to remove system root first?
[SuperSU] Ja_som:
Solved

Sorry, I also ask in this thread, because I´m not sure what causing my issue, if my ROM or SuperSU...

So, I use AOSP Android 7 (http://xdaforums.com/nexus-7-2013/orig-development/p-aosp-n-7-0-google-shame-t3448008) on my Nexus 7 II and I use SuperSU v2.78 SR1, but I´m not sure if is systemless or not...

The "install to /system" option in SuperSU is gray and AdAway needs systemless zip file flashed to work, so it should be systemless, but I tried to use suhide and it asks me if I'm sure that SuperSu is installed as systemless because su file was found in /system/xbin/ folder. Also Secure Settings app works as on SuperSu system mode.

Thanks for any help...
[SuperSU] white7561:
Same as me
[SuperSU] ZRK_NanDRD:
Maybe this might help...

1.Flash Supersu v2.62-2 reboot.

2.Open Supersu go to settings &

-Tick •Enable su during boot•

-Untick •Mount namespace separation•

& reboot device.

{For the next step I used Philz Recovery bcos the latest TWRP can't flash this Aroma SU & then I reverted back to TWRP when done}

3.Boot to recovery & flash SuperSU+Aroma+2.78-SR1+v3.zip by RatchetPanda done.

I install Supersu 'systemless' but didn't install suhide, otherwise you can choose whether to install it or not, during the aroma install process.
[SuperSU] ericotena:
It is a new clean system
[SuperSU] Ja_som:
If you have same ROM as I, it is prerooted, for that reason suhide does not flash...

Here is solution for this:

http://xdaforums.com/showpost.php?p=69046655&postcount=1826
[SuperSU] dazzlerdevil:
hi, please help

After flashing this superuser '[BETA][2016.09.15] SuperSU v2.78 SR1' on android 7.0.0 (NBD90X, Oct 2016) on my nexus 6p i am getting an strange error, it is showing 'no sim card' and when i restored my nandroid backup eventually my sim was working fine just like before, so i gave this superuser another try and result were same it is not detecting my gsm sim card. please help ?
[SuperSU] Nowak4G:
Try flashing latest vendor
[SuperSU] dazzlerdevil:
Thanx for taking taking time to reply buddy, but i am already on latest vendor, as i installed this latest firmware through full flashing only.. any other way ?
[SuperSU] Derekjjm:
Has anyone managed to get the latest version working on a HTC one m9? I still get a bootloop with 2.78 SR1 and have to revert back to 2.65, with european 3.35.401.12-boot.img? Thanks for the help
[SuperSU] 912180343:
how to flash in systemless-mode and how to flash in system-mode?:confused:
[SuperSU] Ja_som:
Use the search function on this forum
[SuperSU] jesssiii:
Has always worked fine on my 6P, even on stock NBD90X. I'm using a stock-based NBD90X rom with SuperSU SR1 and Chainfire's 0.55 suhide ATM, no issues either. Not sure what's wrong for you, sorry. I'd say maybe your SIM card was failing, but if it works without SuperSU then that's likely not it.

Nexus 6P
[SuperSU] olivercervera:
Hi all, I have a strange problem.

I have been flashing some ROMs on my Nexus 5, and I discovered that i have a folder called /supersu in the root of my device that doesn't go away.

This folder has several files, like su, superuser.apk, install-superusu.apk and so on.

If I delete it, using TWRP file manager, it comes back after reboot.

There is also another folder that seems to be linked to this one but is empty: /root.

I also tried to flash the latest factory image, but the folder is still there. I also installed SuperSU 2.78 SR1 (systemless), and then remove root. unSU zip did not make any difference.

Still here. What can I do?
[SuperSU] Pkt_Lnt:
It is part of TWRP, so install stock recovery and it will go away. Of course then you can not flash anything but stock images.
[SuperSU] olivercervera:
I have been wasting two days to figure out how to remove that folder... my dear lord. Thanks

---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------

I just have found the answer in this post, but you deserve a thanks anyway. I'll go back to flashing. :p
[SuperSU] alexeei:
Have strange problem with CM13 rom on Note 4 and systemless root. I need to use custom kernel with it, and firstly i run supersu 2.78 sr1 installer from twrp, it works correctly, then if i reboot without flashing custom kernel, i have systemless root. But if i'm flash custom kernel after supersu and then reboot, i have custom kernel but without root %) As i understood, supersu patched boot image for root working and when i flash custom kernel it rewrite patched boot image with image from custom kernel and root gone. So, is it possible use custom kernel with systemless supersu?
[SuperSU] dtriguero:
Should work it has with my S4 flash custom kernel then supersu 2.78s1 then suhide0.55

Edit-I also have systemless xposed 86.2 installed and everything works great and all checks with safetynet helper

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] tejaskadaskar:
Hi guys, I flashed SR1 in Systemless mide using echo command.. If i flash a new rom and I wanna flash SR1 then do i have to use echo command again to flash in systemless mode or It will automatically get flashed in systemless mode?

Thank you.
[SuperSU] egingell:
If you wipe data (factory reset), then you will have to do it, again.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1