yashsingh1/xdaforums huggingface dataset:
[SuperSU] leleobhz:
Issue/Bug Report

In both BETA-SuperSU-v2.71-20160331103524.zip and UPDATE-SuperSU-v2.65-20151226141550.zip I got this on V500 using cm-13.0-20160411-UNOFFICIAL-awifi.zip, resulting in a boot loop. Does not happens in AOSP ROM for V500.

04-21 18:34:27.864 9289 9289 W init : type=1400 audit(0.0:1113): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p23" ino=16210 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
04-21 18:34:30.994 9290 9290 I Netd : Netd 1.0 starting
04-21 18:34:30.994 9290 9290 I QtiConnectivityAdapter: Failed to open libconnctrl, some features may not be present.
04-21 18:34:30.995 9290 9290 D TetherController: Setting IP forward enable = 0
04-21 18:34:31.907 9309 9309 W init : type=1400 audit(0.0:1114): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p23" ino=16210 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
04-21 18:34:36.015 9310 9310 I Netd : Netd 1.0 starting
04-21 18:34:36.015 9310 9310 I QtiConnectivityAdapter: Failed to open libconnctrl, some features may not be present.
04-21 18:34:36.015 9310 9310 D TetherController: Setting IP forward enable = 0
04-21 18:34:36.922 9333 9333 W init : type=1400 audit(0.0:1115): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p23" ino=16210 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
04-21 18:34:41.050 9335 9335 I Netd : Netd 1.0 starting
04-21 18:34:41.050 9335 9335 I QtiConnectivityAdapter: Failed to open libconnctrl, some features may not be present.
04-21 18:34:41.050 9335 9335 D TetherController: Setting IP forward enable = 0
04-21 18:34:41.967 9353 9353 W init : type=1400 audit(0.0:1116): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p23" ino=16210 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
04-21 18:34:46.115 9357 9357 I Netd : Netd 1.0 starting
04-21 18:34:46.116 9357 9357 I QtiConnectivityAdapter: Failed to open libconnctrl, some features may not be present.
04-21 18:34:46.116 9357 9357 D TetherController: Setting IP forward enable = 0
04-21 18:34:47.002 9373 9373 W init : type=1400 audit(0.0:1117): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p23" ino=16210 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

04-21 18:34:51.127 9375 9375 I Netd : Netd 1.0 starting
04-21 18:34:51.128 9375 9375 I QtiConnectivityAdapter: Failed to open libconnctrl, some features may not be present.
04-21 18:34:51.128 9375 9375 D TetherController: Setting IP forward enable = 0
04-21 18:34:52.047 9395 9395 W init : type=1400 audit(0.0:1118): avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p23" ino=16210 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

What is wrong?
[SuperSU] alireza_simkesh:
I tried this solution to bring back compatibility mode but It doesn't seem to be doing anything. After performing the above command in Terminal Emulator I checked my /data folder and indeed there is a .supersu file with has the line, containing BINDSYSTEMXBIN=true, however, after flashing SuperSu again I don't see any compatibility options in the settings.

Does anyone know how we can bring back compatibility in SuperSu?
[SuperSU] fmc000:
There's no option to activate. It's enabled automatically when you reflash the zip and the .supersu file has that line.
[SuperSU] alireza_simkesh:
Roger that.

I confirm that compatibility mode is indeed activated automatically after following that instruction, even though there is no options for it in the settings.

Thanks.
[SuperSU] torhect:
I have a problem i dont know why but my supersu 2.71 is not there anymore! And i flashed again and nothing happened im still without root :( i have a custom rom and a custom kernel cam someone help me????
[SuperSU] Fif_:
Recovery.log from the SuperSU flashing session please.
[SuperSU] torhect:
Sorry but i dont understand!
[SuperSU] Fif_:
http://bfy.tw/5PFY
[SuperSU] XAL2:
Root Android N

I'm sorry if this has already been answered but how do I root android n? Do I just flash the zip file in the recovery after flashing the android n image file?
[SuperSU] dechronic:
It must be a custom recovery and only 2.71 Beta supports it. If that helps
[SuperSU] Deltadroid:
The unofficial aosp rom for v500 is running in permissive mode and the unofficial cm13 rom for v500 is running in enforcing mode. That is why SuperSU works for aosp and not cm13 for v500.

If you check the v500 forums, there is a thread I created with scripts to bump the boot image and set it to permissive mode, if you want to use supersu with cm13 for the v500.
[SuperSU] Joker87:
I own a galaxy S5, G900F, flashed stock MM fw, then TWRP and flashed Supersu Beta 2.67... no root present :-/
[SuperSU] XAL2:
So I would have to use adb commands to get the custom recovery on android n?
[SuperSU] Ja_som:
Yes.

But it depends on that if you can use custom recovery (TWRP) on your Andoid N device. On some encrypted devices TWRP does not work. So if your device is not encrypted, flash TWRP via fastboot command from your PC and then flash SuperSu zip in TWRP. If your devices is encrypted, use CF auto root from PC to root your device.
[SuperSU] Alxoom33:
TWRP works just fine on my encrypted NEXUS 6 running Android N P2.
[SuperSU] Ja_som:
I changed my post now :)

