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
Related
Has anyone else that has their bootloader unlocked been able to download netflix from the play store? I tried but just said device not compatible. I was able to download the apk somewhere else but just wondering it that happened because of the bootloader
Yes it's because of the bootloader
ErickF said:
Has anyone else that has their bootloader unlocked been able to download netflix from the play store? I tried but just said device not compatible. I was able to download the apk somewhere else but just wondering it that happened because of the bootloader
Click to expand...
Click to collapse
It's been that way since Android 4.0 or something like that.
Sent from my Moto Z (2) using Tapatalk
Na just recently actually
Just download the apk from apkmirror
Though apk mirror works, I'm getting sick of this sort of thing. Kodi doesn't block unlocked bootloaders... I've been a Netflix customer for years... This is really annoying...
-RioT- said:
Though apk mirror works, I'm getting sick of this sort of thing. Kodi doesn't block unlocked bootloaders... I've been a Netflix customer for years... This is really annoying...
Click to expand...
Click to collapse
Kodi also has nothing to do with movie and television studios and is mostly used for pirating
Sent from my Moto Z (2) using Tapatalk
altimax98 said:
Kodi also has nothing to do with movie and television studios and is mostly used for pirating
Click to expand...
Click to collapse
Sure.
-RioT- said:
Though apk mirror works, I'm getting sick of this sort of thing. Kodi doesn't block unlocked bootloaders... I've been a Netflix customer for years... This is really annoying...
Click to expand...
Click to collapse
Can you guys link to the Netflix APK that works for you?
I also just have my bootloader unlocked running factory Sprint 8.0.0 July patch and when I launch Netflix it shown the Netflix logo and just hangs there. No error just hangs on the Netflix logo.
Thanks!
jeffritz1 said:
Can you guys link to the Netflix APK that works for you?
I also just have my bootloader unlocked running factory Sprint 8.0.0 July patch and when I launch Netflix it shown the Netflix logo and just hangs there. No error just hangs on the Netflix logo.
Thanks!
Click to expand...
Click to collapse
Do you have magisk installed?
Marcowe said:
Do you have magisk installed?
Click to expand...
Click to collapse
I do not. I was trying to make it happen without breaking OTAability
jeffritz1 said:
I do not. I was trying to make it happen without breaking OTAability
Click to expand...
Click to collapse
So there isn't a solution for you, every solution breaks OTA.
The only solution without breaking OTA is relocking bootloader.
Netflix fix:
must be rooted.
go to the root directory with a file manager that will let you like Root Explorer
Go to: /system/vendor/lib
Find the file "liboemcrypto.so" and delete it.
Reboot
go to play store and download Netflix, Hulu and or Vudu
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.
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?
https://www.getdroidtips.com/root-vivo-nex-3-pd1924f/
hope it can help you guys
does this even work? especially the unlocking-bootloader part.
kezzuki said:
does this even work? especially the unlocking-bootloader part.
Click to expand...
Click to collapse
fake
wolfgart said:
fake
Click to expand...
Click to collapse
thought so. cus vivo's official customer service says root is not supported, anf by that they probably meant bootloader-unlocking
Maybe somebody can unlock bootloader and try to install magisk? So we can use gpay) (I've ordered this phone and it still hasn't arrived). I hope it'll work:
https://forum.xda-developers.com/general/rooting-roms/how-to-unlock-bootloader-vivo-phones-t3686690
Or we can try to certify phone with Google to get working gpay: https://www.google.com/android/uncertified/
1) You have to know gfs id. Google gives the instruction on there page. Another method is to know it through file manager /data/data/com.google.android.gsf/databases/gservices.db
2) After certifying phone you have to factory reset your phone. And now it would be certified with Google.
Root is necessary here to fix Google Pay that it seems VIVO won't fix himself
I also ordered the phone. Did anyone managed to get GPay working?
xchatter said:
I also ordered the phone. Did anyone managed to get GPay working?
Click to expand...
Click to collapse
Need root to fix it
Google pay works for me global version
Change emojis
From what I have found, SafetyNet and Netflix still work as they would with an unlocked bootloader (at least on LineageOS). Is there any camera or audio functionality missing? Can you still download and watch Netflix/Disney+ content?
I'm sure some of these questions were answered before I just want to be sure before I do something to my phone that I might not be able to change back
Nothing happens. you can use your phone as usual
itsfaiez said:
Nothing happens. you can use your phone as usual
Click to expand...
Click to collapse
Really? So you can still use banking apps and streaming services?
ivao said:
Really? So you can still use banking apps and streaming services?
Click to expand...
Click to collapse
Streaming services no problem. I don't know about banking apps.
itsfaiez said:
Streaming services no problem. I don't know about banking apps.
Click to expand...
Click to collapse
Are you using a custom rom or stock? This might be too much to ask but can you install a safetynet testing app (try https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample) and send a screenshot of the results? You can uninstall it after
I went ahead and unlocked the bootloader anyway and Widevine L1 and safetynet basic integrity remain. I forgot to copy the screenshots to my computer before installing LineageOS (oops).
On LineageOS Widevine L1 is still there and Netflix/Disney+ work perfect when downloaded from Aurora Store. I haven't bothered checking safetynet because I'm using MicroG meaning it won't pass anyway.