yashsingh1/xdaforums huggingface dataset:
[SuperSU] FletchF:
Thanks for the tip on Root Checker. Do you need the advanced version for the SafetyNet checks? On Basic, there doesn't seem to be a way to run the test a second time.

I've had various errors using Android Pay with both rooted and fully stock phones. In most cases, I'm pretty sure it's not SafetyNet related, but the error messages are not very useful. It would be great to have an independent way to test whether my phone passes or fails SafetyNet.
[SuperSU] andresee:
Same dont see it listed either...
[SuperSU] JimSmith94:
Same here. I have Root Checker Pro, have run it several times, both in the same session and from scratch, and I still don't see any SafetyNet info.
[SuperSU] Mircolino:
Android Pay works
[SuperSU] jackdubl:
I don't think you heard his question correctly.
[SuperSU] Mircolino:
What do you mean?

AdAway modifies the system partition. Yet with systemless root Android Pay works, with traditional root it doesn't.

To me that's a huge benefit.
[SuperSU] jackdubl:
Yeah, but in his question he said he was modifying the system. So Android Pay won't work.
[SuperSU] andresee:
You can mod the system and Pay stillworks. FYI
[SuperSU] Mircolino:
Yes it does. AdAway modifies the system and Android Pay works just fine.

I even changed /system/build.prop to unlock tethering on my Nexus 6P and Android Pay still works just fine.
[SuperSU] Chahk:
When you say "root restricted devices" do you mean those with locked bootloader? If so, you wouldn't be able to use systemless root in the first place, because it needs a custom recovery.

I thought Android Pay will stop working when it detects a modified /system partition, even if you temporarily disable root. Is this incorrect?

Well yes, since you don't need to modify /system to symlink the host file. What I'm asking is if I plan on installing Xposed or doing other modifications to /system, is there a benefit of using systemless root over system one?
[SuperSU] jackdubl:
Wait, what? Since when? Everyone has posted that simply changing your DPI causes it to fail. Or adding the line to unlock tethering in the build.prop. So maybe Adaway doesn't trigger it(this is the first I've heard of that) but other changes do. Or has something changed?

---------- Post added at 02:17 PM ---------- Previous post was at 02:15 PM ----------

So has something changed, because that used to cause Android Pay to fail?
[SuperSU] Evo_Shift:
Yeah, I thought modifying system at all broke Android pay which is why I still just use the old root method. If we can actually modify the system and still use android pay with systemless root I'll do that. What exactly is Android Pay looking at if it isn't a modified system?

---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------

How does adaway work without modifying the host file on the system?
[SuperSU] Mircolino:
Not sure if and when it changed.

I'm running MMB29M with systemless root SuperSU 2.61 (which you can't even disable).

I have AdAway installing hosts in /system (not symlinking) , I modified build.prop to enable tethering and I just paid at Trader's Joe with Android Pay a couple of hours ago :)
[SuperSU] andresee:
Go to settings and change the location of the host file in adaway. Like to /data/hosts ... It will create a symlink.

---------- Post added at 08:30 PM ---------- Previous post was at 08:25 PM ----------

But you cant use the xbin_bind if you want pay to work... But 2.62 works great.
[SuperSU] jackdubl:
Looks like it's time to try systemless then. [emoji4]
[SuperSU] Pig Vomit:
Nexus 6P, stock 6.0.1 MMB29M, rooted with 2.62-3 systemless.

Yesterday went to McDonald's, Android Pay didn't work.

This morning, flashed stock Recovery, Boot and System. Went to McDonald's. Android Pay worked. Earned my $20 Best Buy gift card.

Went home. Went back to TWRP and 2.62-3. Went to McDonald's for lunch. Android Pay would not work.

Only thing I haven't tried is disabling superuser through SuperSU with a reboot prior to trying Android Pay (this used to work on Lollipop). Maybe tomorrow.

I'm tired of eating at McDonald's trying to get this to work.

UPDATE: I tried it again, disabled superuser with reboot, didn't work.

I have now deleted xbin_bind, will try again soon and will post back. No, hadn't done that before.
[SuperSU] andresee:
Make sure you are not using xbin_bind
[SuperSU] swallowingled:
The SafetyNet Check was just added in the most recent update. I have the pro version and it's towards the bottom. There's also another app called SefetyNet Playground that can run the test.
[SuperSU] FletchF:
Thanks. Just bought the Pro version and it's now there.
[SuperSU] Ketawa:
Beware, upgrading to Pro by purchasing the bundle through the basic version of Root Checker will not work correctly. Google Play does not recognize that I am authorized for the Pro app directly through the store. Also, the bundle upgrade does not add the SafetyNet check feature. If you want the full functionality of the Pro version, you need to download it directly from Google Play. I requested a refund from the developer for the bundle to upgrade to Pro.
[SuperSU] dk0r:
Same here. I tried complete wipes and rerooting SuperSu 2.61 and 2.62-3 nearly ten times on MMB29M and Android Pay failed every time.

