[Moto G7 Plus Questions & Answers] aron.sjoberg:
I succeeded in flashing stock per your instructions and the touchscreen on the phone is now working again! Huzzah! :)

However, I still couldn't download the OTA system update:

I tried to lock the bootloader again using "fastboot oem lock" from ADB but even thought the phone was reset I still get this when booting the phone:

and still the same error message as above when trying to download the system update about the "system integrity is compromised".

I thought maybe the reason was the bootloader still being locked. When I run " fastboot getvar all" (the fastboot command "fastboot oem device-info" didn't work) I get this output:

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-8ca64c4-190401
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: WEJP
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 563EFE15
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: XXXXXXXXX
(bootloader) meid:
(bootloader) date: 04-20-2019
(bootloader) sku: XT1965-3
(bootloader) carrier_sku: XT1965-3
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 4231
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:9/PPWS29.98
(bootloader) ro.build.fingerprint[1]: -66-2/9d952:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.231.3.lake.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: M636_03.08.02.35R LAKE_WEJPDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g9d19292 (hud
(bootloader) kernel.version[1]: soncm@ilclbld31) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Apr 1 15:04:53 CDT 2019
(bootloader) git:abl: MBM-3.0-lake_retail-8ca64c4-190401
(bootloader) git:xbl: MBM-3.0-lake_retail-deba0a5-190401
(bootloader) git:pmic: MBM-3.0-lake_retail-deba0a5-190401
(bootloader) git:rpm: MBM-3.0-lake_retail-f920ba6-190401
(bootloader) git:tz: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) git:hyp: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) git:devcfg: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) git:cmnlib: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) git:keymaster: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) git:prov: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) git:storsec: MBM-3.0-lake_retail-42aad5d-dirty-190401
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(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.284s

Where in the output can I check if the bootloader is locked or unlocked?

Is it somehow possible to restore the phone so I can update the waiting OTA system update? You wrote that "once bootloader is unlocked we usually can't receive official updates anymore" but is this true even if I lock the boatloader? The system still knows the bootloader have been tampered with and this prevents the phone from ever getting OTA updates?

I'm terrible sorry for all my questions! It's been a while since I did this and what I'm remembering was that you could always restore the phone to stock... Have I missed restoring something?