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

Search This thread


Mar 29, 2016
Did you read my above answer? You must be on the latest build. I've also provided how to do the OTA ..

I think yes i have thé last build. No ?

And yes i have execute the command in a terminal for the OTA but no update.

2 screenshot.


  • Screenshot_20210111-232913_Updater.png
    56.6 KB · Views: 65
  • Screenshot_20210111-233104_LineageOS_Settings.png
    86.9 KB · Views: 65


Recognized Developer
Nov 13, 2013
I think yes i have thé last build. No ?

And yes i have execute the command in a terminal for the OTA but no update.

2 screenshot.
bad luck there was a small time slot where a build was online without enforcing. I have mentioned that in my automation channel, always a good idea to keep an eye on it.
Please flash the latest ROM which has the same date as yours in recovery manually.
  • Like
Reactions: francescum


Mar 29, 2016
but now i have a problem with the sound when i make calls. my interlocutor does not hear me and on my side the sound cuts

I have reflashing a stock ROM 2 times with differrent in odin:

and reinstall TWRP and your ROM, same problem ...

When i push the touch speaker the call sound work but only 3 or 4s, and if i re-push speaker touch he re-work, after push speaker touch sound reword but cut 3 or 4s after.

log : https://mensuel.framapad.org/p/x80hv8co6t-9l6m?lang=en
Last edited:


New member
Dec 24, 2020
SafetyNet got an update, it's not linked to the latest release.
With the following patch I'm able to pass SafeNet again :)

  • Like
Reactions: steadfasterX


New member
Feb 15, 2021
Are there any more detailed guides to flashing this? It seems I can only manage to bootloop the phone when flashing twrp unless there's something I'm missing.


Recognized Developer
Nov 13, 2013
Are there any more detailed guides to flashing this? It seems I can only manage to bootloop the phone when flashing twrp unless there's something I'm missing.

you would:
1. you unlock the device (there are guides for that)
2. flash latest TWRP in ODIN
3. boot directly to TWRP after that (otherwise TWRP will be overwritten on android boot - if you missed to boot into TWRP you have to repeat that step)
4. doing a full clean as described in FAQ 2
5. flash this ROM

If you struggle in flashing TWRP tell us which TWRP version you try, what ODIN version, how you flashed it in ODIN (i.e. in which slot)
also ensure you match the requirement as in the OP regarding the stock firmware version first.

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Thanx for great rom!

    whats the differences between Unofficial and Custom ?
    check out the brand new FAQ #9 for that ;)
    when you try to backup /data can you share the recovery.log aftewards?
    Here's my recovery.log: https://pastebin.com/ELaMqzQv
    News about SHRP: I understand that the recovery is expected to ask for a decrypting password at boot when /data is encrypted. Since SHRP does not ask for my PIN, I tried to force decryption via command line (https://twrp.me/faq/openrecoveryscript.html) and got the following:
    j5y17lte:/ # twrp decrypt ********
    Attempting to decrypt data partition or user data via command line.
    No crypto support was compiled into this build.
    j5y17lte:/ #
    SHRP's current behaviour is then expected.
    Pls see: https://code.binbash.rocks:8443/MVA...mmit/bfb5fe5ef00980739a72f50ed8376dfc12c20813
    Shouldn't the recovery try to backup the whole data partition as a single encrypted file then? Yet the log shows a per-file approach:
    788.| I:addFile '/data/misc_de/0/xnnZ+wmTPfWXkfeWumVXaD' including root: 0
    789.|   ==> set selinux context: u:object_r:storaged_data_file:s0
    790.| I:addFile '/data/system' including root: 0
    791.|   ==> set selinux context: u:object_r:system_data_file:s0
    792.| I:addFile '/data/system/EKRwi+BdRece6DSbSzpxxB' including root: 0
    793.|   ==> set selinux context: u:object_r:system_data_file:s0
    794.| I:Error adding file '/data/system/EKRwi+BdRece6DSbSzpxxB' to '/external_sd/TWRP/BACKUPS/5203ac375f5ab43b/2021-04-07--18-44-04_e_j5y17lte-userdebug_10_QQ3A200805001_30_UN/data.ext4.win'
    FBE (FILE based encryption), encrypts just files not a whole partition (which is done by FDE, Full Disk Encryption). So the recovery just see files there. It does not know anything else (e.g. that these are encrypted files) as this has been disabled in my recovery builds (bc - as said this is not working and might never will).

    the recovery will try to backup files as this is what they are: files. that part is expected.

    So one can ask: why is that failing then? Good question, the log does not really help here. Is it worth digging deeper - u may ask. well. lets say you have a backup of that encrypted data and wipe your device, restoring the backup, and then.. nothing. the device will not be able to decrypt these files again due to the wipe and so its useless backing up /data at all.
    Instead I recommend using regular backups within Android. I use Titanium Backup (paid ed) , encrypt these and upload the encrypted backup in gdrive.

    The latest build from today (CUSTOM) contains the fix for the call issue.
    UNOFFICIAL build follows in approx 9 hours (otherwise I would overwrite the today's build..). Check my TG group for a notification.

    So if you are on UNOFFICIAL wait for the tomorrow build or switch to the CUSTOM one (wipe system partition before then).
    Pls note that CUSTOM from yesterday and UNOFFICIAL from today contains a fix regarding the OTA server access - so once flashed OTA will work again. I mentioned that in my TG channel.

    Anyhow, the problems is this: The standard Camera app from /e/OS takes photos just fine, but videos are corrupted somehow. Playback shows only a still image and video length is shown as 98 hours or something like that. Gallery app shows other videos just fine, and the corrupted videos cannot be played on laptop either, so the problem really happens when saving the video.

    The workaround I discovered was to install the CameraMX app from Apps. Videos taken by it are also corrupted, *but* if its FX mode is enabled, videos are saved correctly. Even if no effects are enabled.

    Well I cannot re-produce this issue here so logs are crucial important.
    Pls try it again on the latest build and follow FAQ #1 to provide the proper logs.
  • 2

    brought to you by the

    * 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.


    • 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)
    • If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.

    • 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!

    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!


    Get your builds from my leech server (new installs or re-installs)

    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!)

    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.


    • search results from this thread: click


    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

    • 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..


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

    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

    Created 2020-10-01
    Last Updated 2020-10-01
    Very nice rom, working great, thank you for your work.
    Any news about getting it official?
    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.

    The ROM work Fine for me, except PIN and fingerprint configuration in lock screen ...

    I set PIN but no effect ater, my lock screen is set to swipe or no ...

    The ROM work Fine for me, except PIN and fingerprint configuration in lock screen ...

    I set PIN but no effect ater, my lock screen is set to swipe or no ...
    It´s the same here on my device. Only swipe to unlock works.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone