Database Users

How to update firmware if you've already flashed TWRP

I figured out how to update after flashing twrp. Maybe obvious to some but I've seen questions about it.
The zip in the "Convert CA to WW" thread has the stock rom in a zip file. Open it and inside is a recovery.img file in it, extract it to your adb folder on your PC.
Download the firmware update from ASUS official site and save to the root of your sd card or internal storage (it will recognize both.)
Reboot into fastboot on your device.
fastboot flash recovery recovery.img
When that finishes reboot and your phone should find the update and ask if you want to install. Do so. You may need to power cycle first.
When you're done you can reflash TWRP.
Once you have TWRP you can flash Magisk or SuperSU as you see fit.
It's painless.

An old post from you, but thank you. This was really easy. I've spent 2 days trying to figure out how to upgrade without restore stock rom, boot etc. and lose all data. I was about to give up when I saw this post, I didn't expect it to work - to easy. But I could give it a try.
This was painless.
Then it took me 3 hours to figure out how to reinstall twrp again, it wasn't just to flash and reboot I had to boot directly into recovery after flash. But that is another story.

Thanks, you just saved me some time!

Kasdarack said:
I figured out how to update after flashing twrp. Maybe obvious to some but I've seen questions about it.
The zip in the "Convert CA to WW" thread has the stock rom in a zip file. Open it and inside is a recovery.img file in it, extract it to your adb folder on your PC.
Download the firmware update from ASUS official site and save to the root of your sd card or internal storage (it will recognize both.)
Reboot into fastboot on your device.
fastboot flash recovery recovery.img
When that finishes reboot and your phone should find the update and ask if you want to install. Do so. You may need to power cycle first.
When you're done you can reflash TWRP.
Once you have TWRP you can flash Magisk or SuperSU as you see fit.
It's painless.
Click to expand...
Click to collapse
Will this recovery work for upgrading nougat to oreo?

Em Kay said:
Will this recovery work for upgrading nougat to oreo?
Click to expand...
Click to collapse
You need to upgrade to latest N - ...14.2020.1712.85, once you do that you should get Oreo as FOTA after reboot

DanFreed said:
You need to upgrade to latest N - ...14.2020.1712.85, once you do that you should get Oreo as FOTA after reboot
Click to expand...
Click to collapse
Thanks, man.
Can I manually update with the recovery by downloading the rom?
I think, the FOTA won't arrive as I've rooted my phone.

Em Kay said:
Thanks, man.
Can I manually update with the recovery by downloading the rom?
I think, the FOTA won't arrive as I've rooted my phone.
Click to expand...
Click to collapse
When you flash stock recovery and update you unroot, so you will get FOTA. Just update to Oreo and then flash twrp and Magisk (or whatever you use) again.
I am rooted and updated to Oreo then chose updates involving battery improvement and/or system stability (downloaded to external sd), after installed the last update I flashed twrp and rooted again.
You need to flash stock recovery before update. The phone will find the updated with custom recovery but update will fail.
The site I downloaded stock recovery from is down so you have to search for it, or download RAW stock rom and extract the recovery from it

DanFreed said:
You need to flash stock recovery before update. The phone will find the updated with custom recovery but update will fail.
The site I downloaded stock recovery from is down so you have to search for it, or download RAW stock rom and extract the recovery from it
Click to expand...
Click to collapse
Anyone know where I can get stock recovery or how to extract from stock image from the ASUS site?

derbend said:
Anyone know where I can get stock recovery or how to extract from stock image from the ASUS site?
Click to expand...
Click to collapse
Seems like Mega is up again. You should find stock recovery here
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB

DanFreed said:
Seems like Mega is up again. You should find stock recovery here
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!xhVEhCjB
Click to expand...
Click to collapse
Thanks! I ended up having to use the 11.41.87.2 recovery in order to flash a Nougat update - it wouldn't work with the older recoveries.

Update Failed WAS-LX1

Hello,
today i wanted to update my *rooted* WAS-LX1 to B182, so i downloaded the update.zip and tried to flash it with FlashFire.
Then my phone booted in Error Mode. So i tried to boot in Fastboot mode, and it worked. So i flashed TWRP and now i want to install Stock firmware again, but i don't know which file i should flash. I've got 3 files called update.zip, update_data_full_public.zip and update_full_WASL21A_hw_eu.zip.
I hope you can help me.
Zillinda

