GALAXY J1 SM-J100F updates & firmware
This page tracks every software update Samsung's update servers list for the Samsung GALAXY J1 (SM-J100F). The latest stable build is J100FXXU0APB1 (Android 4, feature update), first released on Apr 25, 2016. Samsung has published 17 stable builds for this model since Jan 26, 2015: 0 security and 17 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 J100FXXU0APB1 (Android 4) is live in 1 of 7 regions, first released on Apr 25, 2016 in XSG (United Arab Emirates). Still waiting: AFG, AFR, ILO, KSA, PAK, TGY.
- Latest build
J100FXXU0APB1- Released
- Apr 25, 2016
- Android
- Android 4
- Bootloader bit
- 0
- Regions
- 7
- Stable builds
- 17
Update policy
The GALAXY J1 no longer receives updates: the last firmware appeared on Apr 25, 2016, 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 |
|---|---|---|---|---|---|
AFG | Afghanistan | J100FXXU0APA1 | Android 4 | Feb 25, 2016 | 6 |
AFR | Africa | J100FXXU0APA1 | Android 4 | Feb 25, 2016 | 6 |
ILO | Israel | J100FXXU0AOC3 | Android 4 | Nov 8, 2015 | 2 |
KSA | Saudi Arabia | J100FXXU0APA1 | Android 4 | Feb 25, 2016 | 7 |
PAK | Pakistan | J100FXXU0APA1 | Android 4 | Feb 25, 2016 | 7 |
TGY | Hong Kong | J100FZHU0AOI2 | Android 4 | Oct 11, 2015 | 2 |
XSG | United Arab Emirates | J100FXXU0APB1 | Android 4 | Apr 25, 2016 | 12 |
Firmware history (17 builds)
Every stable build (PDA version) Samsung has published for the SM-J100F, 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 |
|---|---|---|---|---|---|---|
J100FXXU0APB1 | Apr 25, 2016 | Android 4 | Feature | 0 | 1 | on server |
J100FXXU0APA1 | Feb 18, 2016 | Android 4 | Feature | 0 | 5 | on server |
J100FXXU0AOK1 | Dec 23, 2015 | Android 4 | Feature | 0 | 1 | pulled |
J100FXXU0AOC3 | Nov 8, 2015 | Android 4 | Feature | 0 | 1 | pulled |
J100FXXU0AOJ1 | Nov 8, 2015 | Android 4 | Feature | 0 | 1 | on server |
J100FXXU0AOJ2 | Oct 20, 2015 | Android 4 | Feature | 0 | 1 | pulled |
J100FXXU0AOI1 | Oct 12, 2015 | Android 4 | Feature | 0 | 4 | on server |
J100FZHU0AOI2 | Oct 11, 2015 | Android 4 | Feature | 0 | 1 | on server |
J100FXXU0AOH3 | Oct 1, 2015 | Android 4 | Feature | 0 | 1 | pulled |
J100FXXU0AOF1 | Jun 17, 2015 | Android 4 | Feature | 0 | 1 | pulled |
J100FXXU0AOE1 | May 28, 2015 | Android 4 | Feature | 0 | 4 | pulled |
J100FZHU0AOB4 | Mar 10, 2015 | Android 4 | Feature | 0 | 1 | pulled |
J100FXXU0AOC1 | Mar 10, 2015 | Android 4 | Feature | 0 | 5 | pulled |
J100FXXU0AOB5 | Feb 26, 2015 | Android 4 | Feature | 0 | 5 | pulled |
J100FXXU0AOB1 | Feb 9, 2015 | Android 4 | Feature | 0 | 5 | pulled |
J100FXXU0AOA8 | Feb 3, 2015 | Android 4 | Feature | 0 | 3 | pulled |
J100FXXU0AOA7 | Jan 26, 2015 | Android 4 | Feature | 0 | 2 | pulled |
How to download SM-J100F 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-J100F -r XSGReplace XSG 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-J100F / XSG 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).