yashsingh1/xdaforums huggingface dataset:
[SuperSU] nathanchance:
It's because SuperSU is no longer running in compatibility mode (Chainfire made a post on it a little while ago). Either switch to a file manager that doesn't have a hard coded su path (recommended) or type echo "BINDSYSTEMXBIN=true" >> /data/.supersu into a terminal editor and reflash SuperSU then let the developer know to fix their app.
[SuperSU] Dudebowski:
Some folks in the g3 forums are wondering why super su bootloops marshmallow... LG's bootloader self-checking is temperamental to any changes. Black screen and tiny white text saying something like

" secure booting error cause boot certification verify "

Then goes dark and the led flashes intermittent blue and red

* insert krs-1 whoop whoop*

Anyways, this flashable will bump the original back into place, just run it at the end of your twerp script. It's also patch for the overboard stock display's sharpening setting, so two bird one stone, select zero during the AROMA script.

Whatever chainfire is doing with the bootloader, it's apparently unnecessary after his script is completed cuz su is still installed properly after you've bump'dd the bootloader back to normal.

THIS IS FOR LG G3 DEVICES ONLY.

http://xdaforums.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648

[MENTION=631273]Chainfire[/MENTION] , any chance your script could do this process all on its own? Thank you for your continued efforts, you're a legend and a scholar.
[SuperSU] tag68:
Is there a chance that flashing SuperSU 2.71 directly using TWRP succeeds on a Moto X Play Android 6.0(1)? Until now I only know of SuperSU 2.62-3 working. Versions 2.65 and 2.68 did not, and older versions also do not. Same with Moto G 2014. Updating to later versions after root succeeds is fine, but flashing 2.68 did prevent booting. I will try it after a backup, but only if chances are that it works.

Did search a bit in this thread, but it is too much, and I didn't find the right search terms I'm afraid.

Does Solid Explorer copy attributes (like time stamps) if you copy or move files internally using the power of root, like Total Commander does?
[SuperSU] DingoBat:
I've just tested and copied a file in Solid Explorer and the timestamps changed to the time it was copied...
[SuperSU] magnamentis:
2.71 was originally made for N-Preview and contains further restrictions as to writing to system and more. you should not use it on MM even though it works for all those who don't use root apps that are not yet updated to N-standards because until now it was possible to work around. It's the app devs that have to make their apps compliant more sooner than latet but as long as they don't we have to live with the facts or avoid their apps which in some cases is not an option for me. ( personal preference )

Use 2.68 or 2.65 stable. there is a workaround to get 2.71 up to speed and i use it on my N-Preview on my nexus 6 but only because 2.71 is mandatory to work with N-Preview. on all 6 other devices i'm on 2.68. here are the terminal commands to improve 2.71 compatibility with some apps.

Terminal Commands for Secure Settings in N-Preview and probably other apps to be fixed (write to system) (survives reboots)

mount -o remount,rw /system

touch /sbin/su /system/bin/su /system/xbin/su

mount -o remount,ro /system

or

su

mount -o remount,rw /system

ln -s /su/bin/su /system/bin/su

ln -s /su/bin/su /system/xbin/su

mount -o remount,ro /system

Terminal Commands to allow SELinux Mode Changer to work without reboot into Safe Mode ! (does not survive reboot, not worth it, use an app for MM roms, not worth it on N IMO)

1. stop logd

2. setenforce 0
[SuperSU] Ch3vr0n:
Not using 2.71 on mm is bollocks, if that was the case then I'm pretty sure flashfire wouldn't be installing it with everroot on mm either. Which for the record, it does.
[SuperSU] Badger50:
Agreed. Using 2.71 on 6p between stock/exposed rom with gravity box, and on AICP cm-13 rom. No issues with any of my root appa whatsoever [emoji106]
[SuperSU] Chainfire:
http://xdaforums.com/lg-g2/general/bump-supersu-t3273251

It was the first result when Googling "supersu g3 bump"
[SuperSU] yung40oz84:
How install system mode? I tried the SYSTEMLESS=false>> and then flashed Kylo kernel and it will not boot. Are there any other commands I need to do or just the SYSTEMLESS one? Do I flash kernel or superSU first?
[SuperSU] magnamentis:
you should read carefully and i knew someone would jump. i stated explicitely that:

- it works

- it's some apps that don't (which is a fact)

hence no reason to defend anything just because you're using it and you don't use one of the apps that have issues. and since we're at it, you can read in this thread ( first few pages) as well as in G+ that he himself said exactly that. in perhaps more sophisticated words.

i even provided the workaround which as well you find in CF's G+ community

so stay of my back
[SuperSU] Chainfire:
Compatibility mode is re-enabled by using the BINDSYSTEMXBIN feature. This doesn't require writing to /system.
[SuperSU] suku_patel_22:
Just delete the file you echoed it to
[SuperSU] Erik Rye:
Wait, nevermind, i see now that you aren't talking about N preview. Sorry
[SuperSU] fessa:
I see the issue was mentioned before, but not sure whether it was fixed or not. If it wasn't - is it an issue with ROM or with SuperSU?

I'm flashing ROM from http://xdaforums.com/galaxy-s4/i9505-orig-develop/jdcteam-android-source-project-mra58v-t3251663/

and getting:

***
Boot image patcher
***
-- Finding boot image
--- Boot image: /dev/block/mmcblk0p20
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting

I tried 2.68, 2.70 versions - the same result. 2.52 works fine.

phone: Galaxy S4 (I337).
[SuperSU] magnamentis:
assuming that noone is using all root apps in existence i ask you to try the following 2 things and report back if you can make it work without the 2 scripts i posted:

a) install tasker on N-Preview install secure settings and try to activate system+ if it works without the scipt i was wrong, for me it did not work out of the box but i'm ready to learn

b) install SELinux Mode Changer or try to perform any other method to set Setenforce=0 in N-Preview if it works without "stop logd" i was wrong it did not work for me without that scipt, it was immediately booting into save mode, while with terminal command "stop logd" it worked but did not survive a reboot.

there are other apps with similar problems and again i repeat, i blame the apps not SSU 2.71, nevertheless in several of the 19 threads i'm following I met with users who had various similar issues within MM and the issues got resolved by reverting to SSU 2.68. Of course i cannot tell if they did something else wrong, i just share what i was reading and how it got resolved in those cases and a few own observations

those who don't use an app that misbehaves ( the app to stress it once more ) cannot confirm anything and hence should not reply in a condescending manner but simply accept that others don't invent issues and perhaps simply mentioned that they don't have any issues.

to make sure there is no misunderstanding, i tried that out about 4 days ago, if anything has changed in the mean time i was wrong, if not, test it and confirm or deny, if only for correctness after IMO prematurely confirming that others are making up things.

Secure settings is a very important tasker plugin that does about 15 jobs for my use case and SELinux permissive is needed for some apps to work because of the same reason, the app developers did not bring the apps up to standard yet, probably because until now it was so easy to circumvent the problem, some roms even come with a permissive switch built in. Nevertheless it's a fact that those apps still exist and some of them are either unique or very useful.

i never said anything else than that and as a conclusion if someone reports issues that hint to such circumstances i recommend to revert back to SSU2.68 i cannot see any reason in such a recommendation, well meant BTW, to be a trigger for replies with a condescending undertone.

EDIT: one thing that 2.71 definitely resolved in N-Preview is the error message in TitaniumBackup, that works flawlessly now, probably due to the re-enabled compatibility mode
[SuperSU] Fen-X:
I already posted my feedback but i can read post saying the problem persist. For me i m on an oppo find 7s x9076 with omnirom 6.0.1 and supersu 2.71 and the solution in page 550 (bindsystemxbind) works great. Hope this help.
[SuperSU] Mad at my Cat:
Hey guys, I'm having a lot of problems and need your help. Here is my original post, they told me to take it here instead. http://xdaforums.com/showpost.php?p=66446330&postcount=4896

I have an S4 Galaxy, I545VRUGOF1 (OF1) that I've tried nearly every method to SuperSu it. Kingroot works, but SuperSuMe and usb debugging methods do not remove Kingroot and install SuperSu to the point where I can update the binary. I've been staring at a screen that says KingRoot v4.8.5 is installed with SuperSuMe (v9.3.8) sitting there at Processing, please wait... for around 20 minutes now.

I've tried flashing the OC1 kernel and trying MobileMe OneClickRoot, but my phone reboots half way and foils it.

