Open GApps silently fails to install via Lineage recovery
Expected Behavior
Sideloading the latest Open GApps from Lineage recovery should add Google apps to the active slot.
Current Behavior
The sideload operation completes successfully, but no Google apps are installed.
Here's what happens:
- The Open GApps installer script attempts but fails to mount the system partition to
/system
. - The failure to mount
/system
is ignored by the installer script. - The installer script attempts but fails to install each Google app to
/system
(because/system
is on a read-only mount). - Each failure is ignored by the installer script.
- The script exits with a 0 exit status so Lineage recovery believes that it completed sucessfully.
Open GApps could fix the installer script, but it currently works in TWRP so users reasonably expect it to also work with Lineage recovery.
Possible Solution
Steps to Reproduce
- Flash Lineage recovery to slot b:
- Reboot into the bootloader
- Run
fastboot flash boot_b ./lineage-17.1-20200501-recovery-mata.img
- Run
fastboot set_active b
- Boot into recovery (slot b)
- Install LineageOS on slot a:
- Select "Apply update"
- Select "Apply from ADB"
- Run
adb sideload ./lineage-17.1-20200501-nightly-mata-signed.zip
- Reboot into recovery (slot a)
- Install Open GApps:
- Select "Apply update"
- Select "Apply from ADB"
- Run
adb sideload ./open_gapps-arm64-10.0-pico-20200501.zip
- Select "Factory reset"
/device mata /version lineage-17.1 /date 2020-05-01 /kernel 4.4.220-lineage+ /baseband 2.0.c4-M2.0.10 /mods OpenGApps
I have read the directions.
Edited by Richard Hansen