[OnePlus 8T Guides, News, & Discussion] BillGoss:
Well, trying to keep root with the KB2003 incremental update didn't work for me. Here's what I did.

**F15i**

I found that under /data/ota_package/OTA there was an incremental (~380 MB) install zip called my_manifest_kb2003_11.f.15_2150_202212052235.44.04e8330b_patch.zip/']my_manifest_KB2003_11.F.15_2150_202212052235.44.04e8330b_patch.zip

It had showed up overnight and About Device said it had failed extraction. (Screenshot) This isn't surprising since I'm both rooted and use Orange Fox.

But I wanted to use Local update rather than Auto update (the only option available).

So I copied and then deleted the files under data/ota_package and backed up F13 data (using OF 14.01).

When I had finally got rid of the pending update then I used method B.2.3 to do the update.

...

And the phone wouldn't boot!

I kept getting sent back to recovery.

I then tried flashing the partitions in fastboot[d] as I had used payload-dumper to create full image files from F13+F15i but that gave the same result.

...

So I went back to F13 by flashing the logical partitions on the F13 slot and finally got the phone working again on F13.

I then saw that Oxygen Updater now had images available so I downloaded a full image (I call it F15ou).

I ended up not using the Oxygen Updater download because I was concerned that all the logical partition images are different between F15i and F15ou (see **F15i vs F15ou** below).

**How I finally updated**

After a while back on F13 I again got a notification of an update. This time I decided to not try to keep root (as I already had a copy of the stock boot and Magisk patched boot from my previous installation attempt) but to let the system install the update.

So I restored the stock boot (I was rooted) and recovery (I was using Orange Fox), turned on Auto update in Developer options and let the update download and install.

I turned Airplane mode on before rebooting the phone and it came up cleanly on F15 (security patch date of 5-Dec-22).

I then used fastboot boot <Magisk patched boot image> and then did a Direct install in Magisk and rebooted again and turned off Airplane mode.

And now I'm finally on F15 with root and Orange Fox.

I then dumped all the partitions that get updated and compared the md5s of the logical partitions of F15 (working) and my initial set derived from the incremental update and, while the image files are the same size, they have different md5s. So something in my initial process is flawed.

I couldn't compare the physical partitions because the sizes created by payload-dumper are smaller than those you get when you dump a partitions. Even if the contents were the same, the md5s would be different because trailing 0 bytes change the md5sum.

**F15i vs F15ou**

I used payload-dumper to create full image files of F15 from F15i + F13.

I also used Oxygen Updater to get a full update (F15ou) and used payload dumper to extract the images.

I compared the resulting images and found out that:

- F15i and F15ou files have exactly the same size

- F15i and F15ou physical partition files have the same md5 - they are therefore identical

- F15i and F15ou logical partitions all have different md5s[/icode]