Fastboot not working - OnePlus 7T Questions & Answers

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

Related

[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!

Here is a patched MSM download tool for TMobile OP7T.
It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.
1) Download the patched MSM download tool: [removed]
2) Run the tool, connect your phone in EDL mode (see below how to do it if you don't know), ensure the "sha256 check" is NOT checked, click the Start button and wait until it's completed.
3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Now run the following fastboot command:
Code:
fastboot flashing unlock_critical
4) Bootloader is now unlocked. Update your fastboot executable, otherwise you'll encounter errors and modem issues. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Then boot the phone in fastboot mode, and follow the steps 7, 8 and 9 of this nice guide : https://forum.xda-developers.com/oneplus-7t/how-to/guide-t-mobile-brand-conversion-to-t4019495
How to enter EDL mode:
VQ30DE said:
[...] Getting into EDL mode took me a while because I'd never had to do that on any previous phone way back when I used custom ROMs. Note that in EDL mode the screen is blank, and apparently it times out after 10 seconds. So the way to do it is to power off the phone and disconnect the USB if it's connected. Then press both volume UP and DOWN at same time, then while holding those buttons down, insert the USB which should already be connected to your computer. The best way would be to have the MSM program already open on your PC, then put phone into ELD mode. I had my left hand holding the volume buttons on the phone (press hard with two fingers to be sure), used right hand to plug in USB, then right hand on the mouse to work MSM. Once the USB is plugged in, watch the MSM window and look for it to say "Connected". Then just click the Start button. You can then release the volume buttons on the phone and let MSM do its thing. [...]
Click to expand...
Click to collapse
Thanks you very murch
Tested and working? If something goes wrong is it easily fixed/corrected? This is to bypass the 7 day waiting period for the unlock token?
Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.
I can confirm steps 2 and 3 work. Step 2 for my case took 234 seconds so be patience. Now trying step 4.
Superboy58 said:
Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.
Click to expand...
Click to collapse
Confirmed! Presently bootloader unlocked and global rom installed. Will receive my unlock token on Friday......hee hee.
Wanted to say thank you for putting this together and making it dummy proof.
when i do a fastboot oem get_unlock_code, i get the following error message
FAILED (remote: Unknow command)
finished. total time: 0.006s
May I know where did i went wrong?
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
step 8 flash-all.bat, i got the following error messages, is it serious?
< waiting for any device >
Finished. Total time: 8.649s
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.005s]
Sending sparse 'system_a' 1/5 (523144 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 17.884s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 17.760s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Press any key to continue . . .
---------- Post added at 02:13 AM ---------- Previous post was at 01:52 AM ----------
I tried flash-all.bat again, there is no error message but the fastboot oem get_unlock_code, i get the following error message
FAILED (remote: 'Unknow command')
fastboot: error: Command failed
I checked the Build Number, it is indeed the version i downloaded.
Anyone can help?
---------- Post added at 02:26 AM ---------- Previous post was at 02:13 AM ----------
Guys, my dual sim is working and I no longer see the T-mobile locked. Is that all i need?
@warlord2045 you don't ever have to run the command you run "fastboot oem get_unlock_code".
Follow the instructions in the first post, it will work.
Thank you so much!
Superboy58 said:
@warlord2045 you don't ever have to run the command you run "fastboot oem get_unlock_code".
Follow the instructions in the first post, it will work.
Click to expand...
Click to collapse
Brilliant. If anyone is attempting this on Linux, I'd recommend getting the latest platform-tools straight from Google. Even the fastboot version from 2019 available in my repository was too old to perform a lot of the steps.
I wonder who'll be the first to convert a McLaren to International??
inneyeseakay said:
I wonder who'll be the first to convert a McLaren to International??
Click to expand...
Click to collapse
We are on the 7T forum.
That being said, I made the same kind of tool for McLaren, but it only allows to unlock it's bootloader. There's no international firmware for McLaren. Unfortunately, there is no hardware equivalent for the McLaren sold as an international phone (it was easy for the 7T to convert because it's the same hardware, or at least very very close).
maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine
edit----
something is wrong with the conversion...
c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
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.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
SALHERO said:
maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine
edit----
something is wrong with the conversion...
c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
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.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
Click to expand...
Click to collapse
I don't know why you were not able to boot into fastbootd (it says "Failed to boot into userspace fastboot" which means failed to boot into fastbootd).
But it's because of this error that all the warnings "Flashing is not allowed for Critical Partitions" are appearing.
If your fastboot executable is too old, the command "fastboot reboot fastboot", which allows you to boot in fastbootd, will not work. So I suggest you download the latest platform tools zip from Google, so you'll be using the latest adb and latest fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then ensure that in the terminal, the right version of fastboot is used (pay attention to the existing environment variables which might make your terminal use the old fastboot executable in another location).
Then run again the script flash-all.bat.
Please update,
Thanks
Congrats!
Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.
Thank you allowed me to unlock the bootloader on my wifes 7t and convert to global firmware then i relocked the bootloader the global firmware and software just runs so much smoother than the T-Mobile software not sure why.
Hello,
is anybody know can this guide somehow help me to get my OnePlus 7T unlocked? I mean Network unlocked...
Please if somebody can help me with that I would really appreciate it. Thank you!
@floopidze please read the first post.
Shortychance said:
Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.
Click to expand...
Click to collapse
It will work on a simlocked device, but it will not sim unlock the phone.
Please read the first post.

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

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?

Can't unroot to official ROM Oneplus 7T

Hi guys,
Een tijd geleden heb ik mijn toestel geroot en gebruikte ik de LineageOS ROM.
Na enige tijd besloot ik om Derpfest een kans te geven en heb ik daarop een tijdje gewerkt.
Nu zou ik graag het toestel terug origineel zetten maar blijk hierin te falen.
Ik heb al vrij veel pogingen ondernomen waardoor ik eigenlijk genoodzaakt ben om hier dus hulp te zoeken.
Dit is mijn stappenplan:
1. Boot into fastboot mode (device is recognized succesfully)
2. Download official ROM:
10.0.13-EUROPE-OnePlus7TOxygen_14.E.19_OTA_019_all_2009281550_5278fc102a-FASTBOOT
3. Click on 'flash all'
This is my output:
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.460s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25493504 4k blocks and 6385824 inodes
Filesystem UUID: fa624be0-e6ab-11ec-a300-012318ae63e0
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4616 KB) OKAY [ 0.158s]
Writing 'userdata' OKAY [ 0.016s]
Erasing 'metadata' OKAY [ 0.000s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.128s
Sending 'boot_b' (98304 KB) OKAY [ 3.040s]
Writing 'boot_b' OKAY [ 0.418s]
Finished. Total time: 3.654s
Sending 'dtbo' (16384 KB) OKAY [ 0.501s]
Writing 'dtbo' OKAY [ 0.052s]
Finished. Total time: 0.633s
Sending 'modem_b' (165396 KB) OKAY [ 5.073s]
Writing 'modem_b' OKAY [ 0.763s]
Finished. Total time: 8.291s
Sending 'reserve' (250164 KB) OKAY [ 7.702s]
Writing 'reserve' FAILED (remote: '(reserve_b) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.031s]
Writing 'recovery' OKAY [ 0.363s]
Finished. Total time: 3.521s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.026s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_system' OKAY [ 0.000s]
Finished. Total time: 0.032s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Click to expand...
Click to collapse
On my device, the stock recovery is started. I now press English -> Advanced -> Reboot to fastboot
and the cmd script continues (with a lot of errors now)
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.046s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.011s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'bluetooth' (828 KB) OKAY [ 0.032s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.016s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.016s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.005s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'hyp' (480 KB) OKAY [ 0.032s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.016s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'keymaster' (248 KB) OKAY [ 0.016s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.214s]
Writing 'LOGO' OKAY [ 0.063s]
Finished. Total time: 0.309s
Sending 'multiimgoem' (16 KB) OKAY [ 0.016s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'odm' (912 KB) OKAY [ 0.052s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.079s]
Writing 'oem_stanvbk' OKAY [ 0.032s]
Finished. Total time: 0.127s
Sending 'opproduct' (586912 KB) OKAY [ 17.758s]
Writing 'opproduct' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'qupfw' (72 KB) OKAY [ 0.020s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'storsec' (24 KB) OKAY [ 0.016s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'tz' (3092 KB) OKAY [ 0.101s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl' (3120 KB) OKAY [ 0.115s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.015s]
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 [ 24.129s]
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) OKAY [ 24.186s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 24.242s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Press any key to continue . . .
Click to expand...
Click to collapse
The phone is rebooted into recovery and that's about it...
No one?
Msmtool will install unrooted, bootloader locked, stock 11.0.5:
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
HueyT said:
Msmtool will install unrooted, bootloader locked, stock 11.0.5:
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your reply, unfortunately msmtool cant find my phone
Awaces said:
Thanks for your reply, unfortunately msmtool cant find my phone
Click to expand...
Click to collapse
Needs Qualcomm 9008 drivers for Windows 10 and put phone into EDL mode via button presses
HueyT said:
Needs Qualcomm 9008 drivers for Windows 10 and put phone into EDL mode via button presses
Click to expand...
Click to collapse
Lol... I missed the critical step to put the phone into EDL mode.
Thanks a lot mate ! You solved my issue

TWRP FAILED (remote failure)

So, I was trying to install the twrp, but when I do put out the comand for the flash recovery I get this section:
sending 'recovery' (44474 KB)...
OKAY [ 1.537s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 1.585s
I did try to just boot it already and got this:
downloading 'boot.img'...
OKAY [ 1.216s]
booting...
FAILED (remote failure)
finished. total time: 1.400s
Can anyone help?

oneplus 7T phone stuck at fastboot OS 12

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. ¯\_(ツ)_/¯

Categories

Resources