Development [ROM][UNOFFICIAL][Q] /e/ OS Q for Samsung Galaxy S10/S10e/S10+ (beyond*lte family)

Search This thread

sappounet

Member
Jan 30, 2011
48
9
Actually, by looking at the thread of the underlying ROM that is used to build this /e/ ROM, it seems like one person was able to install LOS+microG and have all the safety checks validated.

See https://forum.xda-developers.com/t/...-v1-4-update-2020-12-17.4076585/post-84220117

So when I have some time I will give a try to get the same kind of thing working on this /e/ ROM.

I guess that ideally we would want all the safety checks validated directly upon install, but I'm not exactly sure if it's technically possible to pre-patch the /e/ ROM image with those changes.

@Anghirrim do you think it would be possible ?
 

bertino

Senior Member
Oct 17, 2014
301
118
Actually, by looking at the thread of the underlying ROM that is used to build this /e/ ROM, it seems like one person was able to install LOS+microG and have all the safety checks validated.

See https://forum.xda-developers.com/t/...-v1-4-update-2020-12-17.4076585/post-84220117

So when I have some time I will give a try to get the same kind of thing working on this /e/ ROM.

I guess that ideally we would want all the safety checks validated directly upon install, but I'm not exactly sure if it's technically possible to pre-patch the /e/ ROM image with those changes.

@Anghirrim do you think it would be possible ?
I think that comment was referring to the checks inside microg settings, which indicate that microg has been properly installed, and not to safetynet, as some piece of the protocol used by apps to request safetynet verification is not properly implemented in microg. (see https://github.com/microg/RemoteDroidGuard/issues/24)
 

Anghirrim

Senior Member
Apr 29, 2011
1,102
246
Google Nexus 5
Samsung Galaxy J5

Anghirrim

Senior Member
Apr 29, 2011
1,102
246
Google Nexus 5
Samsung Galaxy J5
Updated 0.14 builds made by @petefoth (hope I mentionned the right guy accross forums).


@petefoth , feel free to update the links here too!
 

petefoth

Senior Member
@petefoth , feel free to update the links here too!

Before you flash, please read this post on the /e/ forums

The patched versions (name ending `-mpv`) have more chance of working, I would be very interested to know if the the unpatched Samsung Galaxy S10+ (SM-G975F, beyond2lte) works. Any and all feedback is welcome!

Here are the links to the relevant directories on Android File Host

- 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


The manifest used in the build is available here

Good luck!
 
  • Like
Reactions: Anghirrim

trendgegner

Member
Dec 2, 2020
14
1
Hey guys .. so I wanted to give some feedback after 3 weeks with e .13 .. mostly good I would say :)

overall it was pretty stable and fast

I don't tested much apps but only one I had problems with, was "ebay-kleinanzeigen" but could be because of trackers ?! Even banking apps worked stable.

BUT calling is still crazy! only way I found to do calls, is press powerBTN direct after starting a call and I had to remove all call-stoping settings from shortcut menu. (but still all existing shortcuts are pressed radomly, like light goes on)

Light-Sensor is the same, auto-brightness is just changing all the time. So Light- and Face-Sensor isn't working properly (but maybe is the same thing)
 

trendgegner

Member
Dec 2, 2020
14
1
Also wanted to try .14 from @petefoth but both images not working.
- beyond2lte-mpv is just 93MB
- beyond2lte says zip corrupt (see screenshot) .. downloaded twice on different browsers (chrome, opera) same result
 

Attachments

  • IMAGE 2021-01-26 21:10:39.jpg
    IMAGE 2021-01-26 21:10:39.jpg
    204.7 KB · Views: 22

petefoth

Senior Member
Also wanted to try .14 from @petefoth but both images not working.
- beyond2lte-mpv is just 93MB
- beyond2lte says zip corrupt (see screenshot) .. downloaded twice on different browsers (chrome, opera) same result

Looks like there was a problem uploading to Android File Host. I've deleted the corrupt files and uploaded the built versions again.

The patched version is at <https://www.androidfilehost.com/?fid=17248734326145722773>
The MD5 Checksum is b60b0747c048f4d022b089c0f1f83d59 . You should be able to use that to check the downloaded file, but I have no idea how to do that 🙂

