yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] Ch3vr0n:
No, as stated only a couple posts ago again. Flashfire will need update to support the new N format. [MENTION=631273]Chainfire[/MENTION] is working on it. Until then simply download the OTA manually flashfire will see that zip file just fine.
[Paid Software Announcement and Discussion] rybshik:
Backups page does NOT list backup(s) on SD card

I have (successfully) installed version v0.53 on my rooted Moto G4 Play (with unlocked BL). As advised, I tested with ID backup. So it creates files 'modem1.lz4', 'modem1.md5', 'modem2.lz4', 'modem2.md5'.

When internal storage is selected for a backup, everything seems to work as expected, although I have not attempted restore :)

When SD card is selected, the files are created, too and stored in folder " SD_Card:\FlashFire\Backups\201612260159-ID-MPI24.241-15.3".

But the the app's Backups page does NOT list the backup(s) and I do not see how I can select them for Restore.

My 64Gb SD card is set/formatted as "Portable storage" (not as "internal"). Android 6.0.1.

UPDATE: Instead of 64 GB, I tried a 32Gb SD card and it worked! Now FF does see/list the backup(s) on SD

The phone manufacturer claims "up to 128 GB microSD Card support" though
[Paid Software Announcement and Discussion] Bright.Light:
So I cannot use flashfire to update my rooted S7 with OTA.

I notices FF doesn't find the update.zip in fota automatically, so I moved it to external card. Stil the update.zip isn't recognised by FF!

I bought the app for nothing... Damn. It wasn't cheap either (edit: got my money back, thanks)

Please state this at the beginning of the thread too.
[Paid Software Announcement and Discussion] jeepcook:
When sdcard have not enough space to backup partitions, the process stop without any error messages, and reboot the system.

Edit: in fact we are unable to have more than one backup in external sdcard.. If one is available, flashfire crash
[Paid Software Announcement and Discussion] rybshik:
md5 batch verification utility for FF backups

Can anyone point me to a md5 batch verification utility suitable for verification of FF backups? For Win-7 as well as Android. Thanks!

The MD-5 utilities I know of use an *.md5 file, which contains both: checksum and file name. For example, for firmware file 'modem1.lz4', the corresponding 'modem1.md5' will contain a string "a6346497ba3028298096a7f2e0c5654e *modem1.lz4".

FlashFire check-sum files *.md5 only have checksum and do not contain filename portion.
[Paid Software Announcement and Discussion] rybshik:
So far, I have created 3 backups on (32Gb) SD-card. See my earlier post.
[Paid Software Announcement and Discussion] jeepcook:
I can too ... but I have to move existing backup to another folder so backups folder is empty and finally process works .. So I think it's a alpha release app, I made a lot of tests but back to my previous app to backup and flash.
[Paid Software Announcement and Discussion] rybshik:
I do not have to move anything. Just created one-by-one. All the three are in the original folder.

I have not tried to restore though. Scary :)
[Paid Software Announcement and Discussion] jeepcook:
So it's a random functioning... works for you but not for me !!

I tried the restore process by installing the twrp.zip, and it works. I really think this app will be great after some issue fix and by adding options (default backup folder, default zip location ....)
[Paid Software Announcement and Discussion] rybshik:
Did you mean that you restored your FireFlash backup using "TWRP Install ZIP" (without FireFlash app itself)?

Did you restore "Normal" or "Full" backup?
[Paid Software Announcement and Discussion] jeepcook:
Yes by installing twrp.zip without flashfire but with twrp recovery. I made a normal backup before with flashfire (boot, recovery, system, data gzip compressed). It's the emergency process.. I don't test restore with flashfire, it's not necessary for me, when I want to restore a backup I always use recovery.

edit: more info here https://flashfire.chainfire.eu/actions/backup/
[Paid Software Announcement and Discussion] rybshik:
So what is the advantage of such combined emergency FireFlash+TWRP backup/restore process over just using TWRP alone (for both backing up and restoring) ?
[Paid Software Announcement and Discussion] jeepcook:
Because with Flashfire I can backup on external sdcard directly, with other apps the backup is made in internal sdcard (openrecovery script) and I have to move it to external after the backup/install/reboot process. And I backup and flash my rom everyday (mokee OTA), I just wanted to have a simplier process.

And I test the Flashfire app for fun, because I found chainefire work is great....

