Develop Bugs

[STOCK][FASTBOOT] Fastboot Flashable Images For OnePlus 7T

Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
OnePlus7TOxygen_14.I.05_OTA_fastboot
Code:
ro.vendor.build.date=Wed Sep 25 21:54:29 CST 2019
ro.vendor.build.date.utc=1569419669
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1909250940:user/release-keys
ro.vendor.build.id=QKQ1.190716.003
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=1909250940
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T
Fastboot Commands :
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
Credits :
jamflux
Regards,
acervenky

reserved

Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.

RohanAJoshi said:
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
Click to expand...
Click to collapse
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky

acervenky said:
Download the attachment, and flash it using this command :
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
OK, I will try this and report you back soon.

acervenky said:
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b

RohanAJoshi said:
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
Click to expand...
Click to collapse
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky

acervenky said:
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
Click to expand...
Click to collapse
which file should i dowload ?
stock or mod ?

RohanAJoshi said:
which file should i dowload ?
stock or mod ?
Click to expand...
Click to collapse
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky

acervenky said:
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
Click to expand...
Click to collapse
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.

RohanAJoshi said:
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
Click to expand...
Click to collapse
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?

How2Kritin said:
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
Click to expand...
Click to collapse
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"

cultofluna said:
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
Click to expand...
Click to collapse
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky

acervenky said:
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
Click to expand...
Click to collapse
I did, initially but it said that the /system, /vendor and /product partitions couldn’t be mounted. When I tried to restore I got stuck in the fastboot mode. After that, I’ve used your file and got stuck with the qualcomm crashdump mode.

FIXED
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!

I wonder, if a T-Mobile 7T is unlocked can we use this method to install the international firmware on it?

Is this for EU Model?

Hot-Proton said:
Is this for EU Model?
Click to expand...
Click to collapse
No, Global!
Regards,
acervenky

Ok that is bad. Wait for EU Version.

for T-Mobile no, I messed up mine, it boots but no wifi and data. I did a remote session with oneplus but they can't fix it, they don't have the firmware for the tmobile version, unless if someone has already patched the MSM, but sadly nothing yet
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
How2Kritin said:
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
Click to expand...
Click to collapse
how did you reach out to him, just wanna know if there's a fix for my wifi and data no connections, T-Mobile unlock bootloader, tried flashing the modem from here but no effect and when I tried deleting it, sim card cannot be detected

[Guide] Oneplus 7T T-Mobile to International Firmware Conversion Explained

