You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! There is a critical issue in the latest GApps EROFS build (LineageOS-23.2-20260524-GAPPS-EROFS-GSI).
The system goes into a permanent black screen/crash-loop right after selecting the language and clicking "Next". adbd drops immediately with an error: closed / failed to run abb_exec message, making it impossible to pass or disable via adb shell on stock/live boot.
Root cause:
The image has a severe conflict of multiple provisioning and setup applications baked right into the read-only partition. A find query from recovery reveals that the following apps are present simultaneously and fighting for permissions:
Associated overlays: GmsSetupWizardOverlay.apk and LineageSetupWizard__lineage_arm64_bgNE__auto_generated_rro_product.apk
Why it's a huge problem:
Since the build is packed into EROFS, users cannot even manually mount the system partition as read-write (rw) in OrangeFox/TWRP to rm -rf the conflicting packages. Performing a full Format Data doesn't resolve the issue either, as the broken/conflicting setup configuration is locked inside the immutable EROFS system block.
Please fix the privapp-permissions manifest, resolve the SetupWizard redundancy, or consider dropped EROFS for testing GSI builds entirely.
Right now, the EROFS GApps build is completely unusable out of the box.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi! There is a critical issue in the latest GApps EROFS build (
LineageOS-23.2-20260524-GAPPS-EROFS-GSI).The system goes into a permanent black screen/crash-loop right after selecting the language and clicking "Next".
adbddrops immediately with anerror: closed/failed to run abb_execmessage, making it impossible to pass or disable viaadb shellon stock/live boot.Root cause:
The image has a severe conflict of multiple provisioning and setup applications baked right into the read-only partition. A
findquery from recovery reveals that the following apps are present simultaneously and fighting for permissions:/system_root/system/system_ext/priv-app/SetupWizard/system_root/system/system_ext/priv-app/LineageSetupWizard/system_root/system/priv-app/ManagedProvisioningGmsSetupWizardOverlay.apkandLineageSetupWizard__lineage_arm64_bgNE__auto_generated_rro_product.apkWhy it's a huge problem:
Since the build is packed into EROFS, users cannot even manually mount the system partition as read-write (
rw) in OrangeFox/TWRP torm -rfthe conflicting packages. Performing a fullFormat Datadoesn't resolve the issue either, as the broken/conflicting setup configuration is locked inside the immutable EROFS system block.Please fix the privapp-permissions manifest, resolve the SetupWizard redundancy, or consider dropped EROFS for testing GSI builds entirely.
Right now, the EROFS GApps build is completely unusable out of the box.
All reactions