[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds

[please_dont_brick]

Perhaps old slot got involved. Flashing always goes to other slot.

You can try to flash from local file (to other slot) and before reboot let Magisk patch that other slot. Or you can reboot and then adb sideload Magisk to current new slot (using for example PE 13 recovery image).

The full OOS ZIP can be downloaded with Oxygen Updater.

Flashing again and applying root as described does not hurt.

Personally I flash both slots with latest OOS, one rooted, one not rooted, so I can, if I need so (for specific apps) temporarily boot an work not rooted.

Most apps can have root hidden, but some not.

In any case, to me it looks Magisk for some reason patched your previous slot.

Ok thank your very much for this reasoning. I try what I can do and will report.

 

[please_dont_brick]

I just upgraded to kb2003_11_f15 and the security patch date is December 5, 2022, attached capture, excuse my English.

Have you rooted your phone afterwards using Magisk? Because before that I've also been on patch level December 5

 

[bertmag]

Here's the KB2003 11_f.15 patched image of anyone needs it. I was a goober and installed via the System update, so I had no way to re-root before rebooting. BUT! I followed this guide, specifically these instructions which worked for me;

fastboot getvar current-slot

Depending on whether you get in the result "..... -a" or ".....b" will determine the next step. Once you have my patched 11_f.15 boot image, type the following code:
[CODE]fastboot flash boot_a magisk_patched.img

fastboot reboot

- OR -​

fastboot flash boot_b magisk_patched.img

fastboot reboot

Once you're back into your phone, go through the normal motions; open Magisk --> Install --> Direct install. Then you're rooted! But really I advise you look at the linked guide above in my post.

 

[please_dont_brick]

I used the following command to switch slots

fastboot --set-active=b

After reboot I have no root anymore BUT I'm on December security patch level again ...

 

[Dior DNA]

I used the following command to switch slots

fastboot --set-active=b

After reboot I have no root anymore BUT I'm on December security patch level again ...

Then now you can flash Magisk zip via adb sideload from e.g. PE+ 13 recovery image that you can boot from bootloader. That should root slot 'b' on which, apparently, latest OOS is installed. I assume you somehow previously rooted slot 'a' having previous OOS boot image. As said you can even install same full OOS (from local file) on both slots if you like, e.g. one rooted one not.

 

[please_dont_brick]

Then now you can flash Magisk zip via adb sideload from e.g. PE+ 13 recovery image that you can boot from bootloader. That should root slot 'b' on which, apparently, latest OOS is installed. I assume you somehow previously rooted slot 'a' having previous OOS boot image. As said you can even install same full OOS (from local file) on both slots if you like, e.g. one rooted one not.

I'm trying ... but as soon as I only "boot" the patched Magisk image I downgrade from December patch level to May patch level. After a reboot I'm back at the December patch level, but without root then of course. I also switched slots, makes no difference, as soon as I used the patched image, security patch level drops down.

Here's the KB2003 11_f.15 patched image of anyone needs it. I was a goober and installed via the System update, so I had no way to re-root before rebooting. BUT! I followed this guide, specifically these instructions which worked for me;

fastboot getvar current-slot

Depending on whether you get in the result "..... -a" or ".....b" will determine the next step. Once you have my patched 11_f.15 boot image, type the following code:
[CODE]fastboot flash boot_a magisk_patched.img

fastboot reboot

- OR -​

fastboot flash boot_b magisk_patched.img

fastboot reboot

Once you're back into your phone, go through the normal motions; open Magisk --> Install --> Direct install. Then you're rooted! But really I advise you look at the linked guide above in my post.

I also used your uploaded patched boot image. Same result as with my own one, patch level changes.

 

[gaspolo]

Shi.t i found a bug on os13 , with gesture on screen while locked.
Led cannot start with V gesture , and musico control not work , after couple of lock

anyway , yestareday for error i fastbbooted my os13 with boot.img rooted of OS12
ahahah keyboard not work , battery not recognized sh.it me ahahha

 

[Dior DNA]

I'm trying ... but as soon as I only "boot" the patched Magisk image I downgrade from December patch level to May patch level. After a reboot I'm back at the December patch level, but without root then of course. I also switched slots, makes no difference, as soon as I used the patched image, security patch level drops down.


I also used your uploaded patched boot image. Same result as with my own one, patch level changes.

when your patch level is not December, which slot are you on?

 

[gponces]

Have you rooted your phone afterwards using Magisk? Because before that I've also been on patch level December 5

I had root on android 12, I think c.33 and then it was updated to android 13 f.13 I rooted again and finally I updated to f.15 and rooted again.

 

[21prods]

I need some help. I had a problem with my phone, so I installed OOS 13.F15, got the data I needed for ih8sn to work, and then I installed LOS 20.
My question is, should I update the firmware in the near future, how can I get the fingerprint from the original FW?
I get to the point where I have a copy of the original boot.img, but then I don't know how to get the value of the fingerprint prop.
Thanks in advance and sorry for my English

 

[please_dont_brick]

when your patch level is not December, which slot are you on?

At the moment I have December patch level on slot "a" (not rooted) and May patch level on slot "b" (rooted).

I somehow cannot imagine how the patch level should really "change" if I have the same firmware version KB2003_11_F.15 running on both slots. Maybe it's just a display error??

I used the following command to read the props via adb:

adb shell getprop

The only both props with "security_patch" that I found are:

• [ro.build.version.security_patch]: [2021-10-01]
• [ro.vendor.build.security_patch]: [2022-12-05]

So why there is no 2022-05-05 listed there if it's displayed in the Android settings?

 

[Dior DNA]

At the moment I have December patch level on slot "a" (not rooted) and May patch level on slot "b" (rooted).

I somehow cannot imagine how the patch level should really "change" if I have the same firmware version KB2003_11_F.15 running on both slots. Maybe it's just a display error??

I used the following command to read the props via adb:

adb shell getprop

The only both props with "security_patch" that I found are:

• [ro.build.version.security_patch]: [2021-10-01]
• [ro.vendor.build.security_patch]: [2022-12-05]

So why there is no 2022-05-05 listed there if it's displayed in the Android settings?

I have no sensible explanation and would suggest to fix slot b which does not seem to be in good shape. You can do so by flashing KB2003_11_F.15 again (it will be on slot b if you are on slot a now) from local full ZIP file. Then reboot and you should run KB2003_11_F.15 (no root) from slot b. Next you can then boot, say, PE+ 13vrecovery from bootloader and (adb sideload) flash Magisk (which will root slot b).

If you do not want to change slot b you can root slot a same way (boot, say, PE+ recovery from bootloader and (adb sideload) flash Magisk).

Note that some recoveries (like PE+ 13) may not have working touchscreen on OOS13 firmware so you need to navigate with the hardware buttons.

 

[Shanebacchus]

I was on the EU ROM (original T-Mobile 8T) with working dual SIMS. Got the update message and updated and ended up with KB2003_11_C.15. HOWEVER, now the second SIM is grayed out and does not work though it shows the phone number (of the second SIM). Should I be switching to KB2003 EU_C.15 to regain the dual SIM function?

Has anyone solved this problem ?

 

[jcsww]

Has anyone solved this problem ?

Most have updated to the KB2001 Android 13 Open Beta 1. It is the latest firmware version that allows a KB2007 to work in dual-SIM.

 

[Some_Random_Username]

Added the following files to the OP:
- OOS 12: C.21 (EU), C.21 (IN delivered to OOS 11 users), C.33 (EU delivered to OOS 11 users), C.33 (global), C.35 (EU, IN), C.36 (EU, IN), C.35 downgrade zip (IN) and C.36 downgrade zips (EU, global)
- OOS 13: F.10 (OOS 13 IN OBT 1), F.12 (OOS 13 IN OBT 2), F.13 (all regions) and F.15 (EU)

 

[21prods]

I need some help, please.

I've downloaded the KB2003.13.F.15 firmware in my laptop. I've decompressed it with payload-dumper-go and even unpacked the boot.img file.

Question is, how can I get the 'default.prop' without first installing the OS in my phone? Please bear in mind that I'm running LOS 20, so I don't really want to revert to stock FW but still get some future updates from Oneplus.

I apologise if this message should be posted in a different thread, I've been following many tutorials, but OOS 13 seems to differ from other android releases as to how to edit build.props.

Thanks in advance

 

[Dior DNA]

I need some help, please.

I've downloaded the KB2003.13.F.15 firmware in my laptop. I've decompressed it with payload-dumper-go and even unpacked the boot.img file.

Question is, how can I get the 'default.prop' without first installing the OS in my phone? Please bear in mind that I'm running LOS 20, so I don't really want to revert to stock FW but still get some future updates from Oneplus.

I apologise if this message should be posted in a different thread, I've been following many tutorials, but OOS 13 seems to differ from other android releases as to how to edit build.props.

Thanks in advance

I am not sure in how far LOS 20 mimics OOS 13 *.prop files.

Here are the ones on KB2003.13.F.15

/my_bigball/build.prop
/my_bigball/etc/region/build.prop
/my_carrier/build.prop
/my_company/build.prop
/my_engineering/build.prop
/my_heytap/build.prop
/my_manifest/build.prop
/my_preload/build.prop
/my_product/build.prop
/my_region/build.prop
/my_stock/build.prop
/odm/build.prop
/odm/etc/20807/build.default.prop
/odm/etc/20807/flags.prop
/odm/etc/flags.prop
/odm/etc/normalize/flags.prop
/product/etc/build.prop
/system/build.prop
/system_ext/etc/build.prop
/system_ext/etc/property_list.prop
/system/system_dlkm/etc/build.prop
/vendor/build.prop
/vendor/default.prop

 

[21prods]

Well, that was unexpected, I will go through them and see.
Thank you very much

 

[WO_SEBIx]

If anyone is looking for a patched file to version F.15 for KB2003, here you go:

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

 

[schumissimo]

Hello everyone, I am currently on 11.0.12.12 rom: OnePlus8TOxygen_15.O.30_GLO_0300_2112211344, I would like to update to Android 13, I put the recovery in stock and removed the root. When I try to update locally or by the system, I get an error message just after clicking on "download and install", I've been trying for two days but nothing has changed. Could you guide me please?
Thanking you in advance.