Zillinda said:
Hello,
today i wanted to update my *rooted* WAS-LX1 to B182, so i downloaded the update.zip and tried to flash it with FlashFire.
Then my phone booted in Error Mode. So i tried to boot in Fastboot mode, and it worked. So i flashed TWRP and now i want to install Stock firmware again, but i don't know which file i should flash. I've got 3 files called update.zip, update_data_full_public.zip and update_full_WASL21A_hw_eu.zip.
I hope you can help me.
Zillinda
Click to expand...
Click to collapse
To update my rooted phone to B182 I had to download the full package (2.3gb, including update.zip and update_full_WASL21A_hw_eu.zip). I was not successfull in updating via TWRP. I updated via the official system menu so I don't know how exactly it was applied. According to other guides (http://www.stechguide.com/tag/was-lx1c432b182/ for example) it should be update.zip first and update_full_WASL21A_hw_eu.zip second, without a reboot. Let us know how it worked out...

garris_bibop said:
To update my rooted phone to B182 I had to download the full package (2.3gb, including update.zip and update_full_WASL21A_hw_eu.zip). I was not successfull in updating via TWRP. I updated via the official system menu so I don't know how exactly it was applied. According to other guides (http://www.stechguide.com/tag/was-lx1c432b182/ for example) it should be update.zip first and update_full_WASL21A_hw_eu.zip second, without a reboot. Let us know how it worked out...
Click to expand...
Click to collapse
Unfortunately it didn't work. The only thing i can do is boot in the TWRP recovery. Is there a way to flash the stock rom with fastboot?

Zillinda said:
Unfortunately it didn't work. The only thing i can do is boot in the TWRP recovery. Is there a way to flash the stock rom with fastboot?
Click to expand...
Click to collapse
I only tried flashing the update via sideload and recovery and it didn't work (http://rootmygalaxy.net/flash-ota-firmware-updates-using-adb-fastboot-commands/). Maybe you are lucky. Problem is, I'm quite new to this stuff, hopefully someone else can help out.

Can someone please provide us with a link for the stock recovery?

kazzot17 said:
Can someone please provide us with a link for the stock recovery?
Click to expand...
Click to collapse
https://mega.nz/#!V3AwUI6K!mcqlNCwcyE71MroUZuP9w-bNDhgt3MGzz0svgHUY8Ow

By the way, i solved the problem. I downloaded HuaweiUpdateExtractor for extracting the .img files from the update.app and i flashed them with fastboot.

Nice, congrats

Android Pie 9.0 root possible ??

Hi guys, I had read many posts about rooting essential phone. But those articles aren't mention if it is suitable for android Pie version. Is there anyone knows how to root my essential phone with Pie 9.0 ??

See this thread.

prabs99 said:
See this thread.
Click to expand...
Click to collapse
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:

Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
eric672913 said:
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:
Click to expand...
Click to collapse
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
Click to expand...
Click to collapse

prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
Click to expand...
Click to collapse
Got it , I will try this. Thanks so much:laugh:

eric672913 said:
Got it , I will try this. Thanks so much[emoji23]
Click to expand...
Click to collapse
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Sent from my [device_name] using XDA-Developers Legacy app

eric672913 said:
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Click to expand...
Click to collapse
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.

NaterTots said:
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.
Click to expand...
Click to collapse
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?

jwinstonsf said:
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?
Click to expand...
Click to collapse
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.

NaterTots said:
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.
Click to expand...
Click to collapse
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app

eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Click to expand...
Click to collapse
Boot.img

eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Boot image should go to the boot partition.

Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
When installing Magisk zip, Sideload it.

manr1mg said:
Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
Click to expand...
Click to collapse
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??

eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.

After you flash twrp, go into twrp, install boot.img, MAYBE make sure system is mounted THEN install magisk. I've read some of the red errors happen regardless so I'd just fire up the phone afterwords and see if it works.

eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.

luisoman2000 said:
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.
Click to expand...
Click to collapse
Thanks for your reply. I am sure that I check "boot" when flashing stock img. Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.

manr1mg said:
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.
Click to expand...
Click to collapse
Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.:fingers-crossed:

Painful thread to read.

sideload installation keeps failing.

I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.

TENlll423 said:
I'm trying to revert my oneplus 5 back to stock. I done all the steps got stock recovery installed. When I attempt to sideload original oos through adb sideload it keeps failing at 46%. Any advice would be very appreciated.. I've read so much and tried so many different things. I am completely stuck.
Click to expand...
Click to collapse
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...

strongst said:
Which rom do you want to flash and from which rom are you coming? Maybe there are some updates between you're missing...
Click to expand...
Click to collapse
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.

TENlll423 said:
I got the phone from a friend and it has been completely wiped and formatted through TWRP. He did have a nougat custom ROM on it prior to that.
I tried to sideload to it with TWRP and it wouldn't work. I followed directions from a website that explains how to revert your op5 back to stock using stock recovery. I was trying to put the original oxygen OS ROM on it that came with the phone using the stock recovery and adb and fastboot. I'm thinking maybe I possibly downloaded the wrong OOS version. Who knows. Lol .
It had nougat Pure FusionOS 7.1.2. encrypted...SuperSU root and TWRP blue spark.
Now all it has is stock recovery with No OS
Would like to get OOS pie on it eventually.
Click to expand...
Click to collapse
Do you want to have root along with your new rom? And which rom do you want?

strongst said:
Do you want to have root along with your new rom? And which rom do you want?
Click to expand...
Click to collapse
New OOS 5.1 7. With Magisk v18 would be great.

TENlll423 said:
New OOS 5.1 7. With Magisk v18 would be great.
Click to expand...
Click to collapse
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back

strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?

TENlll423 said:
Thank you... can I do all that by installing TWRP with fastboot and then sideload 5.1.4?
Click to expand...
Click to collapse
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Ok I'll give it a try thanks. And merry Christmas

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
How can I transfer 5.1.4 to phone from pc? My phone is completely wiped. Computer won t recognize phone in PC file explorer? Also, Will I have to fastboot flash recovery twrp img to get new twrp to work? Sorry for all the questions.

strongst said:
There's no need of sideload anything when you flashed twrp through fastboot. Just copy the roms on the device and flash through twrp
Click to expand...
Click to collapse
Keep getting failed to mount/system/ invalid argument in thwrp. Can't transfer rom from pc. Its showing up in PC file explorer but won't transfer

strongst said:
You need to flash 5.1.4 at first to create the vendor partition like described here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 then you can flash 5.1.7. If that fails you need to flash 5.1.5 and 5.1.6 after 5.1.4 and before 5.1.7. You'll find older versions here
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Also you need an actual(latest codeworkx for example) twrp recovery https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
Please report back
Click to expand...
Click to collapse
Can't copy anything to phone. says there's no system and I even tried sideloading rom and said it corrupt
I think it's done. It's beyond me.. I've read so much trying to get this thing fixed I can't even see straight.. lol

It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy

TENlll423 said:
It lets me copy small files over like magisk v18. It works. When I attempt to copy 5.1.4 rpm over it says device stopped not responding. Crazy
Click to expand...
Click to collapse
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?

I'm redownloading 5.1.4
I tried to copy over another ROM I had and it started to copy over so it is the file that was corrupted.
Thanks again I really appreciate it ?

strongst said:
You need to mount internal storage, not system. Is your twrp updated to latest codeworkx?
Click to expand...
Click to collapse
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.

It won't install no vendor to mount or something. I'm done... Thanks for everything anyway.

When I reboot to recovery. This what it says.

TENlll423 said:
Second to latest... I have
TWRP-3.2.3-0-20181031-codeworkx installed.
Latest one wouldn't boot.
Click to expand...
Click to collapse
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.

strongst said:
I'm using twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
You have the same? The vendor partition will be created with 5.1.4.
You can go(in twrp) to mount - > vendor. But the recovery should mount it automatically when it's created by flashing 5.1.4.
Click to expand...
Click to collapse
Yeah that's the same one I'm using I'm thinking maybe I don't have TWRP setup right is there any settings I'm supposed to go into?
Even when I check off everything in advanced wipe and do a wipe it comes up fine all the way to the end and then it says failed to mount vendor (invalid argument)
I liked everything again in TWRP I went to flash 514 and it works all the way up to the end and fails to mount vendor invalid argument.
Somehow I need to activate the vendor partition or something.
well I'm going back to reading like a madman and figure out if anybody else had this problem online. Lol thanks

Problem flashing stock image

I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?

You already took the November OTA or are you still on October?

ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November

Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.

I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.

Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks

Yes.... fastboot flash boot boot.img

ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help

ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?

I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.

ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?

TWRP doesn't work with Q. Just use stock recovery to sideload.

ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images

Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.

The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk

Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?