One of the biggest reasons why I used systemless root and stock Android was so that I could use Android Pay. All was fine and dandy for the longest time, I was passing the checks regularly.
Sometime between yesterday and last week, Safetynet Playground has been telling me I failed to pass the test. When I uninstall systemless root SuperSU it goes back to green for me. This seems to indicate that Google has updated Safetynet to detect systemless root.
For those who might not know: No there was no need to disable root before using Android Pay. No, disabling it now does not help. Yes, this worked, and I've been using it for a while now.
Can anyone else confirm this for me?
formula91 said:
One of the biggest reasons why I used systemless root and stock Android was so that I could use Android Pay. All was fine and dandy for the longest time, I was passing the checks regularly.
Sometime between yesterday and last week, Safetynet Playground has been telling me I failed to pass the test. When I uninstall systemless root SuperSU it goes back to green for me. This seems to indicate that Google has updated Safetynet to detect systemless root.
For those who might not know: No there was no need to disable root before using Android Pay. No, disabling it now does not help. Yes, this worked, and I've been using it for a while now.
Can anyone else confirm this for me?
Click to expand...
Click to collapse
I can still add cards to android pay. I used SuperSU 2.64 and removed /su/xbin today and had no issues. Just tried that app too and I passed.
Keithn said:
I can still add cards to android pay. I used SuperSU 2.64 and removed /su/xbin today and had no issues. Just tried that app too and I passed.
Click to expand...
Click to collapse
Are you on 6.0.1?
And could you clarify what you mean by removing /su/xbin? I see no such folder.
There isn't a /system/su folder
There is an /su/xbin_bind folder though.
Super edit: deleted /su/xbin_bind
Y I no read SuperSU post?
I thought it wouldn't cause problems. My bad
Related
I am running on stock rooted OF8 and can't seem to run android pay. Setting it up it says that it can't determine if it is compatible. Google wallet did work before. Anyone else run into this?
Apparently it doesn't work on rooted phones. Read some where that you can activate it and then root afterwards but haven't tried it yet.
Sent from my SM-G928T using Tapatalk
works for me non root for now
Were i can find android pay ?
It worked for me non rooted at a vending machine. Though rooted or not at Maverick and Smiths, (3 times total) it has caused my phone to freeze after I verify my pattern lock.
Anyone having that issue?
Haven't been even able to set it up. Rooted on OF8. I'm going to flash the new build tonight and see if I can get it working before I root again and see what happens.
Use an app like RootCloak or HideMyRoot. Once you hide root you can add your cards with no problems. Using it to pay you will need to hide root again.... way too many steps for it to be convenient for me.
shoresteve626 said:
Use an app like RootCloak or HideMyRoot. Once you hide root you can add your cards with no problems. Using it to pay you will need to hide root again.... way too many steps for it to be convenient for me.
Click to expand...
Click to collapse
Where can I get a working version of either of those apps? All the ones I found doing a Google search are outdated and people say they don't work anymore.
I use Hide My Root from the PlayStore. It worked for what i needed but you cant use it for individual apps like RootCloak can. I'm odexed and can't get RootCloak going.
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot
Worked for me today at mcdonalds i unrooted so i can update to get samsung pay.
I take it your Knox wasn't tripped with your root?
M9x3mos said:
I take it your Knox wasn't tripped with your root?
Click to expand...
Click to collapse
No
Hey all, I am running stock US unlocked Rom 1.80.617, rooted, s-off, Verizon radio, and Android pay was working fine. Just went to use it and said it couldn't work on this system,... Yada yada.. The only thing that has changed between the last time and this time I used Android pay was that I updated to SuperSU 2.76 through Android play store and I updated AdAway through xda labs. Can someone explain to me why either of those updates would have broken AP or could it be something else? Also, is there any easy way to check if I still have systemless root? Assuming I would do that with an ADB command. Can I run the command in a terminal emulator on the phone? Don't really want to boot up the computer of I don't have to. Thanks in advance.
changed permissions of /su/bin to 751 and safetynet checker passes.. . Assume that means AP will work. Will purchase something and report back. Still unsure why AP worked before then randomly quit.
Edit: OK, safetynet checker didn't pass when i reran it, seems random when it passes or not. Anyone have any ideas?
Light1984 said:
Hey all, I am running stock US unlocked Rom 1.80.617, rooted, s-off, Verizon radio, and Android pay was working fine. Just went to use it and said it couldn't work on this system,... Yada yada.. The only thing that has changed between the last time and this time I used Android pay was that I updated to SuperSU 2.76 through Android play store and I updated AdAway through xda labs. Can someone explain to me why either of those updates would have broken AP or could it be something else? Also, is there any easy way to check if I still have systemless root? Assuming I would do that with an ADB command. Can I run the command in a terminal emulator on the phone? Don't really want to boot up the computer of I don't have to. Thanks in advance.
Click to expand...
Click to collapse
Well you screwed yourself. Adaway modified system, Android pay will not work on a modified system. That's why it require systemless root to work
Behold_this said:
Well you screwed yourself. Adaway modified system, Android pay will not work on a modified system. That's why it require systemless root to work
Click to expand...
Click to collapse
But I used Android pay fine with AdAway for a while right after you posted the 1.80.617 RUU. Installed AdAway from XDA labs and updated if through labs as well. Honestly just seemed to randomly stop working.
So if AdAway is the culprit, is there an app with similar functionality that doesn't break AP (xposed is obviously out cause it breaks AP)?
Light1984 said:
But I used Android pay fine with AdAway for a while right after you posted the 1.80.617 RUU. Installed AdAway from XDA labs and updated if through labs as well. Honestly just seemed to randomly stop working.
So if AdAway is the culprit, is there an app with similar functionality that doesn't break AP (xposed is obviously out cause it breaks AP)?
Click to expand...
Click to collapse
Installing adaway isn't the problem. using ad away is the problem. As soon as you apply ad blocking adway modifies your host file. At that point system has been modified and Android pay will fail.
Behold_this said:
Installing adaway isn't the problem. using ad away is the problem. As soon as you apply ad blocking adway modifies your host file. At that point system has been modified and Android pay will fail.
Click to expand...
Click to collapse
But I updated host files as soon as I installed AdAway when I clean flashed the 1.80.617 RUU you provided. It worked after that on two occasions, would it fix it if I change where the host file is saved (after a clean install before applying updated host files of course)? I think that's an option in AdAway, you can move it into \data.
Light1984 said:
But I updated host files as soon as I installed AdAway when I clean flashed the 1.80.617 RUU you provided. It worked after that on two occasions, would it fix it if I change where the host file is saved (after a clean install before applying updated host files of course)? I think that's an option in AdAway, you can move it into \data.
Click to expand...
Click to collapse
Yeah, i would think that should.
If anyone else is following this I believe google has changed something to kill AP with root again. I've been following another thread (for a different phone) and it seems others have experienced the same thing.
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659/page43
Need help! Don't know if it's been answered. I've checked and haven't going anything. I've tried the chmod 751 in terminal and everything systemless and nothing has worked. Echo command did nothing.
It got patched yesterday. AP doesn't work anymore on rooted devices. Not sure if it's against the rules to link reddit but check r/android for updates like this
katsumex said:
It got patched yesterday. AP doesn't work anymore on rooted devices. Not sure if it's against the rules to link reddit but check r/android for updates like this
Click to expand...
Click to collapse
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?
It should work with systemless root, but you have to disable xposed.
lparcshinoda said:
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?
Click to expand...
Click to collapse
So if you haven't purchased anything yet, try to. It probably won't work. It fails on two parts, me trying to add a credit card after a factory reset and when I had the credit card on it and tried using a touch pay thing.
daClaus said:
It should work with systemless root, but you have to disable xposed.
Click to expand...
Click to collapse
As @katsumex stated, it was patched.
Thread here if you're curious: http://forum.xda-developers.com/oneplus-3/help/oos-3-2-2-safetynet-t3427833
Works fine systemless without xposed enabled
Thanks a lot guys. Well I am systemless and it did t work and this was before the patch. Also don't have exposed and still didn't work. Guess I'll be waiting for a newer setup. Urghhh. To root or not to root?, in the name of Android Pay!!!
lparcshinoda said:
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?
Click to expand...
Click to collapse
Any specific steps to set it up? I mean I am systemless and I don't have Xposed. Still nothing. Maybe I forgot to set something.
SuperSU v2.76 on 3.2.1 stopped working for me yesterday. Have over 20 transactions where it has. According to the play store the app itself last updated 11th July. And I have transactions done after. So whatever's changed is not on the app.
Btw, i will try systemless and report back.
TheLoverMan said:
Works fine systemless without xposed enabled
Click to expand...
Click to collapse
Not anymore.
Correct. The safetynet check no longer passes. The check is performed server side, so there is really no way to work around it at the moment, unless you fully unroot of course. So, even a fully proper systemless root method will fail. Oh well. I have never, nor ever will most likely, use Android Pay anyway. Lol. I was just curious why it wasn't working...so apparently Google has caught on for now. This goes for all phones too, not just the OP3. Good luck!
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Nblufire12 said:
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Click to expand...
Click to collapse
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
sb1893 said:
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
Click to expand...
Click to collapse
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Nblufire12 said:
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Click to expand...
Click to collapse
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
sb1893 said:
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
Click to expand...
Click to collapse
is your build.prop edit still working on oreo for og pixel xl 1?
Nblufire12 said:
is your build.prop edit still working on oreo for og pixel xl 1?
Click to expand...
Click to collapse
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
I've been considering switching to the Pixel XL or the 2XL and this is a critical factor for me. From what I gathered from the 2XL forum, this wasn't working. I'm going to see if I can track down if the same Magisk tether module exists for the 2XL. If anyone knows ahead of time, I'd like to know.
Nblufire12 said:
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
Click to expand...
Click to collapse
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
sb1893 said:
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
Click to expand...
Click to collapse
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Nblufire12 said:
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Click to expand...
Click to collapse
I'd recommend following one of the many guides found on XDA. Here is the one I used to get up and running on magisk...you will need to determine which portions of the guide are relevant to your situation and needs.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Good luck!
S
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
scoobysnack said:
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
Click to expand...
Click to collapse
Interesting. I am unable to edit build.prop with Root Explorer (which does have Root Privs). Whenever I open the file for edit in Text Editor within Root Explorer, it allows me to edit the file, but when I "Save Changes and Exit" or "Save Changes" and then exit...those changes are not retained. The timestamp on the build.prop file is unaltered as is the file size. I wonder what the difference is that allows you to edit your build.prop but prevents me from changing mine...I have poked around on the forums and the magisk threads and haven't been able to figure it out. I stopped researching when I discovered the ability to insert those settings at boot time via the magisk modules and decided that was a viable solution (maybe better as it leaves build.prop stock and unchanged.)
Thanks,
S
I click "Save Changes" then I click "Save and Exit" it will say the original file is name .bak
New to the Pixel Xl and in the past have always run custom roms on my phone. Currently running Pie pure stock but rooted. Running magisk 16.7 with hide enabled. Called verizon on a tech support issue and they tried to blame the issue on me being rooted. How is verizon able to tell I am rooted? Or more to the point how can I block their ability to see I am rooted?
adm1jtg said:
New to the Pixel Xl and in the past have always run custom roms on my phone. Currently running Pie pure stock but rooted. Running magisk 16.7 with hide enabled. Called verizon on a tech support issue and they tried to blame the issue on me being rooted. How is verizon able to tell I am rooted? Or more to the point how can I block their ability to see I am rooted?
Click to expand...
Click to collapse
If you have myverizon app installed, use magisk hide on that. The device health portion of the app has root detection. If you hide my Verizon wish magisk hide, it won't show. Had same issue on sailfish, and tinkered with that, and it did the trick
abranson said:
If you have myverizon app installed, use magisk hide on that. The device health portion of the app has root detection. If you hide my Verizon wish magisk hide, it won't show. Had same issue on sailfish, and tinkered with that, and it did the trick
Click to expand...
Click to collapse
Thanks for the tip, I had uninstalled the my verizon app but upon searching the service remained. So I believe you have solved the mystery. I hid root from that app and should be ok now.
Thanks again... sneaky verizon not uninstalling completely