yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] mochamoo:
Read Chainfire's release notes, specifically:

This update focuses primarily on two issues relating to flashing OTAs:

- Uncrypting errors: some users experienced issues while uncrypting freshly downloaded OTAs (app crash or corrupted uncrypt). This issue should now be solved. If this ever failed for you, there is a good chance your next OTA flash attempt will fail again as well (with a red line complaining about an invalid ZIP file), due to left-over files. The solution is to simply do it twice.

- Multi-stage OTAs: some recent OTAs install in multiple stages; they first flash a new recovery to the boot partition (that is not a typo), then boot to that recovery to perform the rest of the firmware update. FlashFire can now directly handle these OTAs without going through recovery.

Note that sometimes, after flashing an OTA, the device may still boot to recovery (and show you an error message). Simply reboot the device if that happens - it doesn't mean the flash failed.
[Paid Software Announcement and Discussion] Thijssie909:
Hi Chainfire, today I had a first effortless hijack of the OTA on my Google Pixel! :) Really nice to see this working, thanks a lot!!
[Paid Software Announcement and Discussion] jcmm11:
Can you get into TWRP? If so go to /data/system and delete

*.key

locksettings*
[Paid Software Announcement and Discussion] eckstein:
No data partition when flashing firmware package

First of all: thank you for your amazing software. It saved me a lot of time over the last year I had an Nexus device. :good:

Yesterday, I've installed the update of FlashFire from the PlayStore and now I've tried to flash "7.1.2 (N2G47F, Apr 2017)" from the Google developers "Factory Images for Nexus and Pixel Devices" site on my Nexus 5x.

After the download had finished I've chosen "Flash firmware package" and let FlashFire scan the archive. This process completed, the popup showed up, where I could select which partitions to or not to flash. But there was no option on the data partition. The last months I used FlashFire to update my 5x to the latest firmware available, and there I could deselect the data partition to keep my phones data untouched. But this seems to be missing in this version of FlashFire.

Is there any way to keep my data untouched or am I missing something?

Thanks in advantage.
[Paid Software Announcement and Discussion] Chainfire:
"The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem."

It seems your system partition was modified somehow.

It's weird with these A/B OTAs (for the new partition layout of the Pixels) that they do not perform sanity checks before doing the update, like the OTAs for older devices do. In your case, it updates half the device before checking the system hash value and aborting, leaving you with half-old half-new firmware, which obviously doesn't boot.

FlashFire does not flash /data at all from firmware packages. If a package includes it (and it doesn't have to), it's generally just an empty filesystem - if you want to do that, add a wipe action.

By the way, it is usually safer to flash the OTA variant from the same download site.
[Paid Software Announcement and Discussion] eckstein:
Thank you. So it's safe for me to flash the firmware package and my phone should have all apps and data still the same after the update has finished?
[Paid Software Announcement and Discussion] Chainfire:
Should be, yeah. But it never hurts to have a backup :)

As I said in an edit to the other reply: the OTA variant from the same site is usually a tad safer to flash.
[Paid Software Announcement and Discussion] lop1:
[Android 4.2+][ROOT][2017.04.03] FlashFire v0.57

hello,

I have used flashfire pro without any problem on my S5 mini and my nexus 4 and 5 , but with my new A3 2017 under marshmallow Flashfire does not make backups . After running flashfire there is nothing in the flashfire/backups folder .

here is the pastbin of the last log : https://pastebin.com/9X8M2xNE

Flashfire pro v0.57

Android 6.0.1

Rooted with SuperSU pro v2.79

Stock recovery

Where can I get some help on this issue ? thanks in advance

Laurent
[Paid Software Announcement and Discussion] StupidIdea:
Wow, I didn't expect an update that fast. I only tested the first version from pm with downloaded full OTA which finished flashing but bootloop so I flashed 7.1.2 from fastboot. I saw you uploaded and update to PlayStore already but if you were not able to reproduce it and still need a test I can revert to 7.1.1 and test it. Otherwise I will try it for sure with next update. Thank you very much for it.
[Paid Software Announcement and Discussion] TCattd:
Rebooted the device several times after the failed FlashFire session, and always booted up into TWRP; i wasn't just one time. As i said before, finally have to solve it flashing the full OTA https://developers.google.com/android/ota from within TWRP.

Odd.

I tried to rule out that possibility before, flashing the system image from https://developers.google.com/android/images as i said at https://xdaforums.com/general/paid-software/flashfire-t3075433/post71325892#post71325892 doing a flash-all and starting fresh. Completely stock and fresh.

I have installed SuperSU, and just use it for Greenify and AdAway mainly. Greenify shouldn't be a problem (i think), and have enable systemless mode option checked in AdAway so it shouldn't be a problem either.

No /system modification.

Don't know what's happening, really. It's annoying.

Thanks for the time, anyways, Chainfire. Appreciated.
[Paid Software Announcement and Discussion] FlyOnTheWall43:
Worked like a charm, thank you sir! Any idea what I did wrong and/or how to prevent it in the future? I've used Flash Fire for all the security updates and have never ran into this before.
[Paid Software Announcement and Discussion] Chainfire:
I have had the exact issue when I also thought I was starting fresh. The OTA thinks /system is modified, that is all that is certain. I actually started testing a few days ago to reproduce this exact same issue, but of course now everything is working fine on my own device with the latest OTAs. So I guess it did get modified somehow.
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
Awesome Plaything you got there, very useful for my lesser known devices. Although, doesn't work on my Lineage 7.1.1 's " 16 cm su "(or am i doing something wrong?). All the best for fixing.
[Paid Software Announcement and Discussion] Ch3vr0n:
Latest version uncrypted and updated my 6P the ota to 7.1.2 succesfully but the device was NOT ROOTED afterwards and Everroot was enabled and twrp was not restored. And since my usb c port is giving a hard time charging / usb connecting but after about 10 minutes of trying i was able to fastboot boot twrp and flash SR3 that way and was rooted again.

lastlog attached but can't seem to unpack it myself. Winrar reports corrupt archive
[Paid Software Announcement and Discussion] Vledderos:
Ran flashfire 0.57 for today's received ota (7.1.2) on my n5x with success! 7.1.2 installed flawless with everRoot. (Coming from latest monthly patch without custom recovery).

Thx chainfire!
[Paid Software Announcement and Discussion] ytumer:
Another successful OTA update on a N5X. Thank you so much for listening to our feedback and fixing the issues with the OTA unencryption. You are a legend in this community.

EDIT: Just noticed your donation button. Enjoy a hot beverage on me mate.
[Paid Software Announcement and Discussion] MetalWarrior:
Hey folks!

Did anyone already flash this with FlashFire?

https://xdaforums.com/android/softw...market-links-theme-ready-apps-t3447494/page13

Would like to do so on a rooted Wiko Pulp 3G with latest stable SuperSU on stock 5.1.
[Paid Software Announcement and Discussion] Ch3vr0n:
This thread is meant for things related specifically to FlashFire. That mod has zero relevance to flashfire and you need to ask in the mod thread itself.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
Oh god, so embarassing. I didn't know seLinux had to be permissive.
[Paid Software Announcement and Discussion] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], can you please confirm whether or not SELinux Mode has to be in a Permissive state for FlashFire to properly work?

And if so, then am i correct by stating that this requirement began with the release of FlashFire v0.54?

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Ch3vr0n:
Flashfire requires either superSU or a kernel in permissive mode. He said that a long time ago, used to be in the first post too. No clue why it's not there anymore.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Paid Software Announcement and Discussion] KaMyKaSii:
This information is on the website/manual:

"Full root access is required, using either a recent version of SuperSU, CM's su with SELinux set to Permissive, or Magisk"
[Paid Software Announcement and Discussion] Ibuprophen:
I'm not trying to dispute this requirement at all and I do understand it.

I was just asking [MENTION=631273]Chainfire[/MENTION] if this was a requirement from the very first release of FlashFire?

And if not, then which version of FlashFire was this an added requirement?

There's a specific reason for the above questions and depending on the answer, it could explain a whole lot for something else.

I really appreciate your understanding for this small clarification.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] Ch3vr0n:
Pretty sure it always has been, I can remember seeing it in the first post until the main site was up. Magisk wasn't even an option then. It was either superSU or a kernel in permissive mode.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Paid Software Announcement and Discussion] Ibuprophen:
Okay... I'm feeling like a complete noob...

