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

Search This thread

F!CT10N

New member
Jun 6, 2023
2
0
Hi,


Flashed from color os to oxygen os A09, fingerprint sensor not working. Tried updating from A09 to now A10, still throwing error. While testing in *#808*# menu, it says passed.
Whenever i try to enroll fingerprint, it does not even pop up, just vibrates and says " try again unable to complete the fingerprint settings. Please Retry"
Has anyone else faced the same issue and has been able to solve it?

Already tried:

1) Restarting, Resetting, Factory Reset, Re flash.
2) Cleaning Fingerprint sensor area.
3) Updating, downgrading back to a09.

Attaching Pic of error.

The Error
352233853_4343056672586588_8641832256659648476_n.jpg
 

oprocks

Senior Member
Jan 25, 2023
87
11
i had similar issue, issue is fixed by recalibrating fingerprint. you need a special tool, search it in youtube.
 

cavist

Senior Member
Nov 19, 2010
305
116
Hi,


Flashed from color os to oxygen os A09, fingerprint sensor not working. Tried updating from A09 to now A10, still throwing error. While testing in *#808*# menu, it says passed.
Whenever i try to enroll fingerprint, it does not even pop up, just vibrates and says " try again unable to complete the fingerprint settings. Please Retry"
Has anyone else faced the same issue and has been able to solve it?

Already tried:

1) Restarting, Resetting, Factory Reset, Re flash.
2) Cleaning Fingerprint sensor area.
3) Updating, downgrading back to a09.

Attaching Pic of error.

The Error
There is no need to spam same question in different topics.
 
  • Like
Reactions: F!CT10N

wtywtykk

Member
Feb 10, 2023
16
3
Any one tested this method on 11R/ace 2? Maybe need someone to dump files from 11R...
On ace2 forum someone shared one, but seems not working.
 

dekefake

Senior Member
Oct 28, 2013
1,139
1,850
Orleans, France
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.
Hi,

I have tried this exact procedure multiple times with the exact same build (CPH2449 GLO A.10) and also with CPH2449 GPDR A.09, and I cannot get the device to boot. It keeps bootlooping. I also tried to flash the images using fastboot in terminal using this guide but nothing helps. The phone is a CPH2447 imported from India to France, with no success. I've flashed the ocdt multiple times already and it keeps bootlooping. I also tried to flash a ColorOS PHB110_11.A.10 oplusstanvbk and it doesn't helps.

The phone has already been behaving like that and I got it EDL flashed to a CPH2449 GPDR. Testing our first custom kernel build lead to this situation, and I really do not understand how on earth this phone still doesn't boots despite having followed guides most people found helpful.

If you have any ideas, I'd be glad to hear them.
 

semson

Senior Member
Jan 4, 2012
118
30
I’d like to know the answer to this as well, currently thinking about return it but because I bought the 128GB and they sent the 256GB instead, I’d like to keep it.

I didn’t know it was the CN, they unlocked it so no error with the calls but the OS shows the Indian version and can’t update.

Confirming 512GB works. Flashed to CPH2449 A.10 Global using ocdt.img from the OP, OTA to EX01 smoothly.
 

Attachments

  • Screenshot_2023-07-13-16-18-55-36_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2023-07-13-16-18-55-36_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    432 KB · Views: 77

scottlam1

Senior Member
Aug 16, 2011
241
70
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 cpocdt_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
I posted the us ocpt cph2451 img in this thread for people who need it
 
  • Like
Reactions: semson

nonegor

Senior Member
Feb 17, 2023
105
14
oplusstanvbk.img
Hi,

I have tried this exact procedure multiple times with the exact same build (CPH2449 GLO A.10) and also with CPH2449 GPDR A.09, and I cannot get the device to boot. It keeps bootlooping. I also tried to flash the images using fastboot in terminal using this guide but nothing helps. The phone is a CPH2447 imported from India to France, with no success. I've flashed the ocdt multiple times already and it keeps bootlooping. I also tried to flash a ColorOS PHB110_11.A.10 oplusstanvbk and it doesn't helps.

