Develop Bugs

Systemless root 2.66 with android pay

What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.

I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...

smac7 said:
What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.
Click to expand...
Click to collapse
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk

dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked in /system and it's not there. I did however folder called ADDON.D that has Update_SuperSU within it. If i understand correctly, this would set-off the trigger to see system as modified. Is it possible the unSU zip i used (to try to unroot pure nexus) didn't work correctly?

So, apparently i was supposed to go to terminal and enter
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.

smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
If you can add a card you pass the safetynet. You should be ready to use it. Just remember if you do anything else that you can still cause your phone to fail the safetynet and prevent payment even after your cards are added.

I've posted in a Nexus 6P thread, might be helpful though, but I had to disable SuperSU (not Full unroot) in order to get AndroidPay/CapOneWallet/Safetynet to work. And that's after editing build.prop, removing /su/xbin_bind, and installing EX Kernel, using Stock 6.0.1 and SuperSU 2.66 with systemless root.

The folder is located under /su not /system
dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse

bdivs11 said:
The folder is located under /su not /system
Click to expand...
Click to collapse
You're right. I thought it was under /system but it is under /su
Sent from my Nexus 5X using Tapatalk

smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu

2x4 said:
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?

Android Pay is not working on my 5x. I used the MSkip Toolkit's systemless root option, as well as used that Toolkit to unlock, de-encrypt, ect. That was done with I think a temp flash of TWRP so I keep stock recovery?
The only other thing I did to my phone was the build prop edit to enable tethering on Verizon which in the thread people said doesn't break their Android Pay.
Android Pay says cannot verify yadda yadda. I disabled SU in the app, rebooted and AP still doesn't work. Now when I try to re/enable SU fails installing/fails updating binary.
Anyone have any advice? Does some file need to be deleted or a fresh install?

greves1 said:
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?
Click to expand...
Click to collapse
Chainfire (SuperSU dev) is not developing systemless root to be compatible with Android Pay. That was never his aim. Anything he adds is for the purpose of not using /system for root. If you would like to read on changes to SuperSU, I suggest reading the brief changelogs or following his SuperSU beta thread to keep up to date on changes in SuperSu (systemless or otherwise).
Btw, you can flash whichever version of SuperSu you desire. If it is easier to get Android Pay working for you, cool.

I just use 2.61 and it just works with Android pay. No terminal commands or anything

stu5797 said:
I just use 2.61 and it just works with Android pay. No terminal commands or anything
Click to expand...
Click to collapse
Same here. I can't see any reason to "upgrade" since the later versions seem to require additional steps, and for the user I don't seem to get any added value from the later versions.

greves1 said:
I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...
Click to expand...
Click to collapse
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?

tallgrasshawk said:
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?
Click to expand...
Click to collapse
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.

greves1 said:
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.
Click to expand...
Click to collapse
I've done it both ways and it definitely works when you run the terminal commands prior to flashing. I did it wrong (without terminal commands) first, so i had to do "full unroot" from the app itself, then in recovery ran the terminal commands and flashed 2.66 again and now it works fine for me.
You also have to avoid modifying the /system partition after the fact otherwise that will also break android pay, even if you already have a card added.
you can check with this app if android pay will work:
https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground&hl=en
for example, the aggressive doze option on the new greenify beta will break safetynet, as will Adaway (unless you flash the systemless hosts zip first)

newb question
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)

Phssthpok said:
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)
Click to expand...
Click to collapse
Months later but adb/fastboot is the key to for terminal commands to your mobile. Likely you've solved by now but if not, theres an easy way to get adb going: http://www.androidbeat.com/2015/11/how-to-set-up-adb-and-fastboot-on-mac/

Have to flash SU systemless

It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!

No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.

nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.

StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.

@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su

nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.

tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.

nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.

tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su

nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.

No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe

otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.

Xperia Z5 Premium - Magisk Error

Hello everyone
Recently due to Niantic's decision to prohibit root users of playing Pokémon Go I decided to give a try to Magisk. I followed every step and even flashed my ROM again.
But when trying phh's root it wont work. Rootchecker says root was not correctly installed and trying to use any root app won't make Superuser show any prompt for root permissions.
Thank you so much for the help guys.

more info
renezada88 said:
Hello everyone
Recently due to Niantic's decision to prohibit root users of playing Pokémon Go I decided to give a try to Magisk. I followed every step and even flashed my ROM again.
But when trying phh's root it wont work. Rootchecker says root was not correctly installed and trying to use any root app won't make Superuser show any prompt for root permissions.
Thank you so much for the help guys.
Click to expand...
Click to collapse
What is your ROOT Method, That makes a difference since there might be a conflict in ROM (Preinstalled mods or apps), also, What ROM is it?

CKWTHN said:
What is your ROOT Method, That makes a difference since there might be a conflict in ROM (Preinstalled mods or apps), also, What ROM is it?
Click to expand...
Click to collapse
I flash Magisk v6 and phh's on TWRP. On the other hand I use the stock ROM MM 6.0.1 build 32.2.A.0.253