I've tried KingRoot and then every form of SuperSu.

No matter what, it will not update the SuperSu binary. I've heard of people manually changing filesystem permissions (specifically the xbin folder with all of the su tools inside) but it will not let me change them, despite having root from KingRoot.

I've tried many factory restores, ODIN kernel restores, and I'm at my wits end. I've jailbroken every device I've ever owned and have never had such a dirty roadblock.

How do I update the SuperSu binary without fail?
[SuperSU] Erik Rye:
Odin back to stock firmware, everything, not just kernel? I would think that would remove Kingroot. Then start all over. Good luck. Here's another thread about doing just that if you haven't already checked it: http://xdaforums.com/showthread.php?t=2265477
[SuperSU] Mad at my Cat:
Yeah :( I'm starting to think something Verizon-related updated and I cannot have a custom rom anymore. I just did a factory reset, a full I545VRUGOF1_I545VZWGOF1_VZW flash, did not enter anything for wifi and mobile data is not in use until I set in APN options. I only turned on debugging before rebooting. Flashed the OC1 kernel, went into the phone and immediately attempted MobileGo auto-root. It rebooted half way... thus failing again.

I can do the same procedure but with KingRoot version 4.1, 4.5, or 4.8 instead of MobileGo and SuperSume nor SuperSu will not update the binary. I've tried this multiple times with multiple SuperSume versions, and the newer version of SuperSu along with one older one somebody with my phone has reported was working.

Without SuperSu, I don't think I can run Flashfire, can I? Is the dream dead for me at the moment guys?

Edit: I should mention that SuperSu installs, just the binary will not update. I can attempt Flashfire exactly as instructions are telling me, but it will fail and pretty much just factory reset the phone.
[SuperSU] Erik Rye:
I think trying to root with mobilego and kingroot is the issue. Forget about both. After you odin the stock firmware and boot up the phone, use chainfire's autoroot: http://xdaforums.com/showthread.php?t=1980683

And here's the link to chainfire's flashfire app (replaces mobile odin): http://xdaforums.com/general/paid-software/flashfire-t3075433
[SuperSU] Mad at my Cat:
I'm ... kind of shocked at the moment. I was just pouting, trying the same thing I have been doing over and over like a mad man. I mean, expecting different results from the same thing makes you crazy, doesn't it?

MobileGo actually installed SuperSu and updated the binary after another series of tries...

I'm going to try out Flashfire and I'll keep you updated.

I just... don't even...
[SuperSU] Erik Rye:
Dont know from experience but have read about kangoroot also installing bad stuff so I am skeptical about other root apps not from CF. You may get root, or some form of it from these apps, but what else they may install and issues in a few days or weeks may show up.

Do you have custom recovery installed?
[SuperSU] Mad at my Cat:
...Lol, I was just put back into stock ROM. It looks like although SuperSu finally worked, Flashfire failed on me for whatever reason.

I'll give CF a shot.

Edit: Or not, I don't see compatibility for my device with that.

Well, MobileGo is actually successful now. I just installed SuperSu again and it stayed. I'm just going to debloat it and wait for Flashfire to mature.
[SuperSU] Erik Rye:
If/when you get issues again and have to odin back to stock again, install Twrp:

http://www.xda-developers.com/how-to-install-twrp/

And then flash SuperSu in recovery: http://www.xda-developers.com/how-to-install-twrp/
[SuperSU] kucingbaik2:
pls..help me

how to add program on super su list

i didnt find option to add
[SuperSU] Wyneg:
When you use an app what needs root, request is done, don't need to add apps ;)

Just open the app!
[SuperSU] lukaaa477:
where to download 2.52? later doesnt work for me
[SuperSU] LoverBoy2415:
Download it from here :) ..

https://download.chainfire.eu/743/supersu
[SuperSU] Ja_som:
Deleted...

[MENTION=6794596]LoverBoy2415[/MENTION] was faster :)
[SuperSU] LoverBoy2415:
:D Mate ;) .. [MENTION=5201515]Ja_som[/MENTION] ..
[SuperSU] Mad at my Cat:
I wish! My bootloader is locked.
[SuperSU] Alxoom33:
Go to developer options and toggle unlock bootloader. Then you are unlocked. Very easy on all NEXUS devices.
[SuperSU] creeve4:
:confused::confused::eek::confused:
[SuperSU] Ja_som:
Wrong, OEM unlock option in developer settings only allows you to unlock bootloader, after that you need to do it via fastboot command...
[SuperSU] grep_i:
OEM unlock instructions for Nexus devices

