Database Users

Factory reset - locked bootloader - safetynet fails

Some history with the phone. I've gone back and forth a few times with this phone. At one point the bootloader was unlocked, I was rooted, etc etc. This was quite a while ago. Since then I have flashed the factory rom, locked the bootloader and ran 100% pure stock until this morning and everything worked just fine. Android Pay worked, etc. Today I decided I'd do a factory reset and not bother restoring data. Prior to doing that, I decided to give Magisk a quick try just for the heck of it. I flashed the current Oreo factory image (With Sept security patches) left the bootloader unlocked, flashed TWRP, installed Magisk via TWRP. Didn't really give it much of a chance but either way, after a quick check safetynet failed. So I figured, whatever no big deal. I flashed the factory image again, then relocked the bootloader, and eventually rebooted and signed back into my account and didn't bother restoring any backup. Let all the stock apps install/update, checked Android Pay.....and it wouldn't allow me to add a card. I checked the Safetynet tests and it fails the CTS Profile match. I'm pretty much at a loss now as to what in the world the problem is. The phone is fresh off of a factory reset and the bootloader is locked. No magisk, no root, nothing.
Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.

Well I unlocked the bootloader again, flash the August 7.1.2, relocked the bootloader, and after updating apps and Google Play Services, all is well again. Guess I'll just grab the OTA and go from there.

Wow, so sideloading the OTA broke it again.

Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.

glad someone else is seeing this, sideloaded OTA build 017 and Android Pay stopped working with it failing Safetynet's CTS Profile check

ParadingLunatic said:
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
Click to expand...
Click to collapse
Where is this 019 OTA? I'm having this same problem. I thought I was the Andromeda I tried but I knew that was rootless.
Thanks for shedding light on this.
---------- Post added at 07:45 PM ---------- Previous post was at 07:35 PM ----------
Did some more digging. Found it. Gonna see if it works.
Sent from my Nexus 6P using XDA-Developers Legacy app

ParadingLunatic said:
... Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Click to expand...
Click to collapse
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.

stevemw said:
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
Click to expand...
Click to collapse
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.

ParadingLunatic said:
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
Click to expand...
Click to collapse
Didn't realize it was automatically set in Oreo. I went thru 7 and the preview, so this option was already set. I will be getting the Pixel 2 XL, so it's something for me to check on.

Android Pay Not Working Lineage OS 14.1 passes safetynet

Hey Folks!
Hope someone can help me out here. I've read a whole bunch of forums and have tried a number of potential solutions to no avail. I have Magisk 15.2 installed and am running Lineage OS 14.2. Multiple apps confirm I pass Safetynet and I can successfully add a card to Android Pay. However, when I try to pay at a terminal, nothing happens. I have tried multiple terminals with no success. Nfc is enabled and android beam works.
Thanks!!!

Try enabling Core Only Mode in Magisk settings, try disabling systemless BusyBox, or try uninstalling your version of Magisk and trying the latest beta. SafetyNet is a nightmare to keep up with. Every time it updates, Magisk gets broken and we have to wait for a new update. Unfortunately, the only real solution is to stop using SafetyNet-dependent apps or keep a locked bootloader/unrooted phone. Or perhaps have one phone for custom ROM stuff and another one for SafetyNet stuff. :/ This is why I'm so vocal about ROMs passing SafetyNet. Hopefully you'll find a fix.

Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?

lastconfederate2 said:
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
Click to expand...
Click to collapse
You don't get an error message or anything? Sorry, I missed that. Not sure what the issue is, then. I assume by the other apps, you mean legit apps that actually check for SafetyNet, like downloads in Netflix, a game like Fire Emblem Heroes or a banking app like RBS. If you're able to use those apps or use all of the features perfectly, the issue might just be Android Pay, which probably now detects Magisk(?). Anyway, unless you're actually able to use an app that uses SafetyNet, those SafetyNet checkers don't count for much.

Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.

lastconfederate2 said:
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
Click to expand...
Click to collapse
I am experiencing the same issue but with Omni 7.1 and Magisk 15.2.
Card was added but giving "Card read error" at payment terminal.