Apparently Magisk doesn't work properly on Sony devices. See topjohnwu's OP in the Magisk thread.
It partially works for me with some apps like Adaway and TiBU requesting for permissions and working properly but with most other apps not requesting root.

benengyj said:
Apparently Magisk doesn't work properly on Sony devices. See topjohnwu's OP in the Magisk thread.
It partially works for me with some apps like Adaway and TiBU requesting for permissions and working properly but with most other apps not requesting root.
Click to expand...
Click to collapse
I don't know how I could have missed that... Thanks a lot for that. I hope it gets a fix soon enough tho.

SafetyNet on Android 7.1.1?

Hello guys, I'm using the stock version of rom 7.1.1, I made the update via OTA today. I would like to know if there is any way to use safetynet in this rom, Magisk was installed without any problems and seems to work very well (with the exception of safetynet).
Can someone help me?

larilieb1793 said:
Hello guys, I'm using the stock version of rom 7.1.1, I made the update via OTA today. I would like to know if there is any way to use safetynet in this rom, Magisk was installed without any problems and seems to work very well (with the exception of safetynet).
Can someone help me?
Click to expand...
Click to collapse
We need the kernel source so we can modify it, until then magisks safetynet won't pass.

Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!

larilieb1793 said:
Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!
Click to expand...
Click to collapse
There's a Netflix app that by pass the root check,I found it on apk mirror.

larilieb1793 said:
Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!
Click to expand...
Click to collapse
I have 7,1,1 stock and magisk with safety net pass, follow this steps:
1. Unistall magiks with the Unistaller Zip via twrp
2. Install magiks 12.0 vía twrp
3. Boot your phone, install magisk manager and check the correct install of magisk
4. install the module universal safety net fix (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431) via twrp
5. DO THIS!! >>> https://forum.xda-developers.com/moto-z-play/how-to/magiks-moto-z-play-t3545473 .
6. Install magisk 13.3 via twrp and the Latest magisk manager
7. Check that the module are actived and run the safety net test
Good luck sorry for my english

larilieb1793 said:
Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!
Click to expand...
Click to collapse
EDIT: Nevermind, saw in other thread you've already sideloaded Netflix apk.

folken2003 said:
I have 7,1,1 stock and magisk with safety net pass, follow this steps:
1. Unistall magiks with the Unistaller Zip via twrp
2. Install magiks 12.0 vía twrp
3. Boot your phone, install magisk manager and check the correct install of magisk
4. install the module universal safety net fix (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431) via twrp
5. DO THIS!! >>> https://forum.xda-developers.com/moto-z-play/how-to/magiks-moto-z-play-t3545473 .
6. Install magisk 13.3 via twrp and the Latest magisk manager
7. Check that the module are actived and run the safety net test
Good luck sorry for my english
Click to expand...
Click to collapse
Wow! Thank you so much, it worked very well here :good:
Thanks for the help guys!

larilieb1793 said:
Wow! Thank you so much, it worked very well here :good:
Thanks for the help guys!
Click to expand...
Click to collapse
Be careful, magisk and magisk hide drain a lot of battery (SO Android) if you don't need safetynet pass dont active the module and magisk hide

Magisk installed on androidO but can't installed modules?

I successfully installed magisk by flash zip in twrp but fail to install modules.Is it because the module isn't for Oreo or because of the magisk framework?

FrostL4 said:
I successfully installed magisk by flash zip in twrp but fail to install modules.Is it because the module isn't for Oreo or because of the magisk framework?
Click to expand...
Click to collapse
How do you istaled my friend share your metod!!!

caballon said:
How do you istaled my friend share your metod!!!
Click to expand...
Click to collapse
I just flashed it through twrp.Maybe it has something to do with kernel elementalx that i have already installed. Even though magisk was successfully installed i can't open the manager sometimes and as you see i can't use any of its modules.
I do hope this will help.

I'm new to XL. From Magisk author in last post of this thread, XL isn't supported
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3
I used Magisk on 6P with Oreo....works great and easy. Not sure if it's ready for XL yet. I still have to unlock and then choose recovery method and root method. Although some are flashing trial TWRP versions, it seems that fastboot TWRP is still safest and mainstream method?
Then to root. It seems Chainfire SU is preferred method and it has SU hide option if you want Android pay? He does say the suhide method is probably temporary...
Do I have this right?

akenis said:
I'm new to XL. From Magisk author in last post of this thread, XL isn't supported
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page3
I used Magisk on 6P with Oreo....works great and easy. Not sure if it's ready for XL yet. I still have to unlock and then choose recovery method and root method. Although some are flashing trial TWRP versions, it seems that fastboot TWRP is still safest and mainstream method?
Then to root. It seems Chainfire SU is preferred method and it has SU hide option if you want Android pay? He does say the suhide method is probably temporary...
Do I have this right?
Click to expand...
Click to collapse
Thanks for your support.
Is there a flashing twrp version for pixel Oreo?Last time i checked there were only fastboot twrp.

FrostL4 said:
Thanks for your support.
Is there a flashing twrp version for pixel Oreo?Last time i checked there were only fastboot twrp.
Click to expand...
Click to collapse
There are some RC versions, but it doesn't sound like they're ready for prime time yet.....like it takes 10 minutes to boot.