Develop Bugs

fastboot flash partition gpt.bin FAILED (remote failure)

can anyone help me with the following error and hot to fix it?
i have a moto z2 play
HTML:
PS C:\adb> fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.023s]
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.122s
PS C:\adb>

here is getvar ouput if it helps
HTML:
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.82
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: ##
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: D0408C7400000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: ##
(bootloader) meid:
(bootloader) date: 06-19-2017
(bootloader) sku: XT1710-01
(bootloader) battid: SNN5985A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:33:51 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:8.0.0/OPS27.7
(bootloader) ro.build.fingerprint[1]: 6-12-25/26:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.26.albus.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8953P_41.50.07.63R ALBUS_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g554d879 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Apr 4 07:30:46 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC1.82-0-g3523998
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=fbd9875-dirty
(bootloader) devcfg.git: git=fbd9875-dirty
(bootloader) keymaster.git: git=fbd9875-dirty
(bootloader) cmnlib.git: git=fbd9875-dirty
(bootloader) cmnlib64.git: git=fbd9875-dirty
(bootloader) prov.git: git=fbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC1.82-0-g345bd7e
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: bwaca
all: listed above
finished. total time: 0.190s
PS C:\adb>

HTML:
BUILD REQUEST INFO:
SW Version: albus-user 8.0.0 OPSS27.76-12-25-3 4 release-keysM8953P_41.50.07.63R
MBM Version: C0.CD
Modem Version: M8953P_41.50.07.63R
FSG Version: FSG-8953-08.120
Build Fingerprint: motorola/albus/albus:8.0.0/OPSS27.76-12-25-3/4:user/release-keys
CQATest App Version: 6.0.3
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 27.201.4.albus.retail.en.US
Model Number: Moto Z2 Play
Android Version: 8.0.0
Baseband Version: M8953P_41.50.07.63R
Build Id: OPSS27.76-12-25-3
SW Display Build ID: OPSS27.76-12-25-3
Build Date: Fri May 25 03:01:39 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.27.201.4.albus.retail.en.US
Version when read from CPV: albus-user 8.0.0 OPSS27.76-12-25-3 4 release-keys
AB Update Enabled: False
Full Treble Enabled: False

i have twrp can i recover somehow using this tool ?

I have the same problem
I have The Same Problem....
C:\mfastboot>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.031s]
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.094s

Looks like you try to flash an older bootloader version (Security version downgrade). Even though I thought that it would just flash and make problems on next OTA, but it looks like Android downgrade protection refuses the installation

nflnetwork29 said:
i have twrp can i recover somehow using this tool ?
Click to expand...
Click to collapse
Try to restore a nanobackup.
---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------
DeeThou said:
I have The Same Problem....
C:\mfastboot>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.031s]
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.094s
Click to expand...
Click to collapse
I don't know it success or not, but u can try to restore a nanobackup.

Mark2014 said:
I don't know it success or not, but u can try to restore a nanobackup.
Click to expand...
Click to collapse
Is there any step by step to restore nand backup?

At first, u need nanobackup files, and than use TWRP to restore.
---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------
DeeThou said:
Is there any step by step to restore nand backup?
Click to expand...
Click to collapse
At first, u need nanobackup files, and than use TWRP to restore.

Mark2014 said:
At first, u need nanobackup files, and than use TWRP to restore.
Click to expand...
Click to collapse
The thing is i cannot boo into recovery mode

DeeThou said:
The thing is i cannot boo into recovery mode
Click to expand...
Click to collapse
fastboot devices
Does above command work or not?
If it work, try:
fastboot boot recovery twrp.img
To boot into recovery mode

Mark2014 said:
fastboot devices
Does above command work or not?
If it work, try:
fastboot boot recovery twrp.img
To boot into recovery mode
Click to expand...
Click to collapse
Fastboot devices work.... My phone serial showed whenever i use that command.
I aready tried that command, to boot into all kind of twrp, even the stock recovery.img. They always stuck in the logo whenever i use the command to boot the recovery.

DeeThou said:
Fastboot devices work.... My phone serial showed whenever i use that command.
I aready tried that command, to boot into all kind of twrp, even the stock recovery.img. They always stuck in the logo whenever i use the command to boot the recovery.
Click to expand...
Click to collapse
Did you tried to flash it ("flash" not "boot") ? and with 32bit and 64bit of TWRP's version ?

