yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T Guides, News, & Discussion] BillGoss:
The problem is that delta updates require you to restore both recovery and boot partitions to stock otherwise the installation fails.

The process I describe works for both full and delta updates. But, like I said, if you know that the update is a full OTA, then you can simplify the process and, <edit>if you know it's always going to be a full update, then<end-edit> you can use your "usual" process.

PS: this is a source of confusion because the BA ROMs are always full updates, while the AA ROMs are typically delta updates.

So what works for one user will not work for another even though they are both running OOS on an 8T.

And then there's the difference between letting System update download and install versus manual install, which creates another place for confusion is you just talk about "install update" instead of being specific as to the exact method.
[OnePlus 8T Guides, News, & Discussion] The Apostle:
I guess I don't know why people wouldn't simplify the process, download the full ROM, and eliminate steps. It's worked for years on OnePlus devices across android 9, 10, and now 11.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Because there's often no AA full rom to download. They can take months to show up while the delta is available immediately from Google.
[OnePlus 8T Guides, News, & Discussion] The Apostle:
I've never had that issue. Between XDA and OnePlus forums, someone has always posted a host link... Since OnePlus stopped around October.

Regardless, good info you posted.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Thanks. By the way I edited my first reply to you because your "usual" process only works if you are always using full updates.
[OnePlus 8T Guides, News, & Discussion] Feduz:
Hi!

I'm using this method for the update:

Without TWRP

Manually download the update (from whichever source you use) to /sdcard

Magisk>Uninstall Magisk>Restore images - this restores the stock boot image whilst keeping Magisk

Install the update in System Update>Gear icon (local install)

Magisk>Magisk Install>Install to inactive slot

Reboot system

2nd point, if I tap on uninstall magisk, It tells me that I don't have a backup original boot image, how can I proced?

Thanks
[OnePlus 8T Guides, News, & Discussion] BillGoss:
You can't proceed if your update is an incremental update. Otherwise you can go ahead.

You'll need to find a copy of the stock boot image to restore it before installing the incremental update.
[OnePlus 8T Guides, News, & Discussion] Feduz:
I'm on 11.0.11.11KB05BA, to 11.0.12.12. so I need to flash the original boot image via ADB/fastboot? Then proceed with point 3?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
You tell me. I use AA, not BA. If you don't know what type of update it is, then you need to replace stock using whatever method you like.
[OnePlus 8T Guides, News, & Discussion] Feduz:
It's a full update, about 2.8 GB. I'll flash the stock boot.img so
[OnePlus 8T Guides, News, & Discussion] Qnorsten:
if it is a full update you don't need to restore anything before installing it.
[OnePlus 8T Guides, News, & Discussion] Feduz:
Correct, I skipped this part in the first post. I've done the update and then installed via magisk. All went good. Thanks
[OnePlus 8T Guides, News, & Discussion] rmroot:
What should I backup using TWRP before a custom rom update and before a jump from a custom rom to another?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Read the TWRP OP posts for the answer.

https://xdaforums.com/t/recovery-11-official-teamwin-recovery-project-8t-kebab-2022-01-03.4302449/
[OnePlus 8T Guides, News, & Discussion] lvints:
@BillGoss

I will be a user of an OP 9R in a few days and I saw that it shares the same version of TWRP.

In the 9r forum I still haven't found a well explained tutorial and if it's possible.

The instructions you put here allow you to update OxygenOS on 8T and keep root/TWRP, right? Would they be applicable to the 9R as well?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
I know that the 8T and 9R share similar architecture so the process I've described may work on the 9R, but I can't confirm this.

I do know that as one point we had a common TWRP version for both the 8T and 9R, but that's no longer the case and there's no official TWRP for the 9R.

So, from my perspective, you're on your own on this. If it works, great. You may want to post your process and results in the 9R forum, but not here (this is strictly an 8T forum and thread).
[OnePlus 8T Guides, News, & Discussion] JimDandy68:
Thanks very much for this thread, @BillGoss. Just easily upgraded 11.0.12.12.KB05AA to 11.0.13.13.KB05AA with your methods using fastboot boot trwp.xx.img from bootloader mode and simply reinstalling Magisk after letting the update run (airplane mode on, as you suggest). I had just upgraded Magisk before the update, so had the latest apk handy in my downloads.