If changing the settings or flashing a beta build doesn't get it to work, then I'm not sure what will. If you're able to, backup your existing ROM and factory reset it. If your Pro3 variant has an official LeEco ROM that passes SafetyNet natively, flash that and lock the bootloader and set up Android Pay to see if it works. Can't offer much else to help you, sorry.

Might be nothing to do with your problem, but i noticed when using nfc to add contacts with other nfc phones etc, that this phone has its nfc chip at the bottom/middle of the phone (it was a while ago, hope I've not remembered incorrectly). Until i realised this i had problems getting it to work.
Edit.. my memory is so bad in now thinking it was the very very top of the phone. Try both.

Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!

lastconfederate2 said:
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
Click to expand...
Click to collapse
Are you still able to get it to work like this? What was the last update you installed? I am trying to do some research to figure out why this happens on many different devices with different roms and such. Most seem to have the ability to get Pay to work and load cards into it, but using at stores and tapping the terminals does nothing(currently my issue).
So what is you setup as of now? Magisk ver, universal safetynet fix(if you're using that) ver, OS ver/date, and what security patch?
If you can provide those things it would be helpful.
Thank you.

Yes, that is still how it works, though I've found over time that it works more like 25% of the time. The last LOS update I have installed is February 10th. I'm using Magisk 15.3, running Android 7.1.2, and last security patch is 1/05/18.
Thanks!

Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506

wkwk said:
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
Click to expand...
Click to collapse
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en

tsongming said:
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
Click to expand...
Click to collapse
Yes same issue.

Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.

lastconfederate2 said:
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
Click to expand...
Click to collapse
It will probably work in Lineage 14.1 once its been updated for the newer api.

Magisk + Google Pay

Hi,
I have a issue with Google Pay,
first of all I've made a succeful contact-less payment while BL was locked (linked paypal to g pay), but now after unlocking BL and flashing Magisk - I can't, it gives me an error on terminal 'Transaction rejected'
Ofc SafetyNet test passes, and google play store sees my phone as certified device;
Google play services, google pay, google play, paypal and phone are hidden in magisk manager.
So the question is - Have somebody made a succeful contact-less payment with unlocked BL on our OP6T?
Thanks!

it works here perfectly fine using magisk 17.3
Pokemon Go works also (and everything else)

I use Gpay everyday no issue

My op6t is also unlocked and root via magisk and I face the same problem, it worked the first time but now I keep trying to gpay in each store but it fails every time.

I'm using gpay on daily basis, I didn't need to hide it in magisk but you can try to clear gpay/paypal cache or reinstall it.
I'm on OOS 9.0.7 with Magisk 18.0

Yep, got the phone the day it came out, rooted it 5 minutes after it arrived, used pay every day since, never hid anything in magisk. I know that's little help but at least you know you've something going on with your specific configuration. I'm .7 with Magisk 18.0.

I've been using Google Pay on my phone every day since launch with unlocked Bootloader and Magisk. I never had a problem. Magisk 18 and OOS 9.0.7 right now.

Same here no issue with GPay linked with my Revolut credit card

And I have been using gpay with Magisk without issues. Bootloader is unlocked.

Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
OnkeIM said:
it works here perfectly fine using magisk 17.3
Pokemon Go works also (and everything else)
Click to expand...
Click to collapse
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
Sent from my [device_name] using XDA-Developers Legacy app

unlocked bootloader + root works always for me with this config:
- Magisk 18.0
- marked needed apps in "Magisk Hide"
- use " change Magisk package name"-option in settings
- install Magisk modul "MagiskHide Props Config"
- modul needs to setup in a terminal/console-app (open terminal, type "props" , follow option 1)
works for for me on Pokemon, GooglePay, Ingress and other all other apps that didn't started due root detection

Flakito97 said:
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
main reason should not be Pokemon Go since it is a multiplayer game...
The only thing i always do is
1. Change package name from magisk
2. Activate desired app in magisk hide
It always worked with every app I tried like Telekom App or Banking App.
Right now I don't have root anymore, I got my 6T replaced because of a dead pixel and currently don't want to increase my widevine level

OnkeIM said:
main reason should not be Pokemon Go since it is a multiplayer game...
The only thing i always do is
1. Change package name from magisk
2. Activate desired app in magisk hide
It always worked with every app I tried like Telekom App or Banking App.
Right now I don't have root anymore, I got my 6T replaced because of a dead pixel and currently don't want to increase my widevine level
Click to expand...
Click to collapse
Gotcha, well yes I did those but no luck.
No worries. Thanks for the response!
Sent from my [device_name] using XDA-Developers Legacy app

Randomly today without any change or update to my OnePlus 6t Google Pay told me "you can no longer use Google Pay in stores." My CTS match is good everything looks fine. Did they patch anything recently?
Sent from my ONEPLUS A6013 using Tapatalk

xlxcrossing said:
Randomly today without any change or update to my OnePlus 6t Google Pay told me "you can no longer use Google Pay in stores." My CTS match is good everything looks fine. Did they patch anything recently?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I am seeing the same error starting last night and continuing into today.

alryder said:
I am seeing the same error starting last night and continuing into today.
Click to expand...
Click to collapse
Well at least I'm not alone which tells me they patched the CTS exploit...guess we will have to wait for a possible magisk update.
Sent from my ONEPLUS A6013 using Tapatalk

Before I begin this is just a workaround but works flawlessly and you will be able to use google pay again. uninstall the current version of google play services and google pay. You want to be on the previous version of google pay.. Then Google search previous version of google play services (I believe its 14.7.99). Install then restrict background data on both google play store and google play services and all will work great... Do not update either until magisk comes out with an update that will work with the latest play services update versions... This was driving me crazy until I gave this a try after all else failed... Have Fun Spending your Money!!!lol

anthony10126 said:
Before I begin this is just a workaround but works flawlessly and you will be able to use google pay again. uninstall the current version of google play services and google pay. You want to be on the previous version of google pay.. Then Google search previous version of google play services (I believe its 14.7.99). Install then restrict background data on both google play store and google play services and all will work great... Do not update either until magisk comes out with an update that will work with the latest play services update versions... This was driving me crazy until I gave this a try after all else failed... Have Fun Spending your Money!!!lol
Click to expand...
Click to collapse
Which version of Google Pay are you using? I got 2.84.237487748 and it's still working for now. At least the app opens normally & hasn't told me I can't use it. I haven't actually tried paying for something in a few days. And I think I just updated the GPay app within the last week.
FWIW, I'm still using Magisk 17.3 on OOS 9.0.12. With Magisk 18.x, Magisk Hide would stop working, SafetyNet checks would fail and the device would become uncertified. I've had no such issues with 17.3. Although I don't know if any of those things would cause Google Pay to stop working because even with those things happening, Google Pay has never stopped working for me. But now that I've said that, it'll probably will in 3, 2, 1....

sharksfan7 said:
Which version of Google Pay are you using? I got 2.84.237487748 and it's still working for now. At least the app opens normally & hasn't told me I can't use it. I haven't actually tried paying for something in a few days. And I think I just updated the GPay app within the last week.
FWIW, I'm still using Magisk 17.3 on OOS 9.0.12. With Magisk 18.x, Magisk Hide would stop working, SafetyNet checks would fail and the device would become uncertified. I've had no such issues with 17.3. Although I don't know if any of those things would cause Google Pay to stop working because even with those things happening, Google Pay has never stopped working for me. But now that I've said that, it'll probably will in 3, 2, 1....
Click to expand...
Click to collapse
I downgraded Google pay to 2.81. If you haven't used you're Google pay in the past few days chances are you're Google pay is not working. Google play services updates in the background without you knowing which is why I suggested turning off background data.. staying on magisk 17 shouldn't make a difference..

Even with only an unlocked bootloader it won't let you set up google pay (no twrp, no magisk, no root, just unlocked bootloader).

OP6T. Google Pay not working with latest A10 OB

Hey! I know that some people are facing the issue with Google pay, I faced it as well. Google pay says that my device doesn't meet the software requirements. Before update I had latest Android 9 open beta installed. I don't want to rollback, so I'm seeking for a solution. Can the issue with gpay be resolved?

We need to wait for OnePlus/Google to fix it, I saw some weird crashes in the logcat during the boot process, for me doesn't work even with the bootloader locked.

a_korshun said:
Hey! I know that some people are facing the issue with Google pay, I faced it as well. Google pay says that my device doesn't meet the software requirements. Before update I had latest Android 9 open beta installed. I don't want to rollback, so I'm seeking for a solution. Can the issue with gpay be resolved?
Click to expand...
Click to collapse
For me it is working.
Also, Oneplus reported on their forum Google Pay not be working for most of the time.
we need to wait a bit for having a fix. :crying:
For more information about it, head over to the forum, :fingers-crossed:
https://forums.oneplus.com/threads/...a-1-for-the-oneplus-6-and-oneplus-6t.1120323/

It was working for me for a half day on the A10 then suddenly started saying it doesn't meet the security standards.
Just to explain better, the application opens and it's not blocked. Just when you try to pay it says with red exclamation the device doesn't meet the security standards etc. So the payments do not work via nfc

Why I didn't read the "Known Issues" part before switching? My Google Pay doesn't work but I also don't feel like loosing my data... Lessons learned I guess...

Fully working on my side. On 10 beta thread i post the steps i followed. Nothing special btw.

Worked for me for around a day but stopped working for me too.
Guess it'll be fixed soon. Just have to remember to carry my wallet.

stefr07 said:
Fully working on my side. On 10 beta thread i post the steps i followed. Nothing special btw.
Click to expand...
Click to collapse
Did you try to pay with nfc, where you put the phone next to a terminal ? And are you sure you have OnePlus 6T and not just 6 ?
Try to pay today .
If it still works please post the steps here .

PAGOT said:
Did you try to pay with nfc, where you put the phone next to a terminal ? And are you sure you have OnePlus 6T and not just 6 ?
Try to pay today .
If it still works please post the steps here .
Click to expand...
Click to collapse
Yes and I have already used gpay 3 times. So it's quite strange if nobody can have it, I know ..
Maybe in that way it could be fine for you too :
- flash a boot_patched like explain in ob1 theead
- clean cache and storage for play store and Google service and maybe do the same with gpay if you have already try to activate it
- safety patch should be useless but i activate it too
- hide Google service
Then you might configure gpay with success

stefr07 said:
Yes and I have already used gpay 3 times. So it's quite strange if nobody can have it, I know ..
Maybe in that way it could be fine for you too :
- flash a boot_patched like explain in ob1 theead
- clean cache and storage for play store and Google service and maybe do the same with gpay if you have already try to activate it
- safety patch should be useless but i activate it too
- hide Google service
Then you might configure gpay with success
Click to expand...
Click to collapse
So if I understand you correctly, you installed a hacked boot.img and that is how you are saying it works ?
I am on stock I do not want to install custom boot.img, root or magisk modules.
Clearing Google Services would cause my Watch to be deleted so that will not work for me too.
I guess I will have to wait for an official way/fix.

GPay works
Without any update, OnePlus just certified our beta.
Need to:
1) clear cache and data GPay
2) clear cache and data of Google Services
3) Reboot your phone
4) Setup GPay