On my N5X encrypted it does not :)
[SuperSU] XAL2:
Well I am running TWRP on my Nexus 6P right now with Cyanogenmod 13 if that helps any.
[SuperSU] Ja_som:
Not really...

I think, the easiest way is flash N factory image and use CF auto root. You don't need TWRP for that ;)

Or, if you have enough time, you can flash N factory image, flash TWRP, you will see if it works, if yes flash SuperSu. If not (it will not harm your device, it will only stays on TWRP splash screen) reflash stock recovery from factory image and then use CF auto root.
[SuperSU] XAL2:
Oh I definitely have enough time. I was planning on flashing to Android N factory image tonight. I just was scared if I run into problems. However if I do I could just boot into the bootloader and reflash the stock image and be fine correct?
[SuperSU] Ja_som:
Yes, it should. You use CM, so I think it will be good to wipe your data also.

But I also have one thing... N should not be used as daily driver, it has some bugs. On my N5X I have some random reboots, some apps does not work, on all devices BT LE devices can't be connected. And some other bugs...

And now, from N theme back to SuperSu theme ;)
[SuperSU] XAL2:
Okay perfect. I was only gonna try it out for a couple of days. Or perhaps just enroll in the beta program afterwards who knows. Thank you for the help! :)
[SuperSU] leleobhz:
In first place, thanks for you awnser! I'll look for it. Second thing: Its possible to V500 be on top of Incompatible Systemless mode? Modifications to boot image w/o loki correction results in a NOGO bootloader condition.
[SuperSU] Deltadroid:
Yes, systemless works with the script I provided to bump the boot image and set the system to permissive mode. See this post:

http://xdaforums.com/showthread.php?p=65791891

Edit:

This is the script that is needed for v500 running cm13 with SuperSU in systemless mode:

https://www.androidfilehost.com/?fid=95916177934554767
[SuperSU] Joker87:
I own galaxy S5 with official MM fw, I tried supersu beta 2.71

I wanted to try systemless root because with traditional root I can't use the reactivation lock feature. But after flashing TWRP and supersu it will show "Warranty bit kernel" message at boot and still reactivation lock not available, even if I reflashed stock recovery.

Is that TWRP related or supersu related?
[SuperSU] Ch3vr0n:
Neither, it's kernel related.
[SuperSU] qwerty22:
DEL
[SuperSU] sqpp:
Adblock problem fixed on N version already? for my nexus 6 didn't worked a few weeks ago.
[SuperSU] Ch3vr0n:
Why don't you ask in the adblock topic? That's what it's there for, that has nothing to do with superSU.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] sqpp:
my bad, sorry :(
[SuperSU] nixie2121:
quick question... to install systemless, we still need to type the echo SYSTEMLESS=true.....correct? or is there an easier way now? thanks
[SuperSU] The Analog Kid:
... And it is not just for Nexus devices, but for devices running MM, as far as I know
[SuperSU] Alxoom33:
No, that's it! Only once, though.
[SuperSU] Joker87:
Can you make it compatible with samsung's reactivation lock? It won't turn on when rooted
[SuperSU] shoey63:
Hi Chainfire.

As you are aware, the Sony Xperia Z3 is the first non-nexus device to receive the N-preview. There are some issues with sim card not being recognized and random reboots after installing supersu 2.71.

Here are all the logs I could gather, plus the ramdisk and kernel parts of the stock boot.imgView attachment 3732306

Please have a look at them when you have the time.

Thank you.
[SuperSU] cstratz:
SU v2.71 Beta (Root-) is not recognized by several apps on my Note 4 (N910FXXS1COK1): Coolify Flat, SDMaid, TWRP Manager ... but Titanium Backup (7.3.0.2) does.

Last working version is v2.65 stable.

But since update with N910FXXS1COK1, TWRP v3.0.2.0 and SU v2.65, keyboard is always set back to Samsung by default, instead of SwiftKey! (reason unknown) This also happened with SU v2.71 Beta.

Any solution?
[SuperSU] Ch3vr0n:
Tell the app developers to update their apps instead of using hardcoded paths
[SuperSU] Pkt_Lnt:
Chainfire's legacy enable command via terminal.
[SuperSU] :
Some apps like es file manager is not recognizing supersu beta 2.71

Sent from MotoG 2014 Titan

Stock official Marshmallow
[SuperSU] osm0sis:
Same as above, ES File Manager devs needs to fix their app.
[SuperSU] Pkt_Lnt:
Read the post above yours. ;)
[SuperSU] zoppa:
https://plus.google.com/+Chainfire/posts/dGPQytapwe3