Now I will continue with another app waiting for a better flashfire version, and I have a tasker task to automate the move from internal to external sdcard and a task to manage backups retention, and a task to do everything in one time !
[Paid Software Announcement and Discussion] rybshik:
Now I am a bit confused. To back with TWRP, I insert a SD card into my Android device, boot to recovery and backup file(s) are stored on SD

To backup with FlashFire, I insert the same SD card into my Android device, boot OS, start FF app; and backup file(s) are stored on the SD.

What's the deference ? In either case the backup files are on the same physical SD card.

For me the difference would be if FireFlash backs up some additional partitions, which TWRP is not capable of backing up (but perhaps capable of restoring)
[Paid Software Announcement and Discussion] grep_i:
With flashfire you don't need a custom recovery, everything is done from the app, backup, restore and flashing of zip and OTA or full rom, you can even keep rooted.

Other than that I see no real differences apart from the GUI, both TWRP and flashfire gets the job done.
[Paid Software Announcement and Discussion] Rakuu:
Ya but TWRP works if your os is borked.
[Paid Software Announcement and Discussion] grep_i:
Yes that's true, but I do not flash it on my device I only boot to it
[Paid Software Announcement and Discussion] Rakuu:
I still wouldn't suggest FlashFire to be a replacement for recovery because that is far from the truth, if you try to use it like that you'll be in for a world of hurt down the road.
[Paid Software Announcement and Discussion] Ibuprophen:
[MENTION=5906506]Rakuu[/MENTION], I have an open mind but, Just out of curiosity...

What app would you recommend as an effective alternative to a recovery with regards only to flash files that cannot be performed by conventional methods via a stock recovery as a result of an unlockable bootloader?

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[Paid Software Announcement and Discussion] grep_i:
I think you misunderstood me.

I do not flash custom recovery I only boot to it when needed with ADB and fastboot command.

To me flashfire is an excellent replacement for a custom recovery, sorry to hear you have lesser experience with it.
[Paid Software Announcement and Discussion] rybshik:
TWRP backup/restore VS FlashFire backup/restore

You mean booting to TWRP

fastboot boot twrp.img

Correct?

Let's compare one's own ROM backup/restore process,

excluding flashing new firmware

:

(1) TWRP backup/restore via 'fastboot boot twrp.img'

VS

(2) FlashFire backup/restore.

One obvious advantage of (2) is that it does not require a PC or any external device.

On the other hand, (1) is free, can be installed with APK without Google Play Store and Internet.

It's not only about money, but convenience.

I am wondering if one can buy and install Pro version of FireFlash without having a Google account and Internet on Android device.

On my device TWRP can see/backup/restore the following partitions:

/system, /data, /boot.

FireFlash can back up more (all?) partitions, but available for emergency restore are only:

/system, /vendor, /oem, /data (and /cache).
[Paid Software Announcement and Discussion] grep_i:
Yes that's correct that's the way I boot to custom recovery, and flashfire is also free you can download it from Chainfires website if you don't want to use Google Playstore or even download it from a site like apkmirror so it's equal convenient I guess.

Pro version is not needed for most stuff it is nice to buy it to support the developer though.
[Paid Software Announcement and Discussion] rybshik:
Timebomb

What about "timebomb"?
[Paid Software Announcement and Discussion] ridingthewave:
Good Stuff!

This app is great. I unlocked and rooted my Nexus 6 about 2 years ago at 5.1 and disabled the update nag and haven't messed with it since.

Tonight I decided to go thru the hassle of updating to 7.0 and I stumbled upon this app and downloaded the 7.0 update OTA via the settings menu. Flash Fire recognized the update in waiting and two taps and a couple minutes later I am fully updated, still rooted and unlocked!

Easy peasy... Thank you chainfire
[Paid Software Announcement and Discussion] Ch3vr0n:
[MENTION=2093337]rybshik[/MENTION] the timebomb is basically an internal counter with a set expiration date. Developers usually use that approach to 'force' users to use a more recent version of the specific app. This to ensure no bugs are reported by using an out of date version when a newer build exists that would fix the reported bugs.