To backup your boot in TWRP (first know your active slot), you can get to a terminal in the TWRP/Advanced menu. I use the same commands you list in your "Use a CLI" instructions.
[OnePlus 8T Guides, News, & Discussion] Feduz:
Hi, I've updated correctly to the latest OOS, should I need to update Magisk? or will be fine this version?

View attachment 5549027
[OnePlus 8T Guides, News, & Discussion] Gandalf19:
Ok. Thank you. Now I have to find a copy of the firmware.... :)
[OnePlus 8T Guides, News, & Discussion] BillGoss:
You have to have an actual OTA zip. You cannot use the files from https://xdaforums.com/t/firmware-oneplus-8t-kebab-ddr0-ddr1-release-updated.4299231/ because they don't include all the relevant images you need.

The upgrade from OOS 11 to 12 is about 3 GB.
[OnePlus 8T Guides, News, & Discussion] Gandalf19:
Here I found right firmware full OTA EU.

Thank you
[OnePlus 8T Guides, News, & Discussion] JimDandy68:
Sorry if this is answered somewhere in the thread. Search This Thread doesn't seem to work. Any advice for what to do if upgrade went OK (or seemed to) but safetynet checks fail (using USNF 2.3.1 MOD)? I had the original USNF 2.3.1 installed during the upgrade and missed that I needed to use the mod until after rebooting and turning off airplane mode. Thanks
[OnePlus 8T Guides, News, & Discussion] Gandalf19:
Ok.... All right.

If it is useful to others, I will tell my experience

I had android 11.0.13.13.KB05BA on OnePlus 8T EU with root.

I updated following the guide in point B.1.

Updated to C.16. I could not update with automatic update because it was too slow (problem known to Oneplus). So I got the firmware from the only link found on the internet with the complete C.16 EU rom HERE

Then from C.16 to C.20 with built-in System Update tool (Settings>About device>Software update).

Only problem detected with the fingerprint, but I solved it by updating the magisk Universal SafetyNet Fix module to version 2.3.1 HERE

Thanks again to @BillGoss for the work and assistance.

Now the smartphone does not detect any other updates, but I know that the latest version is C.33.

Without waiting, can I download the C.33 full OTA with Oxygen Updater and update always following the guide in point B.1?

Thank you very much
[OnePlus 8T Guides, News, & Discussion] Crom4rtie:
Hi, im having trouble understanding the steps. im currently on 11.0.13.13 unlocked bootloader and rooted. if i want to upgrade to 12 i download the full zip (C33) from oxygen updater and follow the steps b.2.1 right?
[OnePlus 8T Guides, News, & Discussion] mingkee:
Use local update (only available on EU OOS11)

Extract the ROM in order to get boot.img for patching
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Yes, that's right.
[OnePlus 8T Guides, News, & Discussion] Crom4rtie:
I tried updating with the full zip c33 through local upgrade and followed the steps exactly as in b.2.1 after rebooting i was still in android 11 rooted. i checked fastboot which slot im on and tried booting the other slot without success -> i always got back to my origin slot (in this case b) Any ideas?

EDIT: i was stupid, was using a very old version of magisk which apparently wasnt compatible with android 12. i Upgraded to the latest magisk stable and it worked well (b.2.1) thanks for the help
[OnePlus 8T Guides, News, & Discussion] BillGoss:
That's odd!

I would try using MyApplication2 (the OOS 12 local installer linked in B.2.1) - something I've not done previously (using MA2 on OOS 11).

But you'll be on your own at that point and if it all goes wrong you'll have to use MSM to get back to a working phone. And that process is OT in this thread.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
I've updated the OP to cater for installing TWRP permanently. See new section A.2.1 and the updated B.2.1
[OnePlus 8T Guides, News, & Discussion] Gandalf19:
Hi.

Only for information.

If you are on C.20 and you perform a local update (Settings>About device>Software update>Local install) of C.33 using full OTA image, downloaded with Oxygen Updater, you loose root because at the end of update, smartphone reboot independently and you cannot do anything.

But I re-rooted the phone following the guide in point A.1.2. (y)

Thank you again @BillGoss
[OnePlus 8T Guides, News, & Discussion] mingkee:
Regaining root is pretty easy.

