Develop Bugs

Recovering soft brick G5

Hi just on the off chance anyone see's this and can advise.
Family updated their G5 with OTA security update. OTA screwed the device (soft-brick can still access recovery and adb via pc), they reckon it's out of warranty so not worth taking in.
I'm following : https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897 to try to reinstate stock rom and revive the device. However, a little concerned that as the device is not user development mode enabled that i may hit hurdles (e.g. hard brick the bugger).
oem is marked as locked and i have a "fastboot flash mode (secure)" warning in bootloader. Is this going to mess with my plans?
Device is XT1675 (retail) which i understand is out of OTA so little confused as to why the initial error but am certain owner has not tampered in any way with the device. Before you ask, Motorola's solution was 'pay a repair guy'.

UPDATE:
Unsurprisingly, the instrs didn't work and i hit a hurdle. flashing boot resulted in an error "validation failed". Seems the error thinks that i'm trying to flash an old version... There doesn't appear to be a more recent G5 rom available so am i screwed?

deedb said:
Hi just on the off chance anyone see's this and can advise.
Family updated their G5 with OTA security update. OTA screwed the device (soft-brick can still access recovery and adb via pc), they reckon it's out of warranty so not worth taking in.
I'm following : https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897 to try to reinstate stock rom and revive the device. However, a little concerned that as the device is not user development mode enabled that i may hit hurdles (e.g. hard brick the bugger).
oem is marked as locked and i have a "fastboot flash mode (secure)" warning in bootloader. Is this going to mess with my plans?
Device is XT1675 (retail) which i understand is out of OTA so little confused as to why the initial error but am certain owner has not tampered in any way with the device. Before you ask, Motorola's solution was 'pay a repair guy'.
Click to expand...
Click to collapse
Run the "fastboot getvar all" command and paste the whole output into your reply (delete lines with a personal data such as IMEI and serial number first). According to it, I should be able to send you a link for a fastboot firmware that won't hardbrick your device (hardbrick occurs if older gpt and/or bootloader is flashed).
Btw, you can find the bootloader status (unlocked or not) in the bootloader menu. "Flashing unlocked" means it's unlocked, "oem_locked" means it isn't. However, it shouldn't matter as long as you flash the digitally signed stock firmware of the same or newer version (flashing an older one will immediately hardbrick your device, as I already wrote).

deedb said:
UPDATE:
Unsurprisingly, the instrs didn't work and i hit a hurdle. flashing boot resulted in an error "validation failed". Seems the error thinks that i'm trying to flash an old version... There doesn't appear to be a more recent G5 rom available so am i screwed?
Click to expand...
Click to collapse
Use lenovo Moto smart assistant app in pc and select recovery mode and it will flash the whole firmware.

Andrej_SK said:
Run the "fastboot getvar all" command and paste the whole output into your reply (delete lines with a personal data such as IMEI and serial number first). According to it, I should be able to send you a link for a fastboot firmware that won't hardbrick your device (hardbrick occurs if older gpt and/or bootloader is flashed).
Btw, you can find the bootloader status (unlocked or not) in the bootloader menu. "Flashing unlocked" means it's unlocked, "oem_locked" means it isn't. However, it shouldn't matter as long as you flash the digitally signed stock firmware of the same or newer version (flashing an older one will immediately hardbrick your device, as I already wrote).
Click to expand...
Click to collapse
Thanks for your reply and sorry for being so tardy with mine. bootloader is definitely locked "oem_locked".
getvar results as follows;
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=000000000
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=
(bootloader) cpu: MSM8937
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) date: 07-09-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 22:37: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.
(bootloader) ro.build.fingerprint[1]: 8.85-13-2/d04a4:user/rele
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.ce
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_22.29.02.69R CEDRIC_EMEA_C
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g339
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 13:5
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=26cc248
(bootloader) devcfg.git: git=26cc248
(bootloader) keymaster.git: git=26cc248
(bootloader) cmnlib.git: git=26cc248
(bootloader) cmnlib64.git: git=26cc248
(bootloader) prov.git: git=26cc248
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown

deedb said:
Thanks for your reply and sorry for being so tardy with mine. bootloader is definitely locked "oem_locked".
getvar results as follows;
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=000000000
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=
(bootloader) cpu: MSM8937
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) date: 07-09-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 22:37: 2 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.
(bootloader) ro.build.fingerprint[1]: 8.85-13-2/d04a4:user/rele
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.ce
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_22.29.02.69R CEDRIC_EMEA_C
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g339
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 13:5
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=26cc248
(bootloader) devcfg.git: git=26cc248
(bootloader) keymaster.git: git=26cc248
(bootloader) cmnlib.git: git=26cc248
(bootloader) cmnlib64.git: git=26cc248
(bootloader) prov.git: git=26cc248
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
Click to expand...
Click to collapse
Open this site https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/, download the firmware with "OPPS28.85-13-2" in the filename, extract the full content of the downloaded zip into the folder where's your adb/fastboot installed and flash it using the commands below. You can download the "OPPS28.85-13-4" firmware also, but "OPPS28.85-13-2" will be just enough to do not brick your phone (difference: 13-4 is firmware with december 2018 security patch while 13-2 is firmware with october 2018 security patch).
Commands to flash (data in the internal storage will be wiped):
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

Hello, can someone help me find a firmware that will remove the brick in my xt1671? My Getvar all result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31(*)
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2c35acf3
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: C0F87BA300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.063s
Thank you!

Maylo0292 said:
Hello, can someone help me find a firmware that will remove the brick in my xt1671? My Getvar all result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31(*)
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2c35acf3
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: C0F87BA300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.063s
Thank you!
Click to expand...
Click to collapse
There are some important lines such as "(bootloader)ro.build.fingerprint[0]" and "(bootloader)ro.build.fingerprint[1]" missing. It seems that your device was previously hardbricked and now, it is booted (into the fastboot) using the sdcard only, isn't it?

Maylo0292 said:
Hello, can someone help me find a firmware that will remove the brick in my xt1671? My Getvar all result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31(*)
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 2c35acf3
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: C0F87BA300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.063s
Thank you!
Click to expand...
Click to collapse
Here you can get the firmware. https://mirrors.lolinet.com/firmware/moto/cedric/official/
And remove serial no from getvar.

Andrej_SK said:
There are some important lines such as "(bootloader)ro.build.fingerprint[0]" and "(bootloader)ro.build.fingerprint[1]" missing. It seems that your device was previously hardbricked and now, it is booted (into the fastboot) using the sdcard only, isn't it?
Click to expand...
Click to collapse
Thanks for answering. Just turn on fastboot even without the SD Card, when trying to flash any firmware gives errors because the bootloader locked. Any suggestions?
---------- Post added at 06:19 PM ---------- Previous post was at 06:10 PM ----------

Maylo0292 said:
Thanks for answering. Just turn on fastboot even without the SD Card, when trying to flash any firmware gives errors because the bootloader locked. Any suggestions?
Click to expand...
Click to collapse
It doesn't matter that your bootloader is locked - you're flashing official firmware images via fastboot - that's what they are designed for
You are more likely flashing incorrect firmware or firmware that is too old
Without the error output who knows

