General Maybe a proper way to fix issues after converting Color to Oxygen

Search This thread

JimmyTian

New member
May 1, 2023
3
12
Tian San Ying(天伞桜) proposed that if there is no discernible hardware change between the Chinese and foreign versions of OnePlus 11, then the issue of converting Color OS to Oxygen OS may be caused by software issues.

Previously, the inconsistency between the oplusstanvbk partition of the Chinese version and the international version caused the failure of boot. The device won't boot if the oplusstanvbk partition of the Oxygen OS version is flashed on the Chinese version.

Additionally, Oxygen OS's OTA will upgrade this partition and prevent the device from booting.

I compared the partition backups of the international version of the OnePlus 11 provided by Steve0007 on XDA, my own partition backup of the Chinese version of the OnePlus 11, and the partition image included in the OFP package.

The following partitions have the same content:

Code:
align_to_128k_1 align_to_128k_2 apdp_full apdp apdpb cdt connsec devinfo dip driver DRIVER dsp_a engineering_cdt_a fsc fsg keystore limits-cdsp limits logdump logfs mdcompress mdm1oemnvbktmp mdtp_a mdtpsecapp_a multoem_a multqti_a oplus_sec_a oplusreserve3 oplusreserve4 param persist preisp_dt_bk preisp_dt preisp_otp qweslicstore_a rawdump rtice rticmpdata_a secdata splash_a splash_odm spunvm ssd tzsc uefivarstore vm-bootsys_a vm-data vm-persist xbl_sc_test_mode

The following partitions have different content:

Code:
xbl_ramdump_a xbl_config_a misc uefisecapp_a init_boot_a abl_a aop_a aop_config_a modemst2 vendor_boot_a vbmeta_a devcfg_a imagefv_a oplusreserve1 shrm_a ocdt modem_a featenabler_a oplusdycnvbk vbmeta_vendor_a uefi_a bluetooth_a qupfw_a toolsfv oplusstanvbk_a cpucp_a xbl_sc_logs frp metadata oplusreserve5 qmcs dinfo keymaster_a storsec xbl_a vbmeta_system_a boot_a last_parti oplusreserve2 dtbo_a modemst1 ddr tz_a hyp_a recovery_a

In addition, after removing the partitions from the OFP package that we have already flashed, the remaining partitions are:

Code:
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs

With the exception of oplusstanvbk, which is part of super.img, these partitions are not able to flash under fastbootd and are typically not updated after leaving the factory.

The test indicates that using the oplusstanvbk on Oxygen OS can start normally after flashing the ocdt partition, and features like automatic brightness work properly. Following an OTA, the device can also start normally.

When I compared these two files using vimdiff, I discovered that most of the content is just 00 and that only a small portion is different. Although I'm not sure exactly what operations are being managed, it works.

vimdiff.png


Finally, thanks to Steve0007 for providing the partition backup, Tian San Ying for their suggestions, and the group members' enthusiastic assistance.

TLDR:

fastboot flash ocdt ocdt_CPH2449.img

Known issue:

- BeiDou satellite is not available under Oxygen OS.

sha256: 9bc74cce1c8d492d70d35b21bb6012c0e5cd6a9502ede47f2011f08396820c89 ocdt_CPH2449.img
 

Attachments

  • ocdt_CPH2449.img
    128 KB · Views: 724

sunxutian

Senior Member
Jan 22, 2015
87
15
Amazing find, so just need to flash this img once and everything will work even OTA? How about lock the BL
 

Steve0007

Inactive Recognized Developer / Retired Forum Mod
May 10, 2009
5,726
9,013
Paris
OnePlus 8T
OnePlus 9 Pro
Tian San Ying(天伞桜) proposed that if there is no discernible hardware change between the Chinese and foreign versions of OnePlus 11, then the issue of converting Color OS to Oxygen OS may be caused by software issues.

Previously, the inconsistency between the oplusstanvbk partition of the Chinese version and the international version caused the failure of boot. The device won't boot if the oplusstanvbk partition of the Oxygen OS version is flashed on the Chinese version.

Additionally, Oxygen OS's OTA will upgrade this partition and prevent the device from booting.

