[Moto Z2 Force  Questions & Answers] urvurm:
I got to this point after following a guide here to install magisk and MK100 Nash. I lost baseband, probably because I naively flashed XT1789-05 firmware from the guide, to an 04. Idk, anyway, I hadn't read as much at that point and thought I needed to lock the bootloader again *duh duh.* So I'm reading a lot about how this might be impossible to recover from and it's starting to look like it. I've downloaded 10s of GB of firmware to multiple computers, and I for sure can say that the bootloader is rejecting any flashing of firmware from OCX27.109-51 or OCX27.109-36 that I've tried anyway. There may be yet more stock firmwares to try, but I think I'm missing the point with all that because shouldn't any stock firmware be accepted by the bootloader? Anyway, if I could get people to muster up whatever they can on getting out of this trap I laid myself, I would really appreciate it. I was very foolish to attempt this when my food stamps and college application depend on me having a phone number. Plus this phone was sweet I feel like I betrayed it.

I've been trying to fuss with Qualcomm recovery but either EDL is broken too, since some commands I've tried to get it into EDL just resulted in it going to the ol' "can't be trusted," screen but that might be just that it's not going into EDL anyway. Thinking about getting a deepflash cable or something. I lack the patience and dexterity to rig it myself right now. But I don'y want to get my hopes up if it's screwed.

One fun quirk is that if I fastboot boot boot.img it actually does boot to a broken OS where "pixel setup" infinitely crashes but I can get it to let me use a black desktop with limited settings, like I can use the flashlight haha. No adb or ability to change developer settings though. In case it wasn't clear, I can't use TWRP, factory reset, or anything but fastboot essentially.

I'm wondering if someone knows a shell script I could possibly load into fastboot to enable OEM unlock again? AS in, commands to change the OEM unlock to "enable" in dev ops?

I noticed fastboot has a shell option '-c' which I was hoping to leverage with one of those broken boot.imgs maybe change the settings that way?

Btw I also have tried using the LMSA tool and it's a piece of crap, it never seemed like it would work on my other computer, but it had a weird connection. I installed windows on this one and it seemed to work, possibly a USB 2.0 thing, but as soon as LMSA seemed to actually be maybe doing something, I lost the ability to sign in. It just hangs forever and says it was successful then asks again (or it doesn't). I added a new windows user, tried reinstalling like 40 times, it behaved erratically but ultimately the problem persisted and now it remembers my login info between uninstalls and across new users but can't actually log in.

(bootloader) kernel: uefi

(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420

(bootloader) product: nash

(bootloader) board: nash

(bootloader) secure: yes

(bootloader) hwrev: PVT

(bootloader) radio: NA_UMTS

(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: ZY224TL8V5

(bootloader) cid: 0x0015

(bootloader) channelid: 0x85

(bootloader) uid: 3F57D9A7

(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:<Not zero>

(bootloader) meid:

(bootloader) date: 03-25-2018

(bootloader) sku: XT1789-04

(bootloader) carrier_sku: XT1789-04

(bootloader) battid: SNN5987A

(bootloader) battery-voltage: 3748

(bootloader) iccid:

(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-7/9:user/release-keys

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.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: <not found>

(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g668a0f8 (huds

bootloader) kernel.version[1]: oncm@ilclbld30) (gcc version 4.9.x 20150

(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT

(bootloader) kernel.version[3]: Thu Jan 10 22:25:12 CST 2019

(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420

(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420

(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-180420

(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420

(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) git:prov: MBM-3.0-nash_tmo-7d478e6-180420

(bootloader) qe: "qe 1/1"

(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-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: 7

(bootloader) slot-retry-count:_b: 0