Develop Bugs

Re-lock bootloader moto G5 plus Brazilian variant

With the help of @Nirbhay2 I managed to block my bootloader, however what I wanted to share here is that to block the bootloader of the Brazilian variant it is necessary the last ROM with january security patch POTTER_NPNS25.137-92-4. Here you will find the guide to block your Brazilian device.
Have minimal ADB
Have Motorola drivers installed on your PC
Have the january patch ROM stock: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Extract the ROM to any folder and paste the minimal ADB along with the extracted ROM.
Open a command prompt in the folder and with the device in fastboot mode make a flash of the entire ROM stock on your device, to facilitate copying all the commands at once and paste at the command prompt and it will install automatic to your ROM , then do the same with the commands to re-block the bootloader and at the end of this process your device will be started with bootloader locked.
Commands to re-lock bootloader, do this after the full ROM flash
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
Command link for flash ROM stock
https://pastebin.com/ZWTaWuyr
We thank @Nirbhay2 for this great guide.

I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?

pss34 said:
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
Click to expand...
Click to collapse
friend, you need to use this ROM that I made available on the link, if you have a moto G5 plus brazilian you can get the lock, but use this link ROM.
Enviado de meu XT1683 usando Tapatalk

I tried the same thing.
I had TWRP and SuperSu on my phone a few days back. But weirdly, I lost network connectivity and after a botched attempt at installing V4A, the audio died as well. Even the camera and the flash had stopped working. More weirdly, the Root Checker app I had now showed me that root access was not properly installed.
SInce my phone was on the November patch (25-137-92), I found the stock ROM of it online and flashed it with the Moto G5 Plus ToolKit.
Now all the issues I've had are fixed. Everything works perfectly. TWRP has been removed along with SuperSu.
But the bootloader still shows me that software status is modified. The warning on boot-up which tells that the device has been unlocked is still there.
I don't know if it's related but I've got WiFi speed issues now, apps won't download quickly or is it my damn internet?
The bootloader IS locked, though. That I can say confidently because the bootloader unlock option in developer options is now not selected.
Moto G(5) Plus XT1686 4/32 GB Indian Version

Problem flashing gpt.bin with fastboot

Hello, just tried to "downgrade" my phone back to stock firmware after using some custom ROM's after some time. Started following various guides online, but I seem to fail at this bit when flashing the stock firmware
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.073s
Click to expand...
Click to collapse
Any tips or help? Currently my phone just bootloops in fastboot, and after quickly flashing TWRP to check the phone, my system and data partitions seem to be messed up, they are unable to be mounted in TWRP.

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

Moto z2 force Flash Stock Wifi Issues x1789-04 tmobile

Notice there is a huge issue with the modem in another post https://forum.xda-developers.com/z2-force/help/0-imei-pie-xt-1789-03-sprint-t3957851 please stay tune
I am having an issue with Wifi, I attempted to update lineage os 17.1 did process to clean flash. After did all the process provided with the guide of lineage os official wiki of my moto Z2 when it booted it got stuck on the loop lineage logo for over 15 minutes than usual with it configures. I decided to flash it back to stock, did a script for it of course(using an example of rcmaehl here XDA) due to long periods test fail I was able to boot it in stock oreo, but when I got to set it up, it does not show any wifi and not even data of carrier. went to the bootloader again to notice that broadband is unknown(not found). long story short I have a half soft brick phone. Any idea and suggestion.
The script I was able to make flash to stock oreo:
Code:
@echo off
adb reboot bootloader
fastboot --set-active=a
ECHO Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a 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_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to rebooting to flash to B.
pause
adb reboot bootloader
pause
adb --set-active=b
echo Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a 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_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to reboot.
pause
fastboot reboot

Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.

41rw4lk said:
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
Click to expand...
Click to collapse
I attempted as avised with script convertor of RootJunky. First attempt running the script
Code:
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.000s]
Finished. Total time: 0.000s
(bootloader) is-logical:partition: not found
Sending 'partition' (206 KB) OKAY [ 0.016s]
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.185s]
Finished. Total time: 0.216s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.331s]
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.169s]
Finished. Total time: 0.501s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97431 KB) ^CTerminate batch job (Y/N)? n
Sending 'fsg' (5596 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.135s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.594s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB) OKAY [ 0.085s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23357 KB) OKAY [ 0.721s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB) OKAY [ 16.038s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.564s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519125 KB) OKAY [ 16.524s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523779 KB) OKAY [ 16.152s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516309 KB) OKAY [ 16.016s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 13.061s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 16.010s]
Writing 'system_b' OKAY [ 2.907s]
Finished. Total time: 25.177s
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.615s]
Writing 'system_b' OKAY [ 1.648s]
Finished. Total time: 14.835s
(bootloader) is-logical:oem__a: not found
Sending 'oem__a' (175682 KB) OKAY [ 5.476s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'modemst2' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'carrier' OKAY [ 0.001s]
Finished. Total time: 0.004s
Erasing 'cache' OKAY [ 0.000s]
Finished. Total time: 0.004s
Erasing 'userdata' OKAY [ 0.075s]
Finished. Total time: 0.082s
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.006s
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5596 KB) OKAY [ 0.173s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.137s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.001s]
Finished. Total time: 0.004s
I notice the error, then proceeded to fix which it should be flash. all it flashes well, but went attempt to reboot to see if system boots up and go back to bootloader .
I'm aware that my scripting is the worst:laugh:, but funny part it got the job done to able to see the system up and running of course without data or wifi connection. :silly: I do appreciate the assistance and Hopefully keep having the assist with suggestions or guides of course. thankfully I have back up the phone(Not Moto z2) but really wish to go back this phone to able to use it as my main again...

