yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] bouchigo:
Android Pay still works with Viper4Android installed even though certain areas of system are modified; I have, and many others have used Android Pay successfully using Viper4Android with systemless root and busybox installed to /su/bin.

The files modified/changed are:

/system/etc/audio_effects.conf

/system/etc/audio_policy.conf

/vendor/etc/audio_effects.conf

Files added:

/system/lib/soundfx/libv4a_fx_ics.so

Files renamed:

/system/priv-app/MusicFX/MusicFX.apk -> MusicFX. bak

There are certain areas of system you can modify and still be ok. I don't know what all those areas are exactly, but obviously messing with the actual framework apk or build prop will cause issues.
[Nexus 6P General] 1112ee:
Is there anyway to remove xposed framework without having to optimize apps every time?
[Nexus 6P General] chinmay_7d:
Can you confirm Android Pay (able to actually make a transaction) working with Viper installed?
[Nexus 6P General] bouchigo:
Yes, I can:

http://xdaforums.com/showpost.php?p=64297417&postcount=153

http://xdaforums.com/showpost.php?p=64300678&postcount=159

I made a zip that will install it for you, it's in the first post I linked. Or, you can install it manually if you prefer. I personally made an Android Pay purchase at Walgreens earlier this week and it went through fine. I even got my $20 Best Buy gift card already because of that purchase :good:

If you pass all the SafetyNet tests with this app, you should be fine: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
[Nexus 6P General] chinmay_7d:
[MENTION=790321]bouchigo[/MENTION]

Thanks! gonna give it a try. I am on stock kernel, does this need a custom kernel or SELinux to be Permissive?
[Nexus 6P General] bouchigo:
No, it doesn't. You just need systemless root, and busybox installed to /su/bin. Make sure you delete the xbin_bind folder in /su if it's there.
[Nexus 6P General] Andrew025:
Sorry if I'm misunderstanding, but it says to "delete this file in this path" but I have 2 files in there. Just delete them both? I have dexdump and wlutil in the xbin_bind folder.
[Nexus 6P General] bouchigo:
Delete the xbin_bind folder and reboot.
[Nexus 6P General] DeathmonkeyGTX:
Is there an ad blocker that doesn't impact android pay?
[Nexus 6P General] 1112ee:
I've had it work with AdAway, but just in case there's this http://xdaforums.com/showthread.php?t=2190753
[Nexus 6P General] Bootup:
Adaway
[Nexus 6P General] Beast84:
I thought AdAway touched the system? I switched to Adblock Plus with systemless root because of this. But it doesn't exactly do the job. Most ads still get through with it. If this is the case, I'm back to AdAway.
[Nexus 6P General] scoobysnack:
Use MOAAB works just fine. I manually added the host file and renamed the original host file so I can switch it back if I need it to not block a site.
[Nexus 6P General] Beast84:
Manually add it to Adblock Plus? Or AdAway?
[Nexus 6P General] scoobysnack:
MOAAB if a flash able zip. Just extract the host file. Goto system/ect rename the original host file and replace with the extracted one and set the permissions. No need to reboot.
[Nexus 6P General] Beast84:
But that defeats the purpose of what's being talked about. There's no point in having systemless root if you're gonna modify the system. Thanks for the suggestion though
[Nexus 6P General] scoobysnack:
Oh OK I'm sorry. I'm new to this seamless root thing. It's been awhile since I've had a phone I could toy with.
[Nexus 6P General] djeddieone:
Has anyone been able to get Android pay working with cm13?
[Nexus 6P General] :
This is what I did and have Android Pay working now. Systemless root, exposed not installed. Thanks!
[Nexus 6P General] laxattack:
I'm trying to find out the same thing
[Nexus 6P General] RogerPodacter:
I don't know about cm13. But I just found out I edited audio mixer to boost my volume, and android pay stopped working. Man I wish I could keep android pay and modify the volume output to be louder.
[Nexus 6P General] binglejellsx2:
I can confirm that this works, even without root. Some ads still get through, though. I've flashed MoAAB and the zip to enable multi-window (modifies build.prop) while successfully using Android Pay. The biggest difference on my device from everyone else here is that I am not rooted, nor do I have a custom recovery. These were the only two mods I did (currently it's just MoAAB because multi-window is to buggy).

Everytime I want to flash something I just fastboot boot TWRP. I've kept my device stock because Pay never worked on my rooted N5 and Moto X PE '14 - before the Nexus 6P was released. Like everyone else, I was able to add CC's, but actual transactions failed. Systemless root is new to me, but I haven't bothered with it yet. My 6P is still encrypted so I haven't messed with it too much.
[Nexus 6P General] I_alqaraawi:
you just open it or you try to pay?
[Nexus 6P General] SirRastusBear:
Hmm, I'm no noob but I can't seem to find the /su/xbin_bind directory. I do find /system/xbin and that's it. Running Cataclysm with Elemental X and busybox installed along with flashing SuperSU 2.65 systemless zip. Should I delete the xbin folder to get Android Pay to work? Any input is appreciated. Cheers
[Nexus 6P General] j8048188:
DO NOT delete /system/xbin! It will hose your install. If you don't see a /su/xbin_bind directory, then you should be good.
[Nexus 6P General] IM0001:
Why does this seem to continue to go against all that is being posted here? Editing the build.prop breaks AP no matter what, correct? You can still add cards all you want with systemless root, but the minute you mess with the Build.Prop then any purchase you try to make with AP fails.

The question I have, is there a way to get Tethering working natively and keep AP working?
[Nexus 6P General] jackpollard:
To add to this thread; I was initially worried about unlocking and rooting because I do use Pay. But why get a Nexus if your not going to tinker. I unlocked, flashed twrp and used the systemless v2.62-3. I deleted /su/xbin_bind directory. I checked Safetynet Helper and I was all green. I added a few cards and finally had a chance to try it today. I have my lunch and touch my 6P and "not!!". I got the dang "can't use Pay because something or another". I fumble with my wallet and get a card.

I go to eat and I think about it, Oh Yeah, I re flashed some things and sure enough, the /su/xbin_bind was back. I delete it and go buy some things and success!

I have a custom kernel, some root apps and that's about it. I made sure to install busybox to /su/bin folder. I read where there was issues with restoring a nandroid, I was going to wait for that to be fixed to flash a ROM. I've not tried the newest SU, but will this week. Anyway, Pay seems to work with no issues with the above.
[Nexus 6P General] Bootup:
You must've did more than just edit it. Did you check your permissions? I edited my mixer file and still have no problem with Android Pay.

Added Viper, Pay works

Added Adaway, Pay works

Increased audio volume, Pay works
[Nexus 6P General] RogerPodacter:
Yeah I didn't set any permissions afterwards so you're right that's probably the issue. Little happier now, will go test it out.
[Nexus 6P General] GTiceman:
I have partially tested and deleting the su/xbin_bind/ seems to work. Before doing this I couldn't add cards, after I can add. Haven't gone to a store yet. I used 2.62-3
[Nexus 6P General] 4redstars:
I might be missing something but is 2.63v3 better than 2.65 or does it matter?
[Nexus 6P General] SirVilhelm:
What is /su/xbin_bind/ used for?
[Nexus 6P General] NewMan4Life2010:
Yes I can add cards and still use Android Pay with the tether build.prop editing. I even use it with the build.prop tether hack to get the free $20 BestBuy gift card. I think Android Pay won't work if you edited your bulid.prop to change your DPI. I have Cricket with the 20GB plan.
[Nexus 6P General] jackpollard:
Each version had a bit of a different twist on getting Pay to work, the v2.62-3 version just needed the /su/xbin_bind deleted, thats why I've stayed with it. I've not tried the latest 2.65, but if you try it let us know. Some additional info -> http://xdaforums.com/nexus-6p/general/android-pay-rooted-t3260062/page11
[Nexus 6P General] IM0001:
Well then I will have to give this a shot then. Thanks for confirming.
[Nexus 6P General] 4redstars:
Last night I flashed 2.65 deleted xbin_bind and Android pay worked
[Nexus 6P General] jackpollard:
Thanks for letting us know, I will dl it and flash it next time.
[Nexus 6P General] 1112ee:
-snip-
[Nexus 6P General] will.bates94:
What in the hell am I missing here?

Stock

No xposed

TWRP

Busybox installed to su

Rooted with systemless 2.65

deleted xbin_bind

still can't get a pass on the safetynet check in the CTS profile.
[Nexus 6P General] sapphirecoupe:
Does xposed break android pay (nexus 6p) Chroma ROM?
[Nexus 6P General] 1112ee:
Yes
[Nexus 6P General] jackpollard:
It all sounds 100% correct. I suppose you need to go to the next level; have you flashed a custom rom or xposed? If so I wonder if something is hanging out? You change your dpi in buildprop? 100% sure you installed BB in /SU? You running a custom kernel? If so, each time you flash it you have to delete xbin_bind. Also, and this may be just me, I've been using v2.62-3 and have no issue.

