Close

What are you looking for?

cancel
Showing results for 
Search instead for 
Did you mean: 

device is not play protect certified

(Topic created on: 08-08-2022 09:12 AM)
12802 Views
Galaxy s21 new user
First Poster
Options

Hi,

 

A few weeks ago I purchased a new Samsung galaxy s21 device. Unfortunately, it's not play protect certified, and I cannot find any fix. The device is brand new, and is not rooted. I performed factory reset, but it didn't help. The model is on Google's supported devices list (SM-G991B), and I manually registered my device (using it's Google Service Framework ID).

What should be my next step? 

36 REPLIES 36
Christian125
Pioneer
Options

And just to be clear: there was no need to root the Phone and even no need to wipe it. I just had to flash the firmware for Europe and it has been installed like an Over the air Update from Samsung. After installing the firmware i had to reactivate the credit cards via my bankaccount in google wallet. And thats it. 

ARPcPro
Explorer
Options

Thank you @Christian125 . I will flash the Home_CSC and try to follow the other instruction on those links. I was not even considering flashing because I did not wanted to wipe the phone. And now I know better than to accept the OTA updates. I will not accept them unless it is a major operating system change or OneUI version.

0 Likes
Christian125
Pioneer
Options

Let me know if that worked for you.

In my Opinion you can accept OTA Updates. If you are on your CSC you should get the regional pendant. Thats how i understood the whole Thing. At least it's worth a try. 

0 Likes
ARPcPro
Explorer
Options

Flashing the Home_CSC EUX did not work for me. Immediately after booting, the icons of OneUI were reset. All my folders and shortcuts for 300 apps were gone. But the internal memory was not wiped. All the apps were there.

Google Wallet still did not work. I uninstalled the Play Store updates, cleared the data and cache for both the Play Store and Google Services, but still nothing. Reinstalling Google Wallet didn’t help either.

I connected to SamFw to confirm that the CSC was EUX, and it was. I also tried the EUY Home_CSC, but that didn’t help.

The worst part was that after these changes, I got a warning: “Issue with SD card. Tap to fix. Format this SD card.” The SD card wasn’t even readable on my PC. I had to run chkdsk /f, and 160GB of data is now gone from my 512GB SD card.

I should have known better than to leave the SD card in during these risky operations. I think I’ll just buy a Chinese phone next time that doesn’t force me to do all these tricks just to have call recording. It’s not worth the trouble and hours lost.

0 Likes
Christian125
Pioneer
Options

I'm sorry to hear that. Where are you located? 

Have you flashed only the home_csc or even the other parts? 

0 Likes
ARPcPro
Explorer
Options

The phone came from Samsung Germany store. It has a German simcard and I am in Germany. I've flashed only the files named HOME_CSC EUX with Odin. Then HOME_CSC EUY, then again HOME_CSC EUX, SamFw change CSC, and finally went back to HOME_CSC THL. With THL I can still receive OTA. I think it was SamFw or the EUX flash that messed up the SD card. The entire "Recording" folder is gone, where the calls were saved. And I should have removed the SD card and Sim card before using SamFw. I forgot that recommendation.

0 Likes
Christian125
Pioneer
Options

You should have put all files in the right slots in odin (all slots except userdata should be filled AND MAKE SURE U USE HOME_CSC IN CSC SLOT as otherwise data will be wiped). 

Thats how it should be described everywhere.

Falls noch Unklarheiten bestehen, kannst du auch gern auf Deutsch fragen. Es ist im Grunde überall zu lesen, dass das Freischalten des Call Recordings den Effekt mit sich bringt, dass der Regionalcode nicht mehr mit deinem Gerät bzw. deiner Sim Karte übereinstimmt und deshalb das mobile Zahlen nicht mehr funktioniert.

Was heißt denn "wallet funktioniert nicht"? Erhältst du denn die Nachricht "Device is not play protect certified"?

Bist du sicher, dass du die richtige Firmware für dein Gerät heruntergeladen hast? Bei mir gab es keine EUX - Version. Ich musste eine deutsche nehmen (DBT). Es wurde dann aber automatisch EUX daraus übernommen 

0 Likes
ARPcPro
Explorer
Options

It was the first time that I used Odin. I definitely did not put all files in the slots. I just used the Home_CSC in the CSC slot. I've left everything else empty.

You wrote that you have changed the CSC to OXM and EUX and now everything is working fine again. But in reality it appears that you flashed a complete firmware to the phone with AP, BL, CP, Home_CSC. 

The Google Wallet was working fine before until I accepted the OTA update last July. Now it says "This device can't be set up to pay contacless. Your device doesn't meet security standards...." and PlayStore shows not certified.

Thanks for your suggestion. I will then flash completely a firmware from another region (EUX) to the phone, using the HOME_CSC instead of the other CSC. I just hope it doesn't wipe it.

Edit: Then, to get the call recorder back, should I flash again the complete firmware THL firmware, using the Home_CSC of THL. How did you get it back? On my phone model ILO and THL are only available in the Asia firmware. The European does not allow me to change to those regions.

0 Likes
Christian125
Pioneer
Options

Did it work for you? 

You dont get the call recorder Feature back. That is a regional restriction. You have to choose, mobile payment or call recorder. ILO and THL are not available in the European Firmware. For no one! It's a European Firmware! With that you just can choose between the European country Codes/csc's

0 Likes
ARPcPro
Explorer
Options

I haven't tried yet. Do you confirm that a complete flash with AP, BL, CP, Home_CSC EUX will not wipe the device?

I can try the EUX firmware, see if the Wallet works, and then either flash only the THL Home_CSC to see if it activates the call recorder. Or full flash of the complete THL firmware.

Unfortunately I cannot downgrade to the last working THL firmware from 2024-06-01 because it is Bit SW Rev 6. When I accepted the  2024-07-01 it updated the device to Bit SW Rev 7. Otherwise I would downgrade the THL, the Google Wallet would work and the problem would be solved.

0 Likes