yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] deinvater:
That was one idea I also had, but I have no clue how to find out which version I was running before the backup. Any idea?

I have already tried using a Marshmallow version but that resulted in the same thing. I am guessing it has to be the exact same version.

I used the pc version of Odin, is that outdated as well?

Thank you SO MUCH for your help! spent about 7 hours yesterday trying to fix this without success.
[Paid Software Announcement and Discussion] rift999:
I have a Pixel xl and receive error code 20 when attempting to flash ota updates. Attached is the log. Thanks for any help.

http://pastebin.com/isLj06Wn
[Paid Software Announcement and Discussion] jdegreef:
I'm not sure it is possible. In the Flashfire doc it's explained how to restore from TWRP and nothing else.

I think the best solution is to make an ADB backup of your phone for the case you describe. You can then restore it, install Flashfire and restore your Flashfire backup(s).
[Paid Software Announcement and Discussion] TCattd:
[MENTION=631273]Chainfire[/MENTION], same error with March update for the Google Pixel XL.

It detects the OTA, FlashFire opens by itself, but the same ErrorCode: kDownloadStateInitializationError shows up: http://i.imgur.com/GOqWBnu.jpg

Latest FlashFire installed.
[Paid Software Announcement and Discussion] adrman:
Working perfectly with the full OTA dl on Angler.
[Paid Software Announcement and Discussion] JoshwaDroid:
Hello, I have a problem with the latest update, on Samsung S4 Verizon variant with Lolipop, it just loads but doesn't load the red bar screen, and just stay on black screen, until a device reboot with nothing changed, (No Wipe, No Flash, Nothing). does Someone else have this problem?
[Paid Software Announcement and Discussion] KaMyKaSii:
Send /sdcard/FlashFire/lastlog
[Paid Software Announcement and Discussion] veez21:
After a few tests, I think flashfire freezes in flashing when it encounters a script error when using shell(update-binary) :(
[Paid Software Announcement and Discussion] JoshwaDroid:
Hope the best, Thanks for reply.
[Paid Software Announcement and Discussion] JoshwaDroid:
a proper Log on pastebin after reading OP bug Guidelines.

http://pastebin.com/bCin4KkJ
[Paid Software Announcement and Discussion] TR2N:
For me it is not possible to flash the March OTA on my angler device. The app crashes when encrypting the package. No log written.
[Paid Software Announcement and Discussion] TCattd:
[MENTION=631273]Chainfire[/MENTION]

Attached is a FlashFire log.

Today i tried to start fresh to rule out any other error, so i downloaded the stock image from february (to get the march OTA and test this), and flash it into my Pixel XL (flash-all.sh).

Fully stock, i set up the phone, rooted (TWRP and SuperSU 2.79 SR3), installed FlashFire, and triggered the OTA download from the phone settings.

FlashFire catches it, opens itself, and do his thing.

Same error as before. ErrorCode: kDownloadStateInitializationError.

It doesn't work here. From fully stock and wiped. You can check the attached log.
[Paid Software Announcement and Discussion] mousefai0922:
I noticed the app keeps crashing when I trying to get the nexus 6p new security patch..

Any ideas why?

---------- Post added at 01:41 AM ---------- Previous post was at 01:39 AM ----------

same here.. any results yet?
[Paid Software Announcement and Discussion] artistree:
This app is great love the replacement for twrp since it's not available. This is the second phone I've had it on...so far so good!
[Paid Software Announcement and Discussion] Dixon Butz:
Wow, this was EZ mode to sideload the March update on Nexus 6! First time I used this app to sideload since I bought it last month.

Went from stock 7.0.0 rooted to 7.1.1 (N6F26U) rooted in just a couple of clicks. It was so fast.

Worth ever penny!
[Paid Software Announcement and Discussion] whitlecj:
If I am on the verizon version from back in november, should I also flash the bootloader and radio img files? Sorry for the dumb question new to the pixel. Got lucky and bought one that had not been updated.
[Paid Software Announcement and Discussion] GillRigged:
When you choose to "Flash Firmware Package" you'll be able to select/deselect whatever you want but it should have the recommended images selected. Some files (the ones that won't be selected) will say "Protected" (???) Or something similar. Unless you're upgrading to a major version (6.1.1 > 7.0) I would just go with whatever it has selected by default.

