One more question if I may. I thought about it a bit more and, as we are going to use the vendor files from @modpunk’s ROM, then it doesn’t matter what we have in our vendor files. If we can get our ROM to build from the files in the whatawurst vendor repos referenced in your manifest, then we just have to swap our vendor files out after the build, and we would not need to extract all vendor files from @modpunk’s ROM to make ours?
[ANSWER] beyond0lte,beyond1lte both build OK. beyond2lte is missing some vendor files. Instead, I’m using vendor files from zunaid321's android_vendor_samsung_beyond2lte repo
Or is it the case that our ROM won’t build using the files in the whatawurst repos? (I know I could find this out by trying to build, but a: I’m lazy and b: I’d like to find out what I may be letting myself in for!)
And finally (for now ). What device code(s) did you put in the DEVICE_LIST parameter in your build? Is it beyond0lte,beyond1lte,beyond2lte? [SOLVED] Those are the correct device codes
So here are some freshly made ROMs, built from the v0.14q tag
I don’t own any of these devices, so I can’t flash these ROMs and I don’t know whether they will work. There is no reason why they shouldn’t, but please back up everything before you start!
If you are currently running one of @Anghirrim’s e-0.13-q ROMs, then there is a good chance that a ‘dirty flash’ (i.e. without wiping the data partition) will work, but if you care about your existing apps and data, please back up everything before you start!
(A dirty flash may also work if you are currently running a LineageOS 17.1 ROM.)
If this is your first custom ROM, then I would repeat @Anghirrim’s advice in an earlier post
To make the builds I have taken the same approach as @Anghirrim:
I have built the ROMs as usual (see below for more details) using this manifest, based on @Anghirrim’s, but with a change to pick up vendor files for the S10+ from a different repo (owned by a developer known as @zunaid321 who builds AOSP-based ROMs). These files are named as you would expect - e-0.14-q-.... .zip
I have then created patched versions by removing the built vendor files and replacing them with the vendor files from @modpunks latest LineageOS 17.1 ROMs. These files have the characters -mpv appended to the name e-0.14-q-.....-mpv.zip
For S10e (SM-G970F, beyond0lte) and Samsung Galaxy S10 (SM-G973F, beyond1lte) the patched (-mpv) versions are most likely to work, as I haven’t done anything differently from @Anghirrim’s early ROMs. If anyone has time to try the unpatched versions, that would be great, but if you just want to get your phone working, then go with the patched version
For Samsung Galaxy S10+ (SM-G975F, beyond2lte), it may be worth trying the unpatched version, as I am picking up the vendor files from a different repo, and I would love to know whether that makes any difference and allows the ROMs to boot. Again though, if you’re in a hurry, probably best to start with the patched version.
So - and with a final reminder to please back up everything before you start! - here are the files
For Samsung Galaxy S10e (SM-G970F, beyond0lte) the files are here
Samsung Galaxy S10 (SM-G973F, beyond1lte) the files are here
Samsung Galaxy S10+ (SM-G975F, beyond2lte) the files are here
I currently build using a patched version of @andrelam’s?) builde script but it should be possible to build the official way using Docker, (or any other combination of spells that works for you to build e-OS ROMs ). The important / interesting variables I used in the build were
I’ve no plans to do anything with Android 11 until the /e/ developers start making official builds available.
All I am doing is building for devices that /e/ don’t plan to support, and my main interest is in the Sony devices that I actually own Once I have builds for those, I’m happy to build for other devices so long as the build doesn’t take too long. But no long term commitment to support any particular ROM.
At the moment I have a lot of time for this because the weather is awful and golf courses are closed because of Covid. When that changes I will be spending much less time on ROM building
I can point you in the right direction, but it’ll take a couple of days to pull my notes together.You need access to a powerful computer - either your own, or in the cloud - with plenty of memory, 250GB or more disk storage and good internet bandwidth. There are a couple of cloud providers who offer free or cheap computing resource which is how I started off. I’ll give more information and links when I can
In the meantime have a look at this document. It’s the official guide on how to build /e/. That’s pretty much how I started.
Hello, I tried on my S10+ … but didn’t work at all! … -mpv file should be 986.6MB when I download its just 93MB.
beyond2lte looks good (937.5MB) but when I try to install, I get “Zip file is corrupt!” in TWRP
Still looking for an reliable version, @Anghirrim version 13 is already better than 12, but still have many issues with face-sensor (or light-sensor). Some apps are freezing (kleinanzeigen from ebay) … but funny thing is banking apps are running like charm (would have expected the opposite:)
Hey thanks for fast reply (I also posted in xda-forum, sorry was my usual spot:)
mpv version says 986.6MB till the moment you really download, than it save 93MB file tried 3 Browsers now (chrome, opera, tor) each time multiple mirros all the same 93MB file gets saved … maybe a problem with androidfilehost! they should measure the file, right?
the default one (beyond2lte) I tried with and without verification, when on “Zip signature verification failed!”, when off “Zip file is corrupt”.
Downloaded on Opera and Chrome, but the same … My steps: download, copy on SD, start TWRP, wipe “Cache/Dalvic”, format Data, install …
anything wrong with my steps?
Hi @petefoth hope you’re well.
Are you able to create another build for the Samsung S10e? The one based on 0.16 please.
Otherwise I guess I can always install the previous build and update to the latest one using the OTA from /e/?
I’m very sorry, but I have a lot less free time on my hands at the moment, and the time I do have to spend on /e/, I am spending on the two Sony devices (z3c, suzuran) for which I’m the official maintainer, a third which is my daily driver (lilac) and, if I get any spare time, some other Sony devices for which I can produce builds with little or no effort.
The work on these Samsung phones was definitely a one-off for me. But my manifest is still available if anyone else has some free time to take on the build.
/e/ only provide OTA updates for devices which they officially support. For OTA updates of unofficial devices, you would need to find someone who not only has the time to spare to make the builds, but als has access to a server where they can make the OTA updates available. I hope you do, but I wouldn’t hold my breath. Sorry again