How To Guide Convert ColorOS to OxygenOS (OFP & OTA | Bootloader reLock & PIN working)

Search This thread

elurex

Member
Aug 28, 2010
10
1
I bricked my op11 and now I only have bootload and also fastbootd/recovery mode working

it should be userdata issue, I tried to run fastboot -w and I got following error msg
Bash:
>fastboot -w
Erasing 'userdata'                                 OKAY [  0.054s]

        F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 456781056 (223037 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634]       Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668]       Filling nat area at offset 0x01600000
[f2fs_write_root_inode:1281]    Writing root inode (hot node), 2aa00 0 200 at offset 0x00174592
[f2fs_write_default_quota:1357]         Writing quota data, at offset 0002b001, 0002b002
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 2aa00 0 200 at offset 0x00174593
[f2fs_write_default_quota:1357]         Writing quota data, at offset 0002b003, 0002b004
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 2aa00 0 200 at offset 0x00174594
[f2fs_update_nat_root:1502]     Writing nat root, at offset 0x00001600
[f2fs_add_default_dentry_root:1699]     Writing default dentry root, at offset 0x0002b000
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 948 (GC reserved = 484)
[f2fs_write_check_point_pack: 827]      Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982]      Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009]      Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021]      Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032]      Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040]      Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060]      Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081]      Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100]      Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133]   Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB)                         OKAY [  0.003s]
Writing 'userdata'                                 OKAY [  0.076s]
Erasing 'metadata'                                 OKAY [  5.651s]

        F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 131072 (64 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634]       Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668]       Filling nat area at offset 0x00a00000
[f2fs_write_root_inode:1281]    Writing root inode (hot node), 1000 0 200 at offset 0x00004096
[f2fs_write_default_quota:1357]         Writing quota data, at offset 00001601, 00001602
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 1000 0 200 at offset 0x00004097
[f2fs_write_default_quota:1357]         Writing quota data, at offset 00001603, 00001604
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 1000 0 200 at offset 0x00004098
[f2fs_update_nat_root:1502]     Writing nat root, at offset 0x00000a00
[f2fs_add_default_dentry_root:1699]     Writing default dentry root, at offset 0x00001600
Info: Overprovision ratio = 35.000%
Info: Overprovision segments = 16 (GC reserved = 13)
[f2fs_write_check_point_pack: 827]      Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982]      Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009]      Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021]      Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032]      Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040]      Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060]      Writing NAT bits pages, at offset 0x000003ff
[f2fs_write_check_point_pack:1081]      Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100]      Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133]   Writing super block, at offset 0x00000000
Info: format successful
Sending 'metadata' (80 KB)                         FAILED (Write to device failed (no link))
fastboot: error: Command failed
 
Last edited:

oprocks

Senior Member
Jan 25, 2023
86
11
I bricked my op11 and now I only have bootload and also fastbootd/recovery mode working

it should be userdata issue, I tried to run fastboot -w and I got following error msg
Bash:
>fastboot -w
Erasing 'userdata'                                 OKAY [  0.054s]

        F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 456781056 (223037 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634]       Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668]       Filling nat area at offset 0x01600000
[f2fs_write_root_inode:1281]    Writing root inode (hot node), 2aa00 0 200 at offset 0x00174592
[f2fs_write_default_quota:1357]         Writing quota data, at offset 0002b001, 0002b002
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 2aa00 0 200 at offset 0x00174593
[f2fs_write_default_quota:1357]         Writing quota data, at offset 0002b003, 0002b004
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 2aa00 0 200 at offset 0x00174594
[f2fs_update_nat_root:1502]     Writing nat root, at offset 0x00001600
[f2fs_add_default_dentry_root:1699]     Writing default dentry root, at offset 0x0002b000
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 948 (GC reserved = 484)
[f2fs_write_check_point_pack: 827]      Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982]      Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009]      Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021]      Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032]      Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040]      Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060]      Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081]      Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100]      Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133]   Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB)                         OKAY [  0.003s]
Writing 'userdata'                                 OKAY [  0.076s]
Erasing 'metadata'                                 OKAY [  5.651s]

        F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 131072 (64 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634]       Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668]       Filling nat area at offset 0x00a00000
