Android 14 - /e/OS 2.7 GSI - Release- unofficial

Null · January 8, 2025, 10:58pm

Overview

Firstly I’d like to thank you to Phh and AndyYan, for their work on TrebleDroid and Lineage21 GSI.

I’d like to say thanks to @Xxpsilon for providing feedback and testing my builds.

Special thanks to everyone at Murena for building /e/OS!

Information

This is a custom /e/OS build that comes rooted, it is a GSI and should boot on almost any Treble A/B Device.

Download link

Raw system.img (Size: 3.08GB)
This is a unzipped system image, it is identical to the compressed system image

Compressed system.img (Size: 1.27GB)
For those who are getting a long download time for the unzipped file.

You only need to download one, the Raw system image is only made available for those who do not want to unzip a file, but both links are of the same system.img.

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services phone

Xxpsilon · January 9, 2025, 8:48am

Test N°10

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

Initial basis

A. full working ~ iode-5.7-20241117-arm64_ab_official (with build-in microG) by @iode.tech
B. OTA-Update ~ iode-5.8-20241214-arm64_ab_release.img by @iode.tech

C. full working ~ lineage-21.0-20241118-UNOFFICIAL-arm64_bvN.img by @AndyYan

D. /e/ does not boot ~ eos-u-2.7-rc1-root-20250108-UNOFFICIAL-arm64_bvN.img by @Null
System only starts up to the rephone-logo, but not into the e-system. No e-logo; adb logcat does not start. Bootloop.

fastboot flash system

fastboot flash system eos-u-2.7-rc1-root-20250108-UNOFFICIAL-arm64_bvN.img
Invalid sparse file format at header magic
Resizing ‘system_a’ OKAY [ 0.006s]
Sending sparse ‘system_a’ 1/12 (262116 KB) OKAY [ 12.066s]
Writing ‘system_a’ OKAY [ 8.706s]
Sending sparse ‘system_a’ 2/12 (261889 KB) OKAY [ 11.873s]
Writing ‘system_a’ OKAY [ 3.598s]
Sending sparse ‘system_a’ 3/12 (260874 KB) OKAY [ 12.024s]
Writing ‘system_a’ OKAY [ 3.611s]
Sending sparse ‘system_a’ 4/12 (262096 KB) OKAY [ 11.837s]
Writing ‘system_a’ OKAY [ 3.685s]
Sending sparse ‘system_a’ 5/12 (261900 KB) OKAY [ 11.910s]
Writing ‘system_a’ OKAY [ 3.579s]
Sending sparse ‘system_a’ 6/12 (261920 KB) OKAY [ 11.998s]
Writing ‘system_a’ OKAY [ 3.800s]
Sending sparse ‘system_a’ 7/12 (262008 KB) OKAY [ 11.916s]
Writing ‘system_a’ OKAY [ 3.838s]
Sending sparse ‘system_a’ 8/12 (262064 KB) OKAY [ 11.870s]
Writing ‘system_a’ OKAY [ 3.831s]
Sending sparse ‘system_a’ 9/12 (262032 KB) OKAY [ 11.893s]
Writing ‘system_a’ OKAY [ 3.704s]
Sending sparse ‘system_a’ 10/12 (262068 KB) OKAY [ 11.932s]
Writing ‘system_a’ OKAY [ 3.781s]
Sending sparse ‘system_a’ 11/12 (260582 KB) OKAY [ 12.013s]
Writing ‘system_a’ OKAY [ 3.814s]
Sending sparse ‘system_a’ 12/12 (58904 KB) OKAY [ 2.699s]
Writing ‘system_a’ OKAY [ 1.935s]
Finished. Total time: 191.710s