All you can do is

1. extract boot.img from ROM

2. transfer boot to the unit, patch the boot with Magisk, and transfer back to host computer.

3. reboot in fastbootd (adb reboot fastboot)

4. flash patched boot

5. reboot and done
[OnePlus 8T Guides, News, & Discussion] MystikalE:
I'm new to this.

Got my bootloader unlocked, now what? install TWRP and then Magisk? Or should I use only one of them? can you guys tell me the proper way to do so?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
There's no "proper" way. There are different ways and it's up to the user's preferences what they do.

That's why there are options in the OP.
[OnePlus 8T Guides, News, & Discussion] mingkee:
Magisk patched way would be easier for OTA and regain root thereafter
[OnePlus 8T Guides, News, & Discussion] MystikalE:
Aight, then I'll use Magisk to root my 8T with, what are some things I should pay attention to?
[OnePlus 8T Guides, News, & Discussion] mingkee:
The instruction on the first post tells everything.

However, do not use Magisk OTA method but you should use "kernel extraction" method.
[OnePlus 8T Guides, News, & Discussion] heyChristo:
It keeps telling me FirehoseReadData Failed, Erno: 31 after 14 seconds. Readback boot_a Failed.

EDIT: Never mind, found the uploaded image and flash patched that one! You guys are epic for the tremendous amount of work already done for this device. Is there a telegram group for development?
[OnePlus 8T Guides, News, & Discussion] BillGoss:
I can't help you with that. If you can't fix it, you'll need to use one of the other methods, including looking for a thread that's posted the boot image you need.
[OnePlus 8T Guides, News, & Discussion] heyChristo:
Thanks Bill, just edited my post as you responded here. I did find the boot image and am back in business. Thanks for your prompt response and all the documentation you have done here!
[OnePlus 8T Guides, News, & Discussion] MystikalE:
Okay, will this method let me keep use OTA updates in the future as usual, as well as not deleting my current data?

I do not want a method that requires to reset my device.
[OnePlus 8T Guides, News, & Discussion] rmroot:
Bill I was using crdrod 7.14 (oneplus 8t) and I updated the rom to 7.18 using the internal updater (in system options) but at first boot I get a crdroid logo bootloop, I don't know why but it happens everytime I flash/install/update crdroid (this is the only rom I ever used in 8t). I had magisk installed. Do you know what could be the problem? I also disabled pin before upgrading. I don't know if it's a rom problem or I miss something, I flashed roms for years but since I got oneplus8t, I have custom rom installations/upgrading problems most of the times.

Edit: I switched slot and I rebooted to old 7.14 system but I'd like to know where is the problem
[OnePlus 8T Guides, News, & Discussion] moordi:
Apologies for being a bit OT, but I've encountered a very odd situation upon upgrading from 11.0.13.13 to 11_C.33 that I thought might be of interest here.

At the start, I was already unlocked and rooted, and enjoying the ever present warning message at every reboot. However, and this is the strange part, after the upgrade to 12.1, the unlocked bootloader warning message is gone. My phone is still unlocked, rooted and passes all safetynet checks. In fact, after sorting out the inevitable issues caused by switching from OOS11 to OOS12, everything works as expected.

Has anyone ever heard of this happening before? As far as the warning message is concerned, my phone thinks it's locked.

To get back more on topic, I didn't do anything special with Magisk before the upgrade from 11 to 12. I had downloaded a copy of the full upgrade package and forced a local upgrade, but that was the only unusual step I took. Obviously, I lost root when it rebooted, but it's easy enough to re-root with Magisk.

FYI, there was no "reboot" option at the end of the local upgrade. Instead, it merely went through an "extraction" and then offered me the option to "install." However, upon clicking the "install" button, the phone immediately rebooted. So, I assume it had actually already installed. I probably should have ignored the "install" step to avoid rebooting the phone in order to go back to Magisk and follow the instructions in the OP.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Unfortunately I can't help you. I've not used custom ROMs on my 8T other than to do some early testing of TWRP 11 last year.

I would hope that you could get the necessary help with this in the crdroid thread.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
The "missing" unlocked warning is normal for OOS 12, so there's nothing to worry about there. You can still check the unlock status by booting into bootloader mode.

