Has anyone tried using latest flashfire to upgrade NOF26V?

[bush911]

will this keep the phone rooted like it does ever.
to flash the full image and root again is not very easy for me

 

[bush911]

It seems that no one is gonna take a try, I will and revert.

 

[bush911]

Just finished upgrading via flash fire. It worked

 

[sliding_billy]

What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?

 

[bush911]

V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.

Tarp was removed, now no recovery available

What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?

 

[sliding_billy]

V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.

Tarp was removed, now no recovery available

Thanks for investigating. I would have thought you would flash the OTA. Doesn't seem to improve the process if recovery is removed but root isn't.

 

[bowyerv]

I did. Didn't work. Downloaded OTA. Flashfire kicked in (I'm using FlashFire Pro v0.55.1). It appeared to process the OTA. I flashed. OTA was not successful. I re-flashed SuperSU to restore root.

 

[josephpalozzi]

Flashfire works great

I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.

 

[Haz3]

I just retook the 7.1.2 OTA but did not restart after download. Opened FlashFire it autodetected the OTA, offered to install and I accepted. Everything went fine. Still have Su and on Sharkey kernal

 

[llong31]

I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.

I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?

edit: I was able to update to the Feb security patch, but lost twrp in the process. I tried the steps above again, this time I was presented with the ota available pop up screen which I didnt get the first time around. Even with the "preserve recovery" option ticked, it didnt preserve it. I get "no command" when I try to boot into recovery.

 

[sliding_billy]

Just used TWRP sideload, TWRP IMG, TWRP install and SuperSU install to update XL to February. About to do Pixel. I've got FashFire installed and waiting until it is working in a more stable fashion. No point in fixing what ain't broke for me right now.

 

[mac796]

I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?

There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today

 

[llong31]

There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today

Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.

 

[mac796]

Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.

You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system

 

[llong31]

Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.

You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system

I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.

 

[mac796]

I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.

Maybe I'll try the auto detect see if that helps, in not sure if L speed does. I think most stuff for pixel is systemless

 

[IlyaKol]

Sorry to bump this old thread...how long were ya'll phones 'black' during Flashfire? Mine has been black (but still connected to storage via PC so it's not dead) for like 25 min.

EDIT: After almost an hour, I gave up. I force rebooted the phone hoping Flashfire didn't do anything and it looks like it didn't. Phone booted fine. Going to use the old method and sideload the OTA.

 

[alluringreality]

I've used the OTA file from the typical update with FlashFire the past couple months, and I used a file downloaded from Google once before (I don't remember if it was on the phone or a flash drive). The screen didn't stay black very long the times I've used it, I'd guess less than a minute, so apparently something didn't work correctly. Looking through the app and documentation, I'm not sure what you meant by "still connected to storage via PC".