FlashFire v0.72 released
Posted on 2017-09-13, 6 comments, 114 +1's, imported from Google+/Chainfire

NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.

This update is currently rolling out on Google Play.

Another day, another update. Minutes after the release of v0.71 yesterday, two new OTAs were received on my 5X and PixelXL respectively. Both of these slightly different than the OTAs seen before (it would be nice if Google didn't reinvent the OTA system every other month...).

In case of the 5X, the problem was simply a different marker than previously seen that signaled OTA download completion. The fix was a one-liner.

The OTA for the Pixel (XL) however was of the new A/B streaming kind. While this type of OTA has been documented by Google already, I had never encountered one, and thus FlashFire did not support it. After some hours of coding this one works as well now, but with a sample-size of one we'll just have to see if it keeps working for the October update.

Additionally, some users noticed an issue with the Wipe action when doing a wipe of only the dalvik-cache. Some unrelated files were deleted by accident, which on some devices could cause FCs or even a boot-loop. This bug has been present since v0.58 and should now be corrected.

Further updates will be released once more Oreo-related issues have been identified and fixed :)


Google Play:


Direct Download:


Discussion thread on XDA:



  • OTA: Fix new style OTA-download-complete marker detection

  • A/B OTA: Add suppport for 'streaming' style OTAs

  • A/B OTA: Enable pre-mount by default (required for incremental A/B OTAs now)

  • Wipe: Fix dalvik-cache wipe greedily removing some files it shouldn't

[Android 4.2+][ROOT][2017.09.13] FlashFire v0.72

Murat YÜKSEL commented on 2017-09-13 at 11:48:

I installed flashfire around 13:00 (GMT+3) (actually time is 14:38 in here, and installing was around at 1,5 hour ago) and tried to NORMAL backup with SGN2-N7100. I don't know whether protection was on or off. Phone have been stucked at bootloader with Samsung logo by 20 minutes. Tried force to close and open, also tried pull battery off&on, still stucks. But when baterry plugs in, it opens automatically. (Phone is rooted but still in stock rom).

Edit: wiped cache in stock recovery and problem solved.

Hung Nguyen commented on 2017-09-15 at 21:54:

qua tuyet voi ok

Refik Gusseynov commented on 2017-09-19 at 06:57:

Türkçeye çevrilmesi yokmu

Gene Nyland commented on 2017-09-20 at 00:31:

Hi Chainfire, is flash fire still exclusive to Samsung devices?

Pedro Marques commented on 2017-09-22 at 16:37:

+Gene Nyland

I don't think it ever was. He evens says in this post his test devices are the 5X and PixelXL. I personally use the 5X, but I've been having troubles flashing incremental OTAs lately (since 7.1).

Iren Sholikudin commented on 2017-09-25 at 22:56:

Is very nice

This post is over a month old, commenting has been disabled.