Database Develop

[SOLVED]moto XT1900-4 flashing locked and can't unlock

Hi, i own a moto x4 since early 2018 and had no problems with unlocking the bootloader, then installing twrp and then root with magisk...
The problem is I was getting bored about a notification that says that there was a new update for my phone and it always failed when i try to download and install it, so i tried to fix it. I really don't know developing but i thought the problem was related to the "your device can't be checked for corruption" notification that i got everytime y booted my phone. So I thought "Man, i just have to lock the bootloader again" and maybe I'll successful install that update.
Well, things don't go well when I typed the command "fastboot oem lock" on cmd, I saved a security copy of my things before typing the command for the second time. Then i tried rebooting the phone and get that ugly red notification...
It says "Your device is corrupt. It can't be trusted and will not boot". Okay I tried the exact same method I did when unlocked the bootloader for the first time but don't work. So I don't know how to proceed.
Anybody can help me? Thanks for reading
Code:
PS C:\Users\-bich\Desktop\platform-tools_r28.0.0-windows\platform-tools> .\fastboot oem unlock YMCVIWY57PMTFM7EKO56
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
Code:
.\fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180530
(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: ZY224WWDP8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x28
(bootloader) uid: C1F34D0A
(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: 356486081345556
(bootloader) meid:
(bootloader) date: 03-23-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4274
(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-17/23:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.271.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7036.16.01.69R PAYTON_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g8a19f40 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed May 30 14:43:30 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180530
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:pmic: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180530
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:prov: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: opencl
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(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: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above

VicenteCL said:
Hi, i own a moto x4 since early 2018 and had no problems with unlocking the bootloader, then installing twrp and then root with magisk...
The problem is I was getting bored about a notification that says that there was a new update for my phone and it always failed when i try to download and install it, so i tried to fix it. I really don't know developing but i thought the problem was related to the "your device can't be checked for corruption" notification that i got everytime y booted my phone. So I thought "Man, i just have to lock the bootloader again" and maybe I'll successful install that update.
Well, things don't go well when I typed the command "fastboot oem lock" on cmd, I saved a security copy of my things before typing the command for the second time. Then i tried rebooting the phone and get that ugly red notification...
It says "Your device is corrupt. It can't be trusted and will not boot". Okay I tried the exact same method I did when unlocked the bootloader for the first time but don't work. So I don't know how to proceed.
Anybody can help me? Thanks for reading
Code:
PS C:\Users\-bich\Desktop\platform-tools_r28.0.0-windows\platform-tools> .\fastboot oem unlock YMCVIWY57PMTFM7EKO56
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
Code:
.\fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180530
(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: ZY224WWDP8
(bootloader) cid: 0x0032
(bootloader) channelid: 0x28
(bootloader) uid: C1F34D0A
(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: 356486081345556
(bootloader) meid:
(bootloader) date: 03-23-2018
(bootloader) sku: XT1900-4
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4274
(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-17/23:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.271.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M660_7036.16.01.69R PAYTON_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g8a19f40 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed May 30 14:43:30 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180530
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:pmic: MBM-3.0-uefi-dfccc3a-180530
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180530
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:prov: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180530
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: opencl
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(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: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Click to expand...
Click to collapse
is you phone booting in system?
If yes: Enter in Developer Settings an activate "Enable OEM Unlocking" -- No have this option??? Enable ADB, and enable superuser by ADB.
And run: adb shell setprop ro.oem_unlock_supported 1
Now "Enable OEM Unlocking" activated option showing!!! Enable it and re-run "fastboot oem unlock code"!
If your system not booting:
Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in your phone! And repeat steps above!

juniofdm said:
is you phone booting in system?
If yes: Enter in Developer Settings an activate "Enable OEM Unlocking" -- No have this option??? Enable ADB, and enable superuser by ADB.
And run: adb shell setprop ro.oem_unlock_supported 1
Now "Enable OEM Unlocking" activated option showing!!! Enable it and re-run "fastboot oem unlock code"!
If your system not booting:
Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in your phone! And repeat steps above!
Click to expand...
Click to collapse
Worked with the second method! THANK YOU SO MUCH! It has come back to life!

Im getting this error error: device '(null)' not found

juniofdm said:
is you phone booting in system?
If yes: Enter in Developer Settings an activate "Enable OEM Unlocking" -- No have this option??? Enable ADB, and enable superuser by ADB.
And run: adb shell setprop ro.oem_unlock_supported 1
Now "Enable OEM Unlocking" activated option showing!!! Enable it and re-run "fastboot oem unlock code"!
Click to expand...
Click to collapse
Can you tell me or help me to enable superuser by ADB?

fix moto x4 xt1900-7 ro.carrier

my moto has stopped working properly. it gets stuck in the logo screen and won't start. not even the backup solved the problem. I can access to the recovery and the bootloader but if I install a rom, nothing change and remain stuck. Rescue and Smart Assistant does not detect the device and tells me that ro.carrier is missing and to contact the seller to rewrite it. This the log of my device
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224KPP39
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 3A32ECCB
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356516081801693
(bootloader) meid:
(bootloader) date: 08-10-2018
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4298
(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]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.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: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(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: 7
all: listed above
finished. total time: 0.436s
I try this buy not change
fastboot oem config carrier retail
...
(bootloader) <UTAG name="carrier" type="str" protected="FALSE">
(bootloader) <value>
(bootloader) retail
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see (bere Is link buy i can post for now)
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.031s]
finished. total time: 0.031s

CyberrPK said:
my moto has stopped working properly. it gets stuck in the logo screen and won't start. not even the backup solved the problem. I can access to the recovery and the bootloader but if I install a rom, nothing change and remain stuck. Rescue and Smart Assistant does not detect the device and tells me that ro.carrier is missing and to contact the seller to rewrite it. This the log of my device
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224KPP39
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 3A32ECCB
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356516081801693
(bootloader) meid:
(bootloader) date: 08-10-2018
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4298
(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]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.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: M660_7045.36.01.100R PAYTON_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) gitmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) gitrov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(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: 7
all: listed above
finished. total time: 0.436s
I try this buy not change
fastboot oem config carrier retail
...
(bootloader) <UTAG name="carrier" type="str" protected="FALSE">
(bootloader) <value>
(bootloader) retail
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see (bere Is link buy i can post for now)
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.031s]
finished. total time: 0.031s
Click to expand...
Click to collapse
Try
Code:
fastboot oem fb_mode_clear
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Try
Code:
fastboot oem fb_mode_clear
I tried it and it worked. Meanwhile, I tried to install a custom rom, the Superior OS 10 and it starts up correctly. unfortunately with the installation I lost TWRP in favor of the recovery of the rom and the classic method does not make it install again (I will look at how to install it again). unfortunately LMAS does not login (until yesterday work so it will be a momentary disservice of lenovo) and I cannot check if the ro.carrier is working now
Click to expand...
Click to collapse

sd_shadow said:
Try
Code:
fastboot oem fb_mode_clear
I'm a little confused. the installation of the custom rom was successful, but in theory the recovery partition is gone. I say this because if I try to flash TWRP I get this message
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (33432 KB)...
OKAY [ 1.400s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 1.416s
I would think it is a kernel problem, but I can access to the recovery from the bootloader. at this point I think that the recovery partition has been replaced with a partition with a different name. I enclose images of the bootloader, recovery, OS started. I hope you can help me
https://freeimage.host/i/2qZQIe
https://freeimage.host/i/2qZik7
https://freeimage.host/i/2qZsp9
https://freeimage.host/i/img-20200913-194310.2qtEy7
Click to expand...
Click to collapse

You have to download both twrp.img and twrp-installer.zip from twrp.me site. Try "fastboot boot twrp.img" and next install twrp.zip.

unbelievable is a whole day that I have tried that exact command line and I always had error. I restarted the pc and then everything was fine :/
I tried to re-launch LMSA but i always get the same error. with an stock rom should you delete?
https://freeimage.host/i/2qb2sa

Do you have qcn or efs backup , if you have then can you provide that , do it fast

Help moto g7 plus ran out of recovery stock and does not accept twrp

Hello, please help !! My moto g7 plus ran out of recovery when I tried to put twrp on it. If I restart or turn off first, it enters the fastboot option and I have to press star to continue turning on. I already put stock firmware several times and it remains the same. Please someone to explain to me how I do the flashing so that the recovery stock returns. Thank you

Grislu said:
Hello, please help !! My moto g7 plus ran out of recovery when I tried to put twrp on it. If I restart or turn off first, it enters the fastboot option and I have to press star to continue turning on. I already put stock firmware several times and it remains the same. Please someone to explain to me how I do the flashing so that the recovery stock returns. Thank you
Click to expand...
Click to collapse
What does getvar all say? (remove imei before posting)
Code:
fastboot getvar all
edit:
Are you following the install method from this thread?
[RECOVERY] Official TWRP 3.3.1 for Moto G7 Plus [lake]
Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com

hi, i get this. Thank you
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY2269JHHS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x0e
(bootloader) uid: C4AB995C
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 06-24-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 3897
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10
(bootloader) ro.build.fingerprint[1]: 1-21-18-7/fac4a:user/rele
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: M636_21.71.02.66R LAKE_LATAMDSDS
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ (no
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 2
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREE
(bootloader) kernel.version[3]: an 29 09:20:56 CST 2021
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-210129
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-210129
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-210129
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-210129
(bootloader) git:tz: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:hyp: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:devcfg: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:cmnlib: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:keymaster: MBM-3.0-lake_retail-3da76fb4f-21012
(bootloader) gitrov: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) git:storsec: MBM-3.0-lake_retail-3da76fb4f-210129
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tefco
(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: 1
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.203s

Moto x4 corrupted

Moto X4 shows your device is corrupt it cant be trusted and will not boot. pls help I tried few methods but not worked.

arunyesudas03 said:
Moto X4 shows your device is corrupt it cant be trusted and will not boot. pls help I tried few methods but not worked.
Click to expand...
Click to collapse
Try LMSA's Rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

I tried rescue app first but it doesn't work.

I tried rescue app first but it doesn't work.
sd_shadow said:
Try LMSA's Rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse

arunyesudas03 said:
I tried rescue app first but it doesn't work.
Click to expand...
Click to collapse
What error did you get?
What does getvar all say?
Code:
fastboot getvar all

sd_shadow said:
What error did you get?
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
Bro can you check the 3rd image

arunyesudas03 said:
Bro can you check the 3rd image
Click to expand...
Click to collapse
No the error with LMSA

sd_shadow said:
No the error with LMSA
Click to expand...
Click to collapse

sd_shadow said:
What error did you get?
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (0)
(bootloader) serialno: ZY224FMS7V
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 351899080443617
(bootloader) meid:
(bootloader) date: 10-17-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 3775
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.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: M660_7045.36.01.100R PAYTON_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retin
(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: no
(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
all: listed above
finished. total time: 0.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all

arunyesudas03 said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (0)
(bootloader) serialno: ZY224FMS7V
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 351899080443617
(bootloader) meid:
(bootloader) date: 10-17-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 3775
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPW29.69-
(bootloader) ro.build.fingerprint[1]: 40-4/4ca2a:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.421.17.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: M660_7045.36.01.100R PAYTON_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g8668f45 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Sep 5 02:21:39 CDT 2019
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retin
(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: no
(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
all: listed above
finished. total time: 0.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
Click to expand...
Click to collapse
I believe your only option is booting into EDL Mode and using a blankflash
Is my device in EDL Mode?
How to boot into EDL Mode
You will need to find a blankflash for "payton"
https://forum.xda-developers.com/c/moto-x4.6912/

sd_shadow said:
I believe your only option is booting into EDL Mode and using a blankflash
Is my device in EDL Mode?
How to boot into EDL Mode
You will need to find a blankflash for "payton"
https://forum.xda-developers.com/c/moto-x4.6912/
Click to expand...
Click to collapse
Ok let me check

Hi
While connecting my device it detect as usb controllers as unknown usb device(device descriptor request failed).
Not detecting under port as qd loader

arunyesudas03 said:
Moto X4 shows your device is corrupt it cant be trusted and will not boot. pls help I tried few methods but not worked.
Click to expand...
Click to collapse
Managed to solve?

Bootloop simply installing Magisk (solved)

Long time member of XDA,first time actually needing to root a phone.
I successfully unlocked the bootloader of my 64Mb dual sim XT1929-8 (EU variant I believe).
Previously unused phone, I all I did was attempt to install Magisk
Installation
The Magic Mask for Android
topjohnwu.github.io
now it won't boot but can I still start the standard recovery/bootloader.
Where did I go wrong?
This was my config before flashing:
C:\cmd\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-180526
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA_APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM636 1.0 (3)
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 6E5192B0
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 12-15-2018
(bootloader) sku: XT1929-8
(bootloader) carrier_sku: XT1929-8
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4251
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:8.1.0/OPW
(bootloader) ro.build.fingerprint[1]: 28.70-35/8194:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.11.39.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.2.r1-07200-sdm660.0
(bootloader) version-baseband[0]: M636_10.22.01.65R BECKHAM_EMEA_APACDSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g7821a6b-00003
(bootloader) kernel.version[1]: -ge77904a ([email protected]) (gcc vers
(bootloader) kernel.version[2]: ion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Sat May 26 17:35:37 CDT 2
(bootloader) kernel.version[4]: 018
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-180526
(bootloader) git:xbl: MBM-3.0-uefi-bee28a0-180526
(bootloader) gitmic: MBM-3.0-uefi-bee28a0-180526
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-180526
(bootloader) git:tz: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:hyp: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:devcfg: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib64: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:keymaster: MBM-3.0-uefi-ca80f2d-180526
(bootloader) gitrov: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:storsec: MBM-3.0-uefi-ca80f2d-180526
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(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: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.203s
Click to expand...
Click to collapse
I then followed the Magisk instructions, using a boot.img file from BECKHAM_RETAIL_8.1.0_OPWS28.70-56-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip for the patch.
I chose the retail one because the phone was still on firmware 8.1.0, rather than use the EU variant, as the only file available for that was version 9.0. This was the output:
C:\cmd\adb>fastboot flash boot magiskboot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24053 KB) OKAY [ 0.874s]
Writing 'boot_a' OKAY [ 0.702s]
Finished. Total time: 1.622s
Click to expand...
Click to collapse
The phone gives the black bootloader unlocked disclaimer, then the blue motorola logo with the Verity overlay. The overlay goes away but then nothing changes further. I guess this is a bootloop?
Looking at the following helpful posts, https://forum.xda-developers.com/t/firmware-8-1-official-moto-z3-play-beckham.3805433/post-78404153
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants) Firmwares the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) =...
forum.xda-developers.com
I tried applying the unpatched boot.img. And I tried applying it to boot_a:
C:\cmd\adb>fastboot flash boot magiskboot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24053 KB) OKAY [ 0.874s]
Writing 'boot_a' OKAY [ 0.702s]
Finished. Total time: 1.622s
Click to expand...
Click to collapse
But no difference in behaviour.
I notice the recovery screen says Baseband: <not found>
I don't know why that would be gone if all I did was replace the boot partition.
This is now the output of getvar:
C:\cmd\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-3f845b6-180526
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA_APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM636 1.0 (3)
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 6E5192B0
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 12-15-2018
(bootloader) sku: XT1929-8
(bootloader) carrier_sku: XT1929-8
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4194
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.2.r1-07200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gb64b199-02190
(bootloader) kernel.version[1]: -gcdcc31b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Thu Apr 4 12:38:56 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-uefi-3f845b6-180526
(bootloader) git:xbl: MBM-3.0-uefi-bee28a0-180526
(bootloader) gitmic: MBM-3.0-uefi-bee28a0-180526
(bootloader) git:rpm: MBM-3.0-uefi-75767ea-180526
(bootloader) git:tz: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:hyp: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:devcfg: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:cmnlib64: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:keymaster: MBM-3.0-uefi-ca80f2d-180526
(bootloader) gitrov: MBM-3.0-uefi-ca80f2d-180526
(bootloader) git:storsec: MBM-3.0-uefi-ca80f2d-180526
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(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: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.172s
Click to expand...
Click to collapse
I'm curious also why slot-retry-count:_a would decrement from 7 to 6 ?
I thought I would ask on here before trying too many random things.
Surely it can't be too hard to reverse the flash of a single file.

TL;DR : I found the isssue myself - The firmware image I chose wasn't compatible with my stock rom even though it was for the same hardware.
~~~
Just to help anyone else with this issue in the future:
I installed Lenovo 'Rescue and Smart Assitant' and jumped through their account registration hoops.
It reflashed the entire phone with the RETEU rom upgraded to Android 9 and got it running again.
Of course it was not rooted, but this time Magisk instructions worked - using the boot.img file from the RETEU image.
I still had the following error during install:
C:\cmd\adb>fastboot flash boot magiskboot.img
(bootloader) is-logical:boot_a: not found
Click to expand...
Click to collapse
But the phone booted and is successfully rooted.