[f2fs_write_root_inode:1281]    Writing root inode (hot node), 1000 0 200 at offset 0x00004096
[f2fs_write_default_quota:1357]         Writing quota data, at offset 00001601, 00001602
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 1000 0 200 at offset 0x00004097
[f2fs_write_default_quota:1357]         Writing quota data, at offset 00001603, 00001604
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 1000 0 200 at offset 0x00004098
[f2fs_update_nat_root:1502]     Writing nat root, at offset 0x00000a00
[f2fs_add_default_dentry_root:1699]     Writing default dentry root, at offset 0x00001600
Info: Overprovision ratio = 35.000%
Info: Overprovision segments = 16 (GC reserved = 13)
[f2fs_write_check_point_pack: 827]      Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982]      Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009]      Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021]      Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032]      Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040]      Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060]      Writing NAT bits pages, at offset 0x000003ff
[f2fs_write_check_point_pack:1081]      Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100]      Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133]   Writing super block, at offset 0x00000000
Info: format successful
Sending 'metadata' (80 KB)                         FAILED (Write to device failed (no link))
fastboot: error: Command failed

I bricked my op11 and now I only have bootload and also fastbootd/recovery mode working

it should be userdata issue, I tried to run fastboot -w and I got following error msg
Bash:
>fastboot -w
Erasing 'userdata'                                 OKAY [  0.054s]

        F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 456781056 (223037 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634]       Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668]       Filling nat area at offset 0x01600000
[f2fs_write_root_inode:1281]    Writing root inode (hot node), 2aa00 0 200 at offset 0x00174592
[f2fs_write_default_quota:1357]         Writing quota data, at offset 0002b001, 0002b002
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 2aa00 0 200 at offset 0x00174593
[f2fs_write_default_quota:1357]         Writing quota data, at offset 0002b003, 0002b004
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 2aa00 0 200 at offset 0x00174594
[f2fs_update_nat_root:1502]     Writing nat root, at offset 0x00001600
[f2fs_add_default_dentry_root:1699]     Writing default dentry root, at offset 0x0002b000
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 948 (GC reserved = 484)
[f2fs_write_check_point_pack: 827]      Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982]      Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009]      Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021]      Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032]      Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040]      Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060]      Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081]      Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100]      Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133]   Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB)                         OKAY [  0.003s]
Writing 'userdata'                                 OKAY [  0.076s]
Erasing 'metadata'                                 OKAY [  5.651s]

        F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 131072 (64 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634]       Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668]       Filling nat area at offset 0x00a00000
[f2fs_write_root_inode:1281]    Writing root inode (hot node), 1000 0 200 at offset 0x00004096
[f2fs_write_default_quota:1357]         Writing quota data, at offset 00001601, 00001602
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 1000 0 200 at offset 0x00004097
[f2fs_write_default_quota:1357]         Writing quota data, at offset 00001603, 00001604
[f2fs_write_qf_inode:1448]      Writing quota inode (hot node), 1000 0 200 at offset 0x00004098
[f2fs_update_nat_root:1502]     Writing nat root, at offset 0x00000a00
[f2fs_add_default_dentry_root:1699]     Writing default dentry root, at offset 0x00001600
Info: Overprovision ratio = 35.000%
Info: Overprovision segments = 16 (GC reserved = 13)
[f2fs_write_check_point_pack: 827]      Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982]      Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009]      Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021]      Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032]      Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040]      Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060]      Writing NAT bits pages, at offset 0x000003ff
[f2fs_write_check_point_pack:1081]      Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100]      Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133]   Writing super block, at offset 0x00000000
Info: format successful
Sending 'metadata' (80 KB)                         FAILED (Write to device failed (no link))
fastboot: error: Command failed

the QLMFlasherTRIAL tool mentioned in page 2 of this thread helped unbrick mine..
 
  • Like
Reactions: elurex

kaijern

Senior Member
Sep 16, 2012
79
33
the QLMFlasherTRIAL tool mentioned in page 2 of this thread helped unbrick mine..
I agree. The QLMFlasher is a good tools. I also paid 20USD just to try the commercial edition. and.... I can't get get the commercial working. Support also never reply.

They did a good job. Just customer support is a pain
 

kaijern

Senior Member
Sep 16, 2012
79
33
I just updated the post with step 5 and 6 and additional note for QLMFlasher.

The official launch of OnePlus 11 is around the conner. We will be receiving the actual firmware soon. All the fastboot flash might not required anymore.

We will soon receiving the official OFP packed firmware and things will be more easier.

I am glad i did not screw up the phone and i hope this post helped some of you.
 

Danz17