coxik154 said:
GPay works
Without any update, OnePlus just certified our beta.
Need to:
1) clear cache and data GPay
2) clear cache and data of Google Services
3) Reboot your phone
4) Setup GPay
Click to expand...
Click to collapse
The step 2 is a big No Go for me.
I do not wanna lose my settings and my watch ....
Are you sure its mandatory?
---------- Post added at 03:01 PM ---------- Previous post was at 02:07 PM ----------
PAGOT said:
The step 2 is a big No Go for me.
I do not wanna lose my settings and my watch ....
Are you sure its mandatory?
Click to expand...
Click to collapse
Okay tried without the step Nr.2 and I was able to pay via Gpay.

coxik154 said:
GPay works
Without any update, OnePlus just certified our beta.
Need to:
1) clear cache and data GPay
2) clear cache and data of Google Services
3) Reboot your phone
4) Setup GPay
Click to expand...
Click to collapse
I can also confirm that this works!

Phoenix4Life said:
I can also confirm that this works!
Click to expand...
Click to collapse
Same here! Really nice!

None of this is working for me and after 10 years on Android I'm tired of fixing things. None if the steps worked for my phone, of cousrse.

So I cleared cach and data from a gpay. Cleared cash and data from Google services. rebooted the phone. tried to set up Google pay and it says I cannot finnish setup to pay in stores.
Im on 10.3.7... oxygen updater says im up to date.
Im not rooted and haven't unlocked my bootloader.
coxik154 said:
GPay works
Without any update, OnePlus just certified our beta.
Need to:
1) clear cache and data GPay
2) clear cache and data of Google Services
3) Reboot your phone
4) Setup GPay
Click to expand...
Click to collapse