If you restore your phone back to OOS 11 the unlocked warning will be back.
[OnePlus 8T Guides, News, & Discussion] moordi:
I just wanted to confirm that the "new" OOS12 process for updating, following B.2.1 logic with the built-in system update app, has changed slightly. There is no option to reboot after installation. Instead, the option is to "install," which appears after extraction and verification. I suppose the terminology makes sense in a A/B world, since OOS12 is extracting the update to the inactive slot and won't be "installed" until one reboots to that slot.

Nevertheless, it may be confusing/frustrating to users trying to follow the instructions, since there is no longer any step where you obviously DO NOT REBOOT. Instead, the instruction to those using this method should be DO NOT INSTALL. Everything else works exactly as described under B.2.1.

As an aside, I was notified of an available update (for C.35) from the Oxygen Updater app and went ahead and downloaded the full, not incremental, update zip. Then, soon after that, OOS12 notified me of the same update. When I checked the "About device" status it offered an incremental OTA update, which I thought was odd, but decided to check it out anyway. It went through the download and extraction steps, but failed somewhere along the way and dropped the phone into recovery mode. That wasn't too surprising, since my phone is rooted, but it was surprising that OOS12 thought it could get away with an incremental update anyway. In the past, it would detect root and force a full update. Interestingly, after reverting back to the previous install and re-rooting with a copy of the Magisk patched boot image, the OTA update offer vanished. It said I was up to date with C.33. I guess Oneplus thought better about updating my phone again. In any case, I already had the full update zip and proceeded with the local install, as described above.

Hopefully, my experiences will save someone else from losing root and having to re-root the long way.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
I've been waiting for an update so that I could try your method.

Unfortunately, it doesn't work for me. And the reason is that when I reboot into fastbootd (step 6), I'm still on the same slot as I started. I should have ended up on the updated slot.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
You might want to go back and read B.2.1 carefully. Specifically, you do NOT use the system update on OOS 12, but the My Application2 app.

And you do install the update and you don't reboot once the installation has finished.

Also B.2.1 is a subsection of B.2, so I suggest you read it again, starting from B.2.
[OnePlus 8T Guides, News, & Discussion] mingkee:
I have completed mine to C.35 and regained root

Everything looks good so far
[OnePlus 8T Guides, News, & Discussion] moordi:
I think my comment may have mislead you. I followed the logic/steps you supplied in B.2.1, but I used Oneplus' built-in method for updating via a local install. The procedure works perfectly well and is much simpler than the rather involved approach you outlined in B.1. I'm not suggesting there's anything wrong with the procedure in B.1 and, in fact, it may be the only reliable approach for some setups. I only wanted to note that the built-in Oneplus system update tool worked extremely well with your B.2.1 instructions, with the lone exception that I did not tap "install" before executing the steps for patching the boot image via Magisk.

I don't know anything about the My Application2 app. I'm perfectly aware that you recommend using it with your B.2.1 procedure. However, I personally found it unnecessary. I took the route I did because the Oxygen Updater app sort of pushed me in that direction after I downloaded the C.35 update. I'll admit I did what I did, in part, because I'm lazy. However, I am very good at reading and following instructions. I understood exactly what I was doing and took a small risk. The fact that it worked pleased me enough to share my experience here.

To be perfectly clear, I think you've done an incredible job of summarizing the various paths to safely update under OOS11 and OOS12, and the community of 8T users is in your debt. Nothing I've described should be construed as anything but complimentary and complementary to your good work. I'm certainly not suggesting you need to emend anything.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
Wow! If you used the system updater and were able to use the Magisk install to inactive slot, then things have changed!

It used to be that doing it that way would create a mess. If that's no longer the case, then we might be able to collapse B1 and B2.

I'll have to test this out.

Thanks for clarifying what you did.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
@moordi So I went back to C.33 and then updated to C.35 using the system update and then installed Magisk to the inactive slot.

And...

I ended up unable to boot the phone.

So my process in B.2.1 is still the correct process.

It may be that you can get away with using the system update if the update is a full image update. But it won't work on incremental updates.

