Hi,
is the last build working with /e/ online services?
I have 2 S5 mini (one stock and 1 on lineage) , would love to test your build - thx for your work 
Installed it on 2 devices, installation worked like charm. Will take the time to do some testing next week.
Thx for your work
Hi Guys,
I’m quite a noob and I must admit that I’m a bit lost in the process to install /e/ on the Galaxy S5 mini I have.
cellulosam explained in (very) short how to do the install through SD Card, which seems to be the easiest way (regarding the number of steps to follow). Yes, but:
- Which three files is (s)he talking about? I only see 3 zip files on the cloud link (well, actually, there are 6 files but I guess these are two /e/ OS versions. not sure yet). Two of them look like encryption certificates (.md5sum and .sha256sum), so I guess it’s not the files cellulosam is talking about. When I unzip the main file, there are way more than 3 files, there are folders also. From Chimpthepimp answer, I understand that only the main file is useful. Should I un-zip it on the SD Card ?
- What is TWRP? Is it something to install on the phone or on the computer I’m using to install the OS on the phone?
- What does “continue with flashing” mean? It would help me a lot to have more details, step by step, on how to proceed exactly to flash the new OS from SD Card.
Then alibaba managed to do the install thanks to the /e/ documentation for S5. Yet, the whole guide seems to be written for Windows users. I’m running on Ubuntu, where can I find the equivalent?
I also have a thousand questions about this guide, because I’d like to really understand what I’m doing instead of executing the steps blindly but for now, I hope the SD Card method can work in my case, because it looks much easier.
@piero If you are french as your flag seems to indicate, and if you have time and/or live in Lyon, I’d be really happy to connect with you for this ! 
1 Like
I rebuilt on the v1-pie branch for the s5mini, it’s last version tag was e-0.23. I gathered the Spookcity manifests (same as ops) before the s5mini left my hands, but only found the time to build after the device moved on. Someone up to give it a go - @piero?
A handful of device patches didn’t apply and I lazily skipped. There’s also a binary patcher that I was unsure which model I should pick for (so I skipped it too).
/e/s v1-pie branch (and lineages-16.0 ends) with r46, while google went up to r61. The still maintained pie ASB patches aren’t in there either. Anyway, if it works I’ll put in more time - and maybe the s5mini finds it way back to me too.
-
https://transfer.sh/y1pBhY4KK1/e-0.23-p-20230720-UNOFFICIAL-kminilte.zip
(available until end of july)
md5sum e-0.23-p-20230720-UNOFFICIAL-kminilte.zip
a5898e2e6e1d928bae875e8e1125f5ae
That said, it’s a pity for EoL branches that /e/ isn’t into system package distribution (via fdroid indexes) - yet. Hampers the usefulness of doing an old build
Sorry,
I cannot test because the device (with a broken glass) that i had loaned to a friend came back with a non fonctional screen.
1 Like
Oh, I totally missed that part… has it bin saved somewhere else?
I have +10 working devices for testing
<download removed>
as said, device not in my hands anymore to test so manage expectations - also it’s v0.23. I’ll put in more time if it boots and is somehow usable.
Thanks for uploading again.
Unfortunately it did not boot, it just loops into the Samsung boot screen.
Installed it clean twice, and once over the 0.9… I installed just to see, it this would boot. Phone was still on stock Samsung S5mini.
Last working version I ever downloaded and ran on S5minis:
Logs I can not upload, but I have demsg and recovery
sorry for that. If you have pastebin links with logs I’ll read them, but I don’t think I’d make progress without the device in my hands again.
dmesg: https://pastebin.mozilla.org/NOcjYDED
recovery: https://pastebin.mozilla.org/6bbxqd3J
[edit] hade to reupload logs, as they got truncated somewhere
BTW: if it does not cost an arm and e leg, I’m happy to send you a device!
From dmesg:
------------[ cut here ]------------
WARNING: at …/…/…/…/…/…/lineageos-cm-14.1/kernel/samsung/kminilte/fs/sysfs/dir.c:508 sysfs_add_one+0xa8/0xd8()
sysfs: cannot create duplicate filename ‘/bus/sec_os_ctrl’
Backtrace:
[] (dump_backtrace+0x0/0x128) from [] (dump_stack+0x18/0x1c)
r6:c08f6b64 r5:000001fc r4:c0184dac r3:60000013
[] (dump_stack+0x0/0x1c) from [] (warn_slowpath_fmt+0x64/0x80)
[] (warn_slowpath_fmt+0x0/0x80) from [] (sysfs_add_one+0xa8/0xd8)
r3:eeece000 r2:c08f6bd4
r6:eeaab100 r5:eeece000 r4:ffffffef
[] (sysfs_add_one+0x0/0xd8) from [] (create_dir+0x68/0xd4)
r7:ef8833c0 r6:00000000 r5:ef83de78 r4:eeaab100
[] (create_dir+0x0/0xd4) from [] (sysfs_create_dir+0x9c/0xf8)
r8:c0cd17d0 r7:ef883310 r6:ef8833c0 r5:efb91810 r4:00000000
[] (sysfs_create_dir+0x0/0xf8) from [] (kobject_add_internal+0xa4/0x278)
r6:00000000 r5:efb91810 r4:efb91810
[] (kobject_add_internal+0x0/0x278) from [] (kset_register+0x24/0x50)
r8:c0cd17d0 r7:c0b9421c r6:00000000 r5:efb91810 r4:efb91800
[] (kset_register+0x0/0x50) from [] (__bus_register+0xc8/0x2d0)
r5:c0ba5dc4 r4:efb91800
[] (__bus_register+0x0/0x2d0) from [] (subsys_system_register+0x24/0xf8)
r9:c0bf3940 r8:c09ae314 r7:c0ba5e04 r6:c0ba5dc4 r5:c09dcf14
r4:c09ec760
[] (subsys_system_register+0x0/0xf8) from [] (sec_os_ctrl_init+0x1c/0x24)
r7:c09abc9c r6:00000007 r5:c09dcf14 r4:c09ec760
[] (sec_os_ctrl_init+0x0/0x24) from [] (do_one_initcall+0xb8/0x1c0)
[] (do_one_initcall+0x0/0x1c0) from [] (kernel_init+0x16c/0x24c)
[] (kernel_init+0x0/0x24c) from [] (do_exit+0x0/0x84c)
r7:00000013
—[ end trace 419dc916a226cc58 ]—
------------[ cut here ]------------
WARNING: at …/…/…/…/…/…/lineageos-cm-14.1/kernel/samsung/kminilte/lib/kobject.c:198 kobject_add_internal+0x244/0x278()
kobject_add_internal failed for sec_os_ctrl with -EEXIST, don’t try to register things with the same name in the same directory.
Backtrace:
[] (dump_backtrace+0x0/0x128) from [] (dump_stack+0x18/0x1c)
r6:c090de84 r5:000000c6 r4:c02ad7fc r3:60000013
[] (dump_stack+0x0/0x1c) from [] (warn_slowpath_fmt+0x64/0x80)
[] (warn_slowpath_fmt+0x0/0x80) from [] (kobject_add_internal+0x244/0x278)
r3:c07d8a6c r2:c090df64
r6:ffffffef r5:efb91810 r4:efb91810
[] (kobject_add_internal+0x0/0x278) from [] (kset_register+0x24/0x50)
r8:c0cd17d0 r7:c0b9421c r6:00000000 r5:efb91810 r4:efb91800
[] (kset_register+0x0/0x50) from [] (__bus_register+0xc8/0x2d0)
r5:c0ba5dc4 r4:efb91800
[] (__bus_register+0x0/0x2d0) from [] (subsys_system_register+0x24/0xf8)
r9:c0bf3940
fg_get_soc : FG_VBAT = 4162
fg_get_soc : FG_IRQ_CTL_FLAG = 0x1f00
fg_get_soc : FG_VMIN_SMIN_FLAG = 0x0001
fg_get_soc : FG_CRATE_DEVICEID = 0xf901
fg_get_soc : FG_CONFIG = 0x040b
r8:c09ae314 r7:c0ba5e04 r6:c0ba5dc4 r5:c09dcf14
r4:c09ec760
[] (subsys_system_register+0x0/0xf8) from [] (sec_os_ctrl_init+0x1c/0x24)
r7:c09abc9c r6:00000007 r5:c09dcf14 r4:c09ec760
[] (sec_os_ctrl_init+0x0/0x24) from [] (do_one_initcall+0xb8/0x1c0)
[] (do_one_initcall+0x0/0x1c0) from [] (kernel_init+0x16c/0x24c)
[] (kernel_init+0x0/0x24c) from [] (do_exit+0x0/0x84c)
r7:00000013
—[ end trace 419dc916a226cc59 ]—
I guess the -nz suffix means you’re on the other side of the planet to europe? will try to snatch one from ebay. But could take a few weeks I’m sorry. Was hit or miss posting the build
kobject_add_internal failed for sec_os_ctrl with -EEXIST, don’t try to register things with the same name in the same directory.
...
WARNING: at …/…/…/…/…/…/lineageos-cm-14.1/kernel/samsung/kminilte/fs/sysfs/dir.c:508 sysfs_add_one+0xa8/0xd8()
sysfs: cannot create duplicate filename ‘/bus/sec_os_ctrl’
looking at what add_one is doing maybe I’d check this commit for Makefile path changes inside gud-exynos3470
I made a recent Pie build if anyone wants to test:
e-0.23-p-20240116-UNOFFICIAL-kminilte.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-0.23-p-20240116-UNOFFICIAL-kminilte.zip/download
2 Likes
No luck, hangs at Samsung boot logo in a very slow boot loop.
Did two clean install, with wipe & format data.
From SD with these two TWRP:
twrp-3.2.3-0-kminilte.img.tar
twrp-3.6.0_9-0-kminilte.img.tar
Piero wrote this some time ago… might worth a try:
It Boot ! … at the second attempt …
it is common on that old devices that custom build don’t boot completely at the first attempt but the install process is finishing its config (i let 15 or 20min with the “e” bouncing) and then it allow the device to boot at the second attempt …
I have had this too with other /e ROMs
But with this ROM it’s only getting to this:
@piero Do you have a S5mini you can test with?
i don’t have s5mini anymore…
This topic was automatically closed after 60 days. New replies are no longer allowed.