I compared the partition backups of the international version of the OnePlus 11 provided by Steve0007 on XDA, my own partition backup of the Chinese version of the OnePlus 11, and the partition image included in the OFP package.

The following partitions have the same content:

Code:
align_to_128k_1 align_to_128k_2 apdp_full apdp apdpb cdt connsec devinfo dip driver DRIVER dsp_a engineering_cdt_a fsc fsg keystore limits-cdsp limits logdump logfs mdcompress mdm1oemnvbktmp mdtp_a mdtpsecapp_a multoem_a multqti_a oplus_sec_a oplusreserve3 oplusreserve4 param persist preisp_dt_bk preisp_dt preisp_otp qweslicstore_a rawdump rtice rticmpdata_a secdata splash_a splash_odm spunvm ssd tzsc uefivarstore vm-bootsys_a vm-data vm-persist xbl_sc_test_mode

The following partitions have different content:

Code:
xbl_ramdump_a xbl_config_a misc uefisecapp_a init_boot_a abl_a aop_a aop_config_a modemst2 vendor_boot_a vbmeta_a devcfg_a imagefv_a oplusreserve1 shrm_a ocdt modem_a featenabler_a oplusdycnvbk vbmeta_vendor_a uefi_a bluetooth_a qupfw_a toolsfv oplusstanvbk_a cpucp_a xbl_sc_logs frp metadata oplusreserve5 qmcs dinfo keymaster_a storsec xbl_a vbmeta_system_a boot_a last_parti oplusreserve2 dtbo_a modemst1 ddr tz_a hyp_a recovery_a

In addition, after removing the partitions from the OFP package that we have already flashed, the remaining partitions are:

Code:
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs

With the exception of oplusstanvbk, which is part of super.img, these partitions are not able to flash under fastbootd and are typically not updated after leaving the factory.

The test indicates that using the oplusstanvbk on Oxygen OS can start normally after flashing the ocdt partition, and features like automatic brightness work properly. Following an OTA, the device can also start normally.

When I compared these two files using vimdiff, I discovered that most of the content is just 00 and that only a small portion is different. Although I'm not sure exactly what operations are being managed, it works.

View attachment 5905297

Finally, thanks to Steve0007 for providing the partition backup, Tian San Ying for their suggestions, and the group members' enthusiastic assistance.

TLDR:

fastboot flash ocdt ocdt_CPH2449.img

Known issue:

- BeiDou satellite is not available under Oxygen OS.

sha256: 9bc74cce1c8d492d70d35b21bb6012c0e5cd6a9502ede47f2011f08396820c89 ocdt_CPH2449.img

Hi Jimmy,

Can you share the screenshot of the Settings showing up the phone ? Does it show CPH model as CPH2449 ?
We will need also the ocdt ocdt_CPH2451.img for those who want to convert to US Oneplus 11.

Last point: why don't we also flash the remaining imgs that are different like :
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs in order to get a fully converted device?

Steve
 

JimmyTian

New member
May 1, 2023
3
12
Amazing find, so just need to flash this img once and everything will work even OTA? How about lock the BL
I'm not sure if it is a general method or if I accidentally changed something during my testing that made it work on my device, but it did. More testing is therefore required.

I tried upgrading from A.09 OTA to A.10 and it seems to be working fine.

I also tried unlocking and relocking the bootloader and it seems to be working fine as well.
 

sunxutian

Senior Member
Jan 22, 2015
87
15
I'm not sure if it is a general method or if I accidentally changed something during my testing that made it work on my device, but it did. More testing is therefore required.

I tried upgrading from A.09 OTA to A.10 and it seems to be working fine.

I also tried unlocking and relocking the bootloader and it seems to be working fine as well.
Nice work again, so we should be able to lock the BL and OTA fine without any issues
 

JimmyTian

New member
May 1, 2023
3
12
Hi Jimmy,

Can you share the screenshot of the Settings showing up the phone ? Does it show CPH model as CPH2449 ?
We will need also the ocdt ocdt_CPH2451.img for those who want to convert to US Oneplus 11.

Last point: why don't we also flash the remaining imgs that are different like :
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs in order to get a fully converted device?

Steve
Regarding the provided partition images, thank you very much!

01.jpg
02.jpg


