Test N° n5
rephone® (6/128 GB)
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_20250112 (test.img.zip) by @Null
System only starts up to the rephone logo and stops for about 50 seconds; does not boot into the e-system. No e-logo > Bootloop
Cross-check 
works ~ lineage-21.0-20241118-UNOFFICIAL-arm64_bvN by @AndyYan
I guess we’ll have to wait for colors to bring it up for MTK, I’lls ee if Ronnz98 wants to upload the source to github or push the changes to /e/OS foundation. I think the recent app navbar was broken because the way overlays are handled seems to have changed a bit; it could be my device configs but I doubt it for my own reasons
Ah, the build env was missing mediatek hardware support, resolving now and pushing another build… but I have no way of testing the changes I’m making and I also have to contend with the apparent overlay change in /e/OS, but it is alright
You put a lot of effort into the development, which I really appreciate. I’m still available for tests on various MTKs. What must be surprising is that Ron’s build works on the MediaTek Dimensity 900 5G
Download is running at 300 - 400 KB/s. The .zip file should be saved on my computer in an hour.
I can upload it to Mega for you
Not absolutely necessary. Good things take time. My information on download times is not a criticism, but merely a signal that I’m on the ball.
Here you go!
In 12 minutes the time has come …
I don’t know if we implemented it right, but MTK hardware source should be present in this ROM, this test will tell us a lot about it.
Which rephone® stock firmware A12 files could help you?
I think that if we implement MTK HW right, it should work even without access to the stock firmware.
It’s just tough because Ron nor I have a MTK device, it is taking a while because neither of us can slam out test builds for MTK unlike other architecture
Test N° n6
rephone® 6/128 GB
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_20250112_treble_arm64_bvN by @ronnz98 & @Null
Well-known scenario: System only starts up to the rephone logo and stops for about 50 seconds; does not boot into the e-system. No e-logo > Bootloop
Cross-check works ~ lineage-21.0-20241118-UNOFFICIAL-arm64_bvN by @AndyYan
Argh >:( Wtf! I will reconfigure the device tree
|Wait, did you disable verity?
Yes, via vbmeta … … …
Cross-check
I tested this GSI rom on my A32 and don’t boot, boot into fastboot mode
@Null is ZERO. EOL.