Member
Jan 16, 2017
37
2
Manila, Singapore, Dubai
I think the details were not clear at first comment, I am running Oxygen now,

Pretty easy if detailed, need to cover fastboot version and which is the image folder and commands, I can make easier details if OP will allow me to put inputs.
 

mark332

Senior Member
Jul 2, 2017
237
185
I agree. The QLMFlasher is a good tools. I also paid 20USD just to try the commercial edition. and.... I can't get get the commercial working. Support also never reply.

They did a good job. Just customer support is a pain
check your spam email, There is a Mail from tool with Proper support and Login Information, Pro version Login work only after extracting the V1.8/V1.7 tool in V1.0 base version, Otherwise it will not work, it support Lot's of Oppo Realme OnePlus and Vivo Phone in EDL Mod but there is No OnePlus 11, You will get EDL support after a leak
 
Last edited:

kaijern

Senior Member
Sep 16, 2012
79
33
check your spam email, There is a Mail from tool with Proper support and Login Information, Pro version Login work only after extracting the V1.8/V1.7 tool in V1.0 base version, Otherwise it will not work, it support Lot's of Oppo Realme OnePlus and Vivo Phone in EDL Mod but there is No OnePlus 11, You will get EDL support after a leak
Checked and did not received any. Btw, its ok to pay as a "Donation"
 

oprocks

Senior Member
Jan 25, 2023
86
11
after converting to oos, i noticed that color mode change no longer work for me (any change has no effect), confirmed flashing back to stock cos color mode change works.
not sure if this is just me or others that have converted to oos also experienced this.
 

kaijern

Senior Member
Sep 16, 2012
79
33
after converting to oos, i noticed that color mode change no longer work for me (any change has no effect), confirmed flashing back to stock cos color mode change works.
not sure if this is just me or others that have converted to oos also experienced this.
Mine works. But again, even if not working. I am not going to color os. that is just a pain. :)
 

oprocks

Senior Member
Jan 25, 2023
86
11
I think the details were not clear at first comment, I am running Oxygen now,

Pretty easy if detailed, need to cover fastboot version and which is the image folder and commands, I can make easier details if OP will allow me to put inputs.

can you share your method/steps? thanks.
 

kaijern

Senior Member
Sep 16, 2012
79
33
i think you have 32bit windows, extract attachment in qlm/bin folder
nope. mine is 64 bit for sure. Does 32 bit Windows still exits ? :)

its ok, i got curl i can try later on.

The developers should just enable some debug msg and easier for people to know what is happening.
 

mfirestorm

New member
Feb 1, 2023
4
0
Tried to the QLMFlasher and also tried to flash back the ColorOS, but still got bootloop (neither the OOS nor the ColorOS can boot now)

T_T
 

elurex

Member
Aug 28, 2010
10
1
if you brick your op11, you may use follow images+script to fix your op11

Abandon_PHB110.bat
Code:
@echo off
if exist bin\platform-tools-windows\fastboot.exe PATH=%PATH%;bin\platform-tools-windows
setlocal enabledelayedexpansion
title Abandon线刷脚本 [请勿选中窗口,否则卡住活该,卡住按右键或回车或放大缩小窗口恢复]
echo.
echo.刷机注意事项:
echo.①首次刷入官改需要清除数据
echo.②解密Data和不解密Data的包互刷需要清除数据
echo.
echo.
set /p wipeData="是否需要清除数据(y/n)"
echo.
echo.刷机过程中请不要乱动乱点,请注意看标题
echo.刷机过程中请不要乱动乱点,请注意看标题
echo.刷机过程中请不要乱动乱点,请注意看标题
echo.
for /f "tokens=*" %%i in ('curl -sS https://jk.511i.cn 2^>nul ^|findstr fs-22 ^|findstr lh-22 ^|awk NR^=^=2 ^|cut -d ">" -f 2 ^|cut -d "<" -f 1') do (set QQGROUP=%%i)
if "!QQGROUP!" neq "" (
    echo.如果卡在 ^<waiting for any device^> 请前往群(!QQGROUP!)文件搜索”安卓驱动“
    echo.如果卡在 ^<waiting for any device^> 请前往群(!QQGROUP!)文件搜索”安卓驱动“
    echo.如果卡在 ^<waiting for any device^> 请前往群(!QQGROUP!)文件搜索”安卓驱动“
) else (
    echo.如果卡在 ^<waiting for any device^> 请前往群(1365349758)文件搜索”安卓驱动“
    echo.如果卡在 ^<waiting for any device^> 请前往群(1365349758)文件搜索”安卓驱动“
    echo.如果卡在 ^<waiting for any device^> 请前往群(1365349758)文件搜索”安卓驱动“

)
echo.

