yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] WTF?:
you are the one who is confused, I know precisely who I was talking with, and, in fact, both were present - mismatched colors was not the problem, the problem is that the mismatched colors could not be reset by the theme developer nor the Layers app developer, nor myself. Perhaps the bug has been fixed now, but that was pretty huge at the time. Not interested in apps by folks that are flyin by their ass releasing stuff that powerful that's still buggy for MM - same reason I stopped using CM, kinda OCD about bugs that break critical stuff. - like google play, the camera, stuff like that. :rolleyes:

we tried exactly that

starting to to think you could have a reading comprehension problem?

Keep on reading and learning! (likely the hard way, since apparently you don't take advice based on others experiences well)
[Nexus 5X General] Techstro:
Okay, so I used the systemless install, but my SuperSU app is installed as a system instead of user app. I see no directory for su, I do have xbin folder under system. Got no idea how to change permissions to 751 in root explorer, only read/write/execute etc. How can I play with the settings in the SuperSU app to revive Android Pay; moreover, how can I make Android Pay work without factory wiping my data and my Glorious xPosed Mod's customizations?:eek:
[Nexus 5X General] thesoldier:
Xposed and Android Pay won't work in unison, period. Xposed modifies system which immediately breaks AP.
[Nexus 5X General] godzulu:
Worked perfectly this morning. Successful pay at McDonalds :) ka ching
[Nexus 5X General] GTiceman:
So would modifying build.prop also break AP?

EDIT: NM this was talked about before duh
[Nexus 5X General] MrMiami81:
What ad blocker do you use if any? I have ad away too on my nexus 6 and was wondering if that was stopping AP from working. I was able to add cards but purchases didn't go through.
[Nexus 5X General] godzulu:
I use adaway, pure nexus, 2.67 systemless. AP working beautifully
[Nexus 5X General] chazall1:
On an N5> I dont do layers, addaway stuff. I had a working AP with SU 2.67 before it stopped functioning like everyone else. When the new changing file permissions su/bin to 751 you think this fix should work across Nexus devices?
[Nexus 5X General] demlv:
It did for me.
[Nexus 5X General] Techstro:
Yeah, I found out right after posting, it's the system thing. Much thanks for the response. I just feel there has to be a way to modify or patch Android Pay to get it to work without being so snobby. Well I'm gonna make a way, or I'm gonna stab until it gushes!!! In a civilized way of course...
[Nexus 5X General] MrMiami81:
Nexus 6, 6p, or 5x?
[Nexus 5X General] godzulu:
Oops, nexus 6p :)
[Nexus 5X General] VerticalCobra:
AdAway now works with or without ad blocking on. Its not AdAway that's stopping AP from working.
[Nexus 5X General] tjb51681:
So I'm having a big issue, I can get systemless root, after that when I go into terminal in two and type su

Chmod /su/bin it I reboot and I have no cellular service, I can't figure out what I'm doing wrong?
[Nexus 5X General] jlink38:
Re-read the OP... You forgot the 751
[Nexus 5X General] HarmfulMushroom:
This worked for me, before I wasn't even able to get to the add a credit card screen. I was at least able to add one finally, will test whether pruchases also work.

I'm running PureNexus rom
[Nexus 5X General] soltrain:
Worked for me as well! Running stock ROM with elemental kernel and SuperSU-v2.62
[Nexus 5X General] Yaz75:
Part of me is amused because some guy from Google is just going to read this, then make sure they patch this workaround in the next update. So then we can have another of these threads finding another workaround. Google should pay you guys for finding, testing and documenting the security issues that they will patch.
[Nexus 5X General] Joshmccullough:
There was actually another thread active for a while that had a Google employee engaging in discussion with forum members; unfortunately, it devolved into a bunch of nonsense and got closed. Google's probably got enough information on what's going on with Android Pay without having to lurk in XDA to find out about it, hence their previous closure of the loophole that was being exploited, well after that other thread was shut down.
[Nexus 5X General] Seanbest:
I flashed the systemless root and SuperSU shows v2.67, but I have no /su/bin directory to change the permission to configure it work with Android Pay. Suggestion?
[Nexus 5X General] Letitride:
I think I got AP back again, as far as getting bank (CC issuer) to do the verification check & passed, so the default card is ready to use (and, prompted to set up PIN or security lock on the device)

Followed all the steps to unSU, flash newest SU v2.67 and then flashed EX kernel, wipe dalvik & cache. Reboot device - launch (previously installed Terminal Emulator App, downloaded from Store) - and, at the command prompt, type "SU" - then, use ES File Explorer to find & delete /su/xbin-unbind folder. Go back to Terminal still running, type "chmod 751 /su/bin" .

Close Terminal & exit, go to AP and add card ... and take a deep breath. (Note, I had previously run the echo command lines already, if not - do that too) Will need to find a nearby AP terminal & make a purchase just to confirm (and, report/share - update this post ... without creating another one) No other mods on my N5, no Exposed or AdAway or Viper4 sound mods, etc. (on latest Layers build)

On a side note, Google/Android wanting to make life difficult for us to use their AP in the name of security & protection, fine by me - guess what, some of us just won't use it & discontinue and not be bothered with it at all, it takes 5 seconds to pull my wallet & swipe or find those greens, cash is always king. AP will then cease and slowly died of a thousand cuts. Mrs. L won't even be bothered with this AP even it's on her Nexus 6 running stock rom.
[Nexus 5X General] Ketawa:
After modifying the permissions for /su/bin/ as described in the OP, I think AP will work for me now. SafetyNet check passes and I can get to the screen in AP to add cards.

I have a Nexus 6P with SuperSU 2.67.

I used FX file explorer since I didn't want to mess with another file explorer. To change the permissions, I accessed the "Security" option for the directory and unchecked Global Read, which changes the octal from 0755 to 0751.
[Nexus 5X General] Joshmccullough:
Quick Q for those more knowledgeable than I:

Would these steps and the related SuperSU piece be something that could be scripted/put into a flashable .zip? I'd offer to try, but I can't get it working on my N5 no matter what, so testing it would be useless on my end, and while I've got the basics of Bash scripting (VERY basic) under my belt, I'm not sure if that's the shell environment that Android uses......in any case, just wondering out loud for others much more knowledgeable than I to weigh in on.
[Nexus 5X General] ts_mpls:
This might be obvious for everyone else but I thought I'd share in case someone else is having the same problem. I was pretty sure I was doing everything right but I just couldn't get AP to work running PureNexus on my 6P. It turns out, it was because I was running the CMTE build. After switching back to the layers build, it works like a charm!
[Nexus 5X General] jgummeson:
Funny you should ask... I'm working on a simple script to do this now. It's stupid simple - like only 10 lines of shell script. I'm not that great at shell scripting and have never done an update.zip before. Anyway I just ran it on my own N5x after reinstalling systemless root and SafetyNet went from not passing to passing. Looks like it works. Only issue at this point is that I couldn't figure out how to get echo or ui_print to work and show up in TWRP. I guess I'll fix that in the next version.

I've attached my update.zip for anyone who's daring. Otherwise you could probably just edit the SuperSU installer script. There's a place where it chmods everything all the files in /su/ - you would just change the permissions for /su/bin/ there and get the SuperSU install and permissions fix done all at once.
[Nexus 5X General] Joshmccullough:
So in what order would you place this .zip in the 'flashing chain'? Thanks for taking a stab at it!
[Nexus 5X General] jgummeson:
Just flash this anytime after you've flashed the systemless root. In theory it shouldn't matter if you flash other stuff in-between. All this zip does is mount the /su image in recovery and chmod the bin directory for you. It has some handy error messages to tell you if it doesn't detect the systemless root... but they don't work. Not yet anyway.
[Nexus 5X General] phia:
Does this work for nexus 6? Thanks!
[Nexus 5X General] jgummeson:
In theory. If the systemless root installs the same on the 6 it should work. You would be the first to try it though.
[Nexus 5X General] revolt1:
the zip worked on the 6p
[Nexus 5X General] elkay:
Changing /su/bin from 755 to 751 in Root Explorer took Safetynet from fail to pass without even a reboot. I imagine Android Pay will work just fine again since it working or not always correlated to the Safetynet status.
[Nexus 5X General] bgarlock:
Works for me on stock rooted Moto X Pure Edition 2015.
[Nexus 5X General] yongh:
How to run the adb?

---------- Post added at 08:05 PM ---------- Previous post was at 08:01 PM ----------