If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.

it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?

insanegrim said:
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
Click to expand...
Click to collapse
Go back to fastboot and flash the modem only.
fastboot flash modem (drag and drop the NON-HLOS.bin from your firmware here)
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If that doesn't work it may be possible that your persist partition is full and not letting the modem initialize. You'll need root for this.
adb shell
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
exit
exit
adb reboot

41rw4lk said:
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
Click to expand...
Click to collapse
This soft bricked and now it bootloops my xt1789-04

MOTO G8 ENTERING THE FASTBOOT SCREEN AND DOES NOT START

Hello friends, how are you?
I'm Jeferson and I'm sorry if I'm in the wrong place and (my English).
I have a Moto G8 XT2045-1 it is going straight to the fastboot screen after an android error.
I tried to pass the software on it through "RESCUE" it completes successfully but the device appears the motorola logo and restarts (this process happens 4 times) after that it enters a FAIL BOOT screen.
I tried to use some ADB commands but I don't have much knowledge about these commands, I'll leave the commands I used and their results, in case anyone has gone through this problem I appreciate any help.
Thanks.
Cod.
fastboot oem fb_mode_set
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Result.
fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.004s
fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
fastboot flash partition gpt.bin
target reported max download size of 805263360 bytes
sending 'partition' (37 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.383s]
finished. total time: 0.389s
fastboot flash bootloader bootloader.img
target reported max download size of 805263360 bytes
sending 'bootloader' (14204 KB)...
OKAY [ 0.343s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'uefi_sec.mbn' to 'uefisecapp'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'qupfw.elf' to 'qupfw'
(bootloader) - flashing 'xbl_config.elf' to 'xbl_config'
(bootloader) - flashing 'xbl.elf' to 'xbl'
OKAY [ 0.349s]
finished. total time: 0.696s
fastboot flash logo logo.bin
target reported max download size of 805263360 bytes
sending 'logo' (2667 KB)...
OKAY [ 0.063s]
writing 'logo'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.203s
fastboot flash boot boot.img
target reported max download size of 805263360 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.499s]
writing 'boot'...
OKAY [ 0.915s]
finished. total time: 2.421s
fastboot flash recovery recovery.img
target reported max download size of 805263360 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.472s]
writing 'recovery'...
OKAY [ 1.087s]
finished. total time: 2.562s
fastboot flash dsp adspso.bin
error: cannot load 'adspso.bin'
fastboot flash oem oem.img
error: cannot load 'oem.img'
fastboot flash system system.img_sparsechunk.0
error: cannot load 'system.img_sparsechunk.0'
fastboot flash system system.img_sparsechunk.1
error: cannot load 'system.img_sparsechunk.1'
fastboot flash system system.img_sparsechunk.2
error: cannot load 'system.img_sparsechunk.2'
fastboot flash system system.img_sparsechunk.3
error: cannot load 'system.img_sparsechunk.3'
fastboot flash system system.img_sparsechunk.4
error: cannot load 'system.img_sparsechunk.4'
fastboot flash system system.img_sparsechunk.5
error: cannot load 'system.img_sparsechunk.5'
fastboot flash system system.img_sparsechunk.6
error: cannot load 'system.img_sparsechunk.6'
fastboot flash system system.img_sparsechunk.7
error: cannot load 'system.img_sparsechunk.7'
fastboot flash system system.img_sparsechunk.8
error: cannot load 'system.img_sparsechunk.8'
fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9'
fastboot flash system system.img_sparsechunk.10
error: cannot load 'system.img_sparsechunk.10'
fastboot flash system system.img_sparsechunk.11
error: cannot load 'system.img_sparsechunk.11'
fastboot flash system system.img_sparsechunk.12
error: cannot load 'system.img_sparsechunk.12'
fastboot flash system system.img_sparsechunk.13
error: cannot load 'system.img_sparsechunk.13'
fastboot flash system system.img_sparsechunk.14
error: cannot load 'system.img_sparsechunk.14'
fastboot flash modem NON-HLOS.bin
error: cannot load 'NON-HLOS.bin'
fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.014s]
finished. total time: 0.015s
fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.005s]
finished. total time: 0.008s
fastboot flash fsg fsg.mbn
error: cannot load 'fsg.mbn'
fastboot erase cache
erasing 'cache'...
OKAY [ 0.002s]
finished. total time: 0.004s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.219s]
finished. total time: 0.220s
fastboot reboot