Development [ROM][UNOFFICIAL][Q/A10][SM-J530F] /e/ OS for Samsung J5 2017 (j5y17lte) - BYE Google, HELLO Privacy!

Search This thread

steadfasterX

Recognized Developer
Nov 13, 2013
5,944
15,217
127.0.0.1
OnePlus 7T Pro
e-color.png

brought to you by the
eFoundation-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
  • 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 LineageOS
  • My builds come with full OTA update support :)
    ... you know that thing which informs you that a new update is there and where you just click to download + install ;)


Difference from pure /e/ or: why are the builds UNOFFICIAL?

  • There are no differences. its pure /e/. just an unofficial build (if you want to have it official test my builds and report also SUCCESS! this ROM is currently awaiting to get approved by /e/ for official builds)


Known issues:

Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!

  • When your current STOCK firmware or the latest you had flashed is not PIE (Android 9) then flash the following STOCK version: J530FXXS7CTF1 (pie)
  • selinux: permissive (will be set to enforcing once I got some user feedback if my build working as stable for others as for me)
  • Camera preview is "stretched". This affects the preview only, pictures taken are fine. sorry there is no known way to solve that afaik.
  • If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.


Requirements
  • Latest TWRP or SHRP build.
  • This ROM has been tested with stock firmware J530FXXS7CTF1 . If you use an older one switch to this first. If you have a newer one things might not work for you (like cam etc)
  • Do a full (i.e. Nandroid) backup before doing anything!


Installation
  1. Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
  2. Flash /e/
  3. Optional (if you want root): Flash Magisk
  4. 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).
  5. Boot it (will take a bit on first boot!!! be patient!)
  6. Enjoy the most easy way to have a privacy focused and google-free phone!


Download

Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/a10/

If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)

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


Changelogs

  • search results from this thread: click


Support

Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here


Credits
  • nailyk :)
  • Astrako, wth.. you did an AWESOME job for this SoC!
  • LineageOS (the base of /e/)
  • The /e/ foundation and all related devs making this experience possible!
  • The Exynos7870 Team
  • and more..


Sources

XDA:DevDB Information
j5y17lte_eos-q_unofficial, ROM for the Samsung Galaxy J5

Contributors
steadfasterX, nailyk, Astrako for ALL Q porting stuff!!! and: ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e

ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: only tested on PIE bootloader - so upgrade if you are on Oreo or older
Based On: Lineage OS

Version Information
Status:
Stable

Created 2020-10-01
Last Updated 2020-10-01
 
Last edited:

steadfasterX

Recognized Developer
Nov 13, 2013
5,944
15,217
127.0.0.1
OnePlus 7T Pro
.

Frequently Asked Questions (FAQ)

Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.

Often selinux can cause issues so try that at very first:
Code:
if you have magisk installed:
adb shell
su
setenforce permissive

When " usb debugging root" is enabled in developer settings:
adb root
adb shell
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)

If your issue is not solved with selinux permissive click here to proceed:

If your issue is not listed there follow the directions here briefly and I may can fix it:

logcat GUIDE

Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).

Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.

Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.

so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.


Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues

Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.

A regular clean install can be done like this:
  • WIPE -> Advanced -> select: System + Cache
  • Flash the ROM
  • reflash root addon/magisk if you want root

A full clean install needs 2 steps more then the regular:
  • follow the steps for regular clean
  • go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
  • REBOOT -> Recovery
  • Flash the ROM
  • reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.


Q #03: Are there any plans or a chance of official /e/ builds?
Yes. With your help! What you can do? Test and report EVEN SUCCESS in this thread.


Q #4: Is there an /e/ specific FAQ?
Sure:

  • FAQ: click
  • Forum: click
  • HOWTOs: click (a great resource for all your first questions)


Q #5: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:

  • 1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
  • 2) Then perform the following (all one command)

    On Linux:
    adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"

    On windows:
    adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "

  • 3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!

  • 4) Share the logcat output from the console screen using paste.omnirom.org


Q #6: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:


In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.


