yashsingh1/xdaforums huggingface dataset:
[SuperSU] dratsablive:
Android Pay now checks if the bootloader is unlocked.
[SuperSU] Alxoom33:
Use Xsetprop?
[SuperSU] dratsablive:
Well not concerned with AP working, just want to get SUHide to work with 7.1.1 so I can root and play PoGo.
[SuperSU] gunz.jones:
It's based on safety net. Xsetprop was helping to pass with some phones with locked bootloaders tripping the alert. Pretty sure that went out the window today for a few models though.
[SuperSU] antonyyip:
Today Google Services had updated again. Previously method using SuoerSU+Suhide with Magisk+Xsetprop and Rootswitch no longer works! Any one has clue how to make CTS Profile Match true again?
[SuperSU] Araltd:
So sorry, I'm trying to play catch up here... So is there a way to use Android pay or Samsung pay on a rooted device or not?

Or is there an alternative to android pay for using NFC loyalty cards? Not necessarily bank cards? (ie: supermarket loyalty cards, coke rewards cards, movie theater loyalty cards, etc)

Sent from my Note 6
[SuperSU] Alxoom33:
I'm afraid to say that's true for the N6 running 7.0 Su v. 2.78 SR 2 Magical 8.0 mod 2 and Xsetprop 2.1 with root switch.
[SuperSU] centran:
Someone comes out with a method and then shortly after Google patches for it. Cat and mouse game right now. I suspect these methods will have to go underground to invite only forums as this seems to be a losing battle.
[SuperSU] Captain_Throwback:
Magisk seems to be what's detected now, but you don't need Magisk to use xSetProp. So if that's all you're using it for, just uninstall Magisk.

You can put the xsetprop binary from the zip into /su/xbin and the post-fs-data.sh into /su/su.d and it should still work fine.
[SuperSU] Alxoom33:
Just to be specific, do we need to change permissions? I am confused as to what file is the xsetprop binary that you are referring to. There is one file labeled xsetprop in System/xbin which I think is the xsetprob binary, but there is another file labeled update-binary in Meta-inf/com/google/android. Is that the binary?

Also, what do you recommend the best way of uninstalling Magisk. I uninstalled the Magisk APK and deleted the Magisk folder using Root explorer. Is that sufficient? I suspect since I am not passing the SafetyNet, I may have remnents of Magisk left in my device.
[SuperSU] Captain_Throwback:
update-binary is for flashing the zip (which you're not doing).

"xsetprop" is the binary file. And yes, the proper permissions should be applied to the files - 755 for xsetprop, and 700 for the script.
[SuperSU] Alxoom33:
Thank you. It was all set properly, but didn't pass Saftey/Net. I think there may be a Magisk remnant. left. Any idea how to check? I've looked in Root Explorer and in TWRP.
[SuperSU] Captain_Throwback:
If you restored stock boot.img and deleted magisk.img, that should be enough.

If you want to be REALLY thorough, you can delete /data/busybox, /data/magisk, /data/su, and /data/stock_boot.img. If all that is gone, then Magisk is already completely removed, and that's not your problem.
[SuperSU] antonyyip:
I use HTC 10 and followed the removel of magisk and unroot/re-root instructions, then put the extracted files from xsetprop in proper locations with correct premission set, but still failed in CTS Profile check.

The only step different is I only flash custom kernel (ElementalX) rather than a clean boot.img. I also check the above thread that I have no remaining files for Magisk..... any clue why still fail?
[SuperSU] Captain_Throwback:
xSetProp doesn't work with SuperSU on the HTC 10. It only works with Magisk.
[SuperSU] luigidk:
Is there a similar cleanup after uprooting?

After a clean flash I start out rooted with SuperSU 2.71sr1.

When I'm done restoring with titanium backup and some other tweaking... I do a full unroot.

However the only way safetynet passes is if I do a dirty flash and reinstall the ROM and kernel.

Note I'm using a kernel that handles the unlocked boot loader

After the dirty flash safety net passes.

Seems there could/should be cleanup in can perform after unrooting so I don't need to dirty flash
[SuperSU] gotAndroid10:
Currently working for me to pass SafteyNet until Google updates it again...

US bootloader unlocked HTC 10 running latest stable LeeDroid ROM

ElementalX Kernal 0.23

SuperSU 2.78 SR2

Rootswitch 1.3.3.2
[SuperSU] Araltd:
Would that work on a Samsung? Or is it kernel dependant?

Using supersu 2.78 sr2

And Rootswitch 1332

I'm assuming it's kernel dependant, anyone know of a kernel that would work?

Sent from my Note 6
[SuperSU] gotAndroid10:
I'm not sure if it's kernel dependant, but this might help point you in the right direction...Info for Samsung Galaxy users looking to pass Safeynet
[SuperSU] _litz:
I'm having issues with rootswitch ... it turns root off fine (and SN passes), but then fails to turn root back on, requiring a reboot to regain root.

This is on a stock moto x pure, with 2.78SR2, suhide 0.55, and the latest rootswitch (1.3.3.2).

anyone have any ideas?

Also, does anyone know exactly what rootswitch does internally, or if there's a way to integrate it into a Tasker task?
[SuperSU] mimccann2014:
All root switch does basically for systemless root is unmounting /su, which was mounted via /data/su.img

Note all these commands require root, which means it also copy's the su executable from /su before unmounting. For the source code on exactly what it does see the .sh files within the app in the files folder, must be root if looking at the installed app. I don't use tasker, but if you can do anything like this it will be possible. I didn't upload the .sh files because I am not the creator of it and didn't want to violate any terms on here.

For the part of failing to regain root I would try to run the commands in terminal and see which errors are happening and it is most likely a mounting issue, which it should be using busy box I would think. Hope any of this helps.
[SuperSU] mimccann2014:
Update: I downloaded tasker and managed to get the scripts to work.

Steps

1) make task Disable SU