Regarding the SELinux only...

Based solely on the Changelogs that were posted on this thread, i had gathered the following:

v0.26 Beta - The requirement for the SELinux Mode needing to be in a Permissive State was first noted.

v0.28 Beta - The next appearance of SELinux appeared as a sort of additional SELinux fix of sorts.

v0.55 - The next appearance of SELinux appeared as a bug fix of sorts.

Now i do apologize deeply to [MENTION=631273]Chainfire[/MENTION] and the rest of you!

This pretty much confirms my suspensions regarding another issue, though it is FlashFire specific, it has to do with it's use for something else that doesn't belong on this specific thread.

I want to Thank You All for Your Time, Patience and Understanding!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] grep_i:
But this requirement was only meant for CM built in root or CM su or whatever it is called with that su in enforce mode FF would not work.

I for once always used it in enforce mode with Chainfire Supersu.
[Paid Software Announcement and Discussion] Chainfire:
FlashFire needs to modify SELinux for flashing to work.

On SuperSU, this is guaranteed to work and no further action is necessary by the user. Since last version, it also works on MagiskSU most of the time. On CM/LOS, it usually does *not* work, the work-around is to set SELinux to permissive yourself, which disables SELinux.

The latter is usually just executing 'setenforce 0' and is easily executed. This is however not included in FlashFire to be executed automatically because Google actively scans APKs for containing this command, and bans those apps from the Play store.
[Paid Software Announcement and Discussion] carlosbalbuena_:
Sorry for the ignorance but as active the permissive mode?, I have an i337 bootloader blocked I do not know if it needs some kernel or something, thank you for your work.

Enviado desde mi SGH-i337 usando la rom WizCyanV4.1
[Paid Software Announcement and Discussion] saarxee:
FlashFire has stopped working after I choose "install ZIP" on Galaxy S4.

Why?
[Paid Software Announcement and Discussion] Many40:
Hi,

May I recommend something? - if you don't follow this thread, please read at least Chainfire's post #247 and report properly your issue (logcat, FF lastlog). Without this I doubt anyone can guess what might have happened in your case.

Regards
[Paid Software Announcement and Discussion] pro-handler:
Flashfire is not compatible wid my phone :(:(

Sent from my Archos 50 Neon
[Paid Software Announcement and Discussion] freak69ize:
Ive only tried flashing a zip file so far and that worked flawlessly on my Verizon S5. Will try other functions later. Will be buying pro version soon.)) thanks Chainfire.. You the man
[Paid Software Announcement and Discussion] samccfl99:
A couple of questions now that i got FF working

Seems it does not play well with NG3/XDK on my G900A. finally i went down to NCE and rooted and it worked like a charm and i installed stock 5.0 flawlessly and backed it up and then installed Twi5ted rom and then backed it up. i restored both of them.

so my first question is, should i do a wipe first before a restore? i did not and it still worked. probably would not hurt? also when i restored stock it all booted perfect, but when i restored Twi5ted, it got stuck on the Apps loading (the rom does that). had to do a battery pull and then it came up fine. had not tried it again, but i will. i know its still in beta. i donated and bought the pro version. i am not a freeloader.

The other question is, can FF process the Downgrade to NCE tar? i dont have any problem Odining, just in case, but since it can take a tar, it is a logical question.

Hopefully maybe when its out of beta you can make the font a bit bigger when it is doing its thing. BUT ITS GREAT. THANKS! :good::good::good:
[Paid Software Announcement and Discussion] talvigi:
Hay guys can I use flashfire on my LG G2 LS980, if I want to keep root from zvd and continue working on my device. It may be noted that I have used it on my i337 and it is working well.
[Paid Software Announcement and Discussion] Chainfire:
v0.16 released

I have just pushed v0.16 to the Play store, which should start redistributing it to you over the next few hours.

Note worthy changes:

- Various missing partitions have been added to the detection list

- Default compression for backups is now LZ4. It is not as good as GZIP (the former default) but it is much faster, and uses a lot less resources / generates less heat.

- Aside from SuperSU, the app will now also work with CM SU. This has not been extensively tested.

- When you run out of space you get an error instead of just freezing. I think quite a few reported freezes may be 'solved' by this.

- It seems a lot of the reported crashes were caused by having corrupt ZIP files on your storage. The app now reports corrupt ZIPs instead of crashing.

- A lot of file operations are now better cached, which should significantly improve file selection speed, especially if you have a lot of ZIPs on your storage.

Once again, please re-report any issues after testing if they still exist on v0.16. Provide all relevant details and/or link to your previous post.

See the changelog for further details.
[Paid Software Announcement and Discussion] zahni71:
New Version Version(v1.16) misspelled in changelog?

Gesendet von meinem SM-G900F mit Tapatalk
[Paid Software Announcement and Discussion] :
[MENTION=631273]Chainfire[/MENTION], is it possible to set default backup destination (sdcard or internal memory) in menu/settings? I still must choose sdcard in each backup I make now. I prefer sdcard (external memory). Thx
[Paid Software Announcement and Discussion] MeX_DK:
I'm not allowed to join the beta. Is there a place outside of Google play I can download it?
[Paid Software Announcement and Discussion] yoonus:
Not able to download flashfire

I joined the community and signed up.

When I click on the link to download flashfire from playstore getting below error

"We're sorry, the requested URL was not found on this server."

Update: Working now
[Paid Software Announcement and Discussion] angelle97:
Currently have new version.... when I tap install zip, and search for the file, it does not show. I have the file on both internal and external sd. Zip file does not show up in either.

Running stock rooted i537 NE3
[Paid Software Announcement and Discussion] Chainfire:
"Flash ZIP or OTA" only shows ZIPs it detects as compatible. If it does show up when selecting "Flash Firmware Package" then it is not an 'update zip'. When in doubt, post the actual zip.
[Paid Software Announcement and Discussion] angelle97:
It's the lollipop update zip I downloaded from the thread on keeping root using flashfire. I'm re downloading now to see if it will work this time.

deleted ota zip from both internal and external sd. downloaded a fresh download, and tried again...SUCCESS!

everything seems to be in working order to perfection!
[Paid Software Announcement and Discussion] kashortiexda:
[MENTION=631273]Chainfire[/MENTION] just successfully made a backup of ID on S6 Edge 925F International. ... first time it's worked .... latest update 16 Pro version. ..... thank you :)
[Paid Software Announcement and Discussion] lollyjay:
Tried on Asus tf300t, when making backup it freezes and then reboots.
[Paid Software Announcement and Discussion] angelle97:
deleted
[Paid Software Announcement and Discussion] big.simba:
I have the same problem, but on a Galaxy S4.

I'm just making a backup of the system partition, and after a couple of minutes, the phone vibrates twice and reboots. The backup file is incomplete and cannot be restored, and trying to open the .tgz backup file in Windows shows "unexpected end of archive."

Interestingly, the backup always stops/fails at 760MB. If I try to back up two partitions (boot and system), the backup operation stops/fails even sooner at 50MB.
[Paid Software Announcement and Discussion] strikerdj2011:
worked great on 925f s6 edge
[Paid Software Announcement and Discussion] sswagonman:
Damn here in Australia says item not found in play store
[Paid Software Announcement and Discussion] Bakuryu42:
I'm having an issue downloading FlashFire from the Google Play Store. When I go to download it says that its downloaded and installing, but when it ends the install button reappears.
[Paid Software Announcement and Discussion] Ch3vr0n:
Carlos, permissive mode is a kernel thing. Something you can't change with a locked bootloader.

Baku that's a play store issue, not a FlashFire one.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Paid Software Announcement and Discussion] Bakuryu42:
Any ideas on how to fix the play store issue?

Edit: Apparently it is installing, but instead of giving me the open button it stays as the install button, any idea why?
[Paid Software Announcement and Discussion] carlosbalbuena_:
Ok thanks, I'll stick with the old version.

Enviado desde mi SGH-i337 usando la rom WizCyanV4.1
[Paid Software Announcement and Discussion] Ibuprophen:
Thank You Very Much!

I really appreciate you taking the time to respond to the SELinux clarification on this.

