GALAXY CORE LTE Prime SM-G360M updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung GALAXY CORE LTE Prime (SM-G360M). The latest stable build is G360MVJS1BSA1 (Android 5, security update), first released on Mar 3, 2019. Samsung has published 52 stable builds for this model since Jan 21, 2015: 29 security and 23 feature updates, from Android 4 to Android 5. The current bootloader (binary) version is 1. A device on bit 1 only accepts firmware with bit 1 or higher – see downgrading and the bootloader bit.
Rollout: build G360MVJS1BSA1 (Android 5) is live in 1 of 21 regions, first released on Mar 3, 2019 in ZTR (Brazil (Oi)). Still waiting: ARO, CGU, CHX, COB, COL, COM, COO, CRC, CTI, NBS, PET, PGU, PNT, PSN and 6 more.
- Latest build
G360MVJS1BSA1- Released
- Mar 3, 2019
- Android
- Android 5
- Bootloader bit
- 1
- Regions
- 21
- Stable builds
- 52
Update policy
The GALAXY CORE LTE Prime no longer receives updates: the last firmware appeared on Mar 3, 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 | G360MUBS1BRH1 | Android 5 | Dec 17, 2018 | 9 |
CGU | Guatemala (Claro) | G360MUBS1AQB2 | Android 4 | May 21, 2017 | 3 |
CHX | Chile | G360MUBU1BPI2 | Android 5 | Nov 3, 2016 | 4 |
COB | Colombia (Movistar) | G360MUBS1BRH3 | Android 5 | Feb 7, 2019 | 6 |
COL | Colombia | G360MUBS1AQB2 | Android 4 | Apr 2, 2017 | 7 |
COM | Colombia (Claro) | G360MUBS1BRH4 | Android 5 | Oct 10, 2018 | 5 |
COO | Colombia | G360MUBS1BRH1 | Android 5 | Dec 20, 2018 | 10 |
CRC | Costa Rica | G360MUBS1AQB1 | Android 4 | Apr 13, 2017 | 3 |
CTI | Argentina (Claro) | G360MUBS1AQB3 | Android 4 | Apr 5, 2017 | 6 |
NBS | Latin America (open market) | G360MUBS1AQB3 | Android 4 | Mar 8, 2017 | 4 |
PET | Peru (Movistar) | G360MUBS1AQB3 | Android 4 | Mar 14, 2017 | 7 |
PGU | Guatemala | G360MUBS1AQB1 | Android 4 | Apr 13, 2017 | 3 |
PNT | Panama | G360MUBS1BRH3 | Android 5 | Dec 17, 2018 | 8 |
PSN | Argentina (Personal) | G360MUBS1BRJ2 | Android 5 | Dec 20, 2018 | 6 |
SAM | Oceania | G360MUBS1AQB3 | Android 4 | Mar 8, 2017 | 4 |
TPA | Panama | G360MUBS1BRH1 | Android 5 | Sep 26, 2018 | 10 |
TTT | Trinidad & Tobago | G360MUBS1BRH1 | Android 5 | Sep 26, 2018 | 11 |
UFN | Argentina (Movistar) | G360MUBS1BQB4 | Android 5 | Apr 10, 2017 | 6 |
ZTA | Brazil (Claro) | G360MVJS1BSA2 | Android 5 | Feb 24, 2019 | 6 |
ZTR | Brazil (Oi) | G360MVJS1BSA1 | Android 5 | Mar 3, 2019 | 9 |
ZVV | Brazil (Vivo) | G360MVJU1BPI2 | Android 5 | Oct 25, 2016 | 5 |
Firmware history (52 builds)
Every stable build (PDA version) Samsung has published for the SM-G360M, 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 |
|---|---|---|---|---|---|---|
G360MVJS1BSA1 | Mar 3, 2019 | Android 5 | Security | 1 | 1 | on server |
G360MVJS1BSA2 | Feb 24, 2019 | Android 5 | Security | 1 | 1 | on server |
G360MUBS1BRJ2 | Dec 20, 2018 | Android 5 | Security | 1 | 1 | on server |
G360MUBS1BRH3 | Dec 17, 2018 | Android 5 | Security | 1 | 2 | on server |
G360MUBS1BRH4 | Oct 10, 2018 | Android 5 | Security | 1 | 1 | on server |
G360MUBS1BRH1 | Sep 26, 2018 | Android 5 | Security | 1 | 4 | on server |
G360MUBU1BQC1 | May 21, 2017 | Android 5 | Feature | 1 | 1 | on server |
G360MUBS1AQB1 | Apr 13, 2017 | Android 4 | Security | 1 | 2 | on server |
G360MUBS1BQB5 | Apr 13, 2017 | Android 5 | Security | 1 | 1 | on server |
G360MVJS1BQB1 | Apr 13, 2017 | Android 5 | Security | 1 | 1 | on server |
G360MUBS1BQB4 | Apr 10, 2017 | Android 5 | Security | 1 | 1 | on server |
G360MUBS1AQB2 | Apr 2, 2017 | Android 4 | Security | 1 | 2 | on server |
G360MVJS1BQB2 | Mar 28, 2017 | Android 5 | Security | 1 | 1 | on server |
G360MUBU1BPL1 | Mar 14, 2017 | Android 5 | Feature | 1 | 1 | on server |
G360MUBS1BQB3 | Mar 13, 2017 | Android 5 | Security | 1 | 2 | on server |
G360MUBS1AQB3 | Mar 8, 2017 | Android 4 | Security | 1 | 4 | on server |
G360MUBS1BQB2 | Mar 8, 2017 | Android 5 | Security | 1 | 4 | on server |
G360MUBS1AQA1 | Feb 5, 2017 | Android 4 | Security | 1 | 2 | on server |
G360MUBS1BQA3 | Feb 1, 2017 | Android 5 | Security | 1 | 1 | pulled |
G360MUBS1AQA4 | Feb 1, 2017 | Android 4 | Security | 1 | 4 | on server |
G360MUBS1BPL1 | Jan 31, 2017 | Android 5 | Security | 1 | 1 | pulled |
G360MUBS1BQA4 | Jan 31, 2017 | Android 5 | Security | 1 | 1 | pulled |
G360MUBS1AQA2 | Jan 25, 2017 | Android 4 | Security | 1 | 1 | on server |
G360MVJS1BPK1 | Dec 19, 2016 | Android 5 | Security | 1 | 1 | pulled |
G360MUBU1BPK1 | Dec 1, 2016 | Android 5 | Feature | 1 | 4 | pulled |
G360MUBS1APJ2 | Nov 7, 2016 | Android 4 | Security | 1 | 1 | pulled |
G360MVJU1BPI2 | Oct 25, 2016 | Android 5 | Feature | 1 | 2 | on server |
G360MUBS1APH1 | Oct 9, 2016 | Android 4 | Security | 1 | 2 | pulled |
G360MUBU1BPI2 | Sep 22, 2016 | Android 5 | Feature | 1 | 7 | on server |
G360MVJU1BPH1 | Sep 6, 2016 | Android 5 | Feature | 1 | 1 | pulled |
G360MUBS1APF1 | Aug 6, 2016 | Android 4 | Security | 1 | 1 | pulled |
G360MUBS1BPE1 | Jul 24, 2016 | Android 5 | Security | 1 | 1 | pulled |
G360MUBS1APE4 | Jul 20, 2016 | Android 4 | Security | 1 | 2 | pulled |
G360MUBS1BPE2 | Jul 20, 2016 | Android 5 | Security | 1 | 4 | pulled |
G360MUBU1BPF1 | Jul 13, 2016 | Android 5 | Feature | 1 | 1 | pulled |
G360MVJU1BPF1 | Jul 7, 2016 | Android 5 | Feature | 1 | 2 | on server |
G360MUBU1BPE3 | Jul 3, 2016 | Android 5 | Feature | 1 | 2 | on server |
G360MVJS1BPE2 | Jul 1, 2016 | Android 5 | Security | 1 | 1 | pulled |
G360MUBU1BPE1 | May 27, 2016 | Android 5 | Feature | 1 | 1 | pulled |
G360MVJU1BPC2 | May 9, 2016 | Android 5 | Feature | 1 | 1 | pulled |
G360MUBU1BPC2 | Apr 20, 2016 | Android 5 | Feature | 1 | 4 | pulled |
G360MUBU1AOI3 | Mar 16, 2016 | Android 4 | Feature | 1 | 2 | on server |
G360MUBU1BPB2 | Mar 7, 2016 | Android 5 | Feature | 1 | 5 | pulled |
G360MUBU1AOI4 | Oct 28, 2015 | Android 4 | Feature | 1 | 5 | pulled |
G360MVJU1AOI3 | Oct 12, 2015 | Android 4 | Feature | 1 | 1 | pulled |
G360MUBU1BOG1 | Jul 30, 2015 | Android 5 | Feature | 1 | 6 | pulled |
G360MVJU1AOE1 | Jul 1, 2015 | Android 4 | Feature | 1 | 2 | pulled |
G360MUBU1AOE1 | May 26, 2015 | Android 4 | Feature | 1 | 7 | pulled |
G360MUBU1AOB1 | Mar 24, 2015 | Android 4 | Feature | 1 | 8 | pulled |
G360MVJU1AOA2 | Feb 12, 2015 | Android 4 | Feature | 1 | 3 | pulled |
G360MUBU1AOA1 | Feb 11, 2015 | Android 4 | Feature | 1 | 4 | pulled |
G360MUBU1ANL5 | Jan 21, 2015 | Android 4 | Feature | 1 | 8 | pulled |
How to download SM-G360M 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-G360M -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-G360M / 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).