I never authorized twrp 2.8.7.2 to write to /system and I never let twrp flash it's embedded version of SuperSu.

I even completely restored the device to locked&stock and retried a complete unlock/root on 2.62-3 and still, Android Pay failed. Going to try 2.60 now.
[SuperSU] JimSmith94:
I just bought Root Checker Pro and mine shows SafetyNet Status: False like your screenshot. I assume that's why Android Pay doesn't work, but is there a way to see what is causing it to fail?
[SuperSU] Ingenium13:
Not explicitly. I suggest reading this, which gives a thorough description of things that it checks and how it works https://koz.io/inside-safetynet/. It seems to also indicate that blocking doubleclick (ie AdAway) will cause it to fail.

It's really just a matter of time though before Google updates it to point to the new location of the su binary.

Sent from my Nexus 6P
[SuperSU] osm0sis:
Easiest (/free-est) one:

https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

My N7 2013 still passes (for now) with AdAway set up systemless, and busybox, nano and adb installed systemless.
[SuperSU] Ketawa:
My 6P passed the SafetyNet check on SuperSU 2.62-3 after deleting /su/xbin_bind. I have AdAway also. Deleting /su/xbin_bind was the only change I needed to make in order for SafetyNet to change from failure to success.
[SuperSU] Chahk:
Have you tried adding a new card after modifying /system in any way? Just because you can pay using a previously added card, it doesn't mean Android Pay is "working". Only adding a new card is the true test whether or not the safety checks have been defeated.
[SuperSU] Mircolino:
This is rather pointless as it would take Google no time, if they wanted, to find the new su binary location and break Android Pay, systemless or not, no matter how and when you add cards.

Right now it works... I'll take what I get.
[SuperSU] drawde40599:
Yes you can modify system add cards and go pay with them .
[SuperSU] Alxoom33:
If you would read this thread, even the last 5-10 pages or bother to search this thread before posting, you will find numerous posts that the /su/xbin_bind file in 2.62 breaks Android Pay and must be removed for Android Pay to work.

