Develop Bugs

Bricked MOTO G5(XT1676) stucked at fastboot menu

hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found

Flash this firmware https://drive.google.com/file/d/1cESQyuRpeUAmmEn67_to0sQ0KLhkMnWM/view (Oreo 8.1, February 2019 security patch) using fastboot and commands below. All the data in the internal storage of the phone will be erased.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
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: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Any ideas?

pablito1984 said:
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
Any ideas?
Click to expand...
Click to collapse
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
https://mirrors.lolinet.com/firmware/moto/cedric/official/

TheFixItMan said:
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
Click to expand...
Click to collapse
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error

pablito1984 said:
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
Click to expand...
Click to collapse
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)

TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logical: partition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse

pablito1984 said:
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
Click to expand...
Click to collapse
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk

TheFixItMan said:
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
Click to expand...
Click to collapse
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Start up failed:
Your device didn`t start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Last time flashing failed
USB Connected
failed to validate recovery iumage
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Click to expand...
Click to collapse
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.170s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.240s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.689s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.694s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.688s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.969s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (256537 KB) OKAY [ 8.462s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256653 KB) OKAY [ 8.529s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (257978 KB) OKAY [ 8.446s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (260705 KB) OKAY [ 8.488s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (257421 KB) OKAY [ 8.464s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (257865 KB) OKAY [ 8.506s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (252667 KB) OKAY [ 8.402s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (253700 KB) OKAY [ 8.409s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (250301 KB) OKAY [ 8.271s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66366 KB) OKAY [ 2.329s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.258s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase cache
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase customize
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase clogo
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot oem fb_mode_clear
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse

pablito1984 said:
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
Click to expand...
Click to collapse
Either your setup is wrong - try another pc USB cable etc or you have a motherboard fault & need to replace it

TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is

ghettozo said:
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
Click to expand...
Click to collapse
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before

TheFixItMan said:
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
Click to expand...
Click to collapse
thanks. yes im using the forum here and google but im having issues
thankyou\

bootloop whit bootloader lock and debug usb off Moto Z2 play

Hello and thank you for your work, my motorola z2 play came into bootloop from scratch, when it was in stock configuration, then without active debugging usb, bootloader unlocked and being in bootloop I can't unlock anything or even install the official ROM , now I'm trying with Lenovo Moto Smart but I have little hope because the phone keeps turning on and off even when it's in recovery mode. Do you have any advice for me?
Sorry for the poor description but I'm not very experienced, I ask you for advice because I don't know how to do it anymore.
Thank you,
Stephen.
PS: I also tried to unlock the oem with the motorola code but without success
PSS: I copy the account of my tempted to flash the stock rom
>> fastboot flash partition gpt.bin
>> fastboot flash bootloader bootloader.img
>> fastboot flash logo logo.bin
>> fastboot flash boot boot.img
>> fastboot flash recovery recovery.img
>> fastboot flash dsp adspso.bin
>> fastboot flash oem oem.img
>> fastboot flash system system.img_sparsechunk.0
>> fastboot flash system system.img_sparsechunk.1
>> fastboot flash system system.img_sparsechunk.2
>> fastboot flash system system.img_sparsechunk.3
>> fastboot flash system system.img_sparsechunk.4
>> fastboot flash system system.img_sparsechunk.5
>> fastboot flash system system.img_sparsechunk.6
>> fastboot flash system system.img_sparsechunk.7
>> fastboot flash modem NON-HLOS.bin
>> fastboot erase modemst1
>> fastboot erase modemst2
>> fastboot flash fsg fsg.mbn
>> fastboot erase cache
>> fastboot erase userdata
>> fastboot erase customize
>> fastboot erase clogo
>> fastboot oem fb_mode_clear
>> fastboot reboot
OKAY [ 0.002s]
Finished. Total time: 0.007s
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.166s]
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: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.281s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.214s]
Writing 'logo' OKAY [ 0.066s]
Finished. Total time: 0.430s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.547s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.639s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logicalem: not found
Sending 'oem' (232923 KB) OKAY [ 5.260s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Sending 'system' (517135 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (506931 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (522215 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (521087 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (518083 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (515569 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (250209 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory
(bootloader) is-logical:modem: not found
Sending 'modem' (75092 KB) OKAY [ 1.821s]
Writing 'modem' OKAY [ 0.807s]
Finished. Total time: 2.731s
Erasing 'modemst1' OKAY [ 0.028s]
Finished. Total time: 0.032s
Erasing 'modemst2' OKAY [ 0.028s]
Finished. Total time: 0.032s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2932 KB) OKAY [ 0.230s]
Writing 'fsg' OKAY [ 0.086s]
Finished. Total time: 0.336s
Erasing 'cache' OKAY [ 0.006s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.277s]
Finished. Total time: 0.281s
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.132s]
Finished. Total time: 0.135s
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
"Update"
I tried to use Lenovo moto smart assistant and the result is this message:
Start Up Failed:
Your devices didn't start up successfully.
Use the software repair assistant on computer to repair your devices.
Connect your device[...]
Ap Fastboot Flash Mode (Secure)
ERROR: Failed topass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB connected
thank you guys!

Could you find any solution?

stemonta said:
Hello and thank you for your work, my motorola z2 play came into bootloop from scratch, when it was in stock configuration, then without active debugging usb, bootloader unlocked and being in bootloop I can't unlock anything or even install the official ROM , now I'm trying with Lenovo Moto Smart but I have little hope because the phone keeps turning on and off even when it's in recovery mode. Do you have any advice for me?
Sorry for the poor description but I'm not very experienced, I ask you for advice because I don't know how to do it anymore.
Thank you,
Stephen.
PS: I also tried to unlock the oem with the motorola code but without success
PSS: I copy the account of my tempted to flash the stock rom
>> fastboot flash partition gpt.bin
>> fastboot flash bootloader bootloader.img
>> fastboot flash logo logo.bin
>> fastboot flash boot boot.img
>> fastboot flash recovery recovery.img
>> fastboot flash dsp adspso.bin
>> fastboot flash oem oem.img
>> fastboot flash system system.img_sparsechunk.0
>> fastboot flash system system.img_sparsechunk.1
>> fastboot flash system system.img_sparsechunk.2
>> fastboot flash system system.img_sparsechunk.3
>> fastboot flash system system.img_sparsechunk.4
>> fastboot flash system system.img_sparsechunk.5
>> fastboot flash system system.img_sparsechunk.6
>> fastboot flash system system.img_sparsechunk.7
>> fastboot flash modem NON-HLOS.bin
>> fastboot erase modemst1
>> fastboot erase modemst2
>> fastboot flash fsg fsg.mbn
>> fastboot erase cache
>> fastboot erase userdata
>> fastboot erase customize
>> fastboot erase clogo
>> fastboot oem fb_mode_clear
>> fastboot reboot
OKAY [ 0.002s]
Finished. Total time: 0.007s
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.166s]
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: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.281s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.214s]
Writing 'logo' OKAY [ 0.066s]
Finished. Total time: 0.430s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.547s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.639s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logicalem: not found
Sending 'oem' (232923 KB) OKAY [ 5.260s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Sending 'system' (517135 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (506931 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (522215 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (521087 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (518083 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (515569 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (250209 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory
(bootloader) is-logical:modem: not found
Sending 'modem' (75092 KB) OKAY [ 1.821s]
Writing 'modem' OKAY [ 0.807s]
Finished. Total time: 2.731s
Erasing 'modemst1' OKAY [ 0.028s]
Finished. Total time: 0.032s
Erasing 'modemst2' OKAY [ 0.028s]
Finished. Total time: 0.032s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2932 KB) OKAY [ 0.230s]
Writing 'fsg' OKAY [ 0.086s]
Finished. Total time: 0.336s
Erasing 'cache' OKAY [ 0.006s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.277s]
Finished. Total time: 0.281s
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.132s]
Finished. Total time: 0.135s
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
"Update"
I tried to use Lenovo moto smart assistant and the result is this message:
Start Up Failed:
Your devices didn't start up successfully.
Use the software repair assistant on computer to repair your devices.
Connect your device[...]
Ap Fastboot Flash Mode (Secure)
ERROR: Failed topass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB connected
thank you guys!
Click to expand...
Click to collapse
Can u tell me your model [email protected]

Moto Z2 Force Xt1789-5 damage emmc, No bootloder I can't install the TWRP

Good evening everyone, I introduce myself my name is Eduardo de Mexíco, I want to contribute to help people who have problems with the Moto Z2 Force.
I have the Model XT1789-5, first unlock the bootloader with Motorola and upgrade to Android Pie.
Now I don't have IME, baseband and WIfi.
I have read a lot in this forum, but I cannot find the correct repair.
That's why I put this thread in order to give a repair to my cell phone.
Attach the "flash" with minimal ADB and fastbool tool.
Is the emmc damaged?
The blanck flash appears "waiting for devices" I have installed Motorola and Qualcomm drivers.
I can't change firmware.
Can you help me, please?
Microsoft Windows [Versión 10.0.17763.678]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Already locked
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.011s]
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.233s]
finished. total time: 0.248s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.306s]
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.209s]
finished. total time: 0.518s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97407 KB)...
OKAY [ 2.885s]
writing 'modem_a'...
OKAY [ 1.040s]
finished. total time: 3.929s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.173s]
writing 'fsg_a'...
OKAY [ 0.067s]
finished. total time: 0.247s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.006s]
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bluetooth BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.055s]
finished. total time: 0.199s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.487s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.646s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.111s]
writing 'logo_a'...
OKAY [ 0.042s]
finished. total time: 0.157s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23345 KB)...
OKAY [ 0.693s]
writing 'boot_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.878s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.095s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 15.404s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.449s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.299s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.342s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.112s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.163s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 15.335s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.386s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (413387 KB)...
OKAY [ 12.137s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.182s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system_b system_b.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.059s]
writing 'system_b'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.106s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system_b system_b.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (319601 KB)...
OKAY [ 9.336s]
writing 'system_b'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.377s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (163069 KB)...
OKAY [ 4.820s]
writing 'oem_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.862s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.765s]
finished. total time: 0.771s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase ddr
erasing 'ddr'...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
I can't install the TWRP
I currently have the OPXS version 27.109-34-21 With this firmware it worked fine, but not now.
Beforehand
Thank you!!

You flashed pie, you can't go back to oreo, so you have to flash pie again. Since you have no baseband or imei, you must have flashed the wrong variant. Who is your provider, what was your software channel originally? What is the package name of the OREO firmware that worked for you in the past. This information will help determine what you need to flash in order to repair. Why is everyone obsessed with locking the bootloader? When you lock your bootloader, you dramatically reduce the options and tools available to fix your phone when things go wrong.

XDA Developers The BEST!!!
41rw4lk said:
You flashed pie, you can't go back to oreo, so you have to flash pie again. Since you have no baseband or imei, you must have flashed the wrong variant. Who is your provider, what was your software channel originally? What is the package name of the OREO firmware that worked for you in the past. This information will help determine what you need to flash in order to repair. Why is everyone obsessed with locking the bootloader? When you lock your bootloader, you dramatically reduce the options and tools available to fix your phone when things go wrong.
Click to expand...
Click to collapse
41rw4lk
* 41rw4lk
* 41rw4lk
You're the best!!!!!
Thank you!!!! IT WORKED!!!
Thanks for your support!!!!!!
I have IME, Baseband, all normal.
I got an update to PIE is the collection no. PPX29-159-23
I DIDN'T download it.
If I can download it?
regards

If everything is working normally, and you received an ota notification to update, then you should be able to update just fine. If it's some random firmware you came across, I wouldn't.

Pie
Hi good day.
I can't update Android Pie.
Tells me
Incorrect software update
My channel is OPMX.
The phone is company free
What I did was install the NASH RETAIL OPXS27 109 34 21 Firmware, this is what I had.
Then by fastboot install the NASH RETAIL PPX29 159 23 update.
But it is not updated, what can I do.
Recover the IMEI baseband and the phone works well.

lalo74 said:
Hi good day.
I can't update Android Pie.
Tells me
Incorrect software update
My channel is OPMX.
The phone is company free
What I did was install the NASH RETAIL OPXS27 109 34 21 Firmware, this is what I had.
Then by fastboot install the NASH RETAIL PPX29 159 23 update.
But it is not updated, what can I do.
Recover the IMEI baseband and the phone works well.
Click to expand...
Click to collapse
So just to confirm, everything is working on Retail pie right now yes?
Originally, you were on OpenMX firmware, and your software channel was/and is still OPMX yes?
Can you take a screenshot of the update being offered? OpenMX doesn't have pie yet, so if that is the update being offered then it will fail because you're on Retail firmware. So If you want to go back to OpenMX then we need to do a few things and it has to be a pie update being offered. Otherwise, you can update using any new Retail releases. Not Retin, Rebr, etc. Just plain Retail and you have the latest right now.

Pie
Hello
Thanks for your prompt response
It is currently in the openmix channel.
Before I was on the openmix channel the same.
The firmware was RETAIL.
So it was before the bootloader and flash unlock.
Now he is working fine without problems with
Openmix
NASH RETAIL Opxs27 109 34 21
I attach images
Can you help me please upgrade to Pie.

Photo
Good afternoon 41rw4lk
Look how is my phone
The firmware you download is this
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml[IMG
https://ibb.co/7XM0t5Z
https://ibb.co/PC5dVs6

Good afternoon 41rw4lk
Look how is my phone
The firmware you download is this
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
nash/official/RETAIL/NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but it was not installed
What is the correct procedure to update again and what are the commands for the firmware through minimal ADB Fastboot tool
https://ibb.co/v1Jx5Mq
https://ibb.co/q7P5spt
https://ibb.co/34ZFnWZ
https://ibb.co/KmcGKY0
https://ibb.co/vjx9rwR

firmware
Do I install this version?
NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Hold on, we need to check a couple of things because I'm confused.
In your OP you mentioned pie upgrade, did you ever upgrade to pie at all? The reason I ask is because in your photo you're running oreo, which would leave you without a baseband if you upgraded to pie modems.
Long story short, if everything is working (mobile data, wifi, bluetooth) etc. Then you should enable oem unlocking and adb debugging and unlock your bootloader again if you haven't already. An unlocked bootloader won't stop otas, it just gives you more options to flash and fix your phone, plus if you want twrp and/or root you'll need to be unlocked.
This is the firmware you flashed to get oreo running on your phone currently right? NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Option A - If you flashed that Retail firmware and all is well. I would flash this firmware to upgrade to pie. You won't be able to take otas since your channel is OPMX, but you will have pie without any bloat.
Option B - As of now, there is no OpenMX pie firmware on lolinet, but it looks like that's the update being offered since you have OPMX as your software channel and from the photo you posted. So if you want proper OpenMX and the ability to take otas, you'll need to flash back to an OpenMX firmware then take your ota.
I would unlock your bootloader before anything, that way if anything goes wrong you have options. Don't flash any pie firmware until you know what you need. If you are unsure, ask questions. Pie isn't the friendliest firmware to flash and will cause problems if you flash the wrong variant.

Command
Good night 41rw4lk
The problem I think are the commands
First
I had this firmware NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml OK installed.
What I did was unlock the bootloader, with the steps of a YouTube video https://www.youtube.com/watch?v=cXxr-Y1ozSY
Then I updated Pie with this firmware Moto/nash/official/RETAIL/NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It did not work. Back to the firmware of OREO OPXS27 109 34 21, this is where I no longer had the bace band NO IME no Wifi etc.
I was researching for a week ... but nothing worked. The OEM key did not respond, now it responds. I had the pleasure and miracle of meeting you and you tell me:
Go back to the firmware you had.
I do it and then upgrade to PIE PPX29 159 23 and it doesn't work.
Then I turn on the cell phone with OREO OPXS27 109 34 21 and IF the IMEI works the baseband and the Wifi.
Through OTA I get the update message, which is not installed.
Errors The commands I use to flash the firmware.
Now I am watching a YouTube video where they explain how to use the correct commands for each Firmware. What do you think?
The bad thing is that it is in Spanish
https://www.youtube.com/watch?v=a5PwF-qlAVc
What are the correct commands to update the firmware?
I will not flash until I agree with you.
Regards!!

I feel like we're going around in circles lol.
Does your phone work correctly right now? Does it have mobile signal and data, wifi, bluetooth etc?
If it does, what is the full name of the firmware you used to put it in working order?

41rw4lk said:
I feel like we're going around in circles lol.
Does your phone work correctly right now? Does it have mobile signal and data, wifi, bluetooth etc?
If it does, what is the full name of the firmware you used to put it in working order?
Click to expand...
Click to collapse
Hi good day
That's how the phone is working well; It has Wifi signal, IME, base band works 100%.
The firmware I am with now is:
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
To flash, subject to your opinion I have this procedure:
Phone
Activate Android programmer
Activate OEM
Enable USB debugging
Activate flash mode Moto Z2 (volume - and power button)
Computer:
ADB minimal tool v1.43
In the adb folder install the fimware and extract rar files.
NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
In the cmd window write
flashboot deivices
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash 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 system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
As time?
How about?
Regards!!

This is your current firmware right? NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
But when you flash NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip you lose baseband and imei?
If your bootloader isn't unlocked, I would unlock it so that you have some wiggle room if something goes wrong. With a locked bootloader you can only flash official signed, same version or higher, and that's not guaranteed.
As far as your flashing commands, it is best to use the preparation.bat from this thread to generate your own flashall for the firmware you have. Since we have different variants if you're not careful a flashall that you pickup around here might not flash everything you need to flash. So generate your own to be certain.

hello friends, i have a problem, i have a z2 force, with android 8.0.0, retbr software channel, security patch from january 1, 2018, installed version number is opxs27.109-34-4.
In fastboot mode I have baseband not found, I have BL: MBM-3.0-nash_retail-641a15b-180105, in product and variant I have: Nash radio2 64GB PVT and lastly I have Flashing_locked, can anyone help me with which firmware I can try to recover the cell phone ?

Stucked In BootLoop, tried a lot of things

Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.

welitonxdd said:
Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.
Click to expand...
Click to collapse
Does it give any error, when flashing the stock Oreo. Like permission denied for erase user data or any other?

welitonxdd said:
Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.
Click to expand...
Click to collapse
In fastboot mode type the following
fastboot erase userdata
This is the equivalent of doing a factory reset - all data will be erased including anything on internal storage
Without a full hardware/software diagnosis of your phone there really isn't anything else to suggest

riyan65 said:
Does it give any error, when flashing the stock Oreo. Like permission denied for erase user data or any other?
Click to expand...
Click to collapse
No error, give me success, but nothing happens
TheFixItMan said:
In fastboot mode type the following
fastboot erase userdata
This is the equivalent of doing a factory reset - all data will be erased including anything on internal storage
Without a full hardware/software diagnosis of your phone there really isn't anything else to suggest
Click to expand...
Click to collapse
i made this but nothing happens, i have no idea what to do now see video
youtube
watch?v=4apyEzljmjA

welitonxdd said:
No error, give me success, but nothing happens
i made this but nothing happens, i have no idea what to do now see video
youtube
watch?v=4apyEzljmjA
Click to expand...
Click to collapse
It looks like you have no rom installed either due to flashing wrong firmware or incomplete flashing or you have a hardware fault
Download firmware from below - make sure it's the same android version as you currently have eg android 7 or 8
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Commands to use
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Post output - note if you get security downgrade error flashing gpt or bootloader the firmware is too old
If you get permission denied try a different firmware as your device does not have an unlocked bootloader you can't flash unsigned firmware parts

TheFixItMan said:
Post output - note if you get security downgrade error flashing gpt or bootloader the firmware is too old
If you get permission denied try a different firmware as your device does not have an unlocked bootloader you can't flash unsigned firmware parts
Click to expand...
Click to collapse
before I had done it this way, without success too, now that I tried again this option of "is logical not found" appears, but even with this option it seems that the command has tried several firmwares but the one that does not give the mentioned error is last one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D:\adbmoto>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.171s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.091s]
Finished. Total time: 0.286s
D:\adbmoto>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.499s]
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.555s]
Finished. Total time: 1.075s
D:\adbmoto>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.478s]
Writing 'logo' OKAY [ 0.100s]
Finished. Total time: 0.608s
D:\adbmoto>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 1.710s]
Writing 'boot' OKAY [ 0.430s]
Finished. Total time: 2.177s
D:\adbmoto>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 1.316s]
Writing 'recovery' OKAY [ 0.441s]
Finished. Total time: 1.779s
D:\adbmoto>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 1.477s]
Writing 'dsp' OKAY [ 0.282s]
Finished. Total time: 1.803s
D:\adbmoto>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.891s]
Writing 'oem' OKAY [ 7.660s]
Finished. Total time: 21.190s
D:\adbmoto>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (258344 KB) OKAY [ 8.377s]
Writing 'system' OKAY [ 5.902s]
Finished. Total time: 17.582s
D:\adbmoto>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256570 KB) OKAY [ 8.307s]
Writing 'system' OKAY [ 5.519s]
Finished. Total time: 17.536s
D:\adbmoto>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (246510 KB) OKAY [ 8.012s]
Writing 'system' OKAY [ 6.545s]
Finished. Total time: 19.623s
D:\adbmoto>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 8.472s]
Writing 'system' OKAY [ 7.533s]
Finished. Total time: 19.463s
D:\adbmoto>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (261322 KB) OKAY [ 8.451s]
Writing 'system' OKAY [ 11.216s]
Finished. Total time: 24.197s
D:\adbmoto>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 8.481s]
Writing 'system' OKAY [ 5.513s]
Finished. Total time: 17.029s
D:\adbmoto>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (262143 KB) OKAY [ 8.489s]
Writing 'system' OKAY [ 6.678s]
Finished. Total time: 19.322s
D:\adbmoto>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (256817 KB) OKAY [ 8.302s]
Writing 'system' OKAY [ 6.812s]
Finished. Total time: 20.305s
D:\adbmoto>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (237909 KB) OKAY [ 7.713s]
Writing 'system' OKAY [ 7.424s]
Finished. Total time: 18.200s
D:\adbmoto>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66358 KB) OKAY [ 2.278s]
Writing 'modem' OKAY [ 1.050s]
Finished. Total time: 5.473s
D:\adbmoto>fastboot erase modemst1
Erasing 'modemst1' OKAY [ 0.035s]
Finished. Total time: 0.041s
D:\adbmoto>fastboot erase modemst2
Erasing 'modemst2' OKAY [ 0.036s]
Finished. Total time: 0.041s
D:\adbmoto>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.440s]
Writing 'fsg' OKAY [ 0.119s]
Finished. Total time: 0.589s
D:\adbmoto>fastboot erase cache
Erasing 'cache' OKAY [ 0.009s]
Finished. Total time: 0.014s
D:\adbmoto>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.176s]
Finished. Total time: 0.183s
D:\adbmoto>fastboot oem fb_mode_clear
OKAY [ 0.002s]
Finished. Total time: 0.004s
D:\adbmoto>fastboot reboot
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s
D:\adbmoto>
Click to expand...
Click to collapse

welitonxdd said:
before I had done it this way, without success too, now that I tried again this option of "is logical not found" appears, but even with this option it seems that the command has tried several firmwares but the one that does not give the mentioned error is last one
Click to expand...
Click to collapse
There's no errors in the output and everything is normal
Although unlikely to be causing an issue remove any sdcard and sim card from the device & try to boot
If it's still not booting after you have left it trying to boot for a while you may have a hardware fault
There's not really anything I can suggest - you can try using a different fastboot
Try using the mfastboot in the attachment below
Copy firmware to same directory as mfastboot
The commands are the same as above but instead of typing fastboot before each command type mfastboot

TheFixItMan said:
There's no errors in the output and everything is normal
Although unlikely to be causing an issue remove any sdcard and sim card from the device & try to boot
If it's still not booting after you have left it trying to boot for a while you may have a hardware fault
There's not really anything I can suggest - you can try using a different fastboot - I'll upload it in a min
Click to expand...
Click to collapse
the procediments was made without SIM and SD cards. i think the only answers now is the hardware fault.
thanks for your attention. and response in my topic.

welitonxdd said:
the procediments was made without SIM and SD cards. i think the only answers now is the hardware fault.
thanks for your attention. and response in my topic.
Click to expand...
Click to collapse
Try with the mfastboot I just posted in post above just incase the version you're using has issues - just substitute fastboot for mfastboot in the commands

TheFixItMan said:
Try with the mfastboot I just posted in post above just incase the version you're using has issues - just substitute fastboot for mfastboot in the commands
Click to expand...
Click to collapse
I finished now, the last hope was this, I did the procedure and it was the same way, after resetting it stays in the loop

welitonxdd said:
I finished now, the last hope was this, I did the procedure and it was the same way, after resetting it stays in the loop
Click to expand...
Click to collapse
Assuming you have tried the generic retail firmware there's not really anything else I can suggest
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

TheFixItMan said:
Assuming you have tried the generic retail firmware there's not really anything else I can suggest
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Yeah, already made with this firmware, the only accepted.
Strange is dont pass into recovery mode after fastboot screen. hardware fault sucks...
Another information is in Lenovo Smart Assistant continues showing RETBR, ive flashed only retail original

MOTO G8 ENTERING THE FASTBOOT SCREEN AND DOES NOT START

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