yashsingh1/xdaforums huggingface dataset:
[SuperSU] a1exus:
you were not suppose to update binary ..

that's probably because your bootloader still unlocked...
[SuperSU] Alxoom33:
AP only works with properly configured Systemless Root.

Website signature
[SuperSU] agentscreech:
And what is the proper way currently?
[SuperSU] Pig Vomit:
Install 2.68 beta, then delete /su/xbin_bind folder. Reboot.

For most people, using CFAutoRoot is easiest way to install 2.68. Otherwise you can install TWRP recovery, then install the 2.68 beta zip.

Use ESFileExplorer or RootExplorer to delete xbin_bind.
[SuperSU] Alxoom33:
You need to first enter the ADB commands in twrp/advanced/terminal... to force Systemless mode.

I don't recall the 2 lines, I always do a Google search. Look for them...:victory:
[SuperSU] shoey63:
Allowing system modifications sets the /system partition to r/w. That's enough to cause android pay to fail. Re flash of stock system is required. You may also need to delete and re add your cards, seeing as they have been detected as being on a compromised operating system.
[SuperSU] Falinor:
so I wouldnt have to reflash system since I set system back to r/o via TWRP the second time?
[SuperSU] shoey63:
I edited my post. Re flash of stock system is now mandatory.
[SuperSU] Falinor:
Darn, ok :(

so i just need to reflash system and then re-flash twrp? or do i have to reflash system, cache, reboot to recovery, wipe system, then reflash twrp and make sure to keep the system r/o?
[SuperSU] Alxoom33:
See my response in the SuperSu thread.
[SuperSU] a1exus:
I just tried my AP and it wouldn't work( is there a way to get it going? I'm on stock rom, root (2.78)
[SuperSU] Alxoom33:
You need to enable the latest Systemless mode WITH SuperSu2.68 . If 2.68 was not set up to be Systemless, AP won't work.
[SuperSU] a1exus:
sorry, i probably should've mentioned it right away, i'm on systemless root (BETA-SuperSU-v2.68-20160228150503.zip)

any advise? please)
[SuperSU] corkiejp:
Did you make these commands before flashing supersu?

If not then delete /su/xbin_bind.
[SuperSU] a1exus:
I did echo commands after SuperSU was already installed, so I guess "/data/.supersu" is for going forward for me), and I also rename "/su/xbin_bind" into "/su/xbin_bind.bak", and I also performed one more step "chmod 751 /su/bin". with all of that I tried adding CC I couldn't do it, I tried using AP at the pharmacy and it did not work(
[SuperSU] corkiejp:
The latest supersu already has chmod 751.

Check the SuperSU app that it is indeed installed systemless.

Edit: Never-mind, If you have the /su/xbin_bind folder, you probably are systemless.
[SuperSU] a1exus:
So what did you guys do different? Why Android Pay works for you and not work for me? What am I missing?
[SuperSU] Alxoom33:
If you did what you said below AP should be working. Did you Reeboot before trying AP?

Also, the order is important. 1st go into TWRP and enter the two ADB commands. They are quoted a couple more posts above.

Then flash SuperSu.2.68.zip. Confirm that it installed as Systemless. Then reflashed the kernel, EX 3.11 works nicely for me. Then Reeboot. AP should be working and Su should be properly configured.

---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------

Perhaps you should get a better phone. Nexus 6 works great! Lol! Just kidding!
[SuperSU] a1exus:
I'm using Huawei Nexus 6p with stock kernel...

Should I reflash entire march update and try to supersu again? I don't know what else to do( Pleeease? anyone) This drives me bananazz)
[SuperSU] Alxoom33:
No, just go into TWRP and redo your Systemless Root correctly.
[SuperSU] a1exus:
Ok:

alexus@mbp:angler $ adb shell
shell@angler:/ $ su
root@angler:/ # cat /data/.supersu
SYSTEMLESS=true
BINDSYSTEMXBIN=false
root@angler:/ # ^D
shell@angler:/ $ ^D
alexus@mbp:angler $

