Develop Bugs

Safetynet API tripping for systemless root?

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

Android Pay broken, was working.

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

Tethering

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

Unlock, Root, Xposed and then relock

Hi, my Mix2 arrived few days ago and I find MiUI quite nice, yet lacking few things. Those are easily available via xposed, hence I need to root. I'm also not so lucky in these matters so before I start to tinker with it I'd like to learn few things.
What are least dangerous ways to unlock and root phone? (heard sth about magisk, its quite new for me, haven't been rooting phones for couple years now) Is it good?
Suppose I succeed unlocking, rooting and flashing xposed, can I relock bootloader? I want that because ie AndroidPay needs that to work, and I haven't found any working rootcloack or similar (at least on Note2)
How reliable is 'the most official tool' for xiaomi flashing (from eu.xiaomi.com ?)? I mean can it bring back the dead or revert phone back to where I started, without any trace of tinkering?
As a new xiaomi owner are there any critical things I need to know?
Thanks!

If you flash magisk, which is the best thing ever btw, you won't have to relock bootloader to get Android pay working.

yeyeoke said:
If you flash magisk, which is the best thing ever btw, you won't have to relock bootloader to get Android pay working.
Click to expand...
Click to collapse
Thanks, I read about that and intend to use it. Though, there might be some issues with magisk and different versions. What features does it have?
So far, need to wait 3 days to unlock bootloader.

Mighty_Ahti said:
Thanks, I read about that and intend to use it. Though, there might be some issues with magisk and different versions.
So far, need to wait 3 days to unlock bootloader.
Click to expand...
Click to collapse
I've been using magisk on my Note 3 Pro since release and I've never had an issue. Yes, I got my mix 2 today and I'm also waiting for 3 days..

Mighty_Ahti said:
Hi, my Mix2 arrived few days ago and I find MiUI quite nice, yet lacking few things. Those are easily available via xposed, hence I need to root. I'm also not so lucky in these matters so before I start to tinker with it I'd like to learn few things.
What are least dangerous ways to unlock and root phone? (heard sth about magisk, its quite new for me, haven't been rooting phones for couple years now) Is it good?
Suppose I succeed unlocking, rooting and flashing xposed, can I relock bootloader? I want that because ie AndroidPay needs that to work, and I haven't found any working rootcloack or similar (at least on Note2)
How reliable is 'the most official tool' for xiaomi flashing (from eu.xiaomi.com ?)? I mean can it bring back the dead or revert phone back to where I started, without any trace of tinkering?
As a new xiaomi owner are there any critical things I need to know?
Thanks!
Click to expand...
Click to collapse
It's generally considered to be dangerous to relock a bootloader with anything other than perfectly stock/factory firmware installed. It may be ok to do this technically but it sort of "ties your hands" in some ways after making an unofficial modification and makes it a bit harder to recover from a botched situation.
You can have an unlocked bootloader and still use Android Pay. This can be achieved either with a ROM that is built to accomplish this (Epic ROM is an example of this) or by using Magisk, which allows root without any sort of SafetyNet trip in many cases. I don't believe there's *any* way to install Xposed and also use Android Pay or any other SafetyNet apps...the best alternative if you really want Xposed is to use Magisk and then install the Xposed Magisk module...you still can't pass SafetyNet with this setup but Magisk allows you to disable Xposed if you're willing to uncheck it in the Magisk Manager app and reboot the phone, after which time SafetyNet should pass ok...at least with this setup you'll be able to kind of have your cake and eat it too, though it's not ideal as you'll have to reboot if you want to change the status of Xposed.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

Thank you for detailed answer. I didn't know that.
flyer_andy said:
the best alternative if you really want Xposed is to use Magisk and then install the Xposed Magisk module...you still can't pass SafetyNet with this setup but Magisk allows you to disable Xposed
Click to expand...
Click to collapse
I tried AndroidPay few times past few days and it didn't work at all. Perhaps terminals were not compatibile. So lets say I gave up on AndroidPay - can I use regular Xposed along with Magisk? Or does it have to be that module?

Mighty_Ahti said:
Thank you for detailed answer. I didn't know that.
I tried AndroidPay few times past few days and it didn't work at all. Perhaps terminals were not compatibile. So lets say I gave up on AndroidPay - can I use regular Xposed along with Magisk? Or does it have to be that module?
Click to expand...
Click to collapse
Oh! I think I may be able to help you with the Android Pay issue - my phone didn't work right with Android Pay until I made sure *all* Google apps' permissions were allowed via the Apps menu in Settings (along with "Autostart" via the security app)...and also toggled the NFC setting where it lets you select between "embedded secure element" and "HCE Wallet." It probably is on "HCE Wallet" but try toggling to "embedded secure element" and then back to "HCE Wallet" a couple of times. My Mix 2 would not make a terminal connection until I did this...it would just say "card read error." Seems like a firmware bug. Let me know if that helps!
But yeah if you don't want to use Android Pay then normal Xposed should be fine...you wouldn't need Magisk I don't think. Though, I'm not sure but I think the Magisk Xposed module probably functions the same as normal Xposed so I'm not sure there's an advantage in doing so. But of course it's all about personal preference!

Whoah, I'm still new to xiaomi/android7+ policies, where each app's permissions are reduced to bare minimum (messenger not being able to show notifications for example). I will definitely try this tomorrow.
So far I just managed to unlock BL, flash recovery and install magisk. SafetyNet checks ok. Will try xposed tomorrow after some payments ;D Thanks!

HCE wallet worked for me (I had it set to SIM wallet).
If I understand correctly here is the possible solution to xposed+magisk+androidPay.
I'd need phh's su binaries for that and keep crossing fingers for it to work on 7.1
I need to learn more about that stuff before I break something

So as I was expecting I experience troubles in installing Xposed.
I followed official way as in here And got bootloop.
I removed magisk stuff in recovery and fixed bootloop, then installed v89.0 (not .1) and also bootloop.
Im using SDK25, and miui 9 - 7.1.1 so it should be ok I think

Mighty_Ahti said:
So as I was expecting I experience troubles in installing Xposed.
I followed official way as in here And got bootloop.
I removed magisk stuff in recovery and fixed bootloop, then installed v89.0 (not .1) and also bootloop.
Im using SDK25, and miui 9 - 7.1.1 so it should be ok I think
Click to expand...
Click to collapse
Disable hooks from the xposed apps settings before flashing xposed

What hooks? I dont have any modules yet

Mighty_Ahti said:
What hooks? I dont have any modules yet
Click to expand...
Click to collapse
It's a toggle in the settings under experimental, disable resource hooks

Boot took longer but it works. Thanks! Do I have to keep it on all the time ?

Mighty_Ahti said:
Boot took longer but it works. Thanks! Do I have to keep it on all the time ?
Click to expand...
Click to collapse
Yeah, phone won't boot with it on. Don't think it makes much difference anyway

Hi @Mighty_Ahti, how much time was "longer"? it's been loading for over 5 minutes already. Thanks

Certainly below 5 minutes.

Google PAY with unlocked bootloader and root

Hello
Is there any possibility to use Google Pay on rooted device with unlocked bootloader?
I have used magiskhide, but my device still can't pass safetynet test.
Any ideas?

Yes mines working fine with oos,unlocked and rooted

ok, thanks for reply!

make sure you are using the latest magisk zip and apk, it should pass the safety net

Magisk, SuperSU won't work

I have disabled xposed and now works great.
So xposed was generating problem, not rooted device with unlocked bootloader.

pawel.bohdal said:
I have disabled xposed and now works great.
So xposed was generating problem, not rooted device with unlocked bootloader.
Click to expand...
Click to collapse
Xposed breaks safteynet

So rooting and unlocking my device but still using original ROM won't break hce payment???

mobidea said:
So rooting and unlocking my device but still using original ROM won't break hce payment???
Click to expand...
Click to collapse
yes, but you need to use magiskhide to hide root from google pay

pawel.bohdal said:
yes, but you need to use magiskhide to hide root from google pay
Click to expand...
Click to collapse
but I won't be able to upgrade ROM in official way?

mobidea said:
but I won't be able to upgrade ROM in official way?
Click to expand...
Click to collapse
OTA works with root and unlocked bootloader

pawel.bohdal said:
OTA works with root and unlocked bootloader
Click to expand...
Click to collapse
Hmm ok, but as i know flashing custom recovery is mandatory to root. I'm new on OnePlus but in my previous cells flashing TWRP made it impossible to OTA works (because of TWRP not a original kernel).

Hi guys,
I have found a method to run google pay with,
Xposed - active
Magisk - cts profile - false, basic integrity - false
No need to install magisk hide or shell hide.
Just a simple trick.
Video uploaded on youtube.
https://youtu.be/DV_XmlJDi2o

Why not just tell us here instead of a YouTube link?

Go to settings -> application list -> google play services -> permissions -> DISABLE PHONE PERMISSION
This works for me. Try it once.

On some Pie ROMs, it doesn't work even after passing SafetyNET and hiding root using MagiskHide. The only option here is denying the Telephone permission for Play Services and re-enable when you're done. You'll have to do this everytime you need to make a payment.
I created a Tasker module to do this everytime I launch the app. Just run the shell command in Tasker:
To disable permission:
Code:
pm revoke com.google.android.gms android.permission.READ_PHONE_STATE
To enable permission:
Code:
pm grant com.google.android.gms android.permission.READ_PHONE_STATE

yeah I have an essential ph1 and android pay will run on it just fine (pie/magisk hide) yet will not run on my oneplus 6t with stock oos/pie/magisk hide. but I'll use the telephone permission trick if I ever need to use it.

pawel.bohdal said:
Hello
Is there any possibility to use Google Pay on rooted device with unlocked bootloader?
I have used magiskhide, but my device still can't pass safetynet test.
Any ideas?
Click to expand...
Click to collapse
Do you know if google pay still works then?

Didn't want to necropost, but I'd like to know if google pay still works with 9.0.9 and unlocked bootloader/root.

hornedfiend said:
Didn't want to necropost, but I'd like to know if google pay still works with 9.0.9 and unlocked bootloader/root.
Click to expand...
Click to collapse
Yes, works still flawlessly