Gesendet von meinem Nexus 6 mit Tapatalk
[SuperSU] NYCHitman1:
[MENTION=631273]Chainfire[/MENTION] Is there anything that I can personally do to change your mind?

I'm a big fan of your work and not a fan of the janky methods we currently have on Dragon (Pixel C), so whatever it is that you need -- let me know and perhaps we can collaborate on getting this done :)
[SuperSU] Joker87:
I found the answer by myself... :(
[SuperSU] szihs:
[MENTION=631273]Chainfire[/MENTION] With super su 2.71 enable superuser toggle and toggle back looses root. It used to work in earlier versions. On Nexus 5 Marshmallow.. Stock recovery
[SuperSU] sqpp:
May its a dumb question and already asked, but when going to release new version, which fix problems for Nexus devices? (for more info Nexus 6 with Android N)
[SuperSU] IronTechmonkey:
It probably has not been asked because asking for ETAs is a no-no. ;)
[SuperSU] corkiejp:
Which Problems? It maybe not supersu that needs updating, but other apps need to be updated to work on N.
[SuperSU] sqpp:
Yeah i know that, example ES File Explorer (contacting developers gonna fix it for sure..) However AdAway still not work for me. Even its just a simple root. In their thread told me to contact with SuperSU developer(s), cause this should be fixed by them.
[SuperSU] Chainfire:
If you aren't going to supply any relevant information, you might as well not ask the question.

Again, lack of information. What happens exactly? What did you expect to happen exactly? In what post were you told this was a problem with SuperSU, include links.

Also, are others reporting the exact same problem? If so, where (links!)
[SuperSU] junioramboy:
Who said it's not working?

Shamusent
[SuperSU] darioze:
Hello chainfire, 6.0.1 Note 4 Edge N915G there be any root? thanks!
[SuperSU] sqpp:
My bad Chainfire.. Sorry just working right now, so hard to concentrate.

Well look at my steps:

1. Installed Developer Preview 2 via NRT (Nexus Root Toolkit)

2. Then flashed latest TWRP (twrp-3.0.2-0-shamu.img)

3. Then flashed of course SuperSU v2.71 too.

4. Started my phone.

5. Installed latest AdAway from official source.

6. Everything seemd perfect since Root popup came in and allowed it.

7. And then got output like that:

---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------

Look, i not gonna go into this, but tons of user talking about this in AdAway thread.

Simple cannot modify the host file. Even in PureNexus works fine.

After going to N version somewhy its fails.
[SuperSU] IronTechmonkey:
I can't speak to the specifics in this case but it does seem that some people, using systemless root in particular, are having problems managing their hosts file in Adaway, although in most cases it seems to be an issue with process or a unique usage case.

[EDIT] http://xdaforums.com/showthread.php?p=66541490

---------- Post added at 11:54 AM ---------- Previous post was at 11:31 AM ----------

Such a gigantic page hogging image file to make a snarky and unhelpful point. Might I suggest at least using the "Hide" tags for such a thing, and perhaps offering help instead. :)

---------- Post added at 12:00 PM ---------- Previous post was at 11:54 AM ----------

There really is more you could do to help your cause by providing full details. Pardon my getting involved but, there has been an ongoing spat about Adaway under SuperSU in which "loyalists" on both sides are blindly blaming the other guy. Without both SuperSu and Adaway I would consider Android woefully incomplete. With better reporting this might get resolved. Also, do consider that N is very new and which means - issues.
[SuperSU] sqpp:
Of course i understand your point with less details, but i just simply cannot provide more. Since there is no such an error code or something like that.

Only the lines, which already provided. However yeah its a not-ready OS yet.
[SuperSU] zoppa:
And direct the developers of your App to

