[Moto Z2 Force  Questions & Answers] RaminJ:
[MENTION=3302201]41rw4lk[/MENTION], thanks for taking the time, I really appreciate that!

I really wonder why the label on the package says XT1789-04. The IMEI on said label is identical to the one read out in the device. However, XT1789-05 is stamped by the charging port.

From what I can tell (having checked all available variants on lolinet) the following ones have "XT1789-05*" in their names:

AMXBR

AMXCO

AMXLA

AMXMX

OPENMX

RETBR

RETLA

TEFBR

TIMBR

Versions I tried so far without luck:

XT1789-06_NASH_RETIN_8.0.0_OPXS27.109-49-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC

--> no WiFi

--> Bluetooth OK

--> SIM not detected

--> fb: baseband not found

XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

--> WiFi OK

--> SIM detected, not registered to network

--> fb: baseband M998_50.71.02.95M NUS

XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU

--> WiFi OK

--> SIM detected, not registered to network

--> fb: M8998TMO_2027.117.02.41.08R NUS

XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC

--> no WiFi

--> SIM not detected

--> Bluetooth OK

--> fb: baseband not found

XT1789-05_NASH_RETBR_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC

--> boot loop

--> SIM detected --> bootloop

--> reflash

--> WiFi OK

--> SIM detected

--> BT OK

--> fb: M8998_50.71.02.95M NUS

NASH_RETAIL_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CF

--> WiFi OK

--> SIM detected

--> no networks found

--> fb: baseband not found

XT1789-05_NASH_RETLA_DS_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC

XT1789-05_NASH_RETLA_SS_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC

--> with both the system will come up as Dual SIM device

--> dual SIM config: SIM detected but not registered

--> manually patched to single SIM --> same behavior

--> WiFi OK

--> BT OK

--> fb: M998_52.74.02.96M NCD

Whatever version I try, flashing XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU afterwards at least allows me for listing available networks again.

'fastboot getvar all' output:

(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: CHINA
(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: ZY224TK6CL
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 4308BFDA
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *************** (same as on package but hidden here)
(bootloader) meid:
(bootloader) date: 02-25-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4381
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-23/
(bootloader) ro.build.fingerprint[1]: 113ea:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.23.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: M8998_52.74.02.96M NCD
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(bootloader) kernel.version[1]: soncm@ilclbld36) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Jul 5 09:27:21 CDT 2019
(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: tmo
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(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: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.190s

By the way, in a few days I will get another one of these devices. Chances are that the same SW is installed.

Would it be helpful to read out said device's config/software?