2) add the rootswitch disable script as a shell script.

su -c sh '/data/data/com.corner23.android.rootswitch/files/disable'

Alternatively you can copy the entire disable script and have taskedr run it as root.

****** Make sure tasker is granted superuser permissions before you move on. ********

3) run the disable task and verify it worked

4) find which version of the if else statements your device will run in.

My OP3 on CM13 uses the /oem/ version.

To verify yours is this version open any terminal you already granted superuser to and run following command

/oem/bin/su

If you now have a terminal running in root mode it is the same method as mine, as I expect any systemless root mode is.

5) create task Enable SU

6) add root switch enable script as shell script.

/oem/bin/su -c sh '/data/data/com.corner23.android.rootswitch/files/enable'

Note replace /oem/bin/su with the correct path to the su executable root switch creates for you.

7) run the enable task and verify it worked

EDIT: removed extra space in last command on the -c part

EDIT 2: Added 2 more steps of running scripts to check they work.
[SuperSU] Alxoom33:
I was passing Safety Net with Root switch, SuperSu 2.78 SR4, Superhide v.0.55 and Xsetprop working as well. However AP failed at the terminal when I tried to pay...Any ideas why?

Nexus 6 Android 7.0.
[SuperSU] mahsamoh:
not worked super su

samsung j1 ace supersu not working for device
[SuperSU] luigidk:
I'm on an n6p with pure nexus, currently unrooted and a kernel that bypasses the unlocked bootloader issue.

Safetynet passes but nothing happens at the terminal when using ap.

Seems i may have missed something.?
[SuperSU] JimSmith94:
The first step would be to make sure you have NFC turned on. :p
[SuperSU] _litz:
Finally had a chance to get back to this ... works like a charm.

I did have to change the two script calls to "disable.sh" and "enable.sh" though (e.g., added '.sh')

On the moto-x, it's using /oem/su/bin
[SuperSU] luigidk:
Ha, that's first thing I checked. I did just turn off data saver, you never know
[SuperSU] Bl1zZ87:
With 7.1.2 and root switch safety net don't pass actual. Any solution?
[SuperSU] Ch3vr0n:
solution, yes, post in the root switch topic. This is about SuperSU & SafetyNet
[SuperSU] AnkitGourav:
SafetyNet check failed after flashing SuperSU v2.82 on Android 7.1.2, RessurectionRemix 5.8.3
[SuperSU] Alxoom33:
Pardon my slightly OT question. When SuperSU is Flashed, is a backup boot.img saved? If so, where? Thanks.
[SuperSU] swallowingled:
On my Nexus 6P I see it in /data.
[SuperSU] Alxoom33:
I see stock_boot_d0.....f22a.img.gz is that it. Can it be flashed in TWRP? Or is it only fastboot flashable?
[SuperSU] Beall619:
Here is a possible method...

If the Api requires a response telling the Api if safety net passed then wouldn't it be possible to simply hijack the response and replace it with a passed response?
[SuperSU] genius88:
Hi!

Please tell me what is checking basic integrity in SafetyNet attest app? I have one xposed module that gives CTS profile match as true but basic integrity is still false. Finally it gives me test as positive but it's still not enough for some apps. I have custom rom and normally rooted with SuperSU. Thx
[SuperSU] nozz90:
Thank you so much!!!

