Database Develop

[Q] Help: Device locked: 5.1 fastboot flash fails

I have a Moto-maker-made Moto X with T-mobile sim (I think XT1053) and never installed any custom ROMs. The soak from couple weeks ago soft-bricked the phone (factory reset from fastboot menu just powers off the phone). I can get into fastboot, but the device is locked (status code 0). Do I have to unlock it in order to apply the factory image? The steps below fail currently.
I got the TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz from motorola, and ran all fastboot steps until "fastboot flash boot boot.img" which failed:
Windows output:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.913s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.664s
Phone output:
Failed to hab check for boot: 0x56
preflash validation failed for boot

Wrong forums. This is for the second generation (xt1095)

I have a failed flash :/

[Q] Help: Device locked: 5.1 fastboot flash fails

I have a Moto-maker-made Moto X with T-mobile sim (I think XT1053) and never installed any custom ROMs. The soak from couple weeks ago soft-bricked the phone (factory reset from fastboot menu just powers off the phone). I can get into fastboot, but the device is locked (status code 0). Do I have to unlock it in order to apply the factory image? The steps below fail currently.
I got the TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz from motorola, and ran all fastboot steps until "fastboot flash boot boot.img" which failed:
Windows output:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.913s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.664s
Phone output:
Failed to hab check for boot: 0x56
preflash validation failed for boot

gromul said:
I have a Moto-maker-made Moto X with T-mobile sim (I think XT1053) and never installed any custom ROMs. The soak from couple weeks ago soft-bricked the phone (factory reset from fastboot menu just powers off the phone). I can get into fastboot, but the device is locked (status code 0). Do I have to unlock it in order to apply the factory image? The steps below fail currently.
I got the TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz from motorola, and ran all fastboot steps until "fastboot flash boot boot.img" which failed:
Windows output:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.913s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.664s
Phone output:
Failed to hab check for boot: 0x56
preflash validation failed for boot
Click to expand...
Click to collapse
your bootloader must be unloced

Thanks, that fixed it.

Need help!! moto g6 forge (cricket) xt 1922-9 oficial original rom

Hi all,
I have a problem I have a moto g6 forge 16gb (cricket) I installed a different version (retail) to be exact but now the phone goes into fastboot mode and I get the following message: "start up failed, your device didn't star up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant ".
Now I can not enter the system, I need to reinstall the original system that I do not have or how I can fix the problem. What I know is that it's possible to fix, it if it's software no?
Can anybody help me?
Regards,

