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

Search This thread

sunxutian

Senior Member
Jan 22, 2015
87
15
tried that a few times, something about "userdata" not working right..

platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.063s]

F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android

platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata


any idea if there is a way to get fastboot to get userdata partition to proper state first? maybe?
actually I saw the same with the latest version of platform-tools while I have an old version which worked, however I am not sure if clean userdata partition would help fastbootd

the fastboot version which works:
fastboot version 31.0.3-7562133
 

oprocks

Senior Member
Jan 25, 2023
86
11
actually I saw the same with the latest version of platform-tools while I have an old version which worked, however I am not sure if clean userdata partition would help fastbootd

the fastboot version which works:
fastboot version 31.0.3-7562133

thanks, the version you pointed to does let me do "fastboot -w" successfully.

"fastboot reboot fastboot" still not working, same issue : "failed to boot into userspace fastboot.."

some permission issue maybe?
 

sunxutian

Senior Member
Jan 22, 2015
87
15
thanks, the version you pointed to does let me do "fastboot -w" successfully.

"fastboot reboot fastboot" still not working, same issue : "failed to boot into userspace fastboot.."

some permission issue maybe?
I think you can also try to install the Qualcomm driver, I remembered I also reinstalled it then reinstall oneplus driver and try again
 

mfirestorm

New member
Feb 1, 2023
4
0
I also bricked my phone last night, got bootloop and only was able to get into bootloader. I unbricked it by fastbootenhanced and flash the F08 payload.bin file
Hello,

I am now in the same situation where bootloop happens. I tried to flash back the A08 stock firmware but the issue persists.

Any idea?
 

mark332

Senior Member
Jul 2, 2017
235
182
Hello,

I am now in the same situation where bootloop happens. I tried to flash back the A08 stock firmware but the issue persists.

Any idea?
May be you miss something, here is a automated tool which will detected each any every file belong to system/boot and write it to device, the tool support both extracted payload.bin or extracted ofp however you have to merge super.img if you are suing extracted ofp..

Must delete persist.img in extracted firmware
Connect device in fastboot, go to fastboot tab click region changer or unbrick option load extracted payload.bin or ofp folder & wait till reboot.. enjoy
support almost all devices

Download Link: https://mega.nz/file/TFJ3DZwB#SBNzeQn8hFkTFqAcfQzECBNInfzODDT-V_KsiSGNn8Q
 

oprocks

Senior Member
Jan 25, 2023
86
11
May be you miss something, here is a automated tool which will detected each any every file belong to system/boot and write it to device, the tool support both extracted payload.bin or extracted ofp however you have to merge super.img if you are suing extracted ofp..

Must delete persist.img in extracted firmware
Connect device in fastboot, go to fastboot tab click region changer or unbrick option load extracted payload.bin or ofp folder & wait till reboot.. enjoy
support almost all devices

Download Link: https://mega.nz/file/TFJ3DZwB#SBNzeQn8hFkTFqAcfQzECBNInfzODDT-V_KsiSGNn8Q
what's the name of this tool? or which app to run upon downloaded it? it seems windows might have removed some files during unzip, trojan detected?
 

mark332

Senior Member
Jul 2, 2017
235
182
what's the name of this tool? or which app to run upon downloaded it? it seems windows might have removed some files during unzip, trojan detected?
no warning in Mine, it's false threat warning because of obfuscation, turn off defender or use VM
Screenshot (262).png
 

kisame9274

New member
Feb 1, 2023
1
0
It seems I brick my phone.

After I typed in "fastboot flash --slot=all abl abl.elf", I got this error:
ERROR: usb_write failed with status e00002ed
fastboot: error: Could not check if partition abl has slot all

In a poor attempt to fix it, I locked BL, and now it stuck in a bootloop to FASTBOOTD

I couldn't get back to FASTBOOT with pressing physical key. Please help!

P.S. I am using mac
The same thing is happening in my environment.
I locked the bootloader and after that I can't get into bootloader mode with any combination of volume and power buttons.
The adb command is also not accepted because of the boot loop. Any ideas?
 

oprocks

Senior Member
Jan 25, 2023
86
11
no warning in Mine, it's false threat warning because of obfuscation, turn off defender or use VM
View attachment 5825711

i run this app and used the unbrick feature to flash the coloros stock img, it was able to get out of bootloader loop and back to that orange state message but can't seem to be able to boot the os.

during unbrick flash, there are bunch of img it failed to write, any suggestions?

Sending 'splash' 324 KB)...FAILED (command write failed (No error))
Sending 'system' 664440 KB)...FAILED (command write failed (No error))
Sending 'system_dlkm' 340 KB)...FAILED (command write failed (No error))
Sending 'system_ext' 1043236 KB)...FAILED (command write failed (No error))
Sending 'tz' 3844 KB)...FAILED (command write failed (No error))
Sending 'uefi' 3080 KB)...FAILED (command write failed (No error))
Sending 'uefisecapp' 176 KB)...FAILED (command write failed (No error))
Sending 'vbmeta' 12 KB)...FAILED (command write failed (No error))
Sending 'vbmeta_system' 8 KB)...FAILED (command write failed (No error))
Sending 'vbmeta_vendor' 4 KB)...FAILED (command write failed (No error))
Sending 'vendor' 1060108 KB)...FAILED (command write failed (No error))
Sending 'vendor_boot' 196608 KB)...FAILED (command write failed (No error))
Sending 'vendor_dlkm' 129284 KB)...FAILED (command write failed (No error))
Sending 'xbl' 1184 KB)...FAILED (command write failed (No error))
Sending 'xbl_config' 188 KB)...FAILED (command write failed (No error))
Sending 'xbl_ramdump' 812 KB)...FAILED (command write failed (No error))
FAILED (command write failed (No error))
Erasing 'userdata'...FAILED (command write failed (No error))
Rebooting...
OKAY
===============================================================

