COPG-VD

English · العربية · Čeština · Deutsch · Español · فارسی · Français · हिन्दी · Bahasa Indonesia · Italiano · 日本語 · 한국어 · Nederlands · Polski · Português · Русский · Svenska · ไทย · Türkçe · Tiếng Việt · 中文

COPG-VD is a device spoofer: it rewrites the device fingerprint and build so apps see the device you choose instead of the real one.
It runs on Zygisk (KernelSU, APatch or Magisk) and, by default, scopes the spoof to the Google Play stack - so it is a lighter, more robust alternative to PlayIntegrityFix.

Screenshots

How to use?

Install the module, reboot, and the shipped profile (a Pixel) is spoofed to the targeted apps. With a working fingerprint you do not need PlayIntegrityFix or GooglePhotosUnlimited.
Everything is configured in /data/adb/COPG-VD.json, or from the WebUI. All fields are OPTIONAL - a field that is not provided is skipped.

Scope - who sees the spoof

scope_mode decides which processes get the spoofed identity. In a scoped mode the identity is delivered per process by Zygisk and is not leaked to the rest of the system through the global properties.

• Google Play (playstore, the default) - only the Play stack (Google Play services, its unstable process and the Play Store).
• Global - the whole device; every process sees it.
• Whitelist - only the apps in scope_whitelist.
• Blacklist - every app except the ones in scope_blacklist.

Engines - how the spoof is delivered

Each one is independent and can be turned off:

• Build fields (JNI) - rewrites android.os.Build.* in the targeted processes.
• Property hook - presents the spoofed system properties to the targeted processes (a clean-room per-process remap of the property area, no function hook).
• resetprop - rewrites the system properties, managed by group: identity, version, boot state, SELinux, adb/usb, anti-emulator and a cleanup pass. In a scoped mode the identity and version groups stay out of the device-wide resetprop (Zygisk delivers them per process); the boot/lock/SELinux groups stay global.
• DRM / Widevine (off by default) - reports a chosen Widevine security level, L1 or L3, to the apps that read it.

Fields - set, empty, delete or skip

Inside the COPG-VD object each Build field has four states:

• Set - "KEY": "value" writes the value.
• Empty - "KEY": "" writes an empty value.
• Delete - list the key in a top-level "COPG-VD-Delete": [ ... ] to remove it (a Build field becomes null, a property is removed with resetprop --delete).
• Skip - leave the key out entirely; the ROM's own value is kept.

A "global_fields": [ ... ] list applies the named Build fields device-wide even in a scoped mode, to keep a value consistent everywhere - for coherence-safe fields only (the security patch, for example), never identity and never the Android version group.

Example JSON config file

/data/adb/COPG-VD.json

{
  "Instructions": "Use strings on double-quotes only.",
  "Instructions": "All fields are OPTIONAL. If some field is not provided, it will be skipped.",
  "Strings extracted from": "https://dl.google.com/developers/android/CANARY/images/factory/tegu_beta-zp11.260918.007-factory-f5955275.zip",
  "scope_mode": "playstore",
  "COPG-VD": {
    "BRAND": "google",
    "DEVICE": "tegu",
    "MANUFACTURER": "Google",
    "MODEL": "Pixel 9a",
    "FINGERPRINT": "google/tegu_beta/tegu:CANARY/ZP11.260918.007/16484274:user/release-keys",
    "PRODUCT": "tegu_beta",
    "BOOTLOADER": "unknown",
    "BOARD": "tegu",
    "HARDWARE": "tegu",
    "DISPLAY": "ZP11.260918.007",
    "ID": "ZP11.260918.007",
    "HOST": "51b22e6d8afb",
    "INCREMENTAL": "16484274",
    "TIMESTAMP": "1790806751",
    "PREVIEW_SDK": "20261007",
    "USER": "android-build",
    "SDK_FINGERPRINT": "d9ad4b00fa641d6e43c42cc969f49492",
    "UUID": "_mQOcxvuFzRVZAjNEr2UUUpk2fv0mqDc8RpFyaeJjuk",
    "SECURITY_PATCH": "2026-10-05",
    "FIRST_API_LEVEL": "35",
    "DRM_SECURITY_LEVEL": "L1"
  },
  "motor_drm": false,
  "global_fields": ["SECURITY_PATCH"]
}