i tried this but no luck...
C:\Users\Ricardo\Desktop\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.004s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.011s]
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: '')
Finished. Total time: 0.114s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash bootloader bootloader.img
Sending 'bootloader' (7483 KB) OKAY [ 0.792s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.959s]
Finished. Total time: 1.770s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
Sending 'modem' (76974 KB) OKAY [ 5.679s]
Writing 'modem' OKAY [ 1.922s]
Finished. Total time: 7.621s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash fsg fsg.mbn
Sending 'fsg' (2380 KB) OKAY [ 0.307s]
Writing 'fsg' OKAY [ 0.175s]
Finished. Total time: 0.500s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) OKAY [ 1.843s]
Writing 'dsp' OKAY [ 0.483s]
Finished. Total time: 2.342s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash boot boot.img
Sending 'boot' (16384 KB) OKAY [ 0.867s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 1.116s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.0
Sending 'system' (521139 KB) OKAY [ 32.457s]
Writing 'system' (bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 32.604s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.1
Sending 'system' (504408 KB) OKAY [ 25.827s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 25.863s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.2
Sending 'system' (515109 KB) OKAY [ 23.901s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 24.041s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash system system.img_sparsechunk.3
Sending 'system' (487226 KB) OKAY [ 26.055s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 26.258s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash oem oem.img
Sending 'oem' (364938 KB) OKAY [ 19.066s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 19.144s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash vendor vendor.img
Sending 'vendor' (230306 KB) OKAY [ 11.192s]
Writing 'vendor' (bootloader) Security version downgrade
(bootloader) Image v failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
Finished. Total time: 11.404s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase carrier
Erasing 'carrier' OKAY [ 0.120s]
Finished. Total time: 0.214s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.085s]
Finished. Total time: 0.098s
C:\Users\Ricardo\Desktop\platform-tools>fastboot erase DDR
Erasing 'DDR' OKAY [ 0.189s]
Finished. Total time: 0.203s
C:\Users\Ricardo\Desktop\platform-tools>fastboot flash logo logo.bin
Sending 'logo' (1423 KB) OKAY [ 0.096s]
Writing 'logo' OKAY [ 0.150s]
Finished. Total time: 0.260s
C:\Users\Ricardo\Desktop\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\Users\Ricardo\Desktop\platform-tools>fastboot reboot

richi323 said:
Hi all,
I have a problem I have a moto g6 forge 16gb (cricket) I installed a different version (retail) to be exact but now the phone goes into fastboot mode and I get the following message: "start up failed, your device didn't star up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant ".
Now I can not enter the system, I need to reinstall the original system that I do not have or how I can fix the problem. What I know is that it's possible to fix, it if it's software no?
Can anybody help me?
Regards,
Click to expand...
Click to collapse
Well you can't Flash the retail firmware on that device. You need to flash the exact same firmware that was on the device before you bricked it. You can definitely use ADB and fastboot if you can get the phone into fastboot mode.
it's failing because you're trying to install an older firmware than the one you have. You're lucky it did not succeed flashing the GPT. That is the partition index. if you had successfully flash that and the bootloader from an older firmware than what you had you would have a hard brick on your hands with no chance of recovering it without a blank flash file.
Run
Fastboot getvar
To see what version of the software you have on your device. then use fastboot to flash the same or a newer version that is correct for your device.
Look here
https://mirrors.lolinet.com/firmware/moto/jeter/official/
Try cricket or att

madbat99 said:
Well you can't Flash the retail firmware on that device. You need to flash the exact same firmware that was on the device before you bricked it. You can definitely use ADB and fastboot if you can get the phone into fastboot mode.
it's failing because you're trying to install an older firmware than the one you have. You're lucky it did not succeed flashing the GPT. That is the partition index. if you had successfully flash that and the bootloader from an older firmware than what you had you would have a hard brick on your hands with no chance of recovering it without a blank flash file.
Run
Fastboot getvar
To see what version of the software you have on your device. then use fastboot to flash the same or a newer version that is correct for your device.
Look here
https://mirrors.lolinet.com/firmware/moto/jeter/official/
Try cricket or att
Click to expand...
Click to collapse
Hello and thanks for answering, yes i use this rom https://mirrors.lolinet.com/firmwar...ubsidy-CRICKET_regulatory-DEFAULT_CFC.xml.zip to restore my phoen but no luck, and retus rom the problem started but i see this rom is for moto g(6) play, i don´t know if cricket has another rom , my moto g6 forge has jeter OCP27.91-42 and I can not find that rom anywhere.
I have reviewed and donwloaded the att, retus and cricket but internally (3 roms) all are for moto g(6) play and tried with fastboot both with the same error result.
I've seen on Youtube a person who has moto G6 Forge with rom motorola/ jeter_a/jeter 8.0.0 /ocp27.91.41/43 and i think all the roms for this model should be the same but I can not find this rom.
sorry for my english i hope it is understood, any idea?

i have this with fastboot getvar all:
(bootloader) ro.build.fingerprint[0]: motorola/jeter_a/jeter:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-41/43:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.43.jeter_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0

richi323 said:
i have this with fastboot getvar all:
(bootloader) ro.build.fingerprint[0]: motorola/jeter_a/jeter:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-41/43:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.43.jeter_a.a.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
Click to expand...
Click to collapse
You may have yours updated to a build version that hasn't been released yet for download. I can't really help with that. You're supposed to check for a download of your current firmware before trying to flash anything. you're probably going to have to just wait until that firmware is either posted here in the Forum or uploaded to that website.

madbat99 said:
You may have yours updated to a build version that hasn't been released yet for download. I can't really help with that. You're supposed to check for a download of your current firmware before trying to flash anything. you're probably going to have to just wait until that firmware is either posted here in the Forum or uploaded to that website.
Click to expand...
Click to collapse
You are right, I thought that it was rom of my phone. It was the update of my phone and that with the retus I could return to retail but apparently I am still learning.
maybe someone upload the rom or I'll wait for it to be published, like you say.
pd. if it possible that make a rom with other moto g6 forge without root and install with fastboot with the bad moto g6 forge
Thank you,

today with XT1922-9_JETER_A_CRICKET_8.0.0_OCPS27.91-62-7_cid1_subsidy-CRICKET_regulatory-DEFAULT_CFC.xml my phone works again
i have a question, how can I do to unlock my moto g6 forge and use other sim?
I have tried to unlock (by code) it with 2 companies but they can not
regards

What commands do I need to put when I flash the rom? Thank you

HippiexPunk said:
What commands do I need to put when I flash the rom? Thank you
Click to expand...
Click to collapse
Use the commands in the file. You can use RSDlite with a Windows PC and it will flash it all for you. Or use RSDlite XML to batch to convert it to a .bat file for one click in fastboot. It converts it to a batch file to perform that flashes for you.
If you want to wipe data and start fresh, choose the flashfile.xml in the firmware. If you want to try to keep data, use the servicefile.xml.
If you are using official firmware, you don't need the bootloader unlocked
Find the tools here
Use RSDlite 6.2.4
works fine on windows 10.
Great tools on that page.
Get firmware from https.mirrors.lolinet.com

It looks like I'm in a similar situation. Today I went to upgrade my Cricket Moto G6 Play (XT1922-9) to Android Pie, which is available for the XT1922-9 but only for the RETUS channel. I ran the batch file in fastboot and received the "Preflash validation failed" on the boot, recovery and system partitions. Now the device only boots to the bootloader because it fails to validate the boot image. Likewise, recovery mode is inaccessible because it can't validate the recovery image. (Interestingly enough, neither of these images were actually flashed.)
Now the locked device seems completely bricked. Motorola wouldn't allow me to unlock the bootloader, and trying to flash the latest Oreo ROM for the Cricket channel also fails validation. (I had OCPS27.91-62-10 installed, but that doesn't seem to be available for download. I tried OCPS27.91-62-19.)
So am I really stuck on the bootloader with no inability to flash known-good (and properly signed) OEM firmware? How can Motorola create a system that's so fragile?

partition table gone?

Ok, so I bought a Moto X4 (XT-1900-7) with the goal to install lineage OS. I got with android 7.1.1 installed and I updated it with the built-in updater to 8.1 (I guess). After that there were no more updates available.
I unlocked the bootloader and tried flashing pie with a flash-all script I got somewhere.
No I am stuck in a boot loop: The Motorola logo appears with the note "Verity mode is set to logging" for a few seconds, than it turns black an starts over.
When I try to flash a ROM I get:
sudo ./flash-all.sh
(bootloader) is-logicalartition: not found
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.110s]
Finished. Total time: 0.113s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9520 KB) OKAY [ 0.340s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(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 'storsec.mbn' to 'storsec'
(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'
OKAY [ 0.188s]
Finished. Total time: 0.533s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.101s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (94843 KB) OKAY [ 3.288s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5680 KB) OKAY [ 0.186s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'modemst2' OKAY [ 0.003s]
Finished. Total time: 0.004s
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.150s]
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.579s]
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' (2153 KB) OKAY [ 0.068s]
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' (20625 KB) OKAY [ 0.692s]
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' (516148 KB) OKAY [ 17.491s]
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' (523995 KB) OKAY [ 18.490s]
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' (520953 KB) OKAY [ 17.796s]
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' (523244 KB) OKAY [ 17.745s]
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' (522088 KB) OKAY [ 17.449s]
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' (487694 KB) OKAY [ 16.998s]
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' (524133 KB) OKAY [ 18.174s]
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' (222598 KB) OKAY [ 7.805s]
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' (134369 KB) OKAY [ 4.625s]
Writing 'system_b' OKAY [ 1.023s]
Finished. Total time: 5.649s
(bootloader) is-logicalem__a: not found
Sending 'oem__a' (210797 KB) OKAY [ 7.291s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'carrier' OKAY [ 0.011s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.242s]
Finished. Total time: 0.243s
Erasing 'ddr' OKAY [ 0.003s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse
Here is the flash-all:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 9
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 dspso.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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
Click to expand...
Click to collapse
Since the first command of the script is "flash partition gpt.bin", I hoped I could repair the mess by flashing the right Stock ROM, so I tried several - with no luck. I got the ROMs from here: mirrors.lolinet. com/firmware/moto/payton. There are so many of them - I don't know which one is right. Not all of the ROMs tell you whether they are for my kind of X4 or not. Is it important to get a ROM specifically designed for a XT1900-7? I guess so, but why don't all the ROMs say which model they are for?
OK, so I hoped I could fix the device by installing twrp, format it and sideload a ROM. Again no luck. I managed to install the latest twrp and format the thing, but was unable to sideload anything. twrp says the internal sorage had 0MB.
I don't know what to do and need help. I am using ubuntu and have no windows pc available.

Your phone is RETEU variant on lolinet
Try flashing:
XT1900-7_PAYTON_RETEU_DS_9.0.....
You can open the script and copy each step in manually in fastboot to check for any errors, or just run the MAC script in linux.

OK, I thought so. I tried flashing said ROM and got the same problem.
sudo ./flash-all.sh
(bootloader) is-logicalartition: not found
Sending 'partition' (37 KB) OKAY [ 0.007s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.128s]
Finished. Total time: 0.171s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9520 KB) OKAY [ 0.329s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(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 'storsec.mbn' to 'storsec'
(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'
OKAY [ 0.195s]
Finished. Total time: 0.566s
Rebooting into bootloader OKAY [ 0.012s]
Finished. Total time: 0.263s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (94843 KB) OKAY [ 3.191s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5680 KB) OKAY [ 0.185s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'modemst2' OKAY [ 0.003s]
Finished. Total time: 0.003s
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4564 KB) OKAY [ 0.147s]
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.538s]
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' (2153 KB) OKAY [ 0.076s]
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' (20625 KB) OKAY [ 0.701s]
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' (516148 KB) OKAY [ 17.138s]
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' (523995 KB) OKAY [ 17.363s]
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' (520953 KB) OKAY [ 17.834s]
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' (523244 KB) OKAY [ 18.286s]
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' (522088 KB) OKAY [ 18.237s]
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' (487694 KB) OKAY [ 17.075s]
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' (524133 KB) OKAY [ 18.088s]
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' (222598 KB) OKAY [ 7.794s]
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' (134369 KB) OKAY [ 4.592s]
Writing 'system_b' OKAY [ 1.026s]
Finished. Total time: 5.634s
(bootloader) is-logicalem__a: not found
Sending 'oem__a' (210797 KB) OKAY [ 7.264s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'carrier' OKAY [ 0.010s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.170s]
Finished. Total time: 0.170s
Erasing 'ddr' OKAY [ 0.003s]
The problem is in the first line I guess:
(bootloader) is-logicalartition: not found
Click to expand...
Click to collapse
How do I address this?

If you can get into fastboot, try:
fastboot boot twrp-3.3.1-0-twrp.img (with the img file on your computer)
and fix through twrp

If you are bootloop-ing (ignore the verity thing), it simply means you do not have a valid ROM for it to boot. If it were me, I would probably grab an appropriate (stock) ROM from lolinet and RSDlite it. But I have no experience with doing that on an A/B phone, so don't know if that's good advice. But since RSDlite takes the command stack from the zip itself, I would think that would be okay.
scratch that - I don't think rsdlite works on this phone - may have to use that lenovo moto smart assistant thing but that may require a working phone that can run that app... I'll talk with moto about that.
When flashing, beware of going backwards, bootloader-wise. Same or later. some phones will brick if you try to flash a M.

johnjingle said:
If you can get into fastboot, try:
fastboot boot twrp-3.3.1-0-twrp.img (with the img file on your computer)
and fix through twrp
Click to expand...
Click to collapse
What do you mean by "fix"? I dont know, what else I can do?

KrisM22 said:
If you are bootloop-ing (ignore the verity thing), it simply means you do not have a valid ROM for it to boot. If it were me, I would probably grab an appropriate (stock) ROM from lolinet and RSDlite it. But I have no experience with doing that on an A/B phone, so don't know if that's good advice. But since RSDlite takes the command stack from the zip itself, I would think that would be okay.
scratch that - I don't think rsdlite works on this phone - may have to use that lenovo moto smart assistant thing but that may require a working phone that can run that app... I'll talk with moto about that.
When flashing, beware of going backwards, bootloader-wise. Same or later. some phones will brick if you try to flash a M.
Click to expand...
Click to collapse
I went forward and backward with the ROMs, but how can I change the bootloader? What is a "M."?

M is marshmallow - 6 - there is none for the X4 - just 7,8,and 9. N, O, and P.
When you flash a ROM, you defacto change the bootloader if needed with that flash. ou will see a reboot in the early part of the flashall stack after it has flashed a new bootloader. It's part of the flash. Going forward. You cannot do that with a flash going backward - the flash will fail.
Please remember that I am new here so this is my best guess:
I just looked at the error messages in your first post - it says it can't find modem-a
This means to me that your phone is not A/B but just one set of partitions.
It is still effectively at 8.x in terms of bootloader and in terms of partition structure.
You are trying to flash with a stack of commands that assumes you are A/B.
At some point when doing an OTA upgrade from 8.x to 9 on this phone, somebody(I have no idea who) changes the phones partition setup from one to 2 sets.
So I suspect (I dont know - everything is done at your own risk) that you could flash an appropriate 8.x ROM from lolinet but you will have to make a command stack that doesn't reference -a or -b in it. It would also be subtly different from munchy's because that is aimed at a system that has 2 sets of partitions and will not have the flash new bootloader and reboot.
You might have success looking through older threads, perhaps munchy's, or perhaps asking munchy for an older bat file that would work on a phone that still only has one partition set - flash 8.x and at least get your phone running.
THEN...
Now, as to how to get to 9 from 8, I don't think a simple flash with munchy's command stack will do it but he would be able to tell you that. Mine was converted by the OTA update to 9.
If you have a working 8 you could try lenovo moto smart assistant (lmsa) and see if that offers to flash 9 for you, though if OTA didn't offer it, I doubt it will. Whether you can grab a 9 rom from lolinet and just flash it, I have no idea. Munchy might.
EDIT: I just realized that you might now have a situation where you have a 9 bootloader but a 8 partition set. So I don't know what would happen if you find an old command stack for 8 and run it. Will there be a bootloader conflict.

KrisM22 said:
M is marshmallow - 6 - there is none for the X4 - just 7,8,and 9. N, O, and P.
When you flash a ROM, you defacto change the bootloader if needed with that flash. ou will see a reboot in the early part of the flashall stack after it has flashed a new bootloader. It's part of the flash. Going forward. You cannot do that with a flash going backward - the flash will fail.
Please remember that I am new here so this is my best guess:
I just looked at the error messages in your first post - it says it can't find modem-a
This means to me that your phone is not A/B but just one set of partitions.
It is still effectively at 8.x in terms of bootloader and in terms of partition structure.
You are trying to flash with a stack of commands that assumes you are A/B.
At some point when doing an OTA upgrade from 8.x to 9 on this phone, somebody(I have no idea who) changes the phones partition setup from one to 2 sets.
So I suspect (I dont know - everything is done at your own risk) that you could flash an appropriate 8.x ROM from lolinet but you will have to make a command stack that doesn't reference -a or -b in it. It would also be subtly different from munchy's because that is aimed at a system that has 2 sets of partitions and will not have the flash new bootloader and reboot.
You might have success looking through older threads, perhaps munchy's, or perhaps asking munchy for an older bat file that would work on a phone that still only has one partition set - flash 8.x and at least get your phone running.
THEN...
Now, as to how to get to 9 from 8, I don't think a simple flash with munchy's command stack will do it but he would be able to tell you that. Mine was converted by the OTA update to 9.
If you have a working 8 you could try lenovo moto smart assistant (lmsa) and see if that offers to flash 9 for you, though if OTA didn't offer it, I doubt it will. Whether you can grab a 9 rom from lolinet and just flash it, I have no idea. Munchy might.
EDIT: I just realized that you might now have a situation where you have a 9 bootloader but a 8 partition set. So I don't know what would happen if you find an old command stack for 8 and run it. Will there be a bootloader conflict.
Click to expand...
Click to collapse
This is the closest I got towards an explanation for my situation so far - so thank you! I found the script, I used in so many threads, but nothing else. I will keep looking. Since the phone is shipped with a Android 7, there should be more users experiencing the same conflict.

Please report back on how this goes for you...
I've done some more research on lmsa.
go here
https://www.motorola.com/us/lenovo-motorola-smart-assistant
and download it.
Watch the video for software issues(lower left of that page).
Install it.
Start it up.
You want flash/ rescue.
follow the instructions and put your phone into fastboot mode and connect to PC via USB.
If it offers you something(takes a minute) click the little download arrow and when it's downloaded, click rescue.
This is what it looks like for me before I would click the download arrow.

derknobber said:
This is the closest I got towards an explanation for my situation so far - so thank you! I found the script, I used in so many threads, but nothing else. I will keep looking. Since the phone is shipped with a Android 7, there should be more users experiencing the same conflict.
Click to expand...
Click to collapse
Hello, did you managed to fix your problem ? im having exactly the same insue on my moto g7 plus

Moto G5S Plus | TWRP Bootloop

I've checked lots of other posts here, but none of them worked for me.
I've installed a somewhat quirky custom ROM (Pixel experience 12) on my Moto G5S Plus, and now I can't get into TWRP, because it bootloops.
When I try to erase/format any partition that might solve the problem from fastboot, I get:
> fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.000s
the same happens for recovery & userdata.
I can't reinstall stock ROM because the first command also doesn't work:
> flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
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.063s
Also, the custom ROM is working fine, the only problem is TWRP not starting.
Do you guys have any clue on how to solve this?