In Settings there's an option to Flash Bootloaders which is device dependent. Next update I'm going to give it a go but for major updates I'll flash clean with (hopefully soon for the Pixel devices) WugFresh's Nexus Toolkit. When I first got my Pixel XL last December I tried to manually update and it soft bricked on me. In a panic I found the SkipSoft Toolkit and it fricken worked. It's nothing like Wug's but it got the job done and for that I'm very thankful. However, after January dude quit updating the program for device updates. He still hasn't added February security patches and you can't just add your own like with Wug's. So, my point is I wouldn't use this for major version updates and when you do you should do a clean install (wipes device) and either start over or restore data (which sometimes still causes issues). IDK, these are recommendations but I know I'll be testing out a major version jump with this app when the next Android is released. I just always take the time and run a full backup first.
[Paid Software Announcement and Discussion] Johnnycool18:
I have the EXACT same problem. I do not use TWRP so I solved it differently. It failed both on the February and March updates.

Phone comes back up with no root/no update. I then re-rooted the phone using his boot flash img file.

Correct Steps:

1. Download the OTA from here: -> https://developers.google.com/android/ota (current March update for my Pixel XL is Marlin, NOF27B)

2. Then I go into FlashFire and tell it to NOT do the OTA update.

3. Hit the circular PLUS button and manually select the file in my downloads folder. Leave most settings at default if you do not understand them...

4. Hit the lightning bolt button and it updates correctly after that point.

Easy Peasy. Have fun.

Edit:

Oh yeah, the problem... I think that update.zip is not fully downloaded when FlashFire catches it. Then it is not ready to be applied...

There might need to be a check put in to FF that checks for that or maybe a checksum...
[Paid Software Announcement and Discussion] gone_bush:
OTA install

Quick question: I have a Pixel XL, rooted (SuperSU), TWRP and ElementalX kernel so can I use FlashFire to install an OTA?

(Haven't found an answer via Google et al.)

EDIT: Corrected app name
[Paid Software Announcement and Discussion] Alxoom33:
Try FlashFire instead. I like using the factory image rather than the OTA.
[Paid Software Announcement and Discussion] deshwasi:
anyone know where the BLU R1 stores its downloaded OTA image? i am looking in flashfire but cant fidn the image file anywhere (checked in /cache among other places)
[Paid Software Announcement and Discussion] fernsruben:
[MENTION=631273]Chainfire[/MENTION] Would be great if you could introduce profiles. Say like I have a set of four zips I would normally flash every time manually by adding them to the queue every time a fresh flash is required. Would be feasible if we could save the order or set of zips or other combos so that we wouldnt have to manually select files every time we needed to flash something. :)
[Paid Software Announcement and Discussion] dahawthorne:
I've just tried Flashfire and was so impressed that I bought it... :)

One comment which I don't see in the thread. I used FF to install the new TWRP 3.1 on my Nexus 6. I saw the option "preserve recovery" but didn't realise exactly what it meant until I saw in the log "restoring backup" and I ended up with my original TWRP 3.0.2... duh... I unchecked the option and it worked perfectly.

Given that FF is clever enough to recognise the TWRP package as destined for the recovery partition, would it not be more sensible also automatically to uncheck the "preserve recovery" option when flashing recovery?
[Paid Software Announcement and Discussion] grimmaniac:
In that case you would end up with the stock recovery everytime you flash a factory image and forget to check that option. And since recovery updates are less frequent than security updates, I think it's more convenient like it is.
[Paid Software Announcement and Discussion] dahawthorne:
That's true, but my suggestion is specifically about flashing recovery and no other partition. If I'm flashing only recovery, then I clearly don't want the backup recovery to install over the top of the new one.
[Paid Software Announcement and Discussion] Ch3vr0n:
True, but afaik FF can't know your flashing a newer version or know what version you're using. Or FlashFire would have to get file name analyzing powers. And even that cab be easily bypassed by renaming an older version to a newer version than the official 'newest'. It's just not very practical I think.

Sent from my Nexus 6P with Tapatalk.
[Paid Software Announcement and Discussion] dahawthorne:
Yes, I get your points - thanks.

However, it appears to me that FF already has a mechanism for recognising the package, since when I chose to install TWRP the only partition presented for the installation was Recovery. If this is in fact representing what FF recognises (i.e. TWRP is a recovery package), and this is the only partition/image for installation, then surely it's possible for FF to disable the overwriting of the image I've just installed? It makes no sense to install a package and then to have it immediately overwritten with a backup, right?

Still, I make no big thing of this. Chainfire may have better things to work on, and now that I know (and I hope a few more people... :)) I'll be able to aoid the same pitfall in future.
[Paid Software Announcement and Discussion] ih8legal:
Same issue here so bump I guess
[Paid Software Announcement and Discussion] ih8legal:
Also if I navigate to this directory manually in flashfire it doesn't see it so maybe that's also an issue
[Paid Software Announcement and Discussion] dahawthorne:
I'm a FF noob, but I noticed that if you choose the wrong option for the package FF doesn't show it in the directory. If you choose "firmware' it should show. If not, try "zip".
[Paid Software Announcement and Discussion] MultiKoopa:
I am also having this problem. FlashFire keeps crashing whenever I try to generate actions for OTA on my Nexus 6P for the March security patch. Or more specifically, right after choosing to generate the actions, during the "uncrypting" process for the OTA. Anybody have any idea why?
[Paid Software Announcement and Discussion] NPOA556:
Same problem here with the February OTA. I have been watching this thread for over a month hoping [MENTION=631273]Chainfire[/MENTION] would provide an explanation or, better yet, a fix, but he has been silent on this particular issue.
[Paid Software Announcement and Discussion] Alxoom33:
I haven't had any issues. Working flawlessly with my Nexus 6 and Pixel C. Perhaps you might have a bad DL or are doing something incorrectly. I suggest further studying the OP.
[Paid Software Announcement and Discussion] g0d0fmischief:
Nexus 5x 7.1.1 Feb 2017 Patch, magisk v11, ElementalX kernel

Having the exact same problem trying to let it flash the March patch. I just recently started over and restored the factory image to my device that included the Feb patch. It's my first time trying to use flashfire to do this. From what I've read it should work. Just have to flash my kernel and magisk after it's done. Been putting off doing this since it's my first time at this, wanted to allow extra time in case something went badly to fix lol. And it didn't work at all lol.
[Paid Software Announcement and Discussion] g0d0fmischief:
What ROM and kernel are you using
[Paid Software Announcement and Discussion] Alxoom33:
Google factory source stock rooted Android 7.1.1 build N6F26U March patch, EX 4.18 kernel, debloated, themed dark glass for the Nexus 6; and Google beta Android 7.1.2 NPG05D build Jan 2017 release for the Pixel C, rooted, [MENTION=5480152]followmsi[/MENTION] 's kernel, Debloated and themed dark glass by me.
[Paid Software Announcement and Discussion] g0d0fmischief:
I'm having this very same issue. I see there's another post above that says that they have it working.

While I see several of us that have the same thing, crashing @ <10% in uncrypting when it goes to create the actions to flash the March OTA security patch.

I have to wonder if those of us who are having issues are running magisk, and maybe Alxoom33 isn't. From what I gather I should just have to reflash my kernel and/or magisk afterwards. Didn't see anything that said I had to remove it. I haven't gone to this length yet, but I may. Unless others are getting it to work with magisk running.

EDIT:

Can't paste the log file either, the flashfire directory doesn't exist for me.

[IMG="Image"]https://ibin.co/3G2tHJFoexSI.png[/IMG]
[Paid Software Announcement and Discussion] MultiKoopa:
I am NOT using Magisk or a custom kernel. Still having the problem.

Super SU, stock rom, twrp
[Paid Software Announcement and Discussion] Alxoom33:
Deleted post.

---------- Post added at 10:15 PM ---------- Previous post was at 10:06 PM ----------

Good point Mischief. I don't use Magisk or phh superuser, but when I did, FF did not work for me. I suspect that you will need to remove Magisk and re-root with SuperSU 2.79 SR3.

---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------

What is your setup, device, rom, kernel, SuperUser and any special additions, such as Magisk or Xposed?
[Paid Software Announcement and Discussion] g0d0fmischief:
According to the OP Jan 27 2017 the update brought support for magisk and magiskSU. However, there has to be an issue there for several of us with quite similar issues to be having this problem. Except for this one that says so far he doesn't have that running.
[Paid Software Announcement and Discussion] MultiKoopa:
Not sure what you mean by "setup" specifically

Nexus 6P, stock 7.1.1 (February security patch), stock kernel, SuperSU 2.79 (systemless), TWRP 3.0.3-0, absolutely nothing else (no Magisk or Xposed)

In fact, the only other thing I did to this phone is change the HOSTS file using AdAway.
[Paid Software Announcement and Discussion] g0d0fmischief:
It might not be magisk, but it is a systemless root app. Which makes your problem possibly the same as mine. Could be wrong but seems like a common denominator to me. I use AdAway as well. Not that it could be the issue
[Paid Software Announcement and Discussion] MultiKoopa:
What non-systemless root even is there anymore?
[Paid Software Announcement and Discussion] g0d0fmischief:
Guess you are right, these days I suppose. I'm tired, been at work for 13 hours. Grasping at straws.
[Paid Software Announcement and Discussion] grävling:
FF not able to generate flash file from nvidia 5.1 OTA update