if exist images\init_boot_official.img (
    if exist images\init_boot_magisk.img (
        echo.
        set /p rootOrNot="是否需要ROOT?(y/n)"
        if /i "!rootOrNot!" == "y" (
            fastboot flash init_boot_a images/init_boot_magisk.img
            fastboot flash init_boot_b images/init_boot_magisk.img
        ) else (
            fastboot flash init_boot_a images/init_boot_official.img
            fastboot flash init_boot_b images/init_boot_official.img
        )
    ) else (
        fastboot flash init_boot_a images/init_boot_official.img
        fastboot flash init_boot_b images/init_boot_official.img
    )
    fastboot flash boot_a images/boot_official.img
    fastboot flash boot_b images/boot_official.img
) else (
    if exist images\boot_magisk.img (
        echo.
        set /p rootOrNot="是否需要ROOT?(y/n)"
        if /i "!rootOrNot!" == "y" (
            fastboot flash boot_a images/boot_magisk.img
            fastboot flash boot_b images/boot_magisk.img
        ) else (
            fastboot flash boot_a images/boot_official.img
            fastboot flash boot_b images/boot_official.img
        )
    ) else (
        fastboot flash boot_a images/boot_official.img
        fastboot flash boot_b images/boot_official.img
    )
)

if exist images\boot_twrp.img (
    echo.
    set /p twrpOrNot="是否需要TWRP?(y/n)"
    if /i "!twrpOrNot!" == "y" (
        fastboot flash boot_a images/boot_twrp.img
        fastboot flash boot_b images/boot_twrp.img
    )
)

if exist images\recovery_twrp.img (
    echo.
    set /p twrpOrNot="是否需要TWRP?(y/n)"
    if /i "!twrpOrNot!" == "y" (
        fastboot flash recovery_a images/recovery_twrp.img
        fastboot flash recovery_b images/recovery_twrp.img
    )
)

fastboot flash xbl_ramdump_a images/xbl_ramdump.img
fastboot flash xbl_ramdump_b images/xbl_ramdump.img
fastboot flash xbl_config_a images/xbl_config.img
fastboot flash xbl_config_b images/xbl_config.img
fastboot flash xbl_a images/xbl.img
fastboot flash xbl_b images/xbl.img
fastboot flash vendor_boot_a images/vendor_boot.img
fastboot flash vendor_boot_b images/vendor_boot.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a images/vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b images/vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_a images/vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b images/vbmeta.img
fastboot flash uefisecapp_a images/uefisecapp.img
fastboot flash uefisecapp_b images/uefisecapp.img
fastboot flash uefi_a images/uefi.img
fastboot flash uefi_b images/uefi.img
fastboot flash tz_a images/tz.img
fastboot flash tz_b images/tz.img
fastboot flash shrm_a images/shrm.img
fastboot flash shrm_b images/shrm.img
fastboot flash qupfw_a images/qupfw.img
fastboot flash qupfw_b images/qupfw.img
fastboot flash modem_a images/modem.img
fastboot flash modem_b images/modem.img
fastboot flash keymaster_a images/keymaster.img
fastboot flash keymaster_b images/keymaster.img
fastboot flash imagefv_a images/imagefv.img
fastboot flash imagefv_b images/imagefv.img
fastboot flash hyp_a images/hyp.img
fastboot flash hyp_b images/hyp.img
fastboot flash featenabler_a images/featenabler.img
fastboot flash featenabler_b images/featenabler.img
fastboot flash dtbo_a images/dtbo.img
fastboot flash dtbo_b images/dtbo.img
fastboot flash dsp_a images/dsp.img
fastboot flash dsp_b images/dsp.img
fastboot flash devcfg_a images/devcfg.img
fastboot flash devcfg_b images/devcfg.img
fastboot flash cpucp_a images/cpucp.img
fastboot flash cpucp_b images/cpucp.img
fastboot flash bluetooth_a images/bluetooth.img
fastboot flash bluetooth_b images/bluetooth.img
fastboot flash aop_config_a images/aop_config.img
fastboot flash aop_config_b images/aop_config.img
fastboot flash aop_a images/aop.img
fastboot flash aop_b images/aop.img
fastboot flash abl_a images/abl.img
fastboot flash abl_b images/abl.img