Especially for a little guy like myself LOL!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Paid Software Announcement and Discussion] FriendlyNeighborhoodShane:
That explains it.
[Paid Software Announcement and Discussion] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION], as mentioned in the SR3 thread i need to send my phone in for repair. In order to qualify for repair i need to undo ALL traces of root (which means just to be safe) flashing factory image + relocking bootloader. Naturally the first thing i'll do is unlock & root again. Then comes the point of restoring my data. Since i've never needed to do that (or even send a phone in for repair, ever), i was wondering if it's that simple as to select "restore" in FlashFire and point it to the latest backup folder and hit "Flash" or is there more to it?
[Paid Software Announcement and Discussion] Bakuryu42:
I'm having an issue with doing backups. Whenever I run a backup it gets stuck on my Verizon logo. It never saves the backup either. G900V 4.4.2 Rooted.
[Paid Software Announcement and Discussion] Inferi0r:
On my Nexus 5X with Android 6.0.1 I used FlashFire 0.57 to wipe (not format) dalvik + cache. After a succesfull reboot my patern lock is always wrong. So FlashFire messed with my patern lock, as I have a really simple one and the same for 5 years. (default boot+recovery+rom, only latest XPosed)

- Fingersensor is not working as you need to unlock by pattern/code after a full reboot

- I disabled USB debugging, so removing the pattern lock with one of the ADB commands is no option

- No SDcard in Nexus and no custom recovery installed for the pattern-unlock-zip-flash

- Since Android 6 (or even before?) the remote lock function from online Android Device Manager is not replacing the pattern lock anymore but just adding another lock on top of it, and thus no option.

I guess I need to wipe my data partition, to get back, unfortunately.
[Paid Software Announcement and Discussion] skiely666:
This exact thing happened to me on v0.55 & yes I had to wipe & start again. Rolled back to v0.53 to before you have to choose your system type in options it detects it automatically, I think that's what went wrong for me..
[Paid Software Announcement and Discussion] Bakuryu42:
In an effort to better explain my problem and hopefully receive some help I am making this post as detailed as possible.

Phone: Verizon Samsung Galaxy S5 SM-G900V

Android Version: Kit Kat 4.4.2 NCG

Kernel Version: 3.4.0

eMMC Chip: 11 Toshiba

Bootloader: Locked

Rooted: Yes

Safestrap: Yes

Goal: Upgrade to Lollipop while keeping root.

Current instructions on accomplishing this are seen here. I am unsure if there are newer of better instructions, but thus far I haven't found any.

Issues:

1. Flashfire installs from the play store, but never gives the option to open it from the play store after its installed and instead shows the install button still.

2. When attempting to make a backup using Flashfire I get the black screen with the fast flowing directories flying by with an eventual end at which point the screen fades to black and the phone reboots. When the phone gets to the Verizon logo screen it stops and never ends. The only solution is to remove the battery. Once it reboots I find that a backup has not been made.

Considering these two issues I feel it is unsafe to follow the instructions found above to accomplish my goal.

Any help in rectifying these issues and/or helping me accomplish my goal would be greatly appreciated. If you need more info about my phone or what I have installed please let me know here or in a PM.
[Paid Software Announcement and Discussion] ktmom:
Yes, on the repaired phone, you can point FF to the back up and restore the repaired phone to the same point you were at when having done the backup. It is basically a nandroid, but one specific to FF.

I back up then clean flash a different ROM to test something and when done, restore back to my daily driver via a FF backup.

---------- Post added at 17:04 ---------- Previous post was at 16:48 ----------

Have you uninstalled Flashfire, rebooted then tried reinstalling it? Or clearing playstore cache?

I'd resolve this issue before relying on FF for an upgrade. There is a log after every action FF performs in the FF directory. If reading that doesn't help you, post it to pastebin.com and post a link here.

Have you tried deselecting "preserve recovery" in the reboot action for a backup?
[Paid Software Announcement and Discussion] thevoiceover:
Good job to everyone in here... Keep it going guys!
[Paid Software Announcement and Discussion] Bakuryu42:
Yes, it still did it.

Reading the log isn't much help especially because I don't know what I am looking for.

Here is a paste bin of the log: https://pastebin.com/gKiJcHWf

Preserve recovery was not checked, should it have been?