Q #7: What is the difference between CUSTOM and UNOFFICIAL builds?
UNOFFICIAL is like pure /e/ - untouched. This is the base for OFFICIAL builds (coming soon)
CUSTOM:
  • removed: /e/ Apps (read here why)
  • added: AuroraStore, F-Droid, F-Droid xtra repos (manual enable required), DNS66 (adblock w/o root), Omega Launcher (as alternative Launcher)

.-
 
Last edited:
D

Deleted member 9071371

Guest
Gooooood Work!
Will love to see it on other 7870s as well....😅👍
 

pac4life

New member
Dec 27, 2015
4
0
Redmi 9
amazing work sir
it works perfectly so far

sad cuz i cant flash other kernels but hey its smooth af even with stock kernel 💪



keep up the good work 💪
 
Last edited:

steadfasterX

Recognized Developer
Nov 13, 2013
5,944
15,217
127.0.0.1
OnePlus 7T Pro
The last version that was available on SamMobile... It was "J530FXXU6CSK9_J530FXEF6CSL1_XEF"... if that's what you asked...

Here is the screenshot : https://ibb.co/7Q8jq2N
Well i would expect that it should work but as it does not flash the J530FXXS7CTF1 stock firmware . You could also try just flashing the modem partition of that firmware but if you dont know how then the fulk stock firmware is the easiest.





Sent from my OnePlus 7T Pro using XDA Labs
 

tiboleplubo

New member
Mar 23, 2020
4
0
Well i would expect that it should work but as it does not flash the J530FXXS7CTF1 stock firmware . You could also try just flashing the modem partition of that firmware but if you dont know how then the fulk stock firmware is the easiest.