How to check if I have systemless root
[Nexus 5X General] NordomTT:
Is this still working? I've made several purchases with my rooted 6p, the most recent one on this Wednesday. SafetyNet Helper still passes, but I can't make a purchase on a vending machine anymore.
[Nexus 5X General] elreydenj:
What does the phone say when you try to make the purchase?
[Nexus 5X General] NordomTT:
Something can't be verified for compatibility. Or something like this.
[Nexus 5X General] elreydenj:
Anyone else use it today? Last time i used it was Wed. as well. I will try it at some point this weekend.
[Nexus 5X General] NordomTT:
It's probably my ROM. I'm using PureNexus on the latest build, which failed the purchase. I just dirty flashed to a previous build and android pay worked again.
[Nexus 5X General] mng777777:
I work in payment technology and it's pretty embarrassing that I can't demo soft pay with my phone... Thanks for the work you're all doing to get this figured out!
[Nexus 5X General] elreydenj:
Thats what i thought. I just flashed the latest Pure Nexus as well. I will test it out. Are you on CMTE version?
[Nexus 5X General] NordomTT:
Yeah please let me know how it goes. No I'm using layers. I think CMTE breaks android pay no matter what.
[Nexus 5X General] elreydenj:
Correct.

---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------

Did you go through all of the necessary steps after dirty flashing? Changed DPI or using viper or ad blocker?
[Nexus 5X General] NordomTT:
No. Didn't do any of these.
[Nexus 5X General] elkay:
Can follow up now to confirm the above, that Android Pay worked just fine for me at the grocery store that it had worked at in the past before systemless root was blocked.
[Nexus 5X General] Seanbest:
I flashed SuperSU 2.67, but I have no /su/bin to chmod. Suggestions?
[Nexus 5X General] greves1:
Thanks for this, but I tired with the latest Chroma rom and it doesn't seem to work. Can anyone please verify if this is because of the rom or something maybe I've done wrong? I just switched back from cataclysm to Chroma. Flashed this zip stack: vendor, chroma, gapps, systemless2.67, and finally the zip provided in this post.

I'm rooted and everything is great. I just fail API checks. Thanks for any help!
[Nexus 5X General] Jself70:
I'm on chroma with my nexus 6p. I flashed the zip file and now ap is working for me
[Nexus 5X General] greves1:
Did you ever flash any SuperSu zips? (2.67). Perhaps I messed up by flashing this. If I did, anyone know how I can undo what I did to get back to "stock chroma" and flash the zip from this thread. Would Un-SU zip from chainfire work?

Don't know why I didn't notice this last time, but I just went to re-flash the UnSafetyNet.zip and it gave me ERROR=1. Any ideas? Thanks all for getting this working again!

For some reason TWRP (2.8.7.2, also updated to 3.0.0.0 and same error) gave me a screen on reboot to recovery that I had never seen before. I forget exactly what it said, but it was about permissions or something. Sorry I didn't write down the exact message. I hit the box and swiped to select that I wanted to be able to modify my system, or something like that.
[Nexus 5X General] mng777777:
The screen on boot is the normal splash screen the first time TWRP loads in 3.0.0. It doesn't indicate a problem.

Separate from that. Are you saying that TWRP also returned error=1 during the flash upgrade to 3.0.0?
[Nexus 5X General] greves1:
Sorry, maybe I was not clear in my post. The weird splash screen came up in the old TWRP version, which I thought was quite strange because I never saw it before. I hope I chose the correct option. I don't see the setting where to check what I actually chose/change my choice.

Anyway, I updated TWRP through the app. It actually gave me an error, said it didn't install, but asked if I wanted to reboot to recovery. I did, and it went to 3.0.0.0. So apparently it did work, the app just falsely thought it didn't work. I didn't get a splash screen on first boot into 3.0.0.0

I did not get a error=1 from the twrp install because I used the app for that. I just get the error when trying to install this .zip for AP to work.

Sorry if this reply sounds wrong, since the splash screen I saw doesn't make any sense to have come up before updating to 3.0.0.0, but I could have sworn things are as I have just said...

---------- Post added at 07:48 AM ---------- Previous post was at 07:40 AM ----------

Same here. Flashed 2.67, but have no /su/bin. Root permissions are working fine with my apps.
[Nexus 5X General] Jself70:
What I did was flash the unsupzip then supersu 2.67. After that I flashed that update zip. Wipe and then it worked
[Nexus 5X General] greves1:
Thanks for the suggestion. Just tried this. Still getting error: 1 when i try to flash the update zip from this thread. I suspect this is probably related to not having a /su/bin. Do you have this directory?
[Nexus 5X General] gitchrodd:
I had this problem also. I reflashed 2.67 but skipped the "echo BINDSYSTEMXBIN=false>>/data/.supersu" then using a root explorer i had the su directory and i just deleted the xbin folder.
[Nexus 5X General] greves1:
Could you clarify a bit please what you mean by "skipped the echo...." So you did this manually from OPs instructions right? And didn't use the script? I'm still not clear why it seems our phones are different from the others who do have the /su/bin dir.

Edit: went back and saw OP's post:

"UPDATE 3: To clarify on the systemless SuperSU installation (this seems to be a trouble point for some) - there are settings that need to be configured for the SuperSU install to make it systemless and to not create the system/xbin binding. The installer reads these options from a file on /data/. Since you don't have root yet you need write these settings over ADB in TWRP. If you don't see the /su/ directory, you probably don't have a systemless install. In that case you can go back to stock (restore system, boot, and vendor partitions). Then, when you reinstall SuperSU, these are the commands you need to send from your TWRP ADB shell:

Code:

echo SYSTEMLESS=true>>/data/.supersu

echo BINDSYSTEMXBIN=false>>/data/.supersu

Once you've got SuperSU installed, change the permissions of /su/bin/ (either chmod or using a file explorer)"

So it would appear that I can tell I'm not systemless becuase I don't see /su, is that right? So given that I've already got the 2.67 flashed, do i have to "go back to stock" as OP suggests. I wouldn't know what this would mean for people such as myself running chroma. SuperSU comes baked in the rom. Can I just run the commands in my current configuration? Thanks for any help!
[Nexus 5X General] Scottchy014:
This should work for you. Just change everything with "Pure Nexus" to "Chroma" or whatever ROM you are using. It's a dirty flash method.

1. Download*Pure Nexus 1/03/16 or newer,*UnSU,*the latest SuperSU, and a custom kernel if you want one onto your*phone.

2. Boot into TWRP and make a backup (optional but HIGHLY recommended).

3. Flash Pure*Nexus.

4. Flash UnSU.

5. Type these commands, one at a time, into Advanced > Terminal Command > Select current folder in lower right hand corner:

Code:

echo SYSTEMLESS=true>>/data/.supersu

echo BINDSYSTEMXBIN=false>>/data/.supersu

The first one forces systemless, the second prevents /su/xbin_bind from existing.

6. Flash your custom kernel*and SuperSU (refer to your kernel thread for which zip you need to flash first).

7. Reboot and profit

Here is the link to where I got all this info from: http://xdaforums.com/showpost.php?p=64399733

Also, here is the post where you can get the UnSU zip file: http://xdaforums.com/showthread.php?p=63615067
[Nexus 5X General] greves1:
Thank you so much. This worked to get me systemless. I thought it was strange before that after flashing 2.67 I did not have the "two-boot bootloop" which always happens after the boot.img modifications required by the systemless root.

Now, my AP is still not working. I fail the safetynet check. Is this because I haven't changed permissions on the /su/bin folder? If so, I might need a bit of help doing this. I tried using adb as OP says and when I type "su" it says command not recgonized. Not sure how to do this. Ill check through this thread though. Thanks!

Edit: Ran the commands for changing permissions using android terminal emulator. Permissions for /su/bin changed to rwx r-x --x. But I still fail the API check...

Edit 2: Got it working yay! I now pass safetycheck and was able to add a card. All I had missed was to rename /su/xbin_bind to something else. I just added _old. It's all working now finally, yay! Hopefully google won't go ahead and break this again any time soon...
[Nexus 5X General] bobby janow:
[MENTION=3621532]greves1[/MENTION] Were you able to make a purchase?
[Nexus 5X General] greves1:
Will let you know in a day or two when I get a chance to use it. However, many people in the original thread have confirmed purchases working. I've never read anyone say that the safetynet check will show pass and then purchase not work, and I have safetynet passing so I'm quite confident this will work at POS.
[Nexus 5X General] bobby janow:
Tried it today and it worked for me.
[Nexus 5X General] greves1:
Great to know thanks for the update.