QLMFlasherPro V1.7.0.0 Beta
Elapsed Time : 04 minutes : 09 seconds
 

oprocks

Senior Member
Jan 25, 2023
86
11
i run this app and used the unbrick feature to flash the coloros stock img, it was able to get out of bootloader loop and back to that orange state message but can't seem to be able to boot the os.

during unbrick flash, there are bunch of img it failed to write, any suggestions?

Sending 'splash' 324 KB)...FAILED (command write failed (No error))
Sending 'system' 664440 KB)...FAILED (command write failed (No error))
Sending 'system_dlkm' 340 KB)...FAILED (command write failed (No error))
Sending 'system_ext' 1043236 KB)...FAILED (command write failed (No error))
Sending 'tz' 3844 KB)...FAILED (command write failed (No error))
Sending 'uefi' 3080 KB)...FAILED (command write failed (No error))
Sending 'uefisecapp' 176 KB)...FAILED (command write failed (No error))
Sending 'vbmeta' 12 KB)...FAILED (command write failed (No error))
Sending 'vbmeta_system' 8 KB)...FAILED (command write failed (No error))
Sending 'vbmeta_vendor' 4 KB)...FAILED (command write failed (No error))
Sending 'vendor' 1060108 KB)...FAILED (command write failed (No error))
Sending 'vendor_boot' 196608 KB)...FAILED (command write failed (No error))
Sending 'vendor_dlkm' 129284 KB)...FAILED (command write failed (No error))
Sending 'xbl' 1184 KB)...FAILED (command write failed (No error))
Sending 'xbl_config' 188 KB)...FAILED (command write failed (No error))
Sending 'xbl_ramdump' 812 KB)...FAILED (command write failed (No error))
FAILED (command write failed (No error))
Erasing 'userdata'...FAILED (command write failed (No error))
Rebooting...
OKAY
===============================================================

QLMFlasherPro V1.7.0.0 Beta
Elapsed Time : 04 minutes : 09 seconds


ok, i managed to unbrick it and back to coloros now by flashing it manually following this page:


shall i attempt to convert to oos one more time following step at start of this thread? :)
not sure where i done wrong previously..
 
  • Like
Reactions: qriozum

kaijern

Senior Member
Sep 16, 2012
79
33
So, after two days of trying with lock and unlock, PIN lock finally works
 

kaijern

Senior Member
Sep 16, 2012
79
33
tried that a few times, something about "userdata" not working right..

platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.063s]

F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android

platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata


any idea if there is a way to get fastboot to get userdata partition to proper state first? maybe?
i guess userdata is not important ? i dont remember which one, but one of the flash is not working.

remember to clear all userdata. else it might goes into boot loop
 

kaijern

Senior Member
Sep 16, 2012
79
33
I updated the guide abit. If your phone goes into OnePlus logo and keep on reboot, do step 5. Its not a brick, yet.
 

mark332

Senior Member
Jul 2, 2017
235
182
i run this app and used the unbrick feature to flash the coloros stock img, it was able to get out of bootloader loop and back to that orange state message but can't seem to be able to boot the os.

during unbrick flash, there are bunch of img it failed to write, any suggestions?

Sending 'splash' 324 KB)...FAILED (command write failed (No error))
Sending 'system' 664440 KB)...FAILED (command write failed (No error))
Sending 'system_dlkm' 340 KB)...FAILED (command write failed (No error))
Sending 'system_ext' 1043236 KB)...FAILED (command write failed (No error))
Sending 'tz' 3844 KB)...FAILED (command write failed (No error))
Sending 'uefi' 3080 KB)...FAILED (command write failed (No error))
Sending 'uefisecapp' 176 KB)...FAILED (command write failed (No error))
Sending 'vbmeta' 12 KB)...FAILED (command write failed (No error))
Sending 'vbmeta_system' 8 KB)...FAILED (command write failed (No error))
Sending 'vbmeta_vendor' 4 KB)...FAILED (command write failed (No error))
Sending 'vendor' 1060108 KB)...FAILED (command write failed (No error))
Sending 'vendor_boot' 196608 KB)...FAILED (command write failed (No error))
Sending 'vendor_dlkm' 129284 KB)...FAILED (command write failed (No error))
Sending 'xbl' 1184 KB)...FAILED (command write failed (No error))
Sending 'xbl_config' 188 KB)...FAILED (command write failed (No error))
Sending 'xbl_ramdump' 812 KB)...FAILED (command write failed (No error))
FAILED (command write failed (No error))
Erasing 'userdata'...FAILED (command write failed (No error))
Rebooting...
OKAY
===============================================================

QLMFlasherPro V1.7.0.0 Beta
Elapsed Time : 04 minutes : 09 seconds
i think other issue in your device, fastboot.exe not able to write following partition, reboot bootloader again & retry, or Check if GPT is OK, also the Guide is OK but the command written above flash the image on both slot, if something is wrong, you would not be able to boot the system because damaging of both slot, better set current slot to A and use command in this format= 'fastboot flash partition filename' instead 'fastboot flash --slot=all partition filename'

The tool touch only A, if you brick your device on A then you have fully working B to boot the system
 

oprocks

Senior Member
Jan 25, 2023
86
11
I updated the guide abit. If your phone goes into OnePlus logo and keep on reboot, do step 5. Its not a brick, yet.

cool, will give it a try again with fastboot -w after done.

how these files below? because i can find them in "dsp" folder and are in .img.

fastboot flash --slot=all modem modem.img #this file is missing

fastboot reboot fastboot

fastboot flash --slot=all abl abl.elf
fastboot flash --slot=all aop aop.mbn


--------

can you also share how you got screen to work afterward? thanks..
 

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.