The last full image update (for KB2005) was C.11 and every update since then has been incremental.
[OnePlus 8T Guides, News, & Discussion] moordi:
Yeah, that makes sense. I used the full image C.35 update from Oxygen Updater. In the past, OOS would detect root and force a full image update. This time around it attempted the incremental, but the "extraction" failed at some point, and the offer to update disappeared. I'm running the KB2003 model, though I don't know why that should make a difference.
[OnePlus 8T Guides, News, & Discussion] Ma61187:
Over the weekend upgraded from 11.0.13.13 to C.33. Downloaded the update from OP Updater. Update was fine. I used the payload dump, magisk patched the boot.img and it booted to it without issue. Then like before, I did a direct install of Magisk while booted into the patched image. After reboot the phone hard bricked and would only boot to the Qualcomm Crash Dump screen. I was using a bit of an older version of Magisk (24.0). What did I do wrong here? Was it as simple as I was using to old of a version of Magisk? My googling did pull up too many results of exactly what occurred.

Thanks in advanced.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
I use Magisk 25.2 (latest stable) and have never had an issue with it. So, it may well be an issue with using the old version of Magisk.

You should be able to get back to bootloader mode and then flash the stock boot image to get the phone working again.

Power+Vol up should get you out of Crash Dump then immediately use Power + Vol up + Vol down to get into bootloader mode.
[OnePlus 8T Guides, News, & Discussion] mingkee:
I used alternative method:

Right after update installed, DO NOT reboot nor use Magisk OTA method.

Instead, grab updated boot and patch it with Magisk, and copy (updated) patched boot to host PC

Reboot your phone in fastbootd (do not touch the phone during flashing process)

Flash (updated) patched boot

Reboot

I do this method on N10, N200, 8T (Android R and S) and no problem
[OnePlus 8T Guides, News, & Discussion] little_blaine:
C35 instsalled on top of C33 using B.2.1 without issues. I just wanted to call out that step 2 (copy update file to /sdcard) is not needed when using Oxygen Updater, that's the default download location where the file goes anyway. Thanks Bill!
[OnePlus 8T Guides, News, & Discussion] Krosty'Bat:
Hello, C35 update on C33 magisk does not restore the original image because it does not find it. So I found a little tuto to put the image back in place. ( https://xdaforums.com/t/where-does-...restore-needs-to-be-put.3845559/post-87259063 )

Unfortunately I found this technique after uninstalling magisk completely. So I reinstalled my phone completely.

I use a translator, because I don't speak English, so I have a hesitation about the tuto you give in B2.1. Do we have to download the C35 credential update or the full 2G+ update?
[OnePlus 8T Guides, News, & Discussion] little_blaine:
I installed the c35 incremental update over c33 and didn't have any problems restoring images.
[OnePlus 8T Guides, News, & Discussion] Krosty'Bat:
Thank you for your answer. I don't know why magisk couldn't restore the original image. I installed C33 on android 11 and then rooted it with Dumper as explained in this tutorial. Everything went well. It's at the time of the update to C35 that I saw that magisk had not saved the original boot image.
[OnePlus 8T Guides, News, & Discussion] BillGoss:
It seems to me that you didn't follow the instructions properly when you first installed Magisk (A.1.2).

Specifically "2. Do NOT use the "To flash" option in step 11 because this causes issues when you get the next OTA update. Use the the "To Temporarily boot into a rooted system (RECOMMENDED!!)" option."

If you flashed the patched boot image then Magisk would not create a backup of the stock boot image and step 3 in B.2.1 won't work.

I hope this helps you understand what happened.
[OnePlus 8T Guides, News, & Discussion] Krosty'Bat:
Thank you for your intervention but I did not flash the startup image. I have boot on the modified image and then I did a direct installation as it is written in the tutorial.
[OnePlus 8T Guides, News, & Discussion] mingkee:
I used alternative method:

Right after update installed, DO NOT reboot nor use Magisk OTA method.

Instead, grab updated boot and patch it with Magisk, and copy (updated) patched boot to host PC

Reboot your phone in fastbootd (do not touch the phone during flashing process)

Flash (updated) patched boot

Reboot

I do this method on N10, N200, 8T (Android R and S) and no problem

There's a solution

"Patch" the current boot in order to have boot to "restore"

That's why I use boot pull method instead of just install after OTA