Galaxy J3 SM-J320M updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung Galaxy J3 (SM-J320M). The latest stable build is J320MUBU0ASG1 (Android 5, feature update), first released on Aug 12, 2019. Samsung has published 44 stable builds for this model since Feb 11, 2016: 5 security and 39 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 J320MUBU0ASG1 (Android 5) is live in 1 of 32 regions, first released on Aug 12, 2019 in JDI (Jamaica (Digicel)). Still waiting: ARO, BVO, CDR, CGU, CHE, CHL, CHO, CHT, CHX, COB, COM, COO, CRC, CTI and 17 more.
- Latest build
J320MUBU0ASG1- Released
- Aug 12, 2019
- Android
- Android 5
- Bootloader bit
- 0
- Regions
- 33
- Stable builds
- 44
Update policy
The Galaxy J3 no longer receives updates: the last firmware appeared on Aug 12, 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 |
|---|---|---|---|---|---|
ARO | Argentina | J320MUBU0ARD1 | Android 5 | Jul 8, 2018 | 10 |
BVO | Bolivia | J320MUBU0ARK1 | Android 5 | Dec 10, 2018 | 12 |
CDR | Dominican Republic | J320MUBS0AQL6 | Android 5 | Jan 29, 2018 | 5 |
CGU | Guatemala (Claro) | J320MUBS0AQL4 | Android 5 | Jan 29, 2018 | 6 |
CHE | Chile (Entel) | J320MUBU0AQI2 | Android 5 | May 8, 2018 | 3 |
CHL | Chile (Claro) | J320MUBS0ARC1 | Android 5 | Jun 11, 2018 | 6 |
CHO | Chile | J320MUBU0ARB3 | Android 5 | Jul 17, 2018 | 12 |
CHT | Chile (Movistar) | J320MUBU0APAC | Android 5 | Feb 24, 2016 | 1 |
CHX | Chile | J320MUBS0AQL2 | Android 5 | Feb 25, 2018 | 5 |
COB | Colombia (Movistar) | J320MUBS0AQL4 | Android 5 | Jan 22, 2018 | 7 |
COM | Colombia (Claro) | J320MUBS0AQL3 | Android 5 | Sep 16, 2018 | 5 |
COO | Colombia | J320MUBU0ARB3 | Android 5 | Jun 17, 2018 | 12 |
CRC | Costa Rica | J320MUBS0AQL3 | Android 5 | Jan 22, 2018 | 4 |
CTI | Argentina (Claro) | J320MUBS0AQL3 | Android 5 | Jan 22, 2018 | 7 |
EBE | Ecuador | J320MUBU0APE2 | Android 5 | Jun 7, 2016 | 2 |
ECO | Ecuador | J320MUBU0ARB1 | Android 5 | May 9, 2018 | 5 |
IUS | Mexico (AT&T) | J320MUBU0AQB1 | Android 5 | Apr 11, 2017 | 2 |
JDI | Jamaica (Digicel) | J320MUBU0ASG1 | Android 5 | Aug 12, 2019 | 7 |
PEO | Peru | J320MUBU0ARB3 | Android 5 | Mar 8, 2018 | 5 |
PET | Peru (Movistar) | J320MVJU0ARH1 | Android 5 | Aug 26, 2018 | 4 |
PGU | Guatemala | J320MUBS0AQL3 | Android 5 | Jan 22, 2018 | 5 |
PNT | Panama | J320MVJU0ARC1 | Android 5 | Apr 8, 2018 | 9 |
PSN | Argentina (Personal) | J320MUBU0ARD1 | Android 5 | Nov 28, 2018 | 7 |
TCE | Mexico (Telcel) | J320MUBS0AQL4 | Android 5 | Jan 22, 2018 | 5 |
TMM | Myanmar | J320MUBU0ARA2 | Android 5 | Jul 3, 2018 | 3 |
TPA | Panama | J320MUBU0ARB3 | Android 5 | Jul 1, 2018 | 14 |
TTT | Trinidad & Tobago | J320MUBU0ARB3 | Android 5 | Jul 1, 2018 | 13 |
UFN | Argentina (Movistar) | J320MUBU0ARA2 | Android 5 | Nov 12, 2020 | 4 |
UPO | Uruguay | J320MUBU0ARB3 | Android 5 | Aug 22, 2018 | 9 |
UYO | Uruguay | J320MUBU0ARB3 | Android 5 | Jul 12, 2018 | 13 |
ZTA | Brazil (Claro) | J320MUBU0ARD1 | Android 5 | Aug 9, 2018 | 7 |
ZTO | Brazil | J320MUBU0ARD1 | Android 5 | Aug 12, 2018 | 13 |
ZTR | Brazil (Oi) | J320MUBU0ARD1 | Android 5 | Aug 22, 2018 | 8 |
Firmware history (44 builds)
Every stable build (PDA version) Samsung has published for the SM-J320M, 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 |
|---|---|---|---|---|---|---|
J320MUBU0ASG1 | Aug 12, 2019 | Android 5 | Feature | 0 | 1 | on server |
J320MUBU0ARK1 | Dec 10, 2018 | Android 5 | Feature | 0 | 1 | on server |
J320MVJU0ARH1 | Aug 26, 2018 | Android 5 | Feature | 0 | 1 | on server |
J320MUBU0ARD1 | Jul 8, 2018 | Android 5 | Feature | 0 | 5 | on server |
J320MUBS0ARC1 | Jun 11, 2018 | Android 5 | Security | 0 | 1 | on server |
J320MUBU0ARB1 | May 9, 2018 | Android 5 | Feature | 0 | 1 | on server |
J320MVJU0ARC1 | Apr 8, 2018 | Android 5 | Feature | 0 | 2 | on server |
J320MUBU0ARA2 | Mar 29, 2018 | Android 5 | Feature | 0 | 2 | on server |
J320MUBU0ARB3 | Mar 8, 2018 | Android 5 | Feature | 0 | 9 | on server |
J320MUBS0AQL6 | Jan 29, 2018 | Android 5 | Security | 0 | 1 | on server |
J320MUBS0AQL3 | Jan 22, 2018 | Android 5 | Security | 0 | 4 | on server |
J320MUBS0AQL4 | Jan 22, 2018 | Android 5 | Security | 0 | 4 | on server |
J320MVJU0AQL1 | Jan 10, 2018 | Android 5 | Feature | 0 | 1 | on server |
J320MUBS0AQL2 | Jan 4, 2018 | Android 5 | Security | 0 | 14 | on server |
J320MUBU0AQJ3 | Dec 12, 2017 | Android 5 | Feature | 0 | 1 | on server |
J320MUBU0AQD1 | Dec 8, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320MVJU0AQJ2 | Nov 20, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320MUBU0AQJ2 | Nov 16, 2017 | Android 5 | Feature | 0 | 4 | on server |
J320MUBU0AQE2 | Nov 2, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320MUBU0AQI3 | Oct 17, 2017 | Android 5 | Feature | 0 | 5 | on server |
J320MUBU0AQI2 | Oct 5, 2017 | Android 5 | Feature | 0 | 15 | on server |
J320MVJU0AQG3 | Aug 23, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320MUBU0AQG2 | Aug 9, 2017 | Android 5 | Feature | 0 | 6 | on server |
J320MUBU0AQG4 | Aug 9, 2017 | Android 5 | Feature | 0 | 4 | pulled |
J320MUBU0AQG3 | Aug 2, 2017 | Android 5 | Feature | 0 | 12 | pulled |
J320MUBU0AQE1 | Jun 8, 2017 | Android 5 | Feature | 0 | 10 | pulled |
J320MUBU0AQB2 | Mar 12, 2017 | Android 5 | Feature | 0 | 1 | pulled |
J320MUBU0AQB1 | Feb 20, 2017 | Android 5 | Feature | 0 | 5 | on server |
J320MUBU0AQA3 | Feb 2, 2017 | Android 5 | Feature | 0 | 4 | pulled |
J320MUBU0AQA1 | Jan 18, 2017 | Android 5 | Feature | 0 | 9 | pulled |
J320MUBU0APJ1 | Nov 7, 2016 | Android 5 | Feature | 0 | 4 | on server |
J320MUBU0API2 | Oct 11, 2016 | Android 5 | Feature | 0 | 2 | pulled |
J320MUBU0API1 | Oct 2, 2016 | Android 5 | Feature | 0 | 22 | on server |
J320MUBU0APH1 | Sep 6, 2016 | Android 5 | Feature | 0 | 5 | pulled |
J320MUBU0APG3 | Aug 17, 2016 | Android 5 | Feature | 0 | 1 | pulled |
J320MUBU0APF1 | Jul 10, 2016 | Android 5 | Feature | 0 | 2 | pulled |
J320MUBU0APE3 | Jun 13, 2016 | Android 5 | Feature | 0 | 13 | pulled |
J320MUBU0APE2 | Jun 7, 2016 | Android 5 | Feature | 0 | 1 | on server |
J320MUBU0APE1 | May 23, 2016 | Android 5 | Feature | 0 | 6 | pulled |
J320MUBU0APD2 | May 17, 2016 | Android 5 | Feature | 0 | 3 | pulled |
J320MUBU0APC5 | Apr 14, 2016 | Android 5 | Feature | 0 | 1 | pulled |
J320MUBU0APC4 | Mar 27, 2016 | Android 5 | Feature | 0 | 11 | on server |
J320MUBU0APB4 | Mar 9, 2016 | Android 5 | Feature | 0 | 10 | pulled |
J320MUBU0APAC | Feb 11, 2016 | Android 5 | Feature | 0 | 13 | on server |
How to download SM-J320M 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-J320M -r TPAReplace TPA 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-J320M / TPA 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).