yashsingh1/xdaforums huggingface dataset:
[SuperSU] LoverBoy2415:
Thanks [MENTION=5811514]Androidwarrior[/MENTION] :) ..

---------- Post added at 09:47 PM ---------- Previous post was at 09:44 PM ----------

Anyone using 2.70 in lollipop ? ..
[SuperSU] cyrusct82:
Yes me.

Working great on HTC ONE M7 5.0.2
[SuperSU] LoverBoy2415:
Wow...flashed via Recovery or Updated the Binaries Via APK ?? ..
[SuperSU] cyrusct82:
Via recovery.
[SuperSU] LoverBoy2415:
Thanks [MENTION=2871913]cyrusct82[/MENTION] .. I'll flash then :) ..using CM12.1 ...

---------- Post added at 10:29 PM ---------- Previous post was at 10:28 PM ----------

Thanks [MENTION=2871913]cyrusct82[/MENTION] .. I'll flash then :) ..using CM12.1 ...
[SuperSU] belek1979:
After restore twrp backup should I flash again SuperSU 2.68? I had systemless root before I made backup. I'm not sure if TWRP backups systemless root
[SuperSU] nathanchance:
You don't have to since the boot image should still be patched but if you notice it isn't, reflash SuperSU.
[SuperSU] belek1979:
I didn't flash SuperSU after I restored backup (with SuerSU 2.68) and everything is OK.
[SuperSU] LoverBoy2415:
2.70 working flawlessly ;) ..
[SuperSU] zishukkc:
if your rom is pre-rooted then simply install SuperSU from playstore,give it root permission then update binaries as it asks & it will work fine ...
[SuperSU] Wyneg:
You only must install SuperSu systemless over CM13 fresh install (without other versions of SuperSU installed). Flash it through recovery and enjoy it ;)
[SuperSU] Wyneg:
What recovery (and version of) are you using?
[SuperSU] Wyneg:
you try to install always from recovery, just that, not necessary install zip and after apk.

Remember this is beta, not available from playstore (playstore version is system mode, not systemless)

PS: Uninstall super su (full unroot from options), and install zip in recovery and you get root ;) (zip contains app inside!!!!)
[SuperSU] arturox:
I have a Moto X Force with TWRP v3.0 for Kinzie installed and tried to root my phone but every time I flash the SuperSU.zip package and after the phone reboots it gets freeze on the boot logo (where the powered by Android words are), first I tried the stable version of SuperSU v2.65, after the freeze I follow this manual to go back to stock, then I tried the experiment systemless version v2.67 but I get the same error. Please any help?
[SuperSU] nicorvienne:
Hi, take first BETA-SuperSU-v2.62-3-20151211162651 and after that update SU 2.65
[SuperSU] rabiny:
I have the same problem, I dump the content of my boot partition (/dev/block/mmcblk0p20) using dd,

and checked it with `file boot.img` to see if it is compress and got

boot.img: Android bootimg, kernel, page size: 2048, cmdline (androidboot.hardware=qcom user_debug=31 zcache msm_rtb.filter=0)

so i guess it's not, but what can i do to install supersu on my device (Galaxy S4/AT&T w/ TWRP 3.0) ?

P.S - my recovery log can be found here - http://paste.fedoraproject.org/344080/45872863/raw/
[SuperSU] egingell:
The SuperSU zip (2.65) didn't even try systemless on my Sprint Galaxy S4 and, therefore, left the boot image alone. This was with a fresh official Touchwiz Lollipop 5.0.1 on it.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Snowby123:
For about a week now I have been having problems with this app. I have tried both 2.65 and 2.68. Every time I get a prompt to grant or deny root access to an app, none of the buttons show up on the popup. Therefore I cannot grant root access. This problem has shown up for Xposed installer, ES File Explorer, and Titanium backup. What is odd is I have this problem on my tablets but not my phone. Any ideas on what could be causing the problems? I would post a screenshot, but if I try, the XDA app crashes.
[SuperSU] rabiny:
Sorry can you explain :eek:
[SuperSU] egingell:
Explain what? I updated to stock, official, unrooted lollipop and flashed TWRP then SuperSU 2.65 on my SGS4 and it installed to the system. In other words, it did not modify the boot image. The very same SuperSU zip modified the boot image on my SGS5 to do systemless root.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] WhoNeedszzz:
Set Systemless=true and still installs system