The unpatched version is at <https://www.androidfilehost.com/?fid=17248734326145722777>. MD5 checksum is 43b7f41e79d50f75e0e0d846f09e8df1

Do let me know how it goes 🙂
 

trendgegner

Member
Dec 2, 2020
14
1
Upload looks good 987MB now ... will try first default than mpv and give you feed back soon
.. thanks for the new files ..
 

petefoth

Senior Member
I've learned how to use the md5sum

You use it to check the downloaded file: in the directory you downloaded to run the following

`md5sum e-0.14-q-20210124-UNOFFICIAL-beyond2lte-mpv.zip`

The number output should match the checksum i.e

`b60b0747c048f4d022b089c0f1f83d59 e-0.14-q-20210124-UNOFFICIAL-beyond2lte-mpv.zip`

The checksums shown on AFH match the checksums of the files on my build machine :)
 

trendgegner

Member
Dec 2, 2020
14
1
at least both zips now working .. BUT the beyond2lte freezes on yellow triangle screen .. installed twice (with and without wipe)
second (beyond2lte-mpv) works fine .. light sensor is still shaky, but feels a little better

tell you more, when I played a bit with it
 

KenHerman

Member
Feb 8, 2021
6
0
I've installed and run with success on my beyond2lte, but have 1 issue.
I can backup system (et al) with TWRP, but not data. It errors out with a createTarFork() 255 error.

All research I've seen on this error is to delete the offending file listed in the generated log, but I've tried deleting a large number of files through a large number of backup attempts. But, sadly, there is always a new file that causes the error. So, I gave up.

To be fair, this occurs on /e/ 0.12 and 0.13 also. Does anyone know how to fix or bypass this? I really can't use the rom if I can't backup and restore fully. So, for now, I've resigned myself to LineageOS 18.1, but I'd prefer /e/.

And, no, I'm not doing dirty installs - I'm wiping and formatting.

FYI - I have been able to backup data on Lineage and the stock rom - but /e/, no luck at all.

Any help or advice would be much appreciated.
 

petefoth

Senior Member
I've installed and run with success on my beyond2lte, but have 1 issue.
I can backup system (et al) with TWRP, but not data. It errors out with a createTarFork() 255 error.

All research I've seen on this error is to delete the offending file listed in the generated log, but I've tried deleting a large number of files through a large number of backup attempts. But, sadly, there is always a new file that causes the error. So, I gave up.

To be fair, this occurs on /e/ 0.12 and 0.13 also. Does anyone know how to fix or bypass this? I really can't use the rom if I can't backup and restore fully. So, for now, I've resigned myself to LineageOS 18.1, but I'd prefer /e/.

And, no, I'm not doing dirty installs - I'm wiping and formatting.

FYI - I have been able to backup data on Lineage and the stock rom - but /e/, no luck at all.

Any help or advice would be much appreciated.
Sorry I can't be much help as I don't own one of these devices .

I have experienced this problem on other devices, and the two things that have helped me in the past:

- Check you have the correct version of TWRP. Problems can be caused if the version you have is either too old, or too new for the software you are using. If you updated TWRP to work with LOS 18, you might need the earlier version to work with /e/, which is still Android 10 / Q.
- Try formatting your data partition rather than just wiping.