if exist images\preloader_raw.img (
    fastboot flash preloader_a images/preloader_raw.img 1>nul 2>nul
    fastboot flash preloader_b images/preloader_raw.img 1>nul 2>nul
    fastboot flash preloader1 images/preloader_raw.img 1>nul 2>nul
    fastboot flash preloader2 images/preloader_raw.img 1>nul 2>nul
)
echo.
echo.
echo.如果显示 invalid sparse file format at header magic 为正常情况,不是报错
echo.如果显示 invalid sparse file format at header magic 为正常情况,不是报错
echo.
echo.请耐心等待,卡在这里多久取决于电脑性能,也可以看下标题
echo.请耐心等待,卡在这里多久取决于电脑性能,也可以看下标题
echo.
echo.
if exist images\super.img fastboot flash super images/super.img
echo.
echo.
echo.刷完super可能会卡一段时间,请耐心等待,请勿自行重启,否则可能不开机需要重刷
echo.刷完super可能会卡一段时间,请耐心等待,请勿自行重启,否则可能不开机需要重刷
echo.
echo.如果长时间没有反应,请尝试手动开机或者重刷一遍
echo.如果长时间没有反应,请尝试手动开机或者重刷一遍
echo.
echo.

if /i "!wipeData!" == "y" (
    fastboot erase userdata
    fastboot erase metadata
)
fastboot set_active a
fastboot reboot

pause

Source: 救砖包_ColorOS
 

TweetyPeety

Recognized Themer
Aug 22, 2010
1,703
1,565
can someone tell me which version is the global exact CPH2447 and is an OTA Update to CPH2451 possible and the most important. Heard that Widevinelevel is 1 and Saftynet is Passed, but Google Pay, don't work ?
 

sefai77

Senior Member
Nov 3, 2010
174
28
Been staying in China since 2020. Also a Oneplus user since OnePlus one. Give up Oneplus and swtiched to Nothing phone since Oneplus 10. Decided to try out OnePlus 11 and... ColorOS is really pain in the ....

Decided to play around with fastboot flasing this is what i mange to get.

Additional Note:

Just bare in mind, this is a temporary solution to bring the phone from coloros to oxygen. After Feb 7 when the international version is available. I still need to redo the firmware flashing. But that time is just a Oxygen OS upgrade and it will be way easier

Step 1:
Download all the usual tools
- Android SDK
- Get the firmware from this post

Step 2:
In most cases, a soft-bricked drive could already be in the Fastboot Mode. But if you’re stuck in a bootloop, long-press the Power key to turn it off. After that, press and hold the Power + Volume Down keys simultaneously to boot your device to Fastboot Mode.

If you aren’t able to power off the device, allow its battery to drain out. Once this happens, you should connect it to the charger. As soon as it is about to boot up, you should use the Power + Volume Up/Down keys and it’ll boot to the Fastboot Mode

Step 3:
To clear all user data

fastboot –w

Step 4:

Take note, most of the command i got it from this post , if there are missing files, replace tne extension from img to elf or mbn.

fastboot --set-active=a
fastboot flash --slot=all boot boot.img
fastboot flash --slot=all modem modem.img #this file is missing
fastboot flash vendor_boot vendor_boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img

fastboot reboot fastboot

fastboot flash --slot=all abl abl.elf
fastboot flash --slot=all aop aop.mbn
fastboot flash --slot=all aop_config aop_config.img
fastboot flash --slot=all bluetooth BTFM.bin
fastboot flash --slot=all cpucp cpucp.elf
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all dtbo dtbo.img
fastboot flash --slot=all engineering_cdt engineering_cdt.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 init_boot init_boot.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all oplus_sec oplus_sec.img
fastboot flash --slot=all oplusstanvbk oplusstanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all recovery recovery.img
fastboot flash --slot=all shrm shrm.img
fastboot flash --slot=all splash splash.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefi uefi.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl_ramdump xbl_ramdump.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash my_product my_product.img
fastboot flash odm odm.img
fastboot flash my_engineering my_engineering.img
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot flash system_dlkm system_dlkm.img
fastboot flash my_stock my_stock.img
fastboot flash my_heytap my_heytap.img
fastboot flash my_carrier my_carrier.img
fastboot flash my_region my_region.img
fastboot flash my_bigball my_bigball.img
fastboot flash my_manifest my_manifest.img