Be sure to use strings on double-quotes only.
The block above and module/COPG-VD.json.example are refreshed daily by the Update COPG-VD.json workflow, straight from the newest Google factory image.

Keeping the fingerprint fresh

fingerprint-update.sh pulls that file and updates your config, from the WebUI (Check Update / Update Now) or by itself once per boot (Auto-update JSON on boot, on by default).

• Both /data/adb/COPG-VD.json and /data/adb/modules/COPG-VD/COPG-VD.json are updated when both exist, and the previous content is kept as .bak.
• Only the build fields are rewritten (fingerprint, ID, incremental, timestamp, security patch, SDK, UUID, host, user). Everything else you customized is preserved: extra keys, scope_mode, BOOTLOADER/BOARD/HARDWARE, other objects, key order and formatting.
• It never goes backwards: an upstream build older than the one installed is refused. This is routine (the repo can sit behind a config you updated by hand) and it is also the guard that matters most on Android, where the only downloader available is busybox wget, which cannot validate TLS certificates - every value is validated before use for the same reason.
• If your profile spoofs another device (different BRAND/DEVICE/MANUFACTURER/MODEL/PRODUCT), nothing is applied - a Pixel fingerprint on another profile is worse than an old fingerprint.
• At boot it runs in the background and keeps retrying for ~10 minutes, because wifi is usually not up yet when the boot finishes. It never delays the boot.
• resetprop is re-applied right after an update, but android.os.Build is written by the zygisk module when zygote starts: reboot for the new values to reach apps.
• Log at /data/adb/COPG-VD.update.log.

Android version - and why it is not spoofed

ANDROID_VERSION, SDK_INT, SDK_FULL and CODENAME describe your ROM, not the device being spoofed. Telling apps the SDK is newer than the framework really is makes them call APIs that do not exist: Google's apps crash, the phone reboots, and it starts over. The boot itself completes, so it is a softloop and nothing shows up in the boot logs.

• They are not in the shipped config and the updater never writes them.
• Spoof Android version in the WebUI decides whether they are applied at all:
  • Never (default) - the ROM's own version is used.
  • Up to this ROM - only what does not exceed it, which in practice means lowering the SDK.
  • Force - exactly what the config says. This is what causes the softloop.
• The real version is read from /system/build.prop, never from getprop - that is the very thing this module falsifies.

Analyze

Analyze in the WebUI (or fingerprint-update.sh analyze) audits the config as it stands: version against the ROM, whether the file still parses at all (a broken one makes the module spoof nothing, and only logcat says so), whether the fingerprint agrees with the fields around it, keys the module does not read, dates, and whether the props already carry what the config asks for.

WebUI

The WebUI is optional - everything can be edited in the JSON config directly - but it is the easy way to drive the module. It has five tabs: About, Device (every field, set per state, grouped by category), Spoofing (scope and engines), System (the resetprop groups) and Tools (Analyze, Check Update, Update Now, Backup/Restore and the boot auto-update). It makes no network request; everything it needs ships inside the module.
If you are a Magisk user, use KsuWebUI by KOW (https://github.com/KOWX712/KsuWebUIStandalone/releases).

Settings in the config

COPG-VD.json carries its settings next to the profile, so your choices travel with a backup and can be edited by hand: scope_mode, the engine switches, the resetprop groups, global_fields, and a COPG-VD-Settings object (resetprop, autoupdate, spoof_manufacturer, spoof_version). The WebUI writes both the config and the flag files the boot scripts read. "spoof_version": "force" is refused from the file and downgraded: restoring an old backup must not re-arm it behind your back.

Contacts

• https://vd171.ru
• https://vd.priv8.ru
• Telegram: @VD_Priv8 https://t.me/VD_Priv8
• Discord: @VD.Priv8 https://discord.com/users/1296831918989639721
• E-mail: vd.priv8@pm.me
• XDA-Developers: @VD171 https://xdaforums.com/m/vd171.4699873/
• GitHub: @VD171 https://github.com/VD171

---

Tags: Zygisk KernelSU APatch Magisk device-spoofing fingerprint PlayIntegrity Pixel build.prop resetprop root Android COPG COPG-VD