If neither of those help, then I'm fresh out of ideas :(
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    https%3A%2F%2Fe.foundation%2Fwp-content%2Fuploads%2Fe-color.png


    brought to you by the
    https%3A%2F%2Fe.foundation%2Fwp-content%2Fuploads%2FeFoundation-1-400x61.png


    Code:
    /*
    * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
    * Please do some research if you have any concerns about features included in the products you find here before flashing it!
    * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
    * Your warranty will be void if you tamper with any part of your device / software.
    * Same statement for XDA.
    */


    About /e/:
    /e/ is an a mobile ecosystem (ROM + onlines services) that:

    is open source
    is pro-privacy
    is compatible with most existing Android applications
    cares about usability
    is as far as possible freed from shackles by Google and OEMs
    already exists!

    It’s the alternative to the Apple/Google duopoly on the smartphone.

    ... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:

    an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
    a set of sorted and improved default open source applications
    various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.


    Features:
    Based on the stable Lineage OS 17.1
    microG fully pre-installed with Signature Spoofing in restricted mode!
    All features described on the /e/ page: What is e
    All features and fixes of our LOS 17.1 builds (Whatawurst team).
    No OTA suppport for now.

    What works:
    Same as Whatawurst team LOS 17.1 build

    Known issues:
    /e/ Q is still in development stage (still, stable enough for a daily driver with no bugs). So you may still see one or two calls to Google servers until the Q branch is official.
    You tell me
    Same as Whatawurst team LOS 17.1 build

    SECURITY ADVICE

    Don't flash Magisk modules or anything else which sets SELinux to permissive or you open your device for malware!
    Do not flash Multi Disabler on this ROM!


    Requirements:
    Latest TWRP build.
    Do a full Nandroid backup before doing anything!



    Installation:
    If this is your first time flashing a rom, or not coming from @modpunk LOS 17.1 build, please follow the same steps than their detailed installation process

    Otherwise:
    Full clean install is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
    Flash /e/
    Optional (if you want root): Flash Magisk
    Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
    Boot it (will take a bit on first boot!!! be patient!)
    Enjoy the most easy way to have a privacy focused and google-free phone!


    Download:
    Get your builds from my GoogleDrive (I know, it's ironical)
    S10e (beyond0lte, SM-G970F)
    S10 (beyond1lte, SM-G973F)
    S10+ (beyond2lte, SM-G975F)

    Note:
    Builds are updated as soon as possible. There is no build cycle.
    Information pertaining to your device is displayed accordingly.
    The current build is the latest for your device.

    Changelogs:
    Check /e/, LineageOS or whatawurst team changelogs. I build straight from sources

    Support:
    /e/ Support Telegram Channel


    Credits:
    LineageOS (the base of /e/)
    The /e/ foundation and all related devs making this experience possible!
    the whatawurst team for their kernel, device and vendor sources.
    The Exynos9820 Team
    and more..



    Sources:
    How to build /e/
    Local_manifest ==> See attachments


    XDA:DevDB Information
    beyond0lte_eos-Q_custom, ROM for the Samsung Galaxy S10e Exynos

    Contributors:
    Whatawurst team (modpunk, derf elot,Linux4), steadfasterX, Exynos9820 Team

    Source Code:
    https://github.com/whatawurst/

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: XXS9DTI8
    Based On: LineageOS

    Version Information
    Status: Stable
    Stable Release Date: 2020-11-25
    1
    waited both times nearly an hour, but still on triangle page.
    Would make sence to try, the earlier version (20201107)?
    .. thanks a lot .. (twice, because I missed it before:)
    1
    Ah good, your answer is still here!!

    How about checking the md5 on your PC, is the output OK compared with the md5sum files available on the drive?

    Thanks
    Hi, sorry for the delay in answering, I haven't been able to log in so re-registered.
    I checked the md5 and they matched. After installing modpunks LOS 17.1 I thought I would try the earlier build of your /e/ os and it installed without a problem.
    Been using it for a few days and have had no issues.
    Thankyou
    1
    Well, new attempt uploaded for the S10+ (beyond2lte).

    There are two builds on 12/13/2020.
    - e-0.13-q-20201213-UNOFFICIAL-beyond2lte.zip ==> the one to test first, with my hopefully fixed vendor
    - e-0.13-q-20201213-UNOFFICIAL-beyond2lte_mpv.zip ==> Same as above, but with manually replaced vendor.img, using modpunk's latest build one.

    Can someone test and report if it boots? @trendgegner maybe?

    Download folder, same as usual.
    1
    Thank you Anghirrim for your great work !

    I should receive my S10e by the end of next week, and since my existing phone (Xiaomi) is still working perfectly fine, I will be happy to assist with doing some testing on my S10e for couple of days if needed.

    I'll keep an eye on the thread to see if there are more tests needed by the end of next week.

    Also, I have another question :
    I saw that modpunk will stop updating his LOS 17.1 image, and will start working on LOS 18.1.
    But since /e/ does not support LOS18.1 yet, what are your plans ? Do you consider switching to Ivan_Meler's LOS17.1 version ?
    I guess switching to Ivan's version would be the only way to keep the security patches up to date, no ?