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.
Has anyone had any luck with flashing twrp and getting it to stay without flashing supersu? I can flash it but it resets every time the phone restarts and It won't allow any system mods.
I don't really want supersu on there as it doesn't allow me to play pogo, unless someone knows a working way around both.
anthonymackay said:
Has anyone had any luck with flashing twrp and getting it to stay without flashing supersu? I can flash it but it resets every time the phone restarts and It won't allow any system mods.
I don't really want supersu on there as it doesn't allow me to play pogo, unless someone knows a working way around both.
Click to expand...
Click to collapse
You can try to delete recovery-from-boot.p or rename it to
. bak under system, that should keep twrp.
Edit: doesn't magisk hide allow you to play pogo, sry don't play those games.
From Heisenberg's Unlock/Root/Flash Nexus 6P thread...
DP4 tmobile users, are you having a better experience with your LTE connection on the new bootloader?
Hi is there any way to complete disable navbar on Oreo without root ? Because every app i tried, when I swipe up it show navbar...
I want the opposite.
Is there a way to permanently show the navbar. Even in fullscreen apps and pictures and videos?
I'm on Oreo stock ROM S8 with Magisk root.
Immersive mode is the most annoying thing I can think of.
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 ...
I've recently flashed the PicselExperience rom and i noticed that i cant change the AOD to what i want, i tried downloading other apps from the play store but they all dont have a custom image aod feature(except one though, its paid and it's really bad).
I have flashed magisk so apps with root are a ok.