With the latest security patch update (shamu) I reflashed SuperSU with 2.68 and it installed in system mode, completely ignoring the settings in /data/.supersu. I tried going back to 2.67, which had installed properly in Systemless mode previously and it too installs in System mode. I reflashed stock between each attempt to reflash and same result. Why is it picking System mode when I explicitly override it via the official method?

Edit: Removing "SYSTEMLESS=true" from /data/.supersu and it installs Systemless. This makes no sense.
[SuperSU] Flubbad:
Can I use it safely on my International note5?

Which means without tripping my knox counter??
[SuperSU] daniel20sj:
Good afternoon, I have a moto g turbo edition running android marshmallow, I have seen that the method for root in this device, is: flashing a modified recovery (TWRP) and flash "BETA-SuperSU-v2.62-3-20151211162651.zip", my question is: with this method my device passes to have selinux in "permissive" or remain in "enforcing" mode?

Thanks
[SuperSU] nicorvienne:
Selinux will remain in enforcing state! If necessary changing state to permissive take 'SeLinuxChanger app'
[SuperSU] daniel20sj:
Thanks for the prompt response, what happens is that I was a little confused because I found that to avoid changing "enforcing" a "permissive" in the selinux, you had to use a modified boot.img, and the methods to root my device never mention that boot.img

Thanks!
[SuperSU] sreyaz.01:
anyone tried rc 2.70
[SuperSU] Skuggo:
Yes. Works without problems :)
[SuperSU] dragsterman:
After dirty flashing a new ROM build should I re-flash SuperSU in case if it is systemless?
[SuperSU] Alxoom33:
Yes, works great on Android N preview. :)
[SuperSU] fmc000:
On MM too, FWIW.
[SuperSU] tofu:
Encryption bug with superSU above 2.52

Just reporting that latest versions of supersu somehow interfere with encryption process and prevent it. I can only encrypt my phone when I flash SuperSU 2.52 beta - anything above that results in constant boot animation ( the encryption process doesn't start). I have tried this with recently with Slimsaber MM.
[SuperSU] maximumentropy:
Yes.
[SuperSU] TonySuperPony:
Could it be possible to make a addon.d backup script for the patching of the boot image?
[SuperSU] essence25:
Run Root Browser file manager, enter folder .system, try creating a directory there, supersu v2.68beta will show lag then crash(no su binary in app), until reboot. Reinstalled v2.65, no prob. OS 5.1.1, Sammy s2 9.7. Installed via zip twrp.

Sems to have issues displaying the request root dialog in certain apps, where 2.65 does not have this issue.
[SuperSU] belek1979:
Is 2.70 newer version of 2.68 (with N support) or totally new SuperSU just for N? If I don't have N should I update from .68 to .70?
[SuperSU] nathanchance:
I am using 2.70 on Marshmallow without any problems. You can upgrade if you want to but it isn't necessary. I'd check the changelog to see if there is something that you want.
[SuperSU] khalidnoman3:
Where is the link to download 2.70?
[SuperSU] Badger50:
Bout here :)

http://www.apkmirror.com/apk/chainf...70-release/supersu-2-70-android-apk-download/
[SuperSU] Pkt_Lnt:
The Android N preview thread next door.

http://xdaforums.com/apps/supersu/wip-android-n-preview-t3335726
[SuperSU] belek1979:
So "N:" is for new Android and the rest is for MM?
[SuperSU] nathanchance:
Correct.
[SuperSU] Andrew111:
Hello, guys. Please tell me where I can find 2.70 version.

Thanks a lot

Best regards,

Andrew
[SuperSU] belek1979:
OMG, Andrew look around - few posts earlier
[SuperSU] LoverBoy2415:
Click this official thread by [MENTION=631273]Chainfire[/MENTION] .. And Download v2.70 :) ..

http://xdaforums.com/apps/supersu/wip-android-n-preview-t3335726
[SuperSU] mielletseed:
Using 2.68 I have still a problem on TouchWiz 5.11 (S5 Mini G800H). In systemless mode I don't get the root grant dialog when apps requesting root access. Last time I did the following: first I installed superSU in systemless mode and afterward in system mode (without the systemless mode the permissions were not patched and the system wouldn't boot). Are there any hints how to get the root grant dialog working?
[SuperSU] venkatsiddhartha:
I have recently rooted my Samsung galaxy s5 SM G900H with cf autoroot via ODIN. . .I got super su 2.68 with that. . .for the first 3 too 4 days every thing was OK. . but recently it kept on asking for binary updates . .. please help me. . . I could not install any recovery for my phone. it says some mount issues. .I don't know what might be the reasons for that. . .can I g

downgrade my super su version 2.68 to super su version 265 (stable version). . .
[SuperSU] Andrew111:
Thanks a lot. Probably I have lost my eyes.))
[SuperSU] LoverBoy2415:
[emoji1] ;) ... [MENTION=373381]Andrew111[/MENTION] ...
[SuperSU] Alxoom33:
[emoji102]

There you go!
[SuperSU] tsadev:
[MENTION=631273]Chainfire[/MENTION] is there a way to bind to /system/app & /system/priv-app like you've done with xbin? I suppose I could always do the lengthy way of doing it myself but I figured that'd be nice for app developers to work with systemless installs. Obviously you'd have to make the SU mount writable/create another writable mount pointing to a system/app etc disc image but it might make things easier on the devs to have something universal.
[SuperSU] osm0sis:
Yes, but you'd have to duplicate everything in those directories, which would be huge.
[SuperSU] Chainfire:
v2.71 BETA released

v2.71 BETA has been released. See the changelogs. N Preview changes have been merged with the normal BETA releases.
[SuperSU] LoverBoy2415:
Awesome [emoji106] [emoji1] ....
[SuperSU] edgarf28:
With both 2.70 & 2.71 I'm seeing this message from SocketListener every 5 seconds in my logcat.

With supersu 2.68 I don't see this message at all.

I have an G920F, using the latest MM stock firmware.
[SuperSU] Tinchoska:
Guys I can't get super Su working on cm 13 (my phone a Moto x2 victara)

Enviado desde mi XT1095 mediante Tapatalk
[SuperSU] MrKaon:
As always no problem with Nexus .

Thanks
[SuperSU] Skuggo:
Works perfect on my note 4 with cm13.
[SuperSU] dahawthorne:
Installed via TWRP 3.0.0.1 on Nexus 6 directly over v2.70.

ROM MMB29V.

No apparent problems. All looking good.
[SuperSU] bournaze:
Upgrading from 2.68 to 2.71 fixes my problem with Titanium Backup (couldn't obtain root access when namespace separation was enabled ! )

Thanks a lot for your brilliant work ?
[SuperSU] spainter:
Upgraded from 2.70 to 2.71 on Nexus 6 and 2013 Nexus 7 via FlashFire no problems at all. Everything working great.

Thank you Chainfire for your outstanding work.
[SuperSU] LoverBoy2415:
Updated to v2.71 .. On my CM12.1 ..no problems at all..All is Well?... Another Awesomeness by [MENTION=631273]Chainfire[/MENTION] one of the Gods of Devs Community ... ???...
[SuperSU] TsarFlow:
Still rocking ! Nexus 6 and 5 on both PureNexus Marshmallow, brilliant as always ! :)

Envoyé de mon Nexus 6 en utilisant Tapatalk
[SuperSU] TangYang:
not work on HTC One M8 Eye

I installed SuperSU 2.71 but TWRP still required for installing SuperSU.

I can't modify anything in folder system!!!
[SuperSU] nathanchance:
Have you updated TWRP to 3.x? That should have been fixed.
[SuperSU] brinsleyparagao:
!!! Failure on Boot Image Patcher !!!

Error ON >>> /dev/block/mmcblk0p33

Moto X 2014

CM13 - 31/03

TWRP v3 + Unlcoked Bootloader
[SuperSU] monsterkruemel:
Works perfectly on my Nexus 6p with CM13.

You,re awesome! :good:

Thank you!
[SuperSU] koko115:
After instal 2.71 on 2.70 es explorer dont have root, other apps ok..... Galaxy S6 Hacker kernel System Mode.
[SuperSU] Alxoom33:
No problems on Nexus 6 running Android N. :)
[SuperSU] funfun99999:
2.71 doesn't work on lollipop ROM
[SuperSU] eKeith:
Working on mine!

