Develop Bugs

System Update Fails (T-Mobile phone)

Yesterday I got notification from Motorola Update Services about system update version OCXS27.1.2 (Android security updates thru March 1 2018). I download but it fails to install. [Software updated unsuccessful - Sorry, there was a problem updating your Moto Z². No changes were Made. √ OK]
I bought the phone used so dunno it's history. After purchase I unlocked bootloader and installed TWRP but have not rooted. I had it carrier unlocked thru an online service that enabled the T-mobile app on the server side (cellunlocker.net), and installed FreedomPop SIM card.
I called Motorola tech support. They first had me reset app preferences then passed me off to level 2 support after that didn't work, who had me factory data reset, and now they're passing me off to level 3 who may call me next week, since that didn't work either. Note when I did the factory data reset, it rebooted into TWRP automatically which asked for my lockcode, before (apparently) handling the reset request. After reboot I skipped the google login to make sure nothing conflicted, but it still won't do the system update.
I'm wondering if it possibly has to do with the phone's history somehow, or because I unlocked bootloader, or because I'm not using a T-Mobile SIM card, or because I installed TWRP. I dunno. I told this to Moto support and they didn't seem to care or think it mattered. They could see my resets from their side after I provided my IMEI.
Any ideas?

Having twrp flashed modifies /boot as our recovery is in the ramdisk in our /boot, which causes ota to fail. Fastboot flash stock boot.img for your current os (ncx26.2, ncx26.7, ocx27 or, ocx27.1) from the corresponding firmware package (flashall .zip) and you should be good to go. The official twrp can be booted now so no need to have it installed. If you do root in the future the same rule will apply as systemless root is also in /boot.
Sent from my Moto Z (2) using XDA Labs

Installing twrp mounted system as rw. You need to actually do a flash all with the official firmware by the Motorola Firmware Team on AFH. I have a thread in the guides section that educates on how to do this. Tier 3 will probably suggest the same.

You are probably getting this same error. It means you need to flash all with an official zip to have the update go through correctly.

