Galaxy J3 SM-J320F updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung Galaxy J3 (SM-J320F). The latest stable build is J320FXXU0ARL2 (Android 5, feature update), first released on Jan 13, 2019. Samsung has published 62 stable builds for this model since Jan 27, 2016: 3 security and 59 feature updates, from Android 5 to Android 5. The current bootloader (binary) version is 0. A device on bit 0 only accepts firmware with bit 0 or higher – see downgrading and the bootloader bit.
Rollout: build J320FXXU0ARL2 (Android 5) is live in 14 of 30 regions, first released on Jan 13, 2019 in TUR (Turkey). Still waiting: ATO, AUT, BNG, CAU, DBT, ETL, EUR, INS, ITV, LUX, ORX, PHN, SER, SLK and 2 more. In India (INS) the latest official firmware (flash file) is J320FDDU0ARD1 from May 30, 2018.
- Latest build
J320FXXU0ARL2- Released
- Jan 13, 2019
- Android
- Android 5
- Bootloader bit
- 0
- Regions
- 33
- Stable builds
- 62
Update policy
The Galaxy J3 no longer receives updates: the last firmware appeared on Jan 13, 2019, on Android 5.
Compare all models: Samsung update policy by model.
Latest firmware by region (CSC)
Samsung builds firmware per region code (CSC). Pick the code that matches your device – it is shown under Settings › About phone › Software information › Service provider software version. Follow a code for its complete history.
| CSC | Region | Latest build | Android | Released | Builds |
|---|---|---|---|---|---|
AFG | Afghanistan | J320FXXU0ARL2 | Android 5 | Jan 21, 2019 | 10 |
AFR | Africa | J320FXXU0ARL2 | Android 5 | Feb 6, 2019 | 10 |
ATO | Austria | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 7 |
AUT | Switzerland | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 6 |
BNG | Belgium | J320FDDU0ARD1 | Android 5 | Oct 10, 2018 | 9 |
CAU | Caucasus | J320FXXU0AQK2 | Android 5 | Nov 28, 2017 | 7 |
DBT | Germany | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 10 |
ETL | Czech Republic | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 6 |
EUR | Greece | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 7 |
ILO | Israel | J320FXXU0ARL2 | Android 5 | Jan 22, 2019 | 8 |
INS | India | J320FDDU0ARD1 | Android 5 | May 30, 2018 | 25 |
ITV | Italy | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 4 |
KSA | Saudi Arabia | J320FXXU0ARL2 | Android 5 | Jan 21, 2019 | 10 |
LUX | Luxemburg | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 6 |
LYS | Libya | J320FXXU0ARL2 | Android 5 | Jan 21, 2019 | 10 |
MID | Middle East | J320FXXU0ARL2 | Android 5 | Jan 21, 2019 | 10 |
MWD | Morocco | J320FXXU0ARL2 | Android 5 | Jan 22, 2019 | 10 |
ORX | Slovakia | J320FXXU0AQL1 | Android 5 | Jan 18, 2018 | 6 |
PAK | Pakistan | J320FXXU0ARL2 | Android 5 | Jan 21, 2019 | 9 |
PHN | Netherlands | J320FXXU0AQL1 | Android 5 | Jan 17, 2018 | 7 |
ROM | Romania | J320FXXU0AQL1 | Android 5 | Apr 12, 2023 | 7 |
SER | Russia | J320FXXU0AQK2 | Android 5 | Nov 20, 2017 | 12 |
SLK | Sri Lanka | J320FDDU0ARD1 | Android 5 | Jun 18, 2018 | 10 |
THR | Iran | J320FXXU0ARL2 | Android 5 | Jan 21, 2019 | 10 |
TMH | Hungary (Telekom) | J320FXXU0AQH2 | Android 5 | Mar 1, 2023 | 2 |
TPH | Portugal | J320FXXU0AQL1 | Android 5 | Jan 16, 2018 | 7 |
TUN | Tunisia | J320FXXU0ARL2 | Android 5 | Jan 21, 2019 | 11 |
TUR | Turkey | J320FXXU0ARL2 | Android 5 | Jan 13, 2019 | 11 |
XEH | Hungary | J320FXXU0AQL1 | Android 5 | Feb 28, 2023 | 7 |
XEO | Poland | J320FXXU0AQL1 | Android 5 | Jan 22, 2018 | 6 |
XFA | South Africa | J320FXXU0ARL2 | Android 5 | Feb 7, 2019 | 8 |
XFE | South Africa | J320FXXU0ARL2 | Android 5 | Jan 22, 2019 | 9 |
XSG | United Arab Emirates | J320FXXU0ARL2 | Android 5 | Jan 13, 2019 | 10 |
Firmware history (62 builds)
Every stable build (PDA version) Samsung has published for the SM-J320F, newest first. “Released” is the earliest date the build appeared on Samsung's servers in any region (how dates work). “pulled” means Samsung no longer serves the file for that build, usually because newer builds replaced it (details).
| Build (PDA) | Released | Android | Type | Bit | Regions | File |
|---|---|---|---|---|---|---|
J320FXXU0ARL2 | Jan 13, 2019 | Android 5 | Feature | 0 | 14 | on server |
J320FDDU0ARD1 | May 30, 2018 | Android 5 | Feature | 0 | 3 | on server |
J320FDRU0ARD1 | May 30, 2018 | Android 5 | Feature | 0 | 1 | on server |
J320FXXU0AQL2 | Jan 23, 2018 | Android 5 | Feature | 0 | 14 | on server |
J320FXXU0AQL1 | Jan 16, 2018 | Android 5 | Feature | 0 | 13 | on server |
J320FDRU0AQL2 | Jan 4, 2018 | Android 5 | Feature | 0 | 1 | on server |
J320FDDU0AQL2 | Jan 4, 2018 | Android 5 | Feature | 0 | 3 | on server |
J320FXXU0AQK2 | Nov 20, 2017 | Android 5 | Feature | 0 | 3 | on server |
J320FXXU0AQJ1 | Oct 30, 2017 | Android 5 | Feature | 0 | 15 | on server |
J320FDDU0AQJ2 | Oct 19, 2017 | Android 5 | Feature | 0 | 3 | pulled |
J320FDRU0AQJ2 | Oct 19, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDDU0AQI1 | Oct 5, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDRU0AQI1 | Sep 28, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQI1 | Sep 26, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQH3 | Sep 17, 2017 | Android 5 | Feature | 0 | 14 | pulled |
J320FXXU0AQH2 | Sep 7, 2017 | Android 5 | Feature | 0 | 1 | on server |
J320FDRS0AQH2 | Aug 28, 2017 | Android 5 | Security | 0 | 1 | pulled |
J320FXXU0AQG2 | Aug 1, 2017 | Android 5 | Feature | 0 | 15 | pulled |
J320FDRU0AQG1 | Jul 19, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDDU0AQG1 | Jul 19, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDDU0AQF1 | Jul 9, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQF1 | Jul 6, 2017 | Android 5 | Feature | 0 | 14 | pulled |
J320FDRU0AQF1 | Jul 2, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDRU0AQE2 | Jun 11, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQE2 | Jun 11, 2017 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXS0AQE3 | Jun 4, 2017 | Android 5 | Security | 0 | 1 | pulled |
J320FDRU0AQD2 | May 15, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDDU0AQE1 | May 15, 2017 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXU0AQD3 | May 3, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQD1 | Apr 24, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDDU0AQC3 | Apr 7, 2017 | Android 5 | Feature | 0 | 2 | pulled |
J320FXXU0AQC3 | Mar 30, 2017 | Android 5 | Feature | 0 | 5 | pulled |
J320FDRU0AQC1 | Mar 21, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FDRU0AQB3 | Mar 9, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQB3 | Mar 8, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQB1 | Mar 6, 2017 | Android 5 | Feature | 0 | 14 | pulled |
J320FXXU0AQA4 | Feb 19, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQA5 | Feb 2, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0AQA2 | Feb 1, 2017 | Android 5 | Feature | 0 | 2 | pulled |
J320FXXS0AQA1 | Jan 31, 2017 | Android 5 | Security | 0 | 10 | pulled |
J320FDDU0APL1 | Jan 19, 2017 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXU0APL3 | Jan 4, 2017 | Android 5 | Feature | 0 | 2 | pulled |
J320FXXU0APL2 | Dec 27, 2016 | Android 5 | Feature | 0 | 11 | pulled |
J320FDDU0APK3 | Dec 5, 2016 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0APK2 | Nov 7, 2016 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0APJ1 | Oct 29, 2016 | Android 5 | Feature | 0 | 1 | pulled |
J320FXXU0API2 | Oct 10, 2016 | Android 5 | Feature | 0 | 13 | pulled |
J320FXXU0API3 | Oct 5, 2016 | Android 5 | Feature | 0 | 14 | pulled |
J320FDDU0API2 | Sep 27, 2016 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXU0APG2 | Aug 25, 2016 | Android 5 | Feature | 0 | 2 | pulled |
J320FXXU0APH1 | Aug 16, 2016 | Android 5 | Feature | 0 | 2 | pulled |
J320FDDU0APH1 | Aug 11, 2016 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXU0APG1 | Aug 6, 2016 | Android 5 | Feature | 0 | 10 | pulled |
J320FXXU0APD4 | Apr 28, 2016 | Android 5 | Feature | 0 | 13 | pulled |
J320FXXU0APD5 | Apr 26, 2016 | Android 5 | Feature | 0 | 1 | pulled |
J320FDDU0APC4 | Apr 14, 2016 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXU0APC2 | Mar 28, 2016 | Android 5 | Feature | 0 | 1 | pulled |
J320FDDU0APC1 | Mar 14, 2016 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXU0APB8 | Mar 1, 2016 | Android 5 | Feature | 0 | 13 | pulled |
J320FXXU0APB7 | Feb 25, 2016 | Android 5 | Feature | 0 | 3 | pulled |
J320FXXU0APB3 | Feb 17, 2016 | Android 5 | Feature | 0 | 5 | pulled |
J320FXXU0APA8 | Jan 27, 2016 | Android 5 | Feature | 0 | 3 | pulled |
How to download SM-J320F firmware
We do not host firmware. Download it directly from Samsung's servers with a free open-source tool, for example samloader:
samloader download -m SM-J320F -r INSReplace INS with your region code. Step-by-step instructions, including a graphical alternative:
How to download Samsung firmware.
Changelog and security patch level
Samsung publishes the release notes for each update, including the security patch level, on its own site. They are listed per region – for example SM-J320F / INS release notes on doc.samsungmobile.com. Each region page here links to the notes for that code. We don't show the patch level ourselves because Samsung's update servers don't report it (why).