I have experienced two cases as below:
1st case was when I used the converted global ROM from T-mobile with dual-sim, but the same IMEI number for two SIMs. Google pay configuration itself was not allowed because of the IMEI. This is my guess.
2nd case is when I uses the factory unlocked version with global ROM with different IMEI numbers for two SIMs. as you know, 8G/256GB is exactly unlocked & global version. Google pay configuration is ok, now it still works well under OSS 10.3.10.

Latest Magisk 2.4/ cts Profile: false

Hey team,
Having a bit of an issue with my OnePlus 6T.
On a fresh OOS 10.3.2 I cannot pass cts Profile with latest version of Magisk 2.4, it works perfect with Magisk 2.3 and both cts profile and basic integrity passes as true. But with the latest version of Magisk 2.4 no matter what I do I always get cts Profile: false...
I followed same installation procedures as always, flash magisk>downloads>+>osmosis BusyBox>install>reboot.
The back again to Magisk the install magiskhide props config then reboot, then after boot go to termix terminal and su>grant>props> chose finger print etc etc... Chose the one for OnePlus 6t android 10 install and reboot and still after boot the cts profile is false! Have tried everything and nothing with latest Magisk 2.4 but if I uninstall everything all modules and Magisk properly and flash magisk but this time the older version of Magisk 2.3 everything works fine after following all mentioned steps above and now cts profile is true and everything checks.
So is this a known issue with latest version of Magisk?
If so is there a workaround to be able to update to latest version? Or I'm I doing something wrong here. Trust me I googled it couldn't find anything in specific.
I thank you for your time in advance!