I just reflashed BETA-SuperSU-v2.68-20160228150503.zip again via TWRP, now booting ...
[SuperSU] Agg2ressor:
Systemless and AP

I have systemless mode on at the moment and I can't seem to add cards to my android pay at all. I am also on SuperSU 2.68 as well.
[SuperSU] Darke5tShad0w:
Have you run the safety net checker app? Do you have xposed or any other mods?
[SuperSU] Agg2ressor:
Yes I ran the safety net checker app and came back that CTS profile match = false. No, I do not have any other mods.
[SuperSU] Darke5tShad0w:
Did you run the command to create the xbind folder or delete it after install?

Does your rom pass the safety check when clean flashed?
[SuperSU] Agg2ressor:
The echo commands on TWRP terminal? Yes, I ran those. Also ran the chmod 751 /su/bin. I am on March 8th build of PureNexus, SuperSU v2.68.
[SuperSU] Darke5tShad0w:
Which gapps did you flash when you last cleaned installed?
[SuperSU] Agg2ressor:
Pure Nexus GApps. I followed all the instructions in the post about clean flashing Pure Nexus and getting Android Pay to work as well.
[SuperSU] Darke5tShad0w:
If you followed that guide it should then work.

You haven't installed adaway or used the build.prop editor?

Do your cards work for android pay and is it available in your area?
[SuperSU] Agg2ressor:
Oh wow, adaway kills android pay? I had adaway last time, worked fine.
[SuperSU] Darke5tShad0w:
Installing the regular way yes.

You need to use the systemless install

http://xdaforums.com/showthread.php?t=2190753
[SuperSU] Agg2ressor:
I just disabled ad blocking and uninstalled the regular way, and it still breaks android pay :/
[SuperSU] Darke5tShad0w:
You may need to clean flash again as your /system has been modified (hosts file).
[SuperSU] Agg2ressor:
Is there anyway I can revert it without having to clean flash again?
[SuperSU] Darke5tShad0w:
Not that I'm aware, once it has the modified take I don't think it can be removed.
[SuperSU] Agg2ressor:
Is there a list or something of apps that break the safetynet check?
[SuperSU] Darke5tShad0w:
Not in a quick google search, eg es file explorer doesn't but what you do with it will.

Regular nandroids and keep checking with the app.
[SuperSU] egingell:
Such a list would be impossible to maintain and would never be comprehensive.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] DROITURK182:
Do you have a pin, or pattern, or password set for security? If not Android pay will not work or add cards.
[SuperSU] DROITURK182:
Does anybody that has updated there Nexus phones on the March security update have trouble with safety net checks? Just got a update on my GPE M8 for the March security update, stock ROM not rooted and it won't pass any safety net checks. Me and the M8 community are trying to figure out if Google missed up or HTC.
[SuperSU] luigidk:
No issues on my n6p. Though I am rooted with supersu... Systemless
[SuperSU] ifwillems:
Could you describe all the steps you did to get to the upgrade and have Safetynet working? Which GAPPS did you use?
[SuperSU] markwebb:
FAQ
[SuperSU] ifwillems:
I found these instructions: http://xdaforums.com/showpost.php?p=64645717&postcount=4497
[SuperSU] aergern:
So you are saying if one flashes TWRP as the recovery it breaks AP? I just checked .. SafetyNet check is bright green for me. It was bright green with the adway modded hosts. It was bright green after I had the adway app restore to stock and I just checked it after a reboot and flashing the systemless Adway zip .. still green.

What's up? I'm actually confused.
[SuperSU] egingell:
TWRP doesn't install to system - recovery has its own partition which is separate from everything else. I don't know what he's talking about.

Flashing TWRP trips KNOX just like most anything else, but not SafetyNet.

