When I first booted the phone I checked for Widivine level and it came back with level 1.
Now after rooting with Magisk I noticed the device marked as being "not certified" in Play Store and only having Widivine level 3.
My understanding is that the unlock leads to this but so far (on my OP 3, 3T and 5T) rooting with Magisk and installing a custom kernel, my devices would still be "certified".
I am wondering if things changed for Android Pie, or if e.g. installing Magisk with preserving DM-Verity would help. I was tempted to give this a try but verity errors are quite annoying and I don't want to completely wipe phone just to play around with that switch.
Any ideas?
dreinulldrei said:
When I first booted the phone I checked for Widivine level and it came back with level 1.
Now after rooting with Magisk I noticed the device marked as being "not certified" in Play Store and only having Widivine level 3.
My understanding is that the unlock leads to this but so far (on my OP 3, 3T and 5T) rooting with Magisk and installing a custom kernel, my devices would still be "certified".
I am wondering if things changed for Android Pie, or if e.g. installing Magisk with preserving DM-Verity would help. I was tempted to give this a try but verity errors are quite annoying and I don't want to completely wipe phone just to play around with that switch.
Any ideas?
Click to expand...
Click to collapse
This seems to be an issue with Magisk and some versions of OxygenOS.
There is a GitHub issue about that: https://github.com/topjohnwu/Magisk/issues/585
I read a comment in another thread that if you use magisk hide for the play store, then wipe data from the play store app you'll be good to go. immediately after rooting I checked the play store app in the magisk hide section and haven't had an issue.
Pain-N-Panic said:
I read a comment in another thread that if you use magisk hide for the play store, then wipe data from the play store app you'll be good to go. immediately after rooting I checked the play store app in the magisk hide section and haven't had an issue.
Click to expand...
Click to collapse
I just did exactly what you said. In magiskhide check the box for google play store. Force stop play store and wipe it's data. Reopen play store. No longer marked "not certified"
You'll still only have widevine 3. Download "drm info" from the play store and you'll still see L3 not L1. I believe it's the bootloader being unlocked that causes it.
Thanks guys, Play store now says certified but Widevine still only offers L3.
dreinulldrei said:
Thanks guys, Play store now says certified but Widevine still only offers L3.
Click to expand...
Click to collapse
Has been asked several times.
Bootloader unlocked = L3
Always
https://storage.googleapis.com/wvdocs/Widevine_DRM_Getting_Started_Devices.pdf
Thanks, yes, but since it - to my understanding - can be remedied by re-locking, the corresponding code or keys must be somewhere. It's like Safety Net, which is bypassed by Magisk ...
Related
My moto x style EU xt1572 stock nougut stats modified (the only thing modified is that it doesn't have install-recovery.sh,i think), bootloader unlocked , not rooted shows google play uncertified. I upgraded from 6.0.1 using EU ota file uploaded in xda.
I tried to clean data of google play store, google play services,google app then remove account restart and re sing in but it still shows uncertified. What can i do now? And sorry for bad english.
yk1999 said:
My moto x style EU xt1572 stock nougut stats modified (the only thing modified is that it doesn't have install-recovery.sh,i think), bootloader unlocked , not rooted shows google play uncertified. I upgraded from 6.0.1 using EU ota file uploaded in xda.
I tried to clean data of google play store, google play services,google app then remove account restart and re sing in but it still shows uncertified. What can i do now? And sorry for bad english.
Click to expand...
Click to collapse
Does the Play Store not work? Your bootloader is unlocked, thus you are failing SafetyNet check and your device is Uncertified... the Play Store should still work, just a handful of apps are now unavailable for installation from Google (you can still use APKMirror though).
The unfortunate part of Nougat, and more future versions of Android, is that they are becoming more and more secure which means ANY modification is going to trigger to Google.
Like it or not, it is what it is... You can try Magisk and Magisk hide, but they have been playing the back and forth game more often lately, Magisk finds a fix and SafetyNet gets updated, Magisk patches it, SafetyNet gets updated, etc. It is your option.
Also, just to answer your next question, it is not possible to relock the bootloader on Nougat or the even the latest Marshmallow builds, the only way is if you have an older Marshmallow build and it is pure (no skipped gpt.bin or bootloader.img).
acejavelin said:
Does the Play Store not work? Your bootloader is unlocked, thus you are failing SafetyNet check and your device is Uncertified... the Play Store should still work, just a handful of apps are now unavailable for installation from Google (you can still use APKMirror though).
The unfortunate part of Nougat, and more future versions of Android, is that they are becoming more and more secure which means ANY modification is going to trigger to Google.
Like it or not, it is what it is... You can try Magisk and Magisk hide, but they have been playing the back and forth game more often lately, Magisk finds a fix and SafetyNet gets updated, Magisk patches it, SafetyNet gets updated, etc. It is your option.
Also, just to answer your next question, it is not possible to relock the bootloader on Nougat or the even the latest Marshmallow builds, the only way is if you have an older Marshmallow build and it is pure (no skipped gpt.bin or bootloader.img).
Click to expand...
Click to collapse
But when i restore marshmallow (system and boot via twrp and fsg, Bluetooth,modem via fastboot) google play shows certified.
yk1999 said:
But when i restore marshmallow (system and boot via twrp and fsg, Bluetooth,modem via fastboot) google play shows certified.
Click to expand...
Click to collapse
Because in marshmallow the bootloader state is not checked, in Nougat it is.
acejavelin said:
Because in marshmallow the bootloader state is not checked, in Nougat it is.
Click to expand...
Click to collapse
So even if i get rom status to official it will stil show uncertified?
yk1999 said:
So even if i get rom status to official it will stil show uncertified?
Click to expand...
Click to collapse
Correct... if you on official Nougat, completely stock and software status is Official, but your bootloader is unlocked it will show uncertified.
There is currently no way to relock the bootloader if you have taken the December 2016 security update or the Nougat update, we must wait for a newer factory image to be leaked... although it is not known if that will ever happen at this point.
Thanks for the help.
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).
Hi,
im a little bit confused about this problem. From one day to another, G Pay stopped working with NFC. "This device cant be used because its rootet or modified."
I use Magisk with stock Rom severeal month now and gpay ran without any problems. The confusing thing is that I didn´t changed anything what could cause this behaviour.
What I already tried:
-GPay: Delete cache, uninstalled updates. Tried many times to activate NFC payment.
-Erased Cache in TWRP
-Installed complete offline OTA. (Root and TWRP was gone and it still wont work)
-Tried Magisk Hide and random app name.
Does anybody have an idea? I dont want to reset the whole phone for this or lock the bootloader.
Thanks for your help!
Did you update the Gpay app? Mine still works but I never installed the update
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
sharksfan7 said:
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
Click to expand...
Click to collapse
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Probably because having a rooted phone, especially if you are using to send/receive money, opens up a SECURITY HOLE, even if you are using something to "bypass" google.
NOTHING is 100% safe, but, I for one, will never root my phone, if I am using it to spend money.
The days of rooting will be over one of these days. Google is locking down things more and more.
hlzocker said:
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Click to expand...
Click to collapse
Make sure you have hide enabled for pay.
I'm on 18.1 and I don't have issues.
I fought with the same problem.
latest Magisk Canary build was the solution that worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Coumodo said:
I fought with the same problem.
latest Magisk Canary build was the solution the worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Click to expand...
Click to collapse
Yes, that solved the problem for me. Now the activation was successfull. Thanks!
anyone have netflix problem after unclock bootloader? I kept getting a "This app is not compatible with your device." I uninstalled the manufacture using ADB and sideload a version from APK mirror, I kept running into the same error, please help thanks.
Works fine here. Do you have Magisk installed with Magisk hide enabled? I know Netflix is unavailable in play store if safetynet fails, so maybe it needs to pass for it to work too? Just guessing here.
Widevine changes after you unlock the bootloader.
efex said:
Works fine here. Do you have Magisk installed with Magisk hide enabled? I know Netflix is unavailable in play store if safetynet fails, so maybe it needs to pass for it to work too? Just guessing here.
Click to expand...
Click to collapse
aoaleman said:
Widevine changes after you unlock the bootloader.
Click to expand...
Click to collapse
yes it is indeed boot loader unlock with magisk installed, anyway around this?
Vio281 said:
yes it is indeed boot loader unlock with magisk installed, anyway around this?
Click to expand...
Click to collapse
Can you find Netflix in play store? Make sure your play is certified, in case this makes a difference. If you enabled Magisk hide, just clear data for play store and play services and it should get certified correctly.
As I said, Netflix works just fine here, unlocked and rooted with Magisk and hide enabled. No further tweaks needed.
efex said:
Can you find Netflix in play store? Make sure your play is certified, in case this makes a difference. If you enabled Magisk hide, just clear data for play store and play services and it should get certified correctly.
As I said, Netflix works just fine here, unlocked and rooted with Magisk and hide enabled. No further tweaks needed.
Click to expand...
Click to collapse
I use apk mirror app to install netflix I download via apkmirror and it work.
Hello there. I have a question regarding getting my phone to be Google Play Protect certified again. I have unlocked the bootloader, which if I understand correctly is what breaks the certification, Flashed TWRP 3.0.4-1, and installed Magisk v20.4 via TWRP. I verified Root by using the app Root Checker on the play store (and also SU requests popped up after rebooting). I enabled MagiskHide inside Magisk Manager and performed a SafeyNet Check and both the ctsProfile and basicIntegrity returned as True (the first time I ran it cts failed so I enabled hide and rebooted). There are a few apps that I use that indicate my device is not compatible and it is because of this I am guessing (Chewy, Disney+ for example). Oddly, as I was typing this I tried again and looked in the "My Apps" list and I could install Disney+ from there (10 minutes ago I couldn't) but clicking on the app it still said that it was incompatible. Chewy, however, remains unable to be used.
Since I could only find references to this on this thread (https://forum.xda-developers.com/pixel-2-xl/help/play-certification-unlocked-bootloader-t3950857) and the second way to correct this problem, that thread says it doesn't resolve the ctsProfile) I figured I'd ask on here. I already soft-bricked it once and successfully used the MSM tool to bring it back so if I screwed something up I'll try again, but probably only once more :fingers-crossed:
*edit* I haven't activated my actual phone use yet since I want it to be stable first! Not sure if that makes a difference, I don't think it should.
*edit 2* I've since activated my phone. I can receive calls but no text messages. The plot thickens.
Thanks!