I'm sorry to rant but others an I have posted this so many times... times. If you are uncomfortable deleting a file, SU 2.61 also works fine with Android Pay.
[SuperSU] Nikos2k:
If it doesn't work, change some other parameter. Try eating at burger king
[SuperSU] sefrcoko:
After reading the last 10 pages I feel like this is now an android pay thread :(
[SuperSU] GroteBozewolf:
I tried to find my answer in between al the Google Pay issues, but could find it.

So out of curiousity: would 2.62-3 work on a Stock Nexus 4 on Android 5.1.1 (or any 5.1.1 device)? And if so, will it also be systemless? Or will it fallback to the non-marshmallow root?
[SuperSU] mobileman88:
Adaway modifies hosts which is in system

---------- Post added at 10:29 AM ---------- Previous post was at 10:25 AM ----------

Isn't tethering already enabled?
[SuperSU] Pig Vomit:
Deleting xbin_bind got Android Pay to work for me tonight. Only eating at McD's to test out Android Pay! BK doesn't have it!

At least it's good to know I tried *everything* else out, and that was the only thing that worked.

Phone is now perfect!
[SuperSU] Tigana:
Jumping in here to say that I followed instructions, re-flash the stock system image, flashed latest TWRP recovery, flashed SuperSU 2.62.3, deleted the /su/xbin_bind folder. Android Pay is working and AdAway is working and systemless root is awesome on Nexus 5 6.0.1. I'm a happy person. Thanks to everyone that worked on this.
[SuperSU] Neverendingxsin:
Will deleting that folder cause any issues?
[SuperSU] Alxoom33:
2.64 working great on NEXUS 6 Shamu 6.0.1 with Cataclysm Rom/Mod and EX 3.0.7 kernel. Android Pay working if /su/xbin_bind folder Deleted or disabled. I disabled it by renaming the folder by adding .bak and rerbooted so that folder can be restored if needed.
[SuperSU] Midomad:
Could please test if you can delete system apps with TB,i'm on the same setup with N5 and i can't!
[SuperSU] Neverendingxsin:
I assume reflashing SuperSU would also restore the folders.
[SuperSU] buzzwyzr01:
Do you use layers? I have the exact setup as you and since migrating to 2.64 my layers won't install via layers manager app.
[SuperSU] KINGDROID25:
I'm hoping someone can help me as I'm a little nervous about upgrading... Im currently on a nexus 6p with supersu 2.52 and I'd like to upgrade to the beta as I've read that it works with Android pay...
[SuperSU] IronTechmonkey:
Check the WIP thread http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344. Also, probably answered earlier in this thread.
[SuperSU] Alxoom33:
Yes, but I think it's easier to just rename the folder if I want to without flashing.

Yes, quite a few. Your System partition is too full to add any layers. I first flashed the Cataclysm stable rom and debloated any needless gapps using the custom settings in the AROMA Installer. If you need any of those gapps later on, then get them from the Play Store and install as a user apps. After freeing up the System Partition, you can flash the mod and layers will work.

Yes, no problem!

That shouldn't be a problem. But read up first! At least the last 10 pages or so and the OP. If you need help after that pm me, or ask for more help on this thread.
[SuperSU] Alxoom33:
You will need to read up for that one. But, briefly, to root, you need the su binaries which normally reside in the stated Partition.However, since the System Partition is modified you can't take an OTA.

[MENTION=631273]Chainfire[/MENTION] developed a new root method in which the su folder resides in the Data Partition in the Root tab. The System Partition is therefore not modified, thus Systemless Root.

One advantage is that if Systemless Root is modified by deleting one folder from the su folder, Android Pay works, because it cannot detect modified System Partition.

That's my simplistic explanation...I'm sure those who have a better understanding can provide a more detailed explanation.

---------- Post added at 11:52 PM ---------- Previous post was at 11:49 PM ----------

See my post above.[emoji2]
[SuperSU] chazall1:
I am on the current cataclysm 12.21 and Elm 6.7 and su 2.65 and all functioning. When I was using 2.64 I had the file Removing /su/xbin_bind made android pay work. On SuperSU 2.65 android pay does not work. I have rNotes on 2.65+

As 2.65 adds /su/xbin but it seems my install is in /system/xbin?
[SuperSU] Maxr1998:
Well, at first, your device should pass checks for OTAs, secondly, if it doesn't pass, even after manually flashing the new system.img the device stays rooted, and third, Android Pay will work in spite of being rooted.

To switch, you need to a) restore your stock (unrooted) kernel if you used system root on Android 6.0 before, b) reflash a clean system.img/reflash your custom ROM, and c) flash the newest SuperSU.
[SuperSU] drewski_1:
I have system root on my N7 on 6.0.1 so it is compatible. It just upsets some things like Android Pay, but is actually more compatible if a root program is coded to expect root in /system

---------- Post added at 09:07 AM ---------- Previous post was at 08:57 AM ----------

Reflashing the system.img shouldn't mess with your configuration if you don't reformat data.

You're doing a dirty flash, is all ?
[SuperSU] ddrum2000:
Thanks for the help but now I'm thoroughly confused on why this isn't working. I'm running a Nexus 5X. Let detail my steps so you all can see if I'm missing something:

Using SuperSU 2.65 installed as systemless, choose the Full Unroot option.

Fastboot the following Images: Boot, Vendor, System, Cache in that order.

Fastboot TWRP 2.8.7.2

Boot to TWRP to verify that system is mounting RO - it is

mmcblk0p41 is where my system partition is stored. While in TWRP recovery:

~ # cat /sys/fs/ext4/mmcblk0p41/lifetime_write_kbytes
0

Boot into an unrooted system and check if Android Pay gives its error message - It works fine with no error message

Reboot into TWRP. Enter the following into terminal:

echo SYSTEMLESS=true>>/data/.supersu

Flash SuperSu 2.66 and the script output verifies systemless install

Reboot into system and check SuperSu app. It is installed as systemless. In an ADB terminal:

shell@bullhead:/ $ cat /sys/fs/ext4/mmcblk0p41/lifetime_write_kbytes
0

Run Android Pay and it fails! The error message is:

Root for most programs does work.

So how can I get the systemless root running without breaking Android Pay? Also presumably if Android Pay is breaking, OTAs would break as well, correct? Thanks for your help and patience.
[SuperSU] pnr2020:
Just curious how are some people getting android pay to work when knox is tripped when you root. Or im i missing something
[SuperSU] coreydkoster:
Thanks for the help but now I'm thoroughly confused on why this isn't working. I'm running a Nexus 5X. Let detail my steps so you all can see if I'm missing something:

1. Using SuperSU 2.65 installed as systemless, choose the Full Unroot option.

2. Fastboot the following Images: Boot, Vendor, System, Cache in that order.

3. Fastboot TWRP 2.8.7.2

4. Boot to TWRP to verify that system is mounting RO - it is

5. mmcblk0p41 is where my system partition is stored. While in TWRP recovery:

6. Boot into an unrooted system and check if Android Pay gives its error message - It works fine with no error message

7. Reboot into TWRP. Enter the following into terminal:

8. Flash SuperSu 2.66 and the script output verifies systemless install

9. Reboot into system and check SuperSu app. It is installed as systemless. In an ADB terminal:

10. Run Android Pay and it fails! The error message is:

11. Root for most programs does work.

So how can I get the systemless root running without breaking Android Pay? Also presumably if Android Pay is breaking, OTAs would break as well, correct? Thanks for your help and patience.

Not sure if 2.66 still requires this, but I didn't see in your steps where you deleted su/xbin_bind.

Delete that folder and AP should work.
[SuperSU] ddrum2000:
I don't have su/bin_bind but I do have su/xbin_bind. Should I delete the xbin_bind?
[SuperSU] Alxoom33:
Yes, you have to delete or disable the Root folder /su/xbin_bind. I just disable it by renaming it by appending .bak to the file name and rebooting. Android Pay should then work. [emoji2]

Yes! It will.
[SuperSU] jeffreii:
I've been using systemless root for a few weeks now and am quite happy with it. Deleted the folder to get Android Pay to work and it's been excellent.

The only issue I have remaining is GSAM Battery Monitor (Play Store)...specifically its Root Companion app (Play Store). Has anyone else gotten this to work properly? The attached screenshot shows the error I receive when trying to enable it...which I assume is because it's trying to write to /system. The dev told me he's not familiar with systemless root and asked me to flash a zip to achieve the file move but I'm skeptical as to whether or not this is a good idea.

Here is his suggestion:

"That's exactly what the root companion installer needs to do - remount r/w - copy the APK to /system/priv-app/ and then remount system r/o. Why the remount r/w doesn't work, I'm not sure.

Give the flash images a shot. Download the zip - and flash it from recovery.

https://github.com/GSamLabs/GSamBatteryMonitor-RootCompanion/tree/master/RecoveryInstallImages

That should do the trick - let me know if not!"

Any thoughts? What should I explain to him if this is simple a case of him needing to update his app to be compatible with systemless root?

Thanks!
[SuperSU] NZgeek:
Yes, adding anything to /system will modify it, which means that you'll lose the ability to use Android Pay.

It may be possible to create a su.d our init.d script that bind mounts the .apk file into /system/priv-app. The bind mount doesn't actually modify the file system, just makes it look like the file is there.

I'm not sure of the technical details of how to make this work, just that it should (in theory) do what you want. Whether it actually works our not could come down to timing.

Edit: I've looked up the bind mount syntax and have attached a script for you to try.

Download the attached 10gsamrootcompanion.txt.

Remove .txt from the downloaded file name.

Copy the file to /su/su.d.

Set the file permissions to 755.

Reboot.

Post back and let us know if it works.
[SuperSU] pnr2020:
I been trying to get titanium to work for weeks now. My problem is it wont delete apps just freeze them. Wish i never payed for the pro version now
[SuperSU] adrman:
2.66 is working perfectly on N6P angler with MMB29P. The device passes a Safetynet check and Systemless Adaway is also working.
[SuperSU] bigknowz:
AP Fail

Have systemless root with 2.65, but Android Pay fails, wondering if any of these are causing my problem:

1. didn't enter

echo BINDSYSTEMXBIN=false>>/data/.supersu

2. Using Tasker

3. Using TiBu

4. Have busybox, but used the [MENTION=4544860]osm0sis[/MENTION] zip to move it to su/xbin

Any and all thoughts appreciated.
[SuperSU] nathanchance:
Delete /su/xbin_bind if it exists.
[SuperSU] adrman:
Door #1.
[SuperSU] JimSmith94:
I renamed the subdirectory instead of deleting it, just in case. I did have to reboot afterwards to get Android Pay to work again.
[SuperSU] jackdubl:
How do you modify the build.prop and keep Android Pay working? It stops everyone I try. Must I use adb? If so, can it be done in twrp?
[SuperSU] Mircolino:
Perhaps is more of a question of what kind of build.prop modification will AP tolerate.

