Qualcomm SM4250 Snapdragon 460
Oxygen OS 11.0.15.BE83BA (A11)
Stock Recovery
GSI e-2.8-a14-20250310-UNOFFICIAL-arm64_bvS by @Colors - boot & working
Cross-Check
GSI (A14) iodéOS 5.10 20250219 - working
GSI (A15) VoltageOS-microg-arm64-ab-4.2_20250309-UNOFFICIAL - working
Great! I suspect superuser is for adb function. I haven’t tried to see how useful it is.
Do you’ve energy & time to update to Android security update February / March 2025:
e-2.8-a14-20250310-UNOFFICIAL-arm64_bvS
e-2.8-a14-20250227-UNOFFICIAL-arm64_bvN
how I can donate you a Red Bull Energy Drink / Sugarfree / Zero / White Edition / Blue Edition / Purple Edition / Spring Edition 
or a Lavazza Espresso Italiano Cremoso 
No Red Bull please! Aber ich würde gerne einen Kaffee Lavazza Espresso Italiano Cremoso trinken. I’ll do my best aber es wird eine Weile dauern.
Are you sure it is not Version 2.9-a14?
Whether U-2.8 or U-2.9 is not decisive. My aim is to achieve the highest possible Android security level (02/03-2025).
v2.9-beta.2-a14 with security_patch=2025-02-01
Gigaset GS4 (GS4)
SoC: Mediatek Helio P70 MT6771T
Stock Android 11.0 V23 (A11) Kernel: 4.14.186
No custom recovery
GSI e-2.9-a14-20250315-UNOFFICIAL-arm64_bvN by @Colors
boots & works at first glance except for the App Lounge (which is not the cause of the GSI)
Thank you! It turns out that the power consumption is also slightly lower… but it still needs to be checked. Okay, the superuser version I’ll compile tomorrow. Until then a starry night to all.
Xiaomi Mi 9 cepheus
SoC: Qualcomm SM8150 Snapdragon 855
Stock Android 11.0 - V12.5.2.0.RFAEUXM
Android Recovery
GSI e-2.9-a14-20250316-UNOFFICIAL-arm64_bvS 
signed keys by @Colors
Boots & works at first glance
App Lounge 2.13.2
sometimes works more, sometimes less, so a bit bumpy, but better than nothing. Let’s hope it gets better again with App Lounge v2.13.5
v2.9-a14 with security_patch=2025-03-01
https://sourceforge.net/projects/e-os/files/GSI/2.9-a14-20250321-CUSTOM-arm64_bfN.img.xz/download
https://sourceforge.net/projects/e-os/files/GSI/2.9-a14-20250321-CUSTOM-arm64_bfS.img.xz/download
I have included FDroid as a second option to App Lounge.
Xiaomi Mi 9 cepheus
SoC: Qualcomm SM8150 Snapdragon 855
Stock Android 11.0 - V12.5.2.0.RFAEUXM
TWRP Recovery
GSI e-2.9-beta-a14-20250315-UNOFFICIAL-arm64_bvN signed keys by @Colors
App Lounge 2.13.2 works partially
Android Security FEB 2025
GSI 2.9-rc-a14-20250321 
CUSTOM arm64_bfN signed keys by @Colors
App Lounge 2.13.5 works partially
Android Security MAR 2025
It’s your great work @Colors, it’s your CUSTOM GSI 
Thanks for testing. Initially my intention was not to make a custom version. However, the intervention is minimal. But the App Lounge problem persists and I think an alternative is needed. Another problem, I think, is the Gms which apparently consumes a lot of energy. I do not know, maybe it would be an option also a real vanilla version? It must be studied…
To my ears CUSTOM sounds more sympathetic, my eyes read CUSTOM with positive associations. /e/OS GSI VANILLA would also have the advantage that the user can choose whether he wants to use MicroG services or not.
@Colors I’ve had good experiences with other vanilla GSI + CustomROM with MinMicroG-Minimal-UPDATELY-20241211010238 ( 11 Dec 2024 ) = GMS 0.3.5.240913
Thanks for the tutorial, I’m interested in trying it.
You must have a pretty powerful setup? I remember when I built some e/os/ roms, it took like 7 hours, but that was on laptop with only 4 cpu cores and 16GB of RAM.
I suspect GSI images are even more difficult to build?
It’s not difficult. In reality I only have a mini pc with Intel i5 and 64 GB of memory. In fact it would also go with 32 GB if you make some changes in linux. The compilation takes about 90 minutes the longest. The Important thing is to have a stable linux, fast ssd. Possibly for maximum performance use 2 SSDs, on one you have linux system and on the other you make compilation and ccache.
when you talk about 7 hours, i think you include the initial repo sync
i have a comparable poor 30€ computer, i5(2500) 4-core 3,300 Ghz, with 16 Gb RAM DDR3 1333 Mhz and relatively slow SATA 3 Gbit/s BUS.
repo sync already done, for legacy R builds, the first compilation took me about 4h30, then the following compilation for a device of the same SOC family took me about 2h00
Yes, after the initial full build, only repo sync update for the new version was much faster for me, too.
But I’ve never tried GSI build, I thought it was much more complex and resource heavy than rom building.
You can add 15-20% extra resources and time. Obviously a little more storage space consumed on the SSD.
Hi, i would like to use Kitsune root instead of the root which came with the rooted image, what would be the correct way to achieve it?
I’ve tried patching the original stock rom boot.img and flashing it but when i open Kitsune it says my root is older or something.
Amazing work BTW!!
https://sourceforge.net/projects/e-os/files/GSI/2.9-a14-20250403-CUSTOM-gsi_arm64.img.xz/download
Unfortunately the high battery consumption remains.