Both the CPH2447 and CPH2449 images are working properly. The version which is displayed is determined by the version you have flashed.

Perhaps this partition is the same in the international version? We need more feedback.

Baseband is one of the hardware-limited components, so flashing images that is incompatible with the hardware might result in problems like no signal and broken Wi-Fi.

I therefore considered merely making the most minimal changes to the system.
 

jinglei207

Member
Jan 1, 2018
49
7
Does it still randomly shut down? I had this problem when I converted to oxygen Os.


Tian San Ying(天伞桜) proposed that if there is no discernible hardware change between the Chinese and foreign versions of OnePlus 11, then the issue of converting Color OS to Oxygen OS may be caused by software issues.

Previously, the inconsistency between the oplusstanvbk partition of the Chinese version and the international version caused the failure of boot. The device won't boot if the oplusstanvbk partition of the Oxygen OS version is flashed on the Chinese version.

Additionally, Oxygen OS's OTA will upgrade this partition and prevent the device from booting.

I compared the partition backups of the international version of the OnePlus 11 provided by Steve0007 on XDA, my own partition backup of the Chinese version of the OnePlus 11, and the partition image included in the OFP package.

The following partitions have the same content:

Code:
align_to_128k_1 align_to_128k_2 apdp_full apdp apdpb cdt connsec devinfo dip driver DRIVER dsp_a engineering_cdt_a fsc fsg keystore limits-cdsp limits logdump logfs mdcompress mdm1oemnvbktmp mdtp_a mdtpsecapp_a multoem_a multqti_a oplus_sec_a oplusreserve3 oplusreserve4 param persist preisp_dt_bk preisp_dt preisp_otp qweslicstore_a rawdump rtice rticmpdata_a secdata splash_a splash_odm spunvm ssd tzsc uefivarstore vm-bootsys_a vm-data vm-persist xbl_sc_test_mode

The following partitions have different content:

Code:
xbl_ramdump_a xbl_config_a misc uefisecapp_a init_boot_a abl_a aop_a aop_config_a modemst2 vendor_boot_a vbmeta_a devcfg_a imagefv_a oplusreserve1 shrm_a ocdt modem_a featenabler_a oplusdycnvbk vbmeta_vendor_a uefi_a bluetooth_a qupfw_a toolsfv oplusstanvbk_a cpucp_a xbl_sc_logs frp metadata oplusreserve5 qmcs dinfo keymaster_a storsec xbl_a vbmeta_system_a boot_a last_parti oplusreserve2 dtbo_a modemst1 ddr tz_a hyp_a recovery_a

In addition, after removing the partitions from the OFP package that we have already flashed, the remaining partitions are:

Code:
ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs

With the exception of oplusstanvbk, which is part of super.img, these partitions are not able to flash under fastbootd and are typically not updated after leaving the factory.

The test indicates that using the oplusstanvbk on Oxygen OS can start normally after flashing the ocdt partition, and features like automatic brightness work properly. Following an OTA, the device can also start normally.

When I compared these two files using vimdiff, I discovered that most of the content is just 00 and that only a small portion is different. Although I'm not sure exactly what operations are being managed, it works.

View attachment 5905297

Finally, thanks to Steve0007 for providing the partition backup, Tian San Ying for their suggestions, and the group members' enthusiastic assistance.

TLDR:

fastboot flash ocdt ocdt_CPH2449.img

Known issue:

- BeiDou satellite is not available under Oxygen OS.

sha256: 9bc74cce1c8d492d70d35b21bb6012c0e5cd6a9502ede47f2011f08396820c89 ocdt_CPH2449.img
 

Lunisi

Member
Dec 30, 2021
29
5
Let me understand something, if we flash this OCDT file we can boot with OxygenOS oplusstanvbk (without flashing the ColorsOS one), right ?

And another thing, since it _thinks_ we are on the OG European OnePlus 11 model, there should be a way to find how to bypass the region lock that way, right ?
 

らいた

Member
Feb 14, 2023
9
5
Hi
Does fingerprint authentication work?
And does it mean to flash OCDT instead of flashing color os oplusstanvbk?
Thank you for your work.
 

mhoang99