Eventuality, they'll probably change that because they're really good at ruining things for everybody.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] aergern:
Yeah, I knew about KNOX. I was just confused as to how TWRP was going to screw with AP since it is how you said .. not part of /system/ and while I do think Google is chasing things that will cause folks pain ... I doubt they'll do anything to screw with things like TWRP since it wouldn't make sense. I dunno. My feeling is that either the '16 or '17 Nexus and other phones will be required to have a separate chip to handle what SafetyNet takes care of now much like Apple's approach. When this is chip based then rooting and all that won't matter. Much like when folks jailbreak iPhones and Apple Pay still works .. I think Android Pay will go this direction as well. But this is just my opinion.
[SuperSU] Darke5tShad0w:
We didnt even talk about TWRP.

I was talking about apps modifying the system flag.

But reading back now I read one of his/her posts wrong and went down a path slightly irrelevant (Hung over is no excuse in this game)

But as it turns out for some the fi dialer needs to be flashed when on purenexus.
[SuperSU] aergern:
Post #460

"Fyi Also installing twrp to system also results in this."

Maybe scroll up? I was responding to this. So .. whether it's typed twrp or TWRP ... same thing and why I commented. :rolleyes:
[SuperSU] egingell:
*You* said "twrp". If you weren't talking about TWRP, then why did you say it? Granted, it was a 9-day-old post, but still.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Darke5tShad0w:
I apologize, I did say that, But I was referring to when you first install TWRP and it asks if you want to keep it read only. This was part of the wrong path as it relates to stock rom and another process.

Please disregard my last posts and as egingell it was awhile ago and to another user.

If you have any issues in the future I will try to help and double check all info.

Also you are correct TWRP is the same no matter whether you use caps or not.
[SuperSU] aergern:
No worries. I just wanted to make sure that someone didn't read the twrp thing wrong. :D

All good.
[SuperSU] cmcole101:
I'm experiencing the same issues listed above except Android Pay isn't installed on my phone. My SM-N910C has been on 5.1.1, N910COLB2COJ5, rooted with TWRP Recovery version 2.8.7.0 (and it was a real bugger keeping it from going into a bootloop installing the root), but afterwards my Note 4 ran root without problems...well, except for the fact it would randomly shut-off forcing me to either remove the battery or plug it into a power source before I could reboot it, something that didn't happen until I updated to 5.1.1 and rooted it), and while that has been a thorn in my hindquarters, it hasn't been enough of one to force me to unroot.

My current dilemma is now associated with the latest update, N910COLB2COL1 and trying to root with TWRP 2.8.7.0. I flash twrp-2.8.7.0-treltexx.img.tar with Odin3 v3.10.7, then go into TWRP and Install UPDATE-SuperSU-v265.20151226141550.zip and reboot. Once on the Home screen and everything is loaded, I installed SuperSU Pro and Titanium Backup Pro and begin reloading my apps without the data.

My pickle is root works fine until I use something that require root, then it disappears causing me to reboot into Recovery and Install UPDATE-SuperSU-v265.20151226141550.zip again. I've used v2.46, v2.68, v2.67 and v2.71 and the exact same thing happens as soon as I call upon an app that uses root, then root disappears. Root Checker Pro verifies that I have Root Access right after boot, but then returns no access once I use an app, i.e. AdAway, or BusyBox Pro. AdAway will call for Granting root, do its thing, then I can try to call that same app up again and root access has disappeared.

Currently I'm running TWRP 3.0.0.0 and SuperSU Pro v2.65, and I've tried flashing v2.65 through TWRP and Google Play, and the same results occur, root disappears after one or two uses by an app that needs root.

Has anyone found a fix for this or have a solution already, or even suggestions I can try?

Thanks.

Cole
[SuperSU] Alxoom33:
Unfortunately, I haven't been able to use AP since I started using Android N in early March. Had to revert to MM for a little while when I needed to use my Best Buy Google gift certificate then went right back to N. Much better OS, worth it!
[SuperSU] photolarry:
Seems the latest update to Android Pay causes it to quit working. The NFC seems disabled. Why are they being so ridic about this? I want a rooted phone and want to use AP. Why is this asking so friggen much?
[SuperSU] Pig Vomit:
photolarry, did you just get an update to Android Pay today? I see a new version up on APK Mirror as of today (May 3rd, version 1.3.120831396). Hasn't hit me yet. Appears to be first update since January.
[SuperSU] photolarry:
Yes

Yes the newest is on Play Store. I rolled back and told Play not to auto update. I will figure it out another time.
[SuperSU] JsChiSurf:
FWIW, my Android Pay updated yesterday to version 1.3.120831396, manually applied the May Security update today (Nexus 6P / MTC19T), and Android Pay worked w/o issue @ Trader Joe's today (first attempt since Pay updated).
[SuperSU] photolarry:
Are you rooted and if so which method and version of supersu?
[SuperSU] JsChiSurf:
Certainly. System-less root with SuperSu 2.71 (latest).
[SuperSU] photolarry:
Hmmm...perhaps it was fluke at trader Joe. I'll take update and try later and see if there is an issue and report back. The clerk said the terminal was working with other phones. But maybe Apple. I got my coffee earlier with older version. I'll try later at different merchant. Thanks for input.
[SuperSU] photolarry:
Apparently you are right and I worried for nothing. Worked fine at whole foods. They tried to convince me it was my phone not the terminal at trader Joe [emoji15]
[SuperSU] photolarry:
How to Root and get AP working....just in case

So I just tested this twice to make sure it works (with a custom kernel of your choice) - I tested Despair and Hellscore and works great.

1) Flash boot.img and system.img from the MOD30I (build from Google 5/2/16) and boot normally once

Google MOB30I Image

2) Reflash twrp and reboot into Recovery (3.0.2-0 is the current) : Shamu TWRP Recovery image

3) From recovery flash your chosen kernel (this is not mandatory...you may use stock if you do not want a custom kernel)

4) From recovery flash SuperSU 2.71 as systemless (see SuperSU post for instructions)

5) Reboot

6) Once everything starts up and boot has completed, open a terminal window and type the following commands:

su

cd su

chmod 751 bin

rm -rf xbin_bind

exit

7) Reboot

8) Profit
[SuperSU] FletchF:
This is not necessary with a recent SuperSU. 751 has been the default /su/bin permission since 2.68.
[SuperSU] photolarry:
Ok well it does not harm anything to type it to make sure. I did not look to see this was now default.
[SuperSU] Captain_Throwback:
The remove xbin_bind is also unnecessary with the latest Beta.

So after step 5 it should all be good to go.
[SuperSU] Ingenium13:
The directory on /su? I had to delete it to get it to work, even though I had the setting disabled in the config. It seems SafetyNet checks for that particular folder, even if it's empty and unused.

Sent from my Nexus 6P
[SuperSU] nathanchance:
Starting with SuperSU 2.69, xbin_bind has been disabled by default (see changelog). Everything else you said is correct.
[SuperSU] Ingenium13:
I know it's disabled by default, but on my device at least it still creates the directory on /su. It just doesn't bind it. The mere presence of that directory prevents SafetyNet from passing

Sent from my Nexus 6P
[SuperSU] nathanchance:
The binding is what breaks it, not the presence of that directory. I don't even think that directory should exist if it isn't getting bound but I am not sure since I am not on systemless root right now.
[SuperSU] Ingenium13:
Trust me... it does break it. Try it yourself. I wasn't bound, and even after a fresh reboot SafetyNet failed. It was failing for weeks and I had no idea why (I don't use Pay often so it wasn't a priority). Then I deleted the empty non-bound directory and rebooted, and it passed consistently. I even still had the option set in settings not to bind the directory just in case the default install behavior changed.

Sent from my Nexus 6P
[SuperSU] Captain_Throwback:
But that directly will never get created on a clean flash of the latest SuperSU Beta. It would only exist is there was already an su.img on /data or compatibility mode was enabled via .supersu.
[SuperSU] Ingenium13:
All I know is it wasn't there since I had previously deleted it, I upgraded to the latest SuperSU, and it appeared again, but wasn't being bind mounted.