Thanks much. I was a little worried as there seems to be an error message about file system, a scary looking warning, and FAILURE message near the end, but seems to have worked, and was able to OTA update after flashall. The only thing the instructions didn't specifically mention was to start phone with volume down+-power for fastboot, once I figured that out all was well.
Code:
Microsoft Windows [Version 10.0.16299.371]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\>mkdir \Z2-Util
C:\>cd \Z2-Util
C:\Z2-Util>dir
Volume in drive C has no label.
Volume Serial Number is B45D-BE40
Directory of C:\Z2-Util
05/06/2018 03:45 PM <DIR> .
05/06/2018 03:45 PM <DIR> ..
12/30/2017 04:19 PM 1,784,320 adb.exe
12/30/2017 04:19 PM 97,792 AdbWinApi.dll
12/30/2017 04:19 PM 62,976 AdbWinUsbApi.dll
01/30/2018 02:22 PM 16,777,216 adspso.bin
01/30/2018 02:22 PM 23,905,510 boot.img
01/30/2018 02:22 PM 10,121,472 bootloader.img
01/30/2018 02:22 PM 4,604,160 BTFM.bin
12/30/2017 04:19 PM 853,504 fastboot.exe
04/23/2018 09:17 PM 1,433 flashall.bat
01/30/2018 04:24 PM 3,009 flashfile.xml
01/30/2018 02:22 PM 5,730,304 fsg.mbn
01/30/2018 02:22 PM 211,712 gpt.bin
01/30/2018 02:22 PM 3,227,518 logo.bin
01/30/2018 04:24 PM 911 NASH_TMO_C_OCX27.109-51_subsidy-TMO_regulatory-DEFAULT_CFC.info.txt
01/30/2018 02:22 PM 99,753,156 NON-HLOS.bin
01/30/2018 02:17 PM 179,898,736 oem.img
01/30/2018 04:23 PM 0 regulatory_info_default.png
01/30/2018 04:24 PM 2,701 servicefile.xml
01/30/2018 04:22 PM 610 slcf_rev_d_tmo_rsu_v1.1.nvm
01/30/2018 04:23 PM 528,589,836 system.img_sparsechunk.0
01/30/2018 04:23 PM 507,000,512 system.img_sparsechunk.1
01/30/2018 04:23 PM 531,596,644 system.img_sparsechunk.2
01/30/2018 04:23 PM 536,338,408 system.img_sparsechunk.3
01/30/2018 04:23 PM 528,569,592 system.img_sparsechunk.4
01/30/2018 04:23 PM 430,677,116 system.img_sparsechunk.5
01/30/2018 04:24 PM 527,547,620 system_b.img_sparsechunk.0
01/30/2018 04:24 PM 314,597,544 system_b.img_sparsechunk.1
27 File(s) 4,251,954,312 bytes
2 Dir(s) 250,683,760,640 bytes free
C:\Z2-Util>flashall
C:\Z2-Util>fastboot oem fb_mode_set
< waiting for any device >
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
C:\Z2-Util>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.012s]
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.250s]
finished. total time: 0.267s
C:\Z2-Util>fastboot flash bootloader_a bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (9884 KB)...
OKAY [ 0.454s]
writing 'bootloader_a'...
(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.661s
C:\Z2-Util>fastboot flash bootloader_b bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (9884 KB)...
OKAY [ 0.365s]
writing 'bootloader_b'...
(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.243s]
finished. total time: 0.627s
C:\Z2-Util>fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97415 KB)...
OKAY [ 4.009s]
writing 'modem_a'...
OKAY [ 1.047s]
finished. total time: 5.055s
C:\Z2-Util>fastboot flash fsg_a fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5596 KB)...
OKAY [ 0.266s]
writing 'fsg_a'...
OKAY [ 0.078s]
finished. total time: 0.344s
C:\Z2-Util>fastboot flash modem_b NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_b' (97415 KB)...
OKAY [ 3.016s]
writing 'modem_b'...
OKAY [ 1.031s]
finished. total time: 4.063s
C:\Z2-Util>fastboot flash fsg_b fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_b' (5596 KB)...
OKAY [ 0.172s]
writing 'fsg_b'...
OKAY [ 0.078s]
finished. total time: 0.250s
C:\Z2-Util>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Z2-Util>fastboot flash bluetooth_a BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.172s]
writing 'bluetooth_a'...
OKAY [ 0.047s]
finished. total time: 0.234s
C:\Z2-Util>fastboot flash dsp_a adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.625s]
writing 'dsp_a'...
OKAY [ 0.156s]
finished. total time: 0.781s
C:\Z2-Util>fastboot flash logo_a logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (3151 KB)...
OKAY [ 0.141s]
writing 'logo_a'...
OKAY [ 0.047s]
finished. total time: 0.187s
C:\Z2-Util>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23345 KB)...
OKAY [ 0.937s]
writing 'boot_a'...
OKAY [ 0.391s]
finished. total time: 1.344s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516201 KB)...
OKAY [ 20.836s]
writing 'system_a'...
OKAY [ 5.582s]
finished. total time: 26.434s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (495117 KB)...
OKAY [ 20.062s]
writing 'system_a'...
OKAY [ 4.869s]
finished. total time: 24.930s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (519137 KB)...
OKAY [ 20.861s]
writing 'system_a'...
OKAY [ 5.812s]
finished. total time: 26.689s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523767 KB)...
OKAY [ 22.962s]
writing 'system_a'...
OKAY [ 4.966s]
finished. total time: 27.928s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (516181 KB)...
OKAY [ 25.824s]
writing 'system_a'...
OKAY [ 5.688s]
finished. total time: 31.512s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (420583 KB)...
OKAY [ 18.590s]
writing 'system_a'...
OKAY [ 3.969s]
finished. total time: 22.559s
C:\Z2-Util>fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (175682 KB)...
OKAY [ 7.904s]
writing 'oem_a'...
OKAY [ 1.781s]
finished. total time: 9.686s
C:\Z2-Util>fastboot flash bluetooth_b BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (4496 KB)...
OKAY [ 0.172s]
writing 'bluetooth_b'...
OKAY [ 0.078s]
finished. total time: 0.250s
C:\Z2-Util>fastboot flash dsp_b adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_b' (16384 KB)...
OKAY [ 0.750s]
writing 'dsp_b'...
OKAY [ 0.156s]
finished. total time: 0.922s
C:\Z2-Util>fastboot flash logo_b logo.bin
target reported max download size of 536870912 bytes
sending 'logo_b' (3151 KB)...
OKAY [ 0.172s]
writing 'logo_b'...
OKAY [ 0.047s]
finished. total time: 0.219s
C:\Z2-Util>fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (23345 KB)...
OKAY [ 0.812s]
writing 'boot_b'...
OKAY [ 0.391s]
finished. total time: 1.203s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (516201 KB)...
OKAY [ 22.460s]
writing 'system_b'...
OKAY [ 5.437s]
finished. total time: 27.898s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (495117 KB)...
OKAY [ 20.393s]
writing 'system_b'...
OKAY [ 4.872s]
finished. total time: 25.281s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_b' (519137 KB)...
OKAY [ 21.401s]
writing 'system_b'...
OKAY [ 5.859s]
finished. total time: 27.260s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_b' (523767 KB)...
OKAY [ 22.156s]
writing 'system_b'...
OKAY [ 4.984s]
finished. total time: 27.141s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_b' (516181 KB)...
OKAY [ 21.069s]
writing 'system_b'...
OKAY [ 5.667s]
finished. total time: 26.767s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_b' (420583 KB)...
OKAY [ 17.404s]
writing 'system_b'...
OKAY [ 3.994s]
finished. total time: 21.398s
C:\Z2-Util>fastboot flash oem_b oem.img
target reported max download size of 536870912 bytes
sending 'oem_b' (175682 KB)...
OKAY [ 6.563s]
writing 'oem_b'...
OKAY [ 1.766s]
finished. total time: 8.328s
C:\Z2-Util>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot erase ddr
erasing 'ddr'...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Z2-Util>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Z2-Util>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.203s]
finished. total time: 1.203s
C:\Z2-Util>fastboot --set-active=other
Setting current slot to 'b'...
(bootloader) WARNING: Bootloader images on target slot b are not valid!!
(bootloader) There is risk of bricking HW. Please flash valid bootloader
(bootloader) into slot b before activating it. OR you could force to
(bootloader) switch to slot b by running the same command again
(bootloader) within 30 s if you understand what you're doing
FAILED (remote failure)
finished. total time: 0.141s
C:\Z2-Util>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>

