Unlock CN GMS by KOWX712 removes cn.google.services restriction entries from supported Chinese-ROM configuration files through systemless mounts, with updated handling for modern root managers.
Systemless GMS Restriction Removal
A maintained fork of fei-ke's module with broader installation and mount handling for current root frameworks.
XML Configuration
Finds supported permissions and feature files, then prepares copies without the regional GMS restriction entry.
Multiple Partitions
Handles relevant locations under system, vendor, product, ODM, and supported vendor-specific partitions.
Modern Root Support
Uses newer Magisk file-erasure support and falls back to Mountify-style binding where automatic mounting is unavailable.
What the Module Changes
Some China-market firmware includes XML declarations that identify cn.google.services as unavailable. Android reads those declarations during boot and can keep Google features such as Location History or Maps Timeline hidden even when Google Mobile Services has been installed.
The module does not install Google applications. It presents modified copies of the discovered configuration files through the root framework, leaving the read-only partitions unchanged and making removal possible through the module manager.
How the KOWX712 Fork Differs
Version 3.8-M retains the original restriction-removal logic while adapting installation to Magisk, KernelSU, and APatch environments. On sufficiently new Magisk builds, it can use the root framework's file-erasure feature. Where the manager cannot automatically mount the required replacement, the fork uses a compatible bind-mount fallback.
This distinction matters on dynamic-partition ROMs and vendor variants that store the restriction file outside the original system path. The installer reports the paths it finds; review that output to confirm that the device actually contains a supported entry.
Installation Expectations
- Confirm that Google Mobile Services is already installed and functional enough to add an account.
- Install the module through a supported root manager and inspect the console for detected configuration paths.
- Reboot so Android reloads permission and feature declarations, then check the affected Google feature.
- If Location History remains unavailable, the upstream project notes that a separate LocationReportEnabler-style solution may still be necessary.