GALAXY Tab3 Lite SM-T116NU updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung GALAXY Tab3 Lite (SM-T116NU). The latest stable build is T116NUXXU0AQJ1 (Android 4, feature update), first released on Nov 30, 2017. Samsung has published 15 stable builds for this model since Jan 20, 2015: 1 security and 14 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 T116NUXXU0AQJ1 (Android 4) is live in 1 of 9 regions, first released on Nov 30, 2017 in LAO (Laos). Still waiting: BNG, CAM, SLK, THL, XID, XME, XTC, XXV.
- Latest build
T116NUXXU0AQJ1- Released
- Nov 30, 2017
- Android
- Android 4
- Bootloader bit
- 0
- Regions
- 9
- Stable builds
- 15
Update policy
The GALAXY Tab3 Lite no longer receives updates: the last firmware appeared on Nov 30, 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 |
|---|---|---|---|---|---|
BNG | Belgium | T116NUXXU0AQC2 | Android 4 | May 21, 2017 | 6 |
CAM | Cambodia | T116NUXXS0AQB2 | Android 4 | Mar 6, 2017 | 8 |
LAO | Laos | T116NUXXU0AQJ1 | Android 4 | Nov 30, 2017 | 1 |
SLK | Sri Lanka | T116NUXXU0AQC2 | Android 4 | May 21, 2017 | 6 |
THL | Thailand | T116NUXXU0AQC2 | Android 4 | Sep 17, 2017 | 9 |
XID | Indonesia | T116NUXXS0AQB2 | Android 4 | Mar 6, 2017 | 7 |
XME | Malaysia | T116NUXXS0AQB2 | Android 4 | Mar 6, 2017 | 10 |
XTC | Philippines | T116NUXXU0AQC2 | Android 4 | May 29, 2017 | 6 |
XXV | Vietnam | T116NUXXS0AQB2 | Android 4 | Mar 6, 2017 | 9 |
Firmware history (15 builds)
Every stable build (PDA version) Samsung has published for the SM-T116NU, 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 |
|---|---|---|---|---|---|---|
T116NUXXU0AQJ1 | Nov 30, 2017 | Android 4 | Feature | 0 | 1 | on server |
T116NUXXU0AQC2 | May 21, 2017 | Android 4 | Feature | 0 | 4 | on server |
T116NUXXS0AQB2 | Mar 6, 2017 | Android 4 | Security | 0 | 6 | on server |
T116NUXXU0AQA1 | Feb 6, 2017 | Android 4 | Feature | 0 | 8 | on server |
T116NUXXU0APH4 | Sep 26, 2016 | Android 4 | Feature | 0 | 8 | pulled |
T116NUXXU0APH1 | Aug 24, 2016 | Android 4 | Feature | 0 | 6 | pulled |
T116NUXXU0APE1 | Jul 27, 2016 | Android 4 | Feature | 0 | 2 | pulled |
T116NUXXU0AOL3 | Jan 12, 2016 | Android 4 | Feature | 0 | 1 | pulled |
T116NUXXU0AOE1 | Jun 7, 2015 | Android 4 | Feature | 0 | 4 | pulled |
T116NUXXU0AOD1 | May 12, 2015 | Android 4 | Feature | 0 | 2 | pulled |
T116NUXXU0AOC2 | Apr 2, 2015 | Android 4 | Feature | 0 | 7 | pulled |
T116NUXXU0AOC1 | Mar 18, 2015 | Android 4 | Feature | 0 | 5 | pulled |
T116NUXXU0AOB4 | Feb 23, 2015 | Android 4 | Feature | 0 | 2 | pulled |
T116NUXXU0AOB5 | Feb 17, 2015 | Android 4 | Feature | 0 | 4 | pulled |
T116NUXXU0AOA5 | Jan 20, 2015 | Android 4 | Feature | 0 | 2 | pulled |
How to download SM-T116NU 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-T116NU -r XMEReplace XME 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-T116NU / XME 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).