https://plus.google.com/+Chainfire/posts/dGPQytapwe3

where Chainfire explains what might be going wrong.
[SuperSU] Chainfire:
There are two common issues with newer versions, of both SuperSU and Android.

(1) compatibility mode is turned off by default since the N Preview releases, see this post: http://xdaforums.com/showpost.php?p=66140836&postcount=5493.

It's been half a year since the su path has changed, and I have been advocating against hardcoding the su path since 2012, as a change like this was bound to happen at some point. This is what a lot of the apps that aren't getting root at all are doing. This is a documented bad practise, see the Common pitfalls section of the How-To SU document.

The fix for root app developers is in most cases a one-liner.

(2) things change - sometimes significantly - between different Android versions, as any dev who has been around for a while knows. So too with modifying /system on N Preview. Details about the mount issue are documented in my G+ post N Preview: Surviving Your Trip To Mount Doom. This is not part of any official docs yet because preview.

SuperSU isn't even remotely responsible for making you able to write to /system or not (in fact on some devices this cannot be done at all), and even if it was, this specific issue would be hard to solve. Hopefully this issue in Android itself will be fixed in the retail N release, but I somehow doubt that.

The fix for root app developers is in most cases (again) a one-liner.

I have tried to make life easier on root app developers for many years, but at some point, they also have to do some of the work to maintain compatibility.
[SuperSU] sqpp:
Even its for DP1 and me using DP2 doesn't give me explanation why works for somebody and why not for someone else.
[SuperSU] Chainfire:
I'm not sure about the Note4 Edge, but I know there has been some trouble with the 6.0 ROM for the S5. I will be looking into both shortly.
[SuperSU] IronTechmonkey:
Pardon my ignorance but could you or anyone else clarify what one-liner means in this context.
[SuperSU] nathanchance:
One line of code.
[SuperSU] IronTechmonkey:
I should have known but have too much shtick comedy on the brain. "Is this thing on"? :) Thanks.
[SuperSU] Pkt_Lnt:
What I see in that thread is those using the F-Droid version are having issues, and those using the XDA version are not. MrRobinson has updated the version he compiles, and has a flashable zip for those using systemless root. There are many posters with various devices using N preview and Adaway from XDA just fine. The BIND command in the flashable zip solves the "write to system" error because it does not have to write.

It appears the F-Droid version does not have the necessary commits to work with systemless, since the maintainer there has abandoned development and given approval for MrRobinson to take over.
[SuperSU] drewski_1:
+1 AdAway working on my Pixel C on N
[SuperSU] Joker87:
I own a galaxy S5 and have no trouble at all with systemeless root and marshmallow stock firmware
[SuperSU] Chainfire:
That thread is one big ****fest, just wow. I love specifically how systemless SuperSU is bashed while the systemlessness of SuperSU has nothing to do with the issue they are having. It's just completely irrelevant to it. Someone saw a correlation and imagined causation.

Interesting. It failed patching the boot image for me first time around, but I have not had any time to check out further.
[SuperSU] IronTechmonkey:
Nice description. I hope you dont mind if I link directly to this post from the Adaway thread if this comes up there, although it might be better if I copy/paste and cite you so the Adaway specific responses dont end up here.
[SuperSU] Pkt_Lnt:
Cut and paste please. Don't drag that uninformed, misguided mess over here. I don't even reply anymore since the old curmudgeon lecturer took over the thread and then stared the anti-development rant against SuperSU. :eek:
[SuperSU] arbit12:
I have Note Edge 915G 6.0.1 and the root is working fine with both the 6.0.1 firmwares released so far. Used TWRP 3.0 and SU 2.71b.
[SuperSU] IronTechmonkey:
Ha, "old curmudgeon" could just as well be me. Get off of my lawn you crazy kids! :). As to the anti-dev rant, there may have been a small kernel (pun intended ) of truth in it about the general course of dev (only during the first few weeks after systemless root was introduced) which was then stretched too far. Not taking up a debate about it and will try not to go off further off-topic about it here. Will mos-def not link to your post.
[SuperSU] darioze:
Chanfire, I tried the SuperSU with TWRP 3.0 and goes well! Good! Thank you! Sorry for my English!!

Enviado desde mi SM-N915G mediante Tapatalk
[SuperSU] dechronic:
Chainfire has a very good write up about why root apps may not work on Android N Preview on this Google+ page https://plus.google.com/+Chainfire/posts/dGPQytapwe3

This explains why apps cannot mount /system as rw so as to edit files such as the hosts file located at /system/etc/hosts

