Hello, I install a custom ROM in November and I return to stock rom for OTA but my device is not certified by Google play protect when I return to stock ROM
Any help for get Google play protect certification in stock ROM ?
YouTube ban guy said:
Hello, I install a custom ROM in November and I return to stock rom for OTA but my device is not certified by Google play protect when I return to stock ROM
Any help for get Google play protect certification in stock ROM ?
Click to expand...
Click to collapse
Just register your device by using your GSF ID on the play protect registration page (Google it). Use the app named Device ID on play store for the GSF ID.
This works for custom roms too.
Njaiker said:
Just register your device by using your GSF ID on the play protect registration page (Google it). Use the app named Device ID on play store for the GSF ID.
This works for custom roms too.
Click to expand...
Click to collapse
with this you just make sure that you can continue to use the google services on a modifies system . the "uncertified" label doesent goes off on play store settings . you continue as uncertified still having the limitation of an uncertified device .
---------- Post added at 04:32 PM ---------- Previous post was at 04:27 PM ----------
YouTube ban guy said:
Hello, I install a custom ROM in November and I return to stock rom for OTA but my device is not certified by Google play protect when I return to stock ROM
Any help for get Google play protect certification in stock ROM ?
Click to expand...
Click to collapse
its a weird situation . i just wanted the api2 , but i had to unlock my bl to do that . now i'm uncertified . we have to relock bl to get back certification , gona loose api2 though .the only workaround i can think of is root!!! and pass safetynet with magisk . theres a workaround for ota updates with magisk also .
consumimur said:
with this you just make sure that you can continue to use the google services on a modifies system . the "uncertified" label doesent goes off on play store settings . you continue as uncertified still having the limitation of an uncertified device .
---------- Post added at 04:32 PM ---------- Previous post was at 04:27 PM ----------
its a weird situation . i just wanted the api2 , but i had to unlock my bl to do that . now i'm uncertified . we have to relock bl to get back certification , gona loose api2 though .the only workaround i can think of is root!!! and pass safetynet with magisk . theres a workaround for ota updates with magisk also .
Click to expand...
Click to collapse
No, it says certified. Just clear the data of play store after the registration.
I unlocked my bootloader just for some tweaks I wanted to do, unlocking the bootloader tripped the safetynet. After installing Magisk and passing the Safetynet and CTS check. I did this and it worked. Play store was play protect certified.
As OP's bootloader is locked. Safetynet should be intact. So, this procedure should work.
Njaiker said:
No, it says certified. Just clear the data of play store after the registration.
I unlocked my bootloader just for some tweaks I wanted to do, unlocking the bootloader tripped the safetynet. After installing Magisk and passing the Safetynet and CTS check. I did this and it worked. Play store was play protect certified.
As OP's bootloader is locked. Safetynet should be intact. So, this procedure should work.
Click to expand...
Click to collapse
as you said and i mentioned , it says certified cause you are rooted and you are passing safety net with magisk . i'm not rooted to recieve ota and my bl is unlocked to use api2 so i'm uncertified .
clean the data ? ( smile
My problem is solved because I have my certification back when I lock the bootloader
Related
From Endgadget: https://www.engadget.com/2018/03/26/google-starts-blocking-its-apps-on-uncertified-android-devices/
If you're fond of loading custom ROMs on your Android phone, life just became complicated. Google has quietly started blocking access to its apps on uncertified devices whose firmware was built after March 16th. If you're affected, you'll get a warning that a device is "not certified" and can't sign into a Google account. This won't prevent you from loading ROMs, but you'll have to register your device IDs on a white list every time you undergo a factory reset -- when there's a 100-ID limit, you could run into problems if you're routinely wiping your phone to install new firmware.
We've asked Google for comment on the move.
The company is already quite clear about the rationale, however. Vendors officially need to get certification to load Google apps (Android's licensing model is built around this), but some of them ignore this requirement and either load the apps regardless or encourage you to download them yourself. This new block theoretically pushes those less-than-scrupulous brands to clean up their acts by either obtaining certification or sticking to an AOSP version of Android, where they'd depend on third-party apps.
The problem, of course, is that it leaves custom ROM users caught in the crossfire. They may have to be more selective about when they install ROMs and skip minor updates. It's far from the end of custom firmware, but the era of anything-goes firmware (on phones that allowed custom ROMs in the first place, that is) might be winding down.
I was just posting a thread about this aswell. My thoughts are more focused around the app store. How will we access the app store? Are we able to hack / "pirate" the app store apk or is the mod community going to have to start a separate app store? Maybe even twrp install every app we use?
Stop using wonky ass roms, if your rom passes safetynet and certifies your device, you won't need to do this. DU has been passing as certified for like a week now, even before the issue was made public. I made 2 clean flashes yesterday and haven't faced the issue. SO if rom devs fix their stuff, there won't be any need for IMEI or androidID registration.
As you can see my OnePlus 5 is listed as uncertified and I'm on stock OpenBeta 7 with no root or any other mod. Only my bootloader is unlocked that's it. BTW I flash the OpenBeta 7 clean with a erase everything and setup the phone without any issues :good:
Sent from my OnePlus 5 using XDA Labs
Is the certification check is going to be based on Bootloader lock status or ROMs????
I am confused.....
smohanv said:
Is the certification check is going to be based on Bootloader lock status or ROMs????
I am confused.....
Click to expand...
Click to collapse
If I remember me right I look at that before I unlock my bootloader and it shows me certified after the unlock it shows me uncertified, to me it seems it is based on a locked or unlocked bootloader, but I can be wrong this have to answer the gurus here :good:
Sent from my OnePlus 5 using XDA Labs
GraveDigger176 said:
If I remember me right I look at that before I unlock my bootloader and it shows me certified after the unlock it shows me uncertified, to me it seems it is based on a locked or unlocked bootloader, but I can be wrong this have to answer the gurus here :good:
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
mmmm....... so, if this is the case rooting is going to a an issue... until an exploit is found we may have to lock bootloader back and stay without rooting for a while.
Let us wait for more knowledge coming on this subject before we think of any action... at the moment my device is rooted and also I am running crDroid (Oreo 8.1) and also using magisk with Safety Net passed so that I am able to use Google Pay.
GraveDigger176 said:
As you can see my OnePlus 5 is listed as uncertified and I'm on stock OpenBeta 7 with no root or any other mod. Only my bootloader is unlocked that's it. BTW I flash the OpenBeta 7 clean with a erase everything and setup the phone without any issues :good:
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
I clean flashed OB7 on my OnePlus 5, my bootloader is set back to locked as well and my device says certified.
Maybe it's because of the unlocked bootloader that you see uncertified?
dazr87 said:
I clean flashed OB7 on my OnePlus 5, my bootloader is set back to locked as well and my device says certified.
Maybe it's because of the unlocked bootloader that you see uncertified?
Click to expand...
Click to collapse
Yeah it seems so, but i have clean flash OpenBeta 7 with erase everything and unlocked bootloader and setup the Phone without any problems, I let it as it is now until i got problems with signing in google account after a clean flash :good:
I think certified or uncertified it depends on your rom, because my device still showed me certified status, with unlocked bootloader rooted with magisk, yes it's strange but somehow I'll look after it since I'm still waiting the open beta release to stable
Ps: sorry I can't upload screenshot because my xda app keeps saying bad request
sendashano said:
I think certified or uncertified it depends on your rom, because my device still showed me certified status, with unlocked bootloader rooted with magisk, yes it's strange but somehow I'll look after it since I'm still waiting the open beta release to stable
Ps: sorry I can't upload screenshot because my xda app keeps saying bad request
Click to expand...
Click to collapse
Well then is stock OpenBeta 7 crap :laugh:
BTW then all OOS stock roms crap since I unlock the bootloader it shows me uncertified :good:
Sent from my OnePlus 5 using XDA Labs
My OP5 is running stock OB 7, with an unlocked boot loader. I'm not rooted. When I got mine used off of Swappa, I made sure to unlock the bl and then flashed the OB 5 fw. Since then I've taken the OTA's for OB 6 and 7. No issues and my device is certified in the Play Store.
Mine is stock ROM Nougat 7.1 with unlocked bootloader and root and my device is uncertified.
AEX-Rom Oreo, decrypted, rooted with Magisk shows certified.
This is no problem with stock/nonstock/root etc.
Maybe Magisk helps to be certified
Google says that will not uncertified the custom roms
I'm on ob7 unlocked bootloader with magisk installed and shows me certified
OOS 5.04, unlocked bootloader, magisk 16.0 - uncertified!!
I'm on xXx NoLimits 10.1 Stable 5.04 and rooted (Magisk 16.3) with an unlocked bootloader. No problems here.
Hello
I would like to use google pay, but the application informs about phone modification and can not be used.
The phone has unlocked the bootloader, I do not have root. I am on the CLT-L29C432B131 using the HuRUpdater method.
In google play information - no certificate. Is this a problem and how to avoid it?
Same issue here
Unlocked bootloader and now Google Pay isn't working
Unlocking the bootloader breaks safety net. Relock it & you should be ok.
anyone found a workaround? currently trying to install the apk from another phone, will report back
edit: apparently sideloading the apk works. does anyone know why it wouldnt be "compatible" according to the google play store?
Netflix is working on my end. Have you rooted or anything? I'm pure stock for now, just got her today and loving it so far.
GavinMazey said:
Netflix is working on my end. Have you rooted or anything? I'm pure stock for now, just got her today and loving it so far.
Click to expand...
Click to collapse
Nope, stock everything besides unlocked bootloader. I am liking the phone a lot other than this and the battery life
Check in settings on your Play Store account at the bottom to see if your phone listed as Certified. After I unlocked the Bootloader on my X4, phone became Uncertified and had to get Netflix app from other source.
jfalls63 said:
Check in settings on your Play Store account at the bottom to see if your phone listed as Certified. After I unlocked the Bootloader on my X4, phone became Uncertified and had to get Netflix app from other source.
Click to expand...
Click to collapse
yeah this is it, seems stupid to me
bird412 said:
yeah this is it, seems stupid to me
Click to expand...
Click to collapse
If your bootloader is unlocked, you may be tripping Safetynet as well - if SafetyNet is tripped, Netflix may not show up as compatible or show up at all: https://www.xda-developers.com/netf...lly-a-new-feature-in-the-google-play-console/ https://www.xda-developers.com/netflix-app-currently-unavailable-for-rootedunlocked-users/
You could try rooting with magisk to try to hide the bootloader unlocked status or re-lock your bootloader.
echo92 said:
If your bootloader is unlocked, you may be tripping Safetynet as well - if SafetyNet is tripped, Netflix may not show up as compatible or show up at all: https://www.xda-developers.com/netf...lly-a-new-feature-in-the-google-play-console/ https://www.xda-developers.com/netflix-app-currently-unavailable-for-rootedunlocked-users/
You could try rooting with magisk to try to hide the bootloader unlocked status or re-lock your bootloader.
Click to expand...
Click to collapse
ah that makes sense. i sideloaded the app and its working fine right now, ill probably wait for a more stable twrp release to try it out
I have Indian Redmi K20 Pro. I am thinking of unlocking the bootloader and installing some custom rom.
Is there any unsolvable permanent issue possible due to unlocking? I have read about some issues with sensors, Widewine L1 certification etc.
Its completely safe to unlock the bootloader, follow any tutorial on YouTube and follow the instructions. If you're phone gets bricked in fastboot mode you can reflash stock rom and lock the bootloader again using mi tool.
Go with gut, theres first time for everything.
I have been using custom roms and rooting my devices since 2016 and I love to flash plethora of roms.
I'm using evolution X with immensity kernel and phone is smooth as slime.
saiprasanna1100 said:
Its completely safe to unlock the bootloader, follow any tutorial on YouTube and follow the instructions. If you're phone gets bricked in fastboot mode you can reflash stock rom and lock the bootloader again using mi tool.
Go with gut, theres first time for everything.
I have been using custom roms and rooting my devices since 2016 and I love to flash plethora of roms.
I'm using evolution X with immensity kernel and phone is smooth as slime.
Click to expand...
Click to collapse
Thanks for the input. What is your experience with the banking (and other such apps) on custom roms?
dwellexity said:
Thanks for the input. What is your experience with the banking (and other such apps) on custom roms?
Click to expand...
Click to collapse
Banking apps don't work on most roms as unlocked bootloader and root is detected by the apps by reading phone state via app permissions in android. Don't root/Unlock bootloader if you have only one android phone as you will not be able to use banking financial apps. There are several workarounds to this but still it is not advised to root/unlock bootloader if you are not comfortable with this issue.
Adv.Chirag said:
Banking apps don't work on most roms as unlocked bootloader and root is detected by the apps by reading phone state via app permissions in android. Don't root/Unlock bootloader if you have only one android phone as you will not be able to use banking financial apps. There are several workarounds to this but still it is not advised to root/unlock bootloader if you are not comfortable with this issue.
Click to expand...
Click to collapse
I am comfortable with the workarounds. I have used rooted phones in the past. The question is: Do the workarounds (magisk hide etc.) actually work reliably? This is my only phone.
dwellexity said:
Thanks for the input. What is your experience with the banking (and other such apps) on custom roms?
Click to expand...
Click to collapse
I haven't faced any problems with banking apps in evolution X without root.
If you root your mobile you can hide using magisk manager- magisk hide and rename the magisk to any other name (in the hide option)
And if you still face a problem you can use this app called ISLAND in playstore, it creates a dual space in rom and you can use banking apps there.
Using PE (Plus edition) on my K20 pro (Indian version) with all the UPI and banking apps working (I'm not rooted, by the way) without a single issue. Widevine is L1 (not sure how Xiaomi devices are able to retain WVL1 even after unlocking BL and flashing custom ROMs. Devices from other manufacturers such as 1+, Realme, Oppo, Samsung, LG break WV as soon as you unlock the BL).
dwellexity said:
I have Indian Redmi K20 Pro. I am thinking of unlocking the bootloader and installing some custom rom.
Is there any unsolvable permanent issue possible due to unlocking? I have read about some issues with sensors, Widewine L1 certification etc.
Click to expand...
Click to collapse
I have successfully unlocked the bootloader with no apparent issues. L1 certification is working. No apps detect the system as rooted or insecure.
I am using Pixel Experience with OrangeFox recovery. I didn't flash magisk.
dwellexity said:
I have successfully unlocked the bootloader with no apparent issues. L1 certification is working. No apps detect the system as rooted or insecure.
I am using Pixel Experience with OrangeFox recovery. I didn't flash magisk.
Click to expand...
Click to collapse
Using unlocked bootloader phone asap after buying. Used root too with all banking apps as well as other all types of applications running smooth with magisk hide.
I hv used bliss os... Evolution... But presently on latest miui stable build for multi window feature and better systemwide dark mode preformance.
Adv.Chirag said:
Banking apps don't work on most roms as unlocked bootloader and root is detected by the apps by reading phone state via app permissions in android. Don't root/Unlock bootloader if you have only one android phone as you will not be able to use banking financial apps. There are several workarounds to this but still it is not advised to root/unlock bootloader if you are not comfortable with this issue.
Click to expand...
Click to collapse
After unlock bootloader my Google pay,phone and other banking related apps keep stopping how to solve this issue
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
[email protected] said:
Using unlocked bootloader phone asap after buying. Used root too with all banking apps as well as other all types of applications running smooth with magisk hide.
I hv used bliss os... Evolution... But presently on latest miui stable build for multi window feature and better systemwide dark mode preformance.
Click to expand...
Click to collapse
What is best why to root via patched boot or magisk.zip
chickentikka007 said:
After unlock bootloader my Google pay,phone and other banking related apps keep stopping how to solve this issue
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
What is best why to root via patched boot or magisk.zip
Click to expand...
Click to collapse
Magisk.zip
Hello.
How to active my play protect certification?
MIUI Version: MIUI Global 12.5.1 (12.5.1.0(RFKEUXM))
Android version: 11 (RQ1.200826.002)
I've tried all the ways I found on the internet, but none work. (https://www.google.com/android/uncertified/ .. etc)
Please help me!
Afaik there is a easy fix using Magisk Module (You have to root your device first and then install Magisk Manager) .
With locked Bootloader and stock ROM, there must be no problem with Device certification and Play protect (because stock ROMs are certified)
But if you unlocked Bootloader then SafetyNet fails, causing Device is not certified and Play Protect issue - in that case you have to either relock Bootloader or go with Magisk and USNF Magisk module to spoof that Bootloader is not unlocked