[OnePlus 11] mario6425:
There are several ways. All of them work. BUT Oxygenos does not take our rooted procedure into account. The phones are designed with their updates and their security embedded in them so that you don't unlock the bootloader or root the phone.

I had no problems with locked bootloaders. Just for fun, I flashed the stockrom via msm and ran everything through. With the 304(EX01) there were no problems, at least for me, even with the bootloader unlocked.

For those who still have difficulties getting into custom recovery, bootloader mode or fastboot mode, there is still this option as long as the phone is rooted.

Check this :

1. adb shell

su

2. ---> Check partition table <-(no adb command) and find abl.img

ls -la /dev/block/bootdevice/by-name

lrwxrwxrwx 1 root root 16 1970-01-02 21:55 abl_a -> /dev/block/sde10

lrwxrwxrwx 1 root root 16 1970-01-02 21:55 abl_b -> /dev/block/sde42

3. flash extracted abl.img from sdcard

dd if=/sdcard/abl.img of=/dev/block/sde10

!!*******for abl_a

&

dd if=/sdcard/abl.img of=/dev/block/sde42

!!******for abl_b

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Et voila, now you can enter fastboot mode again.

About the OTA update:

It only works via detours, but you don't need an extra ota updater apk. That's nonsense in my eyes.

First of all, basic and device integrity must exist. There are enough articles on this. Strong integrity cannot be passed with an unlocked bootloader, but this is not a problem.

One mistake that many people make is that usb-debugging is switched on and the developer option is switched on, which should always be deactivated before the update.

In a very bad case, a remnant of Magisk on the internal memory was not properly deleted when locking the bootloader, which would ultimately lead to the phone having to be completely reflashed.

Or what could remain unrecognizable: the bootloader was locked, but the critical partitions are still unlocked.

In other words, "fastboot flashing lock", but "fastboot flashing crtical_unlock".

It happens, I've had it myself. You also don't see the orange state message in this case when booting the phone.

When rooted, the easiest way is 1.) to flash lsposed or xposed via magisk and then download the Lucky_tool module via one of the two programs. 2.) Download the ota software version manually via the oxygenUpdater app and use the Lucky Tool module to force the OTA update function in the first screen, select it and be forwarded to the regular screen for the OTA update and only select the zip version to be updated there. The tool has already adopted all settings so as not to cause any errors.

3.) After the version is ready for installation and you only have to click the "Install now" button, flash it into the other OTA slot via magisk, skip the restart here and select the "Install now" button in the OTA update screen.

Important: The flashing into the other slot may only take place after the update has been fully extracted, when the "Install now" button is flashing, otherwise the extraction will fail.

Last but not least, even if there are always ways to avoid things, these bypassed points will creep in somewhere else as errors. . For example, I've noticed that the oos 14 version as well as the previous ones no longer write properly from erofs to ext4. Why this is the case now, I don't know yet.

When rewriting the formatting with the currently available tools such as ro2rw, in my case the wi-fi socket falls by the wayside. This disappears after the rewrite and you are forced to always activate wifi calling via detours. The consideration of where there is an error in the conversion in the fstab, which could generate a wrong remapping, is still unclear to me, because everything is similar with oos 13, except that oos 14 runs more via apex. (well, even Magisk kitsune from huskydg now runs via Apex.)

Sooner or later a solution will surely be found.

my english is not perfect but hopefully understandable :)