This device isn’t Play Protect certified

Support & help
,
22

image
image862×545 33.9 KB

I have the same error

23

Did you switch to developer mode? And please add more information about your device.

24

after I restart the computer, the developer mode still cannot enable

my device info:

Screenshot 2024-03-27 18.38.13
Screenshot 2024-03-27 18.38.131057×948 51.6 KB

25

Screenshot 2024-03-27 18.35.54
Screenshot 2024-03-27 18.35.541011×369 24.6 KB

try restarted fewf time, still not able to enable developer mode

26

Screenshot 2024-03-27 18.37.09
Screenshot 2024-03-27 18.37.09745×443 20 KB

fydeos 18, I have this issue after upgrade from 17.1 to 18

27

Is it a chromebook? A laptop? or a desktop? We need to gather more information. And please send feedback in the system.

28

It is a laptop, XiaoMi laptop

Screenshot 2024-03-27 18.52.01
Screenshot 2024-03-27 18.52.01630×612 37 KB

29

Appears to happen exclusively to those who ‘upgrade’ it other than reflashing them.

30

Can you try to flash v18, run it in the USB and switch to developer mode? If it can be determined to be OTA related, it would be a good clue.

31

I have Lenovo L540 notebook, i try after update from 17 to 18, and after installing fydeos 18 from usb and have the same error

32

Screenshot 2024-03-27 21.07.35

33

Please check the BIOS to see whether it’s on legacy boot.

34

Please check the BIOS to see whether it’s on legacy boot.

35

If your device can’t be switched to developer mode, you can try to switch to UEFI boot in BIOS, some users have successfully solved the problem.

1 Like
36

Succes! Change into UEFI only in bios enable developer mode in FydeOS, Thank You :slight_smile:

37

No, I installed it by flashed USB and I have the same problem, I put the system on my laptop

38

That worked for me in 24h
I am using Asus viviobook intel core i3-7th

39

This is happening to all the users who updated from 17 to 18. I have got the thing done :).
For some reason the ‘shell’ command in cosh and dev mode is not working and that is not the thing I am going to fix. I used adb and Device ID apk to do things. Here is how.

  1. Enable the Linux Subsystem(if you have you are good :slight_smile: )
  2. type sudo apt-get update && sudo apt-get install adb
  3. Now adb connect 100.115.92.2:5555
  4. It will pop up android windows and ask for authorization. Do that.
  5. So type adb devices
  6. If it says unauthorized type adb kill-server Then adb start-server
  7. You can try reboot if unauthorized stays.
  8. Download the Device ID apk and move it to the linux file system from downloads.
  9. so type ls
  10. Copy the app name ( if there is ’ ’ with the name copy that too)
  11. type adb install <the app name>
  12. It should say success.
  13. Go to https://www.google.com/android/uncertified
  14. Login to your gmail.
  15. copy the GSF ID and paste it in the box.
  16. Hit registered.
  17. shutdown your device and go do something else. It should be working after a while.
    Make sure you have registered android ids at the bottom of the registration page after registration.
1 Like
40

ChromeOS old weys ! :rofl: the cloud ready neverware weys… adb wax on / wax off… Not needed just turn in the developer mode and disable rootfs.

41

Hi, I tried to apply all the instructions but at the end I have a syntax error and i could not install device id. How can i fix it.

Screenshot 2024-04-10 20.01.19