Mark2014 said:
Did you tried to flash it ("flash" not "boot") ? and with 32bit and 64bit of TWRP's version ?
Click to expand...
Click to collapse
Yes, i already fastboot flash recovery all the twrp (32, 64, treble, everything on the net) and stock recovery image before i tried to fastboot boot recovery.
As i looked over the internet my problem caused by the EMMC failure, so now i am going to put it in the service center, which is very hard to find in my area.

DeeThou said:
Yes, i already fastboot flash recovery all the twrp (32, 64, treble, everything on the net) and stock recovery image before i tried to fastboot boot recovery.
As i looked over the internet my problem caused by the EMMC failure, so now i am going to put it in the service center, which is very hard to find in my area.
Click to expand...
Click to collapse
Did your TWRP boot into this step? Or just hang on the logo?
{
"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"
}

Mark2014 said:
Did your TWRP boot into this step? Or just hang on the logo?
Click to expand...
Click to collapse
Only on the Moto Logo...

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.

Bought a bricked XT1789-06 for cheap

Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3773
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 3
all: listed above
finished. total time: 0.172s
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_SS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot boot twrp-3.2.3-2-nash.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 30.773s
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny

bennyschw said:
Good morning,
I bougth a X1789-06 for cheap on ebay and thought I can fix it. But its harder then I expected.
The system doesn't start at all, except fot the bootloader. I'm able to run fastboot but I can't do much there because it's locked. ADB is not avavailable.
Here is my fastboot getvar all:
I tried to do fastboot boot boot.img with the rom thats in "ro.build.fingerprint" but it doesn't boot. Neither does TWRP.
The result at booting into TWRP looks like that:
LMSA also doesnt work. It says "Flash failed. Please try again".
Do you have any ideas how to get out of this and get something runnung again?
Thanks
Benny
Click to expand...
Click to collapse
Looks like getvar all says Retail
But you are flashing Reteu?
Try
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
Sent from my mata using XDA Labs

Goot moring,
tried to flash this version with the flashall tool, same result.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ -0.000s]
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.222s]
finished. total time: 0.222s
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.240s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.302s
Those lines above are the first ones with the flashall tool. Flash permission is always denied so nothing changes.
When I try to boot via fastboot boot boot.img the Motorola Logo appears for 30 secounds and then goes to fastboot again.
The problem is, that flasing is locked and I need to unlock it somehow. But its not possible without some Android system running because I have to activate it in the developer options.
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
I dont know witch strange things happend to this poor phone.
But thank you for your reply.
Benny

Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...