E:\adb>fastboot -w
Erasing ‘userdata’ OKAY [ 1.272s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing ‘metadata’ OKAY [ 0.008s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.319s

E:\adb>adb logcat > logcat.txt
– waiting for device –

Update

It’s a rephone®

fastboot getvar product
product: k69v1_64_k419
Finished. Total time: 0.003s

Gigaset and rephone® do not officially provide a stock ROM for public download. It is only possible to dump the files directly from the device.

Null · January 9, 2025, 8:54am

In fastboot mode run:

fastboot getvar product

What is the output from this? Is it a Gigaset k69v1_64 or a Rephone k69v1_64_k419?

If possible, can I get the stock ROM of this device? I may need to add Hardware overlays for it for compatibility

Null · January 9, 2025, 9:52am

If you can dump the stock ROM, I can generate a build for this device.

/e/OS has a lot going on, it is a little different than Lineage21 or Iode so it will not be as compatible unless I do a lot more work on it

Xxpsilon · January 9, 2025, 9:55am

Test N°11

Nothing Phone (1) A063 spacewar
SoC: Qualcomm SM7325-AE Snapdragon 778G+ 5G
NothingOS 2.6 (A14) Security: Nov. 2024
No custom recovery, no LineaageOS; no /e/OS

eos-u-2.7-rc1-root-20250108 GSI by @Null
The system boots up, first showing the Nothing logo, then the animated e-logo with the slogan my data is MY data. Then the screen goes black in a flash.
adb logcat does not respond

Null · January 9, 2025, 9:57am

Check the text file it outputs from adb logcat > text.txt

It will seem to not respond in terminal but it is writing that text file

Xxpsilon · January 9, 2025, 9:59am

I’ve tried three times, but I get no output from adb logcat - none!

Null · January 9, 2025, 10:00am

I will build a flashable image specifically for that device, I have access to the stock ROM for it so…

Xxpsilon · January 9, 2025, 10:05am

It’s curious: In Test N°6 with system-e-2.7_0.3-u-20240107 your e-GSI system was running.

Null · January 9, 2025, 10:06am

Did you issue fastboot -w after flashing it?

Xxpsilon · January 9, 2025, 10:07am

Always! Every time! All the time!

It would be of great benefit to us all if other people would also test the @Null GSI!

Null · January 9, 2025, 10:10am

Are you using the raw system.img or the one that was compressed?

I used ultra compression, which may have corrupted the system.img

Xxpsilon · January 9, 2025, 10:14am

I’ve tested both image variants. The last two times only the raw system.img

Side note: I was able to download the compressed system.img in 2:14 minutes today. With raw system-img the download took 25:02 minutes.

Null · January 9, 2025, 10:17am

Here’s the ultimate question, did the version that booted before have Root?

It may not be able to be rooted on that device, for some reason.

I did two things different in this latest revision, one of the two changes is what is causing this breakage on your device

Xxpsilon · January 9, 2025, 10:21am

None of my test devices were or are rooted.
I only root in exceptional cases, i.e. very rarely.

Null · January 9, 2025, 10:22am

Alright, the next build I push will revert the root commit and we will see if it boots in that case; I think it should

Xxpsilon · January 9, 2025, 10:26am

It would be of great benefit to us all if other people would also test the @Null GSI!

sethdot · January 9, 2025, 10:27am

Thank you for building GSI.

I also failed to boot into it, I tried only on Samsung A21s so far.

All other GSI images (Lineage, unofficial e/os/ GSI Android 13 from the thread below) boot fine so I think there is a problem in this build. I will test more and on other devices.

Null · January 10, 2025, 12:43am

Release Candidate 2 - Download link

I have revoked root and changed device configs somewhat!

This boots as a GSI on my Pixel and everything functions

Xxpsilon · January 10, 2025, 1:52am

Test N°12

Nothing Phone (1) A063 spacewar
SoC: Qualcomm SM7325-AE Snapdragon 778G+ 5G
NothingOS 2.6 (A14) Security: Nov. 2024
No custom recovery, no LineaageOS; no /e/OS

eos-u-2.7-rc2-20250109-gsi_arm64_vN by @Null
Android security update 1 December 2024; microG Services v0.3.6.244735-10
Device name: /e/OS GSI on ARM64

/e/OS-U GSI boots and can be set up. Very good job @Null

e Browser 131.0.6778.140 runs smoothly

App Lounge v2.12.2 foundation.e.apps finds the app you are looking for, offers to install it, but does not install with the message CANCEL