yashsingh1/xdaforums huggingface dataset:
[SuperSU] VivaErBetis:
My story. Today I've upgraded to lollipop a colleage's nexus 5, then I rooted it using CFAR and without rebooting I've installed SuperSU 2.25.

Everything goes OK but we noticed that "ES Explorer" root features doesn't works with SuperSU 2.25 while it works in my nexus 4 & 10 with SuperSU 2.20.

"ES Explorer" was updated yesterday to work in rooted lollipop but suddenly these changes, that works in SuperSU 2.20, doesn't work in 2.25...
[SuperSU] Ben36:
Flash the pie patch - https://app.box.com/s/y2yi8914ov3h2y3zgb57

Sent from my Android 5.0 Nexus 5
[SuperSU] ragz:
SuperSU v2.25 and v2.26 working perfect. Tw 4.4.2 (s5)

SM-G900W8, 0x1
[SuperSU] vukis:
Flashed all factory images of nexus 5 lollipop using googles *bat

Full first boot I restarted into bootloader, Booted up newest TWRP and flashed latest stable super su v2.16 and rebooted. When trying to run superSU app i got "there is no su binary installed"

Then I tried to flash v2.25 same way. But this time it is stuck in those 4 flying color circles state.

Flashed back system img and booted up.

This time I only tried to flash v2.25 with clearing caches. Same stuck in those 4 flying color circles state.

What is wrong with me? Hardest root in whole ~4years of android :)
[SuperSU] GtrCraft:
Use cf autoroot
[SuperSU] Long Island NOOBIE:
v2.25 working perfectly on my older Samsung devices running KitKat. As always, thank you for your valuable time and dedication!
[SuperSU] Srandista:
Do you encrypt your phone?

First run CF-Auto-Root: http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip

And then install newest SuperSU through TWRP: http://download.chainfire.eu/629/SuperSU/BETA-SuperSU-v2.26.zip
[SuperSU] vukis:
Nope. Or is it a default setting on lollipop?
[SuperSU] landstander:
[MENTION=631273]Chainfire[/MENTION] ADB sideload of 2.26 also worked fine. :)
[SuperSU] Srandista:
OK, I just wanted know, because bootloop is happening with SuperSU 2.25, when you have enabled encryption.

Please, proceed through my advices (CF-Auto-Root and SuperSU 2.26).
[SuperSU] tylerdurden83:
Is it safe to test 2.26 on non encrypted devices too?
[SuperSU] Srandista:
Yes, I'm testing it without any problem.
[SuperSU] duki994:
2.26 works good on LG G2
[SuperSU] Rinoceros:
V 2.26 confirmed working perfect on both HTC devices mentioned in my sig below :)
[SuperSU] swat4samp:
:cool:

https://twitter.com/ChainfireXDA/status/535253476021116928
[SuperSU] rrohanjs:
i have rooted via auto root and have the factory image .. but i have super su 2.20 .. so to update i should just flash the latest zip right ?
[SuperSU] swat4samp:
Just flash latest supersu zip
[SuperSU] Srandista:
Still works without any problem, like all SuperSU BETA releases since Lollipop release.

I'm running Nexus 5 with stock Android 5.0 and patched franco kernel r68. I will test it on my Nexus 7 with completely stock configuration later today.
[SuperSU] yash92duster:
Thanks a lot chainfire :svetius::)

SuperSU-v2.78-SR1 works flawlessly on my Galaxy S5 G900H Exynos Variant running S7edge Rom :)
[SuperSU] ech1:
Anyone got N5x rooted with NRD90S and fbe enabled?
[SuperSU] osm0sis:
I just tested it and [MENTION=4587767]egingell[/MENTION]'s idea totally works! Great little hack.

So for things that don't make sense (or are too complicated) to rewrite with &-loops, all you need to do is encapsulate your script inside:

# dirty hack to make this all run in an asynchronous subshell and not impede the boot with su.d
if true; then
<script>
fi&

And the script can remain self-contained. :good: :)
[SuperSU] _that:
Why not simply:

{
echo start;
sleep 5;
echo stop;
}&

?
[SuperSU] egingell:
If that works, then do it. :)

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] osm0sis:
​

Oh damn! Haha duh

Edit: Yup! Totally works. I always forget about creating a subshell that way outside of function making. :highfive:
[SuperSU] Alxoom33:
What's fbe?
[SuperSU] vt0r:
File-Backed Encryption or File-Based Encryption, depending on who you ask.

