Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
upperbladez said:
Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
Click to expand...
Click to collapse
I had the same issue and someone replied and said that the newest version of Google play services can detect unlocked bootloader. It works if you rollback to an older version but it may just be easier to wait until they update Magisk.
Here is a link with more info.
https://forum.xda-developers.com/ap...magisk-discussion-t3906703/page2#post79044917
upperbladez said:
Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
Click to expand...
Click to collapse
This was an issue on the stable release, so I switch to canary. As far as I know now, it should be resolved on stable with a wipe of data from google Pay but see this thread for more info - https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
upperbladez said:
Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
Click to expand...
Click to collapse
Custom or stock rom? What kernel?
I am on HavocOS with Kirisakura kernel. Google pay working fine with latest update for me. I have seen other people discussing non-working google pay, and switching to a different kernel solved it for them.
suhridkhan said:
Custom or stock rom? What kernel?
I am on HavocOS with Kirisakura kernel. Google pay working fine with latest update for me. I have seen other people discussing non-working google pay, and switching to a different kernel solved it for them.
Click to expand...
Click to collapse
Havoc as well, am and was on the same Kirishakura kernal as well so I dont think its kernel related.
Remove all cards. Clear storage for Google pay and Google services. Then add cards again.
shortyboy said:
Remove all cards. Clear storage for Google pay and Google services. Then add cards again.
Click to expand...
Click to collapse
What happens if you don't remove your cards and just clear storage for Google Pay and Google Services? It said it can't remove my card because it's associated with a service or subscription, likely from financing my p2xl through Google. Any other work around to get Google pay working?
fortillian said:
What happens if you don't remove your cards and just clear storage for Google Pay and Google Services? It said it can't remove my card because it's associated with a service or subscription, likely from financing my p2xl through Google. Any other work around to get Google pay working?
Click to expand...
Click to collapse
This happens to me too.
I updated magisk. Still isn't working. Anyone else?
Ehm I have advice because I had this problem either. Just lock bootloader and it will work. But be carefull, if you have custom recovery than there is chance to brick device.
Still ongoing with no permanent solution yet. Its likely going to take an update to Magisk to fix.
All of the workarounds are temporary for a few days before things are detected again.
Relostyt said:
Ehm I have advice because I had this problem either. Just lock bootloader and it will work. But be carefull, if you have custom recovery than there is chance to brick device.
Click to expand...
Click to collapse
thats what google wants you to do when they soft brick your phone with an update and you cant reflash it and you have to pay $$$$$$$$ to fix something you could do for free the allow unlocking option was the worst thing that has happened to android at least before this was around you could recover phone but lose data but now os bricked and cant read state of toggle rip your phone!!! so no im not re locking my bootloader to have android pay work i want it to work but not bad enough to risk my phones safety
billycar11 said:
thats what google wants you to do when they soft brick your phone with an update and you cant reflash it and you have to pay $$$$$$$$ to fix something you could do for free the allow unlocking option was the worst thing that has happened to android at least before this was around you could recover phone but lose data but now os bricked and cant read state of toggle rip your phone!!! so no im not re locking my bootloader to have android pay work i want it to work but not bad enough to risk my phones safety
Click to expand...
Click to collapse
Yeah...I don't think I'd do this one.
Itachisasuke said:
Still ongoing with no permanent solution yet. Its likely going to take an update to Magisk to fix.
All of the workarounds are temporary for a few days before things are detected again.
Click to expand...
Click to collapse
Is that the thread to watch where the fix will be announced?
billycar11 said:
thats what google wants you to do when they soft brick your phone with an update and you cant reflash it and you have to pay $$$$$$$$ to fix something you could do for free the allow unlocking option was the worst thing that has happened to android at least before this was around you could recover phone but lose data but now os bricked and cant read state of toggle rip your phone!!! so no im not re locking my bootloader to have android pay work i want it to work but not bad enough to risk my phones safety
Click to expand...
Click to collapse
upperbladez said:
Yeah...I don't think I'd do this one.
Click to expand...
Click to collapse
Just a heads up guys I've actually relocked and locked my bootloader multiple times maybe 4/5 times in the past month and never experienced no hard it soft bricks always went smoothly as long as you follow the instructions. Now I'm thinking of relocking again because Google pay is actually more important to me than root but if there's an update coming to fix Google pay them I'll wait.
sharpz811 said:
Just a heads up guys I've actually relocked and locked my bootloader multiple times maybe 4/5 times in the past month and never experienced no hard it soft bricks always went smoothly as long as you follow the instructions. Now I'm thinking of relocking again because Google pay is actually more important to me than root but if there's an update coming to fix Google pay them I'll wait.
Click to expand...
Click to collapse
yes your phone wont brick from re locking the problem comes down the line for an update or something like that i have unlocked and relocked bootloaders many times too but what happens when your phone soft bricks months later after an update and it can only get to fastboot and it cant be unlocked because the phone can read the state of the togggle in the os if unlocking is allowed rip phone
billycar11 said:
yes your phone wont brick from re locking the problem comes down the line for an update or something like that i have unlocked and relocked bootloaders many times too but what happens when your phone soft bricks months later after an update and it can only get to fastboot and it cant be unlocked because the phone can read the state of the togggle in the os if unlocking is allowed rip phone
Click to expand...
Click to collapse
Bruh just when i thought i was finally getting the hang of understanding this pixel. My 6p was so much easier to work with lol. So basically what you saying is that it's best to keep bootloader unlocked to prevent any possible bricks later down the road?
sharpz811 said:
Bruh just when i thought i was finally getting the hang of understanding this pixel. My 6p was so much easier to work with lol. So basically what you saying is that it's best to keep bootloader unlocked to prevent any possible bricks later down the road?
Click to expand...
Click to collapse
yup
shortyboy said:
Remove all cards. Clear storage for Google pay and Google services. Then add cards again.
Click to expand...
Click to collapse
Is this fix still working for you after April update? Root is more important to me than Google Pay but it's a convenience.
is this working for anyone else?
Related
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
sniperIT said:
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
Click to expand...
Click to collapse
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
metpage said:
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
Click to expand...
Click to collapse
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
sniperIT said:
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
Click to expand...
Click to collapse
I would try and get your money back, chances are you could have brought a stolen phone.
Darke5tShad0w said:
I would try and get your money back, chances are you could have brought a stolen phone.
Click to expand...
Click to collapse
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
sniperIT said:
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
Click to expand...
Click to collapse
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
sniperIT said:
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
Click to expand...
Click to collapse
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok thank you very much I am in the process, will update once it is complete.
N
sniperIT said:
Ok thank you very much I am in the process, will update once it is complete.
N
Click to expand...
Click to collapse
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
sniperIT said:
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
Click to expand...
Click to collapse
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
16GB unfortunately.
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
PiousInquisitor said:
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
Click to expand...
Click to collapse
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
sniperIT said:
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
Click to expand...
Click to collapse
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
PiousInquisitor said:
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
Click to expand...
Click to collapse
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
sniperIT said:
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
Click to expand...
Click to collapse
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
PiousInquisitor said:
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
Click to expand...
Click to collapse
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
sniperIT said:
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
Click to expand...
Click to collapse
Bummer. Im out of ideas.
What message do you exactly get when trying to execute something via fastboot?
Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.
I had someone suggest I leave my bootloader unlocked. I usually relock it. Does leaving it unlocked stop Google Pay and banking apps from working. Or Games like Pokemon Go?
That was me, but other more knowledgeable folks should feel free to chime in as we all could learn something here.
As I said in the other thread, I don't know. What I do know is that Google's safetynet is more likely to prevent you from using banking apps, Pokémon Go, or Google Pay than the bootloader. Case in point, I have my bootloader completely unlocked yet I still pass safetynet. Now, if an app actively checks for an unlocked bootloader then you may have an issue, but I'm not aware of apps that check for bootloader unlock status.
acheney1990 said:
I had someone suggest I leave my bootloader unlocked. I usually relock it. Does leaving it unlocked stop Google Pay and banking apps from working. Or Games like Pokemon Go?
Click to expand...
Click to collapse
It will certainly stop Google Pay from working, as the phone will report it is insecure.
Banking apps may or may not depending on what they check for.
acheney1990 said:
I had someone suggest I leave my bootloader unlocked. I usually relock it. Does leaving it unlocked stop Google Pay and banking apps from working. Or Games like Pokemon Go?
Click to expand...
Click to collapse
Unlocked breaks Pay. I don't recall any other apps that care.
Leave it unlocked. The forums here are littered with posts that say.... help, I relocked and now it is bricked......and those phones are still bricked.
Don't do it, it's Russian Roulette.
Flash a custom kernel that hides the unlock. Most all of them do, or root it with Magisk and that will hide it.
uicnren said:
It will certainly stop Google Pay from working, as the phone will report it is insecure.
Banking apps may or may not depending on what they check for.
Click to expand...
Click to collapse
This is incorrect.
I have an unlocked bootloader (and am rooted) and use Google Pay without issue.
mitchdickson said:
This is incorrect.
I have an unlocked bootloader (and am rooted) and use Google Pay without issue.
Click to expand...
Click to collapse
its not incorrect, an unlocked bootloader on stock Android will cause Google Pay to not work.
Your root hides the unlocked bootloader (which is why it passes safetynet)
uicnren said:
its not incorrect, an unlocked bootloader on stock Android will cause Google Pay to not work.
Your root hides the unlocked bootloader (which is why it passes safetynet)
Click to expand...
Click to collapse
So you probably shouldn't be saying an unlocked bootloader will definitely stop Google pay from working.
mitchdickson said:
So you probably shouldn't be saying an unlocked bootloader will definitely stop Google pay from working.
Click to expand...
Click to collapse
Except is does, nowhere did the OP mention root, I answered his question 100% correct.
uicnren said:
Except is does, nowhere did the OP mention root, I answered his question 100% correct.
Click to expand...
Click to collapse
You made a blanket statement that an unlocked bootloader definitely stops Google Pay from working. We both know this isn't true.
You aren't just answering the question for OP, but also for any other user who might search for a topic like this.
You should probably edit your post to say that it will definitely stop Google Pay from working if you do not take further steps to protect safety net integrity.
mitchdickson said:
Yes u made a blank t statement that an unlocked bootloader definitely stops Google Pay from working. We both know this isn't true.
You aren't just answering the question for OP, but also for any other user who might search for a topic like this.
You should probably edit your post to say that it will definitely stop Google Pay from working if you do not take further steps to protect safety net integrity.
Click to expand...
Click to collapse
I shouldnt edit anything because its 100% accurate as answered, and as asked.
uicnren said:
I shouldnt edit anything because its 100% accurate as answered, and as asked.
Click to expand...
Click to collapse
Except that it's not.
mitchdickson said:
Except that it's not.
Click to expand...
Click to collapse
It is.
uicnren said:
It is.
Click to expand...
Click to collapse
It's an answer that fails to take any nuance into account, and instead chooses to declare that any unlocked bootloader will cause Google Pay to not work.
mitchdickson said:
It's an answer that fails to take any nuance into account, and instead chooses to declare that any unlocked bootloader will cause Google Pay to not work.
Click to expand...
Click to collapse
I dont go by 'nuance' only by what the OP asked in his question, and in that regard, the answer is 100% correct.
I dont assume anything, had they asked the question differently, then maybe they would get a different answer.
Now people will go unlock their bootloader, without root and wonder why the hell Google pay isn't working, because someone said it would.
uicnren said:
I dont go by 'nuance' only by what the OP asked in his question, and in that regard, the answer is 100% correct.
I dont assume anything, had they asked the question differently, then maybe they would get a different answer.
Now people will go unlock their bootloader, without root and wonder why the hell Google pay isn't working, because someone said it would.
Click to expand...
Click to collapse
Here's the thing: you can have an unlocked bootloader, without root, and still pass Safety Net by flashing a kernel which incorporates this patch: https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
You are continuing to ignore that you are not only answering a question for OP, but for anyone who may come across this thread.
mitchdickson said:
Here's the thing: you can have an unlocked bootloader, without root, and still pass Safety Net by flashing a kernel which incorporates this patch: https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
You are continuing to ignore that you are not only answering a question for OP, but for anyone who may come across this thread.
Click to expand...
Click to collapse
Nope, I only answered for the OP, with the information provided. Im not answering to anyone else.
If they are already going through all the other stuff, they wouldnt be asking the question, since you're stuck on 'nuance' and assumptions.
uicnren said:
Nope, I only answered for the OP, with the information provided. Im not answering to anyone else.
If they are already going through all the other stuff, they wouldnt be asking the question, since you're stuck on 'nuance' and assumptions.
Click to expand...
Click to collapse
You're assuming the OP wouldn't root and would not flash a kernel.
My whole point is that you shouldn't make that assumption.
mitchdickson said:
You're assuming the OP wouldn't root and would not flash a kernel.
My whole point is that you shouldn't make that assumption.
Click to expand...
Click to collapse
I didnt assume anything.
The answer was based on the information provided (or lack thereof).
uicnren said:
I didnt assume anything.
The answer was based on the information provided (or lack thereof).
Click to expand...
Click to collapse
Did I miss where the OP said he wouldn't root and wouldn't flash a kernel?
mitchdickson said:
Did I miss where the OP said he wouldn't root and wouldn't flash a kernel?
Click to expand...
Click to collapse
No, you missed where he said he would.
Not sure if it has anything to do with unlocking bootloader, but it seems that I can't install Netflix because my device is not certified in the Play Store. Anyone else come across this issue?
It is caused by the unlocked bootloader. It has been that way with Pixels since the originals. The solutions are to root with Magisk (do not know if Magisk works with the Pixel 3 or not) or use a custom kernel when one becomes available provided the P3 works like the P and P2.
Sideload it, done.
krabman said:
Sideload it, done.
Click to expand...
Click to collapse
what level is your widevine since you have unlocked your bootloader, did it change?
Actually I need to backtrack here, Netflix wont install on a rooted device and while some say it works I've never had it work with Magisk either. On the other hand you can just sideload and it will work fine rooted. I don't actually know what happens if the device is unlocked but not rooted because I've never done that. lol My bad. I would try sideloading though, it's got a good shot at working and nothing lost if it doesn't.
Just download apk file from apk mirror
Works fine
https://www.apkmirror.com/apk/netfl...flix-6-13-0-build-29940-android-apk-download/
Figured, it's been this way for a fair while now and thats been the fix from the start.
Just open play store in settings\apps, clear data. Reopen the play store and see if it still says it. Might have to do it more than once. I unlocked my bootloader, and I saw that. I had to clear data twice. Now mine shows as certified.
gettinwicked said:
Just open play store in settings\apps, clear data. Reopen the play store and see if it still says it. Might have to do it more than once. I unlocked my bootloader, and I saw that. I had to clear data twice. Now mine shows as certified.
Click to expand...
Click to collapse
No dice for me Google Pay won't work either... strange
virtyx said:
what level is your widevine since you have unlocked your bootloader, did it change?
Click to expand...
Click to collapse
How do I check widevine?
JeromeLeung said:
No dice for me Google Pay won't work either... strange
Click to expand...
Click to collapse
Weird, mine went back to not certified. I did the clear data again and it's good, again. Hrmm
gettinwicked said:
Weird, mine went back to not certified. I did the clear data again and it's good, again. Hrmm
Click to expand...
Click to collapse
Will Google Pay allow you to add a card?
JeromeLeung said:
Will Google Pay allow you to add a card?
Click to expand...
Click to collapse
Nope. Says it cannot complete setup because the device has been rooted or modified. And play store keeps jumping back to uncertified. Guess it won't stick. Have to wait for root. No biggie, I haven't fully jumped on the GPay train yet.
gettinwicked said:
Nope. Says it cannot complete setup because the device has been rooted or modified. And play store keeps jumping back to uncertified. Guess it won't stick. Have to wait for root. No biggie, I haven't fully jumped on the GPay train yet.
Click to expand...
Click to collapse
Okay, I thought something was wrong with my device. Good to know we're all in the same boat
I'm kiinda wondering if the much talked about Titan chip is going to make it harder to hide root. Some of the stuff out there is making that claim. Something related is that I followed a link to a google blog about it and the said that one of it's (Titian's) features is the ability to block unlocking. Not that it did block it, that it had that ability, so presumably it will depend on the OEM whether or not that feature is active. Was wondering where that will put the Verizon guys... Not trying to scare anyone because I haven't run into anything specific that comes from google and says exactly what it does but I know it's got my attention.
JeromeLeung said:
How do I check widevine?
Click to expand...
Click to collapse
you can download an app to check, just search widevine
virtyx said:
you can download an app to check, just search widevine
Click to expand...
Click to collapse
Widevine Security Level: L1
JeromeLeung said:
Widevine Security Level: L1
Click to expand...
Click to collapse
with unlocked bootloader?
Hi
It happens to me on samsung s8 device not certified. I have tried some things( saw in youtube and foruns) and nothing.
So try this...
Open setting/apps/ and look if any app of google is disabled( chrome/gmail/play movies...) activate all from google and voila
My s8 is now certified
virtyx said:
with unlocked bootloader?
Click to expand...
Click to collapse
That's correct
My phone is stock in every way, except bootloader.
What is the best way to lock the bootloader again without loosing any data?
I need my phone locked again to use google pay
rockuman_ex said:
My phone is stock in every way, except bootloader.
What is the best way to lock the bootloader again without loosing any data?
I need my phone locked again to use google pay
Click to expand...
Click to collapse
To use Google Pay, you need to pass Safety net.
It is not related to bootloader.
And relocking bootloader without losing any data is possible if and only if you did not flash any custom mods like recovery , kernel ..As it validates md5 checksum
rockuman_ex said:
My phone is stock in every way, except bootloader.
What is the best way to lock the bootloader again without loosing any data?
I need my phone locked again to use google pay
Click to expand...
Click to collapse
You don't need to re-lock the bootloader to use Google Pay. Install TWRP as your recovery and then install Magisk!
kingme.sri said:
To use Google Pay, you need to pass Safety net.
It is not related to bootloader.
And relocking bootloader without losing any data is possible if and only if you did not flash any custom mods like recovery , kernel ..As it validates md5 checksum
Click to expand...
Click to collapse
My phone is stock, not custom recovery or custom rom. Using 9.05 rom now.
So how do i re lock without losing any data
tye_time said:
You don't need to re-lock the bootloader to use Google Pay. Install TWRP as your recovery and then install Magisk!
Click to expand...
Click to collapse
That's what I'm trying to avoid.
I want to go 100% stock.
I just ran safetynet test, i got cts profile match failed.
How do i fix this?
You will need to relock the bootloader then, you may lose data. Just back up everything first like pictures and videos. All your apps will re-download when you sign back into Google
tye_time said:
You will need to relock the bootloader then, you may lose data. Just back up everything first like pictures and videos. All your apps will re-download when you sign back into Google
Click to expand...
Click to collapse
Is there a way to keep my phone as is when i relock the bootloader?
And how do i relock it?
Link to guide please?
Here is the guide: https://www.androidexplained.com/oneplus-5-lock-bootloader/
You won't be able to keep your phone 'as is' unfortunately, all data will be wiped and the phone reset.
rockuman_ex said:
My phone is stock in every way, except bootloader.
What is the best way to lock the bootloader again without loosing any data?
I need my phone locked again to use google pay
Click to expand...
Click to collapse
I am on latest open beta everything stock no root.. Google pay works flawless.. try disabling telephone permission of google play services & try registering google pay
Yash93 said:
I am on latest open beta everything stock no root.. Google pay works flawless.. try disabling telephone permission of google play services & try registering google pay
Click to expand...
Click to collapse
didn't work for me. still saying my phone is modified etc... :crying:
tye_time said:
Here is the guide: https://www.androidexplained.com/oneplus-5-lock-bootloader/
You won't be able to keep your phone 'as is' unfortunately, all data will be wiped and the phone reset.
Click to expand...
Click to collapse
sigh..... i have everything set up since i got the phone.... a bit reluctant to do this... but there's NO OTHER way right? :crying::crying::crying:
rockuman_ex said:
sigh..... i have everything set up since i got the phone.... a bit reluctant to do this... but there's NO OTHER way right? :crying::crying::crying:
Click to expand...
Click to collapse
Doesn't look like it I'm afraid. Sad times.
tye_time said:
Doesn't look like it I'm afraid. Sad times.
Click to expand...
Click to collapse
finally took the plunge and got my phone re-locked... everything was wiped :crying: