GALAXY ACE4 SM-G313M updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung GALAXY ACE4 (SM-G313M). The latest stable build is G313MUBU0AOI1 (Android 4, feature update), first released on Oct 25, 2015. Samsung has published 9 stable builds for this model since Aug 5, 2014: 0 security and 9 feature updates, from Android 4 to Android 4. 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 G313MUBU0AOI1 (Android 4) is live in 5 of 14 regions, first released on Oct 25, 2015 in TPA (Panama). Still waiting: CGU, CHL, CHT, COL, PBS, PNT, PSN, TCE, TMM.
- Latest build
G313MUBU0AOI1- Released
- Oct 25, 2015
- Android
- Android 4
- Bootloader bit
- 0
- Regions
- 15
- Stable builds
- 9
Update policy
The GALAXY ACE4 no longer receives updates: the last firmware appeared on Oct 25, 2015, on Android 4.
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 |
|---|---|---|---|---|---|
CGU | Guatemala (Claro) | G313MUBU0ANH1 | Android 4 | Sep 2, 2014 | 1 |
CHL | Chile (Claro) | G313MUBU0ANH1 | Android 4 | Sep 22, 2014 | 1 |
CHT | Chile (Movistar) | G313MUBU0ANH1 | Android 4 | Sep 22, 2014 | 1 |
COL | Colombia | G313MUBU0ANI2 | Android 4 | Oct 5, 2014 | 1 |
PBS | Peru (Bitel) | G313MUBU0ANK2 | Android 4 | Feb 4, 2015 | 1 |
PNT | Panama | G313MUBU0ANG5 | Android 4 | Aug 13, 2014 | 1 |
PSN | Argentina (Personal) | G313MUBU0ANH1 | Android 4 | Dec 10, 2014 | 1 |
TCE | Mexico (Telcel) | G313MUBU0AOI2 | Android 4 | Oct 19, 2015 | 3 |
TGP | Paraguay | G313MUBU0AOI1 | Android 4 | Nov 15, 2015 | 3 |
TMM | Myanmar | G313MUBU0ANK2 | Android 4 | Dec 1, 2014 | 1 |
TPA | Panama | G313MUBU0AOI1 | Android 4 | Oct 25, 2015 | 4 |
TTT | Trinidad & Tobago | G313MUBU0AOI1 | Android 4 | Oct 25, 2015 | 3 |
UPO | Uruguay | G313MUBU0AOI1 | Android 4 | Oct 25, 2015 | 3 |
ZTA | Brazil (Claro) | G313MUBU0AOI2 | Android 4 | Dec 23, 2015 | 2 |
ZTO | Brazil | G313MUBU0AOI1 | Android 4 | Oct 25, 2015 | 3 |
Firmware history (9 builds)
Every stable build (PDA version) Samsung has published for the SM-G313M, 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 |
|---|---|---|---|---|---|---|
G313MUBU0AOI1 | Oct 25, 2015 | Android 4 | Feature | 0 | 5 | on server |
G313MUBU0AOI2 | Oct 19, 2015 | Android 4 | Feature | 0 | 2 | on server |
G313MUBU0AOD1 | Jun 28, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G313MUBU0ANK2 | Nov 25, 2014 | Android 4 | Feature | 0 | 8 | on server |
G313MUBU0ANK1 | Nov 17, 2014 | Android 4 | Feature | 0 | 1 | pulled |
G313MUBU0ANI2 | Oct 5, 2014 | Android 4 | Feature | 0 | 2 | on server |
G313MUBU0ANH1 | Sep 2, 2014 | Android 4 | Feature | 0 | 5 | on server |
G313MUBU0ANG5 | Aug 13, 2014 | Android 4 | Feature | 0 | 1 | on server |
G313MUBU0ANG4 | Aug 5, 2014 | Android 4 | Feature | 0 | 4 | pulled |
How to download SM-G313M 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-G313M -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-G313M / 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).