Known issues
This document lists the currently identified bugs, limitations, and performance issues within the project. We are actively working on fixes; please check here before reporting a new issue.
Errors
No space left on device
Many devices do not have enough free space on the system partition to flash the ZIP.
Workaround
LOW_FREE_SPACE option before flashing.Enable it with:
adb shell "setprop zip.microg-unofficial-installer.LOW_FREE_SPACE 1"
Then flash the ZIP as usual.
Note
This option is currently only available in nightly builds, you can download the latest nightly from the download section.
microG can be updated to a newer version manually afterwards using F-Droid.
The device is locked!!!
The boot loader is locked!!!
These errors are raised when the installer detects that the device or its boot loader is locked, which would prevent a successful installation.
The detection relies on system properties and works correctly when the device is booted into recovery mode. However, when the device is running the normal system, certain ROMs or Magisk modules may spoof a locked state even on an actually-unlocked device. In that specific case the detection may report a false positive.
Workaround
If you are certain that your device is unlocked and the error is a false
positive caused by ROM or Magisk spoofing, you can bypass the check by
setting BYPASS_LOCK_CHECK=1 when installing via zip-install.sh:
BYPASS_LOCK_CHECK=1 sh ./zip-install.sh ./microg-unofficial-installer-*.zip
Warning
Only use this bypass when you are sure the device is genuinely unlocked. Installing on a truly locked device will fail and may leave the device in an inconsistent state.