Simply adding "net.tethering.noprovisioning=true" at the end using "Root Explorer" doesn't break AP on my Nexus 6P.
[SuperSU] TheWyzeMan:
Is there a way to tell which method SuperSU chose to root? I'm getting an error when I try to launch Android Pay after clean installing 1/6 Cataclysm and SuperSU 2.66.
[SuperSU] nathanchance:
SuperSU > Settings > Install SuperSU into /system, check the text underneath the setting.
[SuperSU] Apocalypse~:
I understand. But I don't need systemless, as I don't use android pay nor want seamless OTAs, since I'm on a custom ROM. I've also read it causes issues with some things like Layers and V4A. I could be wrong. Either way, system (traditional) root is all I care at this point.

Sent from my Nexus 6P
[SuperSU] Gedablo666:
Yeah after systemless root layers manager not uninstalling layers. But I cant use Franco kernel without it. So nothing I can do here.
[SuperSU] osm0sis:
Yeah that's a foolish restriction on his part since most custom ROMs will obviously include root and systemless is kind of pointless on a custom ROM unless you want to mess around with Android Pay..

My AnyKernel2 zip versions of his latest N5 versions work fine on any ROM and root type, so you could make one for your device if you're up to it, or ask someone in your device's franco.Kernel thread to look into it.
[SuperSU] shaggyskunk:
[MENTION=4544860]osm0sis[/MENTION]

I think that ultimately that's my question - Is Systemless Root of any benefit to someone who is running a Custom AOSP Rom on a Samsung Note 4?

I've heard that you may have some benefits? If the Rom is SELinux Enforcing?

I've also heard - (But not sure how) You can Flash SU 2.66 as a System App if you don't need it to be Systemless?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] milojoseph:
Hello everyone I flash to get system less mode on my S5 5.1.1 I used ur unsu zip and flashed the supersu zip and get this error.
[SuperSU] timbang:
Tried to install 2.66 on Nexus 6 that has 2.56 installed (MMB29K). Following the guidance on the WIP post, I re-flashed stock boot image prior to installing 2.66. When I go into the SuperSU application, it's still showing v2.56. For grins/giggles, I also tried flashing stock system image, stock boot image, and then installing 2.66. Same results. On my Nexus 9 (also MMB29K), the upgrade worked flawlessly. Thoughts?

Incidentally, one of the root check apps I tried shows that the N6 is running 2.66 but the SuperSU application settings screen is still displaying 2.56 and several options that are available on the N9 2.66 remain grayed out on the N6 with the "Not (currently) available in system-less root mode)" message. Both devices running SuperSU Pro if that is relevant.

(forgive if asked/answered in thread... went back 15-20 pages and couldn't find anything but I did find out how to re-enabled Android Pay so thanks for that)
[SuperSU] shaggyskunk:
Without doing anything else - I Flashed SuperSU 2.66 on my already Rooted Nexus 7 running AOSP 6.01

ONLY thing I has to change was to uncheck Name Space in order to get Titanium Backup to work - That's all :)

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] :
Update to Android Pay just hit the store 1.2.111627672 who is brave enough to update and see if it still works with 2.66? :) There is only one merchant near me about 35 minute drive away so it will be a while before I can test
[SuperSU] nathanchance:
Any blocking of systemless root is going to come from Google Play Services, which holds the SafetyNet API, not the app itself.
[SuperSU] lioryte:
Confirmed working
[SuperSU] greatheights:
Am I systemless?

Hi, I'm really sorry if this has already been covered, but I spent ~45 min looking through old posts and didn't see anything.

I'm getting really confused by this: "A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu")."

My question is, how do I know for sure if the installation was systemless or not? I use Wugfresh's NRT to flash everything, so I'm not sure where/how to enter "echo SYSTEMLESS=true>>/data/.supersu", so I didn't. That makes it sound to me like since I didn't override, the installation will modify /system. Is that right?

I'm on a Nexus 6, clean install of stock MMB29S,

TWRP detects an unmodified system partition.

Flashed SuperSU v2.66

TWRP still detects an unmodified system partition.

SuperSU also seems to indicate a system-less installation as "Install SuperSU into /system" is greyed out.

I didn't install BusyBox, Xposed, or anything else that would modify /system, that I know of.

However, Android Pay doesn't work. Is it working for anyone else on MMB29S, or did Google break it with the most recent security patch?

If it's working for others, any clue what I did wrong? Are there any common root apps that modify /system that I might not be thinking of?

Thanks for your help
[SuperSU] nathanchance:
Remove /su/xbin_bind and reboot. AP should work then.