I have an nvidia shield k1 tablet. It is rooted, running stock Android 7.0 released Feb 9 2017. There is a new OTA update of 7.1 available - it was released March 07 2017. Nvidia has recovery images posted here : https://developer.nvidia.com/gameworksdownload ... but the one dated "NVIDIA SHIELD Tablet WiFi Recovery OS Image 5.0.0" has the March 07 date. I don't know whether that means that this recovery is actually 5.1, but misnamed or if really is 5.0 as it says on the label. I have SuperSU Pro 2.79 installed. I've been away on vacation, without my PC, so I am late with installing the new 5.1 upgrade, as these things go.

I can write to my sd card, which is not mounted as adopted storage. I have titanium backup installed there and many files, so I believe that this requirement is satisfied. I have more than 1 GB free in /system and in /storage/emulated/0 (as well as on my sdcard) so I think that requirement is also met.

I thought I would give Flashfire a try. It correctly detected the OTA update, but when it tried to generate a file for me to flash, I got 'uncrypting OTA' (which, by the way I don't think is an english word, you want unencrypting or decrypting instead, perhaps) and then 'FlashFire has stopped'. I sent in feedback about what happened.

I am in no desperate hurry to install the 5.1 upgrade. I will wait around a few days and see if you want me to do anything to help debug this problem. Otherwise, I will just install the upgrade and then reflash SuperSU to regain root access.

Thank you,

Grävling
[Paid Software Announcement and Discussion] Ch3vr0n:
Uncrypting is a word. As chainfire stated it it means an 'unencrypted file on an encrypted partition'

Sent from my Nexus 7 (2013) with Tapatalk
[Paid Software Announcement and Discussion] RolfFrie:
flashfire adb wireless backup - how to

I tried to backup wirelessly using flashfire and adb. But after flashfire reboots the device it ist waiting fr adb. I tried to the command which was suggested by the flashfire app 'adb connect 192.168.178.0' but on the pc after a while I got the message that it could not connect. Which ist the same using ping.

The wirelss adb connection works fine if android is running.

What step is missing?
[Paid Software Announcement and Discussion] Alxoom33:
Try updating to 2.79 SR 3. Can't hurt! Did you update your busy box?
[Paid Software Announcement and Discussion] MultiKoopa:
I'll give that a shot when I can.

No busy box for me.
[Paid Software Announcement and Discussion] truckmann:
I'm having the same issue as others on my Nexus 6P where it crashes trying to decrypt an OTA. All stock phone with root.
[Paid Software Announcement and Discussion] grävling:
uncrypting

Thank you. Do you have a reference for that? One of the things I do is track new english coinages, for inclusion in the latest of English-Swedish and Swedish-English dictionaries. It's not showing up in the OED or Cambridge ED, or the Mirriam-Webster, even in the online sections for 'new words we have just noticed in the last few months' sections. Before I can stick it in _our_ new words heard, to track list, I need a better reference than 'Ch3vr0n on xda-developers told me so'. :cowboy:

'Uncrypting' had better be a verb, though. But it is likely that we have never needed a word for 'unencrypting a file on an encrypted partition' before Nougat, so this is a perfect time for a new coingage. This sort of thing makes me very happy. But I would love a reference.

Thank you.
[Paid Software Announcement and Discussion] g0d0fmischief:
It's not a standardized proper English word. It's a tech term specific to a specific decryption circumstance like this. So you can't use it in standard speak to replace the word decrypt
[Paid Software Announcement and Discussion] idnaidna:
Same problem with the "uncrypting" of the 7.1.2 beta 2 OTA on N5X (running 7.1.2 beta 1 stock and rooted).
[Paid Software Announcement and Discussion] dirtyreturn:
[MENTION=631273]Chainfire[/MENTION] - https://xdaforums.com/showthread.php?t=3576409

Could you please take a look?

I have a nexus 6p and I made a user error while using your app. didn't know if you could take some time to give me a hand.
[Paid Software Announcement and Discussion] eturk01:
6P and same crash uncrypting OTA 7.1.2 beta 2.

Seems flashing of OTA updates doesn't work. Abandoned feature? Only manually downloading entire ROM to flash works: https://amp.reddit.com/r/Nexus6P/comments/5z38qm/flashfire_crashes_when_trying_to_load_ota/
[Paid Software Announcement and Discussion] Squii:
[MENTION=631273]Chainfire[/MENTION]

I am having a problem flashing an OTA with flashfire. I am in the android beta program on my Pixel XL and am currently running 7.1.2 NPG05E which i flashed with flashfire originally on the device with no problems.

An update came through today for a new beta update 7.1.2 NPG47I which downloaded and flashfire automatically captured the update. Tried to flash and there was an error on screen that said something like download Initalization failed........

After reboot and failure root is gone. I reflashed SR3-SuperSU-v2.79-SR3-20170114223742 and root is back. Tried flashing about 3 times and same result. I even tried opting out of the beta program and flashing the 7.11 OTA and same failure.

I uploaded the lastlog to pastebin. pastebin dot com/QJzMPwYG

Thanks
[Paid Software Announcement and Discussion] asusgarb:
Hi. I am an happy owner of a Samsung Galaxy Note 10.1 2014. I'm using Lineage OS Rom, with SD card set as internal memory. This means I cannot flash from twrp because it is not recognised.

When I choose wipes in flashfire, which one is best for cache? Wipe cache or format cache?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Paid Software Announcement and Discussion] veez21:
Wipe cache ;)
[Paid Software Announcement and Discussion] vandyman:
I do not think there is an issue with Flashfire installing the OTA, It is the OTA that is at fault. Let me explain...

For the last four months, Flashfire has failed to install the otas, so I tried using TWRP and it failed as well. I had to use adb to get the job done.
[Paid Software Announcement and Discussion] vedantdude:
Would adb sideload work with a modded device?
[Paid Software Announcement and Discussion] vandyman:
Sure, I do not see why it would not.
[Paid Software Announcement and Discussion] vedantdude:
Just tried sideload with TWRP , but it said the zip was corrupt.

I had copied the zip from /data/ota_package to internal memory and then to pc. Did i do anything wrong?
[Paid Software Announcement and Discussion] Squii:
Flashfire is working fine I just confirmed. I previously installed a 7.1.1 update and a 7.1.2 beta with flashfire and never had a problem. I just wiped my phone and installed nof27b 7.1.1 and re rooted the phone. After that flashfire installed the NPG47I 7.1.2 beta update fine. In the log file for flashfire there were a lot of errors referring the the "system". My novice guess is something I installed modified the system causing the problem.
[Paid Software Announcement and Discussion] Ch3vr0n:
The only ota's for me it fails to install are the ones Android downloads. Grab the (incremental) OTA from droidsec and it gets flashed just fine for me.

Sent from my Nexus 6P with Tapatalk.
[Paid Software Announcement and Discussion] adrman:
I've been using the full OTA dl from Google and it also works correctly. I wasn't aware that droidsec had an incremental. I'll give it a try for April's update.
[Paid Software Announcement and Discussion] MultiKoopa:
http://www.droidsec.org/nexus/

doesn't look it has any incremental updates for the last few months :\
[Paid Software Announcement and Discussion] Ch3vr0n:
I grab them there or from the OTA ref sticky in device section whoever is first. Or i report an OTA myself

Sent from my Nexus 6P with Tapatalk.
[Paid Software Announcement and Discussion] bailey boy:
Nexus 5x here. Flash fire crashing during the uncrypting stage every time.
[Paid Software Announcement and Discussion] g0d0fmischief:
Hoping chainfire pops in soon, the more and more who pop in and add they have this issue, the more I'm thinking it might be something he can fix. Have you been able to use it for this purpose successfully prior to now
[Paid Software Announcement and Discussion] bailey boy:
Yah, I've changed over to Magisk since then and started using Lspeed. That's the only changes on my end.

OTA uncrypting is crashing FF around 80-90%
[Paid Software Announcement and Discussion] skiely666:
Flashed android O successfully​ but root failed..

Nexus 6P

Flashfire 0.53
[Paid Software Announcement and Discussion] g0d0fmischief:
Hmm I'm using magisk as well. This seems to be a common denominator amongst "most" that are having an issue too. You should try to uninstall it, then try it.
[Paid Software Announcement and Discussion] Chainfire:
The uncrypting issue is not related to Magisk. I'm not sure what it is related to. I caught the exception before I went on vacation last month, but it seems I never published that. I'm not sure if what I caught actually fixes the problem or just hides the symptom. I need to do a round of tests on it.