[LEGACY_BUILDS] collection for /e/ OS supported "legacy devices"

/e/OS Devices UnOfficial Builds
26

Finaly!? Thanks piero. I’m waiting for that. You’re the best.

27

Hi piero, i just tested your build and it works great. But one thing i notice that rootbeer is not pass and it detect a root device. i think ih8sn not integrated with your build, on /e/ device wiki it showed that rootbeer is pass on my device. I remember when build still dev on 2022, /e/os injected ih8sn on dev build. I can use my whatsapp without custom rom pop up warning, or maybe i was wrong?

28

try this (English version) :

29

I resolved it with flashing with ih8sn GitHub - luk1337/ih8sn but i swap a conf file with etc/ih8sn/ih8sn.conf · staging · os / public / lineage / vendor_extra · GitLab
Config itself more universal with all device.

1 Like
30

OK, now I can fully confirm my suspicion about your builds.
Today I installed i on my old S4:

e-2.3-r-20250121-LEGACY-jfvelte.zip

And the same problem is present as in your LEGACY build for S5 ‘klte’.

First I wiped out everything System partion and Factory reset.
Then installed from your recovery (2.3 LEGACY from your download) as it should be installed, then did:

adb sideload e-2.3-r-20250121-LEGACY-jfvelte.zip
The recovery recognized keys after verifying your ROM, the phone started normally, and after first initial configuration i clicked on the browser and it crashed:

“Your device couldn’t open Browser. To fix the issue, download the latest Browser update from your app store”

So indeed you have some build environment problems, because two phones is unlikely to get the same error.
Summarizing, the same error when opening the Browser is present in klte and jfvelte.

P.S.
also, checked if the system is fully wiped out, and it was, after restart from recovery it went straight to Download mode, without touching any buttons.

It could also mean that Captive Portal do not work aswell, but I don’t know how to test it.

31

Can anybody post link to the OFFICIAL latest /e/OS for Galaxy S4 “jfvelte” Value edition (GT-I9515)? That was in the download section on the Wiki page. Thanks!

32

There is already e-1.9-r-20230312268580-dev-jfvelte.zip available (thanks to @make-nz)

33

Thanks, but it’s not the newest one. The newest was e-2.2

I have already installed like one year ago on my phone. Is there any way to extract it from my current installed ROM?

If it’s possible, I can upload it then to some hosting site for others to enjoy.

34

***Update:
I’ve tested your ROM (LEGACY 2.2 on S4 ‘jfvelte’) where Browser was not working, and installed from USB OTG cable Aurora Store, and Brave browser was working good, so maybe only Browser doesn’t work, and I’m suspecting that with that Portal Login will not work, but I didn’t test it.

1 Like
35

i have to rebuild for some devices that i builded too fast (“for the series”) last month.

Edit : it’s done

36

I was able to install @piero’s e/OS/ 2.3 20250121 LEGACY build on my Xiaomi Redmi Note 6 Pro “twolip”. However the browser app keeps crashing, both the default one and others installed via F-Droid.

When you have time, could you please rebuild LEGACY e/OS/ for twolip as well, to avoid this quite nasty browser issue?

Thank you very much! :slight_smile:

2 Likes
37

Thank you! I have “hlte” (Note 3) and “jfvelte” and “jflte”. I can test all of them.
***Sidenote:

Does anybody know if there was official support for “trlte”? Because I couldn’t find it…

38

Today I installed e/OS/ 2.3 20250223 build on my twolip and I’m happy to report that the browser crash issue has been solved.

I would love to have a way to donate money to @piero, who allowed me to keep using an e/OS/ compatible legacy device.

1 Like
39

thanks for repporting.

for this device, there is also [UNOFFICIAL BUILDS] Xiaomi Redmi Note 5 (whyred) / Xiaomi Redmi Note 6 (twolip) for /e/OS-T by @ronnz98.

thank you for the intention, but it is not possible,
you can help /e/ here : Donate - e Foundation - deGoogled unGoogled smartphone operating systems and online services - your data is your data.

40

Confirmed!

Fresh installation after total wipe, for Galaxy S4:
e-2.3-r-20250226-LEGACY-jfltexx.zip

The browser now is working as it should be.

1 Like
41

Now, another problem with another LEGACY ROM:

adb sideload e-2.3-r-20250123-LEGACY-klte.zip
Total xfer: 1.00x

It installed correctly, but the same problem with system browser that cannot be started. As in previous situation.

42

Seeing the date it is one i had forgotten to rebuild. I will do it in the next days.

edit : it’s done !
#### build completed successfully (02:45:42 (hh:mm:ss)) ####
please confirm it works …

1 Like