GALAXY E7 SM-E700H updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung GALAXY E7 (SM-E700H). The latest stable build is E700HXXS1BRK2 (Android 5, security update), first released on Dec 28, 2018. Samsung has published 31 stable builds for this model since Jan 6, 2015: 7 security and 24 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 E700HXXS1BRK2 (Android 5) is live in 6 of 21 regions, first released on Dec 28, 2018 in XFE (South Africa). Still waiting: BNG, CAM, CHO, GLB, INS, KSA, MID, MWD, SMA, TPA, XID, XME, XTC, XTE and 1 more. In India (INS) the latest official firmware (flash file) is E700HXXU1BPL3 from May 11, 2017.
- Latest build
E700HXXS1BRK2- Released
- Dec 28, 2018
- Android
- Android 5
- Bootloader bit
- 1
- Regions
- 21
- Stable builds
- 31
Update policy
The GALAXY E7 no longer receives updates: the last firmware appeared on Dec 28, 2018, 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 |
|---|---|---|---|---|---|
AFR | Africa | E700HXXS1BRK2 | Android 5 | Dec 28, 2018 | 6 |
BNG | Belgium | E700HXXU1BPL3 | Android 5 | May 11, 2017 | 5 |
CAM | Cambodia | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
CHO | Chile | E700HXXS1BRI2 | Android 5 | Dec 5, 2018 | 5 |
EGY | Egypt | E700HXXS1BRK2 | Android 5 | Dec 28, 2018 | 6 |
GLB | Philippines (Globe) | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
INS | India | E700HXXU1BPL3 | Android 5 | May 11, 2017 | 9 |
KSA | Saudi Arabia | E700HXXS1BRK1 | Android 5 | Dec 28, 2018 | 7 |
LYS | Libya | E700HXXS1BRK2 | Android 5 | Dec 28, 2018 | 5 |
MID | Middle East | E700HXXU1AOD4 | Android 4 | May 14, 2015 | 1 |
MWD | Morocco | E700HXXS1BRK1 | Android 5 | Dec 28, 2018 | 7 |
SMA | Philippines | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
THR | Iran | E700HXXS1BRK2 | Android 5 | Dec 28, 2018 | 6 |
TPA | Panama | E700HXXS1BRI1 | Android 5 | Nov 11, 2018 | 6 |
TUN | Tunisia | E700HXXS1BRK2 | Android 5 | Dec 28, 2018 | 5 |
XFE | South Africa | E700HXXS1BRK2 | Android 5 | Dec 28, 2018 | 5 |
XID | Indonesia | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
XME | Malaysia | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
XTC | Philippines | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
XTE | Philippines (Smart) | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
XXV | Vietnam | E700HXXS1BQA1 | Android 5 | Mar 15, 2017 | 4 |
Firmware history (31 builds)
Every stable build (PDA version) Samsung has published for the SM-E700H, 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 |
|---|---|---|---|---|---|---|
E700HXXS1BRK2 | Dec 28, 2018 | Android 5 | Security | 1 | 6 | on server |
E700HXXS1BRK1 | Dec 28, 2018 | Android 5 | Security | 1 | 2 | on server |
E700HXXS1BRI2 | Dec 5, 2018 | Android 5 | Security | 1 | 1 | on server |
E700HXXS1BRI1 | Nov 11, 2018 | Android 5 | Security | 1 | 1 | on server |
E700HXXU1BPL3 | May 11, 2017 | Android 5 | Feature | 1 | 2 | on server |
E700HXXS1BQC1 | Apr 25, 2017 | Android 5 | Security | 1 | 2 | on server |
E700HXXS1BQA1 | Mar 15, 2017 | Android 5 | Security | 1 | 8 | on server |
E700HXXS1BPL3 | Feb 22, 2017 | Android 5 | Security | 1 | 6 | on server |
E700HXXU1BQA1 | Feb 6, 2017 | Android 5 | Feature | 1 | 1 | on server |
E700HXXU1BPL5 | Jan 23, 2017 | Android 5 | Feature | 1 | 1 | on server |
E700HXXU1BPH2 | Sep 13, 2016 | Android 5 | Feature | 1 | 2 | on server |
E700HXXU1BPC2 | Apr 3, 2016 | Android 5 | Feature | 1 | 1 | pulled |
E700HXXU1BPB3 | Mar 6, 2016 | Android 5 | Feature | 1 | 1 | pulled |
E700HXXU1BPA2 | Feb 11, 2016 | Android 5 | Feature | 1 | 6 | pulled |
E700HXXU1BPA1 | Jan 25, 2016 | Android 5 | Feature | 1 | 8 | on server |
E700HXXU1BOL1 | Dec 21, 2015 | Android 5 | Feature | 1 | 4 | pulled |
E700HXXU1BOJ7 | Nov 9, 2015 | Android 5 | Feature | 1 | 1 | pulled |
E700HXXU1AOI2 | Sep 24, 2015 | Android 4 | Feature | 1 | 2 | pulled |
E700HXXU1AOE5 | Jul 28, 2015 | Android 4 | Feature | 1 | 4 | pulled |
E700HXXU1AOE4 | Jun 1, 2015 | Android 4 | Feature | 1 | 1 | pulled |
E700HXXU1AOE3 | May 28, 2015 | Android 4 | Feature | 1 | 1 | pulled |
E700HXXU1AOD6 | May 10, 2015 | Android 4 | Feature | 1 | 2 | pulled |
E700HXXU1AOD5 | May 6, 2015 | Android 4 | Feature | 1 | 4 | pulled |
E700HXXU1AOD4 | May 1, 2015 | Android 4 | Feature | 1 | 8 | on server |
E700HXXU1AOAC | Feb 3, 2015 | Android 4 | Feature | 1 | 2 | pulled |
E700HXXU1AOAD | Jan 26, 2015 | Android 4 | Feature | 1 | 2 | pulled |
E700HXXU1AOAB | Jan 26, 2015 | Android 4 | Feature | 1 | 8 | pulled |
E700HXXU1AOAA | Jan 22, 2015 | Android 4 | Feature | 1 | 8 | pulled |
E700HXXU1AOA6 | Jan 22, 2015 | Android 4 | Feature | 1 | 2 | pulled |
E700HXXU1ANLE | Jan 7, 2015 | Android 4 | Feature | 1 | 1 | pulled |
E700HXXU1ANLD | Jan 6, 2015 | Android 4 | Feature | 1 | 5 | pulled |
How to download SM-E700H 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-E700H -r INSReplace INS 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-E700H / INS 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).