[Moto X4 Questions & Answers] Stringmander:
Hello everyone,

I am in a bit of a dire situation here with my Moto X4 (Model No. XT1900-1), and I cannot tell you how grateful I would be if someone might be able to assist me in fixing it. To begin, I flashed LineageOS onto my Moto X4 a couple of years back, and have had trouble updating Lineage every time there was a major update. While my phone would be able to successfully boot into the operating system, it would be unable to connect to the cellular network or WiFi, and I would have to perform 2 fresh installations in order to get the phone working properly. I tolerated it, but for this reason (and that installing Open GApps and Magisk would also require a manual update) I would rarely update the phone.

Against my better judgement I attempted to update the phone to Lineage 18.1 today, and experienced the same issue once again. Wanting to get to the root of the issue, I requested assistance in Lineage's support chat, and someone pointed out that I probably missed the critical step of copying the configuration of slot A into slot B as detailed in their fresh installation instructions, and also recommended attempting to update the firmware. I attempted the fresh installations as I normally would to fix this (the instructions are detailed here), and flashed the copy-partitions-20210323_1922.zip package linked in said instructions, sadly to no avail, even after multiple installation attempts. I then decided it might be best to attempt to flash a stock ROM and update the firmware. Using the this stock ROM and the instructions and commands detailed in this thread, I successfully flashed the software, but when it booted up I saw, to my horror, that the phone was still experiencing the same issue. My most recent attempt to fix this was to flash a stock 9.0 ROM from this thread because Lineage's instructions do specify that the firmware does need to be updated to Android 9, and I would still like to use Lineage after I overcome this issue, but sadly the phone is still experiencing the same issue in this case as well.

(EDIT) I did some more digging and stumbled upon this thread which pointed me to the LSMA. I restored the phone using the LSMA, and had a degree of success. The phone does now recognize the cellular and WiFi hardware, and can pick up their respective networks, but both the cellular and WiFi connections constantly flicker on and off. I did also try using the copy partitions package detailed in that particular thread, but sadly this new issue persists after flashing it. I have pasted the output of "fastboot getvar all" after restoring using the LSMA below:

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-eca8056-191217
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2258KN6T
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: A9FB75A4
(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: 356484083595567
(bootloader) meid:
(bootloader) date: 12-14-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4270
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-4/4011a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.481.16.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g81a5f80 (hud
(bootloader) kernel.version[1]: soncm@ilclbld103) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Tue Dec 17 16:30:24 CST 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191217
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191217
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191217
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191217
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(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