enetec said:
Since of locked status you can't change bootloader at moment. So don't try to flash an OS version different from actual bootloader (Nougat?)
Flash an OS version "compatible" with boot loader (don't try to flash bootloader!!), boot to system, switch to unlockable status, unlock it and... enjoy!
Remember anyway thay since you have fastboot access it isn't still hardbricked at all...
Click to expand...
Click to collapse
What makes me suspicious is that it says "RETAIL" in the fingerprint but I have the German/Europe version. So it should be "RETEU".
Anyway, tried to flash the 7.1.1 retail stock rom because theres no reteu 7.1.1 available but the result is still the same: "Permission denied". But it was worth a try!
"Fastboot boot boot.img" doesn't work either. Bootscreen appears for a while, it vibrates and then goes back to fastboot.

I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Try flash this one https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

berka38 said:
I have a European z2 and it's retail version.
When it bootloop I flashed wrong firmware retu. Had the ADB debug not available and bootloader locked.
Then power and volume down I read the right version and downloaded the ROM and flashed it whit error but it worked.
Click to expand...
Click to collapse
How do I know whats the right version for my bootloader? Just by trial and error?
Ist there a list somewhere?
But yes, there is some hope rising inside me
EDIT:
I tried the rom you suggested already. It dowsn't work. Same error as always: Permission denied.

I got to check how I find my info what was on it later but it also gave me error when flashed but It booted

berka38 said:
I got to check how I find my info what was on it later but it also gave me error when flashed but It booted
Click to expand...
Click to collapse
Nope, tried it again. While flashing there are those known permission denied errors. When it should boot the "device is corrupt" screen shows up and it shuts down after a while.
But the slots changed somehow:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565180808xxxxxx
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3760
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(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.274s
EDIT:
Uh, I noticed that the bootloader has also changed. Don't know whats happening here.
EDIT 2:
Is there a way to "hardbrick" the phone on purpose to do a blankflash?

bennyschw said:
Nope, tried it again. While flashing there are those known permission denied errors. ...<CUT>
Click to expand...
Click to collapse
Since what you posted you have an Oreo Reteu flashed on this phone. More, it is reported verity off and warranty void, so your bootloader should be unlocked.
My suspect is that someone has flashed it with Oreo THEN tried to relock bootloader and... bricked it! :silly:
Anyway, i don't know bootloader versions, but if this has been already flashed with Oreo, I don't think you will be able to reflash it with Nougat easily...
So, I would try this way...
- try to oem unlock it and look what it says...
- try to flash it with Oreo RETEU or Oreo Retail and look what happens...
What is weird is that "flashing locked" status...

You should try the lmsa tool first, see if it will do a rescue and get you back to booting.
https://support.lenovo.com/us/en/downloads/ds101291
If no go, then you can try a blankflash. It's possible that between all the flashing there have become discrepancies in the boot chain, and a blankflash will fix that. Afterwards you flash the correct firmware for your phone. You have an -06 Dual Sim right? So you'll probably want reteu ds firmware, but retail should also work. Either way it should boot, the only problem could be no modem. If that's the case, then factory reset from the recovery to see if that sorts it. If not, then flash the retail firmware and do a factory reset from the recovery, modem should be back.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
I would stay away from pie firmware until you're up and running. Just for verification it does say xt1789-06 by the charging port right? Does it have a dual sim try as well? Your priority should be, getting booting, sign into google, oem unlock. Once your bootloader is unlocked you'll have wiggle room, until then it'll be a little tough going.

Goot morning,
LSMA failes. It says "Fastboot flash single partition - Flash failes. Please try again.
When I do the oem unlock the phone replies:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RXNDLVGJRXZ65Y62EZUE
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.006s]
finished. total time: 0.007s
Now I just tried to flash the boot.img of RETEU:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.541s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.547s
And RETAIL:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.538s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.544s
In my first post I was trying to flash the single sim version. Was my fault. But the same things happend there. This is a XT1789-06 with dual sim.
But as you said, it should have booted with no mobile connection.
By the way, fastboot oem blankflash doesnt work either:
Code:
C:\Users\Schwe\Downloads\NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Is there another way to go to blankflash?
I also tired the edl cable method. But it went right into bootloader.
Right now I'm setting up my old laptop with only USB 2 ports. Maybe theres a difference. I'll keep you up to date.
Thank you for your effort!
Benny

This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.

41rw4lk said:
This is the last retail oreo firmware, it appears to be newer than what you've tried or at least what has been shown from your getvar output.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Before you try and flash it, run getvar command again and note your build version, build fingerprint, and which slot is your current slot . Then try to flash the retail firmware and boot. If nothing seems to change run the getvar command again and see if there are any changes to what you noted before. If your current slot is different, run the flashall again. If the current slot is the same, then fastboot --set-active=other and faatboot reboot bootloader. Run getvar command again to verify that you're on the other slot, and note the items listed above. Then run your flashall again. Run getvar command one more time and note the items again.
Hopefully enough of that will flash so you can boot. Between what you've flashed and god knows what was flashed before you, there could be a hodge-podge of nonsense scattered between the slots.
If still no boot, try running the lmsa tool again, maybe enough was cleaned up for the tool to run. Make sure that you're using admin privileges for the tool and command prompt if needed.
*Note - oem unlock won't work until you've enabled oem unlocking in dev settings, which is why booting is your 1st priority.
Click to expand...
Click to collapse
Absolutely nothing has changed except the battery voltage
Tried all the different retail and reteu 8.0 versions but there changes nothing. I also tried to boot the roms via boot boot.img but no one worked.
LSMA replies with the same error as before.
Cant even change the slots manually:
Code:
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=other
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\Schwe\Downloads\XT1789-06_NASH_RETEU_DS_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot --set-active=b
Setting current slot to 'b'...
FAILED (remote failure)
finished. total time: 0.006s
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny

adb-fastboot_ver29.0.5
Attached is the latest adb/fastboot files pulled from androidsdk. It's weird that you can't even switch slots, so here is the latest files, just unzip to their own folder. Open folder, hold shift then right-click a blank area in the folder, open command window here. Try repeating the instructions in my last post and see if anything works this time around, use a 2.0 port if possible and use a port off the motherboard. Trivial it seems, but necessary for some. Double check the command fastboot --setactive="a,b, or other" could be "_a or _b" I don't use that command often so the syntax could be wrong, so try with or with the underscore_ or simply use 'other' w/o 'quotes' to switch slots. We're trying to get the slots as matched as possible so that if all else fails hopefully the lmsa tool will at least do a rescue on it. Right now I think you have bits and pieces of everything and lmsa sees it as something foreign or custom and won't touch it.

bennyschw said:
I think I bought this phone: https://forum.xda-developers.com/z2-force/help/bricking-support-questions-xt1789-06-t3995049
:silly:
Anyway, my hope is not gone!
Thank you
Benny
Click to expand...
Click to collapse
I thought you were being funny until I looked at the serial no. in both posts... it the same f'n phone. Flashed to pie, f'd up, rolled back to oreo, bootloader locked, all kinds of wrong. Since it was on pie before, you'll need pie to fix it. Depending on what version of pie was flashed, you might need to wait for an update to roll out so you have a new enough firmware to overwrite the nv values. So there's that.

Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny

bennyschw said:
Well, that how it is now. I'll let it sit for a while, maybe sonething changes or I have some new ideas
But I'm happy about every new suggestions from you.
Thanks for your help!
Benny
Click to expand...
Click to collapse
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots

danyfenton said:
Did you succeed benny?
I'm practically having the same problem.
but when I try to change the slot with the command "fastboot --set-active = b"
the error appears: fastboot: error: Device does not support slots
Click to expand...
Click to collapse
The same situation here, I am stuck in the bootloader because it indicates "Flashing_lock", I cannot enter the operating system to unlock because it says that the device is corrupt, I cannot change the slot in Fastboot mode, I cannot flash a new ROM, Neither the same ROM or the old ROM ... What do you think about forcing the EDL state, to try to recover with blankflash? (If I already tried the blankflash commands and do not allow them in the Fastboot, I would have to damage the cell phone on purpose but I don't know how)

and you haven't achieved anything yet have you?
mine is still standing here.

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!

XT1922-2 JETER softbricked (newbie)

Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.

Here's all the variables if that's helpful:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-aljeter_retail-b1f322d35c1-2
(bootloader) version-bootloader[1]: 00404
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZL4223V3D5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 3572CA9F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 08-29-2018
(bootloader) sku: XT1922-2
(bootloader) carrier_sku: XT1922-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 5 11:34:57 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter_n/aljeter_n:9/PPP
(bootloader) ro.build.fingerprint[1]: S29.55-35-18-7/6a0d0:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.7.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: M8937_34.42.05.98R JETER_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g3e480e17e11
(bootloader) kernel.version[1]: f-04280-g407726838ebf ([email protected]
(bootloader) kernel.version[2]: 8) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Sat Apr 4 12:
(bootloader) kernel.version[4]: 24:37 CDT 2020
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-0d2031d6b9-200404
(bootloader) rpm.git: MBM-2.1-aljeter_retail-af31f6ae-200404
(bootloader) tz.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) prov.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) aboot.git: MBM-2.1-aljeter_retail-b1f322d35c1-200404
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: eegb
(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.152s
Click to expand...
Click to collapse

xt123xt said:
Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.
Click to expand...
Click to collapse
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Ruben8ap said:
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
Click to expand...
Click to collapse
Thank you for your reply.
It gave me an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system aljeter.zip
target reported max download size of 535822336 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 411641469 is not a multiple of the block size 4096
sending sparse 'system' 1/3 (523260 KB)...
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
OKAY [ 17.139s]
writing 'system' 1/3...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.145s
Click to expand...
Click to collapse

Try these https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETEU/

I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.

xt123xt said:
I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.
Click to expand...
Click to collapse
Download this file --> https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Then you open the CMD and put in fastboot devices and the phone code should appear, of course the phone should already be in fastboot mode for that moment.
If everything is in order you should copy these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Just select all then copy and paste them into the CMD and the stock installation process will start :fingers-crossed:

I suppose you've saved my phone. Thank you very much!

Hi, I carried out the instruction as given above by Ruben8ap, on my XT1922-2 Aljeter Moto G6 Play phone, and have recovered my phone, so I can boot into the OS, but I have lost access to Fastboot and TWRP, etc. So, I now have a phone that is stuck with this OS and no way of gaining root access or anything else. My bootloader says AP Fastboot Flash Mode (Secure). I cannot flash anything from the stock recovery on the SD card. Can anyone advise how I can get out of this state?