Google play uncertified - X Style (Pure) Q&A, Help & Troubleshooting

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.

Related

Redmi 3S bootloop after updating MIUI8.0.3.0 Global stable ROM

TWICE. This is because I've disabled some apps (Hangout, Google Play Music, Google Play Books etc.) from Google Play. It causes my phone stuck at MI Logo and the powered by Android screen. If I enter recovery mode it shows a MI phone and a USB cable. At first I thought was wrong update package or what but it seems not. I didn't download the update package from anywhere else. It's the official update. And I saw someone saying if you disabled any apps then your phone can't boot in MIUI8. But seems MI never mention this problem. Well played Xiaomi.
yes, same thing happens to me too, disabling some google apps will cause bootloop
Yappuccino said:
TWICE. This is because I've disabled some apps (Hangout, Google Play Music, Google Play Books etc.) from Google Play. It causes my phone stuck at MI Logo and the powered by Android screen. If I enter recovery mode it shows a MI phone and a USB cable. At first I thought was wrong update package or what but it seems not. I didn't download the update package from anywhere else. It's the official update. And I saw someone saying if you disabled any apps then your phone can't boot in MIUI8. But seems MI never mention this problem. Well played Xiaomi.
Click to expand...
Click to collapse
Do not disable any Google App. Ever. On the stock ROM. If you do so, you'll be stuck in a bootloop.
I guess, you did not make a backup before you disabled the apps (e.g. with TWRP | backup)?
If you did't - you can unbootloop by flashing the MIUI Global stable ROM again (all data on phone will be erased).
Uhm... by the way - here - is a list of apps that can be disabled
himfa71 said:
yes, same thing happens to me too, disabling some google apps will cause bootloop
Click to expand...
Click to collapse
They do informed at MIUI Forum but I think they should state it together with the update package
Wokoloko said:
I guess, you did not make a backup before you disabled the apps (e.g. with TWRP | backup)?
If you did't - you can unbootloop by flashing the MIUI Global stable ROM again (all data on phone will be erased).
Uhm... by the way - here - is a list of apps that can be disabled
Click to expand...
Click to collapse
Unfortunately I don't even unlock my bootloader at the moment so I don't have any recovery for my device
psychopac said:
Do not disable any Google App. Ever. On the stock ROM. If you do so, you'll be stuck in a bootloop.
Click to expand...
Click to collapse
Now I have TWRP on my phone so I don't care anymore

passing safetynet with magisk 10.2 on x727 or x720?

Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.
Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.
suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!
robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.
Magisk V10 and phh SU r266 working fine for me on 20s
Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.
Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.
are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.
I could not pass safety net, got CM13, with MAGISK installed. Dang=)
squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks
I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.
Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?

What ROM setup can I use Netflix with?

