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!
Related
Has anyone gotten latest version of PoGo working on latest Oreo with ElementalX? I've never played but my friends keep asking me to join so I figured what the heck..
Slight problem... Device Not Compatible??
I had magisk and xposed, but I tried disabling, and even fully uninstalling xposed (and all additional xposed modules), and adding PoGo to the MagiskHide options, with no luck.
It still says that my device is not compatible...I would assume that's due to the rooting?
Or is it because I'm using ElementalX kernel?
I read somewhere that there's a (not pokemon go-specific) bypass sort of thing involving SatefyNet, but you have to install Magisk *before* going through initial phone setup, but any guide I've ever read about flashing/rooting ph-1 says to go through setup and then install magisk. I tried to find the post that talks about it but I can't find it right now. Anyway, I would imagine there's some kind of checksum against system and if magisk has been added after the fact, the checksum wont match? I really have no idea, just a guess.
I haven't seen any other posts specifically mentioning Essential being incompatible, so maybe it's just me.
I was originally thinking it was because of root or magisk remnants(?), but maybe it's the non-stock kernel.
If anyone could help, I'd really appreciate it.
I feel silly asking such a noob question, I've just never play PoGo...or any Pokemon...ever.
extra info:
I have successfully created an account using their google auth option.
I get through the first Professor Willow part, then character selection.
Usually part way through character selection, I get the error in the attached image.
Its not on any one specific section, however, it can/has occur at any point during the loading.
I've cleared cache and data a hundred times because it seems to get further each time if I do a fresh data wipe and start over -- I know the next step already so I can get through faster maybe lol
--update--
I finally got through character selection and made it to the first chance to catch pokemon. I hit a squirtle and it was trying to break free, and then that error popped up.
Haven't been able to get back in far enough again to see if it actually added to my PokeDex or not.
Sorry for the late reply, but you have to hide root detection under magisk.
For Pokemon go to work, go to Magisk > MagiskHide > then search for Pokemon go and select it then reboot.
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 ...
A few days ago Google pay randomly stopped working. I'm running Magisk 17.3 since the newer versions stop magisk hide spontaneously. (Tried the latest version tho). I'm passing safetynet, play store says my device is certified, latest os, magisk hide works and I've hidden magisk (and enabled systemless hosts) and hidden root from google pay, still it says that the phone has been rooted or altered in some way.
Any other ideas?
Same problem here. Started 1.3.19
Same here, just rooted last week to get Call Screening here in Canada, and finally got around to getting my Google Pay set up again. No luck
There's been quite a few reports about this, but nothing major enough to get traction, I think. You can try checking this thread, there's a number of possible fixes in there, though they didn't help me, maybe it could work for you.
https://forum.xda-developers.com/apps/magisk/help-magisk-google-pay-t3887147/page4
I have tried quite a lot custom roms on my backup phone (S8+) a couple of months ago. Most things worked fine but i kept having problems with Netflix and my tv provider app. Both issues are related to SafetyNet, as far as i know (and or the fact that phone is rooted). If i do a SafetyNet check the phone fails.
So i am trying to fix this.
I have installed TWRP 3.3.3.1 and am running PixelExperience_Plus_dream2lte-10.0-20200421-0746-UNOFFICIAL.
When i am try Magisk v23.zip with TWRP i am getting error 1.
I was also trying to install:
SafetyNet-fix-v1.1.1 and MagiskHideProConf-v5.4.0 but they also both failed.
First question: am i trying to do the right thing to pass the SafetyNet check?
And how can i fix the error?
P.S. Netflix doesn't show up in the Google store. Installing older version APK only works for a few times.
Tv provider app just says "cannot play video"
If all else fails, use XposedFramework, just don't use it as a primary solution.
Hey,
I come to you with a peculiar set of bugs? Problems?
I got a pretty fresh 12G Ram Nothing Phone (1) here. I tried rooting it pretty much immediately with help of the forum post here, but the OTA updater failed afterwards, so I let magisk uninstall itself, flashed a clean full European update and then ran the OTA updater al the way up to 1.1.4, using the phone for 2 days no problems now.
Today I ran into a problem I have never seen before: Netflix on the app store is listed as not compatible with my device. All other streaming apps work. In fact pretty much all other apps I previously used do work (acutally KWGT also showed as incompatible, but the apk from another page worked).
Now all my banking apps still work and they are super sensitive to any changes (except GPay of course, since the bootloader is still unlocked), but I still ran a safety net check, which passed, however the apps I used for testing did still show a cts profile mismatch. How can this be? Is there anything I could do to fix it? Could this cause for whatever reason just a ban on netflix in the store?
Im kind of lost here. Id like to try everything before I have to do a full reset, as that would mean a lot of trouble.
Edit: Well nvm Im idiot. So apparently just having the bootloader unlocked causes a CTS profile mismatch and Netflix does get removed from the appstore for that. Never encountered this on my rooted to death Mix 3 before, which is why I made the assumption that it is weird. Delete this thread if you want
Still any good fix available rn? The Netflix apk alone doesnt seem to work and root is not available yet on 1.1.4 afaik.
Leolele99 said:
Hey,
I come to you with a peculiar set of bugs? Problems?
I got a pretty fresh 12G Ram Nothing Phone (1) here. I tried rooting it pretty much immediately with help of the forum post here, but the OTA updater failed afterwards, so I let magisk uninstall itself, flashed a clean full European update and then ran the OTA updater al the way up to 1.1.4, using the phone for 2 days no problems now.
Today I ran into a problem I have never seen before: Netflix on the app store is listed as not compatible with my device. All other streaming apps work. In fact pretty much all other apps I previously used do work (acutally KWGT also showed as incompatible, but the apk from another page worked).
Now all my banking apps still work and they are super sensitive to any changes (except GPay of course, since the bootloader is still unlocked), but I still ran a safety net check, which passed, however the apps I used for testing did still show a cts profile mismatch. How can this be? Is there anything I could do to fix it? Could this cause for whatever reason just a ban on netflix in the store?
Im kind of lost here. Id like to try everything before I have to do a full reset, as that would mean a lot of trouble.
Edit: Well nvm Im idiot. So apparently just having the bootloader unlocked causes a CTS profile mismatch and Netflix does get removed from the appstore for that. Never encountered this on my rooted to death Mix 3 before, which is why I made the assumption that it is weird. Delete this thread if you want
Still any good fix available rn? The Netflix apk alone doesnt seem to work and root is not available yet on 1.1.4 afaik.
Click to expand...
Click to collapse
You added playstore and play services to the denylist and installed safetynet fix i guess?