TheFixItMan said:
It doesn't matter that your bootloader is locked - you're flashing official firmware images via fastboot - that's what they are designed for
You are more likely flashing incorrect firmware or firmware that is too old
Without the error output who knows
Click to expand...
Click to collapse
I have tried to install the latest firmware version from the RETAIL and several companies and I always get the following result in fastboot:
C:\Users\Escritorio\Downloads\Firmware>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.061s]
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.172s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 5.047s]
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 failure)
finished. total time: 5.291s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (2242 KB)...
OKAY [ 2.173s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 2.215s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 16.292s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.495s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16484 KB)...
OKAY [ 15.957s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.179s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash dsp adspso.bin
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 15.551s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 15.579s
C:\Users\Escritorio\Downloads\Firmware>fastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [141.870s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 141.946s

Maylo0292 said:
I have tried to install the latest firmware version from the RETAIL and several companies and I always get the following result in fastboot:
C:\Users\Escritorio\Downloads\Firmware>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.061s]
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.172s
...
Click to expand...
Click to collapse
That's why does it fail. You are trying to flash older firmware.
Try to flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (clicking the link will start the download. Source here https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/).

Maylo0292 said:
(bootloader) Security version downgrade
Click to expand...
Click to collapse
What the above post says - this error means the firmware you are trying to flash is too old
gpt and bootloader must be the same or newer than what is already on your device

Andrej_SK said:
That's why does it fail. You are trying to flash older firmware.
Try to flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (clicking the link will start the download. Source here https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/).
Click to expand...
Click to collapse
Thank you very much for answering. It's just the firmware that I downloaded and installed and which gives me that error that I mentioned. Do you know where I can get the most current?
---------- Post added at 11:15 PM ---------- Previous post was at 11:09 PM ----------
TheFixItMan said:
What the above post says - this error means the firmware you are trying to flash is too old
gpt and bootloader must be the same or newer than what is already on your device
Click to expand...
Click to collapse
Thank you very much for answering.
It's strange for me to get that error, I downloaded and installed the firmware CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Do you know which one I should install to fix it?

Maylo0292 said:
Thank you very much for answering.
It's strange for me to get that error, I downloaded and installed the firmware CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Do you know which one I should install to fix it?
Click to expand...
Click to collapse
I don't own this device
I suggest you download the most recent for your region
Eg
Retin = India
Retgb = United Kingdom
Reteu = Europe
You get the idea
Obviously if you flashed an ota from a different region you may have to use firmware from that region as it maybe newer than yours which is why you should never flash otas outside of the about phone section of your phone unless they come direct from the manufacturer and not via a 3rd party website

Maylo0292 said:
Thank you very much for answering. It's just the firmware that I downloaded and installed and which gives me that error that I mentioned. Do you know where I can get the most current?
---------- Post added at 11:15 PM ---------- Previous post was at 11:09 PM ----------
Thank you very much for answering.
It's strange for me to get that error, I downloaded and installed the firmware CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Do you know which one I should install to fix it?
Click to expand...
Click to collapse
That's weird, as you are always getting security downgrade error, but OPPS28.85-16-6 is the latest available official build for Moto G5 ever released by Lenovo (https://support.motorola.com/in/en/softwareupgrade). Are you sure that you are trying to flash the correct firmware?

Andrej_SK said:
That's weird, as you are always getting security downgrade error, but OPPS28.85-16-6 is the latest available official build for Moto G5 ever released by Lenovo (https://support.motorola.com/in/en/softwareupgrade). Are you sure that you are trying to flash the correct firmware?
Click to expand...
Click to collapse
I reinstalled the firmware PPS28.85-16-6 and it no longer gives the downgrade error but now the following comes out in the fastboot:
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
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 failure)
finished. total time: 0.065s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.197s]
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 failure)
finished. total time: 0.409s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.628s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.800s
Do you know why this is?
---------- Post added at 06:55 PM ---------- Previous post was at 06:51 PM ----------
TheFixItMan said:
I don't own this device
I suggest you download the most recent for your region
Eg
Retin = India
Retgb = United Kingdom
Reteu = Europe
You get the idea
Obviously if you flashed an ota from a different region you may have to use firmware from that region as it maybe newer than yours which is why you should never flash otas outside of the about phone section of your phone unless they come direct from the manufacturer and not via a 3rd party website
Click to expand...
Click to collapse
Thank you. I went back to flashing the firmware PPS28.85-16-6 that you suggested to me and now it gives the following in fastboot:
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
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 failure)
finished. total time: 0.065s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (5179 KB)...
OKAY [ 0.197s]
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 failure)
finished. total time: 0.409s
C:\Users\Escritorio\Downloads\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-D
EFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.628s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.800s
Do you know why this is?

Did you start the flashing process with
fastboot oem fb_mode_set
Then
fastboot flash gpt
fastboot flash bootloader
And so on
If so then probably same issue
If you have an sd card with the mmcblk0 image on it then you can test your device is working correctly
Flash everything from the latest firmware except gpt & bootloader
Restart the phone back to bootloader with the sd card in
Use volume keys to select the start normally option
Your phone should boot
If you want to boot the phone without the SD card you need to find firmware which will allow gpt and bootloader to flash

TheFixItMan said:
Did you start the flashing process with
fastboot oem fb_mode_set
Then
fastboot flash gpt
fastboot flash bootloader
And so on
If so then probably same issue
If you have an sd card with the mmcblk0 image on it then you can test your device is working correctly
Flash everything from the latest firmware except gpt & bootloader
Restart the phone back to bootloader with the sd card in
Use volume keys to select the start normally option
Your phone should boot
If you want to boot the phone without the SD card you need to find firmware which will allow gpt and bootloader to flash
Click to expand...
Click to collapse
I started flashing with those commands but I get the same results, I think it's a serious problem in the EMMC so I'll take it to support. Thank you very much for the help.

Moto G8 Play Stuck On Fastboot (No Bootable A/B Slot)

Sorry if I have some grammar errors, English is not my main language
OK so Recently I bought this phone from a friend thinking it was an easy fix by just flashing a rom but I couldn't find a way to make it work.
I've tried many way on how to fix, via LMSA and from ADB but got no luck.
The rom I use is the one who LMSA gave me:
LIMA_32_AMX_PMD29.70-81_subsidy-DEFAULT_regulatory-XT2015_2L_CFC
This is what the command ¨fastboot getvar all¨ trows at me:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-210600d2e-200306
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY326VQQK5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x08
(bootloader) uid: F60944C9BFC7792F000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) meid:
(bootloader) date: 10-28-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 12 2:10:26 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32_amx/lima:9/PMD29.
(bootloader) ro.build.fingerprint[1]: 70-81/cb27e:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.51.97.lima_32_amx
(bootloader) ro.build.version.full[1]: .amx.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.90R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 171) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Fri Mar 6 0
(bootloader) kernel.version[3]: 9:15:39 CST 2020
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: amxco
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C70228
And this is the ADB command that i use before
Code:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
I already tried to flash the boot.img using boot_a and boot_b
I hope that someone could help me, I would be very grateful

DoctorStrange007 said:
Hi Juan
Very simple to solve. In the bootloader with the side buttons go to find recovery, in recovery the droid will appear, hold the Power button and with it pressed press up on the volume and hit factory reset . If that doesn't work what I think is impossible ,because your bootloader is blocked only using midiatek's flash tool
Click to expand...
Click to collapse
Thanks for the fast response, but my phone goes back to the fastboot menu after attempting to get in the recovery.
Is there any way I can get my hands on a scatter file, I didn't find one online or where I can contact someone who is willing to help?

same problem
JuanChoF23 said:
Thanks for the fast response, but my phone goes back to the fastboot menu after attempting to get in the recovery.
Is there any way I can get my hands on a scatter file, I didn't find one online or where I can contact someone who is willing to help?
Click to expand...
Click to collapse
im also stuck on fastboot, tried to flash firmware but didnt work
EDIT: can someone help me find the apropiate rom/firmware for my device:
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-191003
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY326R9C9F
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 520DE472090CB2D5000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-04-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 10 21: 4:55 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMD29.70-7
(bootloader) ro.build.fingerprint[1]: 0/a51aa:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.51.85.lima_32.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.88R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 151) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Mon Nov 18
(bootloader) kernel.version[3]: 20:12:45 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C56212
all: listed above
finished. total time: 0.188s

youtube.com/watch?v=svtPdIVoloE

Moto Z2 Force T-Mobile branding -> flash to retail firmware won't work