Step 5:


If your phone goes into bootloop with oneplus logo. Most likely its not brick. Just need to do a factory reset in fastboot or QLMFlasher.

QLMFlasher

As mention by mark332 use the free edition. Goto the fastboot tab and unbrick your phone.

I also paid for the commercial edition. Received username/password which can never login to the commercial editon. Commercial edition allows flash in EDL which i wanted to try.

Overall, its a good software. But customer support is hopeless. No one reply me till now.

If you just want a simple way to fix it. Just shutdown completely, power + volume down, connect to usb and run

fastboot –w

Step 6:

For some reason, i wanted to relock the bootloader. Just to make it clean.

After locking the bootloader, the PIN will never work.

Tips from alexander宇 is unlock and relock until the pin works. It does work for me like after 30 tried.

One last try before it actually work, i did use QLMFlash to unbrick and some testing. It was a repeating process too. So, i did not know what is making it work.


View attachment 5822655
hi, i was try this methot but my phone is not open always bootloader screen, i was factory reset in fastboot but same agan. i was flash fastboot rom with cmd for come back stak coloros but same again not open, my bootloader is onlock. How can i open my phone ?
 

quynh2v

Senior Member
Mar 15, 2013
75
9
Hi

I try fastboot –w but got an error:
fastboot: usage: unknown command ûw

how to do?
 

[email protected]

Senior Member
Mar 26, 2019
115
26
hi, i was try this methot but my phone is not open always bootloader screen, i was factory reset in fastboot but same agan. i was flash fastboot rom with cmd for come back stak coloros but same again not open, my bootloader is onlock. How can i open my phone ?
EDL mode, MSM tool last
You have to completely power down the phone. Press both the volume buttons simultaneously and hold for 5 seconds (NO POWER BUTTON) and connect to PC. For devices older than the 7 series, only the volume up button for 5 seconds is required.
 
  • Like
