Hello, October 2022
Attachments
Does anyone run a Custom Android 13 ROM flashed on top of OOS13 ? Like, for example, on top of EU KB2003_11_F.13 ? I tried PixelExperiencePlus Android 13 ROM but the touchscreen did not work (not in recovery not in system). Developer acknowledges one needs to flash PE+13 on top of OOS12. Hence my question: maybe other Custom Android 13 ROM can be flashed on top of OOS13 ?
This ROM can't boot you have to be on OOS12 fw, but when you're on OOS13 fw you can try Flamingo or Evo both are build on OOS13 fw and since today AICP also 9n OOS13 fw
Is it me or is OnePlus really terrible at rolling out their updates?
My wife has a EU 8T and still didn't receive the A13 update.
If I check using the OxygenUpdater app, it will only show it when I enabled advanced/experimental options.
But then I get a verification failed error after trying to local install it.
I hear people are editing the zip file and using other local upgrade apks to get it installed and I also read people getting stuck on old patch levels and losing the ability to play Netflix...
Why do they need so much time to release the damn upgrade to all of their users...
What a company..
My wife has a EU 8T and still didn't receive the A13 update.
If I check using the OxygenUpdater app, it will only show it when I enabled advanced/experimental options.
But then I get a verification failed error after trying to local install it.
I hear people are editing the zip file and using other local upgrade apks to get it installed and I also read people getting stuck on old patch levels and losing the ability to play Netflix...
Why do they need so much time to release the damn upgrade to all of their users...
What a company..
at the same time a lot of people successfully received updates and installed OOS13 without any issues both manually and via OTA.
Old patch levels, is a misspelling of string 05/10/22 which one user erroneously read as 10th of may, though it was obviously october.
Netflix is working ok, if you don't mess with root and not passing SafetyNet checks.
Yes I am running a Android 13 ROM on OOS13 base.
There are only a few OOS13 based custom ROMs right now.
FlamingoOS
Pixel Blaster
and I guess 1 or 2 more.
Last edited:
Ok, I found out a really strange thing: I just Installed the new update KB2003_11_F.15. After the reboot I looked into the settings and saw that the update was successful and I am on December security patch level 05/12/2022.
I then extracted the boot.img from the update zip file via payload-dumper-go, patched it via Magisk (v25.2) and flashed it via fastboot. After that I successfully got root but when I looked at the security patch level I "fell back" to May again (05/05/2022). How the hell is that possible? I put you 2 screenshots in here. The first is before the Magisk patch, the second is after the Magisk patch.
I then extracted the boot.img from the update zip file via payload-dumper-go, patched it via Magisk (v25.2) and flashed it via fastboot. After that I successfully got root but when I looked at the security patch level I "fell back" to May again (05/05/2022). How the hell is that possible? I put you 2 screenshots in here. The first is before the Magisk patch, the second is after the Magisk patch.
Attachments
Sure, this is the boot.img I extracted via payload-dumper: https://www.swisstransfer.com/d/c0a90baf-bb86-4fe8-9c33-a2fd77e9bff1
I additionally need to say, that I downloaded the KB2003_11_F.15 update zip via Oxygen Updater and flashed it manually via the normal local update function.
Hi!
Can you upload the KB2003_11_F.15 update zip as well?
That would be great and helpful for me.
Thanks a lot.
So nobody has an idea what could be the reason for the "displayed" security patch level to drop down to May 2022 again?
I downloaded the oxygen updater ota, maybe you should download it again and reflash.You're all good. That is what it's supposed to be
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.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
522I downloaded KB2003_11_F.62 but when I want to install it I notice "Local install" item is grayed out in the menu. Can someone confirm/deny also having it grayed out on KB2003_11_F.15?
update : sorry to answer own question, apparently, with adb device attached, menu item is not grayed out menu.22 -
44As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find.
Note: This is not a support thread for issues you may have with OxygenOS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread.
For the sake of simplicity, only signed flashable (full) zips are listed. These are recovery-flashable zips of the full ROM that won't overwrite your data partition unless mentioned otherwise. They can be flashed via local update in Settings --> System --> System Updates or TWRP recovery (if it becomes available for this device)
Packages with build tag KB05BA are intended for the following variant:
KB2003: EU
Packages with build tag KB05DA are intended for the following variant:
KB2001: India
Global devices (KB2005) with build tag KB05AA zips use Google OTA servers, thus making impossible to capture full OTA zips. Should however full zips be posted on support website they will be added.
KB2000 units are Chinese units running HydrogenOS out of the box and may be able to run OxygenOS after conversion via local update. They will however need to format /data and wipe cache to avoid bootloop.
KB2007 units are T-Mobile units running their own version of OxygenOS labelled KB09CB and lack local update option in Settings->System->System Updates and are therefore not supported.
Signed flashable zips
Signed flashable zips (Open Beta)
Downgrade zips (will wipe your data)
11Want to return to stock using one of these full ota zips rather than MSM?
Use a payload dumper, reboot to bootloader and copypasta below in the same directory as your dumped images
EDIT: Thanks @Fif_
Fif_ said:
Code:fastboot flash recovery recovery.img fastboot flash boot boot.img fastboot flash dtbo dtbo.img fastboot reboot fastboot fastboot flash --slot=all recovery recovery.img fastboot flash --slot=all boot boot.img fastboot flash --slot=all dtbo dtbo.img fastboot flash --slot=all abl abl.img fastboot flash --slot=all aop aop.img fastboot flash --slot=all bluetooth bluetooth.img fastboot flash --slot=all cmnlib64 cmnlib64.img fastboot flash --slot=all cmnlib cmnlib.img fastboot flash --slot=all devcfg devcfg.img fastboot flash --slot=all dsp dsp.img fastboot flash --slot=all featenabler featenabler.img fastboot flash --slot=all hyp hyp.img fastboot flash --slot=all imagefv imagefv.img fastboot flash --slot=all keymaster keymaster.img fastboot flash --slot=all logo logo.img fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img fastboot flash --slot=all modem modem.img fastboot flash --slot=all multiimgoem multiimgoem.img fastboot flash --slot=all qupfw qupfw.img fastboot flash --slot=all spunvm spunvm.img fastboot flash --slot=all storsec storsec.img fastboot flash --slot=all tz tz.img fastboot flash --slot=all uefisecapp uefisecapp.img fastboot flash --slot=all xbl_config xbl_config.img fastboot flash --slot=all xbl xbl.img fastboot delete-logical-partition system_a fastboot delete-logical-partition system_b fastboot delete-logical-partition system_ext_a fastboot delete-logical-partition system_ext_b fastboot delete-logical-partition product_a fastboot delete-logical-partition product_b fastboot delete-logical-partition vendor_a fastboot delete-logical-partition vendor_b fastboot create-logical-partition system_a 100000 fastboot create-logical-partition system_b 100000 fastboot create-logical-partition system_ext_a 100000 fastboot create-logical-partition system_ext_b 100000 fastboot create-logical-partition product_a 100000 fastboot create-logical-partition product_b 100000 fastboot create-logical-partition vendor_a 100000 fastboot create-logical-partition vendor_b 100000 fastboot flash odm odm.img fastboot flash system system.img fastboot flash system_ext system_ext.img fastboot flash product product.img fastboot flash vendor vendor.img fastboot flash --slot=all vbmeta vbmeta.img fastboot flash --slot=all vbmeta_system vbmeta_system.img
Reboot to recovery, factory reset, reboot system, profit
I use it all the time, hasn't failed me yet108OxygenOS 11.0.13.13.KB05BA (EU)
OnePlus8TOxygen_15.E.31_OTA_0310_all_2202182356_c7bd2.zip
MD5: ecc4bccb555141973baf8cfb28a4ad04
[Updated] Android Security Patch to 2022.028Now EU: 11.0.9.9.KB05BA Full OTA is available for download via Oxygen Updater.
or via direct link:
https://otafsg1.h2os.com/patch/amaz...en_15.E.27_OTA_0270_all_2107120935_b276b8.zip
Thanks to rage302 from the "updates thread".