By the way, does anyone know why AP was broken the first time, a month or more ago by some google update? What exactly was it that killed it? And can this be prevented in the future? (even if it means losing the monthly security updates -- which I assume if we're rooted with AP we probably don't care much about anyway). I don't like that it seems google can just take away our AP at any time without warning...
[Nexus 5X General] Ketawa:
SafetyNet has always been able to detect modifications to /system, so Android Pay never worked with system root. Android Pay was able to work with systemless root at first, then SafetyNet was modified to also detect the location of the su binary with systemless root. By taking away the Global Read permission for /su/bin, it isn't able to do that. I don't think it's related to an update to Android; this happened independent from that.
[Nexus 5X General] greves1:
Thank you for this explanation. So it would appear the next move would be to check for permissions for /su/bin and if it doesn't have global read permission, fail the test, no? The game of cat and mouse continues...
[Nexus 5X General] bobby janow:
I don't think so. From the above explanation it seems that the su binaries shouldn't be there at all. So if the check can't see it then all is good. They might be able to find something else in the system that is modified due to the availability of root but then that is just a root app. Not sure how it will play out but as it seems we currently have the upper hand for the moment. That could change before I hit the submit key. And knowing we're not trying to subvert security just make it better and more friendly for the end user.
[Nexus 5X General] Seanbest:
I didn't do the echo commands either and still no su/ directory.
[Nexus 5X General] gitchrodd:
You have to do the first echo command or it won't do a systemless install.

echo SYSTEMLESS=true>>/data/.supersu
[Nexus 5X General] flashcity90:
Im on a Nexus6p to begin, and posting here because your forum is the most informative.

Can someone help explain to me the full process of a clean install with AP working. I've tried this multiple times and cant get it. Went full stock unrooted to begin. Then I flashed for systemless root and confirmed in SU(under settings it has an option to install Superuser in system, but cant and is greyed out if your on systemless). Flashed purenexus, gapps, Un-su, Terminaled the 2 echo commands, flashed SU 2.67. Booted. Android Pay no go. Edited permissions for su/bin to rwx r-x --x, Android Pay still a no go. Can annnnyone please clue me the F**k in.....
[Nexus 5X General] thvoicwethin:
worked for me, thanks!

changed permissions in Root Explorer of the su/bin to 751, deleted the su/xbin_bind, restarted, and VOILA! I'm very happy someone finally found a fix for this!
[Nexus 5X General] jgummeson:
I'm copying this from my post over in AP thread on the SuperSU forum. Simplified installation steps and updated flashable zip if you choose to use it (error messages should be working now if it can't detect your systemless root install). These are the steps:

1. If you haven't rooted yet, make sure AP works. If it doesn't work before rooting it won't work after rooting with the permissions change.

2. Configure SuperSU for a systemless install without the xbin bind if you haven't already. From ADB or terminal run these commands :

echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu

3. Flash SuperSU and reboot

4. Flash UnSafetyNet.zip (or just boot up your phone and do the permissions change with a file explorer/ADB - the change from failing to passing should be immediate and doesn't require a reboot)
[Nexus 5X General] Jinded:
At what point does Android Pay fail? Have you tried removing all cards, rebooting, then re-adding?
[Nexus 5X General] martyfried:
Just an FYI about a typo: the second echo command is missing the final 'u' - says "/data/.supers" instead of "/data/supersu".

Probably a cut and paste error.

EDIT: Looks like it has been fixed now. Really, I'm not actually imagining things. :)
[Nexus 5X General] ydnolb4:
Just adding another data point, this works for me on Cataclysm 6.0.1. I was able to add a card and make a purchase yesterday.
[Nexus 5X General] martyfried:
After ignoring AP and using normal system root, I decided that I might want to try it sometimes, so when the last Pure Nexus Rom release came out, I decided to do a full install and go systemless. I followed the (directions by Nathan Chance very carefully, installed Android Pay from the play store, and it would not allow me to enter a credit card.

Being a full-time Linux user, I double checked everything that has been specified; I didn't run the script, but I had no trouble understanding what it was doing, so I went through the steps manually, so I could be sure everything was as it should be...

1. I checked that superSU was installed systemless using the app; I also followed the unSafetynet script and verified /data/su.img was present;

2. I had already set the permissions of /su/bin to 751, but since it wasn't working, I booted into twrp, used the terminal to mount su.img, and double-checked that it was indeed 751;

3. I opened the file /data/.supersu, and triple-checked that the two lines I had echoed before the superSU install were there and exactly as specified;

4. I did not ever have /su/xbin_bind, so I assume the 2nd line did its job.

I am using superSU 2.67.

If anyone has any other ideas, I'd appreciate it.