Let us know what happens!
[Nexus 6P General] will.bates94:
Im on stock rom, flashed pure nexus for less than an hour and didn't like it, restored my backup.

No xposed

No dpi changes.

I'm 100% sure I installed BB, opened the app and saw where it installed, even uninstalled it with safety net still failing.

I am in fact running ElementalX Kernel, but I dont think this the cause is it?

Should I just flash everything back to stock and unroot and then go from there to see what is breaking android pay?
[Nexus 6P General] jackpollard:
I'm using EX also and it works great. How ever time I flash it, I have to delete /su/xbin_bind again, but I'm sure you checked that. When you restored, did you wipe system or just restore over it? Any other root apps installed? I know V4A has/had some issues, it changed something in /system. You wipe caches before and after you restored?

I would hate to say go ahead and flash it back to stock, it's usually a bit of a pita.

I'm on Cataclysm + EX, I was very picky on what rom/kernel I used because I use AP all the time and that combo worked well.

If you have the time, it may make sense to wipe and flash back to stock, it would clean up any issues, but like I said, it's a pita.
[Nexus 6P General] will.bates94:
Agreed I'm not much of a fan on getting this back to stock. But yes I've been sure to make the nandroid backups after I had deleted xbin_bind folder. No viper sound mods. Literally stock, systemless rooted, twrp, and EX kernel.

I also have Rom Toolbox installed and TiBu.
[Nexus 6P General] MaliceOmega:
I'm using chroma ROM, no xposed, no special kernel w/ systemless root SU 2.61 and android pay work fine for me. No need to take off root or anything
[Nexus 6P General] will.bates94:
So I just did a full system reset. Had safteynet helper all green as well until I rooted with the same method you used. I even went in and deleted the /su/xbin_bind. After deleting it, I rebooted, and ran the safetynet helper again and still get a false on the CTS profile match. I used the exact same systemless v2.62-3.

I really don't think its worth mentioning, I also did a nandroid backup of my unrooted system... I highly doubt that this changes anything in the /system folder since its just a backup....

Any ideas?

EDIT: Just checked my internal storage and see that I used the 2.65 instead of the 2.62-3. Ill report back to see if anything changes after i restore and re-root.

---------- Post added at 11:14 PM ---------- Previous post was at 10:58 PM ----------

Confirmed that there is something up with any systemless root thats post v2.62-3. Deleting just xbin_bind yielded a full pass on the safteynet helper, and rooting with v2.65 will require more than just deleting just xbin_bind in order to get a full pass on safteynet helper.
[Nexus 6P General] DubelBoom:
With Systemless root v2.65 & TWRP Recovery (obviously unlocked bootloader) after deleting /su/xbin_bind/ I was able to reach the screen where you add the credit card.

I still didn't check if it works in store, but because Android Pay isn't supported in Israel I'm not sure at all if it works in store (some people worldwide said they were able to use Android/Apple Pay in not supported countries, you just need a compatible credit card, but for now you can use Android Pay with all credit cards so I will try it soon).
[Nexus 6P General] subhumanderelict:
I hate being the guy that claims to have found something contrary to what is being stated in a thread, but I think there might be another solution here using the traditional root method.

I’ll start with my information:

Model: 64GB on Sprint (US)

Build number: MMB29M (flashed factory image)

SuperSU version: 2.52 (free)

TWRP version: 2.8.7.2

Everything else is stock (no custom kernels, modules, etc…)

I followed Heisenberg’s root method (link) as soon as I took the phone out of the package late last month. I followed steps 1, 2, 3 (if I remember correctly), and 7 (traditional root method). The only issue I encountered during the process was a bootloop which I traced back to me forgetting to use the modified boot.img file.

Yesterday, I disabled SuperSU, went into Android Pay, added my Bank of America debit card, re-enabled SuperSU, and was able to successfully make a purchase at a Meijer. No tricks; I just unlocked with the fingerprint scanner, held the phone to the reader, and everything went through. I plan on trying this at a Walgreen's and/or CVS this week as well.
[Nexus 6P General] IM0001:
Just wanted to chime in as well that I was able to have both Systemless SuperSU Root and add and use a card for AP all while having the build.prop edit for tethering added.

On Sprint

Latest 6.0.1 OTA.

Used the Root Toolkit to unlock bootloader.

Pushed latest TWRP to Recovery.

Copied over SuperSU 2.66 zip and flashed in TWRP.