Hi there,
I'm new to xda. Thanks for having me.
I am new to the whole topic of unlocking/flashing a mobile phone, since I did not see a real need for it until now.
What's the story:
I bought a new Motorola Moto Z2 Force (XT1789-04) on eBay. The phone was shipped from the US apparently (I live in Germany).
It has a T-Mobile branding pre-installed, which was not mentioned before and which I find terrible.
So I decided to flash the Z2 with a retail firmware to get rid of all those useless pre-installed apps.
I started reading a bit about how to do this. The first pages suggested to use RSD Lite with the latest motorola drivers and provided appropriate stock firmware.
I went into developers options on the phone, and allowed USB debugging. I started fastboot with "volume down" and power.
However, the phone is not recognized in RSD Lite. The list remains empty. I reinstalled the motorola driver multiple times, rebooting my Win10 PC as was suggested.
I also tried the universal ADB drivers. No change.
I then used the adb / fastboot cmd lines to check if something is amiss. And i found a couple of strange things:
Code:
fastboot getdev all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
[B](bootloader) secure: no[/B]
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: [XXXXXXXXXXX]
(bootloader) [B]cid: 0xDEAD[/B]
(bootloader) channelid: 0x00
(bootloader) uid: D7BF5C89
(bootloader) [B]securestate: engineering[/B]
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [XXXXXXXXXXX]
(bootloader) meid:
(bootloader) date: 01-23-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4272
(bootloader) iccid: 89148000003630606544
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NNS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:prov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.119s
I am unable to get unlock data.
Code:
fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
finished. total time: 0.003s
Code:
fastboot flashing get_unlock_ability
...
(bootloader) use get_unlock_bootloader_nonce and web portal
(bootloader) .....motorola.com/unlockbootloader
OKAY [ 0.004s]
finished. total time: 0.005s
In the phone setup I also noticed, that "unlock bootloader" is greyed out. It states, the bootloader would already be unlocked.
Now I tried the unlock cmd in fastboot, since it should state something like already unlocked, but instead I get this message:
Code:
fastboot oem unlock
...
(bootloader) Unsupported on engineering phone
OKAY [ 0.001s]
finished. total time: 0.002s
Now I found this quite confusing, but I tried to flash TWRP, in case this might resolve the problems with "engineering mode" without quite knowing what that really implies.
I downloaded the latest TWRP for nash (Z2 Force) and tried to flash it over fastboot:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (34224 KB)...
OKAY [ 0.081s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.085s
Now I am out of ideas.
Can anyone help me? Maybe start by explaining, why my phone doesn't just let me do the things I want...
Thanks!

12die4 said:
Hi there,
I'm new to xda. Thanks for having me.
I am new to the whole topic of unlocking/flashing a mobile phone, since I did not see a real need for it until now.
What's the story:
I bought a new Motorola Moto Z2 Force (XT1789-04) on eBay. The phone was shipped from the US apparently (I live in Germany).
It has a T-Mobile branding pre-installed, which was not mentioned before and which I find terrible.
So I decided to flash the Z2 with a retail firmware to get rid of all those useless pre-installed apps.
I started reading a bit about how to do this. The first pages suggested to use RSD Lite with the latest motorola drivers and provided appropriate stock firmware.
I went into developers options on the phone, and allowed USB debugging. I started fastboot with "volume down" and power.
However, the phone is not recognized in RSD Lite. The list remains empty. I reinstalled the motorola driver multiple times, rebooting my Win10 PC as was suggested.
I also tried the universal ADB drivers. No change.
I then used the adb / fastboot cmd lines to check if something is amiss. And i found a couple of strange things:
Code:
fastboot getdev all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
[B](bootloader) secure: no[/B]
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: [XXXXXXXXXXX]
(bootloader) [B]cid: 0xDEAD[/B]
(bootloader) channelid: 0x00
(bootloader) uid: D7BF5C89
(bootloader) [B]securestate: engineering[/B]
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [XXXXXXXXXXX]
(bootloader) meid:
(bootloader) date: 01-23-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4272
(bootloader) iccid: 89148000003630606544
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NNS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:prov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.119s
I am unable to get unlock data.
Code:
fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
finished. total time: 0.003s
Code:
fastboot flashing get_unlock_ability
...
(bootloader) use get_unlock_bootloader_nonce and web portal
(bootloader) .....motorola.com/unlockbootloader
OKAY [ 0.004s]
finished. total time: 0.005s
In the phone setup I also noticed, that "unlock bootloader" is greyed out. It states, the bootloader would already be unlocked.
Now I tried the unlock cmd in fastboot, since it should state something like already unlocked, but instead I get this message:
Code:
fastboot oem unlock
...
(bootloader) Unsupported on engineering phone
OKAY [ 0.001s]
finished. total time: 0.002s
Now I found this quite confusing, but I tried to flash TWRP, in case this might resolve the problems with "engineering mode" without quite knowing what that really implies.
I downloaded the latest TWRP for nash (Z2 Force) and tried to flash it over fastboot:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (34224 KB)...
OKAY [ 0.081s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.085s
Now I am out of ideas.
Can anyone help me? Maybe start by explaining, why my phone doesn't just let me do the things I want...
Thanks!
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi, the command reply is seen in the first code box.
Sorry, I mixed up the headlines. It's NOT "fastboot getdev all", but as you said "fastboot getvar all". My mistake. :cyclops:

12die4 said:
Hi, the command reply is seen in the first code box.
Sorry, I mixed up the headlines. It's NOT "fastboot getdev all", but as you said "fastboot getvar all". My mistake. :cyclops:
Click to expand...
Click to collapse
Does the device still boot normally?
Sent from my Moto E (4) using Tapatalk

Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)

41rw4lk said:
Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Correct getvar says securestate engineering
Sent from my perry_f using XDA Labs
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
If you get twrp installed, make a complete backup.
Engineering devices have unique firmware, I think.
It may not behave like a consumer model.
Sent from my perry_f using XDA Labs

41rw4lk said:
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Thank! I will try to do that. I understand that you can Boot a remote (PC located) Boot Image with this command? Flashing TWRP via fastboot didn't however. Not sure why.

41rw4lk said:
Looks like you have an engineering phone, bootloader should already be unlocked. I haven't had any experience with an engineering phone so I don't know the limitations... if any.
You can try to boot twrp, if your bootloader is unlocked it should boot.
fastboot boot (Drag N' Drop twrp.img here)
Click to expand...
Click to collapse
Great, fastboot boot twrp.img worked!
What do I do now? My idea was: Run "install" and try to flash the new Firmware via TWRP.
Therefore I need to copy the new img-file onto an sd-card and select it in TWRP as source. Right?
Or which procedure would you recommend?
sd_shadow said:
[/COLOR]If you get twrp installed, make a complete backup.
Engineering devices have unique firmware, I think.
It may not behave like a consumer model.
Click to expand...
Click to collapse
Thanks for the advice. I tried a backup with all boxes checked - there was a failure (error 255).
But when checking only firmware and bootloader, the backup worked fine.
Do I need the other options or are firmware and bootloader sufficient for my purposes? I'm not sure, what is actually overwritten when installing the stock firmware.

12die4 said:
Great, fastboot boot twrp.img worked!
What do I do now? My idea was: Run "install" and try to flash the new Firmware via TWRP.
Therefore I need to copy the new img-file onto an sd-card and select it in TWRP as source. Right?
Or which procedure would you recommend?
Thanks for the advice. I tried a backup with all boxes checked - there was a failure (error 255).
But when checking only firmware and bootloader, the backup worked fine.
Do I need the other options or are firmware and bootloader sufficient for my purposes? I'm not sure, what is actually overwritten when installing the stock firmware.
Click to expand...
Click to collapse
You want boot twrp, install twrp in booted twrp with a twrp.zip, then back up.
Sent from my ali using XDA Labs
---------- Post added at 05:02 AM ---------- Previous post was at 04:57 AM ----------
https://dl.twrp.me/nash/
Sent from my ali using XDA Labs

sd_shadow said:
You want boot twrp, install twrp in booted twrp with a twrp.zip, then back up.
Sent from my ali using XDA Labs
---------- Post added at 05:02 AM ---------- Previous post was at 04:57 AM ----------
https://dl.twrp.me/nash/
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hurra! Installing twrp worked now. Thanks!
How do I get to boot twrp now that it is installed locally? Do I still need to use the command "fastboot boot twrp.img" or is there a possibility without adb/fastboot protocol?
I was also able to create a backup of all partitions. I only deselected "Data (excl. storage)" in the options, since the phone was not actively used yet, so there shouldn't be any data that's relevant for backup.
Next I tried installing the new retail firmware ("NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"), but TWRP states the ZIP has an invalid file format.
Why is it not working? Is it an incorrect firmware after all?

12die4 said:
Hurra! Installing twrp worked now. Thanks!
How do I get to boot twrp now that it is installed locally? Do I still need to use the command "fastboot boot twrp.img" or is there a possibility without adb/fastboot protocol?
I was also able to create a backup of all partitions. I only deselected "Data (excl. storage)" in the options, since the phone was not actively used yet, so there shouldn't be any data that's relevant for backup.
Next I tried installing the new retail firmware ("NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"), but TWRP states the ZIP has an invalid file format.
Why is it not working? Is it an incorrect firmware after all?
Click to expand...
Click to collapse
You should be able to boot to twrp using bootloader recovery option.
Stock firmware is not twrp compatible.
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
You should be able to boot to twrp using bootloader recovery option.
Stock firmware is not twrp compatible.
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Ow, that sounds tricky. (tools that are no longer updated and might or might not work...)
For now, I tried to install LineageOS 17.1 on my Z2 Force.
Maybe there is no need to keep Retail Moto-Firmware after all...
However I have some issues with LineageOS. I will post them in the corresponding thread.
For now. Thanks a lot!

XT-1675 with locked bootloader [HELP]

Hi,
I have a cedric xt-1675 with locked bootloader (i have a key to unlock and i tried unlocking it through fastboot it says its disable) and when I try to load into recovery mode it gave me error
FAILED TO PASS VALIDATION. BACKUP TO FASTBOOT
BOOTUP FAILED
I tried flashing firmware through fastboot white doing mfastboot flash partition gpt.bin
C:\Users\Abdul Rafy\Desktop\New folder\ar\boot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.007s]
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...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.077s
all other flash commands works fine except mfastboot flash partition gpt.bin
Thanks

You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options

TheFixItMan said:
You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options
Click to expand...
Click to collapse
thanks for the reply, I never have unlocked my device before it has locked bootloader since start. anyway, I have tried "fastboot oem unlock UNLOCK_KEY" it says enable oem unlocking from developer option and the problem is i couldn't get into phone not even into recovery just fastboot. It used to get stuck at moto logo but now when I try to boot normally it says
Failed to verify hab image boot
failed to validate boot image
Error: Failed to pass validation. backup to fastboot
Boot up failed
and if I try to go into recovery, it says
Failed to verify hab image recovery
failed to validate recovery image
Error: Failed to pass validation. backup to fastboot
Boot up failed
another thing I did try Software repair assistant but it gave me error on 47%

Here the getvar just in case:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A4 FV=00000000000000A4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x4e
(bootloader) uid: 0295944600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Last time flashing failed
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 03-07-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 8: 2: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_46.42.02.75R CEDRIC_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tescogb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above

This is because the boot.img you flashed is not signed by Motorola and its failing to pass verification
If you were trying to unlock the bootloader you should have followed the correct process and enabled adb and oem unlock from the dev options
Never flash firmware on a locked bootloader - if it goes wrong you have no chance of correcting it
You basically have two options now
Try and find firmware that will flash fully on your device
Firmware can be found here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
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
Or take to a repair shop for either a motherboard replacement or if possible flashing with a jtag

Cedric XT-1676 firmware error:

ERROR: This package requires from an Android 8.1 stock ROM build.
Such a bug prevents me from updating the lineage-18.1-20220116-microG-cedric.zip image to a newer version,
e.g. lineage-18.1-20220301-microG-cedric.zip
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZYxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AADB0F5700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:17:47 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01u CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.061s
I installed the stock rom via fastboot from the image:
CEDRIC_OPPS28.85_13_6_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
using this commands:
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
Click to expand...
Click to collapse
I installed TWRP, wiped the / system partition, / data, / cache,
then I installed lineage-18.1-20220116-microG-cedric.zip + Magisk.
the system is working fine.
However, the update to lineage-18.1-20220301-microG-cedric.zip stops on a bug with the firmware version.
I download lineage images from here:
cedric
Cheers

Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com

TheFixItMan said:
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Click to expand...
Click to collapse
Thank you very much for that firmware link... I was ready to give up.
Oddly, the official Motorola Repair tool does not install a Lineage-friendly version of the stock firmware.
If it helps any other noob, I used this site to install the stock firmware:
Install Stock Firmware on Moto G5 via Fastboot Commands
In this comprehensive tutorial, we will show you how to install stock firmware on Motorola Moto G5 via Fastboot commands and unbrick it.
www.droidwin.com

Hi
I Installed via fastboot:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After this operation, my Cedric does not have a unique IMEI number.
As a result, the SIM card does not work at all, I can only make emergency calls.
fastboot getvar all 2>&1| grep -i imei
(bootloader) imei: 356476085352435
I tried to fix IMEI according to this thread:
Moto G5 Cedric - Repair Imei = 0
After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?
forum.xda-developers.com
I did several times (after installing stock ROM, after installing LineageOS, after installing LineageOS-microg):
fastboot erase modemst1; fastboot erase modemst2 ; fastboot erase cache
Erasing 'modemst1' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'modemst2' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'cache' OKAY [ 0.017s]
Finished. Total time: 0.020s
However, to no avail, the phone has no IMEI number on any SIM card.
It seems the XT1676 European version is more resistant to IMEI repair attempts.
Cheers

My IMEI was also zeroed by the stock ROM.
I tried using the recommendations in the following link, but I was ultimately unable to recover the IMEI from within the stock rom. Flashing LOS worked.
Moto g5 plus IMEI 0 after flashing anything? Read on!
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required! Prerequisites: U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on...
forum.xda-developers.com

Same here. Unable to recover IMEI for XT1676. The suggested procedure just does not work in this phone version with latest stock ROM OPP28.85-19-4-2.