Sent from my Nexus 7 (2013) with Tapatalk
[Paid Software Announcement and Discussion] rybshik:
if a time-bombing developer abandons the project (or decides to make it's currently free features paid), then we are out of luck :)
[Paid Software Announcement and Discussion] Rakuu:
I used to have an art s5 so I know this situation very well. This is the best app for what it is, especially if you don't have a custom recovery available, that said IF YOU DO, this is not an appropriate replacement since you have an easier alternative. Even on locked bootloader you may be able to use safestrap which is what I used.
[Paid Software Announcement and Discussion] rybshik:
What would be an "easier alternative"? TWRP or ADB/fastboot?
[Paid Software Announcement and Discussion] kilroystyx:
On my device TWRP can see more partitions [emoji1] but FF see much more.
[Paid Software Announcement and Discussion] rybshik:
How come? Are there some hidden options or tricks in TWRP? I am using the latest available for my device
[Paid Software Announcement and Discussion] kilroystyx:
Twrp-3.0.2-0 for my device come with this offer.

Details here

Official site here
[Paid Software Announcement and Discussion] anees02:
Could I make a flashfire backup and then flash it via odin?

If yes ,how to do it?
[Paid Software Announcement and Discussion] jcmm11:
Yes. See the Odin section on this page

https://flashfire.chainfire.eu/actions/backup/
[Paid Software Announcement and Discussion] anees02:
I don't have odin choice.

I have

Normal backup

ID backup

Full backup

RAW backup

Fastboot

And no odin choice.
[Paid Software Announcement and Discussion] ktmom:
Is your bootloader unlocked (it's a prerequisite). What device?
[Paid Software Announcement and Discussion] anees02:
Yes the Bootloader is unlocked

My device (SM-N910P).
[Paid Software Announcement and Discussion] KaMyKaSii:
If I'm not mistaken, the odin backup feature was delayed (in the middle of the year) for several inconsistencies, which took a lot of time from Chainfire and ended up discouraging him from developing FlashFire, since he has several other works to keep. He already quoted a new update a few pages ago, so maybe he could fix the bugs in this kind of backup, maybe not. We can only wait to see
[Paid Software Announcement and Discussion] HorusEyE:
Hi guys...

I have already followed some tutorial using FlashFire to update from 4.4.2 to 5.0.1 without loosing root or triggering the Knox flag but I can't find it anymore...

Can wanyone point me a tutorial to do so for a Galaxy S4 (GT-I9505 LTE)???

Thanks
[Paid Software Announcement and Discussion] HorusEyE:
Thanks again... I remember now that you was the one who helped me last time too!
[Paid Software Announcement and Discussion] Lem0ns:
I have a strange problem after using Flashfire backup.

Samsung s4 i337m (canadian)

Never been updated since buying the phone new 2 years ago.

Used towelroot on day 1 and installed super SU

everything has been fine since then. Decided to try to update to the latest official today.

Updated SuperSU binary and installed Flashfire.

Rebooted and everything was normal.

Ran flashfire and did the fastboot backup. took 30 minutes... at the end the phone rebooted and all apps crash (unfortunately xxxx has stopped) on startup on a black screen.

I have not attempted to update anything yet, only ran the backup.
[Paid Software Announcement and Discussion] KaMyKaSii:
When you said that already followed a tutorial about it, I remembered that I helped you. We are here for this.

---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------

Can you get /sdcard/FlashFire/lastlog file and send it here?
[Paid Software Announcement and Discussion] Lem0ns:
I posted too soon before attempting to clear the cache. I thought it wouldn't help because nothing was modified but all is back to normal after clearing. Thanks anyway!
[Paid Software Announcement and Discussion] grep_i:
I think you need to combine these two options for best results
[Paid Software Announcement and Discussion] BROKEN1981:
Will this work for the LG V20?
[Paid Software Announcement and Discussion] Ch3vr0n:
Make a nandroid backup, try it and find out. That's what they invented backups for.

Sent from my Nexus 7 (2013) with Tapatalk
[Paid Software Announcement and Discussion] Cone1237:
Im on note 5 920t having problem all of a sudden with this it's just sitting on root permission just started doing this last couple days any help would be much appreciated thanks
[Paid Software Announcement and Discussion] ktmom:
What root are you using?
[Paid Software Announcement and Discussion] haher2:
Installed Flashfire from google play on moto g4 play, CM 14.1.

When I launch it, there is a warning screen:

Exclamation mark in a red circle

"Root access could not be acquired, or you are not runnign either SuperSU or (CM SU with SELinux set to Permissive). Are you rooted?"

Root access is enabled in "Developer options"

Update: solved. Set SELinux to Permissive mode via terminal.
[Paid Software Announcement and Discussion] anees02:
Could anyone tell about flashing custom roms on locked Bootloader with flashfire?

Is it safe?
[Paid Software Announcement and Discussion] Cone1237:
I'm using super su been rooted since day one it was working fine last 2 days or so it just Sartre stick on getting permission I'm on a note7 posted rom

---------- Post added at 07:54 PM ---------- Previous post was at 07:54 PM ----------

It's strange
[Paid Software Announcement and Discussion] hiimpig1:
This works when i locked my bootloader?
[Paid Software Announcement and Discussion] jhs39:
You need to unlock your bootloader if you are going to flash a custom ROM. Why would you want to keep your bootloader locked?

---------- Post added at 08:55 AM ---------- Previous post was at 08:49 AM ----------

If your bootloader is locked you can't really flash anything. Why do you want to keep your bootloader locked?

---------- Post added at 08:57 AM ---------- Previous post was at 08:55 AM ----------

Maybe you should try flashing the latest SU zip in recovery.
[Paid Software Announcement and Discussion] rybshik:
Maybe to flash and then re-lock?
[Paid Software Announcement and Discussion] Cone1237:
So for hell of it I open the old mobile odin and grated su right away my flashfire still sitting on gaining root access any one experience this or have a fix thanks was working 2 days ago on n5 920t rooted n7 port rome

---------- Post added at 09:09 AM ---------- Previous post was at 09:02 AM ----------

I believe I am on it the 2.79 if I'm right or is there a newer one out thanks for replying
[Paid Software Announcement and Discussion] danmaman:
Hi [MENTION=631273]Chainfire[/MENTION] (Happy New Year ) and all XDA members

Please can you update Flashfire with Supersu 2.79

everytime if i want to flash a factory image or ota, it injects supersu 2.78 and i have to update through the playstore supersu app the new binaries to 2.79

is it possible?

thanks in advance
[Paid Software Announcement and Discussion] grep_i:
Wow, you can flash SuperSU v2.79 yourself in the same queue just add it after your factory image or OTA and ofcourse don't choose to inject the everroot method.

When I use flashfire I make a queue of factory image

SuperSU

Custom Kernel

Xposed

Suhide

Than you can always select the latest versions of everything.
[Paid Software Announcement and Discussion] Cone1237:
Thanks bud I flashed the new 2.78 sr1 it took few but worked thanks for your help
[Paid Software Announcement and Discussion] jhs39:
If you aren't fully stock and relock the bootloader you could end up in a bootloop.

---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------

I think 2.79 is the latest stable version.

https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
[Paid Software Announcement and Discussion] Chainfire:
v0.54 PRE-RELEASE - PIXEL ONLY

Linked below is a pre-release of the next FlashFire version. This version will not be available on Play.

--- FOR

PIXEL

AND

PIXEL XL

ONLY ---

(use on other devices completely untested, the rest of this post assumes usage on Pixel)

--- USE ONLY TO FLASH

OTA

WITH "

Flash ZIP or OTA

" ACTION ---

(backup, restore and full firmware flashes are not yet fully supported)

This release is far from finished, but seeing as the January update for the Pixels (NMF26U/V) is starting to roll out, we might as well test this functionality now.

There are two relevant types of OTAs:

- Full OTAs that are horribly misnamed and you can download from Google's website ( https://developers.google.com/android/ota )

- Incremental OTAs that are downloaded by the device automagically

Flashing

Full

OTAs

- Copy the download ZIP to the device

- Use "

Flash ZIP or OTA button

" in FlashFire to select the ZIP

- Make sure "

Inject SuperSU

" option in "

EverRoot

" action is enabled

- In the "

Reboot

" action, set the reboot delay to 5 minutes.

Flashing

Incremental

OTAs

- If all is well, FlashFire should have hijacked the OTA system completely. In other words, once the download of the OTA completes, FlashFire should be started automatically and will offer to flash the OTA for you.

- In the "

Reboot

" action, set the reboot delay to 5 minutes.

Because the Pixel does not have a dedicated recovery partition, TWRP is located inside the boot partition. If you flashed TWRP to your device (rather than just booted it) and used that to flash the SuperSU ZIP, this means the backup of the boot partition that SuperSU generated is actually of TWRP, and not of the stock boot image. The "

Restore boot and recovery images

" option will thus restore the wrong boot image. Currently the only solution to this is turning off this option and manually flashing back your current firmware's stock boot image as an action before flashing the OTA ZIP.

I am investigating possible workarounds for the final release.

Additionally, the very first time I tested this whole procedure, for me the OTA would fail to flash the modem partition. Apparently the modem partition flashed to my device at the factory was not the one the (incremental) OTA expected, which is very weird in itself. I had to (fastboot) flash the full firmware before my device was in a state that I could flash the OTA. I expect more people to run into similar issues.

This first flash may be a bit cumbersome, but once it's all up and running, future OTAs should be effortless.

During flash

The flash itself shouldn't take more than 5 minutes. Please watch the screen for one of these messages:

If successful: OTA RESULT == 0

If failed: OTA RESULT != 0

Please let me know if the above is correct. I have some doubts if the != value occurs on all failures.

Download

USE AT YOUR OWN RISK

FlashFire-v0.54-PRE-20170103224010.apk

Note: EverRoot installs SuperSU v2.79 SR2
[Paid Software Announcement and Discussion] KaMyKaSii:
[MENTION=631273]Chainfire[/MENTION] I was very excited when I saw your post about a new update. I do not have a Pixel, but since I was experiencing some issues with FlashFire (device rebooting soon after "show ui" in lastlog without entering FlashMode), I was certainly willing to test the new version, I'm sorry if this is not the feedback you waited.

In the past, FlashFire worked quite randomly, but I did not quite understand why sometimes yes and sometimes not and because every reboot is precious, I stopped using the app temporarily. Up to now! Because in the three consecutive attempts I made, they all went into FlashMode. A few comments that I would like to do:

1. Running the new FlashFire and the older versions along with the SuperSU v2.79 SR1 and the older versions, the lastlog gets filled with "permissive" lines, after using FlashFire to upgrade to SuperSU v2.79 SR2 (on first test), all those lines are gone (In the next tests) so I think that's good.

2. In all three tests, before the "loading" screen appeared my bootanimation flashed on the screen through, as if the device were doing a soft reboot, and the same happened before FlashMode started. But this does not interfere with what really matters, which is to complete the actions.

3. In the last test, an error occurred while preserving recovery, both in backup and restore.

I would also like to make a suggestion: would not it be better if the "preserve recovery" option is automatically activated only when a Flash OTA action is added? Because if the only action you add is to flash a recovery and click "FLASH", in the end you will continue with the old recovery.

And also a question: In the past you requested the"/proc/last_kmsg" file in bugs reports, Why did you stop asking?

Here are the logs of the three tests if required:

https://drive.google.com/folderview?id=0B1uvONk-jlRiMzFEdmJPSElrcDQ
[Paid Software Announcement and Discussion] Chainfire:
That is good news, I did spend quite some time on trying to fix this.

That part of the log is cut off in case FlashFire goes beyond the 'show ui' part, as it's no longer relevant.

This is to work around some issues with SurfaceFlinger. The bootanimation binary force-initializes the screen in case of a non-standard SurfaceFlinger initialization routine. For example on the Samsung S7 on the latest Nougat Beta, if you don't do this, you get only a few pixels of display in the top-left corner.

This is a bug and will be fixed for next release.

The app tries to be smart about this, it isn't enabled by default. Perhaps it could be even smarter, but I have so many things with a much higher priority to fix.

No specific reason. It hasn't been that relevant lately. In the future, I hope to automate the collection of all relevant logs, but I don't think this'll be in the next update.

Thanks.
[Paid Software Announcement and Discussion] shotonhead:
[MENTION=631273]Chainfire[/MENTION] tried it on my pixel xl.everything went smooth.i tried it with full ota.no problem here booted just fine.root was present after boot.twrp gone reverted back to stock recovery.only thing weird was i had installed viper4android and it has gone now:D only that lol.thanks for ur work.:good:
[Paid Software Announcement and Discussion] Majesty00:
Here's the log of my failed January OTA update with FlashFire Pro 0.54-PRE on my Pixel (5", 32GB version).

I hope it helps find a bug, if not, what went wrong on my side?

Thank you!
[Paid Software Announcement and Discussion] phishfi:
Do you recommend that we install SuperSU before installing TWRP to the boot partition then? There's that timeframe between fastboot boot twrp and flashing the twrp zip. Sounds like you're saying our best bet for getting a safe backup image through SuperSU would be to flash SuperSU, then flash the twrp zip...