I have Lineage Marshmallow and Netflix did not show in Google Play. I installed Magisk through its manager, made sure Hide was on, then Netflix was still not in Play. I downloaded an apk from a trusted site (can't remember want it was at the moment, apkmirror or something like that). It started bootlooping during that install. Had to wipe and reinstall the ROM.
What ROM and magisk combo can I use to get Netflix running? I need Marshmallow or higher, and the camera to function. Suggestions?
Stock Nougat.
Face it, apps are getting better at seeing the **** you do, so just play by the rules. That or stop using ****ing Lineage OS, use AOSP 7.1.2 and stuff, its less customized and thus a bit harder for apps to see with safetynet or similar, but the thing is, at that point you might as well just run stock.
How do I get stock Nougat that has a working cam, and miracast? I was of the impression that Nougat roms disabled both.

Device not certified after root

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 ...

Widewine L1 or L3?

Hi,
So a bit of a noob question, but I was on beta OOS11 prior to going over to Open Beta and my Widewine support is L3 and not L1. I thought this was a result of unlocking the bootloader but was told this should not be the case. Any chance I can fix this as the Oneplus 8 Pro should have L1?!
Thanks in advance.
Shredz98 said:
Hi,
So a bit of a noob question, but I was on beta OOS11 prior to going over to Open Beta and my Widewine support is L3 and not L1. I thought this was a result of unlocking the bootloader but was told this should not be the case. Any chance I can fix this as the Oneplus 8 Pro should have L1?!
Thanks in advance.
Click to expand...
Click to collapse
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
efex said:
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
Click to expand...
Click to collapse
My bootloader is unlocked, I'm rooted, magisk and magiskhidr props config is installed and safety net passes but still I'm on L3
Shredz98 said:
My bootloader is unlocked, I'm rooted, magisk and magiskhidr props config is installed and safety net passes but still I'm on L3
Click to expand...
Click to collapse
Did you try clearing data/cache for Netflix (or whatever app you're using)? Does DRM Info (app) also show L3? Then I'm out of ideas.. Always worked for me on all versions since OOS 10.5.10. I'm on EU model IN2023
efex said:
According to some users SafetyNet must pass to get L1. On stock OB1 I believe it still fails. I've never checked L status when my safetynet failed, but I pass and have L1.
If you havent unlocked your BL, do it, flash magisk, install magiskhide props config (to make it pass) and you SHOULD get L1 again.
Click to expand...
Click to collapse
efex said:
Did you try clearing data/cache for Netflix (or whatever app you're using)? Does DRM Info (app) also show L3? Then I'm out of ideas.. Always worked for me on all versions since OOS 10.5.10. I'm on EU model IN2023
Click to expand...
Click to collapse
Yeah that's the the thing the DRM info (app) shows L3 as does Netflix, tried clearing cache, uninstalling and reinstalling, everything but lock my bootloader again.
Thanks for your help in any case
Shredz98 said:
Yeah that's the the thing the DRM info (app) shows L3 as does Netflix, tried clearing cache, uninstalling and reinstalling, everything but lock my bootloader again.
Thanks for your help in any case
Click to expand...
Click to collapse
One more thing, is your play store certified? Shouldn't make a difference, but worth a try.
If not certified, clear data för Play store and Play services and it should be after self-updating.
efex said:
One more thing, is your play store certified? Shouldn't make a difference, but worth a try.
If not certified, clear data för Play store and Play services and it should be after self-updating.
Click to expand...
Click to collapse
Play store is certified. I wonder whether it is because I bought the 8 pro and it immediately updated to 10.5.12EU i believe it was but then I unlocked bootloader and went to OOS 11 DP3 though I didn't root nor check my Widewine status then, then updated to DP4 and then to OB1. It was only on OB1 that I rooted my phone and installed Magisk and only then that I checked Widewine status.
So I'm thinking I'm one of the unlucky ones who lost their L1 status via official update from OnePlus.
Shredz98 said:
Play store is certified. I wonder whether it is because I bought the 8 pro and it immediately updated to 10.5.12EU i believe it was but then I unlocked bootloader and went to OOS 11 DP3 though I didn't root nor check my Widewine status then, then updated to DP4 and then to OB1. It was only on OB1 that I rooted my phone and installed Magisk and only then that I checked Widewine status.
So I'm thinking I'm one of the unlucky ones who lost their L1 status via official update from OnePlus.
Click to expand...
Click to collapse
I was L3 until update 10.5.10 (or maybe 10.5.9). After that L1 all the way. I even clean installed DP4, updated to unrooted OB1, rooted, and still L1.
I would suggest that you MSMDtool back to an earlier OOS, unlock and root (and fix fingerprint issue that relocking BL causes), and then check L1 status. If it's L1 you should be good to update to OB1 again and root. I know I was L3 before that one update från OP so it's definetly reversable.
efex said:
I was L3 until update 10.5.10 (or maybe 10.5.9). After that L1 all the way. I even clean installed DP4, updated to unrooted OB1, rooted, and still L1.
I would suggest that you MSMDtool back to an earlier OOS, unlock and root (and fix fingerprint issue that relocking BL causes), and then check L1 status. If it's L1 you should be good to update to OB1 again and root. I know I was L3 before that one update från OP so it's definetly reversable.
Click to expand...
Click to collapse
Had a feeling you would say this and honestly the only reason I didn't MSMDtool back to an earlier OS is because of the whole fingerprint issue and scared of not being able to fix it.
I'll see what I can do, thanks mate!
Shredz98 said:
Had a feeling you would say this and honestly the only reason I didn't MSMDtool back to an earlier OS is because of the whole fingerprint issue and scared of not being able to fix it.
I'll see what I can do, thanks mate!
Click to expand...
Click to collapse
The fingerprint issues is easy to fix, I've done it a couple of times myself.. The instructions are good so just do what it says.
efex said:
The fingerprint issues is easy to fix, I've done it a couple of times myself.. The instructions are good so just do what it says.
Click to expand...
Click to collapse
Does the fingerprint issue always happen when relocking the bootloader or just sometimes? Anything I can do to avoid it?
Shredz98 said:
Does the fingerprint issue always happen when relocking the bootloader or just sometimes? Anything I can do to avoid it?
Click to expand...
Click to collapse
Not sure about that.. I've run the msmdtool twice, had to fix the reader both times.
efex said:
Not sure about that.. I've run the msmdtool twice, had to fix the reader both times.
Click to expand...
Click to collapse
Ugh, I'll now need to figure out whether L1 is worth it ?

Categories

Resources