Updated from 2.68 beta

Moto X 2014 PE

Android 6.0 24.11-18

Unlocked bootloader

TWRP v.3

Note that I also previously flashed BusyBox 2.41 from Osmosis' thread.
[SuperSU] niebloomj:
Bad zip for some reason on twrp 3.0.1. Can't flash. Latest marshmallow.
[SuperSU] FlyingHorseGA:
Working great on Lollipop for me :silly: Upgraded from 2.68 via TWRP 3.0.0-0.
[SuperSU] TangYang:
I can't find TWRP 3.x for M8 Eye, but TWRP 2.8.0.3 :(
[SuperSU] j1gga84:
I installed 2.71 over 2.70 on my galaxy tab s running AICP10 (5.1.1) in TWRP recovery.

I still have root but I cannot get root with trimmer (fstrim) app anymore.

I had the same on my smartphone running 6.0.1 Resurrection Remix. Here I had to reflash my ROM..

Any suggestions?

Regards

Sent from my SM-G900F using german Tapatalk 4
[SuperSU] H4X0R46:
Dumb question inbound. Is the newest SuperSU supposed to support all Android versions? Or is it much more complicated than that? Thanks! Like. would this successfully root ICS, KK, JB etc.?
[SuperSU] funfun99999:
Doesn’t work for me on galaxy note edge n915fy official rom. After flashing it via TWRP 3 all the apps don’t have root any more.
[SuperSU] Herbie_2005:
It is exactly the same for me on my Samsung Galaxy Note 10.1 (2014). Whereas Super-Su 2.65 works flawlessly, I cannot make Super-Su 2.68 or 2.70 or 2.71 work.
[SuperSU] Chainfire:
If you don't have root in apps, try getting Terminal Emulator, run it, enter "su" (without the quotes) and see if you get the # symbol instead of the $ symbol.

If that works, you have old ****ty apps that haven't been properly updated in ages. Since the N Preview releases, SuperSU is no longer running in compatibility mode by default

Entering the following in a rooted shell (Terminal Emulator, after su, with # symbol, will work), then reflashing SuperSU, will re-enable compatibility mode:

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

If this works, please complain to the authors of your root apps that they should update their apps. If that doesn't work, something else is going wrong, and we need to dig deeper.
[SuperSU] mielletseed:
On my Galaxy S5 Mini G800H the only way I found was first to install SuperSU systemless (for patching the boot image) and the install it again in system mode.

System mode only won't boot (since the boot image is not patched) and in systemless mode I got no root grant dialogue (and sometimes the SuperSU app told me there were no root binaries installed).

But now it works flawless.
[SuperSU] relevant_placeholder:
[MENTION=631273]Chainfire[/MENTION], how about fingerprint auth option in Pro, possible?
[SuperSU] mielletseed:
[MENTION=631273]Chainfire[/MENTION]: is it known that it doesn't work on Samsung TouchWiz lollipop? Do you need logs to look after this issue? What would be helpful?
[SuperSU] :
Ignore this
[SuperSU] usafle:
Hello all. Just installed SuperSU v2.71 and the binary refuses to update. I'm coming from whatever the previous version was. I grabbed the .apk from Apkmirror.com

Im running a Nexus 6 / 6.01 March security level.

I've tried to install an older version on top of this SU 2.71 but it won't let me. I'm afraid to just remove the app at this point.

I've rebooted multiple times, still with the same result, no joy.

TIA
[SuperSU] shawek:
Info for 5.1 users...updated to 2.71 beta.zip,everything is working fine(TB working,all root apps working...)

Sent from my HTC One
[SuperSU] LoverBoy2415:
Flash the v2.71 Zip instead of Updating the Binary via APK [MENTION=3159413]usafle[/MENTION] ...
[SuperSU] usafle:
That fixed it. Just saw the .apk on Apkmirror, had no idea there was an entirely new ZIP file. Thanks!!!!
[SuperSU] LoverBoy2415:
Welcome ;) ? ...

Better Subscribe to Supersu Beta & Stable threads by [MENTION=631273]Chainfire[/MENTION] for New Version updates ;) instead of Seeing other download source [MENTION=3159413]usafle[/MENTION] .. All third party Sites will be having APK only ,No Zips :) ..
[SuperSU] francescorm:
In Galaxy s7 edge 935F work perfectly !!.. Thanks very much for your hard work... Are you great master!

Inviato dal mio 935F
[SuperSU] LoverBoy2415:
He is ..[emoji111] [emoji6] ...
[SuperSU] alex00006:
Me too also update apk su 2.71 and binary but

After few minute..its failed and reboot

again Failed..

N920C

MM Rom

Custom Rom RSR

before install su 2.71 i have su 2.68
[SuperSU] wilbigdaddy2000:
Same here. Running HTC desire 626s Lollipop sense 7.

DWil's Magic Carpet
[SuperSU] sadab:
CM13

SuperSU zip doesn't work on my Xperia Sp(CM13). I flashed the latest stable,beta version . But the result is negative . I know cm13 is pre-rooted but the native root doesn't work properly. :confused:
[SuperSU] wurstherpes:
Work on HTC One M8s, Android 5.1, CM 12
[SuperSU] LoverBoy2415:
Flashed the v2.71 Zip Nah ? ..Now Everything Fine right? [MENTION=5147100]alex00006[/MENTION] ...
[SuperSU] Fen-X:
I have an oppo find 7s with omni rom 6.0.1 (last nightly), supersu pro version, and total recall premium version.

For me everything works perfectly. which is very nice and very fluid. However, I have one problem with a call recording applicationnamed TOTAL RECALL/ CALL RECORDER : https://play.google.com/store/apps/details?id=com.killermobile.totalrecall&hl=fr

Until the 2.68 version of supersu, everything works. I have not tried the 2.69 release. But with 2.70 and 2.71 versions, the application does not work or bad.

Let me explain.

In the application settings there must be an option to install a patch specific to my phone to unlock the root recording. As I said, until the 2.68 version of supersu this option appears and once applied, the application works fine. But since 2.70 version and upper, this option does not appear and the root recording method option is grayed out while with the 2.68 version and less everything is correct. Here are some screens in 2.68 and 2.71 versions so that it is more understanding.

Sorry for my bad English. If something is incomprehensible, let me know and I'll try to rephrase.

What I want to know is if it is able to prblème super or the recording app?

Except this app, all other apps work fine (power nap, greenify etc...

Thanks for your help
[SuperSU] nathanchance:
Did you read the previous page? Always a good idea before making a new post. You may need to use this process to get it working.
[SuperSU] tsadev:
That makes sense, though if we had UnionFS support in the kernel would it be possible? I'm not entirely an expert in Linux but if I understand it correctly, UnionFS is simply an overlay of sorts that maps two directories on different devices (I.e. loop devices, not physical) to one combined directory.
[SuperSU] osm0sis:
Yup. If the kernel supports UnionFS then you could do that as an add-on of sorts. :good:
[SuperSU] Fen-X:
thank you for your remarks because although legitimate , you managed to stay very courteous. To answer your question , yes , I read but I misunderstood because as I have root access to all other applications I thought it was not the solution that shall regulate my problem . I have read extensively the solution and will test it on.

Thank you a thousand times to you.
[SuperSU] jwds1978:
I'm using SuperSU v2.71 on my Note 3 (SM-N900W8) with a stock 5.0 ROM and haven't had any real issues with it.
[SuperSU] rgavioli:
Not yet on the HTC M9

Just tried 2.71 on a HTC M9, Marshmallow and Sense 7.

Unfortunately, it doesn't work: Infinite bootloop.

The last version that works is the 2.65.

Thanks, anyway! I'll keep trying.:good:
[SuperSU] j1gga84:
I just want to inform you that this worked, trimmer has root again :)

I want to get in contact with the developer of that app because it was not updated a while, you are totally right, so what does he has to update/what should I communicate to them to fix that problem?

Many thanks an regards

Sent from my SM-G900F using german Tapatalk 4
[SuperSU] Wickii:
Secure Settings Pro seems to work again, ES File Explorer Pro sadly not. Not possible to enable Root within the App (Popup with "Oops, that's not possible...". Any idea what could fix this? App Problem?
[SuperSU] Pkt_Lnt:
Read the last line that you quoted. ;)
[SuperSU] mielletseed:
Yes, you are on 5.0. I guess it installed in system mode and there was no need to patch SELinux policies of the boot image since these came with 5.1 on TouchWiz ROMs. But I can be wrong.