Preparation:
Notes are important, please pay attention
ONLY use stock USB-A to USB-C cable
I have tried the stock cable from Axon 7, fail fail and more fail, don't make this mistake
DON'T store flash files on USB storage.
fastboot will timeout if your flash files are stored at a slow storage device such as a USB drive, or slow computer with eMMC drive
Download and extract the patched MSM download tool and related flash files (credit)
Download and extract TWRP 3.4.0-2 Test by mauronofrio (credit)
Download and extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip (credit)
Optional: Unlock bootloader at this official OnePlus page with those steps
automated process you have to wait 1 whole week for
if you take this route, you will have an easier time get into EDL
Optional for Driver and boot into EDL: Download and extract the TOOL ALL IN ONE (credit) (untested) (can skip this step if you have driver and completed preparation step 7)
Flash Operations:
Run the MSM executable with Administrator Privilege
Boot into bootloader on 7T (if you already have adb connection, adb reboot bootloader would work as well)
Restart device: Vol Up + Power
Boot into recovery: when system reboot from step 4, immediately press and hold Vol Down + Power until recovery screen
Boot into fastboot: English -> Advanced -> fastboot
Boot into EDL on 7T
If you have OnePlus unlock token from Preparation step 7
Connect USB cable to both PC and 7T
on MSMDownloadTool, click Enum to display your device
fastboot flash cust-unlock unlock_token.bin
fastboot oem unlock
fastboot boot twrp.img
when TWRP boot: adb reboot edl
on MSMDownloadTool it will now show connected
If you don't want to wait for token (untested)
Use TOOL ALL IN ONE
Or, hold down the buttons then click start in MSM. If you release the volume buttons early it will kick you out of EDL--well at least for me. you can release the buttons once MSM starts (credit)
When MsmDownloadTool display connected, hit Start until 7T display CORRUPT message (normal behavior) and reboot into fastboot by ITSELF. If your 7T doesn't get into fastboot screen automatically, something is wrong with previous step, redo EDL flashing and do NOT proceed.
Start Power-Shell with Administrator Privilege and go to the extracted path of 10.0.13-global-oneplus7toxygen_14.o.19_ota_019_all_2009281709_1026-fastboot.zip (DO NOT USE DOS, it will fail you miserably)
Unlock bootloader: .\fastboot flashing unlock_critical (suggested, because it works, so I didn't test the oem unlock method)
To avoid potential conflict with installed fastboot binary (possibly lower version), you can either
edit the flash-all.bat, and change fastboot to .\fastboot, such that only the local fastboot binary will be invoked instead of pathed binary
OR run those identical commands with copy and paste
Code:
.\fastboot -w
.\fastboot flash boot boot.img
.\fastboot flash dtbo dtbo.img
.\fastboot flash modem modem.img
.\fastboot flash reserve reserve.img
.\fastboot flash recovery recovery.img
.\fastboot --disable-verity flash vbmeta vbmeta.img
.\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
.\fastboot reboot fastboot
.\fastboot flash abl abl.img
.\fastboot flash aop aop.img
.\fastboot flash bluetooth bluetooth.img
.\fastboot flash cmnlib cmnlib.img
.\fastboot flash cmnlib64 cmnlib64.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash dsp dsp.img
.\fastboot flash hyp hyp.img
.\fastboot flash imagefv imagefv.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash LOGO LOGO.img
.\fastboot flash multiimgoem multiimgoem.img
.\fastboot flash odm odm.img
.\fastboot flash oem_stanvbk oem_stanvbk.img
.\fastboot flash opproduct opproduct.img
.\fastboot flash qupfw qupfw.img
.\fastboot flash storsec storsec.img
.\fastboot flash tz tz.img
.\fastboot flash uefisecapp uefisecapp.img
.\fastboot flash xbl xbl.img
.\fastboot flash xbl_config xbl_config.img
.\fastboot flash system system.img
.\fastboot flash vendor vendor.img
.\fastboot flash product product.img
.\fastboot reboot
Few notes
User data is wiped, again, lol
reserve partition flashing can produce error msg: FAILED (remote: '(reserve_a) No such partition'), it is OK but others should not Fail
Device will reboot once during the flashing process
After reboot, device will NOT go into fastboot screen but instead go into stock recovery screen, however fastboot will pick up and resume flashing the rest, ONLY IF YOU ARE UNDER POWER-SHELL, so DO NOT flash under DOS
if anything else fails besides the reserve partition, repeat step 7
Device will boot into system, you may use the OS updater to upgrade to the lastest firmware then relock bootloader or proceed with root with Magisk
Hope this will save you some precious time. Major kudos for previous contributions from post 1 and post 2.
All steps are recorded from memory, please let me know if any mistakes are in need of correction.
Tested working on Dec 5, 2020

I have followed this method (and literally anything else I can find) to a T and the farthest I get is when flashing the ROM, I get "Flashing is not allowed for critical partitions" - which I can only find people saying that means the bootloader needs to be unlocked, but it is?! It's definitely, fully unlocked. No matter what I try I can't get around that error during the flashing process and it stays stuck on the T-Mobile ROM.

I had the same issue with the critical partition error when I was under DOS and during the reboot process, 7T will only boot into the normal fastboot screen. In here, I always gets that error over and over. I stopped getting it when 7T boot into the recovery screen under power-shell.
Few things to make sure:
Stock cable
Power-shell in admin priv
Use local fastboot binary
If things still not looking up, I would try a different PC.
Good luck.

Yup, those are all correct and I have tried another PC. Now I'm scared I may have bricked it, because other than booting it into FastBoot it just loops on the "Your device is corrupted" screen. Any thoughts? It did this after I re-locked the bootloader to try unlocking Critical again.

Is your device is corrupt screen the one that gets displayed after the MSM EDL flashing?
If so, does your device auto boot into fastboot afterwards?
My thinking is after MSM tool, your device is corrupted, then you unlock critical flashing. Afterwards, the partitions being flashed in by the fastboot should prevent the corrupt msg being displayed. If you are all getting corrupt msg after the fastboot reboot, then something is off with the first part of your fastboot flashing.

It's that same screen, yes, but the phone is just stuck in a boot loop. It says "Your device is corrupt. It can't be trusted and will not boot." and goes black and says it again, over and over. It will not automatically boot to Fastboot, but if I mess with the volume/power keys, I can get it to the fastboot screen. But no matter what else I do it goes back to an endless loop with the corrupt message.

I think some error could have been carried over from the MSMDownloadTool flashing process. My 7T always auto boot into fastboot screen after the corrupt msg display without interaction on my end.
Try your EDL flashing part again, and at the same time, re-download the preparation step 4 file over again and try use that instead afterwards if you are still stuck on the boot loop, just to prevent possible discrepancies might be caused by corrupted file (unlikely, but it doesn't hurt right?)

Gotcha, thanks. Got it into EDL mode and am running MSM right now.

Okay, EDL/MSM was successful, then I tried flashing the ROM per the instructions again but got the same error of being unable to flash to Critical. It no longer does the "device is corrupt" error boot loop, but the phone ONLY boots to Fastboot now, no matter what I do.

Best of luck. Hope the pain stops for you soon, hah.

Can you post your power-shell display message for the last flash-all.bat invocation?

Also, are you using .\fastboot flashing unlock_critical in admin priv power-shell to unlock the bootloader after MSM flashing?

Yes, that's what I was using. Unlocking it wasn't an issue, and when I try any type of unlock command it says it's already unlocked, which I believe to be true. But it still refuses to write to critical.
I can post my powershell message when I get back home. But basically it ran fine at first, it did fail at the "reserve" portion which I read to be normal, but after that it kept saying cannot flash to critical.
I just got the phone today so I hope it's not already bricked. But the fact that I got it out of the "corrupt" loop gives me hope I can fix it. Is there any place to download the stock T-Mobile ROM so I can try and start over? Assuming it will even let me flash it. I couldn't find any by searching.

One observation I found to be very interesting.
The device should have been locked by the MSM tool through EDL flashing; yet, your device shows it's already unlocked.
I think the issue is still with your EDL flashing process as it should lock the bootloader then use flashing unlock critical to prevent critical partition flashing errors.
Also, your device is not bricked as long as you can still perform EDL flash. Just kept going and you can get it working without having to EDL flash anything else.

I see, thanks for the insight. So just so I don't mess anything up further, exactly what steps in what order do you recommend I perform?

My first instinct is to keep trying the EDL flashing until you can perform flashing critical unlock properly.
If things keep on failing, try to change your PC, driver, or other environmental variables.
It's just a painful process of elimination that you have to stick to.
Also, unless there are potential hardware issues, flashing like this shouldn't carry any more risk to brick your device compare to just using your device regularly. You aren't changing the hardware/software that is responsible for facilitating EDL.

EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com

seryniti said:
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Click to expand...
Click to collapse
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.

seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Let me know what you find. I didn't even know there was other versions of MSM so I'll try that as well. I'd love to just at least get mine out of only being able to boot to Fastboot.

seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Your 7T should be on the stock recovery screen when fastboot reboot fastboot completes. If your device boots into T-Mobile boot screen or bootloader, something is wrong with your env on PC.
You should never see T-Mobile boot screen at any given time during fastboot flashing process.
The final reboot should complete the conversion and boot into the intentional version OS.

Question Qualcom CrashDump Mode After OTA, Magisk Lost Root

I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?

I'd suggest waiting for the next OTA and do it again.
However, I don't understand why you did the uninstall, update, install to the other partition etc part. I usually just do the following steps:
Install OTA (do NOT reboot yet)
Install Magisk in the other partition
Reboot
So far it has worked for me for each update.

Ecna said:
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
Click to expand...
Click to collapse
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good

Appreciative said:
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Click to expand...
Click to collapse
How would I copy my good partition to the broken one?

viktak said:
I'd suggest waiting for the next OTA and do it again.
Click to expand...
Click to collapse
The current OTA is still pending, and I don't have root anymore, so waiting won't get me anywhere.
However, I don't understand why you did the uninstall, update, install to the other partition etc part.
Click to expand...
Click to collapse
I just followed the Magisk instructions here:
https://topjohnwu.github.io/Magisk/ota.html

Ecna said:
How would I copy my good partition to the broken one?
Click to expand...
Click to collapse
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm

Appreciative said:
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Click to expand...
Click to collapse
Thank you, I'll dig into these links!

I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?

sumfahg said:
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
Click to expand...
Click to collapse
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version

TheGhost1951 said:
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
Click to expand...
Click to collapse
I am on Windows, where can I download fastboot enhanced?

sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
There is an xda threads on it. Just search xda forums for fastboot enhanced.

sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)

zjhjack123 said:
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.

Ecna said:
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Click to expand...
Click to collapse
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.

Appreciative said:
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
Click to expand...
Click to collapse
Fastboot --set-active=a or b which ever you need in bootloader mode

Ecna said:
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Click to expand...
Click to collapse
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.

zjhjack123 said:
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
Click to expand...
Click to collapse
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?

Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
When you flash tom in the system, it only update the firmware in another slot. So if your current good rom is in slot b, you can just boot into slot b and apply system update via local update, the updated rom will be in slot a.

Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
If you have the images:
fastboot flash system_a system_a.img
fastboot flash system_b system_b.img
it's also possible to pull the whole partitions down with msm tool (press f8, select partitions and readback, files go to c:\) or using dd.
If not, #19 above

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

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
[email protected]
wtywtykk
mark332
alexander宇
daxiaamu
Following is the steps to flash the OTA updates:​
Step 1:
Download all the usual tools
Download Fastboot Enhance
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449 Global A07: eea73728a1b945ea8e3ff6b628495af5.zip
ColorOS: Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
Reboot back into bootloader, as in step 2 item 4.
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin
Step 4:
Boot into fastbootd (Phone Screen: The one with language selection)
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is YES
Flash payload.bin
Step 5:
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img exits
Boot into fastbootd (Phone Screen: The one with language selection)
Use Fastboot Enhance or command line
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
Android SDK
Get the firmware from this post
Firmware also availble at https://yun.daxiaamu.com/OnePlus_Roms/一加11/
CPH2449GDPR_11_A.06_2023010723370128.zip
Abandon_PHB110_V13_202301030.zip (only oplusstanvbk.img needed)
Step 2:
To boot into bootloader from Android
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
Run $ adb reboot-bootloader
After enter into fastboot (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Run $ fastboot flashing unlock
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,
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Go into bootloader again. follow step 2
Run $ fastboot flashing lock
Again, go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.

sth_safal said:
Nice! Would it be possible to write the steps, please?
I believe you had to unlock bootloader? Have you tried locking bootloader after? Thanks.
Click to expand...
Click to collapse
i tried to, after locking the bootloader. the system not able to set the screenlock pattern

kaijern said:
i tried to, after locking the bootloader. the system not able to set the screenlock pattern
Click to expand...
Click to collapse
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..

sth_safal said:
Ohh, that's odd. Is it just screen lock pattern or also pin locks that had issue? No luck with factory reset either I would imagine..
Click to expand...
Click to collapse
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?

alexander宇 said:
Both. I had that problem as well after unlocking the bootloader of my Chinese Onplus 11. According to a Chinese post it's a common issue and you need to keep relocking/unlocking until you are able to set the pin/pattern. Worked for me.
Click to expand...
Click to collapse
I am the same.
Can I recover with relock?

sth_safal said:
Hmm.. Thanks.
So just unlock again and relock, setup phone and try out if pin works? If it doesn't repeat the post again? Would it be possible to link the Chinese post, please? Couldn't find any info online.. Did you move to Oxygen Os as well?
Click to expand...
Click to collapse
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
Since its worling. I will wait for the international version to be avilable after Feb 7 and try to do a complete flash again. By that time is just all about from Oxygen to Oxygen nothing risky.

alexander宇 said:
yep, that's how I resolved the problem. Don't remember where I saw it, probably a Bilibili video comment. Not yet haven't got a chance to switch, been traveling.
Click to expand...
Click to collapse
I tried to relock it.
fastboot oem lock、fastboot flashing lock、fastboot oem unlock、fastboot flashing unlock
Every command gives me an error.

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

if you can give a step by step, or actually a video, that would actually be amazing. i fear for my phone haha

Is this version of package able to receive the OTP update of OOS?

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

sunxutian said:
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
Click to expand...
Click to collapse
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
Why can't you boot into fastbood? Did you try fastboot reboot fastboot?

oprocks said:
i bricked mine as well, trying to do the same of reflashing payload.bin, but fastbootenchaned won't flash payload.bin because i can't reboot it into "fastbootd mode". any idea?
Click to expand...
Click to collapse
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver

sunxutian said:
what you might need to do is to reinstall oneplus driver, I got unknown device when booting into fastbootd and fixed it by reinstalling driver
Click to expand...
Click to collapse
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?

oprocks said:
"fastboot devices" works.
this is the actual error:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.016s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
any ideas?
Click to expand...
Click to collapse
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader

sunxutian said:
Try fastboot -w to clean user data, also you can try flash boot.img or everything which can be flashed from bootloader
Click to expand...
Click to collapse
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?

How To Guide Reverting back to ColorOS (PHB110)

Steps I used to revert back to ColorOS on my Chinese Model Oneplus 11. I saw a few folks asking how to. This worked for me, all features working.
Prereq
-ADB
-Fastboot Enhance
-PHB110 .zip payload
-ocdt.img (scroll to the bottom and download)
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
adb reboot-bootloader
enter into fastboot
fastboot flashing unlock
adb reboot-bootloader
Download and unzip PHB110 Link to firmware
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO
Flash payload.bin
Boot into fastbootd
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is YES
Flash payload.bin
Download and unzip ocdt.img (this is the ColorOS version)
enter into fastboot
fastboot flash ocdt ocdt.img
Fastboot reboot
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
adb reboot-bootloader
After enter into fastboot
fastboot flashing lock
fastboot reboot

I can not setup the phone, I can not pass the network screen

acm1108 said:
Steps I used to revert back to ColorOS on my Chinese Model Oneplus 11. I saw a few folks asking how to. This worked for me, all features working.
Prereq
-ADB
-Fastboot Enhance
-PHB110 .zip payload
-ocdt.img (scroll to the bottom and download)
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
adb reboot-bootloader
enter into fastboot
fastboot flashing unlock
adb reboot-bootloader
Download and unzip PHB110 Link to firmware
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO
Flash payload.bin
Boot into fastbootd
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is YES
Flash payload.bin
Download and unzip ocdt.img (this is the ColorOS version)
enter into fastboot
fastboot flash ocdt ocdt.img
Fastboot reboot
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
adb reboot-bootloader
After enter into fastboot
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
Did you use the ocdt.img backed up from your OnePlus 11, or did you get it from another source? I'm asking because the ocdt.img is unique to each device, rather than being specific to the operating system.

softhive said:
Did you use the ocdt.img backed up from your OnePlus 11, or did you get it from another source? I'm asking because the ocdt.img is unique to each device, rather than being specific to the operating system.
Click to expand...
Click to collapse
I used someone else's and it worked fine.

acm1108 said:
Steps I used to revert back to ColorOS on my Chinese Model Oneplus 11. I saw a few folks asking how to. This worked for me, all features working.
Prereq
-ADB
-Fastboot Enhance
-PHB110 .zip payload
-ocdt.img (scroll to the bottom and download)
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
adb reboot-bootloader
enter into fastboot
fastboot flashing unlock
adb reboot-bootloader
Download and unzip PHB110 Link to firmware
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO
Flash payload.bin
Boot into fastbootd
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is YES
Flash payload.bin
Download and unzip ocdt.img (this is the ColorOS version)
enter into fastboot
fastboot flash ocdt ocdt.img
Fastboot reboot
Go in to OxygenOS, skip all the setup. DO NOT SET THE PIN
Turn On developer mode
Turn on USB Debug
Turn on OEM-unlock
adb reboot-bootloader
After enter into fastboot
fastboot flashing lock
fastboot reboot
Click to expand...
Click to collapse
thanks, it work for me

NightS12321 said:
thanks, it work for me
Click to expand...
Click to collapse
That's what I like to hear good!

Where do I find the ocdt img in my stock firm, I did not find it after dump my PayLoad Bin?
I was not successful using your file. Could not pass networksettings.

lassetth said:
Where do I find the ocdt img in my stock firm, I did not find it after dump my PayLoad Bin?
I was not successful using your file. Could not pass networksettings.
Click to expand...
Click to collapse
Do you have a Chinese model...?

Canuck Knarf said:
Do you have a Chinese model...?
Click to expand...
Click to collapse
No, 2449 EU/Global

lassetth said:
No, 2449 EU/Global
Click to expand...
Click to collapse
look at post this is for phb 110 china verson

Canuck Knarf said:
look at post this is for phb 110 china verson
Click to expand...
Click to collapse
Ok, Thanks!

lassetth said:
Ok, Thanks!
Click to expand...
Click to collapse
this may help you
[WIP] Porting LineageOS 20 to the Oneplus 11
We all know the path OnePlus/Oppo went with development, MSM Tools and all, and I want to make it clear and short : I'm going to work on this phone no matter what. The OnePlus 10 series were a failure in this regard and I don't want the OnePlus...
forum.xda-developers.com

You have to be rooted to install but dose a complete backup

But if you have ColorOS payload file of your model....and have payload dumper or python you can get all your img files for the payload file

Thank sir. I come back to phb10 color os ok