The phone has already been behaving like that and I got it EDL flashed to a CPH2449 GPDR. Testing our first custom kernel build lead to this situation, and I really do not understand how on earth this phone still doesn't boots despite having followed guides most people found helpful.

If you have any ideas, I'd be glad to hear them.
you should firstly to flash the oplusstanvbk.img to make sure your device can be switched on.
 

105abs

Member
Jan 10, 2013
47
4
cairo
OnePlus 5T
OnePlus 11
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.

Actually we've been through a long way with this. Now, we have EDL and I'm running LineageOS. Thanks anyway 😁

I thinks I have the same problem, but I cannot get the phone connected to EDL.

The problem is that I tried the ocdt method with fastboot enhance.

but when I flash the payload.bin in the fastboot, the phone restart on its own at around 60% and load in OOS which seems corrupt and keeps restarting. When I get back to fastboot mode the fastboot enchance resumes flashing as if nothing happened, but still the OS is corrupted.

Now I am stuck with Corrupt OOS.........

may be I will try to flash another OOS version or flash ColorOS payload.bin??

any Help...?
 

nonegor

Senior Member
Feb 17, 2023
105
14
I thinks I have the same problem, but I cannot get the phone connected to EDL.

The problem is that I tried the ocdt method with fastboot enhance.

but when I flash the payload.bin in the fastboot, the phone restart on its own at around 60% and load in OOS which seems corrupt and keeps restarting. When I get back to fastboot mode the fastboot enchance resumes flashing as if nothing happened, but still the OS is corrupted.

Now I am stuck with Corrupt OOS.........

may be I will try to flash another OOS version or flash ColorOS payload.bin??

any Help...?
During the flashing process, there is no restart. I think your flashing steps are wrong
 
  • Like
Reactions: 105abs

105abs

Member
Jan 10, 2013
47
4
cairo
OnePlus 5T
OnePlus 11
I thinks I have the same problem, but I cannot get the phone connected to EDL.

The problem is that I tried the ocdt method with fastboot enhance.

but when I flash the payload.bin in the fastboot, the phone restart on its own at around 60% and load in OOS which seems corrupt and keeps restarting. When I get back to fastboot mode the fastboot enchance resumes flashing as if nothing happened, but still the OS is corrupted.

Now I am stuck with Corrupt OOS.........

may be I will try to flash another OOS version or flash ColorOS payload.bin??

any Help...?


here my two cent.

I couldn't fix the Qualcomm drivers. So i can't connect to the EDL tool.

I then used ocdt method mentioned above.

Notes
*backup your ocdt.img
* don't flash ocdt-2449 first.
* I used OOS 13.1, so you can used.
*before starting the OOS boot to recovery and format data, as using adb didn't wipe correctly.
*use cmd with adb not windows powershell as it doesn't lock the bootloader back.
 

xymeng

Member
Mar 28, 2019
45
14
OnePlus 11
Can anyone confirm this method solves the e-sim problem on Chinese version converted to Oxygen OS?

Update: still cannot add e-sim
eSIM won't work as the CN variant does not have an eUICC on the motherboard. At least I cannot get the Eid of it via any methods/APIs.

If you really want to use eSIM, my post may help you. But u need to buy a chip from Taobao or you may need to DIY...
 

dekefake

Senior Member
Oct 28, 2013
1,139
1,850
Orleans, France
Could someone dump the CPH2447 ocdt.img please ? I flashed the CPH2449 one months ago but forgot to make a backup. The funny thing is, all ocdt images were uploaded by various people on the thread, except the indian one. I'd appreciate if someone could do that for me.

Thanks

To dump, use termux or adb shell, and run :

su
dd if=/dev/block/by-name/ocdt of=/sdcard/ocdt.img
 

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