New member
May 8, 2023
1
0
Hi
I tried to convert from ColorOS to CPH2449 last night.
I installed the A09 version through Fastboot Enhanced, then flashed ocdt img. The phone got bootlooped at the oneplus logo screen.
Then I flashed the oplusstanvbk from the coloros A09 rom, and the phone booted successfully.

Not so sure what I did wrong, but in my case, I still had to flash the oplusstanvbk for it to work.
 

oprocks

Senior Member
Jan 25, 2023
87
11
i can confirm auto brightness works, and no need to flash oplusstanvbk from cos.

but i still can't get fingerprint to work, during fingerprint enrollment there is no sensor light popup but just typing vibrating like continuously.

esim also not working, won't enable during attempt.
 
Last edited:

t0ng00

Member
May 7, 2023
6
1
i can confirm auto brightness works, and no need to flash oplusstanvbk from cos.

but i still can't get fingerprint to work, during fingerprint enrollment there is no sensor light popup but just typing vibrating like continuously.

esim also not working, won't enable during attempt.
Hi, I actually have a brand new CN OnePlus 11 waiting to be flashed - would you mind to share the steps you did and I will try maybe tomorrow and post the result back?

Regards,
 

oprocks

Senior Member
Jan 25, 2023
87
11
Hi, I actually have a brand new CN OnePlus 11 waiting to be flashed - would you mind to share the steps you did and I will try maybe tomorrow and post the result back?

Regards,

1. unlock bl
2. use fastbooteh to flash 2449's payload.bin
3. flash ocdt mentioned in start of this thread
4. lock bl

that's all.
 

oprocks

Senior Member
Jan 25, 2023
87
11
i flashed back cos, wifi no longer worked there. it seems this ocdt messed up wifi back in original cos, something in the baseband got changed?
 

jinglei207

Member
Jan 1, 2018
49
7
Hi
I tried to convert from ColorOS to CPH2449 last night.
I installed the A09 version through Fastboot Enhanced, then flashed ocdt img. The phone got bootlooped at the oneplus logo screen.
Then I flashed the oplusstanvbk from the coloros A09 rom, and the phone booted successfully.