Sent from my Nexus 6P
[SuperSU] Pig Vomit:
I'm *not* trying to argue.....but installing SuperSU 3.71 using CFAutoRoot on my otherwise stock 6P does not result in xbin_bind being created, it passes SafetyNet, and Android Pay works just fine without any additional modifications.

As far as my concern that the latest Android Pay version stopped working with root.....not a concern. New version of AP was pushed to me today and I just used it, no problem.
[SuperSU] zikronix:
I updated to the latest super su, and have the latest android pay. I dont have an xbin folder in SU and su is set as 751 still fails safey net.
[SuperSU] Nekromantik:
Anyone in the UK got it working with Android Pay app?
[SuperSU] BioT3rm:
Wouldn't Xposed & rootcloak bypass this restriction? here is the link it's quite old now but could still work http://xdaforums.com/showthread.php?p=49351848

I will post back results after installing, rootcloak updated september 2015
[SuperSU] NYLimited:
Sadly, no.
[SuperSU] Alxoom33:
It's alive!!!

Android Pay working again on Android N Preview 3!!!!

Joy. :)

Systemless Root!
[SuperSU] bobby janow:
The question is how did you root? Are you encrypted or decrypted?
[SuperSU] Alxoom33:
Ñexus 6, N3, SuperSu 2.72 Systemless, encrypted..

I didn't think encryption made a difference.
[SuperSU] bobby janow:
Reason I'm asking is that TWRP doesn't work encrypted on N3 so how did you get systemless root working without a custom recovery.
[SuperSU] steviemch:
Android Pay working fine here. Nexus 6P, systemless 2.72, latest Dev preview.

Nexus 6P
[SuperSU] Alxoom33:
TWRP works fine on encrypted N3. I'm not sure where you are getting your information. I am using TWRP 3.02
[SuperSU] bobby janow:
http://xdaforums.com/showpost.php?p=66928574&postcount=588

edit: I flashed cf-autoroot and it gave me systemless 2.74 and AP works.
[SuperSU] drewski_1:
Encryption support in TwRP seems to be device dependant
[SuperSU] Alxoom33:
Works fine with Nexus 6.
[SuperSU] Alxoom33:
Used Android Pay successfully at McDonalds last night. Nexus 6 Running Android N Preview 3, SuperSU 2.72 EX 4.04 Kernel and TWRP 3.0.2 Encrypted.
[SuperSU] smohanv:
Should AP work along with xposed framework.... I tried with unroot, removed xposed using xposed unistaller and then flashed SuperSu 2.74 and then installed AP. Doesn't work. I am on PN latest (05th May) version. Can anyone help please.
[SuperSU] Captain_Throwback:
No. Android Pay will not work with Xposed.
[SuperSU] smohanv:
Thanks for your feeback...
[SuperSU] Alxoom33:
You probably didn't remove all traces of exposed framework. Or you may have installed root in the System Partition. Either will kill AP.

Try reflashing your ROM and make sure you make a Systemless SuperSu instillation. Than add AP.
[SuperSU] Max88888:
Will it work?

I want to now if the following config will work with Google Pay:

Nexus 6P + Disabled Systemless SuperSU

---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------

Which device and android version do you have?
[SuperSU] bobby janow:
I'm running Android N DP4 Nexus 5X. No mods other than root and recently Elemental X kernel flashed via Flashfire.
[SuperSU] Karl Brunton:
I have android pay working on dr ketan m5 rom for N910F.

Not sure if it's the same for all users but I initially set up AP on stock then installed twrp, rooted and flashed custom rom but all is working perfectly.

If it's not too long winded, install stock rom, set up AP, flash custom rom and set up AP again. Your cards will already be there and should be good to go.
[SuperSU] Max88888:
AP works with custom kernel?

