casualsnek / waydroid_script

Python Script to add OpenGapps, Magisk, libhoudini translation library and libndk translation library to waydroid !
GNU General Public License v3.0
1.65k stars 157 forks source link

"This device isn't Play Protect certified" even after registration #26

Open Heath123 opened 2 years ago

Heath123 commented 2 years ago

image

I've registered the device and waited a few days I've also cleared the cache and storage many times

casualsnek commented 2 years ago

image

I've registered the device and waited a few days I've also cleared the cache and storage many times

Did you reinit or completely reinstalled waydroid ? This will change your device id too ! Can you check your current device id and open the google's device registration page and confirm that current device id is registered ? ( Registered device id's are listed at bottom of device registration page )

Heath123 commented 2 years ago

image I've registered the device and waited a few days I've also cleared the cache and storage many times

Did you reinit or completely reinstalled waydroid ? This will change your device id too ! Can you check your current device id and open the google's device registration page and confirm that current device id is registered ? ( Registered device id's are listed at bottom of device registration page )

No, I didn't, and yes, my ID still matches what's listed on the page, both with the helper script and a Device ID app

Heath123 commented 2 years ago

I could try reinstalling if that could make it work

casualsnek commented 2 years ago

I could try reinstalling if that could make it work

Since device registration is something only google can handle, reinstalling and starting over is the only thing we can do, maybe different id gets registered properly :(

danyisill commented 2 years ago

I had the same thing, but it worked after waiting like 5 minutes.

GAMER-H2 commented 2 years ago

I'm currently have this issue as well. It's been a few hours since I registered so I will see if it works in 24 hours times since google may be taking a while to register it.

curiousercreative commented 2 years ago

This sounds like an issue that affects all custom ROMs and requires device fingerprint spoofing to pass.

Heath123 commented 2 years ago

Now it stopped doing that but does this instead: image Sometimes it says about not being able to connect to Google servers or something

Heath123 commented 2 years ago

image After waiting for a bit

KingWaffleIII commented 2 years ago

I also got this error, OP, but what I did was add my Google account in the Accounts section in the Settings app. One reboot later and Play Store worked fine.

Nakamerica commented 2 years ago

Hi, i have the same issue, i added my google account through settings > accounts and also registered my device id, but it's still not certified... please let me know if I can do anything to fix this, it has been a couple of days now.

Heath123 commented 2 years ago

I also got this error, OP, but what I did was add my Google account in the Accounts section in the Settings app. One reboot later and Play Store worked fine.

I tried that but I just get this again: image

Nakamerica commented 2 years ago

I also got this error, OP, but what I did was add my Google account in the Accounts section in the Settings app. One reboot later and Play Store worked fine.

I tried that but I just get this again: image

hm that's interesting, I can sign in with my google account just fine, it's just that the play store refuses to be certified

Heath123 commented 2 years ago

I also got this error, OP, but what I did was add my Google account in the Accounts section in the Settings app. One reboot later and Play Store worked fine.

I tried that but I just get this again: image

hm that's interesting, I can sign in with my google account just fine, it's just that the play store refuses to be certified

I got that error before and now it started doing this

JordanViknar commented 2 years ago

I also got this error, OP, but what I did was add my Google account in the Accounts section in the Settings app. One reboot later and Play Store worked fine.

I was able to connect to my Google Accounts in the settings, but Play Store still refuses to work for me. I still have microG installed from before I installed GAPPS using this script, perhaps microG is conflicting ?

JordanViknar commented 2 years ago

Update : Google Play Services now works properly, since I tried Waydroid many days ago. I guess it just took a pretty long time for them to actually add my device.

I don't think this issue is caused by this script at all, so perhaps it should be closed ?

Nakamerica commented 2 years ago

Update : Google Play Services now works properly, since I tried Waydroid many days ago. I guess it just took a pretty long time for them to actually add my device.

It took 15 days for your device to be certified?

Idcrafter commented 1 year ago

i would suggest using microG and AuroraStore witch both let you Optionally sign-in and work right out of the box

benintech commented 1 year ago

I had to wait about 6 hours after registration. I restarted many times my Waydroid session, until after about 6 hours the "device isn't Play Protect certified" message finally went away, and I can now use my google account.

AlexR012 commented 1 year ago

Encontre una forma de registrar la certificacion de play protect, descargue esta app "https://www.apkmirror.com/apk/evozi/device-id/device-id-1-3-2-release/device-id-1-3-2-android-apk-download/" luego copie el ID de Google Services Framework que me da la app y lo registre aqui "https://www.google.com/android/uncertified/" (al escribir el ID saldra en rojo pero ignorenlo), despues de registrarlo detuve Google Play Services y borre los datos, reinicie Waydroid y listo

dustojnikhummer commented 1 year ago

I had to wait about 6 hours after registration. I restarted many times my Waydroid session, until after about 6 hours the "device isn't Play Protect certified" message finally went away, and I can now use my google account.

I had to reinstall Waydroid once to get a different ID, but it took 5 minutes, system reboot and force closing Play Store and Play Services

Aman9das commented 1 year ago

Just cleaning play services cache is needed

rodneycheung commented 1 year ago

For those who try to find a solution, this is the one.

You need to register the device on google's database

In order to get the device id, refer to this post

dustojnikhummer commented 1 year ago

For those who try to find a solution, this is the one.

You need to register the device on google's database

In order to get the device id, refer to this post

As I said, sometimes it is possible a GMS ID gets generated is already used, then you must rebuild Waydroid from scratch.

And that post's guide is overcomplicated.

Install https://f-droid.org/en/packages/makeinfo.com.getid/

Register it with Google https://www.google.com/android/uncertified

Wait 10 minutes, clear cache of Play Store and Play Services and it should work

luisg595 commented 1 year ago

Encontre una forma de registrar la certificacion de play protect, descargue esta app "https://www.apkmirror.com/apk/evozi/device-id/device-id-1-3-2-release/device-id-1-3-2-android-apk-download/" luego copie el ID de Google Services Framework que me da la app y lo registre aqui "https://www.google.com/android/uncertified/" (al escribir el ID saldra en rojo pero ignorenlo), despues de registrarlo detuve Google Play Services y borre los datos, reinicie Waydroid y listo

This work for me! Thanks

dhelafrank commented 1 year ago

image

I've registered the device and waited a few days I've also cleared the cache and storage many times

Please how can I clear cache

dhelafrank commented 1 year ago

I have the same issue, device registered in Google but the notification still pops up

dhelafrank commented 1 year ago

I have the same issue, device registered in Google but the notification still pops up

fixed this 😅 Had to stop and restart waydroid-container-services Came back up and everything was fixed.

emarcanor commented 1 year ago

This error solved this way: 1) open terminal 2) sudo waydroid shell 3) copy and paste all:

ANDROID_RUNTIME_ROOT=/apex/com.android.runtime ANDROID_DATA=/data ANDROID_TZDATA_ROOT=/apex/com.android.tzdata ANDROID_I18N_ROOT=/apex/com.android.i18n sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "select * from main where name = \"android_id\";"

4) This show you an android id same : android_id|2845653241515221950 , Only copy the numbers

5) Go to Google url: https://www.google.com/android/uncertified

6) Paste the android_id result of point # 4 and register this on google

7) Open waydroid stop and clear data of Google play Services

8) open playstore and joy :+1:

chenxiex commented 1 year ago

I had the same problem. And after I clean all the cache and storage of google play store and google play service in "Settings"->"App & notifications", it is solved.

ghost commented 1 year ago

Just cleaning play services cache is needed

thank you @Aman9das the only solution worked for me is this

dustojnikhummer commented 1 year ago

This error solved this way:

  1. open terminal
  2. sudo waydroid shell
  3. copy and paste all:

ANDROID_RUNTIME_ROOT=/apex/com.android.runtime ANDROID_DATA=/data ANDROID_TZDATA_ROOT=/apex/com.android.tzdata ANDROID_I18N_ROOT=/apex/com.android.i18n sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "select * from main where name = "android_id";"

  1. This show you an android id same : android_id|2845653241515221950 , Only copy the numbers
  2. Go to Google url: https://www.google.com/android/uncertified
  3. Paste the android_id result of point # 4 and register this on google
  4. Open waydroid stop and clear data of Google play Services
  5. open playstore and joy 👍

As I already said, ADB isn't necessary. This fdroid app can show you the necessary ID https://f-droid.org/en/packages/makeinfo.com.getid/

Viktini commented 1 year ago

Set Waydroid up for the first time with GAPPS, it still nags me about it not being certified even though I have registered it to my Google account. I don't buy that it's already been used because Google will have stopped me from using the code if it has. The worst part is that the services constantly nag me that it's uncertified unless I put it on DND. Almost certainly been an hour since I added it too.

EDIT: Nvm, it worked. Either clearing the cache or just waiting fixed it.

xiao-mantou commented 6 months ago

This one can be installed without bypass the SDK block in Android 14. I just leave it here in case someone need it.