I have the same problem, but I do not have TWRP installed. Only booted into it, to install Magisk(and root). Otherwise, I'm stock image and stock bootloader.

Unseeablething said:
I have the same problem, but I do not have TWRP installed. Only booted into it, to install Magisk(and root). Otherwise, I'm stock image and stock bootloader.
Click to expand...
Click to collapse
You installed magisk which mounted a partition as r/w

Uzephi said:
You installed magisk which mounted a partition as r/w
Click to expand...
Click to collapse
Got it! Guess at this point, I'll just go over to DU.

So is there anything we can do to keep root and install updates?

teradark said:
So is there anything we can do to keep root and install updates?
Click to expand...
Click to collapse
Not really. The Motorola OTA checks the hash sum of each partition and if there is any discrepancy on partitions you wouldn't be able to edit without unlocking, it will fail as shown in the ota error message image a few posts back.

So if root is in a particular part of the partition, could I flash that specific part where root is stored, then perform the update, then re root?

teradark said:
So if root is in a particular part of the partition, could I flash that specific part where root is stored, then perform the update, then re root?
Click to expand...
Click to collapse
Root mounts system and maybe other partitions as read/write when they aren't supposed to be, making the hash sum different. You would need to at least flash the official system sparses from the Motorola firmware team's flash all if not more than that. (Root is nestled in boot, so you'd need to flash that as well).

Well I can't update again but for some other reason, even after flashall.
Previously it was cuz of TWRP so flashall then OTA update no problem. Then I installed magisk and adaway and all fine. Then I was trying to figure out how to get rid of tmobile stuff, tried a couple apps on playstore, including titanium backup, but couldn't figure it out. Then I saw someone wrote an exe to do it (debload) and running that made phone not boot. flashall again, try debload, it works, happy, but can't find update (different message, says there are no updates). Disappointed but decide rather have no t-mobile apps than update, so move on and install magisk. Then it can't boot. Decide I'd rather have adaway than no t-mobile so flashall again, but still can't update.
So other than installing magisk or twrp, what could make it so I can't update immediately after flashall? I imagine that debload did something that flashall doesn't undo, but there's no real detail or source/etc about what it's doing other than removing oem partition, but I see flashall puts that back so doesn't seem like that's it...

So I flash all and installed the OTA, does this mean that since i installed the OTA that i cant install the flash all manual update(btw updating this device is a pain on linux)

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

Image signed with bad key trying to flash stock firmware (boot.img, recovery.img)

I'm trying to relock the bootloader on my Moto G5s coming back after a hardbrick. I have the BC.12 (2018-06-26) bootloader and I've tried a dozen different firmwares. All have the same problem when flashing boot and recovery images.
Code:
D:\www.stockrom.net_MONTANA_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory_NO_ERASE_CFC.xml>fastboot flash boot boot.img
Sending 'boot' (16384 KB) OKAY [ 0.519s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.380s]
Finished. Total time: 0.907s
D:\www.stockrom.net_MONTANA_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory_NO_ERASE_CFC.xml>fastboot flash recovery recovery.img
Sending 'recovery' (16484 KB) OKAY [ 0.522s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.411s]
Finished. Total time: 0.944s
All of the other images flash fine, and the phone does boot, but it won't let me relock the bootloader due to the images not being signed. Is there any way of fixing this or am I doomed and stuck with an unlocked phone?

Same Problem here, anyone a idea to fix?

okay, i finally found a solution after 2 days of fighting haha
so, here's what you need to do:
download the latest firmware (link)
then flash it with the usual method but without flashing partition and bootloader images
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
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 erase cache
fastboot erase userdata
fastboot erase DDR
fastboot fb_mode clear
and then do:
Code:
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 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 boot boot.img
fastboot oem lock
this worked for me on xt1794

THX A LOT!!! This really helped!

It didn't work. What else can I do?
Code:
E:\moto\fb>fastboot oem fb_mode_set
...
OKAY [ 0.004s]
finished. total time: 0.004s
E:\moto\fb>fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2195 KB)...
OKAY [ 0.071s]
writing 'logo'...
OKAY [ 0.106s]
finished. total time: 0.180s
E:\moto\fb>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.382s]
finished. total time: 0.901s
E:\moto\fb>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.522s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.413s]
finished. total time: 0.938s
E:\moto\fb>fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (67978 KB)...
OKAY [ 2.141s]
writing 'modem'...
OKAY [ 1.078s]
finished. total time: 3.222s
E:\moto\fb>fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (3560 KB)...
OKAY [ 0.114s]
writing 'fsg'...
OKAY [ 0.125s]
finished. total time: 0.241s
E:\moto\fb>fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.518s]
writing 'dsp'...
OKAY [ 0.283s]
finished. total time: 0.802s
E:\moto\fb>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (135426 KB)...
OKAY [ 4.263s]
writing 'oem'...
OKAY [ 1.828s]
finished. total time: 6.093s
E:\moto\fb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (256294 KB)...
OKAY [ 8.065s]
writing 'system'...
OKAY [ 4.087s]
finished. total time: 15.253s
E:\moto\fb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256762 KB)...
OKAY [ 8.633s]
writing 'system'...
OKAY [ 3.316s]
finished. total time: 11.953s
E:\moto\fb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (255764 KB)...
OKAY [ 8.597s]
writing 'system'...
OKAY [ 3.545s]
finished. total time: 12.145s
E:\moto\fb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (260630 KB)...
OKAY [ 8.759s]
writing 'system'...
OKAY [ 3.389s]
finished. total time: 12.150s
E:\moto\fb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (257521 KB)...
OKAY [ 8.661s]
writing 'system'...
OKAY [ 3.360s]
finished. total time: 12.023s
E:\moto\fb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (245941 KB)...
OKAY [ 8.264s]
writing 'system'...
OKAY [ 3.176s]
finished. total time: 11.442s
E:\moto\fb>fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (258569 KB)...
OKAY [ 8.685s]
writing 'system'...
OKAY [ 3.244s]
finished. total time: 11.931s
E:\moto\fb>fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (251493 KB)...
OKAY [ 8.456s]
writing 'system'...
OKAY [ 3.680s]
finished. total time: 12.139s
E:\moto\fb>fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (257933 KB)...
OKAY [ 8.666s]
writing 'system'...
OKAY [ 3.741s]
finished. total time: 12.408s
E:\moto\fb>fastboot flash system system.img_sparsechunk.9
target reported max download size of 535822336 bytes
sending 'system' (214096 KB)...
OKAY [ 7.202s]
writing 'system'...
OKAY [ 2.700s]
finished. total time: 9.905s
E:\moto\fb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
E:\moto\fb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.248s]
finished. total time: 0.250s
E:\moto\fb>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.002s]
finished. total time: 0.004s
E:\moto\fb>fastboot fb_mode clear
fastboot: usage: unknown command fb_mode
E:\moto\fb>fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.006s]
finished. total time: 0.006s
E:\moto\fb>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.007s]
finished. total time: 0.008s
E:\moto\fb>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (135426 KB)...
OKAY [ 4.263s]
writing 'oem'...
OKAY [ 1.814s]
finished. total time: 6.079s
E:\moto\fb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (256294 KB)...
OKAY [ 8.066s]
writing 'system'...
OKAY [ 4.092s]
finished. total time: 12.161s
E:\moto\fb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (256762 KB)...
OKAY [ 8.078s]
writing 'system'...
OKAY [ 3.292s]
finished. total time: 11.372s
E:\moto\fb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (255764 KB)...
OKAY [ 8.046s]
writing 'system'...
OKAY [ 3.500s]
finished. total time: 11.547s
E:\moto\fb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (260630 KB)...
OKAY [ 8.199s]
writing 'system'...
OKAY [ 3.394s]
finished. total time: 11.595s
E:\moto\fb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 535822336 bytes
sending 'system' (257521 KB)...
OKAY [ 8.103s]
writing 'system'...
OKAY [ 3.348s]
finished. total time: 11.451s
E:\moto\fb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 535822336 bytes
sending 'system' (245941 KB)...
OKAY [ 7.738s]
writing 'system'...
OKAY [ 3.185s]
finished. total time: 10.924s
E:\moto\fb>fastboot flash system system.img_sparsechunk.6
target reported max download size of 535822336 bytes
sending 'system' (258569 KB)...
OKAY [ 8.135s]
writing 'system'...
OKAY [ 3.250s]
finished. total time: 11.387s
E:\moto\fb>fastboot flash system system.img_sparsechunk.7
target reported max download size of 535822336 bytes
sending 'system' (251493 KB)...
OKAY [ 7.914s]
writing 'system'...
OKAY [ 3.677s]
finished. total time: 11.592s
E:\moto\fb>fastboot flash system system.img_sparsechunk.8
target reported max download size of 535822336 bytes
sending 'system' (257933 KB)...
OKAY [ 8.115s]
writing 'system'...
OKAY [ 3.724s]
finished. total time: 11.842s
E:\moto\fb>fastboot flash system system.img_sparsechunk.9
target reported max download size of 535822336 bytes
sending 'system' (214096 KB)...
OKAY [ 6.737s]
writing 'system'...
OKAY [ 2.693s]
finished. total time: 9.432s
E:\moto\fb>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.517s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.374s]
finished. total time: 0.893s
E:\moto\fb>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.005s

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.