Not so sure what I did wrong, but in my case, I still had to flash the oplusstanvbk for it to work.
Did you factory reset the smartphone after flashing Oxygen OS?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    Tian San Ying(天伞桜) proposed that if there is no discernible hardware change between the Chinese and foreign versions of OnePlus 11, then the issue of converting Color OS to Oxygen OS may be caused by software issues.

    Previously, the inconsistency between the oplusstanvbk partition of the Chinese version and the international version caused the failure of boot. The device won't boot if the oplusstanvbk partition of the Oxygen OS version is flashed on the Chinese version.

    Additionally, Oxygen OS's OTA will upgrade this partition and prevent the device from booting.

    I compared the partition backups of the international version of the OnePlus 11 provided by Steve0007 on XDA, my own partition backup of the Chinese version of the OnePlus 11, and the partition image included in the OFP package.

    The following partitions have the same content:

    Code:
    align_to_128k_1 align_to_128k_2 apdp_full apdp apdpb cdt connsec devinfo dip driver DRIVER dsp_a engineering_cdt_a fsc fsg keystore limits-cdsp limits logdump logfs mdcompress mdm1oemnvbktmp mdtp_a mdtpsecapp_a multoem_a multqti_a oplus_sec_a oplusreserve3 oplusreserve4 param persist preisp_dt_bk preisp_dt preisp_otp qweslicstore_a rawdump rtice rticmpdata_a secdata splash_a splash_odm spunvm ssd tzsc uefivarstore vm-bootsys_a vm-data vm-persist xbl_sc_test_mode

    The following partitions have different content:

    Code:
    xbl_ramdump_a xbl_config_a misc uefisecapp_a init_boot_a abl_a aop_a aop_config_a modemst2 vendor_boot_a vbmeta_a devcfg_a imagefv_a oplusreserve1 shrm_a ocdt modem_a featenabler_a oplusdycnvbk vbmeta_vendor_a uefi_a bluetooth_a qupfw_a toolsfv oplusstanvbk_a cpucp_a xbl_sc_logs frp metadata oplusreserve5 qmcs dinfo keymaster_a storsec xbl_a vbmeta_system_a boot_a last_parti oplusreserve2 dtbo_a modemst1 ddr tz_a hyp_a recovery_a

    In addition, after removing the partitions from the OFP package that we have already flashed, the remaining partitions are:

    Code:
    ddr dinfo frp last_parti metadata misc modemst1 modemst2 ocdt oplusdycnvbk oplusreserve1 oplusreserve2 oplusreserve5 oplusstanvbk_a qmcs storsec toolsfv xbl_config_a xbl_sc_logs

    With the exception of oplusstanvbk, which is part of super.img, these partitions are not able to flash under fastbootd and are typically not updated after leaving the factory.

    The test indicates that using the oplusstanvbk on Oxygen OS can start normally after flashing the ocdt partition, and features like automatic brightness work properly. Following an OTA, the device can also start normally.

    When I compared these two files using vimdiff, I discovered that most of the content is just 00 and that only a small portion is different. Although I'm not sure exactly what operations are being managed, it works.

    vimdiff.png


    Finally, thanks to Steve0007 for providing the partition backup, Tian San Ying for their suggestions, and the group members' enthusiastic assistance.

    TLDR:

    fastboot flash ocdt ocdt_CPH2449.img

    Known issue:

    - BeiDou satellite is not available under Oxygen OS.

    sha256: 9bc74cce1c8d492d70d35b21bb6012c0e5cd6a9502ede47f2011f08396820c89 ocdt_CPH2449.img
    4
    1. unlock bl
    2. use fastbooteh to flash 2449's payload.bin
    3. flash ocdt mentioned in start of this thread
    4. lock bl

    that's all.
    I will try this method when it arrives

    from @kaijern and @JimmyTian post

    1. Turn On developer mode
    2. Turn on USB Debug
    3. Turn on OEM-unlock
    4. adb reboot-bootloader
    5. enter into fastboot
    6. fastboot flashing unlock
    7. adb reboot-bootloader
    8. Download and unzip CPH2449 GLO A.10 https://onl.sc/H1ACkaU
    9. Goto Fastboot Enhance
    10. Check "Ignore Unknown Partition"
    11. Make sure fastbootd is NO
    12. Flash payload.bin
    13. Boot into fastbootd
    14. Goto Fastboot Enhance
    15. Check "Ignore Unknown Partition"
    16. Make sure fastbootd is YES
    17. Flash payload.bin
    18. Download and unzip ocdt_CPH2449.img
    19. enter into fastboot
    20. fastboot flash ocdt ocdt_CPH2449.img
    21. Fastboot reboot
    22. Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
    23. Turn On developer mode
    24. Turn on USB Debug
    25. Turn on OEM-unlock
    26. adb reboot-bootloader
    27. After enter into fastboot
    28. fastboot flashing lock
    29. fastboot reboot
    Is this procedure OK?

    【edit】
    I confirmed that I can flash with this method.
    2
    Hi There,
    Can someone help me on this please? I've tried to follow a guide on DroidWin and managed to get through the following steps while trying to convert the device

    1) Unlock Bootloader
    2) Using Fastboot Enhanced, Flash Payload.bin for OxygenOS
    3) Using FastbootD, Flash Payload.bin for OxygenOS
    4) due to some versioning error, I was not able to extract the oplusstanvbk.img file.

    After getting stuck on the above, I managed to find this thread and have tried to retrace the steps given by @

    [B]らいた[/B] on #27, but after step 21 I don't get to setup my device, and it straightaway goes into the OS but a popup code.aurora keeps stopping, and shows battery at 0%., keyboard does not work. Even after factory resetting the device I'm not able to get to the new device registration. Does locking the bootloader address this issue or is there something else that i missed out?


    edit: I've since booted into recovery mode and selected format data (instead of earlier reverting to factory settings through the settings screen) and things look good now, Thanks!
    2
    I tried this on my chinese 512GB and after step 13. my phone never turned back on and seems dead now. Fastboot enhance doesnt recognize it, I can't turn on, no button combination gives any reaction, no recovery mode, nothing.

    I am desperate for help, does anyone have a solution?
    Use EDL
    2
    ocdt from CPH2447