When phone is on and connected to a PC with USB cable type from a terminal

adb reboot-bootloader

when in bootloader mode

Type

fastboot oem unlock

This will wipe your phone so make sure you make nandroid backup
[SuperSU] Ja_som:
Why I get this from you? :confused:
[SuperSU] grep_i:
That was an error
[SuperSU] NLBeev:
To reboot the bootloader with adb ?
[SuperSU] Ja_som:
Deleted...
[SuperSU] NLBeev:
Humorous ! ?
[SuperSU] Pkt_Lnt:
Read his original post.

http://xdaforums.com/showpost.php?p=66452827&postcount=5772

It is a Samsung Galaxy S4 and you are giving bad information to use fastboot!
[SuperSU] mcnamaragio:
Can anyone test if Notifications Off works with this SuperSU update?
[SuperSU] bissa:
does it work with xperia Z2 4.4.4 .167 firmware?
[SuperSU] Srandista:
Hi Chainfire.

SuperSU 2.23 seems to working without any issues for me. And I want to report, that after this update Wakelock Detector starts to working again.
[SuperSU] ajack2001my:
I saw this at Chanfire's Google+ post...
[SuperSU] Wimmme:
2.23 working well on LG G2. SOD's seems to be gone now.

Also tested on CM12 rom for Lg G2, working well too.

And finally working well on Nexus 7 Lollipop too .

Tnx for the efforts and your good idea for 2.23 ;)
[SuperSU] mag01:
With 2.23 beta, some apps that were previously broken now work, for example Autostarts, or App Ops (by Lars Team: com.findsdk.apppermission) Autostart feature - e.g. these that use the pm command that needs to be executed within platform_app or system_app context.

Some apps are still broken though, for example ES File Explorer 3.2.2 (the one they didn't update for Android 5.0 themselves, I know there's an updated 3.2.3 but that would work anyway) reports that root test failed.
[SuperSU] jediratte:
2.23 working on long live frank by syko + Unleashed 93v2 by defconoi
[SuperSU] vs0587:
SuperSU 2.23 and ES file explorer now 3.2.3 works! Nexus 5 lollipop..... ;)
[SuperSU] dangelkov:
SuperSU_2.23 flashed trough TWRP Latest latest version on nexus 5 with stock Lollipop. Everything working without issues. Titanium backup started working again.
[SuperSU] shayne9512:
Viper4Android still doesn't work without changing SELinux mode to Permissive in the App. :crying:
[SuperSU] ragz:
Works with supersu 2.23,on s5, power amp, I have made no SELinux changes.
[SuperSU] JulGer01:
Anybody else with problems downloading the new beta? I only get a white page...

Gesendet von meinem GT-N7000 mit Tapatalk
[SuperSU] RedSkyRoad:
It's impossible to get TWRP onto these Xperias. Can I still flash it with CWM?
[SuperSU] JulianJenner:
2.23 Beta works good with my LGE-P760 Lollipop by Artas182x, thanks [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] Srandista:
Yes, of course.
[SuperSU] Tinchoska:
If you have a recovery, no matter which one, you are able to flash supersu zip
[SuperSU] simonbigwave:
jus wanna report SuperSU Pro v2.23 on CM 11, 1117nightly installed on GT-i9505 all OK here.
[SuperSU] ciano865:
OK on nexus 4 with Lollipop ROM NX5 AOSP based, flashed .zip with TWRP
[SuperSU] Garbsener:
wakelock works on Nexus5

i've tested wakelock detector on my Nexus 5, didnt worked with 2.22, works with 2.23! great! [MENTION=631273]Chainfire[/MENTION]
[SuperSU] 60nine:
it's just been released on PlayStore...
[SuperSU] grep_i:
It is possible I made a mistake again but I was reacting at post #5786 :silly:
[SuperSU] Erik Rye:
I'd be surprised if nobody has been able to get flashfire to work on the S4. I have a feeling you'll get it all figured out. Good luck!
[SuperSU] Pkt_Lnt:
Samsung devices have bootloaders too, but unlocking them, where possible, is a very different procedure than fastboot.

