Issue type
Feature not working as intended
Device
OnePlus 9 Pro 5G (lemonadep)
crDroid version
crDroid 12
Exact version / Build date
12.11/2026-06-27
Bug description
After performing a completely clean installation of the latest official crDroid Android 16 build on a OnePlus 9 Pro (lemonadep), Google Play Services successfully performs check-in but the device never becomes Play Protect certified.
Observed behavior:
• Play Store reports "Device is not certified".
• Play Integrity API returns:
- App Integrity: UNEVALUATED
- Device Integrity: UNEVALUATED
- Play Protect Verdict: UNEVALUATED
- Licensing Verdict: UNEVALUATED
• TB Checker reports no GSF ID.
However, Google Play Services successfully completes check-in and stores a valid Android ID internally.
Evidence collected:
• checkin_id_token exists
• Checkin.xml contains:
android_id = 4427078468136666482
• /data/user/0/com.google.android.gms/databases/gservices.db exists and contains the same android_id.
• Google account login succeeds.
• Google Play Services functions normally.
However:
• /data/user/0/com.google.android.gsf/databases is never created.
• Legacy GSF state never appears to initialize.
• Device never becomes Play Protect certified.
This issue occurs on a completely clean installation before rooting. KernelSU, Zygisk, and Play Integrity Fix were only installed later for debugging and are not required to reproduce.
During investigation I verified that Google Play Services successfully completes check-in, stores a valid android_id, and creates gservices.db, but Google Services Framework never creates its own database and the Play Integrity API remains UNEVALUATED.
Steps to reproduce
- Clean flash latest official firmware.
- Flash latest official crDroid Android 16.
- Reboot recovery.
- Flash MindTheGapps ARM64 Android 16.
- Boot system.
- Sign into Google account.
- Wait for Play Services check-in to complete.
- Open Play Store.
Result:
Play Store remains "Device not certified".
Play Integrity API returns UNEVALUATED verdicts.
Google Play Services successfully performs check-in but Google Services Framework never provisions its database.
Relevant log (logcat/build log)
CheckinTask:ReceivedResponse
Updated ID in checkin_id_token file
setAndroidIdGservices, New Aid:4427078468136666482
Checkin.xml
android_id=4427078468136666482
sqlite3 gservices.db
android_id|4427078468136666482
ls /data/user/0/com.google.android.gsf/databases
No such file or directory
Screenshots or videos
No response
Solution
No response
Additional context
I tested both NikGApps and MindTheGapps on clean installations with identical behavior. I also tested with and without KernelSU, Zygisk Next, and Play Integrity Fix. The issue occurs on a completely clean installation before rooting, suggesting it is not caused by root or Play Integrity modules.
Acknowledgements
Issue type
Feature not working as intended
Device
OnePlus 9 Pro 5G (lemonadep)
crDroid version
crDroid 12
Exact version / Build date
12.11/2026-06-27
Bug description
After performing a completely clean installation of the latest official crDroid Android 16 build on a OnePlus 9 Pro (lemonadep), Google Play Services successfully performs check-in but the device never becomes Play Protect certified.
Observed behavior:
• Play Store reports "Device is not certified".
• Play Integrity API returns:
• TB Checker reports no GSF ID.
However, Google Play Services successfully completes check-in and stores a valid Android ID internally.
Evidence collected:
• checkin_id_token exists
• Checkin.xml contains:
android_id = 4427078468136666482
• /data/user/0/com.google.android.gms/databases/gservices.db exists and contains the same android_id.
• Google account login succeeds.
• Google Play Services functions normally.
However:
• /data/user/0/com.google.android.gsf/databases is never created.
• Legacy GSF state never appears to initialize.
• Device never becomes Play Protect certified.
This issue occurs on a completely clean installation before rooting. KernelSU, Zygisk, and Play Integrity Fix were only installed later for debugging and are not required to reproduce.
During investigation I verified that Google Play Services successfully completes check-in, stores a valid android_id, and creates gservices.db, but Google Services Framework never creates its own database and the Play Integrity API remains UNEVALUATED.
Steps to reproduce
Result:
Play Store remains "Device not certified".
Play Integrity API returns UNEVALUATED verdicts.
Google Play Services successfully performs check-in but Google Services Framework never provisions its database.
Relevant log (logcat/build log)
Screenshots or videos
No response
Solution
No response
Additional context
I tested both NikGApps and MindTheGapps on clean installations with identical behavior. I also tested with and without KernelSU, Zygisk Next, and Play Integrity Fix. The issue occurs on a completely clean installation before rooting, suggesting it is not caused by root or Play Integrity modules.
Acknowledgements