Develop Bugs

FAILED (remote: 'Chunk data size exceeds partition size') when flashing system.img

Hi, guys.
I couldn't install update 10.0.3.0 after restoring boot.img from Magisk.
So, I flash boot.img in fastboot but still cannot.
And then I found out maybe because Substratum modified system.img
Then I tried to flash 10.0.2.0 system.img using this command:
Code:
fastboot flash system_a system_10.0.2.0.img
and this error shown:
Code:
Sending sparse 'system_a' 1/3 (462332 KB) OKAY [ 10.736s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Chunk data size exceeds partition size')
Finished. Total time: 30.924s
I also tried these 2 commands get from this solution:
Code:
fastboot flash -S 256M system_a system_10.0.2.0.img
fastboot flash -S 128M system_a system_10.0.2.0.img
but same error.
Any help is appreciated.
current-slot:
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s

Sorry guys, problem solved.
I don't know what happened, my phone suddenly stuck in bootloop?
no animation just black screen, increase brightness to 100 then drop to 0 then increase to 100 and cycle.
then I boot into fastboot and try flash again
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.012s
D:\platform-tools>fastboot flash boot_a boot_10.0.2.0.img
Sending 'boot_a' (27219 KB) OKAY [ 0.633s]
Writing 'boot_a' OKAY [ 0.339s]
Finished. Total time: 0.996s
D:\platform-tools>fastboot flash system_a system_10.0.2.0.img
Sending sparse 'system_a' 1/4 (522236 KB) OKAY [ 17.728s]
Writing sparse 'system_a' 1/4 OKAY [ 5.516s]
Sending sparse 'system_a' 2/4 (522236 KB) OKAY [ 17.947s]
Writing sparse 'system_a' 2/4 OKAY [ 5.576s]
Sending sparse 'system_a' 3/4 (522236 KB) OKAY [ 17.854s]
Writing sparse 'system_a' 3/4 OKAY [ 5.629s]
Sending sparse 'system_a' 4/4 (447916 KB) OKAY [ 15.042s]
Writing sparse 'system_a' 4/4 OKAY [ 4.804s]
Finished. Total time: 148.451s
D:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
now the system.img split into 522.236 MB instead of 462.332 MB and got 4 parts instead of 3?
wtf is happening!
Anyway, the updated is installed successfully.

Z2 Force dead, just turn on with USB connected, don't charge

Hi, guys!
I just found XDA on internet search and hope you guys help me
I have a Z2Force and it don't turns on unless the USB are connected on charge or PC. When I connect the cable, the charge icon display appears but stays on an infinite loop and does not show the charge percentage.
When I try to turn on the phone (with charge connected), it goes into infinite loop on Motorola logo.
I can get into the fastboot menu pressing power + vol - , but only with USB connected. There on that screen, it says "Power OK".
I tried to flash stock rom using Minimal ADB and fastboot, I got the ROM on "lolinet dot com" (I can't post links, 'cause I'm new user). I downloaded on nash/official/RETBR (my Z2F is from Brasil). I used this commands:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
the installation goes to the end, but after restarting, the phone keeps looping on the logo screen...
I don't know if this information will be helpful, but the bootloader is locked (oem_locked).
I don't have developer knowledge, but I can follow your guidance, just tell me what to do.
I will be happy to pay a beer for those who help me
Please, guys, help me, I don't have another phone
Thank you very much in advance.
Edit: I got this phone from a friend, he tried to use a custom ROM, the phone worked but without Play Store, he tried to restore to stock ROM and got to this situation. So, he gave me the phone, because my Z2Play fell on water and died

Anyone??
Please, can anyone help me? :/

Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.

41rw4lk said:
Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.
Click to expand...
Click to collapse
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/

AgrippaJr said:
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/
Click to expand...
Click to collapse
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?

41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
Yeah, this one...

41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737

AgrippaJr said:
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
Click to expand...
Click to collapse
Not adb/fastboot, the flashall.bat that you're using where did you get that?

41rw4lk said:
Not adb/fastboot, the flashall.bat that you're using where did you get that?
Click to expand...
Click to collapse
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...

AgrippaJr said:
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...
Click to expand...
Click to collapse
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.

41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
OK... I will try here... I'll let u know

Test result, questions
41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?

AgrippaJr said:
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?
Click to expand...
Click to collapse
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.

41rw4lk said:
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.
Click to expand...
Click to collapse
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...

AgrippaJr said:
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...
Click to expand...
Click to collapse
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.

What is your battery voltage when you fastboot getvar all?

Uzephi said:
What is your battery voltage when you fastboot getvar all?
Click to expand...
Click to collapse
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...

41rw4lk said:
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.
Click to expand...
Click to collapse
I follow all the tutorial steps, in two different PC's, windows versions and cables, cmd says 'waiting for device'... It don't detect the phone...
When i do the 'devices' command at adb and fastboot:
C:\Users\Junior\Desktop\adb and fastboot>adb devices
List of devices attached
C:\Users\Junior\Desktop\adb and fastboot>fastboot devices
0042953957 fastboot
Did i miss something?

AgrippaJr said:
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...
Click to expand...
Click to collapse
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.

Uzephi said:
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.
Click to expand...
Click to collapse
I see... And where do you think the defect is? Maybe the battery or something else? What can I do about it? :|
maybe I should open and measure the battery voltage with a multimeter... What do you think?
If you have another solution, let me know

Can't update 1/2020 flash, phone stuck in bootloader please help!

ETA: YAY, I'M BACK UP AND RUNNING AFTER USING STOCK RECOVERY TO SIDELOAD THE FULL OTA. THANKS EVERYONE, YOU'VE MADE MY DAY!!!
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
...
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with bothe the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
Seems odd. Did you try a different cable or USB port? Do you have the latest ADB / SDK on your PC?

swieder711 said:
Seems odd. Did you try a different cable or USB port? Do you have the latest ADB / SDK on your PC?
Click to expand...
Click to collapse
Thanks for the quick reply, those are all good ideas. Before asking for help I tried 2 different USB ports and 2 different cables. I fully updated my Android Studio before starting this, which includes the latest SDK, platform tools, etc., I was current with everything before starting.I have no idea how to fix this, I haven't hears a lot of people having issues flashing the january update so I assume its something on my end. I DO use Magisk and Kirisakura custom kernel, but I dont know how to disable either one via fastboot, which is all I have available.

lukefgoogler said:
Thanks for the quick reply, those are all good ideas. Before asking for help I tried 2 different USB ports and 2 different cables. I fully updated my Android Studio before starting this, which includes the latest SDK, platform tools, etc., I was current with everything before starting.I have no idea how to fix this, I haven't hears a lot of people having issues flashing the january update so I assume its something on my end. I DO use Magisk and Kirisakura custom kernel, but I dont know how to disable either one via fastboot, which is all I have available.
Click to expand...
Click to collapse
Is there a way to disable Magisk via Fastboot? I was able install the December update with just -w removed. I had Magisk+modules enabled along with Kiris kernel installed. I haven't installed the Jan update yet because I am waiting for the new kernel.
Other than disabling Magisk, you might have to try installing the update with the -w option. Hopefully you have some good backups offline!

swieder711 said:
Is there a way to disable Magisk via Fastboot? I was able install the December update with just -w removed. I had Magisk+modules enabled along with Kiris kernel installed. I haven't installed the Jan update yet because I am waiting for the new kernel.
Other than disabling Magisk, you might have to try installing the update with the -w option. Hopefully you have some good backups offline!
Click to expand...
Click to collapse
I tried to do a factory reset via recovery, other than nuke my personal data it didn't seem to do much, still only able to boot to bootloader with either a or b partition active. Starting to get worried...

lukefgoogler said:
I tried to do a factory reset via recovery, other than nuke my personal data it didn't seem to do much, still only able to boot to bootloader with either a or b partition active. Starting to get worried...
Click to expand...
Click to collapse
Have you tried sideloading the OTA with the stock recovery?

To not lose data you need to flash the "Full Ota" image and not the factory one... Then you need to do nothing just flash it...
Also from your console output it seems that the image you downloaded is corrupted as it's missing files...

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
The failure at product started during Q beta. To this day, I have seen nobody with an exact reason for it, but there is a fairly easy solution. When the error happens, don't unplug anything or even turn off command prompt. You are still in fastbootd. Press a key on the computer to get back to a command line. Go to recovery on the phone, and start an OTA sideload. If you don't already have the OTA downloaded, you will need to do that. Going from fastbootd to recovery will get you the ability to run adb sideload XXX from command prompt. It will run, complete, change slots and you will not lose data. I have had to do it a few times with my wife's P3. This month before running the flash-all (without -w), I flashed the Dec stock boot.img to both slots and then while still in BL ran the flash-all. Guess what? It took just fine with no product failure.

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
Make sure the USB is not plugged into a charging port

I owe a big "Thank You!" to EVERYONE who replied, sideloading the full OTA using the stock recovery worked like a charm! (Wish I didn't wipe data when I was casting about for a fix...)
Thanks all, you rock.

[OPN105G][OOS 86AA/89BA] 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 modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord and OP8T here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N10.
Albeit it has not been tested, you should hopefully be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
Please note that crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. For reference EU devices project ID is 20889 while international devices project ID is 20886. This has been found with @Elidone unit, which hasn't been able to crossflash EU software on his international device (see second screenshot attached). I therefore assume that same happens when trying to flash international software on EU units.
BE86AA tools (international firmware):
ANDROID 10:
OOS 10.5.7
OOS 10.5.8
OOS 10.5.9
OOS 10.5.11
Mirror for first and last MSMs: https://onepluscommunityserver.com/
BE89BA tools (european firmware):
ANDROID 10:
OOS 10.5.7
OOS 10.5.8
OOS 10.5.9
OOS 10.5.10
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@Elidone for testing 10.5.7 AA version on his device and for the screenshots
OnePlus for the device and OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Reserved

Good!
I planned to get US version once it's released

Hello kind sir. I just tested out the wonderful software you provide, and may I say, it works flawlessly!
Have a great Christmas!

I really wish this was available before I spent well over two weeks waiting for their support to use this exact tool on my bricked N10. At least I have their tools now. Thanks for the release, and hopefully no one else has to go through the support for this kind of stuff again.

@Some_Random_Username
Hi. Do you have a new version 10.5.9.BE86AA?

Alexey71 said:
@Some_Random_Username
Hi. Do you have a new version 10.5.9.BE86AA?
Click to expand...
Click to collapse
Hi, no, most likely because 10.5.9 got released too recently (today is first time I'm hearing of that build).
I however have 10.5.8 which I aim to release in next days.

@Some_Random_Username
Tell me how to unpack billie8_14_O.01_201121.ops?
I need stock xxx.img

Alexey71 said:
@Some_Random_Username
Tell me how to unpack billie8_14_O.01_201121.ops?
I need stock xxx.img
Click to expand...
Click to collapse
You can't, however you can find OOS 10.5.7 BE86AA stock boot.img at https://forum.xda-developers.com/t/root-n10-using-magisk.4197369/ (in the zip file boot_10.5.7.BE86AA.zip )

Added OOS 10.5.8 MSMs
For those unfamilliar, you don't need latest version to unbrick your device, it's just a convenience to restore to a newer build.

Mod edit - translated by https://www.deepl.com/translator:
Which region does the version of the appliance belong to? Firmware 10.5.9. BE86AA. Model BE2029. Global or Eu? And where can i download full firmware images for this phone model?
*******************************
К какому региону относится версию аппарата? Прошивка 10.5.9. BE86AA. Модель BE2029. Глобал или Eu? И где можно скачать полные образы прошивки для этой модели телефона?

serg7500 said:
Mod edit - translated by https://www.deepl.com/translator:
Which region does the version of the appliance belong to? Firmware 10.5.9. BE86AA. Model BE2029. Global or Eu? And where can i download full firmware images for this phone model?
*******************************
К какому региону относится версию аппарата? Прошивка 10.5.9. BE86AA. Модель BE2029. Глобал или Eu? И где можно скачать полные образы прошивки для этой модели телефона?
Click to expand...
Click to collapse
Please use the English language! [Пожалуйста, используйте английский язык!]
XDA Forum Rules (excerpt):
...
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
...
Click to expand...
Click to collapse

serg7500 said:
Mod edit - translated by https://www.deepl.com/translator:
Which region does the version of the appliance belong to? Firmware 10.5.9. BE86AA. Model BE2029. Global or Eu? And where can i download full firmware images for this phone model?
*******************************
К какому региону относится версию аппарата? Прошивка 10.5.9. BE86AA. Модель BE2029. Глобал или Eu? И где можно скачать полные образы прошивки для этой модели телефона?
Click to expand...
Click to collapse
BE86AA software is global software.
Unfortunately OnePlus hasn't released full zip for it on its support website yet.

Some_Random_Username said:
BE86AA software is global software.
Unfortunately OnePlus hasn't released full zip for it on its support website yet.
Click to expand...
Click to collapse
Mod edit - translated by https://www.deepl.com/translator and quotation repaired:
Would you kindly provide a link to this website?
********************************
А будьде добры дать ссылку на этот веб-сайт

serg7500 said:
[QUOTE = "Some_Random_Username, сообщение: 84311381, участник: 8234677"]
Программное обеспечение BE86AA - это глобальное программное обеспечение.
К сожалению, OnePlus еще не выпустил полный zip для него на своем веб-сайте поддержки.
[/ QUOTE]
А будьде добры дать ссылку на этот веб-сайт
Click to expand...
Click to collapse
Please, english only
OnePlus Support Softwareupgrade - OnePlus (United States)
support softwareupgrade
www.oneplus.com

Thanks, it worked like a charm.

Some_Random_Username said:
BE86AA software is global software.
Unfortunately OnePlus hasn't released full zip for it on its support website yet.
Click to expand...
Click to collapse
It may be worth asking support about it. They seemed to release the UK zip the day after I asked about it to them.

Thanks for posting this. You saved my a$$.
Just got a BE86AA 2 days ago and I rooted it per the instructions posted here.
It worked perfectly rooted for over 24 hours, then refused to boot, just hung at the message about the bootloader being unlocked.
I tried reflashing the patched boot image--no help, then tried wiping anything I could from recovery--no help.
I then flashed the unpatched boot image--still no luck, then I re-locked the bootloader--still not booting.
At that point I downloaded the unbrick tool and I was able to restore to stock successfully !!!
Thank you so much for posting this here !!
FYI: Just before the failure to boot I installed a couple of Magisk apps, the first Magisk apps that I installed.
It's nice to know that I have a solution to restore my phone no matter what happens to it.

Any way to do it in Linux ? i mean script to do all, i know about
extracting zip to fastboot all like
Code:
[email protected] ~/Downloads/extract_android_ota_payload-master $ python extract_android_ota_payload.py OnePlusN10Oxygen_14.E.09_OTA_009_all_2101021731_9c32820c43e443f1.zip 1/
Extracting 'payload.bin' from OTA file...
Extracting 'abl.img'
Extracting 'boot.img'
Extracting 'dtbo.img'
Extracting 'odm.img'
Extracting 'product.img'
Extracting 'recovery.img'
Extracting 'system.img'
Extracting 'vbmeta.img'
Extracting 'vbmeta_system.img'
Extracting 'vendor.img'
Extracting 'aop.img'
Extracting 'bluetooth.img'
Extracting 'devcfg.img'
Extracting 'dsp.img'
Extracting 'featenabler.img'
Extracting 'hyp.img'
Extracting 'imagefv.img'
Extracting 'keymaster.img'
Extracting 'modem.img'
Extracting 'qupfw.img'
Extracting 'storsec.img'
Extracting 'tz.img'
Extracting 'uefisecapp.img'
Extracting 'xbl_config.img'
Extracting 'xbl.img'
Extracting 'oem_stanvbk.img'
(n):cry:[email protected] ~/Downloads/extract_android_ota_payload-master $ cd 1
abl.img dtbo.img odm.img storsec.img vendor.img
aop.img featenabler.img oem_stanvbk.img system.img xbl_config.img
bluetooth.img hyp.img payload.bin tz.img xbl.img
boot.img imagefv.img product.img uefisecapp.img
devcfg.img keymaster.img qupfw.img vbmeta.img
dsp.img modem.img recovery.img vbmeta_system.img
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
< waiting for any device >
Sending 'boot_b' (98304 KB) OKAY [ 2.314s]
Writing 'boot_b' OKAY [ 1.953s]
Finished. Total time: 4.279s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (782003 KB) OKAY [ 18.506s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.822s]
Finished. Total time: 0.828s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot -w
Erasing 'userdata' OKAY [ 0.801s]
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.318s]
Writing 'boot_b' OKAY [ 1.885s]
Finished. Total time: 4.217s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.195s]
Writing 'dtbo' OKAY [ 0.188s]
Finished. Total time: 0.391s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash modem modem.img
Sending 'modem_b' (152332 KB) OKAY [ 3.607s]
Writing 'modem_b' OKAY [ 2.974s]
Finished. Total time: 6.590s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 2.412s]
Writing 'recovery' OKAY [ 2.023s]
Finished. Total time: 4.455s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.477s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash abl abl.img
Sending 'abl_b' (1996 KB) OKAY [ 0.057s]
Writing 'abl_b' OKAY [ 0.028s]
Finished. Total time: 0.093s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash aop aop.img
Sending 'aop_b' (176 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.020s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash bluetooth bluetooth.img
Sending 'bluetooth_b' (220 KB) OKAY [ 0.007s]
Writing 'bluetooth_b' OKAY [ 0.008s]
Finished. Total time: 0.021s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash devcfg devcfg.img
Sending 'devcfg_b' (44 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.005s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dsp dsp.img
Sending 'dsp_b' (65536 KB) OKAY [ 1.618s]
Writing 'dsp_b' OKAY [ 0.531s]
Finished. Total time: 2.153s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash featenabler featenabler.img
Sending 'featenabler_b' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_b' OKAY [ 0.006s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash hyp hyp.img
Sending 'hyp_b' (396 KB) OKAY [ 0.011s]
Writing 'hyp_b' OKAY [ 0.010s]
Finished. Total time: 0.025s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash imagefv imagefv.img
Sending 'imagefv_b' (524 KB) OKAY [ 0.017s]
Writing 'imagefv_b' OKAY [ 0.012s]
Finished. Total time: 0.036s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash keymaster keymaster.img
Sending 'keymaster_b' (232 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.008s]
Finished. Total time: 0.022s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash logo logo.img
fastboot: error: cannot load 'logo.img': No such file or directory
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash oem_stanvbk oem_stanvbk.img
Sending 'oem_stanvbk' (2920 KB) OKAY [ 0.078s]
Writing 'oem_stanvbk' OKAY [ 0.038s]
Finished. Total time: 0.123s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash odm odm.img
Resizing 'odm_b' OKAY [ 0.004s]
Sending 'odm_b' (968 KB) OKAY [ 0.027s]
Writing 'odm_b' OKAY [ 0.293s]
Finished. Total time: 0.331s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash qupfw qupfw.img
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.005s]
Finished. Total time: 0.012s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash storsec storsec.img
Sending 'storsec_b' (20 KB) OKAY [ 0.001s]
Writing 'storsec_b' OKAY [ 0.005s]
Finished. Total time: 0.013s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash tz tz.img
Sending 'tz_b' (2960 KB) OKAY [ 0.076s]
Writing 'tz_b' OKAY [ 0.038s]
Finished. Total time: 0.120s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.018s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl xbl.img
Sending 'xbl_b' (3296 KB) OKAY [ 0.083s]
Writing 'xbl_b' OKAY [ 1.794s]
Finished. Total time: 1.884s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl_config xbl_config.img
Sending 'xbl_config_b' (96 KB) OKAY [ 0.003s]
Writing 'xbl_config_b' OKAY [ 0.029s]
Finished. Total time: 0.040s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/4 (523001 KB) OKAY [ 12.780s]
Writing 'system_b' OKAY [ 3.391s]
Sending sparse 'system_b' 2/4 (520279 KB) OKAY [ 12.756s]
Writing 'system_b' OKAY [ 3.428s]
Sending sparse 'system_b' 3/4 (523321 KB) OKAY [ 12.786s]
Writing 'system_b' OKAY [ 3.450s]
Sending sparse 'system_b' 4/4 (450188 KB) OKAY [ 11.003s]
Writing 'system_b' OKAY [ 3.045s]
Finished. Total time: 62.944s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Resizing 'vendor_b' OKAY [ 0.003s]
Sending sparse 'vendor_b' 1/3 (523167 KB) OKAY [ 12.819s]
Writing 'vendor_b' OKAY [ 3.502s]
Sending sparse 'vendor_b' 2/3 (510001 KB) OKAY [ 12.478s]
Writing 'vendor_b' OKAY [ 3.398s]
Sending sparse 'vendor_b' 3/3 (291316 KB) OKAY [ 7.133s]
Writing 'vendor_b' OKAY [ 2.147s]
Finished. Total time: 41.657s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash product product.img
Invalid sparse file format at header magic
Resizing 'product_b' OKAY [ 0.003s]
Sending sparse 'product_b' 1/4 (522958 KB) OKAY [ 12.807s]
Writing 'product_b' OKAY [ 3.412s]
Sending sparse 'product_b' 2/4 (523010 KB) OKAY [ 12.818s]
Writing 'product_b' OKAY [ 3.418s]
Sending sparse 'product_b' 3/4 (520218 KB) OKAY [ 12.759s]
Writing 'product_b' OKAY [ 3.440s]
Sending sparse 'product_b' 4/4 (235736 KB) OKAY [ 5.795s]
Writing 'product_b' OKAY [ 1.825s]
Finished. Total time: 56.543s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.051s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $

powergo said:
Any way to do it in Linux ? i mean script to do all, i know about
extracting zip to fastboot all like
Code:
[email protected] ~/Downloads/extract_android_ota_payload-master $ python extract_android_ota_payload.py OnePlusN10Oxygen_14.E.09_OTA_009_all_2101021731_9c32820c43e443f1.zip 1/
Extracting 'payload.bin' from OTA file...
Extracting 'abl.img'
Extracting 'boot.img'
Extracting 'dtbo.img'
Extracting 'odm.img'
Extracting 'product.img'
Extracting 'recovery.img'
Extracting 'system.img'
Extracting 'vbmeta.img'
Extracting 'vbmeta_system.img'
Extracting 'vendor.img'
Extracting 'aop.img'
Extracting 'bluetooth.img'
Extracting 'devcfg.img'
Extracting 'dsp.img'
Extracting 'featenabler.img'
Extracting 'hyp.img'
Extracting 'imagefv.img'
Extracting 'keymaster.img'
Extracting 'modem.img'
Extracting 'qupfw.img'
Extracting 'storsec.img'
Extracting 'tz.img'
Extracting 'uefisecapp.img'
Extracting 'xbl_config.img'
Extracting 'xbl.img'
Extracting 'oem_stanvbk.img'
(n):cry:[email protected] ~/Downloads/extract_android_ota_payload-master $ cd 1
abl.img dtbo.img odm.img storsec.img vendor.img
aop.img featenabler.img oem_stanvbk.img system.img xbl_config.img
bluetooth.img hyp.img payload.bin tz.img xbl.img
boot.img imagefv.img product.img uefisecapp.img
devcfg.img keymaster.img qupfw.img vbmeta.img
dsp.img modem.img recovery.img vbmeta_system.img
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
< waiting for any device >
Sending 'boot_b' (98304 KB) OKAY [ 2.314s]
Writing 'boot_b' OKAY [ 1.953s]
Finished. Total time: 4.279s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (782003 KB) OKAY [ 18.506s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.822s]
Finished. Total time: 0.828s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot -w
Erasing 'userdata' OKAY [ 0.801s]
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.318s]
Writing 'boot_b' OKAY [ 1.885s]
Finished. Total time: 4.217s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.195s]
Writing 'dtbo' OKAY [ 0.188s]
Finished. Total time: 0.391s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash modem modem.img
Sending 'modem_b' (152332 KB) OKAY [ 3.607s]
Writing 'modem_b' OKAY [ 2.974s]
Finished. Total time: 6.590s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 2.412s]
Writing 'recovery' OKAY [ 2.023s]
Finished. Total time: 4.455s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.477s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash abl abl.img
Sending 'abl_b' (1996 KB) OKAY [ 0.057s]
Writing 'abl_b' OKAY [ 0.028s]
Finished. Total time: 0.093s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash aop aop.img
Sending 'aop_b' (176 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.020s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash bluetooth bluetooth.img
Sending 'bluetooth_b' (220 KB) OKAY [ 0.007s]
Writing 'bluetooth_b' OKAY [ 0.008s]
Finished. Total time: 0.021s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash devcfg devcfg.img
Sending 'devcfg_b' (44 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.005s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash dsp dsp.img
Sending 'dsp_b' (65536 KB) OKAY [ 1.618s]
Writing 'dsp_b' OKAY [ 0.531s]
Finished. Total time: 2.153s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash featenabler featenabler.img
Sending 'featenabler_b' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_b' OKAY [ 0.006s]
Finished. Total time: 0.014s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash hyp hyp.img
Sending 'hyp_b' (396 KB) OKAY [ 0.011s]
Writing 'hyp_b' OKAY [ 0.010s]
Finished. Total time: 0.025s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash imagefv imagefv.img
Sending 'imagefv_b' (524 KB) OKAY [ 0.017s]
Writing 'imagefv_b' OKAY [ 0.012s]
Finished. Total time: 0.036s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash keymaster keymaster.img
Sending 'keymaster_b' (232 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.008s]
Finished. Total time: 0.022s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash logo logo.img
fastboot: error: cannot load 'logo.img': No such file or directory
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash oem_stanvbk oem_stanvbk.img
Sending 'oem_stanvbk' (2920 KB) OKAY [ 0.078s]
Writing 'oem_stanvbk' OKAY [ 0.038s]
Finished. Total time: 0.123s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash odm odm.img
Resizing 'odm_b' OKAY [ 0.004s]
Sending 'odm_b' (968 KB) OKAY [ 0.027s]
Writing 'odm_b' OKAY [ 0.293s]
Finished. Total time: 0.331s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash qupfw qupfw.img
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.005s]
Finished. Total time: 0.012s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash storsec storsec.img
Sending 'storsec_b' (20 KB) OKAY [ 0.001s]
Writing 'storsec_b' OKAY [ 0.005s]
Finished. Total time: 0.013s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash tz tz.img
Sending 'tz_b' (2960 KB) OKAY [ 0.076s]
Writing 'tz_b' OKAY [ 0.038s]
Finished. Total time: 0.120s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash uefisecapp uefisecapp.img
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.018s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl xbl.img
Sending 'xbl_b' (3296 KB) OKAY [ 0.083s]
Writing 'xbl_b' OKAY [ 1.794s]
Finished. Total time: 1.884s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash xbl_config xbl_config.img
Sending 'xbl_config_b' (96 KB) OKAY [ 0.003s]
Writing 'xbl_config_b' OKAY [ 0.029s]
Finished. Total time: 0.040s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash system system.img
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/4 (523001 KB) OKAY [ 12.780s]
Writing 'system_b' OKAY [ 3.391s]
Sending sparse 'system_b' 2/4 (520279 KB) OKAY [ 12.756s]
Writing 'system_b' OKAY [ 3.428s]
Sending sparse 'system_b' 3/4 (523321 KB) OKAY [ 12.786s]
Writing 'system_b' OKAY [ 3.450s]
Sending sparse 'system_b' 4/4 (450188 KB) OKAY [ 11.003s]
Writing 'system_b' OKAY [ 3.045s]
Finished. Total time: 62.944s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Resizing 'vendor_b' OKAY [ 0.003s]
Sending sparse 'vendor_b' 1/3 (523167 KB) OKAY [ 12.819s]
Writing 'vendor_b' OKAY [ 3.502s]
Sending sparse 'vendor_b' 2/3 (510001 KB) OKAY [ 12.478s]
Writing 'vendor_b' OKAY [ 3.398s]
Sending sparse 'vendor_b' 3/3 (291316 KB) OKAY [ 7.133s]
Writing 'vendor_b' OKAY [ 2.147s]
Finished. Total time: 41.657s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot flash product product.img
Invalid sparse file format at header magic
Resizing 'product_b' OKAY [ 0.003s]
Sending sparse 'product_b' 1/4 (522958 KB) OKAY [ 12.807s]
Writing 'product_b' OKAY [ 3.412s]
Sending sparse 'product_b' 2/4 (523010 KB) OKAY [ 12.818s]
Writing 'product_b' OKAY [ 3.418s]
Sending sparse 'product_b' 3/4 (520218 KB) OKAY [ 12.759s]
Writing 'product_b' OKAY [ 3.440s]
Sending sparse 'product_b' 4/4 (235736 KB) OKAY [ 5.795s]
Writing 'product_b' OKAY [ 1.825s]
Finished. Total time: 56.543s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.051s
[email protected] ~/Downloads/extract_android_ota_payload-master/1 $
Click to expand...
Click to collapse
No, as said in OP this tool is Windows only.
It is not a GUI for fastboot, it uses Qualcomm EDL mode to flash your device like at factory.

Question Xiaomi pad 5 fastboot error

Hello!
I'm writting this post because I have a problem and I'm going nuts. The only thing I want is to flash fastboot global version (I have the EU one). I flashed it and this is what I found:
product: nabu
erasing 'boot_ab'...
(bootloader) Partition boot_a erase successfully
(bootloader) Partition boot_b erase successfully
OKAY [ 0.017s]
finished. total time: 0.017s
target reported max download size of 805306368 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.010s]
writing 'crclist'...
OKAY [ 0.007s]
finished. total time: 0.018s
target reported max download size of 805306368 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.009s]
writing 'sparsecrclist'...
OKAY [ 0.003s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'xbl_ab' (4054 KB)...
OKAY [ 0.164s]
writing 'xbl_ab'...
(bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.037s]
finished. total time: 0.201s
target reported max download size of 805306368 bytes
sending 'xbl_config_ab' (120 KB)...
OKAY [ 0.016s]
writing 'xbl_config_ab'...
(bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.028s
target reported max download size of 805306368 bytes
sending 'abl_ab' (204 KB)...
OKAY [ 0.013s]
writing 'abl_ab'...
(bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.008s]
finished. total time: 0.021s
target reported max download size of 805306368 bytes
sending 'tz_ab' (3115 KB)...
OKAY [ 0.120s]
writing 'tz_ab'...
(bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.021s]
finished. total time: 0.141s
target reported max download size of 805306368 bytes
sending 'hyp_ab' (476 KB)...
OKAY [ 0.025s]
writing 'hyp_ab'...
(bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.037s
target reported max download size of 805306368 bytes
sending 'devcfg_ab' (53 KB)...
OKAY [ 0.015s]
writing 'devcfg_ab'...
(bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.010s]
finished. total time: 0.025s
target reported max download size of 805306368 bytes
sending 'storsec' (20 KB)...
OKAY [ 0.008s]
writing 'storsec'...
OKAY [ 0.005s]
finished. total time: 0.013s
target reported max download size of 805306368 bytes
sending 'bluetooth_ab' (1020 KB)...
OKAY [ 0.041s]
writing 'bluetooth_ab'...
(bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.013s]
finished. total time: 0.055s
target reported max download size of 805306368 bytes
sending 'cmnlib_ab' (385 KB)...
OKAY [ 0.024s]
writing 'cmnlib_ab'...
(bootloader) Partition cmnlib_a flashed successfully
(bootloader) Partition cmnlib_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.036s
target reported max download size of 805306368 bytes
sending 'cmnlib64_ab' (503 KB)...
OKAY [ 0.025s]
writing 'cmnlib64_ab'...
(bootloader) Partition cmnlib64_a flashed successfully
(bootloader) Partition cmnlib64_b flashed successfully
OKAY [ 0.011s]
finished. total time: 0.036s
target reported max download size of 805306368 bytes
sending 'modem_ab' (108236 KB)...
OKAY [ 3.986s]
writing 'modem_ab'...
(bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.437s]
finished. total time: 4.423s
target reported max download size of 805306368 bytes
sending 'dsp_ab' (65536 KB)...
OKAY [ 2.193s]
writing 'dsp_ab'...
(bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.267s]
finished. total time: 2.460s
erasing 'metadata'...
FAILED (remote: Erase of metadata is not allowed in merging state)
finished. total time: 0.003s
Erase metadata error
I've changed the USB cable, the USB port, tryed a windows and linux pc, erased data with xiaomi's recovery... And no idea what else to do. The bootloader is unlocked. Thanks in advance.

Well, it seems I've hit the nail on the head. I have tried to flash by fasboot with linux and with windows, change the cable and ports, with different miflash... and nothing.
I found this link (https://source.android.com/devices/t...l_ab/implement) to know what happens with the fastboot protocols because of the "merging state" problem, so I tried the following command to find out what status the tablet was in: fastboot getvar snapshot-update-status. It said it was in "merging" As a last resort I went to the miui updater and downloaded the rom from there again and updated from it. It was updated and I entered the same command again for fastboot: fastboot getvar snapshot-update-status. It said it was set to "none". From there I flashed the rom by fastboot running flash_all.bat and I have the global rom.
For those who, having the same problem as me, do not boot the tablet and go back to fastboot automatically, take the boot.img of the fastboot rom from the area that had the rom (in my case it was the European one) and open the cmd and put the following command: fastboot flash boot boot.img. Reboot and it should be back to normal. All this should work as long as you have the same error as me and the data and metadata partitions have not been deleted. I hope that it would be useful to someone.