yashsingh1/xdaforums huggingface dataset:
[SuperSU] lzanoni:
Thanks for your tip about posting, I never thought about hide :o.

Regarding the issue with the secure container creation, I still thinks it's related to some wrong permission, or context set on some of the binaries. For instance, avec using SuperSU (systemless), the 'system' user is not able to write to the external SDCard.

Of course I can't try without root as obvisously I 'm not able to "su system" ;)

Maybe SuperSU misses some context policy ?

And regarding the fact that it works a little better in permissive mode (creating the secure contained in internal /mnt), it's still failing to use the external sd as it should.

You talk about an app I should update/replace: which one exactly ? I'm only using SuperSu (and flashed TWRP), then trying to side-load various APK. My concern was that some apps refuse to install after rooting, they don't require root support. It looks like SuperSu changed some internal behaviour of the system.

Is it possible to log an audit of the failures caused by SElinux or Vold related stuff ?
[SuperSU] grep_i:
Yes you can log that with logcat.

I misread your story and thought you were using a filebrowser (app) to copy files to a secured folder and that the app does work when SU is in systemmode but not when in systemless mode.
[SuperSU] Chainfire:
I'm not really sure what's going on here. SuperSU doesn't change any rules (directly) relating to vold, and I'm not even sure if what you're doing is even supposed to be possible.

Nevertheless, I was able to install this package to sd after running this in a root shell:

supolicy --live "allow { kernel vold } vold_tmpfs file"
[SuperSU] Mazellat:
I use eXzistenZ Custom Rom (Nougat) by master [MENTION=599722]niaboc79[/MENTION] for my Xperia™ XZ Dual but there is no root, I flashed this same result. Is there a solution?
[SuperSU] hackxda:
Not compatible on Honor7 Android 6.0

I flashed Supersu v2.79 and v2.79 SR2 with SELinux mode. The phone stuck during booting. Always showing a booting logo but never enter the system. So, I modified the boot.img myself to change the cmdline from "androidboot.selinux=enforcing" to "androidboot.selinux=permissive", and then reboot. The phone can start normally and enter to the system. But if I changed the "androidboot.selinux" back to "enforcing", the phone stuck during booting again.

So, how can I fix the problem? Thank you!
[SuperSU] culiacanazo:
You did.... Lol i don't know sorry
[SuperSU] grep_i:
For starters you could give some more information about your phone model and make and Android version or ROM version and name and if possible post a logcat of a stuck boot maybe we can find out together what happens.

Or if possible replace your devices kernel with one that works with SELinux enforced modus.
[SuperSU] Chainfire:
There will be a new beta (SR) out soon (in a week or so?), which I think will fix this problem. If it doesn't, let me know.
[SuperSU] Devilix:
[MENTION=631273]Chainfire[/MENTION]

Hi, on gt-i9100 (S2) with Cyanogenmod 13, after a full unroot (tested via SafetyNet checker) i have try to flash SuperSU in "system mode" but after, i get always in a bootloop...

Instead, with RR rom this not happen...

Can you tell me something about this? Thanks. :)
[SuperSU] zizuka:
[MENTION=631273]Chainfire[/MENTION] would you recommend people running an "outdated" Android version to use latest SuperSU? I am on KitKat 4.4.2 and have been using SuperSU V2.0.1 for months. It has been working perfectly fine so I am not sure if I shall bother updating?

Thanks for everything!
[SuperSU] Badger50:
If it ain't broke......don't fix it [emoji106]

Sent from me :)
[SuperSU] DB126:
Community forum; if you want a 1-1 conversation use PM.
[SuperSU] pkelly517:
And yet Chainfire doesn't reply to technical questions via PM.