It works now ! (I don't understand, I didn't do anything... Just think I had not been patient enough ^^')
Sorry for disturbing ^^' Anyway, thanks again, I hope we'll get an official build !
 

pupunar

Member
Oct 28, 2010
6
0
Gapps

Hi, thanks for your work. Please, i need to have gapp on this Rom, how i can (if is possible) install it?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,944
15,217
127.0.0.1
OnePlus 7T Pro
Hi, thanks for your work. Please, i need to have gapp on this Rom, how i can (if is possible) install it?

uhm.. you want to use /e/ which main goal is to live without google.... and you want to install google bloat and spyware on it? maybe read the Installation topic again?

View attachment 5119347

if you really need gapps (really?) and so google crap then simply go with LOS instead.

.-
 

lPolarisl

Member
Dec 25, 2018
23
1
Hey !
Quick question, I currently have an unofficial CrDroid on my phone that works great, except for the camera, which is stretched in almost all the apps...
So, just to be sure, does the camera work flawlessly in this rom ?

Thanks for your hard work ! :victory:
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,944
15,217
127.0.0.1
OnePlus 7T Pro
Hey !
Quick question, I currently have an unofficial CrDroid on my phone that works great, except for the camera, which is stretched in almost all the apps...
So, just to be sure, does the camera work flawlessly in this rom ?

Thanks for your hard work ! :victory:
Yea within my vacation i had an user report about that. Will check that soon.


Sent from my OnePlus 7T Pro using XDA Labs
 

Morceaux

Member
Aug 12, 2020
10
0
Hi, I have a question, I have only one app on my phone that use the Google Service Framework sadly..
I'm pretty sure I already know the answer, but will it work with /e/ ?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,944
15,217
127.0.0.1
OnePlus 7T Pro

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hello again, managed to try with SoundpeatsAir3, and the behavior is the same as with the car audio, i.e., I can play music, but only get noise when a call connects.

    Logcat also looks very similar :-( :


    - any idea what else I could try to find out more? Thanks.
    I have exactly the same problem on the same device, but with a CrDroid OS...
    1
    when doing that logcat could you switch between BT and speaker (while not disconnecting the call ofc)? --> share that log then :)
    what happens when switching to speaker then btw? Are you able to hear the other site?
    Is there any diff when you call out or someone calls in?

    So far, no difference observed between incoming and outgoing calls.
    After switching to the speaker during the call, if I remember correctly, the sound started to be normal (and noise again after switching back to the BT headset).
    Anyway, I'm going to re-check and send the corresponding logs :)
  • 5
    e-color.png

    brought to you by the
    eFoundation-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
    • 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 LineageOS
    • My builds come with full OTA update support :)
      ... you know that thing which informs you that a new update is there and where you just click to download + install ;)


    Difference from pure /e/ or: why are the builds UNOFFICIAL?

    • There are no differences. its pure /e/. just an unofficial build (if you want to have it official test my builds and report also SUCCESS! this ROM is currently awaiting to get approved by /e/ for official builds)


    Known issues:

    Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
    So back up regularly and frequently!

    • When your current STOCK firmware or the latest you had flashed is not PIE (Android 9) then flash the following STOCK version: J530FXXS7CTF1 (pie)
    • selinux: permissive (will be set to enforcing once I got some user feedback if my build working as stable for others as for me)
    • Camera preview is "stretched". This affects the preview only, pictures taken are fine. sorry there is no known way to solve that afaik.
    • If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.


    Requirements
    • Latest TWRP or SHRP build.
    • This ROM has been tested with stock firmware J530FXXS7CTF1 . If you use an older one switch to this first. If you have a newer one things might not work for you (like cam etc)
    • Do a full (i.e. Nandroid) backup before doing anything!


    Installation
    1. Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
    2. Flash /e/
    3. Optional (if you want root): Flash Magisk
    4. 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).
    5. Boot it (will take a bit on first boot!!! be patient!)
    6. Enjoy the most easy way to have a privacy focused and google-free phone!


    Download

    Get your builds from my leech server (new installs or re-installs)
    http://leech.binbash.rocks:8008/e-os/a10/

    If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
    Android settings -> Updater (yes my builds have built-in OTA support!)

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


    Changelogs

    • search results from this thread: click


    Support

    Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
    and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here


    Credits
    • nailyk :)
    • Astrako, wth.. you did an AWESOME job for this SoC!
    • LineageOS (the base of /e/)
    • The /e/ foundation and all related devs making this experience possible!
    • The Exynos7870 Team
    • and more..


    Sources

    XDA:DevDB Information
    j5y17lte_eos-q_unofficial, ROM for the Samsung Galaxy J5

    Contributors
    steadfasterX, nailyk, Astrako for ALL Q porting stuff!!! and: ananjaser1211,DarkLord1731,Exynos7870 Team (github)
    Source Code: https://gitlab.e.foundation/e

    ROM OS Version: Android 10
    ROM Kernel: Linux 3.x
    ROM Firmware Required: only tested on PIE bootloader - so upgrade if you are on Oreo or older
    Based On: Lineage OS

    Version Information
    Status:
    Stable

    Created 2020-10-01
    Last Updated 2020-10-01
    2
    Hey steadfasterX,

    thx for your work. I tried your build on a j5 and it works wonderful!

    I have aquestion regarding updates: as I thought it would work, I would look at my "Updater" App and will see if there is a new version. But now I got an automated system message that there are new updates, but they seem to be directly from e. I am a bit confused. The system meessage let me download: e os 0.19 (27.09.2021) and e os 0.18 (8.08.2021). Are these messages for your version?

    thanks and best regards
    Vik iA
    You can check where the update is coming from like this:
    In the updater app,
    long press the update.
    Option to "Copy URL" pops up.
    Select it,
    then paste clipboard contents somewhere.
    Check if the update is coming from
    where you expected.
    1
    Hello,
    Very nice rom, working great, thank you for your work.
    Any news about getting it official?
    1
    Thanks for your great rom. (y)I have installed it on a space locked J5, and now there are 9GB free flash space, this is great!
    At the moment I see two minor problems:
    Is it some hoe possible to fix the mac address for known networks. At the moment I get a new mac after each reboot.
    Volte looks disabled with this rom. Is there a possibility to enable volte?
    Thanks again for your great work.
    1
    when doing that logcat could you switch between BT and speaker (while not disconnecting the call ofc)? --> share that log then :)
    what happens when switching to speaker then btw? Are you able to hear the other site?
    Is there any diff when you call out or someone calls in?

    So far, no difference observed between incoming and outgoing calls.
    After switching to the speaker during the call, if I remember correctly, the sound started to be normal (and noise again after switching back to the BT headset).
    Anyway, I'm going to re-check and send the corresponding logs :)