[Moto Z2 Force  Questions & Answers] Loperaco:
Hi.

I have fresh news.

The first thing I tried was to enable the option to unlock the OEM because that option was in gray, try to connect the internet via USB cable and no option worked, but when connecting by bluetooth (which is not easy either for those who don’t know how) I did it! and once connected, I enabled the option again, so I activated it to allow me to unlock the OEM, but when restarting the bootloader to verify it was still showing the status "Flashing_locked" (sad face).

Even knowing this, try the options in this order and with these results:

1. Try the command 'adb reboot-edl' or 'adb reboot edl'. The first command that the console recognized was 'adb reboot -edl' but once accepted by the CMD the cell phone was rebooted alone and went back to the ROM, that is, it was not blank.

2. Go to fastboot and try 'fastboot oem blankflash'. When doing this the result obtained in the CMD was “(bootloader) Command Restricted FAILED (remote failure) finished. total time: 0.006s”, probably due to the fact that the bootloader still indicates "Flashing_locked".

3. Boot into QCOM mode and try 'fastboot oem blankflash'. When I start the QCOM option from the bootloader the cell phone automatically loads the ROM, after this I activated the USB Debugging and ran the command in question but the result was "<waiting for any device>" and nothing happens. I tried the command again without activating the USB Debugging and nothing happened either. If I enter the command "fastboot devices" the command does not give any results, I give way to the next line as if nothing happened.

4. I was sad after all this so I decided to retry everything, starting with the command to put the phone in mode 9008, so, just out of curiosity I tried the second sentence you wrote, that is, 'adb reboot edl' (without the line in the middle before the word “edl”), this command also recognized it but this time if it went to blank (yeah !!!). So after accomplishing this I followed the instructions of https://xdaforums.com/z2-force/help/hard-bricked-blankflash-z2-force-t3705789, but the result when executing the Blank-Flash file was:

[ 0.000] Opening device: \\.\COM11

[ 0.001] Detecting device

[ 0.004] ...cpu.id = 94 (0x5e)

[ 0.005] ...cpu.sn = 3632543294 (0xd884363e)

[ 0.005] Opening singleimage

[ 0.005] Loading package

[ 0.009] ...filename = pkg.xml

[ 0.012] Loading programmer

[ 0.012] ...filename = programmer.elf

[ 0.013] Sending programmer

[ 0.091] ReadFile() failed, GetLastError()=0

[ 0.644] Unexpected command, expecting 3 or 18 or 4, got 1 instead.

[ 0.644] ERROR: sahara_download()->general error

[ 0.644] Check qboot_log.txt for more details

[ 0.645] Total time: 0.646s

[ 0.645]

[ 0.645] qboot version 3.85

[ 0.645]

[ 0.645] DEVICE {

[ 0.645] name = "\\.\COM11",

[ 0.645] flags = "0x64",

[ 0.645] addr = "0x28FD74",

[ 0.645] sahara.current_mode = "0",

[ 0.645] api.buffer = "0x2160020",

[ 0.645] cpu.serial = "3632543294",

[ 0.645] cpu.id = "94",

[ 0.645] cpu.sv_sbl = "0",

[ 0.645] cpu.name = "MSM8998",

[ 0.645] storage.type = "UFS",

[ 0.645] sahara.programmer = "programmer.elf",

[ 0.645] api.bnr = "0x20C7ED0",

[ 0.645] }

[ 0.645]

[ 0.645]

[ 0.645] Backup & Restore {

[ 0.645] num_entries = 0,

[ 0.645] restoring = "false",

[ 0.645] backup_error = "not started",

[ 0.645] restore_error = "not started",

[ 0.645] }

[ 0.645]​

When executing the "blank-flash" file again, the result obtained was:

[ 0.000] Opening device: \\.\COM11

[ 0.001] Detecting device

[ 34.005] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

[ 34.005] Check qboot_log.txt for more details

[ 34.005] Total time: 34.006s

[ 34.005]

[ 34.005] qboot version 3.85

[ 34.005]

[ 34.005] DEVICE {

[ 34.005] name = "\\.\COM11",

[ 34.005] flags = "0x64",

[ 34.005] addr = "0x28FD74",

[ 34.005] api.bnr = "0x612CA8",

[ 34.005] }

[ 34.005]

[ 34.005]

[ 34.005] Backup & Restore {

[ 34.005] num_entries = 0,

[ 34.005] restoring = "false",

[ 34.005] backup_error = "not started",

[ 34.005] restore_error = "not started",

[ 34.005] }

[ 34.005]​

I thought I had made a worse mistake, but turning off the cell phone normally returned to enter the ROM without problem.

At this point I was left with no more ideas...