GALAXY CORE2 SM-G355M updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung GALAXY CORE2 (SM-G355M). The latest stable build is G355MUBS0AQB4 (Android 4, security update), first released on May 21, 2017. Samsung has published 59 stable builds for this model since Jun 11, 2014: 23 security and 36 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 G355MUBS0AQB4 (Android 4) is live in 1 of 26 regions, first released on May 21, 2017 in CGU (Guatemala (Claro)). Still waiting: ARO, BVO, CHE, CHL, CHO, CHT, COL, COM, COO, CRC, CTI, NBS, PBS, PET and 11 more.
- Latest build
G355MUBS0AQB4- Released
- May 21, 2017
- Android
- Android 4
- Bootloader bit
- 0
- Regions
- 26
- Stable builds
- 59
Update policy
The GALAXY CORE2 no longer receives updates: the last firmware appeared on May 21, 2017, 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 |
|---|---|---|---|---|---|
ARO | Argentina | G355MUBS0AQA3 | Android 4 | Jan 24, 2017 | 10 |
BVO | Bolivia | G355MUBS0AQA3 | Android 4 | Jan 24, 2017 | 11 |
CGU | Guatemala (Claro) | G355MUBS0AQB4 | Android 4 | May 21, 2017 | 3 |
CHE | Chile (Entel) | G355MUBS0APH4 | Android 4 | Nov 24, 2016 | 4 |
CHL | Chile (Claro) | G355MUBS0AQA9 | Android 4 | Feb 5, 2017 | 3 |
CHO | Chile | G355MUBS0AQA6 | Android 4 | Jan 23, 2017 | 9 |
CHT | Chile (Movistar) | G355MUBS0AQA9 | Android 4 | Feb 12, 2017 | 7 |
COL | Colombia | G355MUBS0AQA4 | Android 4 | Feb 2, 2017 | 7 |
COM | Colombia (Claro) | G355MUBS0AQB2 | Android 4 | Apr 12, 2017 | 1 |
COO | Colombia | G355MUBS0AQA3 | Android 4 | Jan 24, 2017 | 10 |
CRC | Costa Rica | G355MUBS0AQB3 | Android 4 | Apr 12, 2017 | 1 |
CTI | Argentina (Claro) | G355MUBS0AQA2 | Android 4 | Feb 7, 2017 | 9 |
NBS | Latin America (open market) | G355MUBS0AQA2 | Android 4 | Feb 2, 2017 | 4 |
PBS | Peru (Bitel) | G355MUBS0AQA2 | Android 4 | Feb 5, 2017 | 5 |
PET | Peru (Movistar) | G355MUBS0AQB7 | Android 4 | Apr 12, 2017 | 2 |
PGU | Guatemala | G355MUBS0AQB5 | Android 4 | Apr 12, 2017 | 4 |
PNT | Panama | G355MUBS0AQA2 | Android 4 | Feb 2, 2017 | 6 |
PSN | Argentina (Personal) | G355MUBS0AQA7 | Android 4 | Feb 2, 2017 | 7 |
TCE | Mexico (Telcel) | G355MUBS0AQA2 | Android 4 | Feb 5, 2017 | 11 |
TPA | Panama | G355MUBS0AQA3 | Android 4 | Jan 24, 2017 | 11 |
TTT | Trinidad & Tobago | G355MUBS0AQA3 | Android 4 | Jan 24, 2017 | 13 |
UFN | Argentina (Movistar) | G355MUBS0AQA2 | Android 4 | Feb 13, 2017 | 8 |
UPO | Uruguay | G355MUBS0AQA3 | Android 4 | Jan 24, 2017 | 10 |
ZTA | Brazil (Claro) | G355MUBS0AQA2 | Android 4 | Feb 5, 2017 | 6 |
ZTO | Brazil | G355MUBU0AQB1 | Android 4 | Mar 21, 2017 | 12 |
ZTR | Brazil (Oi) | G355MUBS0AQA2 | Android 4 | Feb 12, 2017 | 7 |
Firmware history (59 builds)
Every stable build (PDA version) Samsung has published for the SM-G355M, 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 |
|---|---|---|---|---|---|---|
G355MUBS0AQB4 | May 21, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0AQB5 | Apr 12, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0AQB2 | Apr 12, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0AQB3 | Apr 12, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0AQB7 | Apr 12, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBU0AQB1 | Mar 21, 2017 | Android 4 | Feature | 0 | 1 | on server |
G355MUBS0AQA9 | Feb 5, 2017 | Android 4 | Security | 0 | 2 | on server |
G355MUBS0AQA4 | Feb 2, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0AQA7 | Feb 2, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0AQA2 | Feb 2, 2017 | Android 4 | Security | 0 | 8 | on server |
G355MUBS0AQA3 | Jan 24, 2017 | Android 4 | Security | 0 | 6 | on server |
G355MUBS0AQA6 | Jan 23, 2017 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0APL5 | Dec 28, 2016 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0APL4 | Dec 21, 2016 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0APL2 | Dec 21, 2016 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0APL1 | Dec 20, 2016 | Android 4 | Security | 0 | 6 | on server |
G355MUBS0APH4 | Nov 24, 2016 | Android 4 | Security | 0 | 1 | on server |
G355MUBU0API2 | Nov 17, 2016 | Android 4 | Feature | 0 | 1 | on server |
G355MUBS0API2 | Oct 9, 2016 | Android 4 | Security | 0 | 1 | on server |
G355MUBS0APH5 | Sep 19, 2016 | Android 4 | Security | 0 | 1 | pulled |
G355MUBS0APH6 | Sep 18, 2016 | Android 4 | Security | 0 | 1 | pulled |
G355MUBS0APH1 | Sep 6, 2016 | Android 4 | Security | 0 | 6 | pulled |
G355MUBS0APH2 | Sep 6, 2016 | Android 4 | Security | 0 | 8 | on server |
G355MUBU0APE2 | Aug 18, 2016 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBS0APE4 | Jul 25, 2016 | Android 4 | Security | 0 | 5 | pulled |
G355MUBU0APE3 | Jul 12, 2016 | Android 4 | Feature | 0 | 1 | on server |
G355MUBU0APF1 | Jul 5, 2016 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0APF2 | Jun 30, 2016 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBS0APE3 | Jun 14, 2016 | Android 4 | Security | 0 | 6 | pulled |
G355MUBU0AOI2 | Nov 8, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0AOI4 | Oct 11, 2015 | Android 4 | Feature | 0 | 17 | on server |
G355MUBU0AOI1 | Oct 11, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0AOH1 | Aug 26, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0AOG2 | Aug 5, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0AOF4 | Jul 1, 2015 | Android 4 | Feature | 0 | 4 | pulled |
G355MUBU0AOF3 | Jun 24, 2015 | Android 4 | Feature | 0 | 3 | pulled |
G355MUBU0AOF1 | Jun 14, 2015 | Android 4 | Feature | 0 | 3 | pulled |
G355MUBU0AOC5 | Apr 2, 2015 | Android 4 | Feature | 0 | 12 | pulled |
G355MUBU0AOB2 | Mar 1, 2015 | Android 4 | Feature | 0 | 10 | pulled |
G355MUBU0AOB3 | Feb 25, 2015 | Android 4 | Feature | 0 | 3 | pulled |
G355MUBU0AOA2 | Feb 4, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0AOA1 | Jan 26, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0ANL3 | Jan 9, 2015 | Android 4 | Feature | 0 | 2 | pulled |
G355MUBU0ANH1 | Jan 7, 2015 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0ANK2 | Dec 22, 2014 | Android 4 | Feature | 0 | 2 | pulled |
G355MUBU0ANL2 | Dec 19, 2014 | Android 4 | Feature | 0 | 4 | pulled |
G355MUBU0ANJ4 | Dec 2, 2014 | Android 4 | Feature | 0 | 2 | pulled |
G355MUBU0ANK1 | Nov 20, 2014 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0ANI7 | Nov 4, 2014 | Android 4 | Feature | 0 | 3 | pulled |
G355MUBU0ANJ1 | Oct 28, 2014 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0ANJ3 | Oct 28, 2014 | Android 4 | Feature | 0 | 3 | pulled |
G355MUBU0ANI5 | Oct 7, 2014 | Android 4 | Feature | 0 | 8 | pulled |
G355MUBU0ANI6 | Oct 1, 2014 | Android 4 | Feature | 0 | 2 | pulled |
G355MUBU0ANH5 | Sep 17, 2014 | Android 4 | Feature | 0 | 3 | pulled |
G355MUBU0ANG3 | Aug 21, 2014 | Android 4 | Feature | 0 | 7 | pulled |
G355MUBU0ANF7 | Jun 26, 2014 | Android 4 | Feature | 0 | 9 | pulled |
G355MUBU0ANF4 | Jun 23, 2014 | Android 4 | Feature | 0 | 3 | pulled |
G355MUBU0ANF6 | Jun 23, 2014 | Android 4 | Feature | 0 | 1 | pulled |
G355MUBU0ANF1 | Jun 11, 2014 | Android 4 | Feature | 0 | 3 | pulled |
How to download SM-G355M 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-G355M -r TTTReplace TTT 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-G355M / TTT 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).