You must give good advice if you are going to give it. Helping someone brick their phone is not good advice. You should be more careful in what you tell people. That post would have been best if your reply to ask what phone he has if you cannot scroll up the thread to find his original post.
[SuperSU] Alxoom33:
In grep's defense, I instigated the whole exchange with a seemingly innocuous comment about how easy it is to unlock NEXUS devices.
[SuperSU] grep_i:
You're right I only had Nexus devices even my Samsung was a Nexus device and could be unlocked with fastboot. But frankly it's true I don't know about other models how to do it.

But as strong as you seem to come on my advice which I gave on Nexus devices. I don't see the solution coming from you too.

Please come up with the solution instead of flaming other people for not having it right instead. [emoji4]

Thanks in advance
[SuperSU] Pkt_Lnt:
I'm not flaming anyone, I was very civil in my posts suggesting that no advice is better than bad advice. Think of how this thread would be if Chainfire answered the way some here do, with no regard for accuracy?

I did not post a solution for him, since I do not know what that solution might be. Better to keep your mouth shut than open it with bad advice. :D

SuperSU is a very powerful and potentially harmful tool if misused, so I think that good advice is especially important in this thread.
[SuperSU] grep_i:
Can't argue with that and I do think the same, if you were not flaming me than I apologise for thinking that.

My advice was not bad it was aimed at Nexus devices I changed the post to include it so no one could think something else.
[SuperSU] ipdev:
This may help for Samsung devices.

(Sorry if this link has been posted before. I only skim this thread. Haven't run into too many su issues.)

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

Sent from my SM-T330

Running 2.71 on everything (Except one.)
[SuperSU] matrixex:
Hi sir sorry to disturb you but i have a problem with your supersu, SUPER SU DOESN'T WORKS WITH AOSP BASED ROMS SIR ANY IDEA/HELP WILL BE APPRECIATED. (others pls don't reply if you are not a DEV,please)

DEVICE CONFIGURATION

Model - Sony Xperia M

OS : AOSP MARSHMALLOW. 16-7-2016(update)

SElinux Status: ENFORCING (may be this is the reason for not working)

PROBLEM OCCURRED : "No super SU BINARY INSTALLED "

SU VERSION TESTED:

BETA-SuperSU-v2.71-20160331103524.zip

UPDATE-SuperSU-v2.02.zip

Old versions like 1.39~

ANY INFO YOU NEED PLEASE ASK
[SuperSU] fmc000:
I'm not the dev but I think at least you should write which method you tried for installing the app. Forget the older version, they won't work with MM but the 2.71 definitely works on AOSP-based ROMS.

And it works perfectly with selinux in enforcing mode, so that shouldn't be the cause of the failures.
[SuperSU] jaygod611:
Just wanted to ask, I flashed the file via TWRP but it is not installing the app after a reboot. Any ideas would be appreciated.

Thanks!
[SuperSU] dechronic:
There is a script located at /sbin/launch_daemonsu.sh that is run at the first boot to put everything in place. See if that is there and if not, SuperSU is not installing correctly from TWRP. Look for errors in the install log.

If the file is there try running it manually from a terminal and see if the app installs.

To run it type the following and tap the "Return"/"Enter" touch key:

/sbin/launch_daemonsu.sh
[SuperSU] drewski_1:
Maybe someday logs? Recovery from when you flash SuperSu & in Android when you get the no binaries message
[SuperSU] dechronic:
You should be using SuperSU 2.65 or higher for Marshmallow.

What are you using to install SuperSU?

Does it give any errors during installation?

If not, why do you think the SU binary is not installed?

After installation and provided a back up was made of the kernel to /data/stock_boot_?????????.img.gz the kernel is modified as necessary and for systemless an ext4 image is placed at either /data/su.img or /cache/su.img and mounted on the initial boot to the folder /su with the binary being installed at /su/bin/su via a script run from /sbin/launch_daemonsu.sh
[SuperSU] jaygod611:
Thanks! I just checked and the file is not there, what would I do next? Not really sure where to get the log as well.. :(

EDIT: I flashed a new kernel and this time, supersu v2.71 was installed. However, I do not see anything on the sbin folder, is this normal?