Reactions: Danz17 and qriozum

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Please stop littering this forum with repetitive posts. People have already given you advices. Go find a friend offline to help you with firmware flashing if you are not willing to try it yourself. Or request the seller to provide support.
    Dude, I've just got rid of all my problems. Don't you see that I was only looking for help after spend a bunch of money in a phone that was completely useless? Why are you trying to rebuke me for seeking help? Isn't this forum exactly for things like this? If you have nothing to contribute, just shut up and don't be a moron. You can't expect normal users to start flashing phones if they have no clue how to start, which was exactly my case.
    Come on
    Be a better person for fcks sake.
  • 17
    Update: 18th March 2023

    **** Give Up ****


    I got so fedup and decided to goto HK and get my OnePlus 11, a real CPH2449 GLO. Paid and waiting to collect.

    I will not be update and maintaining this post from now on.

    Why give up?

    Minor issue like auto brightness and things is still something i can live along with.

    Some othe rmajor issue are just impossible to make this chiniese converted 1+11 to be my daily driver:

    - Auto reboot randomly
    - Lagging randomly, screen lag, video recording lag.
    - OTA update issue, refreshing/reinstall at every update is just anonying

    My advice? just get a proper non chinese version or if you own a Chinese version just stick with colorOS.


    **** Flash at your own risk ****
    **** Flash at your own risk ****
    **** Flash at your own risk ****

    *** DO NOT OTA UPDATA Your Phone After Convert. It will brick and only Official MSM Tool can save you ***


    A Oneplus user since OnePlus one. Give up Oneplus and swtiched to Nothing phone since Oneplus 10. Decided to try out OnePlus 11 and ColorOS is really pain in the a**

    This post tested converting from PHB110 to CPH2447 / CPH2449. I did not test CPH2451.

    Model:
    • CPH2447 - Indian
    • CPH2449_EEA - EU
    • CPH2449_GLO - International
    • CPH2451 - North America
    • PHB110 - China

    Credits:

    Thanks for their feedback

    Following is the steps to flash the OTA updates:


    Step 1:

    Download all the usual tools
    Step 2:

    To boot into bootloader from Android
    1. Turn On developer mode
    2. Turn on USB Debug
    3. Turn on OEM-unlock
    4. Run $ adb reboot-bootloader
    5. After enter into fastboot (The one with Menu and shows SECURE BOOT/DEVICE STATE)
    6. Run $ fastboot flashing unlock
    7. Reboot back into bootloader, as in step 2 item 4.
    Step 3:
    1. Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
    2. Goto Fastboot Enhance
    3. Check "Ignore Unknown Partition"
    4. Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
    5. Flash payload.bin

    Step 4:
    1. Boot into fastbootd (Phone Screen: The one with language selection)
    2. Goto Fastboot Enhance
    3. Check "Ignore Unknown Partition"
    4. Make sure fastbootd is YES
    5. Flash payload.bin
    Step 5:
    1. Download and unzip Abandon_PHB110_V13_202301030.zip
    2. Unzip make sure radio/oplusstanvbk.img exits
    3. Boot into fastbootd (Phone Screen: The one with language selection)
    4. Use Fastboot Enhance or command line
    5. fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
    Step 6:

    Follow step 6 from "flash the OFP/EDL Packages"

    Following is the steps to flash the OFP/EDL Packages:


    Step 1:

    Download all the usual tools

    Step 2:

    To boot into bootloader from Android
    1. Turn On developer mode
    2. Turn on USB Debug
    3. Turn on OEM-unlock
    4. Run $ adb reboot-bootloader
    5. After enter into fastboot (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
    6. Run $ fastboot flashing unlock
    7. Reboot back into bootloader, as in step 2 item 4.
    Step 3:
    • fastboot flash --slot=all modem radio/modem.img
    • fastboot flash --slot=all boot images/boot.img
    • fastboot flash vbmeta_system_a images/vbmeta_system.img
    • fastboot flash vbmeta_system_b images/vbmeta_system.img
    • fastboot flash vbmeta_a images/vbmeta.img
    • fastboot flash vbmeta_b images/vbmeta.img
    • fastboot flash vendor_boot_a images/vendor_boot.img
    • fastboot flash vendor_boot_b images/vendor_boot.img
    • fastboot flash vbmeta_vendor_a images/vbmeta_vendor.img
    • fastboot flash vbmeta_vendor_b images/vbmeta_vendor.img

    Step 4:

    Go into fastbootd (Phone Screen: The one with language selection)
    • fastboot reboot fastboot
    • fastboot flash --slot=all init_boot images/init_boot.img
    • fastboot flash --slot=all abl radio/abl.img
    • fastboot flash --slot=all aop radio/aop.img
    • fastboot flash --slot=all aop_config radio/aop_config.img
    • fastboot flash --slot=all bluetooth radio/bluetooth.img
    • fastboot flash --slot=all cpucp radio/cpucp.img
    • fastboot flash --slot=all devcfg radio/devcfg.img
    • fastboot flash --slot=all dsp radio/dsp.img
    • fastboot flash --slot=all dtbo images/dtbo.img
    • fastboot flash --slot=all engineering_cdt images/engineering_cdt.img
    • fastboot flash --slot=all featenabler radio/featenabler.img
    • fastboot flash --slot=all hyp radio/hyp.img
    • fastboot flash --slot=all imagefv radio/imagefv.img
    • fastboot flash --slot=all keymaster radio/keymaster.img
    • fastboot flash --slot=all oplus_sec radio/oplus_sec.img
    • # Flash the ColorOS version A.08 # fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
    • fastboot flash --slot=all qupfw radio/qupfw.img
    • fastboot flash --slot=all recovery images/recovery.img
    • fastboot flash --slot=all shrm radio/shrm.img
    • fastboot flash --slot=all splash images/splash.img
    • fastboot flash --slot=all tz radio/tz.img
    • fastboot flash --slot=all uefi radio/uefi.img
    • fastboot flash --slot=all uefisecapp radio/uefisecapp.img
    • fastboot flash --slot=all xbl radio/xbl.img
    • fastboot flash --slot=all xbl_ramdump radio/xbl_ramdump.img
    • fastboot flash --slot=all system images/system.img
    • fastboot flash --slot=all system_ext images/system_ext.img
    • fastboot flash --slot=all vendor images/vendor.img
    • fastboot flash --slot=all product images/product.img
    • fastboot flash --slot=all my_product images/my_product.img
    • fastboot flash --slot=all odm images/odm.img
    • fastboot flash --slot=all my_engineering images/my_engineering.img
    • fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
    • fastboot flash --slot=all system_dlkm images/system_dlkm.img
    • fastboot flash --slot=all my_stock images/my_stock.img
    • fastboot flash --slot=all my_preload images/my_preload.img
    • fastboot flash --slot=all my_heytap images/my_heytap.img
    • fastboot flash --slot=all my_carrier images/my_carrier.img
    • fastboot flash --slot=all my_region images/my_region.img
    • fastboot flash --slot=all my_bigball images/my_bigball.img
    • fastboot flash --slot=all my_manifest images/my_manifest.img

    Step 5:

    From the fastbootd screen (with language selection),
    • English
    • Format Data

    Step 6:

    From daxiaamu blog post,
    1. Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
    2. Go into bootloader again. follow step 2
    3. Run $ fastboot flashing lock
    4. Again, go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
    5. Once passed the setup screen. Goto settings and set the pin

    Additional Tips:

    If your phone goes into bootloop with oneplus logo. Most likely its not brick. Just need to do a factory reset in fastboot or QLMFlasher.

    As mention by mark332 use the free edition. Goto the fastboot tab and unbrick your phone.

    I also paid for the commercial edition. Received username/password which can never login to the commercial editon. Commercial edition allows flash in EDL which i wanted to try.



    1676377681790.png
    4
    Mod edit - translated by https://translate.google.com/?hl=en&sl=auto&tl=en&op=translate:
    Are you sick too?
    ****************
    Bác cũng bị à kk
    Mod edit - translated by https://translate.google.com/?hl=en&sl=auto&tl=en&op=translate:
    Haha I sent the phone to 2 places and couldn't save it. Hardbrick now
    ****************
    Haha gửi máy 2 chỗ rồi ko cứu đc. Giờ hardbrick luôn
    Mod edit - translated by https://translate.google.com/?hl=en&sl=auto&tl=en&op=translate:
    Please print4 a message for your convenience :3
    ****************
    Xin in4 nhắn tin cho tiện bác :3
    Mod edit - translated by https://translate.google.com/?hl=en&sl=auto&tl=en&op=translate:
    what's wrong with it bro? no fastbootd? I'm just wondering how to get up
    ****************
    nó bị sao bác? ko có fastbootd hả? e cũng mới bị mò mò sao lên đc rồi nè
    Mod edit - translated by https://translate.google.com/?hl=en&sl=auto&tl=en&op=translate:
    What version did you flash?
    ****************
    bác flash bản nào thế
    @trungth4nth0ng @xuanhoang1811 @Namhoang05

    As courtesy I've translated your above posts. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Vietnamese posts.
    4. Use the English language.
    We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
    Already yesterday, my esteemed team mate @TNSMANI translated posts. This is now enough! Please read my message as a friednly warning! I've subscribed to this thread and any future non-English post will simply get deleted. Additionally, I reserve the right to apply more severe consequences to your accounts.

    Thanks for your cooperation!
    Regards
    Oswald Boelcke
    Senior Moderator
    3
    Just sharing the steps I took for successful flashing of my device

    0. Backed up my nudes (obviously)
    1. Unlock bootloader (fastboot flashing unlock)
    2. copy paste the commands line by line, use only the files from images folder

    2(a). after fastboot -w I got
    make_f2fs failed: 4294967295
    fastboot: error: Cannot generate image for userdata


    Safely ignorable, ntg wrong

    2(b). any missing files, again ignore, just proceed (will appear like quite a few missing, dont worry)

    3. After the last my_manifest file, I again ran the "fastboot -w" (with same output as 2(a)).
    4. fastboot reboot - brought me to recovery, choose english, factory reset, reboot

    After that it booted into OOS, but lock screen security didnt work
    as mentioned in the thread, the solution was to keep locking/unlocking/locking till it worked

    Thankfully for me it worked first time so;
    5. fastboot flashing lock - voila
    3
    Oneplus sucks! After having regional lock and limitation of converting from ColorOS to OxygenOS, I gave up finally. It is no more Never Settle, and I become no more a Oneplus fan after 6 years. ColorOS has unlimitedly ridiculous notifications of Chinese advertisements made by Baidu news. You become a pathetic user again facing algorithmic harassment.
    2
    @kaijern Any luck with the Global firmware and obtaining it? Also, are you rooting your Oneplus 11?
    i been using oxygenOS for a week now. Everything works, even with bootloader lock. I did not roo.