Do I understand you correctly? You have AP working with custom kernel?
[SuperSU] Ingenium13:
Yes, it also works fine for me with stock system and ElementalX. I just added a new card to it the other day.

Sent from my Nexus 6P
[SuperSU] Alxoom33:
Been running AP on Nexus 6 rooted with SuperSu 2.74 Systemless, layers and Ex 4.06 kernel. Android N DP4. Since N became compatible with AP Dp3.
[SuperSU] steviemch:
No problems using AP on N6p running latest N preview, systemless root, Layers, ElementalX, Adaway.... You get the picture.

Nexus 6P
[SuperSU] kiradotee:
Is there a list with new systemless SuperSU's? The only one that "works" for me (as in root works but not Android Pay) is this one but they are quite old versions.
[SuperSU] ldeveraux:
What do you mean? If your device and system are capable, the newest version will automatically install systemless when flashing.
[SuperSU] Alxoom33:
2.76 is the latest. Best use that one and install as Systemless.
[SuperSU] kiradotee:
I tried flashing the latest stable UPDATE-SuperSU-v2.76-20160630161323.zip from this thread but my phone got stuck on boot (during the install it seemed that it tried to modify /system).

Although BETA-SuperSU-v2.62-3-20151211162651.zip installed successfully and works.
[SuperSU] Alxoom33:
Read the OP.
[SuperSU] MDHACK:
Peharps someone else have the same issue than me. AP seems to work good before making a payment. I can add cards with no problem. The thing is that when I approach the phone to the paying machine, it asks me for the password, but then when I enter it, it keeps asking for the password and payment is not processed. This only happens when I have root. I have to flash stock system to make AP work. BTW my phone is a T-Mo Samsung Note 4 on stock Android 6.0.1 TW
[SuperSU] Alxoom33:
AP seems OK to me. I'm on N 7.0 Preview 5.
[SuperSU] DROITURK182:
Well I had to disable SuperSU 2.76 just to get Android pay to work today at vending machine. Had system less root also, looks like the cat and mouse game is on again with Google..[emoji19]
[SuperSU] Ingenium13:
Sometimes I've had it randomly stop working and a reboot fixes it. I used it fine twice today, and SafetyNet is still showing True.

Sent from my Nexus 6P
[SuperSU] Pig Vomit:
Unfortunately, I think he's right. Just had it give me an error (Android Pay can't be used with this device) while trying to pay. Something server side. Probably a slow roll out. I haven't seen that error since the last time Google disabled it, then CF got around it with systemless.

Stock Nexus 6P, latest Marshmallow MTC19X build, systemless 2.76, Android Pay v1.4.126456861.

I have recently and frequently used AP with this exact set up, so that's why I say it's server side, or they have updated SafetyNet. I haven't used any SafetyNet checking apps for months, as I have had no problems. SafetyNet Helper is indicating:

"SafetyNet request: success

Response validation: success

CTS profile match: false".....so I'm not able to use AP.
[SuperSU] Ingenium13:
Sent from my Nexus 6P
[SuperSU] Pig Vomit:
Before I left my house, was getting consistent CTS: false, but at the gym consistent CTS: true and passing SafetyNet test. Did another test just before I got to the register at Sprouts, passed. Tried to pay with AP.....denied. Ran another SafetyNet test right after, passed.

It was nice while it lasted. Goodbye AP. Can't go unrooted.
[SuperSU] drewski_1:
+1 nice to crush the hopes and will of the Early Adopters, Google :(
[SuperSU] RandomPooka:
I can't blame Google on this one. We're trying to get a thing to work that has been specifically addressed by them and we were told it isn't going to work intentionally.

The financial institutions do NOT want you to be performing these transactions on a device with root. I completely get their perspective here. There are countless possible ways to commit fraud with that combination, and there's plenty of possibility that a malicious app could be doing "bad things" in the background even if you aren't actively trying to be fraudulent. (From their perspective, mind you)

The easiest way to deal with it is to not allow devices that have had the system modified.