It just means each file is encrypted individually, rather than an entire volume/partition being encrypted at the block level.
[SuperSU] Alxoom33:
Thanks, it does not appear to be an option with my Pixel C or Nexus 6 at the moment. The Pixel C is out of the Beta version, NRD90R, while the N is still Dp5.
[SuperSU] blue4you:
Check version of supersu app. If it is still 2.78 without SR1, deactivate supersu app in settings menu and if you be ask, reset supersu to factory that uninstall any udates of supersu app.

On this way I get 2.78SR1 to work.
[SuperSU] ianmacd:
Actualy {} is precisely for command grouping in the current shell.

If you explicitly want a subshell, use (), so:

(
echo start;
sleep 5;
echo stop;
)

No need for an ampersand.
[SuperSU] Kamal363:
Im on SR1... in system/bin i change permission on su file to 4755... after reboot i get su binaries update... is this ok with the change permission i make...?

Thx...

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
Please help whenver i try to flash SuperSU 2.78 RS1 and open supersu app i get "There are no binaries installed" what to do? need help to be able to flash suhide afterwards. Thanks in advance
[SuperSU] tnpapadakos:
did you try going to the play store and installing "Busybox installer" from there?
[SuperSU] bon122728:
i don't have busybox. sorry i don't know but busybox has something to do with wha'ts happening?
[SuperSU] Kamal363:
Try go system/bin then change 'su' permission 4755.. reboot..

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
im on v2.76 again.. i do this after flashing v2.78RS1 or do it before flashing?
[SuperSU] Kamal363:
After

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
okay, I'll try thank you man :good:
[SuperSU] Kamal363:
Deleted..

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
the one you changed to 4755 from system/bin? you also copied and replaced the same su in system/xbin?
[SuperSU] Kamal363:
Dont... sorry

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
noob question, how do i change the permission to 4755?
[SuperSU] Kamal363:
Using file manager like foot explorer... go to #root-system/bin.. find 'su'... long prees file.. klik permission... change to '4755'.. ok.. then reboot... just follow tick in pic.

This what i get after doing this...

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] KabalLV:
I cant get SuperSU working on my CM13 . I need it for few apps because on CM13 root without supersu manager, my substratum doesn't work and clean master features too. I tried flashing 2.78 but in logcat it just says failure aborting at some point. I tried unrooting, then flashing root.boot zip for my Moto X 2014 XT1092 and the right after i flashed it, I flashed 2.78 supersu zip. No errors in logcat noticed. Tried booting and its bootloop. Found people with similar problem but found no solution. Any ideas ?
[SuperSU] bon122728:
omg why I don't have su on my syste,/bin? but in my system/xbin there is an su file. is this normal? im still on v2.76
[SuperSU] Kamal363:
Try change the permission..it just to get u binaries update...

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
okay, thank you for helping me, i'll try this methods. :highfive:

---------- Post added at 12:53 PM ---------- Previous post was at 12:31 PM ----------

I just did the flashing after i booted, i then go to system/bin and system/xbin i didn't find any su files? Omg why? :crying:
[SuperSU] Kamal363:
Plz check su installed or not...

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
`i flashed it, I then go to settings to check at my supersu then it says "there is no SU binary installed, and supersu cannot install it"
[SuperSU] Kamal363:
So its no binaries only right..?

But SuperSu is installed right...

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
ya i have su app in my settings
[SuperSU] Kamal363:
Check ur inbox... i had slow net..

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0

---------- Post added at 02:05 PM ---------- Previous post was at 01:09 PM ----------

Su folder location..

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] bon122728:
Weird thing is whenever i flash this my phone gets unrooted..tried it with two custom roms. I flashed then when i open supersu app it prompts "there is no SU binary installed". Then i go to my root folders and there were no su folder in /root and no su files in /system/bin and /system/xbin, so i cant try what Kamal363 suggested to try to cha[IMG="i got this after flashing rs1"]https://s15.postimg.io/jtp6t7m7t/Screenshot_20160918_224710.png[/IMG]nge the permission. So, there. Hope someon can help.
[SuperSU] zalcsooo:
After you flash SuperSU, FBE option disappears from developer settings, so sadly it's impossible to use it. Donno if [MENTION=631273]Chainfire[/MENTION] has any plan with this in the future or if it is even possible to make it compatible.
[SuperSU] Kamal363:
Try flash xXx rom... its preroot.. just choose setting with root etc.. read xXx OP... after flash and setting device flash supersu 2.78SR1... see if u get fc etc...

Need to sleep back... GL bro..

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] Kamal363:
[MENTION=631273]Chainfire[/MENTION]... su binaries should be auto install in system/bin..,system/xbin or both..?

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] osm0sis:
Weirdly enough, that doesn't work in my testing just now; if I use () it goes back to hanging the boot for the 60 second su.d timeout, but {}& does not.

Edit: Looks like (m)ksh doesn't support () to fork into subshells, so & is the way to go:

http://stackoverflow.com/a/15312007 :good:
[SuperSU] Chainfire:
Have not looked at it yet. The option didn't use to disappear though... weird.
[SuperSU] ianmacd:
Very interesting. I had no idea that Android used mksh, or that mksh has this behaviour. You learn something every day.

For what it's worth, this is at odds with POSIX (not that I expect anyone to care), which has this to say:

mksh evidently optimises subshells out of existence (at least some of the time).
[SuperSU] miloytyn:
The option is still there at least on my 6P.
[SuperSU] grep_i:
Security wise I would set the octal to 0755 you do not need the setuid, if you have poorly programmed apps on your device it could pose as a security thread when used with 4755.

Also in my opinion you should not manually fondle with file security, only if you are very experienced, these things spin out of control easily.

Also it might be possible he is systemless so check your files in /su/bin or /su/xbin
[SuperSU] mikeoswego:
I may be misunderstanding the conversation here.. I thought the point of what Chainfire said was that our script should go somewhere like /su/[x]bin and then we call it from a script in su.d putting it in the background there. I have 2 scripts that wait for boot completed, one being gappsintegrator.

I moved /su/su.d/000gappsintegrator to /su/bin/gappsintegrator then created a new file /su/su.d/000gappsintegrator with only the following content:

su/bin/sush /su/bin/gappsintegrator &

Then the actual script doesn't have to be coded around avoiding boot delay.
[SuperSU] Chainfire:
Either way works, it's up to the scripter :)

In the example case of LiveBoot I do it that way because the app can change it's own script without needing root.
[SuperSU] Dead-neM:
Yes after testing what people have said i keep my idea which is same of chainfire and yours, to launch script with an other.

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

I don't agree. With 2.78 sr1. It's the only way to have proper script execution.

Osmosis trick will loop the echo value for an infinite time.

Anyway doing it like LiveBoot does cause no problem.
[SuperSU] Mudvayne622:
How do I make sure SuperSu installs as systemless? Can't seem to find an answer anywhere.
[SuperSU] Wolfcity:
superSU does it by itself if it's possible. If yes it installs systemless if not it installs in system.
[SuperSU] Mudvayne622:
Ok I'll just have to flash and see what happens. How can I verify which installation it did? I'm running AICP MM on Nexus 6.
[SuperSU] Wolfcity:
Scroll down in superSU app settings to "install to system" after flashing.
[SuperSU] osm0sis:
Nah, we're way past my initial example now. Like [MENTION=631273]Chainfire[/MENTION] says, it's pretty much up to preference. Sometimes it might make more sense to rewrite a loop differently to make it work as a subshell, but [MENTION=4878287]_that[/MENTION] corrected us all with by far the easiest solution; basically wrap the entire script in a subshell with {}&. I prefer this way since everything stays self-contained.

[MENTION=5849464]mikeoswego[/MENTION], I already force-pushed the fix into gappsintegrator yesterday, so we should be good. :)

https://github.com/osm0sis/gappsintegrator/commit/d1ea6d5f03c62f589671e9c95ca411b9afc7a3f3
[SuperSU] :
Everytime I try to update via zip it uninstalls the version I have and nothing is flashed in case I am not rooted. I'm on the latest stable version. Runming custom stock 6.0.1 with unlocked BL.
[SuperSU] jabarel:
this superSu it`s for recive OTA updates? i just what to know, i`m running on my nexus 5x Android Nougat 7.0 tnx
[SuperSU] Ch3vr0n:
superSU is never for ota's and never has been.
[SuperSU] jacobv93:
is there a way for me to install this to the verizon galaxy s7 g930v?
[SuperSU] ulxerker:
this thread isn't a root howto, please refer to the appropriate subforums for your phone here: http://xdaforums.com/verizon-galaxy-s7
[SuperSU] jacobv93:
is the s7 supported for this supersu install, no better place to ask then the thread for supersu.
[SuperSU] egingell:
The method by which SuperSU is installed is exactly the same for (most) every device (especially Samsungs). You need TWRP (or Fastboot) which requires going there to learn how to set that up. Then flash SuperSU.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] nefescalanadam:
Cant get systemless root.. When flash supersu v2.78 sr1 , its only normal root my device
[SuperSU] Ch3vr0n:
Again read a few posts back. Unroot, enter that terminal command, flash SuperSU zip file
[SuperSU] nefescalanadam:
I said didnt work to you
[SuperSU] Ch3vr0n:
Then post logs
[SuperSU] nefescalanadam:
Pm me
[SuperSU] egingell:
Don't ask for PMs. Just post here.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] -Happy Feet-:
Has anyone an idea how can I install supersu as systemless with the Xperia Z3? When I flash the su zip it's normal installed in system.
[SuperSU] Ch3vr0n:
Yeah, read the last couple pages about uninstalling, entering a terminal command and flashing the zip.
[SuperSU] Zythyr:
In TWRP first mount the Data partition. Then go to Terminal and enter the following command:

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

Credit goes to @jcadduono for telling me how to force systemless install...
[SuperSU] RandomPooka:
Well, that's how you do it. But, it's also in this thread like ten thousand times if you just search for it.
[SuperSU] akarol:
Could you please link the post? I'm having a difficult time finding the exact post send command you are referring to.

Thanks in advance...
[SuperSU] The_Kian:
Hi, I installed SuperSU systemlessly, and i successfully flashed suHide. The xposed module didn't flash. I still can't pass the safetynet check. Any suggestions? I might consider reflashing my rom but that's a last resort option
[SuperSU] ashyx:
Then surely it makes sense to document it in the OP either here or the stable thread?
[SuperSU] eboissier:
Try to rename bin/su and xbin/su then reinstall xposed from xposed installer...
[SuperSU] nefescalanadam:
I try everything about read force systemless root, then flash supersu and it did patch boot image.. But still when try flash suhide, i get error message

Here my log;

https://drive.google.com/file/d/0B_U82T_MR6EHenZkT0tLX1VLSGM/view?usp=sharing
[SuperSU] Ch3vr0n:
No I can't, as it was just posted again in the post directly before yours
[SuperSU] Mudvayne622:
So I finally decided to jump in and do this so that I can use PokÃ©mon Go and Android Pay. Unfortunately I got a little worried after I disabled the built-in root on the Rom I'm using (AICP MM Nexus 6) and booted to TWRP. I went to the File Manager to delete or rename the "SU" files in system/bin and system/xbin but only bin was found in system and there were no files in the folder. I did find a Superuser folder shown in the screenshot. Using Root Explorer I found su in system/bin & /xbin. Am I missing something? What should I do? Delete the SU files from Root Explorer?
[SuperSU] Captain_Throwback:
You have to mount System in TWRP.
[SuperSU] Mudvayne622:
Ahhh of course. Thank you. Do I delete the SuperSu folder also? Also do I unmount System before flashing SuperSu and Suhide?
[SuperSU] egingell:
Also note that the /supersu folder in TWRP does not exist when booted into Android. It is part of TWRP.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Mudvayne622:
So you does that mean I leave that folder alone? Here's what I'm planning to do:

Disable Built-in root. Reboot

Reboot to TWRP and mount system

Delete Su file from system/bin & /xbin

Flash Sr9 SuperSu (not sure if I need to unmount system)

Reboot System

Reboot to Recovery

Flash Suhide

Reboot System and hope I'm systemless and pass Safetynet

Should work right?
[SuperSU] corkiejp:
Pixel Phones Not Yet Rootable with Current Methods

Pixel Phones Not Yet Rootable with Current Methods

[MENTION=631273]Chainfire[/MENTION] You will probably be kept busy with the above soon?
[SuperSU] Ch3vr0n:
Let's worry about that when the devices are actually announced/released shall we? So far everything is pure speculation and/or based on rumors. Google has yet to announce anything official or even confirm the name 'pixel phone'.
[SuperSU] _that:
The mentioned commits in the Android source code give us a rough understanding how the A/B stuff works, and apparently it works by using the boot image's ramdisk only for recovery. So the classic "systemless" rooting method will no longer work.
[SuperSU] Ch3vr0n:
Doesn't matter what they say now, things can change between now and actual release. Not the first time it happens. *Cough*root worked on L preview, but didn't on final release*cough*. That's exactly why chainfire stated for M he would not work on anything until final images were released. The same is true for devices.

Let's worry about that for when the 'pixel items' are released/announced shall we, so chainfire would exactly have someone to work with. For all we know every leak could be wrong and they could be watches or TV's. There is NO official announcement yet and there's won't be for another few weeks.

Everything is speculation right now and has nothing to do with superSU 2.78SR 1
[SuperSU] egingell:
I just mean that deleting that folder won't do any good in your quest to reroot and/or pass SafetyNet.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Mudvayne622:
Thanks. I ended up leaving the Folder alone and everything worked fine. Any idea if I have to do it this all over if I update my Rom to the latest nightly?
[SuperSU] egingell:
I don't think you'll have to unroot. Just make sure you don't wipe data and leave /data/.supersu alone if you forced systemless, but you still need to flash SuperSU after a ROM update.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Mudvayne622:
So you mean don't wipe data and cache as I normally would when doing a dirty flash?
[SuperSU] egingell:
If you're just updating your current ROM, wiping data is rarely needed.

At any rate, wiping data also wipes root because the root image (su.img - it's a virtual disk image) is in /data. But if you do wipe data, you don't need to track down any su binaries to delete because there are none.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Mudvayne622:
Ok good to know. Maybe I'll try it tomorrow and just reboot after flashing the Rom and SuperSu
[SuperSU] Wordzperfekt:
After flashing this file I received an att..error..and would not boot up.. The error said unauthorized software was added to this phone please turn off phone and go to your nearest att.. Store for help.. It wouldn't boot or anything but luckily I had the root g930a file to root still on my como and I had to reflash the root file and luckily I was able to get it back on I'm running an S7 g930a with echoe rom

Why did it try to change the boot. Img file that's what caused the major error
[SuperSU] .NetRolller 3D:
I have a strange issue on my Note 4 N910C on stock Marshmallow.

After installing 2.78 SR1, if I open a terminal emulator, "su" gives "not found".

Explicitly typing in "/su/bin/su" works.

If I set BINDSYSTEMXBIN=true in /data/.supersu, that fixes it.

If that helps, I have Magisk installed, and I previously had phh's superuser installed as a Magisk mod.

EDIT: If I set BINDSYSTEMXBIN, typing "which su" in a root shell gives the expected "/su/bin/su", but in a regular shell, "/system/xbin/su".

EDIT 2: Also, suhide 0.53 + xposed 86.2 doesn't work, it repeatedly clears the dalvik cache while it's being rebuilt, causing the rebuild to never complete. This happens with or without BINDSYSTEMXBIN. Suhide alone works, and so does xposed alone. Xposed 86.5 + suhide works too, but fails safetynet.
[SuperSU] gothicVI:
That's how it works. Simply restore your backup.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] egingell:
That's not strange. It's normal for an app whose dev hard codes the path to su, which has been poor form for a very long time.

Your edit 2 is not SuperSU related. It's Xposed, Magisk, or one of your Xposed modules.

"which" is a command that comes with busybox and should never be used to diagnose SuperSU issues.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] .NetRolller 3D:
Nothing is hardcoded here. I'm literally typing "su" into a terminal emulator. Same thing happens if I type "su" in the ADB shell. In fact, the only workaround I found is to hardcode "/su/bin/su", which is even worse, as it breaks compatibility with anything other than SuperSU.

Either /su/bin is not in the $PATH, or its strange permissions (executable but not readable) are preventing the shell from finding su in it.

Edit 2 is suhide-related, but suhide is strongly intertwined with SuperSU v2.78 SR1 (it won't run with any other version), so it could easily be a SuperSU bug.
[SuperSU] jody04c:
Running without issue on Oneplus 3, I have been rather fortunate as have never has issues with superSU, credit to Chainfire. Thanks for the ongoing support.
[SuperSU] danieldmm:
Getting some wird bug installing SuperSU 2.78 SR1 on cm14 , last night it was installing just fine, now its having a wird error and blocks at Creating paths.

Tried to see if was something cm14 intruduced over the last day but wont see nothing relative that can cause the hang.

- System-less mode, boot image support required
- Creating image
/data/su.img: recovering journal
/data/su.img: 365/6144 files (0.3% non-contiguous), 1610/24576 blocks
- Mounting image
mknod: /dev/block/loop0: File exists
- Creating paths
mkdir: can't create directory '/su/bin': File exists

Something on my side only ? Or if you need the full log from TWRP since the SuperSU installation started let me know.
[SuperSU] Starphish:
2 weeks ago I updated my Nexus 7 to the latest MM and rooting w/systemless SuperSU using NTR. SuperSU is not present in my app drawer. I have root confirmation and the Play Store shows SuperSU is installed.

When I did the update I did it over MoRom MM on which SuperSU appeared in settings. Now it is nowhere visible. Is there a wipe I missed, or some other trick to have SuperSU appear again. I'd prefer not to do a full wipe just for this bit of housekeeping. Suggestions?

Thanks!
[SuperSU] Phazmos:
Extract apk and install