If it's technical, use the community forum.
[SuperSU] ulxerker:
why would you do that as it has been working perfectly fine for you? never touch a running system ... :)
[SuperSU] corkiejp:
Hope your not suggesting people PM Chainfire? His signature includes: -
[SuperSU] DB126:
No - just skip the '@' reference as that effectively becomes a PM. Unless highly "technical" ask the question and let the community respond. If I'm off base here Chainfire will weigh in.

Edit: For awareness signature blocks don't display in XDA labs (thankfully).
[SuperSU] zizuka:
i agree since it works but from 2.0.1 to 2.79 is a big jump so i was just thinking maybe there are benefits in upgrading. Changelog is huge but if it is nothing more than root in the end then i guess yea better to just stick to the old version ;)
[SuperSU] Ibuprophen:
My opinion is that the SuperSU updates is catered to reflect both the changes in devices as well as the Android versions. If an older SuperSU was successful in the older Android version then updating the SuperSU is not necessary.

With that stated, updating the SuperSU to a newer version should not be harmful but, always keep in mind that it might not be much, if any, different than the older version.

I have another device with the same Android version and have been content with the SuperSU 2.68 (i think that was the version) Stable installed and never found a reason/need to update it.

I wish you the best of luck with your decision.
[SuperSU] Strephon Alkhalikoi:
I dug my Dell Streak running Android 2.3.3 out of storage and managed to update it to 2.79 SR2 without trouble. Android 4.4.x should be a cakewalk in comparison. That said, there won't be much of a difference between versions.
[SuperSU] ulxerker:
FYI: SuperSu 2.79 SR3 has been released: https://xdaforums.com/showpost.php?p=70555217&postcount=8858
[SuperSU] DB126:
OT - ask in the Nexus 5 forum: https://xdaforums.com/google-nexus-5
[SuperSU] psychatog64:
delete
[SuperSU] :
Problem removing systemless root

I have tried to remove systemless root by unrooting from SuperSU main app and flashing stock kernel.

The problem is that after those actions i can't even load the boot animation.The kernel refuses to load the operating system.

It's something between bootloop and hard-brick.

If I flash SuperSU from recovery again,everything works fine.

Also,in my root folder "/ " there are some interesting files of Supersu (the su folder,init.supersu.d,and maybe others).

Why?Please help!

I have an unlocked bootloader,TWRP Recovery and Android 6.0 .
[SuperSU] Mesmurized:
Is it possible to install 2.79 in System mode (Nexus 5X, PN 7.1.1)? I used "echo SYSTEMLESS=false>>/data/.supersu" (trying to force system mode) during a clean PN flash but it would never finish the first boot.
[SuperSU] KaMyKaSii:
Try this:

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120/post64648982
[SuperSU] Mesmurized:
Thanks. Followed this thread for months, but never saw this system-mode reference. Just assumed is was a true/false switch setting.
[SuperSU] KaMyKaSii:
This is not an official version. The script is modified. It's probably even illegal if it violates the SuperSU terms of use
[SuperSU] Mesmurized:
Looking as the SU Setting page, from an Official 2.79 install, am I system or systemless mode?
[SuperSU] KaMyKaSii:
You forgot to post the screenshot
[SuperSU] Mesmurized:
Sorry about that. https://www.dropbox.com/s/wl0uzbew02uwiyr/Screenshot_20170117-200603.png?dl=0

This is the pits.... i've tried pastbin, imgur, and dropbox.... can't make any image display.

It's not like I've never done this before. But tonight ...... nothing.....
[SuperSU] KaMyKaSii:
You are running systemless. I recommend that you install stock boot.img and system.img before installing SuperSU system mode. But remember: If your device has forced encryption, It will be encrypted when you boot on Android
[SuperSU] Mesmurized:
Thanks. Guess my image was displayed (not to me :) ). I also installed Adaway, and wasn't required to enable systemless mode and it didn't show as systemless in settings. I'm soooooo confused now.