Rebooted System (Make sure you do not let TWRP install its version of SuperSU as it doesn't detect the one you just flashed).

Using ES File Explorer, enabled root access and edited the build.prop to include net.tethering.noprovisioning=true at the bottom.

Removed the /su/xbin_bind folder

Ran Security Checker and came up green.

Added card, called to authorize, and was able to make a purchase at Jamba Juice yesterday.
[Nexus 6P General] dratsablive:
I was finally able to get Android Pay to work with Systemless Root. After flashing the new images and SuperSU Beta, it still wasn't working. But since /system was not mounted RW I couldn't delete /su/xbin_bind. So I did

adb shell

su

rm -f -r /su/xbin_bind

Rebooted phone and Android Pay now works.
[Nexus 6P General] itch808:
Ok, so I read through everything but have had no luck with AP working.

Hx: Unlocked bootloader via fastboot, flashed TWRP, flashed Cataclysm 1/6/16, flashed SuperSU 2.66, booted. Haven't edited my build.prop, no Xposed, and there's no /su/xbin_bind. I'm unable to add any card. I was able to add a card when I was stock and unrooted.

What am I missing here?
[Nexus 6P General] dratsablive:
There might be something with Cataclysm that Android Pay doesn't like.
[Nexus 6P General] jackpollard:
I'm running Cat + Pay works great. I had something similar and I realized I did not have systemless root, you have to issue 1 command to force systemless root. Try this then let us know --> in TWRP, go to terminal and type "echo SYSTEMLESS=true>>/data/.supersu" and so you don't have to delete /su/xbin you can do this --> "echo BINDSYSTEMXBIN=false>>/data/.supersu"

Then reflash 2.66.
[Nexus 6P General] itch808:
THANK YOU!!!!! This fixed it! I was able to add a card to AP! I'll test it out later in stores
[Nexus 6P General] jackpollard:
Nice, I should of told you to also grab this app, safetynet helper --> https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en

Run it and if your green you good to go.
[Nexus 6P General] geoff5093:
You need to flash SU 2.62-3. Anything later causes Android Pay not to work, from what I heard. Run the UN-SU script then reflash 2.62-3.
[Nexus 6P General] 1112ee:
FYI, android pay is working with system-less root on Pure Nexus rom
[Nexus 6P General] dratsablive:
I am using SU2.66 and Android Pay is working fine.
[Nexus 6P General] geoff5093:
On Cataclysm?
[Nexus 6P General] dratsablive:
No sorry, on stock. Have you tried this after flashing 2.66?

adb shell

su

rm -f -r /su/xbin_bind

reboot.
[Nexus 6P General] geoff5093:
No need, just use a file explorer to remove it. It was posted on the Cataclysm ROM page that SU 2.62-3 works after deleting xbin_bind, but if you install a later version like 2.65 or 2.66, even after deleting that, it doesn't work.
[Nexus 6P General] dratsablive:
None of the file explorers I have, Root, or EFS work with systemless root. Can't delete using those.
[Nexus 6P General] geoff5093:
Works fine with Solid Explorer.
[Nexus 6P General] 4redstars:
This must just be a rom problem as I'm on 2.66, deleted Xbin_bind with Solid Explorer and it works great. I'm on stock with ElementalX.
[Nexus 6P General] adatydoo:
I believe 2.64+ will attempt a non-systemless install unless you first go to the TWRP terminal and run "echo SYSTEMLESS=true>>/data/.supersu".
[Nexus 6P General] thair7391:
I'm having some strange issues as well regarding the CTS profile match.... I'm running the PureNexus ROM, franco kernel, completely unrooted it (with unSU.zip) then rooted wtih 2.66 (Systemless; I verified it isn't auto going to system install). I have installed BusyBox to /su/xbin (for Layers compatibility; Layers won't work for me in /su/bin). Everything works just fine; root, BusyBox, etc.... Here's the weird part:

I run the SafetyNetHelper and half the time, everything checks out and it's green; the other half of the time, it fails and says CTS Profile Match: false..... What's going on here??? I can literally keep the app open, run the test several times in a row, and sometimes it will pass a few times in a row, and other times it will fail and then switch back to passing if I keep going. I have deleted the /su/xbin_bind folder; this isn't the issue. What could be constantly writing and unwriting to /system to cause this?? I've tried denying root permissions to everything to make sure nothing is getting access to system and it still happens; changes back and forth....

What's going on here? What can I do to permanently pass this?
[Nexus 6P General] jasoraso:
I updated to 2.66 at the same time I updated to the latest security patch, and then I flashed the Elemental Kernel (love swipe to wake). Somewhere along the line, it broke AP.

Finally fixed it by reinstalling boot, system, and vendor from latest source files from Google, then flashing TWRP, booting into TWRP and NOT allowing it to modify system, then flashed 2.66 and Elemental, and now I have working AP again. I think the key for me was not allowing TWRP to modify system on my first boot into TWRP. Perhaps the command to force a systemless install of 2.66 would have worked the same.
[Nexus 6P General] KnifeSkills:
Same issue here, happens using both SafetyNet Helper as well as SafetyNet Playground to test. I'm on Chroma 1/10, stock kernel, 2.66 systemless, but it was also happening on stock systemless rooted 6.0.1.
[Nexus 6P General] 83097markcynt:
Step 1 Flash UPDATE-unSU.zip http://xdaforums.com/showpost.php?p=63615067&postcount=2459

Step 2 Flash SuperSU 2.61 https://download.chainfire.eu/746/SuperSU/BETA-SuperSU-v2.61-20151207213702.zip

Now I don't have busybox installed so maybe that's a problem but I've used 2.61 for all my systemless root install and AP/Safetynet work every time.
[Nexus 6P General] divadkha:
I'm on stock 6.0.1, and I was able to modify build.prop and get AP to work, but only if I disable SuperSu (not uninstall) afterwards. At least I'm at the point where I only need to modify build.prop for native homescreen and lockscreen rotation, and not need constant root access.

So the entire process for me was:

Flash stock boot.img and system.img

Boot twrp.img (or flash then boot TWRP)

Flash SuperSU 2.66 for systemless root

Boot and use Solid Explorer to edit build.prop, and delete /su/xbin_bind folder

Disable root from SuperSU app (again, not uninstall or Full Unroot) for Android Pay usability

Reboot

OPTIONAL: Install EX Kernel from TWRP

Might not be very useful for anyone needing constant root access. But for those who just need to make few changes before disabling root, like editing build.prop, then this workaround should be useful.

I was also able to install EX Kernel afterwards from TWRP and still retain Android Pay usability. But again, SuperSU had to stay disabled for me, which probably also meant not being able to manage the kernel from the EX Kernel Manager app (which I don't do anyways).

I also wanted to add that I've been using Capital One's Wallet app to easily check for NFC payment usability. If there was an issue it would disable it's NFC payment feature, which was a good indicator that Android Pay would also give an error at a NFC terminal. Once I tried all the different steps to try and get AndroidPay/NFC payment to work, the CapOne Wallet app would allow the NFC payment feature and let me assign my card. Which, coincidentally, Android Pay will also complete transactions at the terminal.

In my opinion, it's better than relying on Android Pay to fail at a terminal just to find out if it thoroughly works. Since, it won't give any indication if it will complete transactions whether or not you're able to add cards.
[Nexus 6P General] thair7391:
Thanks for this information; I appreciate it.

I was on Chroma prior, not having any issues, then I dirty flashed the latest build. Ever since then I've been having the issue of the safetynet SOMETIMES passing and SOMETIMES failing. Of course, I unrooted after the flashing (unSU) and reapplied the latest systemless 2.66 at the time and installed BusyBox to /su/xbin. I've been having these issues since and I have recently tried the PureNexus ROM and am encountering the same issues here. I would try and older build like 2.62 or lower, but then I can't use /su/xbin as a BusyBox install path which you need for Layers Manager to work properly.

*EDIT* Actually.... Thanks for this!!!! I tried disabling SUperSU and this has gotten me consistent passes in the SafetyNet Helper. The question is, what keeps using root to write to system and change my status while root is enabled? I can't find anything in the logs.... At least I know now it isn't my BusyBox installation so that's good because I really don't want to move it out of /su/xbin.

---------- Post added at 07:55 AM ---------- Previous post was at 07:53 AM ----------

If you notice, I said that during my process, I flashed the ROM, the kernel, then UNROOTED with "unSU" and then flashed the superSU binary. This will work for a matter of minutes when I boot back into Android and then it will start failing and passing on and off again. I can literally run the SafetyNet test 5 times in a row and some of them pass, some fail. So something is CONSTANTLY writing to /system and then unwriting it. Why else would it change like this?
[Nexus 6P General] jackpollard:
Have you run the TWRP command; "echo SYSTEMLESS=true>>/data/.supersu" before you flashed 2.66? Then flashed 2.66? It tries to force systemless root if you dont issue that command and that seems to break Pay.

You can also run; echo BINDSYSTEMXBIN=false>>/data/. supersu right after the 1st command and then you dont have to delete /su/bin_bind.

Also, if your using EX kernel, you flash supersu before you flash the kernel.