Samsung J5 (2017)
Overview
| codename j5y17lte | |
| Flavor (?): | Pro |
|---|---|
| Android: | 10 |
| First released: | 2024-06-20 |
| Firmware: | manual |
| Encryption (?): | FBEv1 |
| Relockable: | no |
| VerifiedBoot/AVB (?): | false |
| Verified & tested by: | The AXP.OS team |
| State: | stable |
Installation guide
You want to switch between flavors or coming from DivestOS?
Please read this first: All about AXP.OS flavors If you miss a flavor you can request it here.
Known issues
General Known Issues
Issue tracker won’t fix
Boot modes
Each device has its own method to access special boot modes.
See: j5y17lte (@LineageOS wiki)
Firmware
AXP.OS for the Samsung J5 (2017) does not include firmware.
You must ensure correct firmware manually to avoid unexpected problems.
Follow the firmware guide.
If missing, check the j5y17lte firmware guide and match the Android version.
Install / Upgrade
recovery
While not recommended you can use any other recovery of course but keep in mind that only the official one is able to verify the AXP.OS OTA signature and is hardened* like the OS itself. So it is HIGHLY recommended to use the official AXP.OS recovery.
Download the latest official AXP.OS recovery from here: leech server
*) note: the hardened recovery by AXP.OS for the J5 includes all security patches and hardening as the OS except for being permissive. exploiting this recovery is not easy though as the only attack surface is the OTA or sideload mechanism (i.e. those must have vulnerabilities and then an attacker still might require additional vulns to get any further). In any case it is WAY more secure then using TWRP or any other custom recovery.
Flashing the recovery should be done by using heimdall (a tool which is e.g. included in mAid):
heimdall flash --RECOVERY recovery.img
then boot to recovery and follow the guide Install (non A/B) guide:
Setup AXP.OS
Follow Setup
XDA thread
See here
Debugging
DEVICE-BOOT-DEBUG-PATH: /cache
See Logs
Download
All downloads have a GPG signed sha512sum file which should be used to verify the download & file integrity.Details how to make use out of it can be found here.
💡 The hashsum of new builds are also send in the sfX Automation channel. This gives you a second and independent option for comparison if the download server is compromised.
| Flavor (what's this?) | OS zip | Recovery image | Release key (what's this?) |
|---|---|---|---|
| Pro 🥩 | |||