BTW: I'm running Pure Nexus + Elemental X Kernel. I believe both disable forced encryption.
[SuperSU] KaMyKaSii:
Apps do not have to really worry about what kind of root installation was done. This is (almost) totally done by SuperSU. Apps only need to call "su" and SuperSU responds
[SuperSU] Mesmurized:
Thanks. Yea, I understand the concept. Used to be a Xenix admin about 20-25 years ago.

For me, it seemed systemless was a loosing battle to get AP plus a few banking apps working while rooted plus always had significant free space on the system partition. Figured it would always be a cat/mouse game which I wasn't interested in pursuing. Hense the reason to stay pure Unix system mode. Maybe I'm wrong and should just "go-with-the-flow"
[SuperSU] Uqbar:
Update the flashable zip, please!

Update the flashable zip, please!
[SuperSU] Mesmurized:
Why does it need to be updated?
[SuperSU] Uqbar:
The zip is from 2016, the OP talks about 2017!
[SuperSU] Pkt_Lnt:
When the Service Release (2.79SR3 Beta) is done (now at version 3) it will be updated. This is the current [STABLE] release!
[SuperSU] Mesmurized:
v 2.79 (released 12/5/16) is the latest stable release. Service (aka beta) releases are found in a different thread.
[SuperSU] egingell:
Because demanding updates is how you get updates, right? ... Right?

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] calaiou:
Hello and sorry my english, i instal official nougat DPLT with odin in ly S7 flat , i flash twrp, encryption...... all ok , but when i flash this superSu , i have my camera dont work , sorry
[SuperSU] Gibz97:
Hi everyone.

I'm trying to root a Tecno W4 phone running on Android version 6.0.

I have flashed SuperSU-v2.79-201612051815.zip in TWRP mode and it was successful (did not face any error in TWRP).

However on booting into the phone, there is no superSU app and root has not been installed as reported by the Root Checker app, other apps which require root do not work as well

I have attached the TWRP log. Can anyone help me out please.

Thanks in advance.
[SuperSU] jcmm11:
Try SuperSU 2.79-SR3

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] Gibz97:
Thank you for the response.

I have downloaded and flashed SuperSU 2.79-SR3 but still facing the same problem, no root is installed.

Log attached
[SuperSU] grep_i:
In your log there are issues with mounting /cache and /data and while patching the boot image your device runs out of space in the /boot mountpoint.
[SuperSU] Gibz97:
Any suggestions?
[SuperSU] grep_i:
You could try and install busybox try agai to flash SuperSU and see if the problem gets resolved or you could try to clean flash the rom and than try flashing SuperSU again.

Otherwise you could try to mount the mountpoints manually and see if you get a better error message, that are all the things I can think of right now.
[SuperSU] jdegreef:
That's a well known message that everybody get. Look at the dd command following, it succeed.

---------- Post added at 21:04 ---------- Previous post was at 21:02 ----------

What busybox has to do with flashing Supersu from TWRP ?
[SuperSU] grep_i:
I have just reported everything I could find in his log and if all this is normal behaviour maybe you can tell why it is not working for him ?

Try Google about BusyBox and toybox and maybe you will understand it better than I can tell you.
[SuperSU] jdegreef:
The question is : did install busybox solve the problem ?
[SuperSU] Ibuprophen:
Just to let you know that, for me, if the BusyBox Binaries are installed correctly, it also Symlinks with the Toybox Binaries that BusyBox doesn't have too.

I can see the Toybox along with the BusyBox Binaries listed within the app.

But, that's just my experience when it comes to my d2vzw device with CM13. I'm not sure if that's the case for other rooted devices.
[SuperSU] Fif_:
[Posted by mistake, sorry]
[SuperSU] grep_i:
I do not understand your question, I am not having any issue.

So it does not matter what I install isn't it ?

Have you read up about toybox and BusyBox ?

I do not know if BusyBox solved the problem because the guy with the problem did not respond anymore or I missed his response that's also quite possible.

All I answered were suggestions not facts which would solve his problem so if you want to know the answer on that question ask the one with the problem.