I thought my boot image was gone forever
[SuperSU] Chainfire:
suhide-lite: https://xdaforums.com/apps/supersu/suhide-lite-t3653855
[SuperSU] Semitarra:
super su and pokemon go

hello xda i have only need help for one thing

i have android 4.4 rooted with su and i want to play pokemon go

can anyone help me please?

do i need to swicth su to magisk? if yes how?

(is magisk even compatible with android 4.4?)

or another way...

if i remove the root and can i play pokemon go?

if i remove root and unistall su can i root and install su back again?﻿ if yes how?

Thanks
[SuperSU] Roopak9:
I am give permission
[SuperSU] Phantom Thief:
If you just wanna spoof without root move now the spoofing app to /system and flash this on TWRP : https://xdaforums.com/showpost.php?p=63615067&postcount=2459 Then safetynet should pass
[SuperSU] corkiejp:
^^^ Why oh why are you replying to a 2 year old post. On a Thread about a practically dead app?
[SuperSU] drewski_1:
He's trolling for Thanks? :rolleyes:
[SuperSU] moko ngalam:
Hello
[SuperSU] Michael Westen:
I still have SuperSu on a very old phone that I still play around with sometimes.

Magisk is pretty much the gold standard nowdays I think. Passes safetynet pretty handily and allows for most anything SuperSu provides/provided. Never could get the hang of edXposed or whatever it's called, so pretty much abandoned the thought of resuming old Xposed ways and habits.
[SuperSU] Captain_Throwback:
The intent of systemless root isn't to make banking apps "not see root." It is intended to leave system untouched so that verity remains uncompromised and OTA updates can more easily be taken. As Chainfire has previously stated, even the side effect of Android Pay working and devices passing SafetyNet checks is unintended.

At the end of the day, root is root. So there's no reason your apps shouldn't be able to detect it.
[SuperSU] sunnytexas:
Thank You for the clarification! I usually use Titanium Backup for backing up settings and programs. I just wasn't aware of this issue with MM, but again Thank You for the info.:)
[SuperSU] The Gingerbread Man:
I don't know in truth. The phone was 100% unrooted though. I tried the unsu zip thing, didn't work, dirty flash the rom and unsu right after and that didn't work. Flashing the rom would return system & boot and the unsu should remove root completely.

Now surely if systemless root is good enough for android pay to work why won't it work on sky sports? I am a paying customer with a valid login so its not like I'm riping them off. All I want to do is watch this rugby game but without flashing back to stock rom I can't see it working. Any more suggestions (not xposed) feel free to comment.
[SuperSU] Ingenium13:
[MENTION=631273]Chainfire[/MENTION] clever hack for the bind mount in 2.62! It breaks SafetyNet though unfortunately. I'm guessing it just checks for su in the old locations rather than if /system has been modified. So if anyone still wants to use Android Pay (at least until Google updates SafetyNet), you should follow the instructions in the WIP thread to disable /system/xbin.
[SuperSU] Chainfire:
Good catch. They should both be "custom_boot_image_patch.sh", I'll fix and upload a new ZIP probably sometime today.

I'm not sure why restoring backup would fail. Can't really diagnose this unless I can reproduce it.

Perhaps the caches aren't properly wiped, I'll add some lines to script for this.

It's fully expected to break SafetyNet. Root is in general. The other way will soon also be detected by SafetyNet. I do not intentionally work around SafetyNet.

Yes.

Then it wouldn't be a stock boot image.

You can do this now and then reflash the ZIP to get the same result.

The original /system/xbin and /su/xbin_bind are merged at each boot, with /system/xbin being leading. If the destination path is unconstrained input, I'd actually use /su/bin, but /su/xbin_bind should also work.

Installing into /system/xbin probably fails because the app detects it can't remount /system, and thus assumes it cannot modify /system/xbin. If you don't mind modifying /system, you can unmount /system/xbin first, then install to /system/xbin.

As always though, I strongly recommend against installing BusyBox and symlinking it. In my experience it is the largest reasons for unexpected behavior of root apps.

I think so, but I don't know what. I don't know what could explain this.

Perhaps, consult the experts in your specific device's forum...

If you start with deleting a bunch of crap, you should be fine. The problem only occurs when /system is almost full, but you try to modify files or add files.

Interesting this, so far no idea what is going on.

EDIT: both with xbin bind mount enabled and disabled Keep doesn't ask me...
[SuperSU] The Gingerbread Man:
Hi Chainfire, as your around would you mind taking a look at this issue which could of been easily missed in this fast thread! I'm using nexus 6p, Franco kernel, android 6.0.1 with systemless root 2.61 and chroma rom.

