[Android 4.2+][ROOT][2017.09.21] FlashFire v0.73

[eckstein]

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

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?

 

[Chainfire]

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?

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.

 

[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

 

[StupidIdea]

Have you had a chance to test the last version I sent you in PM ?

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.

 

[TCattd]

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.

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.

"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.

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://forum.xda-developers.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.

 

[FlyOnTheWall43]

Can you get into TWRP? If so go to /data/system and delete
*.key
locksettings*

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.

 

[Chainfire]

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://forum.xda-developers.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.

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.

 

[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.

 

[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

 

[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!

 

[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.

 

[MetalWarrior]

Hey folks!

Did anyone already flash this with FlashFire?

https://forum.xda-developers.com/an...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.

 

[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

 

[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.

Oh god, so embarassing. I didn't know seLinux had to be permissive.

Sent from my GT-I9082 using XDA Labs

 

[Ibuprophen]

@Chainfire, 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...

 

[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

 

[KaMyKaSii]

@Chainfire, 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...

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"

 

[Ibuprophen]

I'm not trying to dispute this requirement at all and I do understand it.

I was just asking @Chainfire 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...

 

[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

 

[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 @Chainfire 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...