[Moto Z2 Play  Questions & Answers] Adanadhel:
Greetings!

I have a Moto Z² Play Dual Chip (XT1710) which has been recently updated to Pie and right after it, it started presenting several issues (restarts, freezes, etc.) and then, 3 days ago, it simply didn't enter the system anymore. It loops on fastboot and it presents a huge number of errors whatever I try to do - and I've tried a lot.

On AP Fastboot Flash Mode (Secure) screen, it shows the following information:

BL: MBM-2.1-albus_retail-b625135-190911

Baseband:

Product/Variant: albus 000000000000000 64GB P4

Serial number: a8d9e088

CPU: MSM8953

eMMC: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=000000000000007

DRAM: 4GM SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F

Console [NULL]: null

Tools Mode Config: DISABLED

Battery OK

oem_locked

Transfer Mode: USB Connected

If I select any option from the fastboot menu (Recovery, Start, BP tools, Qcom, Factory), I get a "Start Up Failed" and the following message:

Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant.

and

AP Fastboot Flash Mode (Secure)

Fastboot reason: Last time flashing failed

USB connected

failed to validate boot (or recovery) image

ERROR: Failed to pass validation, backup to fastboot

Boot up failed

I can switch tools mode on and if I select barcodes, it shows only zeros for IMEI and SKU.

Based on the message displayed on the startup failure, I downloaded Lenovo Moto Smart Assistant and selected Rescue. When I select the device's model it shows a message saying: "Information you input does not match connected device. Your device is [000000000000000]. Want to use it?" and the only option offered is to Apply delected info, which leads to a "Doesn't match the appropriate firmware. You can try to select a firmware by yourself manually.", but there's no box to select firmware manually. If I ask it to read current device it says it's "Unable to match the appropriate firmware. Some key information cannot be read from the device".

After some digging, I came across RSD Lite 6.2.4 and have also downloaded the following STOCK ROM:

ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.

I've also tried different stock roms (RETBR, RETCA) and different android versions (Nougat and Oreo) but the message was always the one on this screen:

https://imgur.com/Xdq36E8

Finally, I tried flashing it manually with system wide Platform Tools. Just to check, I tried unlocking the bootloader. When I typed 'fastboot oem get_unlock_data', this was the outcome:

>fastboot devices

a8d9e088 fastboot

>fastboot oem get_unlock_data

(bootloader) Unlock data:

(bootloader) read datablock error

(bootloader) Failed

OKAY [ 0.004s]

Finished. Total time: 0.082s

Then, I typed the getvar command and got the cid: 0xDEAD:

>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: MBM-2.1-albus_retail-b625135-190911

(bootloader) product: albus

(bootloader) board: albus

(bootloader) secure: yes

(bootloader) hwrev: P4

(bootloader) radio: 5

(bootloader) storage-type: emmc

(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F

(bootloader) cpu: MSM8953

(bootloader) serialno: a8d9e088

(bootloader) cid: 0xDEAD

(bootloader) channelid: 0x00

(bootloader) uid: 5FA607D400000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: n/a

(bootloader) max-download-size: 534773760

(bootloader) reason: Last time flashing failed

(bootloader) imei: 000000000000000

(bootloader) meid:

(bootloader) date: 01-01-1970

(bootloader) sku: 000000000000000

(bootloader) carrier_sku:

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sbl1.git: sbl1.git

(bootloader) rpm.git: rpm.git

(bootloader) tz.git: tz.git

(bootloader) devcfg.git: devcfg.git

(bootloader) keymaster.git: keymaster.git

(bootloader) cmnlib.git: cmnlib.git

(bootloader) cmnlib64.git: cmnlib64.git

(bootloader) prov.git: prov.git

(bootloader) aboot.git: MBM-2.1-albus_retail-b625135-190911

(bootloader) frp-state: no protection (err)

(bootloader) ro.carrier:

(bootloader) current-slot:

(bootloader) slot-suffixes: _a

(bootloader) slot-count: 1

(bootloader) slot-successful:_a: INVALID

(bootloader) slot-successful:_b: INVALID

(bootloader) slot-bootable:_a: INVALID

(bootloader) slot-bootable:_b: INVALID

(bootloader) slot-retry-count:_a: unknown

(bootloader) slot-retry-count:_b: unknown

all: listed above

Finished. Total time: 0.078s

Even though I knew I'd hardly achieve anything after that, I tried flashing it manually, inputting line by line, but didn't get very far (I tried both fastboot and mfastboot). These are the steps I followed:

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot flash dsp adspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot flash system system.img_sparsechunk.8

fastboot flash system system.img_sparsechunk.9

fastboot flash system system.img_sparsechunk.10

fastboot flash system system.img_sparsechunk.11

fastboot flash system system.img_sparsechunk.12

fastboot flash oem oem.img

fastboot erase carrier

fastboot erase cache

fastboot erase DDR

fastboot oem fb_mode_clear

fastboot reboot

The outcomes for each command are the following:

>getvar max-sparse-size returns:

max-sparse-size: 268435456

Finished. Total time: 0.002s

>oem fb_mode_set returns:

FAILED (remote: '')

fastboot: error: Command failed

>flash partition gpt.bin:

(bootloader) is-logical:partition: not found

Sending 'partition' (45 KB) OKAY [ 0.167s]

Writing 'partition' (bootloader) Validating 'gpt.default.xml'

(bootloader) Committing 'gpt.default.xml'

(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'

(bootloader) Flashing primary GPT image...

(bootloader) Failed to write primary GPT.

(bootloader) Failed to program partition table

FAILED (remote: '')

fastboot: error: Command failed

>flash bootloader bootloader.img

(bootloader) is-logical:bootloader: not found

Sending 'bootloader' (5115 KB) OKAY [ 0.417s]

Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'

(bootloader) Committing 'bootloader.default.xml'

(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'

(bootloader) Failed to erase partition

(bootloader) Failed to flash partition aboot

FAILED (remote: '')

fastboot: error: Command failed

>flash modem NON-HLOS.bin

(bootloader) is-logical:modem: not found

Sending 'modem' (62728 KB) OKAY [ 2.951s]

Writing 'modem' (bootloader) Failed to erase partition

FAILED (remote: '')

fastboot: error: Command failed

>flash fsg fsg.mbn

(bootloader) is-logical:fsg: not found

Sending 'fsg' (4124 KB) OKAY [ 0.364s]

Writing 'fsg' (bootloader) Failed to erase partition

(bootloader) Failed to flash partition fsg

FAILED (remote: '')

fastboot: error: Command failed

>flash dsp adspso.bin

(bootloader) is-logical:dsp: not found

Sending 'dsp' (16384 KB) OKAY [ 0.904s]

Writing 'dsp' (bootloader) Failed to erase partition

(bootloader) Failed to flash partition dsp

FAILED (remote: '')

fastboot: error: Command failed

>flash logo logo.bin

(bootloader) is-logical:logo: not found

Sending 'logo' (2192 KB) OKAY [ 0.249s]

Writing 'logo' (bootloader) Failed to erase partition

(bootloader) Failed to flash partition logo

FAILED (remote: '')

fastboot: error: Command failed

>flash boot boot.img

(bootloader) is-logical:boot: not found

Sending 'boot' (16384 KB) OKAY [ 0.748s]

Writing 'boot' (bootloader) Image boot failed validation

(bootloader) Preflash validation failed

FAILED (remote: '')

fastboot: error: Command failed

>flash recovery recovery.img

(bootloader) is-logical:recovery: not found

Sending 'recovery' (20580 KB) OKAY [ 1.087s]

Writing 'recovery' (bootloader) Image recovery failed validation

(bootloader) Preflash validation failed

FAILED (remote: '')

fastboot: error: Command failed

>flash system system.img_sparsechunk.0 (it was the same from 0 to 12)

(bootloader) is-logical:system: not found

Sending 'system' (262141 KB) OKAY [ 12.211s]

Writing 'system' (bootloader) Image s failed validation

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

FAILED (remote: '')

fastboot: error: Command failed

>flash oem oem.img

(bootloader) is-logical:oem: not found

Sending 'oem' (135836 KB) OKAY [ 6.299s]

Writing 'oem' (bootloader) Image o failed validation

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

FAILED (remote: '')

fastboot: error: Command failed

>erase carrier

Erasing 'carrier' (bootloader) Failed to erase partition

FAILED (remote: '')

fastboot: error: Command failed

>erase cache

Erasing 'cache' (bootloader) Failed to erase partition

FAILED (remote: '')

fastboot: error: Command failed

>erase DDR

Erasing 'DDR' (bootloader) Failed to erase partition

FAILED (remote: '')

fastboot: error: Command failed

>oem fb_mode_clear

FAILED (remote: '')

fastboot: error: Command failed

>reboot (reboot works lol)

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.004s

So, is it dead after all? Or am I doing something wrong? There was a video on YouTube in which the guy managed to solve the 0xDEAD cid by using a UMT dongle, but it's a rather expensive equipment.

Any suggestion will be highly appreciated.