Magisk hide is off by default in now in version 20.4, it was enabled in 20.3. make sure you are enabling it on 20.4. See my Guide Installing Lineage, Section 5 Very Optional Magisk. I bring this up. The Android 10 fingerprint no longer passes reliably. You need to choose the Android 9 one.
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
See this post about the change to Magism. There are changes coming that work arounds need to be found for otherwise undetected root / unlocked bootloaders, will no longer be a thing.

OhioYJ said:
Magisk hide is off by default in now in version 20.4, it was enabled in 20.3. make sure you are enabling it on 20.4. See my Guide Installing Lineage, Section 5 Very Optional Magisk. I bring this up. The Android 10 fingerprint no longer passes reliably. You need to choose the Android 9 one.
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
See this post about the change to Magism. There are changes coming that work arounds need to be found for otherwise undetected root / unlocked bootloaders, will no longer be a thing.
Click to expand...
Click to collapse
Hey thank you for your answer/ it helped me tremendously! I was able to enable magiskhide and now both are true.
For now the android 10 fingerprint for OnePlus 6t passes fine as both true, my understanding is that will change soon..?
Thank you for the link, very good information.
So that means Magisk will eventually completely not work to pass Google certificates..? Once Google enforces the new key rules?

@OhioYJ

badpanda said:
So that means Magisk will eventually completely not work to pass Google certificates..? Once Google enforces the new key rules?
Click to expand...
Click to collapse
Essentially. Basically if no new work around is found before this happens Magisk would provide root, but any app that wants to look for root will know about it. Google flipped the switch a while back, but then had to reverse course some because some OEMs hadn't implemented things correctly.
TopJohnWu post about key attestation.