GALAXY Ace 2 GT-I8160L updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung GALAXY Ace 2 (GT-I8160L). The latest stable build is I8160LUBMK2 (Android 4, – update), first released on Jun 2, 2014. Samsung has published 18 stable builds for this model since May 25, 2012: 0 security and 0 feature updates, from Android 2 to Android 4. The current bootloader (binary) version is 30. A device on bit 30 only accepts firmware with bit 30 or higher – see downgrading and the bootloader bit.
Rollout: build I8160LUBMK2 (Android 4) is live in 1 of 8 regions, first released on Jun 2, 2014 in PGU (Guatemala). Still waiting: PBS, THL, TNZ, TPA, TTT, ZTA, ZVV.
- Latest build
I8160LUBMK2- Released
- Jun 2, 2014
- Android
- Android 4
- Bootloader bit
- 30
- Regions
- 8
- Stable builds
- 18
Update policy
The GALAXY Ace 2 no longer receives updates: the last firmware appeared on Jun 2, 2014, 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 |
|---|---|---|---|---|---|
PBS | Peru (Bitel) | I8160LVSLK1 | Android 2 | Dec 18, 2012 | 2 |
PGU | Guatemala | I8160LUBMK2 | Android 4 | Jun 2, 2014 | 2 |
THL | Thailand | I8160LDCME1 | Android 4 | Jun 26, 2013 | 5 |
TNZ | New Zealand (Spark) | I8160LDOMF1 | Android 4 | Jul 16, 2013 | 2 |
TPA | Panama | I8160LUBLL1 | Android 2 | Jun 2, 2013 | 1 |
TTT | Trinidad & Tobago | I8160LUBMC2 | Android 4 | Aug 20, 2013 | 4 |
ZTA | Brazil (Claro) | I8160LVJMJ1 | Android 4 | Nov 19, 2013 | 2 |
ZVV | Brazil (Vivo) | I8160LVJMJ1 | Android 4 | Nov 26, 2013 | 2 |
Firmware history (18 builds)
Every stable build (PDA version) Samsung has published for the GT-I8160L, 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 |
|---|---|---|---|---|---|---|
I8160LUBMK2 | Jun 2, 2014 | Android 4 | – | 30 | 1 | on server |
I8160LVJMJ1 | Nov 19, 2013 | Android 4 | – | 31 | 2 | on server |
I8160LUBMC2 | Aug 20, 2013 | Android 4 | – | 30 | 1 | on server |
I8160LDOMF1 | Jul 16, 2013 | Android 4 | – | 13 | 1 | on server |
I8160LDCME1 | Jun 26, 2013 | Android 4 | – | 13 | 1 | on server |
I8160LUBLL1 | Jun 2, 2013 | Android 2 | – | 30 | 1 | on server |
I8160LVSLK1 | Dec 18, 2012 | Android 2 | – | 31 | 1 | on server |
I8160LUBLK1 | Dec 18, 2012 | Android 2 | – | 30 | 1 | pulled |
I8160LDCLK2 | Nov 21, 2012 | Android 2 | – | 13 | 1 | pulled |
I8160LVSLH1 | Oct 8, 2012 | Android 2 | – | 31 | 1 | pulled |
I8160LVJLH1 | Sep 17, 2012 | Android 2 | – | 31 | 1 | pulled |
I8160LUBLE2 | Aug 24, 2012 | Android 2 | – | 30 | 1 | pulled |
I8160LVJLF3 | Aug 24, 2012 | Android 2 | – | 31 | 1 | pulled |
I8160LDCLH1 | Aug 23, 2012 | Android 2 | – | 13 | 1 | pulled |
I8160LUBLH1 | Aug 21, 2012 | Android 2 | – | 30 | 2 | pulled |
I8160LDCLF1 | Jun 28, 2012 | Android 2 | – | 13 | 1 | pulled |
I8160LDOLE3 | Jun 4, 2012 | Android 2 | – | 13 | 1 | pulled |
I8160LDCLE3 | May 25, 2012 | Android 2 | – | 13 | 1 | pulled |
How to download GT-I8160L 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 GT-I8160L -r THL
Replace THL 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 GT-I8160L / THL 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).