I have been using lineage on my phone for 9 months now. RCS works fine for me.
2 Likes
When I flip the Offline+ switch my cell signal indicator shows a ‘!’ symbol. Wifi and bluetooth still work fine. If I am listening to an audiobook or music the sound is affected for about 20 seconds. This happened to me when I used the stock OS as well.
2 Likes
Hey everyone,
I’m looking for some help. I’m really happy with the mudita as a device to fight my tech addiction. The friction of the slower processor, limited refresh e-ink, etc are working well. Like others I have some mandatory apps that require Android 13 or higher for corporate security approval and would ideally like full gapps for things like Google Voice which has been a primary contact number for me for nearly two decades. I wouldalso like to have functional RCS if possible.
I am trying to install LineageOS 20 GSI on a Mudita Kompakt by following the instructions in the original post. I have an unlocked Kompakt with a working bootloader and can reliably restore it to a clean MuditaOS K 1.1.1 installation, but every GSI attempt returns to Fastboot instead of booting Android. I’ve been attacking this directly with hands on keys and also with multiple AI coding assistants trying to stab at possible solutions.
For reference I am in North America, so I assume if there’s a different regional version that’s what the company sent when I ordered.
Stock 1.1.1 verification
I restored the device using only the official Proton Drive 1.1.1 files:
• 1.1.1_partitions.zip
• 1.1.1_ota.zip
• Stock boot.bin
• Stock dtbo.bin
• Stock vendor_boot.bin
• Stock vbmeta.bin
I flashed the stock boot-related partitions to both slots, sideloaded 1.1.1_ota.zip , performed a factory reset, and confirmed that the phone booted normally to the MuditaOS K 1.1.1 setup screen. I also repeated this restoration after the GSI tests, and the phone again returned successfully to the 1.1.1 setup screen.
The bootloader reports:
product: Kompakt
unlocked: yes
secure: no
slot-count: 2
GSI images tested
I tested the following images independently, wiping data between attempts:
lineage-20.0-20251021-UNOFFICIAL-arm64_bgN-signed.img
lineage-20.0-20251021-UNOFFICIAL-arm64_bvN.img
lineage-19.1-20250606-UNOFFICIAL-arm64_bgN-signed.img
lineage-20.0-20251021-UNOFFICIAL-arm64_bvS.img
The last image was the exact arm64_bvS image mentioned by another user in post 28 as working:
lineage-20.0-20251021-UNOFFICIAL-arm64_bvS.img.gz
The images were flashed successfully to the logical system_a partition from Fastbootd. Each attempt ended with the device returning to the regular Fastboot screen rather than booting LineageOS.
The Android 12 Lineage 19.1 test also failed, so the problem does not appear to be limited to Android 13 compatibility.
AVB and vbmeta testing
The original instructions use an empty vbmeta image, but the device showed AVB-related behavior not described in the original post. One test produced a dm-verity corruption error before returning to Fastboot.
I tested:
fastboot flash vbmeta vbmeta.img
I also flashed the empty vbmeta image explicitly to both slots:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
I additionally tested empty vbmeta_system and vbmeta_vendor images.
Because the stock 1.1.1 boot ramdisk contains this first-stage fstab restriction:
avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey
I created a correctly rebuilt 1.1.1 boot image with that GSI key whitelist removed from the first-stage and recovery fstab. The image retained the complete ramdisk and valid boot image footer. Flashing that patched boot image also failed and returned to Fastboot.
I then restored the completely stock 1.1.1 boot, dtbo, and vendor_boot images before further tests.
Reproducing the later forum method
After finding the later post reporting success with arm64_bvS , I also reproduced the newer procedure described by another successful user:
fastboot --disable-verity --disable-verification flash vbmeta --slot=all vbmeta.img
fastboot reboot fastboot
fastboot flash system lineage-20.0-20251021-UNOFFICIAL-arm64_bvS.img
For this attempt I deliberately did not run fastboot erase system .
I entered recovery and performed the factory reset.
After selecting Reboot system now, the phone again returned to Fastboot.
Current state
The phone is currently restored and booting clean MuditaOS K 1.1.1. I can repeat the stock restoration reliably. No Lineage image has booted successfully.
At this point I am wondering whether:
• This is related to global vs NA hardware revisions.
• A required partition other than boot , dtbo , vendor_boot , vbmeta , and system differs between working and non-working devices.
• A modem, para , metadata, boot-control, or other partition must be restored or modified.
• The working users had a different original firmware version or partition layout.
Has anyone with a Kompakt that initially failed with an infinite Fastboot loop identified the missing step? If someone has a working Lineage installation, a comparison of the relevant partition layout, original firmware version, hardware/region variant, or exact complete flashing sequence would be extremely helpful.
2 Likes