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
Attention: this ROM only for the migration from COS Android 11 to OOS Android 11. Do not try to use it for switching to/from other version of Android. This can lead to the boot loop.
You can find ROMs maintained by @penguinus which are more universal than these and allow to switch between Android versions.
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.11 zip:
4.3 GB file on MEGA
mega.nz
boot.img OxygenOS A.11 https://mega.nz/file/RVAXCJya#SXukMoZbmWqScbSuE3iVtTEYYkYlOt8eajfV8xCIOdI
Fastboot ROM OxygenOS A.08 zip:
https://mega.nz/file/LYFElKaL#9-gO2xVEenHufecxaDSTRTUuCuJY-QlxIRRbSUtHfo8boot.img OxygenOS A.08 https://mega.nz/file/kJQyCCTS#VHy7tzjPEhDlrtZm1v1AB-lmEN4ckx5dUVlnX0YZ0gs
Fastboot ROM OxygenOS A.07 zip:
https://mega.nz/file/4JZ2XRiT#7fIk6nL0V9zkr02CcGL9tgxiVJPfJpYN1S8jA-DAxE8boot.img OxygenOS A.07 https://mega.nz/file/dZpHiAYI#eEuNHhz7nO0dCqFJrl3kK57s2PAnwr7zfa2UvBecgAE
Fastboot ROM OxygenOS A.06 zip:
https://mega.nz/file/QZQQUZqZ#3PntyL67g71AneyGKjPD5UH-gVyTxHk21MkLoTxojpA
Fastboot ROM OxygenOS A.05 zip:
https://mega.nz/file/MBgg2AjJ#98vdiFZPUCMm9gskDu5SQmic-D8jHZ3snO8pLbqrbFY
Fastboot ROM OxygenOS A.04 zip:
https://mega.nz/file/oFhjDKrI#jUajmG5fAeH1TvYS3b6EZB6Pwj5MzDpAt47fwr6gurMhttps://disk.yandex.ru/d/U8WxNFOFU4rDfA
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).
[2022-07-20] add A.11 version of firmware (prepared by @penguinus)
[2022-10-12] add attention message about downgrading.
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?
bonez56 said:
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?
Click to expand...
Click to collapse
It has an option to upgrade without wipe.
Please read instructions more carefully (last part of instruction about upgrade from previous version)
Thanks for posting this.
bonez56 said:
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?
Click to expand...
Click to collapse
Choose update.bat to update and all your data is kept intact
Thank you so much, really appreciate it
Valdem said:
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:
File on MEGA
mega.nz
Яндекс
Найдётся всё
disk.yandex.ru
Credits:
- @abhinavgupta371
- @HELLBOY017
- @penguinus
Click to expand...
Click to collapse
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 ?
borg79 said:
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 ?
Click to expand...
Click to collapse
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.
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
Solved
deleted
miky03 said:
I have the mt2110 model comming from colorOs v12
i can boot to fastmode what should I do please help
Click to expand...
Click to collapse
Try to flash again. By log it looks like your phone didn't rebooted to fastbootd correctly when install script tried to do that.
miky03 said:
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
Click to expand...
Click to collapse
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).
Valdem said:
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).
Click to expand...
Click to collapse
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.
miky03 said:
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.
Click to expand...
Click to collapse
it is ok. fastbootd mode looks like recovery. but script should not fail with message 'fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.'
Where is bootloader drivers for OP9RT？
miky03 said:
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.
Click to expand...
Click to collapse
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.
miky03 said:
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.
Click to expand...
Click to collapse
Have you put your Window OS into "testsigning" mode before executing the batch file ?
Valdem said:
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.
Click to expand...
Click to collapse
Hi i did until 3. Then reboot to this menu in cmd waiting for any device
borg79 said:
Have you put your Window OS into "testsigning" mode before executing the batch file ?
Click to expand...
Click to collapse
Hi im running on win 7 64bit.what is testing mode?
Related
Hi, I rooted my Pixel 2XL a couple of weeks ago and just recently decided to remove the root and lock the bootloader. So I just locked the bootloader, which I thought would only delete all data and reset it back to normal. But instead the whole operative system got removed. When I noticed that I tried to install the factory image. But that only gave me errors...
This is what happens every times:
Code:
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.004s
--------------------------------------------
Bootloader Version...: TMZ12a
getvar:version-baseband FAILED (remote: 'unknown command')
getvar:serialno FAILED (remote: 'GetVar Variable Not found')
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (remote: 'unknown command')
Checking 'product' FAILED
Could not getvar for 'product' (remote: 'GetVar Variable Not found')
fastboot: error: requirements not met!
Press any key to exit...
And this happens a second time:
Code:
Sending 'bootloader' (55680 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Sending 'radio' (60428 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Unknown error))
getvar:serialno FAILED (Write to device failed (Unknown error))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Unknown error))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...
Anyone who has any idea what to do?
Sadly, 99% chance you have created a very expensive coaster for your beer... Hopefully you can RMA it.
The phone NEEDS to be returned to 100% factory stock BEFORE locking the botloader or it bricks the phone. There MAY had been a few cases of folks sideloading an OTA afterwards but it might just be chatter like Bigfoot sightings...
CyberpodS2 said:
Sadly, 99% chance you have created a very expensive coaster for your beer... Hopefully you can RMA it.
The phone NEEDS to be returned to 100% factory stock BEFORE locking the botloader or it bricks the phone. There MAY had been a few cases of folks sideloading an OTA afterwards but it might just be chatter like Bigfoot sightings...
Click to expand...
Click to collapse
Thanks for the response. I will make sure I think of that next time. Fortunately it was only the cable that needed switching for it to be able to send the files.
You did the one thing that you must not do. Good luck with unbricking.
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
fjgato said:
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
Click to expand...
Click to collapse
Nevermind, just tried another cable I found and it worked . I don't know how to change the title thought.
fjgato said:
Nevermind, just tried another cable I found and it worked . I don't know how to change the title thought.
Click to expand...
Click to collapse
Just report your thread to the moderator team designated to your area, which I am not, and have them change the thread title to what you want. Glad you figured out your problem :good::laugh:
fjgato said:
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
Click to expand...
Click to collapse
I'm having the same trouble that you did got the same stuff to pull up and everything all you did was switch out your data cable
On a Saturday midnight, I thought I wanted to revert back to Android 8.1 on my Pixel. However, I made a big mistake doing it at midnight, mistakenly flashing the user debug AOSP instead. My phone is now corrupted and will always stuck at the white Google logo with me unable to undo the damage. What I have tried so far is flashing the factory images via ADB update and Fastboot, but it seems like the software is failing to register the phone as a Pixel.
I keep getting fail messages with ADB updates reporting
E: footer is wrong
Update package verification took 0.1s (result 1).
E: Signature verification failed
E: error: 21
Click to expand...
Click to collapse
And fastboot reporting
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.002s
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: 'unknown command')
getvar:serialno FAILED (remote: 'GetVar Variable Not found')
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvarroduct FAILED (remote: 'unknown command')
Checking 'product' FAILED
Could not getvar for 'product' (remote: 'GetVar Variable Not found')
fastboot: error: requirements not met!
Click to expand...
Click to collapse
I would really appreciate any help because I'm in a really desperate situation, or in case the situation can't be fixed, would replacing the hardware revive the phone. Thank you in advance.
Im trying to flash a rom and get errors. I'm not sure why.
I have the most up to date adb drivers, usb debugging is on.
Erasing 'system' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'system_ext' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'odm' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'product' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'vendor' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Sending 'boot_a' (98304 KB) OKAY [ 2.327s]
Writing 'boot_a' OKAY [ 0.385s]
Finished. Total time: 3.219s
Sending 'dtbo' (24576 KB) OKAY [ 0.585s]
Writing 'dtbo' OKAY [ 0.085s]
Finished. Total time: 0.689s
Sending 'odm' (102400 KB) OKAY [ 2.414s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
Nvm Fixed by using FastbootD
hi i got the OS 12 air update today i install it into my phone but the phone was buggy freezing something not right, i try to downgrade back to OS 11 using local update, this option is no longer available so i did factory reset the phone stuck on fastboot
i try TOOL ALL IN ONE didnt work i try fastboot rom nothing works anymore any idea how to fix it
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.125s]
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
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 = 203820072 (99521 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1147] Writing root inode (hot node), 1b800 0 200 at offset 0x00112640
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001be01, 0001be02
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1b800 0 200 at offset 0x00112641
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001be03, 0001be04
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1b800 0 200 at offset 0x00112642
[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001be00
Info: Overprovision ratio = 0.640%
Info: Overprovision segments = 635 (GC reserved = 320)
[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.011s]
Writing 'userdata' OKAY [ 0.004s]
Erasing 'metadata' OKAY [ 0.007s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 7.984s
Sending 'boot_b' (98304 KB) OKAY [ 2.218s]
Writing 'boot_b' OKAY [ 0.367s]
Finished. Total time: 2.669s
Sending 'dtbo' (16384 KB) OKAY [ 0.371s]
Writing 'dtbo' OKAY [ 0.067s]
Finished. Total time: 0.471s
Sending 'modem_b' (165396 KB) OKAY [ 3.737s]
Writing 'modem_b' OKAY [ 0.901s]
Finished. Total time: 4.785s
Sending 'reserve' (250164 KB) OKAY [ 5.607s]
Writing 'reserve' FAILED (remote: '(reserve_b) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 2.200s]
Writing 'recovery' OKAY [ 0.442s]
Finished. Total time: 2.726s
Sending 'vbmeta' (8 KB) OKAY [ 0.013s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.035s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.031s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.039s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.019s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'bluetooth' (828 KB) OKAY [ 0.028s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib' (384 KB) OKAY [ 0.017s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.018s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.009s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.468s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'hyp' (480 KB) OKAY [ 0.024s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.007s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'keymaster' (248 KB) OKAY [ 0.020s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.161s]
Writing 'LOGO' OKAY [ 0.044s]
Finished. Total time: 0.232s
Sending 'multiimgoem' (16 KB) OKAY [ 0.015s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'odm' (912 KB) OKAY [ 0.028s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.065s]
Writing 'oem_stanvbk' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'opproduct' (586912 KB) OKAY [ 13.173s]
Writing 'opproduct' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'qupfw' (72 KB) OKAY [ 0.016s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'storsec' (24 KB) OKAY [ 0.009s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'tz' (3092 KB) OKAY [ 0.078s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.017s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl' (3120 KB) OKAY [ 0.075s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.013s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784708 KB) OKAY [ 17.615s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB)
if tis happen to any of you i have fix the problem i guess by luck i give up trying all the old methods nothing work
i download twrp-3.6.0_11-0-hotdog.img
i use cmd command fastboot flash boot twrp-3.6.0_11-0-hotdog.img
i repeat the command few times then the phone reboot to the languages screen from there i click at
format system
OS 12 been formatted and my phone back to OS11
note TWPR never open but i dont care as long the problem fixed
Starting from here in your log.
Code:
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Fastboot mode was not available so, you were rebooted back into bootloader mode, critical partitions can not be flashed in bootloader mode.
Newer devices have two modes for fastboot commands.
bootloader (fastboot).
fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
---
With 7T, fastbootd mode is part of the recovery image.
So you need to flash a compatible version of stock recovery or a custom recovery that supports fastbootd mode.
Then you you can run the fastboot update in bootloader mode.
The update can then switch into fastbootd mode when needed.
---
I updated my 7T a few weeks ago from 11 to 12 but, I used the local update option..
MAGISK MODULE ❯ Universal SafetyNet Fix 2.3.1 - [ xdaThread ] - Post #2,514
Cheers.
PS.
For reference.
The fastbootd (fastboot_d) mode (for the lack of a better description) is a low level recovery.
This mode allows flashing secure (critical) partitions that are not available to flash in bootloader.
Years ago..
Pixel 2XL, OnePlus 5T and some other devices supported unlock critical that allowed flashing secure (critical) in regular fastboot (bootloader).
This shift to fastbootd never made sense to me because what is more critical than being able to flash the actual bootloader. ¯\_(ツ)_/¯