Are you rooted in systemless mode or in system mode?
[SuperSU] Wickii:
I did.
[SuperSU] Pkt_Lnt:
For some reason the logcat does not show. :confused:

And when was ES File Explorer last updated?
[SuperSU] Wickii:
4 weeks ago.
[SuperSU] egingell:
The latest update to ES Explorer was Wednesday, March 29th.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Pkt_Lnt:
SE File Explorer problems are mentioned often in this thread. It is probably hard coded for su in /system. No one has posted logs, so nothing can be done to help.
[SuperSU] corkiejp:
Pro version last updated 7 March 2016

[MENTION=2367829]Wickii[/MENTION] What device are you using?

Just tested with Nexus 9, after

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

And reflashing SuperSU, ES Explorer (v4.0.4.9 not Pro Version) now allows root access.

Check that /data/.supersu is present and contents correct.

Try Flashing SuperSU again from TWRP.
[SuperSU] spainter:
I have had a lot of problem with ES File Explorer since they garbaged it up. Not related to root. I finally just uninstalled it. I use Root Explorer, FX, or Solid Explorer. Just my two cents worth.

Nexus 6 and Nexus 7 V2, Stock MM 6.01.
[SuperSU] Dnorris55:
ES File Explorer Pro working OK on my Samsung Tab S running MM (aosp-eng.ubuntu.20160317.214308).

SuperSU 2.71, TWRP 3.0.0.0-1
[SuperSU] funfun99999:
Using Terminal Emulator and enter "su" I don’t get the # symbol

galaxy note edge n915fy android 5.1.1
[SuperSU] drewski_1:
Maybe not a bad thing?

https://forums.oneplus.net/threads/security-es-file-explorer-privacy-concerns.305336/

Sent from my Moto X
[SuperSU] egingell:
I use the free version of ES Explorer on both an SGS4 and an SGS5 and, based solely on the fact that the version numbers for Free and Pro are vastly different (Pro is 1.x while Free is 4.x), I'd say Pro is just a activation app, but it's not mentioned in the description and I could be wrong.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Wickii:
Seems legit :)

Sorry, but wrong. Pro is a standalone App. :)

Nevermind, kicked ES and testing FX and Solid atm. Thanks guys. :)
[SuperSU] Andy3366:
SuperSU broken for Bq A4.5, after 2.68

The A4.5 runs MM 6.0 and if i install (via TWRP 3) anything after 2.68 the device lands in a infinite boot loop. The only way to solve this is to restore the org. boot.img via flash and reinstall the 2.68 version.
[SuperSU] mi3user:
i want to root MIUI 6.3.17(Marshmallow update ) Xiaomi Mi3.

Which file should i flash ?
[SuperSU] todivefor:
Saw this code was redone in 2.70. I just tried this in 2.71. Same result. No big deal for me. Was hoping I could get Android Pay to work. No deal! Galaxy S6 (SM-G920P) , 6.0.1 stock except for root and Xposed.
[SuperSU] drewski_1:
Xposed modifies /system regardless of the Root method

There's a thread for Android Pay

http://xdaforums.com/showthread.php?t=3298115
[SuperSU] Alxoom33:
Android Pay will not work with root, unless you use updated Systemless Root. Can't use Xposed with Android Pay, no way!
[SuperSU] todivefor:
Thank you for the AP thread. Might have to read through the 45 pages to see where it leads. I'll deal with AP later, if at all. About SU. Is the fact that I installed Xposed which modified system the reason that disabling superuser is not working? ie, once you modify system SU disable will break.
[SuperSU] Mariner_1712:
Is anyone else unable to update the binary after installing the 2.71 or 2.70 betas?
[SuperSU] casouzaj:
If you installed the Beta SuperSU zip in recovery, its binaries are already there! There's no need to update them!
[SuperSU] Alxoom33:
Yes, installing Xposed will prevent your use of Android Pay. However, you also need to install Super Su as Systemless, which requires an adb command in TWRP. You can google the details or read in the Ap and SuperSu beta thread.
[SuperSU] Mariner_1712:
The problem is that the dialog won't go away permanently. The app seems to function fine and nothing else is acting out of the ordinary, I just don't understand what's causing the binary dialog to keep coming back.