I had an issue with a app which was detecting root even when I unrooted. The steps I took was using the full unroot option SuperSU, then tried flashing unsu, then tried dirty flash rom + unsu. Remove & reinstall app, clear cache, phone cache. Everything apart from 100% stock firmware. None of the above worked and this little zhit of an app still wanted to think I am rooted.

Although this issue isn't nesesarilly a su problem I would still like to hear from you if you have any ideas. I have already emailed the company asking for support why their apo thinks I'm rooted when I'm not. Is it possible something is still getting left behind? I don't know how the app makes it check for root sorry.

The app I was trying to use was sky sports, a video streaming service part of the BSkyB company over here in the UK. I am a valid paying customer of theirs and use their TV service at home.
[SuperSU] Chainfire:
Should work on 2.3 (or was it 2.1 ?) and newer :)

I can't possibly tell why the app thinks you are rooted, or if something has been left behind. The only thing I can tell you to do is complain loudly to the company that whether or not you want full control of your own device is none of their business, and their detecting root and refusing to deliver service is bull****. As with banking, if it works on a normal Windows computer, you have the same rights there as on a rooted Android device.

I can understand why they want to do this, but I would vote with my wallet.
[SuperSU] bobby janow:
Android Pay is not working with systemless root. That is probably due to Google PS or AP update.
[SuperSU] egingell:
The fact that it worked before it's purely coincidental. Systemless root was not made to make Android Pay work with root.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] Alxoom33:
Unfortunately, I can confirm. Not working for me, either. NX 6, 6.0.1 2.6.2-3
[SuperSU] PresidentMcCain:
No:

http://xdaforums.com/showpost.php?p=64161125&postcount=3
[SuperSU] Ketawa:
Check the WIP thread. If you delete /su/xbin_bind, Android Pay will work again. /su/xbin_bind is a workaround for root apps that weren't working with systemless root, so you might not need it.
[SuperSU] jesssiii:
Can confirm this works.
[SuperSU] chazall1:
I got Android Pay to work as well by deleting /su/xbin_bind .
[SuperSU] Alxoom33:
I went back to my Nandroid with Super Su 2.6.1 and installed Busybox Pro and guess what? Android pay now working[emoji2] [emoji106]

I think it is Super Su 2.62 v. ? That broke Android Pay.

Was /su/xbin_bind the only issue?
[SuperSU] tsadev:
You really should read before posting.

From the WIP thread:

In case it isn't clear, any modifications to /system will trip Android Pay's detection system (discussed previously on this thread).

2.61 doesn't do the above, and hence doesn't bother Android Pay.

As [MENTION=631273]Chainfire[/MENTION] has said previously, this is unintended behavior which will probably be patched by Google in the near future.
[SuperSU] Alxoom33:
Dude, take it easy! I read it, in fact, I have read every post in this thread, I had no idea it broke Android Pay.
[SuperSU] tsadev:
I wasn't trying to come off as rude, just informing you as to why it works for 2.61 ootb but not 2.62 :p
[SuperSU] elreydenj:
It doesn't work because of a file Chainfire added. Nothing to do with Google. Look in WIP thread to see which SU file to delete. Android Pay working fine on 2.62 version 3. Just remove the file Chainfire added to help get comparability for other root apps.
[SuperSU] Alxoom33:
I am using 2.61 works flawlessly and Android Pay works with this version of Systemless root. Why modify 2.62 v3?
[SuperSU] Chainfire:
I'll give it another week to see if any significant new issues arise, before claiming it's as stable as 2.52.

We're not at full OTA compatibility yet. Work in progress!

Either case you need to flash back stock boot image and recovery (this can/will be automated). I have seen the error myself on the 6P, but have not checked out the cause yet.

If you reflashing boot and system and it still doesn't boot, then it's not SuperSU, because you've wiped that.

This is not a known problem. Try getting a logcat if possible.

From your logs it seems the boot image wasn't patched.

I don't know. I suggest someone tries that.

Allow it to make modifications will remount /system in writable mode, and that action itself will prevent /system from being OTA compatible. Other than that, there are no drawbacks.

Yes, though I do not advice it. See the top of this post.

Free space is not an issue on the 6P. The above quote is for make /system writable by apps, and is unrelated to the free space issue.

Because else you'll be stuck on 2.61 forever and you will not get any support here on anything but the very latest version.
[SuperSU] Alxoom33:
Thank you for responding. OK, I'm back using 2.62-3 with /su/xbin_bind file removed to allow Android Pay to work (for now) instead of 2.61. What is the downside to removing the xbin_bind file?