Do you know the answer to solve the guy his problem ?

If so please spit it out.

My setup is:

Nexus 5 Hammerhead Android 6.0.1 M4B30Z, Google & LG

Supersu 2.79-SR3, Chainfire & CCMT

Flashfire v0.54-pre, Chainfire

TWRP 3.0.3-0, TeamWin (not flashed on device but only boot to)

ElementalX-N5-6.27, Flar2

Xposed systemless v86.1 SDK23, Romracer

suhide v0.55, Chainfire

Rootswitch 1.3.3.2, Shakalaca

BusyBox 1.26.2, Stericson

Passing safetynet green and can use Xposed completely without problems.

Can play Pokemon GO if wanted and even Snapchat login is working if I want this to be used on my device.

Please press the "Thanks" button I really like it, thanks.
[SuperSU] Gibz97:
Yes, I flashed busybox bionic zip in recovery from this thread https://xdaforums.com/showthread.php?t=1929852 as it was impossible to install it in System due to the fact that I am still not rooted, then flashed systemless SuperSU v2.76 and unfortunately the phone is still not rooted and SuperSu app is not installed.

I tried flashing UPDATE-SuperSU-v2.79-SYSTEMMODE from this thread https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 and this time the SuperSu app is installed in the System, even prompts me to allow Superuser access to apps, however the apps complain that root has not been installed. Root Checker app shows "root access not properly installed on this device".

I have attached the recovery log after flashing systemmode SuperSu
[SuperSU] grep_i:
Great news :highfive: :good:

One thing the log you posted is from when you flashed osm0sis unsu script nothing else.
[SuperSU] Gibz97:
Oops! My bad.

I have updated the log. Thanks
[SuperSU] TimSchumi:
Hello,

I was trying to root my OnePlus 3 using the SuperSU-v2.79-201612051815 package.

It always fails on extracting the ramdisk, but it will still continue and the script finishes successfully. But after the reboot root access is still missing.

This only seems to happen if the phone is decrypted (using the "fastboot format userdata" command). I think it's not about the ROM, as it happens on Sultanxda's CM 13 and on the unofficial LineageOS 14.1 by koenkk.

I made it work some time ago, but I don't remember if the device was decrypted there.

EDIT: I now returned to 100% stock through the OnePlus 3 Unbrick Tool, erased userdata, flashed TWRP and then I rooted it through the SuperSU ZIP. It went through the process without a problem and after I rebooted, I had root access and the phone was decrypted on stock OxygenOS 3.1.2

I'll flash CM again and will see if it works

EDIT2: It now worked after I wiped everything in TWRP, flashed CM and flashed SuperSU

@Chainfire Would be worth investigating this though
[SuperSU] flaxx187:
hey

1) i flash 32.2.A.5.11

2) install twrp-3.0.2-0-E6653-20160417.img

3) start and configure the start-up

4) install SuperSU-v2.79-201612051815.zip

after the restart i have the blanc white sony display

but what did i wrong ?

Xperia Z5
[SuperSU] Mesmurized:
Does anyone find this text confusing to determine system/systemless install mode?

In SuperSU/Settings/System

------- dimmed (2 lines) --------

Install SuperSU into /system

Not (currently) available in system-less root mode
[SuperSU] culiacanazo:
It's not meant to determine install mode...

It's meant to allow you to install as a system app, and when in systemless, it grays out and it proceeds to tell you how it's "not (currently) available in system-less root mode..."
[SuperSU] Portgas D. Ace:
Not really confusing, as it clearly states that it is in systemless mode.
[SuperSU] Mesmurized:
Thanks. Never realized this was a possible option.
[SuperSU] jaladhjin:
Hopin' for a little help I've got a Kindle Fire 5th Gen with Kingroot on it & I'm trying to get SuperSU going..

