Development [FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices

Search This thread

Valdem

Senior Member
Nov 3, 2015
65
53
Greetings,


I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing.

PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT UNLOCKING DEVICE WILL WIPE INTERNAL STORAGE COMPLETELY.

THIS ROM UNOFFICIAL AND BASED ON IMAGES MANUALLY EXTRACTED FROM MT2111 DEVICES AND OTA UPDATES


This ROM can be used on MT2110 devices (Chinese version initially delivered with ColorOS) for migration to OxygenOS
Device bootloader can be locked after flashing this ROM

Everything related to SafetyNet checks is working on this ROM like on original MT2111 devices.
If device is not rooted it can receive OTA updates.

Known issues:
- Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111". Fixed in latest firmwares.


Migration instructions:
- On your PC, install bootloader drivers for OP9RT and check if device is recognized in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (adb and fastboot)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 RT to bootloader mode.
- Connect the OP9RT to your PC
- On your PC open command line window in the uncompressed folder,
- type install.bat
- wait till device boot to "Setup wizard" screen (it will take 5-7 min)
- at this point device bootloader can be locked if you need this.

Upgrade instruction (for devices with OxygenOS where standard updater decline update):
- follow the installation procedure till
- instead of install.bat you need to run upgrade.bat in command line window
- user data will be preserved


Good luck!

Edit:
Some linux users reports issue with device wipe during installation. It is related to fastboot dependencies. It requires android platform tools installed.
As an alternative after final reboot (device should reboot automatically twice during installation) device will boot to recovery mode where you need to wipe it manually.



DOWNLOAD LINKS:
Fastboot ROM OxygenOS A.08 zip:
boot.img OxygenOS A.08
Fastboot ROM OxygenOS A.07 zip:
boot.img OxygenOS A.07
Fastboot ROM OxygenOS A.06 zip:

Fastboot ROM OxygenOS A.05 zip:

Fastboot ROM OxygenOS A.04 zip:

Credits:
- @abhinavgupta371
- @HELLBOY017
- @penguinus

Updates:
[2022-02-22] fixed installation and upgrade for some specific device state (if you have installed previous version successfully, you doesn't need re-installation).
[2022-03-01] add A.05 version of firmware.
[2022-03-11] add A.06 version of firmware.
[2022-03-20] add A.07 version of firmware.
[2022-05-23] add A.08 version of firmware.
[2022-06-06] update A.08 version of firmware (fixed issue with telegram by @penguinus).
 
Last edited:

bonez56

Member
Mar 30, 2008
31
6
Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?
 
  • Like
Reactions: raghu102 and archz2

Valdem

Senior Member
Nov 3, 2015
65
53
Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?
It has an option to upgrade without wipe.
Please read instructions more carefully (last part of instruction about upgrade from previous version)
 
Last edited:
  • Like
Reactions: raghu102 and archz2

ThingVn

Senior Member
Nov 20, 2014
73
20
VN
Cảm ơn vì điều này. Tôi đang chạy cái này trên MT2110 của mình (mặc dù là phiên bản A03).
Điều này có thể bị bẩn được hiển thị trên đầu cài đặt gốc hay nó sẽ xóa tất cả các cài đặt / ứng dụng của tôi?
Choose update.bat to update and all your data is kept intact
 

borg79

Senior Member
Sep 11, 2010
140
21
Greetings,


I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing.

PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT UNLOCKING DEVICE WILL WIPE INTERNAL STORAGE COMPLETELY.

THIS ROM UNOFFICIAL AND BASED ON IMAGES MANUALLY EXTRACTED FROM MT2111 DEVICES AND OTA UPDATES


This ROM can be used on MT2110 devices (Chinese version initially delivered with ColorOS) for migration to OxygenOS
Device bootloader can be locked after flashing this ROM

Everything related to SafetyNet checks is working on this ROM like on original MT2111 devices.
If device is not rooted it can receive OTA updates.

Known issues:
- Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111".


Migration instructions:
- On your PC, install bootloader drivers for OP9RT and check if device is recognized in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (adb and fastboot)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 RT to bootloader mode.
- Connect the OP9RT to your PC
- On your PC open command line window in the uncompressed folder,
- type install.bat
- wait till device boot to "Setup wizard" screen (it will take 5-7 min)
- at this point device bootloader can be locked if you need this.

Upgrade instruction (for devices with OxygenOS where standard updater decline update):
- follow the installation procedure till
- instead of install.bat you need to run upgrade.bat in command line window
- user data will be preserved


Good luck!

Edit:
Some linux users reports issue with device wipe during installation. It is related to fastboot dependencies. It requires android platform tools installed.
As an alternative after final reboot (device should reboot automatically twice during installation) device will boot to recovery mode where you need to wipe it manually.



DOWNLOAD LINKS:
Fastboot ROM OxygenOS A.04 zip:

Credits:
- @abhinavgupta371
- @HELLBOY017
- @penguinus
Thank you for the good work ! I install it successfully using the upgrade.bat and able to relock the bootloader ! If OnePlus release its official rom in the future, would it be possible for me to upgrade to those rom ?
 
  • Like
Reactions: raghu102

Valdem

Senior Member
Nov 3, 2015
65
53
Thank you for the good work ! I install it successfully using the upgrade.bat and able to relock the bootloader ! If OnePlus release its official rom in the future, would it be possible for me to upgrade to those rom ?
If you talk about next OTA - then answer is YES, because you lock bootloader.
The main requirement for OTA - unmodified data on device system's partitions.

If you talk about official MSMDownload Tools. Then nothing can stop you to flash it. It is low level firmware, which can restore almost everything.
 

Crackeds

Senior Member
Jan 25, 2012
52
9
Gran Canaria
OnePlus 9RT
I own the chinese version with 8/256 GB. Will this rom work? I know, its the only version, thats not coming to india, but i would like to install this rom for better use.. Thanks for answering :)
 

Valdem

Senior Member
Nov 3, 2015
65
53
hi i did like you write unfortunly i get the

QUALCOMM CrashDump Mode:
dm-verity device corrupted verity_ctr

I have the mt2110 model comming from colorOs v12

i can boot to fastmode what should I do please help


D:\op9rt-oos-A04-fastboot-rom>install.bat
###################
# Formatting data #
###################

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

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 470920600 (229941 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 2b800 0 200 at offset 0x00178176
[f2fs_write_default_quota:1357] Writing quota data, at offset 0002be01, 0002be02
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178177
[f2fs_write_default_quota:1357] Writing quota data, at offset 0002be03, 0002be04
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178178
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0002be00
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 963 (GC reserved = 484)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.004s]
Writing 'userdata' OKAY [ 0.012s]
Finished. Total time: 1.630s
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'metadata' (44 KB) OKAY [ 2.541s]
Writing 'metadata' OKAY [ 0.886s]
Finished. Total time: 5.592s
#######################################################################
# Oxygen OS Flasher For OnePlus 9RT by abhinavgupta371 and HELLBOY017 #
# updated by Va1d3m #
#######################################################################
#################################
# Flashing firmware into slot A #
#################################
Setting current slot to 'a' OKAY [ 0.008s]
Finished. Total time: 0.013s
#################################
# Flashing bootloader img's #
#################################
Sending 'boot_a' (196608 KB) OKAY [ 5.309s]
Writing 'boot_a' OKAY [ 0.384s]
Sending 'boot_b' (196608 KB) OKAY [ 4.253s]
Writing 'boot_b' OKAY [ 0.381s]
Finished. Total time: 10.370s
Sending 'modem_a' (190060 KB) OKAY [ 5.191s]
Writing 'modem_a' OKAY [ 0.376s]
Sending 'modem_b' (190060 KB) OKAY [ 4.143s]
Writing 'modem_b' OKAY [ 0.435s]
Finished. Total time: 10.186s
Sending 'vendor_boot' (196608 KB) OKAY [ 5.316s]
Writing 'vendor_boot' OKAY [ 0.430s]
Finished. Total time: 5.767s
Sending 'vbmeta' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
Finished. Total time: 0.018s
##########################
# Rebooting to fastbootd #
##########################
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
#################################
# Flashing fastbootd img's #
#################################
fastboot: error: Could not check if partition abl has slot all
fastboot: error: Could not check if partition aop has slot all
fastboot: error: Could not check if partition bluetooth has slot all
fastboot: error: Could not check if partition cpucp has slot all
fastboot: error: Could not check if partition devcfg has slot all
fastboot: error: Could not check if partition dsp has slot all
fastboot: error: Could not check if partition dtbo has slot all
fastboot: error: Could not check if partition engineering_cdt has slot all
fastboot: error: Could not check if partition featenabler has slot all
fastboot: error: Could not check if partition hyp has slot all
fastboot: error: Could not check if partition imagefv has slot all
fastboot: error: Could not check if partition keymaster has slot all
fastboot: error: Could not check if partition mdtp has slot all
fastboot: error: Could not check if partition mdtpsecapp has slot all
fastboot: error: Could not check if partition multiimgoem has slot all
fastboot: error: Could not check if partition oplus_sec has slot all
fastboot: error: Could not check if partition oplusstanvbk has slot all
fastboot: error: Could not check if partition qupfw has slot all
fastboot: error: Could not check if partition qweslicstore has slot all
fastboot: error: Could not check if partition shrm has slot all
fastboot: error: Could not check if partition splash has slot all
fastboot: error: Could not check if partition tz has slot all
fastboot: error: Could not check if partition uefisecapp has slot all
fastboot: error: Could not check if partition vm-bootsys has slot all
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
###############################
# Resizing logical partitions #
###############################
Deleting 'odm_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'odm_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_ext_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'system_ext_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'vendor_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'vendor_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_carrier_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_carrier_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_company_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_company_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_engineering_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_engineering_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_heytap_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_heytap_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_manifest_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_manifest_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_preload_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_preload_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_region_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_region_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_stock_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Deleting 'my_stock_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'odm_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'odm_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_ext_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'system_ext_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'vendor_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'vendor_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_carrier_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_carrier_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_company_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_company_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_engineering_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_engineering_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_heytap_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_heytap_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_manifest_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_manifest_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_preload_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_preload_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_product_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_region_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_region_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_stock_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Creating 'my_stock_b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
###############################
# Flashing logical partitions #
###############################
Sending 'vendor' (621044 KB) OKAY [ 18.220s]
Writing 'vendor' FAILED (remote: '(vendor_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'odm' 1/2 (786428 KB) OKAY [ 17.645s]
Writing 'odm' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system' (760184 KB) OKAY [ 23.335s]
Writing 'system' FAILED (remote: '(system_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786428 KB) OKAY [ 18.302s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'product' (71056 KB) OKAY [ 1.946s]
Writing 'product' FAILED (remote: '(product_a) No such partition')
fastboot: error: Command failed
Sending 'my_carrier' (340 KB) OKAY [ 0.010s]
Writing 'my_carrier' FAILED (remote: '(my_carrier_a) No such partition')
fastboot: error: Command failed
Sending 'my_company' (340 KB) OKAY [ 0.009s]
Writing 'my_company' FAILED (remote: '(my_company_a) No such partition')
fastboot: error: Command failed
Sending 'my_engineering' (340 KB) OKAY [ 0.009s]
Writing 'my_engineering' FAILED (remote: '(my_engineering_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_heytap' 1/2 (786368 KB) OKAY [ 17.396s]
Writing 'my_heytap' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'my_manifest' (720 KB) OKAY [ 0.019s]
Writing 'my_manifest' FAILED (remote: '(my_manifest_a) No such partition')
fastboot: error: Command failed
Sending 'my_preload' (3520 KB) OKAY [ 0.097s]
Writing 'my_preload' FAILED (remote: '(my_preload_a) No such partition')
fastboot: error: Command failed
Sending 'my_product' (267700 KB) OKAY [ 7.769s]
Writing 'my_product' FAILED (remote: '(my_product_a) No such partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_region' 1/2 (781680 KB) OKAY [ 17.330s]
Writing 'my_region' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'my_stock' 1/2 (750628 KB) OKAY [ 16.707s]
Writing 'my_stock' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
#######################
# Rebooting to system #
#######################
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s
Press any key to continue . . .View attachment 5543893View attachment 5543895
From the log it seems that device was reconnected at the middle of installation or device can't correctly boot into fastbootd mode (need more investigation why). You can restart install.bat one more time from the bootloader state (like on second attached picture).
 

miky03

Senior Member
Apr 19, 2015
90
9
From the log it seems that device was reconnected at the middle of installation or device can't correctly boot into fastbootd mode (need more investigation why). You can restart install.bat one more time from the bootloader state (like on second attached picture).
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
 

Valdem

Senior Member
Nov 3, 2015
65
53
Thanks for fast response,
I tried already 2 times all the same.
As you mentioned after automatic reboot in the script im ending up in recovery mode.
It's weird.
You can check manually if device reboots into fastbootd properly.
Just do next steps and report here about output.
1. Open command line in folder with firmware.
2. Boot device in bootloader mode
3. run next commands to boot into fastbootd mode
Code:
fastboot reboot fastboot
4. device should reboot into fastbootd mode it looks like recovery mode.
5. after reboot run
Code:
fastboot devices
5. it should print serial number of device

if no serial number is printed - there is issue with fastboot binary.

Update: It looks like you have some issue with drivers.
 
Last edited:

miky03

Senior Member
Apr 19, 2015
90
9
It's weird.
You can check manually if device reboots into fastbootd properly.
Just do next steps and report here about output.
1. Open command line in folder with firmware.
2. Boot device in bootloader mode
3. run next commands to boot into fastbootd mode
Code:
fastboot reboot fastboot
4. device should reboot into fastbootd mode it looks like recovery mode.
5. after reboot run
Code:
fastboot devices
5. it should print serial number of device

if no serial number is printed - there is issue with fastboot binary.

Update: It looks like you have some issue with drivers.
Hi i did until 3. Then reboot to this menu in cmd waiting for any device
 

Attachments

  • 16455962551898277337984476742529.jpg
    16455962551898277337984476742529.jpg
    2.7 MB · Views: 136
  • 1645596226660979541258252084856.jpg
    1645596226660979541258252084856.jpg
    2.3 MB · Views: 138

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Does anyone have an error that can't send images on telegram?
    Both a07 & a08
    Found what causes an issue. It happens because of old fastboot version in firmware package, it does wipe before flashing incorrectly in some way.
    In order to fix it, you should do wipe/factory reset in system settings or in recovery. Please note all data will be erased. Don't forget to do backup and restore it after wipe!
    1
    FYI. Original post was updated with new version of A.08 firmware. @penguinus find the solution for issues with some application (telegram, gmail) which works with device filesystem. Issue is related to specific version of `platform-tools`, which used to flash device. Tools do device cleanup incorrectly. New version include fix for this issue.
    Issue can be fixed without full flashing of this firmware. Just by factory reset of device from the menu.

    !!!DO BACKUP!!! of you data before this operation. Do not use TWRP for this operation because TWRP storing dump of `userdata` partition and restoring it after factory reset most probably return the original issue.
  • 17
    Greetings,


    I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing.

    PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
    AND BE WARNED THAT UNLOCKING DEVICE WILL WIPE INTERNAL STORAGE COMPLETELY.

    THIS ROM UNOFFICIAL AND BASED ON IMAGES MANUALLY EXTRACTED FROM MT2111 DEVICES AND OTA UPDATES


    This ROM can be used on MT2110 devices (Chinese version initially delivered with ColorOS) for migration to OxygenOS
    Device bootloader can be locked after flashing this ROM

    Everything related to SafetyNet checks is working on this ROM like on original MT2111 devices.
    If device is not rooted it can receive OTA updates.

    Known issues:
    - Device name in settings displayed incorrectly "Lahaina for amd64" instead of expected "MT2111". Fixed in latest firmwares.


    Migration instructions:
    - On your PC, install bootloader drivers for OP9RT and check if device is recognized in Bootloader and Fastbootd modes.
    - Ensure you're using the LATEST version of SDK platform tools (adb and fastboot)
    - On your PC, download the Fastboot ROM zip from the download link below.
    - On your PC, unzip downloaded file
    - On your PC, navigate to its now-uncompressed folder
    - Reboot your OnePlus 9 RT to bootloader mode.
    - Connect the OP9RT to your PC
    - On your PC open command line window in the uncompressed folder,
    - type install.bat
    - wait till device boot to "Setup wizard" screen (it will take 5-7 min)
    - at this point device bootloader can be locked if you need this.

    Upgrade instruction (for devices with OxygenOS where standard updater decline update):
    - follow the installation procedure till
    - instead of install.bat you need to run upgrade.bat in command line window
    - user data will be preserved


    Good luck!

    Edit:
    Some linux users reports issue with device wipe during installation. It is related to fastboot dependencies. It requires android platform tools installed.
    As an alternative after final reboot (device should reboot automatically twice during installation) device will boot to recovery mode where you need to wipe it manually.



    DOWNLOAD LINKS:
    Fastboot ROM OxygenOS A.08 zip:
    boot.img OxygenOS A.08
    Fastboot ROM OxygenOS A.07 zip:
    boot.img OxygenOS A.07
    Fastboot ROM OxygenOS A.06 zip:

    Fastboot ROM OxygenOS A.05 zip:

    Fastboot ROM OxygenOS A.04 zip:

    Credits:
    - @abhinavgupta371
    - @HELLBOY017
    - @penguinus

    Updates:
    [2022-02-22] fixed installation and upgrade for some specific device state (if you have installed previous version successfully, you doesn't need re-installation).
    [2022-03-01] add A.05 version of firmware.
    [2022-03-11] add A.06 version of firmware.
    [2022-03-20] add A.07 version of firmware.
    [2022-05-23] add A.08 version of firmware.
    [2022-06-06] update A.08 version of firmware (fixed issue with telegram by @penguinus).
    5
    FYI. Updated OP with latest version A.08.
    2
    Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
    Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?
    2
    Thank you for this. I'm running this on my MT2110 (albeit the A03 version).
    Can this be dirty flashed over the top of the original install, or will it wipe all my settings/apps?
    It has an option to upgrade without wipe.
    Please read instructions more carefully (last part of instruction about upgrade from previous version)
    2
    Have you ever Rooted? If you are rooted, the system may have problems!
    You try to flash all again, let the phone boot and use normally, then use fastboot to relock
    no my phone is not rooted.. never tried to root.. i think i should manually upgrade my phone until the MSM tools are available. because if i brick it. there are no MSM tools available for 9rt to fixed.. or am i missing something