Yeah it’s a mtk issue it seems, working hard on resolving this!
3 Likes
I uploaded a new version now
1 Like
@Xxpsilon did your test Ron’s new build? 
we’re closing on on getting this to work for devices that won’t boot presently
eos_u_2.7v2_20250110_gsi_arm64_vN
Test N° r4
Gigaset GS4 (GS4
SoC: Mediatek Helio P70 MT6771T
Stock Android 11 (A11) Kernel: 4.14.186
No custom recovery
/e/ does not boot ~ eos_u_2.7v2_20250110_gsi_arm64_vN by @roonz98
Restart only takes place up to the orange Gigaset logo, remains for one minute; no e-logo - then > bootloop.
Cross-check 
works ~ e-2.6.3-t-UNOFFICIAL-gsi_arm64 by @colors
Ok, i have identified the failing MTK component as being from the GPU, this has been patched and there shouldn’t be an issue booting it on MTK devices from here on out.
I’m aware @colors is also doing a port of A14 but I am not sure if they are doing it from source or doing a port of pre-existing firmware the more traditional way.
Nonetheless we’ll continue on with the source-built version of this GSI for bring-up of an eventual A15 version when it drops
‘citius, altius, fortius’ (Pierre de Coubertin) ~ higher, faster, stronger.
But it doesn’t always have to be the latest, highest Android (A15) version, which requires ever higher demands on hardware, firmware and developers.
/e/OS-U GSI (A14) offers fantastic possibilities, but a /e/OS-T GSI (A13) would be a huge asset, especially for many older devices. Apart from @AndyYan, hardly any GSI developers still care about Lineage-19 GSI and Lineage-20 GSI.
The only reason I think it is important to establish a open source A14 version is so it can be used in the bringup for A15 so we can get a GSI of it immediately.
Either way it is inevitable that a fully functioning GSI for A14 will be produced at this point?
@ronnz98 is working on one, I’m working on one and @colors is working on one and everyone is for the most part open-sourcing their work, who does it first doesn’t matter as long as it gets done
@ronnz98 has build one using an updated codebase and his has a great chance of booting on your rephone, but it is tough for both of us to test as we do not have MTK devices. 
As you have experienced so far, I’ve several MTK devices, and - I would like to continue testing your GSI builds.
This was built by Ron and I, it is vastly improved over the previous builds; very interested in your rephone feedback, it should probably boot
Various errors have been resolved, such as the return of the touch gesture bar, which was missing from the Release Candidate builds…
Download runs sluggishly at max. 620 KB/s
Do you see where it says ‘Problems Downloading’?
Try a mirror closer to you if it is intolerable, excited to hear your feedback on this revision and I’m excited to see if it works
saturday influx of visitors !
If it is still no good I’m uploading it to Mega.nz for you now
Don’t chase after the meaning of your life, but devote yourself to something valuable to you with perseverance and love. Everything will turn out well 
2 Likes
Here you go @Xxpsilon!
If this works as intended, we’ll be able to get away with the most abusive stuff possible in regard to pushing /e/OS as a GSI lol!
Three more minutes … … …
1 Like
Test N° rn4
rephone® (6/128 GB like Gigaset GS5 pro)
SoC: MediaTek Helio G85 - k69v1_64_k419
Stock Android 12 (A12) Kernel: 4.19.191
No custom recovery
/e/ does not boot ~ eos_u_2.7_20250111_treble_arm64_bvN by @ronnz98&@Null
System only starts up to the rephone-logo, but not into the e-system. No e-logo > Bootloop.
Cross-check works ~ lineage-21.0-20241118-UNOFFICIAL-arm64_bvN by @AndyYan
Ok, I will have a build from our alternate codebase for you to test by tomorrow, thank you X!
2 Likes
Try this, overlay is broken in this but I just want to see if it boots on MTK devices