With each new iteration of android there has been more security features.

According to that post it is clearly NOT SuperSU but SuperSU is providing a work around.

The bashing of SuperSU for problems with root apps on an incomplete and unreleased operating system to the mainstream is highly unfair and uncalled for.

If someone, even a developer, doesn't understand the new changes his first course of action should be to ask a question or share his findings so as to promote what XDA stands for. Community.
[SuperSU] myocytebd:
I am confused about systemless mode's current status.

Is SuperSU defaulted to systemless when available?

Or what must I do to apply systemless mode from stock?

I cannot find any explanation or guide dated after chainfire closed systemless thread.
[SuperSU] nathanchance:
Starting with version 2.64 and above, the installer will attempt to install SuperSU into /system first then fallback to a systemless installation if that is not possible. Should you want to force SuperSU to install as systemless, type this into the terminal in TWRP or a terminal emulation, then flash SuperSU:

echo SYSTEMLESS=true >> /data/.supersu

On stock Android (6.0.1 Marshmallow) for Nexus devices (my area of expertise), SuperSU will default to systemless because root via /system is not possible without a reloaded sepolicy.
[SuperSU] LoverBoy2415:
Deleted..
[SuperSU] grep_i:
It's the other way around first systemless and if you're rom has reloaded or patched sepolicy Supersu falls back to system mode.

I guess most custom roms have patched or reloaded sepolicy that's why most of them installs systemmode.

This you can find literally in the change log of v2.64
[SuperSU] nathanchance:
No, no it isn't. System detection is done first meaning that is the default. Open up the zip file and look at the updater-script. Also straight from Chainfire himself:

.

Fewer firmwares from both OEMs and developers are including the modified sepolicy because systemless works so well but systemless is NOT the default because if it were default, you would need an override to install into system forcefully, not the other way around.
[SuperSU] teddy0209:
Just look at the update_binary guys... you'll see everything there... ???
[SuperSU] magnamentis:
i alone mentione this multiple times as did many others, stick to v2.68 for MM only for N-Preview this beta is mandatory.

not sayin' it does not work well on MM but there still are apps that were not brought up to standards hence if you need help to troubleshoot it's better to avoid possible trouble in the first place and stick to v2.68 or even v2.65 stable.
[SuperSU] Ch3vr0n:
Wrong, 2.71 works just fine on MM. It's the apps that need updating to not use hardcoded paths. There's no point in advising users to use an outdated version, how can things be verified to be fixed or occurring if people don't use newer versions.

What you're advising to do is simply bad advise.
[SuperSU] Alxoom33:
I have a NEXUS 6 on Android N. 2.71works perfectly.
[SuperSU] crisjogos:
Just for info, v2.71 doesn't work well with secure settings app on Samsung Stock MM 6.0.1. Version 2.68 works fine.
[SuperSU] grep_i:
Please read your own comment it is contradicting.

If system mode is the default than why is there a check added to check to install system mode in the changelog and not a check to install systemless ?

Read the following text this is directly from the install script you do mention I hope this will clarify:
[SuperSU] nathanchance:
Okay, if you have a firmware with a loaded sepolicy and you flash SuperSU, what happens? It passes the system check since that takes place first and installs as system root. Then say you flash it on a firmware without that loaded sepolicy? It fails the system check since that takes place first and installs as systemless root. That's what I mean by "default"; perhaps a better word is primary. Seems we are arguing over semantics here. The reason it is said that systemless root is installed by "default" on those firmwares is because it has been determined that they don't have the loaded sepolicy and so will fail the check guaranteed; however, the check for system root takes place first in the binary and will take that route if possible so my initial statement you claimed was wrong is correct. If you want to continue arguing with me, my PM is always open. I will continue to say what I have been saying and I am sure you will too. I think it's best to get back on topic.
[SuperSU] MrKaon:
AdAway working with no problems, Nexus 6p system less root stock.
[SuperSU] grep_i:
You are right because systemless is default you have to check for other things before the default kicks in, if you do it afterwards the default already has done it's work thats why this check was implemented in this version and is mentioned in the change log, it was requested by people using systemmode roms in in most cases it was about CM roms.

You are also right that we will never come to an agreement about this just purely as you states that this is about semantics but clearly it is not if you were right I would already admitted it but there is nothing you told me that proves me otherwise, in my eyes everything you say does still support my claim.

You are a clever man but we do not need to PM about this as it will not change each other views as you mentioned earlier.
[SuperSU] pkelly517:
You forgot the 'echo' the command.