It used to be simple.. there were terminal emulator scripts for it.. SuperSU itself even attempts to take care of it all it seems..

But lately it appears KingRoot is actively attempting to prevent SuperSU from taking over..

Anybody have any advice on how to let SuperSU take over Kingroot 5.0.3

http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Does not work :(
[SuperSU] DB126:
Responded in 5th gen Fire forum. In a nutshell once KingUser is removed as a device admin use the KingRoot -> SuperSu function in the 5th gen "SuperTool" to execute the conversion. SuperSume will not work on this device.
[SuperSU] farquea:
Had my phone rooted but suddenly unrooted itself and can't get root back. Tried reflashing and using the super su unroot option but can't get root. Any ideas?
[SuperSU] zimmen:
Anyone who knows if SuperSU works with the Nougat update on Huawei Honor 8?
[SuperSU] DB126:
Experiencing something similar on one device with CM 12.1. Spontaneously unroots, often following a privilaged app delete. Frustrating. My awkward solution involves reflashing SuperSU, wiping cache partition (not dalvik) and then reinstalling SuperSU app. Tried several recent SuperSU builds. Can not reproduce on demand. Note: the cache wipe is essential; otherwise SuperSU claims no su binary is installed even though it's clearly there (system/xbin).
[SuperSU] injuhneer:
Attempting to use Wifi Tether App on HTC A9/6.0.1 with SuperSU 2.79.

Have been attempting to get Wifi Tether App to work since 2.78 SR1 (worked under 2.46 on KitKat / Desire 510). Wifi app log indicates ndc is not present.

- ****** Check Status On Various Users ******

-

- Error: /system/bin/ndc: Permission denied

-

- Check with Simple User

- Error: sh: <stdin>[1]: /system/bin/ndc: not found

ndc is in the path and permissions set.
[SuperSU] KaMyKaSii:
You can't expect an app from early 2014 (in the KitKat era) to work perfectly on Marshmallow. In addition to not being upgraded to the new system, it also has not been upgraded to work with systemless SuperSU. This is an app problem, you should report this to developer, but as the development is gone, all you have to do is look for a similar (updated) app
[SuperSU] injuhneer:
In the event I was not clear:

CURRENT phone is A9 on Marshmallow. Wifi app is current version. SuperSU is current version.

I have reported to app developer who then pointed directly to the ndc denial stating this is a SuperSU issue. With the transition of SuperSU from Chainfire to new guys I brought the question/problem here.

It is nice to have the devs pointing to each other. Sort of leaves me in the middle with no working options. :(

I will do as you suggest and report to the wifi app dev (again) but I already know what his answer will be.
[SuperSU] farquea:
I fixed my issue. By disabling SuperSU and enabling again from the app settings gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.
[SuperSU] injuhneer:
OK, here is the dev response:

I'm sorry to say otherwise

This depends on SuperSU

what you have pasted of the log as an error is normal it happens to all devices

because an attempt is made without root permissions

if can not start ndc without root permissions this is error is that you've pasted before
[SuperSU] ktmom:
Maybe try installing in system mode. It might help if the app you're using isn't totally updated to "modern" systemless methods.
[SuperSU] EmirSc:
Installed and rooted successfully (ver. SuperSU-v2.79-201612051815) on a Huawei G8 with [ROM][7.1.1 LineageOS]

this is the first time i root a phone, what next, what should i do?. (take advantage of rooting)
[SuperSU] ktmom:
Why did you root if you don't need it? Usually a device is rooted to achieve a goal, not as an end goal.
[SuperSU] EmirSc:
because im curious, yesterday learned to install TWRP and install custom room, now im here.
[SuperSU] ktmom:
this
[SuperSU] EmirSc:
lol yeah, already did, with: i rooted my phone now what, thanks.
[SuperSU] DB126:
Google is your friend: http://bfy.tw/9iJP
[SuperSU] EmirSc:
yeah as ktmom pointed out.
[SuperSU] Leon:
Guys, I had bootloop and fail to update it. Also now some apps don't work that request root.Running HTC One M8 with Android 7.1.1

Is there any solution? Is supersu enough optimized to work with nougat or should stick with the root that comes with the rom?

I flashed v2.46 from here https://download.chainfire.eu/696/supersu/

But I see now there is a newer version? So this side is out of dated?

Thank in advice.

PS

Solved.
[SuperSU] khalid11:
Ok
[SuperSU] MPeti1:
SuperSU bug with MIUI applock

Hi!

If I lock SuperSU with MIUI 8 (Global Developer 7.1.19) applock and I open an app what has no su permission yet, MIUI applock opens because SuperSU wants to show the permission window, wants to draw the pattern or read fingerprint, but before i can scan my fingerprint, SuperSU denies access, and blocks it for some time for the new app.

In this video i show it with FlashFire:

https://www.youtube.com/watch?v=FaIjW5da_c4
[SuperSU] Ja_som:
Then do not use MIUI app lock and use pin protection in SuperSU ;)
[SuperSU] jhadsfi:
Hi I have a problem. I have an HTC 10 with LOS 14.1. When using the builtin root gsam and better battery stats are able to display battery stats. But when I root using supersu they stop working with root access granted. Can anyone tell me how to solve this?
[SuperSU] jdegreef:
You can increase the delay before Supersu denies access in Supersu parameters.
[SuperSU] 7root:
Hi there,

I have an issue with SuperSU 2.79. I installed the ZIP via TWRP on my OP3 running CypherOS 3.5.1 based on Android 7.1.1. I tried granting root permissions to an app and it was stuck in the "acquiring root permissions screen". Reinstalled the ZIP and it worked. 10 minutes later root was broken again. The SuperSU app is telling me that there are no SU binaries installed, although everything should be working fine. Root Checker does not detect root access as well. Any advice?
[SuperSU] DB126:
Happens to me regularly on all builds post 2.76 on one device. Rather frustrating as there seems to be no acknowledgement of problem. I've learned to deal with it by wiping the cache partition (dalvik not required) and then reflashing SuperSU zip when root is lost. The supposedly missing binary remains on the device but apparently can not be seen/accessed. Feels like a permissions issue.
[SuperSU] Y314K:
Looking for SuperSU v2.05 Final APK or full zip. On the search engines there are mostly dead links or mislabeled APK's. I've been told this version of the SuperSU APK will open up the apps GUI on a rooted AFTV. So would like to test that out. Appreciate any help getting a hold of it. TY
[SuperSU] Ja_som:
2.05 is really old

https://download.chainfire.eu/461
[SuperSU] 7root:
How frequently is root lost in your device? Because having to reflash the ZIP every hour is not a long-term solution. I tried to uninstall SuperSU because my ROM is apparently pre-rooted and used unSU, but that also deleted the ROM SU binaries. Is there a way to regain them?
[SuperSU] Y314K:
Yeah, but seems to be the last version that GUI will open on a rooted AFTV1 device.

TY, thought there might be a FINAL version of it. ?
[SuperSU] egingell:
A "final" version? You got *the* version.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Whoeta:
Su
[SuperSU] DB126:
Irregular but often cooresponds with a reboot following work with any app that requests privileged access. Device in question is running CM 12.1; none of my KitKat or MM (systemless) exhibit this behavior. Root Validator indicates SU is in the expected location with expected permissions after root is denied.

Have never used unSU. You *may* have to reflash your ROM to regain binaries.
[SuperSU] Y314K:
Your right. Just checked the change log & that version was a beta. Is there a way or trick to find/search any *the* version from chainfire's site?
[SuperSU] egingell:
That's the version you want. Use it.

Every version was once a beta.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] jdegreef:
See OP !
[SuperSU] Y314K:
I meant for a way to find/search for older versions. Not latest @ chainfire.eu.