[Moto Z2 Play  Questions & Answers] wizard-dima:
Hi everybody.

I ask for any help to restore my smartphone.

The problem is:

That I accidentally uploaded someone else's backup, the "cid" section. Now I have a cid: 0xDEAD

An interesting case, after this recovery the bootloader locked. Status:

securestate: oem_locked

*verity-state: enforcing

And I can not unlock it :( He writes an error, I think it's because of the frp section that changes the last byte to 01. After setting the checkbox in the setting - for the developer - the factory unlock.

D: \ ADB> fastboot oem get_unlock_data

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

...

(bootloader) Unlock data:

(bootloader) validate header error: 55

(bootloader) 3A15880808988261 #

(bootloader) 5A5932323442425A5642004D6F746F205A320000 #

(bootloader) 9D6169D0A91A800175B1EDA6CADAE6D3FB144F98 #

(bootloader) 09FAAB8E000000000000000000000000

OKAY [0.103s]

finished. total time: 0.104s

D: \ ADB> fastboot oem unlock XBZQPOSESK3KL7XQRRFT

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

...

(bootloader) feature disabled

OKAY [0.007s]

finished. total time: 0.008s

I watched a lot of articles and videos on the web. And I found an interesting video, where on Moto x the 2nd generation. In this situation, the bootloader was unlocked, unlocked, i.e. after flashing and starting the phone, oem_unlocked has already been indicated on the screen. I wonder if it's possible to do this on Z2 play?

https://www.youtube.com/watch?v=aYjzD9WZum0

I was trying to flash a full firmware. I can download all the parts of the firmware, except: system, boot, recovery. oem.img

In recovery I also can not get, only fastboot.

When flashing different versions of the bootloader, the file names change when prompting fastboot getvar all. So the bootloader loads well. But I have on my smartphone's screen:

Start up failed:

Your device did not start up succeessfuly.

Use the sofrware Repair Assistent on your computer to repair your device.

Connect yor device to your omputer to get the Software Repair Assistant.

When loading bootloader.img

-keys-cid50_retru \ Windows> fastboot flash bootloader bootloader.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot: bootloader: not found

target reported max download size of 536870912 bytes

sending 'bootloader' (5115 KB) ...

OKAY [0.178s]

writing 'bootloader' ...

(bootloader) Validating 'bootloader.default.xml'

(bootloader) Committing 'bootloader.default.xml'

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

(bootloader) - flashing 'rpm.mbn' to 'rpm'

(bootloader) - flashing 'tz.mbn' to 'tz'

(bootloader) - flashing 'devcfg.mbn' to 'devcfg'

(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'

(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'

(bootloader) - flashing 'keymaster.mbn' to 'keymaster'

(bootloader) - flashing 'prov.mbn' to 'prov'

(bootloader) - flashing 'sbl1.mbn' to 'sbl1'

OKAY [0.550s]

finished. total time: 0.730s

All is well.

.

But here's an example of boot.img

-keys-cid50_retru \ Windows> fastboot flash boot boot.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot: boot: not found

target reported max download size of 536870912 bytes

sending 'boot' (16384 KB) ...

OKAY [0.514s]

writing 'boot' ...

(bootloader) Image boot failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.726s

If you look at the smartphone's screen in bootlaoder logs - Failed to verify hab image boot.