(7,496 ratings)
App: FlashFire
Version: 0.28 (28)
armeabi-v7a + x86
af, am, ar, az, bg, bn, ca, cs, da, de, el, en, es, et, eu, fa, fi, fr, gl, gu, hi, hr, hu, hy, in... Show all
Package: eu.chainfire.flash
8.68 MB (9,096,697 bytes)
Min: Android 4.2 (Jelly Bean MR1, API 17)
Target: Android 5.0 (Lollipop, API 21)
Uploaded March 15, 2016 at 8:53PM UTC by Sruly J
Download APK
There's a more recent version available below!

Whoa there!

It looks like you're using an ad blocker, so you'll have to wait 15 more seconds.
Please add this site to your allowlist to skip the wait and help us pay for bandwidth, hosting, and other bills.

The release notes and changelogs are far too large to post here. Please see these links:
Release notes:
XDA discussion thread:

FlashFire is the spiritual successor to Mobile ODIN.

It's long overdue for release, but some i's still need to be dotted and some t's crossed. That being said, most of the functionality actually works well already, and it's pretty darned powerful. I have used it to update various Samsung devices from 4.x to 5.x, done (block-level!) OTAs on Nexus devices, etc.

If you're fairly tech-savvy and/or used to Mobile ODIN I suspect you won't have much trouble getting around with this app. Updates and the manual (which would be bloody useful, wouldn't it?) are coming over the next few days and weeks.

Notes and hints to help you use it:
- No kernels or recoveries are flashed for FlashFire to run, Android is torn down and restarted in a minimalist manner for the flashing part of the app to run. I'm sure this will completely fail on some devices.
- A lot(!) of memory is used, likely the entire operation will fail on low-memory devices. I strongly suggest you make an 'ID' backup as the very first test and see if that works at all.
- Technically it should be compatible with 4.2, but note virtually all of the testing so far has been done on 4.4 and 5.0 firmwares.
- SuperSU is required, unless you are running a CM-based ROM in permissive mode.
- While development has focused so far on Samsung and Nexus compatibility and features, it should be able to function on many devices. Specific support for some other manufacturers is coming via updates soon.
- Individual files need to be named correctly (after their partitions) to be flashable or be contained in archives. Archive-wise, TAR, ZIP, and various firmware-specific formats are supported. Compression-wise, ZIP, GZIP and BZIP2 are supported. These can be embedded inside each-other, so yes, you can directly flash the standard ZIP-inside-TGZ Nexus firmwares, as well as TAR-inside-ZIP Samsung firmwares. More formats are to come.
- Backups can be to internal, external (sd) or USB storage. The backups are compressed. There is no way of knowing if the backup will fit, you are not warned about this. (6.0 note: tested only on internal storage)
- Backups are TGZ or TLZ4 for file-based, and plain GZIP or LZ4 for raw partitions
- For block-level OTAs, flash a stock system partition or restore a (raw!) system (and vendor) backup before applying the OTA. After the OTA action, create a (raw!) backup of system (and vendor). The latter will be restorable to apply the next OTA.
- On systemless SuperSU roots, if you have not modified /system, FlashFire can often install the OTA update directly, and EverRoot after. Let your device download the update, but don't install it - instead, just open FlashFire, it should detect the OTA. (Tested on several Nexus devices)
- The embedded SuperSU version installed by EverRoot is v2.70 RC BETA

- Pro version is unlocked if you have Mobile ODIN Pro installed, but you still see an upgrade option. This is a (much cheaper) In-App Purchase you can optionally do, so you don't need to keep MOP installed.
- Pro version actually does nothing different at the moment.

In case of issues, immediately after rebooting back into Android:
- Post /sdcard/FlashFire/lastlog
- Post /proc/last_kmsg
The latter may not be present, and is replaced on every reboot. So if you rebooted twice, no sense posting it.

If you are ready to start messing around with it, this is how you get the BETA:
- Go to:
- Use the link provided on that page to download the app. Note that it may take minutes to even hours before the provided link actually works.

If you have no idea what any of the above means, you might want to wait with playing with this until proper instructions are available, and more people have tested it.

All versions
September 21, 2017
September 13, 2017
September 12, 2017
September 11, 2017
August 15, 2017
August 14, 2017
August 13, 2017
April 3, 2017
January 26, 2017
January 3, 2017