Thanks[emoji106] .
[SuperSU] Cares:
By the way, I wanted to share that I'm failing SafetyNet checks and can't use Android Pay anymore. Previously it worked. Not sure if it is attributed to new version of SuperSU or if Android Pay was somehow patched.

Sent from my Nexus 6P
[SuperSU] pkelly517:
Seriously?

Search. Then post.

Or, more likely, search and then there is no need to post.
[SuperSU] Alxoom33:
You can delete folder /su/xbin_bind or flash version 2.61
[SuperSU] dratsablive:
Flashed stock system.img then used the SU 2.62 Beta to flash systemless root. However Android Pay still doesn't work after hiding root (either through SU or using Root Cloak and Xposed.)

Nexus 6P

6.0.1
[SuperSU] bobby janow:
When you get to a computer with a search function, type in Android Pay and you'll have your answer within a minute.
[SuperSU] Alxoom33:
I'm sure he will get it. [emoji2]

---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------

Either go back to 2.61 or delete /su/xbin_bind in 2.62
[SuperSU] sash11:
Systemless root brings no benefit for your N4 since there is no Android Pay or Marshmallow. I wouldn't even bother with it. Just stay on latest stable 2.46 SU.
[SuperSU] NYLimited:
Android Pay runs fine on the N4 with 5.1.1 (as long as you're not rooted)
[SuperSU] Alxoom33:
If you want to use Systemless Root with Android Pay you will need to delete the /su/xbin_bind folder after flashing the 2.62.zip or use version 2.61
[SuperSU] JimSmith94:
I have done this with 2.61, 2.62, and 2.62-3 and still can't get Android Pay to work. I didn't wipe system though, and I hate the thought of doing so.

I'd like to get it working by the end of the month so I can get this $20 offer: http://www.google.com/nexus/tap/
[SuperSU] david.degraw54:
I have also tried wiping /system and re flashing my rom (UberMallow) then SuperSU 2.61 and still can't get Android pay to work. Do I have to be on stock? Maybe something like purenexus? I also am using Phasma kernel
[SuperSU] jcsww:
Custom ROM's are almost always pre-rooted. Your best bet would be to inquire in the thread for your ROM and possibly even the kernel, as some kernels are modified. I would say that the ROM or the kernel is why you can't get Android Pay to work.
[SuperSU] Alxoom33:
So you might want to follow all of the directions.
[SuperSU] rquinn19:
I'm having Android Pay issues as well. Completely stock. Installed TWRP, didn't install root. Setup Android Pay no issues. Installed 2.63 and went into Android Pay and all seemed OK still till I went to add another card and I couldn't.
[SuperSU] andresee:
Just tried ANDROID Pay and it wasnt working for me. I used it Monday. Just seeing if any one else has noticed anything. I wonder if google is detecting systemless root now. Will report back if I figure anything out.
[SuperSU] szale9001:
Is your SuperSU mount binding xbin? That will definitely break Pay.
[SuperSU] Ketawa:
Seriously? The fix for this has been pointed out multiple times in the last few pages and is in the third post of the SuperSU WIP thread.
[SuperSU] Ketawa:
I was just incredulous that you haven't didn't search the thread or read the last few pages before posting your question. I just added a new card in Android Pay by implementing the fix mentioned countless times in this thread and the WIP thread. Then I verified it was the correct fix by reinstalling SuperSU 2.62-3; Android Pay would no longer add another credit card. Then I implemented the fix again and I could add a card. It's the correct fix.
[SuperSU] andresee:
Adding the card was not the issue it was using it.... I was able to add the card but not able to use it . And like i said it worked monday

---------- Post added at 03:05 PM ---------- Previous post was at 02:50 PM ----------

I reflashed system and su and made sure xbin mount wasnt used. Will test again. I know I wasnt using it before but just to be safe I did it all again.

Thanks
[SuperSU] Wehdota:
So I've uninstalled Xposed and my Emoji switcher app, as it says it modifies system files. Whenever I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can?

EDIT: I am dumb. I wasn't running my file explorers with root permissions. Did that, deleted no problem.
[SuperSU] Ingenium13:
Reboot. For some reason my phone started failing SafetyNet yesterday, and I thought Google finally updated it. I rebooted though and it started passing again.

SafetyNet has a range of tests it does, one of which is checking a set of random running processes, so it's possible it saw some root app that triggered it. You can lookup how it works, it's pretty comprehensive.

You can use the app "root checker" to see if you pass or not. Usually you have to run it a second time for the SafetyNet check to show up.

Sent from my Nexus 6P