[Moto X4 Questions & Answers] Micael Jarniac:
Hi!

I have a Motorola Moto X4 (payton XT1900-6 32GB P4), and today I tried installing LineageOS 17.1 on it. I failed.

I've posted about what happened today on Reddit, but I can't link to it in here.

Well, the problem now is that `fastboot` isn't working very well.

For example, if I want to run `fastboot getvar all`, I often have to run it like 10 times until it works:

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
getvar:all FAILED (remote: 'unknown command')
Finished. Total time: 0.003s

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
(bootloader) alllash: not found
getvar:all FAILED (remote: '')
Finished. Total time: 0.003s

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
getvar:all FAILED (remote: 'unknown command')
Finished. Total time: 0.003s

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
(bootloader) alllash: not found
getvar:all FAILED (remote: '')
Finished. Total time: 0.004s

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
getvar:all FAILED (remote: 'unknown command')
Finished. Total time: 0.002s

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
(bootloader) alllash: not found
getvar:all FAILED (remote: '')
Finished. Total time: 0.003s

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
getvar:all FAILED (remote: 'unknown command')
Finished. Total time: 0.002s

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-5cff2cb-180615
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0040097631
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: E3500D98
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ########
(bootloader) meid:
(bootloader) date: 10-31-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4319
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-22/28:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.281.28.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M660_7036.16.01.69.01R PAYTON_LATAMDSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g755d0b4 (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]: Tue Aug 14 12:39:24 CDT 2018
(bootloader) git:abl: MBM-3.0-payton_retail-5cff2cb-180615
(bootloader) git:xbl: MBM-3.0-payton_retail-436ef6e-180615
(bootloader) git:pmic: MBM-3.0-payton_retail-436ef6e-180615
(bootloader) git:rpm: MBM-3.0-payton_retail-3e0955c-180615
(bootloader) git:tz: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) git:hyp: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) git:devcfg: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) git:cmnlib: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) git:keymaster: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) git:prov: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) git:storsec: MBM-3.0-payton_retail-a4559c6-dirty-180615
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 4
all: listed above
Finished. Total time: 0.115s
C:\Users\Micael Jarniac\Documents\Android\payton>fastboot boot twrp-3.4.0-0-payton.img
Sending 'boot.img' (33432 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed

C:\Users\Micael Jarniac\Documents\Android\payton>fastboot boot twrp-3.4.0-0-payton.img
Sending 'boot.img' (33432 KB) # This gets stuck

I do have TWRP installed and working, and I can use `adb sideload`, but I can't `fastboot flash`.

I wanted to flash the stock firmware back, to kinda fix the phone, but I couldn't find a way to do that without `fastboot flash`.

So now I have absolutely no idea what to do. I can install LOS back (through TWRP), but then it'd constantly crash if I have a SIM card inserted. To fix that, I'd have to update the modem. To update the modem, I need `fastboot`.

I think it's worth mentioning that I tried multiple USB ports, both 2.0 and 3.0, and I tried two USB cables too. I rebooted my computer many times. I also redownloaded the platform-tools thingy just in case. And installed some fresh drivers too.

Motorola Moto X4 (payton XT1900-6 32GB P4)
twrp-3.4.0-0-payton.img
twrp-installer-3.4.0-0-payton.zip
copy-partitions-20200903_1329.zip
lineage-17.1-20201020-nightly-payton-signed.zip
open_gapps-arm64-10.0-stock-20201023.zip

Edit:

I'm not sure if this is actually what's going on, but it seems to me like basically all `fastboot` commands are having its end trimmed:

'get_unlock_' is not a supported oem commandSee 'fastboot oem help'
FAILED (remote failure)

So the entire command isn't making it through to the phone, or the phone isn't correctly reading the command all the way through.

C:\Users\Micael Jarniac>fastboot oem get_unlock_data
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed

C:\Users\Micael Jarniac>fastboot oem get_unlock_data
FAILED (remote: 'unknown command')
fastboot: error: Command failed

C:\Users\Micael Jarniac>fastboot oem get_unlock_data
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed

C:\Users\Micael Jarniac>fastboot oem get_unlock_data
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote: '')
fastboot: error: Command failed

C:\Users\Micael Jarniac>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) [here there be characters]
(bootloader) [here there be characters]
(bootloader) [here there be characters]
(bootloader) [here there be characters]
(bootloader) [here there be characters]
OKAY [ 0.021s]
Finished. Total time: 0.022s

Edit:

I tried using a different computer, and on the other computer I had no problems with `fastboot` at all.

My computer was working just fine with `fastboot`, I used it to flash my wife's phone a few days ago, and it was with my computer that I started the process on my phone, successfully flashing custom recovery and all. Something along the way broke the compatibility between my phone and the `fastboot` on my computer (ADB works perfectly fine).

I've now flashed retail ROM on my phone, and that should allow me to now flask LOS 17.1 and not break things.