e/OS 0.22 p won't boot though LineageOS 16.0 does

Ok, I will give it a final try, using the “android” repo instead of “releases” (never realised the difference anyway), and clear ccache before (because of the mysterious 64 bit file in the build - I did several 64-bit builts of e/OS with this setup…). If that won’t work I think I’ll give up on the S5 mini… :neutral_face:

Hmm, even after building again with a clean ccache the rom still reboots to bootloader. I am running out of ideas.

@Manoj: I am beginning wondering if anyone lately succeeded in building a pie (or any) version for arm7 at all…?

Anyway, I will stick to the LOS 16 unofficial build for now. At least , now it has the e bootanimation (after testing if the bootanimation would cause the problem), so I at least can pretend it was e :laughing:.
However, especially when using several devices, the e services do have their advantages…

Do you want to inspect the working pie boot for kminilte here

1 Like

Would be interesting to try and build version 0.9, and see if it is booting. I assume now that the error somehow relates to the system.img, I will check the e/OS boot.img with the LOS build…

Edit: Yes, both boot.img are interchangeable with the LOS build, so there must be something wrong with the system.img… (system partition is 2.2 GB though, system.img is 1.5 GB, no error when flashing)

I think those patches were found here: android_device_samsung_smdk3470-common/patch at P · Spookcity/android_device_samsung_smdk3470-common · GitHub … I hope that helps :slight_smile:
All the best and kind regards :slight_smile:


Thanks for the link, much appreciated! I find references to G800F in some comments. I have G800H (qcom). Would the patches be applicable?
Best regards and a happy weekend!

Ah no the ones i used from spookcity are for Samsung Galaxy S5 mini - (G800F/G800M/G800Y) “Kminilte”, only. For the H version you will need different sources…

1 Like

Did you known that ?

And that ? (s3neo)
( Qualcomm MSM8226 Snapdragon 400 / Quad-core Cortex-A7 - 1.6 GHz / Adreno 305 )

Thanks for the hint! I indeed missed the Pie versions for some Samsung devices. So it seems there is a special problem with my SM-G800H, not with e building Pie in general. This is good news in a way. However, the thought that it probably has a very simple solution (if you only know where to “tap”) annoys me… But know-how-wise I only scrached the surface of rom building.

The post on XDA I know very well, I made it myself :grin:

1 Like

Hi @Manoj, although this has no priority at all, I would be very happy if it would be possible to have someone of the team give his opinion on what typical reasons in this case could be, or maybe if it makes sense at all to go on trying…?

One of the reason why some builds on LOS boot while the /e/OS ones do not is because the device manifests on /e/OS side are not updated. We /e/OS is not exactly a copy of LOS code. There are changes which at time do not work in builds. /e/OS not having dedicated maintainers for a number of devices is another issue.


Thank you, @Manoj, for giving your opinion, much appreciated!

After successfully building e for two other unsupported devices, always starting from an unofficial LOS build, I thought it to be the rule, that LOS device manifests would work with e. Now I understand from your reply that this is not necessarily the case.

I noticed there are about 40 repos (of about 700, depending on the version) in the default manifest specific to e, mostly forked from LineageOS. Are there “typical” (i.e. “e-specific”) issues to handle in such a case (just wondering what to look for)?

1 Like