yashsingh1/xdaforums huggingface dataset:
[Moto Z Play Questions & Answers] joshua764:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8953-C1.82

(bootloader) product: addison

(bootloader) board: addison

(bootloader) secure: yes

(bootloader) hwrev: P7

(bootloader) radio: 2

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B

(bootloader) cpu: MSM8953

(bootloader) serialno: ZY223LCGC3

(bootloader) cid: 0x0000

(bootloader) channelid: 0x23

(bootloader) uid: 9C2DFF1200000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 534773760

(bootloader) reason: UTAG "bootmode" configured as fastboot

(bootloader) imei:

(bootloader) meid:

(bootloader) date: 08-29-2017

(bootloader) sku: XT1635-02-SS

(bootloader) battid: SNN5975A

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Mon Jan 5 2:39: 1 UTC 1970"

(bootloader) ro.build.fingerprint[0]: motorola/addison/addison:8.0.0/OPN

(bootloader) ro.build.fingerprint[1]: 27.76-12-22/24:user/release-keys

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full[0]: Blur_Version.27.21.24.addison.ret

(bootloader) ro.build.version.full[1]: ail.en.US

(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0

(bootloader) version-baseband: M8953_10238.63.04.83R ADDISON_ROW_CUST

(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g174984b (hud

(bootloader) kernel.version[1]: soncm@ilclbld67) (gcc version 4.9.x 2015

(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT

(bootloader) kernel.version[3]: Mon Mar 26 08:27:14 CDT 2018

(bootloader) sbl1.git: git=MBM-NG-VC1.82-0-g3523998

(bootloader) rpm.git: git=bd19194

(bootloader) tz.git: git=fbd9875-dirty

(bootloader) devcfg.git: git=fbd9875-dirty

(bootloader) keymaster.git: git=fbd9875-dirty

(bootloader) cmnlib.git: git=fbd9875-dirty

(bootloader) cmnlib64.git: git=fbd9875-dirty

(bootloader) prov.git: git=fbd9875-dirty

(bootloader) aboot.git: git=MBM-NG-VC1.82-0-g345bd7e

(bootloader) frp-state: protected (77)

(bootloader) ro.carrier: attmx

all: listed above

finished. total time: 0.517s
[Moto Z Play Questions & Answers] joshua764:
hi, download another firmware stock and flash it fastboot and just start the phone, thank you very much for your time, something is wrong with the firmware
[Moto Z Play Questions & Answers] echo92:
Thanks for the output. It does look like your bootloader was re-locked during the last flash. As such, those fallthrough errors suggest your bootloader cannot verify your device partitions (e.g. kernel, system, recovery, etc) and thus is blocking boot https://source.android.com/security/verifiedboot/ That could point to, for example, a bad flash or failing flash memory (so your bootloader cannot read the partitions).

With your original flash of the Oreo stock ROM, did you note any errors in the flash, or is the flash log you provided from the original flash? Looking at your output it does suggest the flash worked as the values (bootloader version C1:82, baseband and kernel) seem to match the stock Oreo update.

I'd try a different computer and/or different USB ports, update your ADB tools and see if you can re-flash your device again. I'd also try to unlock your device bootloader if possible (though if your OEM unlocking is off, that's not possible until you can boot). If your device is still unable to boot and you cannot flash your device or cannot get a flash to work, there may be a more serious hardware/flash memory error on your device.

EDIT - glad to hear you got it fixed, which firmware did you download in the first place?
[Moto Z Play Questions & Answers] KrisM22:
great - is your bootloader unlocked?

Thanks [MENTION=7970352]echo92[/MENTION] !!!
[Moto Z Play Questions & Answers] joshua764:
No, that's another issue, the Motorola page tells me that it can not be unlocked, a month ago I opened it without problem, now it does not let me unlock it
[Moto Z Play Questions & Answers] KrisM22:
did you lock it using SupahCookie's module?
[Moto Z Play Questions & Answers] joshua764:
use this tutorial

https://xdaforums.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
[Moto Z Play Questions & Answers] KrisM22:
Are you using the same binary that motorola gave you the first time?

Yes, I have heard of some folks not being able to unlock again. What error message does it give you?
[Moto Z Play Questions & Answers] joshua764:
Yes, I use the same binary. tells me that the key is not valid

and when I ask for a new one, he tells me that the bootloander can not be opened
[Moto Z Play Questions & Answers] KrisM22:
Yup. extreme bummer... :(
[Moto Z Play Questions & Answers] joshua764:
yes. a pity, I missed many things to try, sell and buy another mobile, I'm waiting for the motorcycle z4. I hope it comes out this year.

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play Questions & Answers] KrisM22:
Again [MENTION=7970352]echo92[/MENTION] Good catch! I would not have caught that. You have done a lot of work around the bootloader environment,

BUT

QUESTION - if Joshua's bootloader is locked, how was he able to flash the correct ROM and correct the situation?
[Moto Z Play Questions & Answers] echo92:
I imagine by re-flashing the correct stock ROM, the signatures for the partitions on Joshua's device would have matched that expected by the bootloader and the chain of trust (as established by a locked bootloader). Hence, the bootloader and kernel, upon verifying the partitions and matching them to its internal keys, would have permitted boot. If you'd like to read more, here's some technical documents on the Android Source pages: https://source.android.com/security/verifiedboot/verified-boot

That also means by extension you cannot (or should not be able to) root or modify your device, then attempt to re-lock your bootloader without a full flash of the correct stock firmware (which should be as new or newer than your bootloader). By doing so, you change the aforementioned signatures on your system partition, for example, and if your bootloader is locked, it'll likely cause boot to fail (hence the fall through to fastboot, or a boot loop) until you flash a fully stock ROM that is as new as your current bootloader or unlock your bootloader. This security feature appears to mainly be to ensure system integrity and prevent root/malware from interfering.
[Moto Z Play Questions & Answers] KrisM22:
YES - I understand the use of the phrase "correct stock".

So if someone grabs just any stock and flashed it to an unlocked phone, then fastboot locks it, It will likely never be able to be unlocked. Yes?

Thanks for the link - I am heading out for a bit but will read it when I get back. Your posts are very interesting. :)

---------- Post added at 09:27 PM ---------- Previous post was at 09:16 PM ----------

edit: though, if this rom was so correct as to be allowed in even with locked bootloaders, why can't it then be unlocked?
[Moto Z Play Questions & Answers] echo92:
As far as I understand it, it can't be just any stock - the firmware you want to lock with must be at least the same bootloader version as on your device or newer, and must be cryptographically signed by Motorola. For example, if your bootloader is C1:14, from what I've seen you would need the Feb 2018 7.1.1 firmware or the Oreo stock firmware to re-lock your bootloader. Attempts to lock with older firmware may fail as your bootloader may reject the fastboot flash (security downgrade errors and the like). Most of the firmwares I've seen appear to have originated from the Motorola servers, and as such should be digitally signed. As an aside, this digital signing is why blankflashes are so difficult to make, the blankflashes must be signed by Motorola (and match the signed keys on our devices) and have special programmers to permit them to flash over newer bootloaders. Motorola and other OEMs will not give them out (as they affect the bootloader directly, so in theory could be used to tamper with the security).

In theory, you should be able to unlock your device again using the same unlock key (since it should be based on your IMEI and other device variables). However, it does seem that, on occasion, after flashing the stock ROM (maybe a side effect from flashing the stock ROM or custom ROMs?) that some device parameters change or are lost, which then makes the unlock key invalid for a reason that I don't know about. I don't recall seeing any flags or counters that would limit the number of unlocks, but there appears to be side-effects. In Joshua's case, though, I don't see anything unusual (the CID can be 0x0000).

Without knowing the root cause of those side effects, if you wish to unlock again, you'd likely have to ask Motorola to generate an unlock code for you via the official forums: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809
[Moto Z Play Questions & Answers] KrisM22:
took a quick initial look at those links

"OEM key	The OEM key is a fixed, tamper-protected key available to the bootloader that must be used to verify the boot image."

"IMPORTANT:

VERIZON WIRELESS, ATT WIRELESS, AND REPUBLIC WIRELESS DEVICES ARE NOT ELIGIBLE FOR THE UNLOCKABLE BOOTLOADER PROGRAM.

Okay, so some giggles in there...

We would be guessing as to a solution to Joshua's problem. It might be to find the earliest 7.x rom of his channel and flash it, try unlock, let it ota, try unlock, etc.. Wish we had the version and base of what he had prior to first unlock.

Had a person just comment on my new Q&A thread saying they had locked and unlocked many times. So I have to categorize that as "lucky".

I really have no way to guide them as some channels like reteu seem sporadic in themselves and seem to have little or no continuity.

And some do not receive ota's at all if they stay within original channel.

Wish I could be sure of a way for [MENTION=4685751]joshua764[/MENTION] to regain unlockability, though if I were in that situation I guess I would grab every similar rom and try to flash it and then try to unlock it. Though of course at any turn an unsolvable brick is possible.

Yes, a lot of variables in there and apparently a lot of things determine whether you can repeat unlock.

the only solution to me is never to relock after you've unlocked. That doesn't help anyone who has already been screwed.

It's a bit like the flash TWRP and then take an ota and get a brick.

I have been absent from XDA for Feb-June. On my return this stuff seemed so obvious. But it didn't when I was here in Jan, though I was mightily confused by the 8 bl from the new pre-Oreo roms. Now I see, and understand, and have done, and that it's not a confusion at all but easy to go back and forth - the bl have the environment and the environment release number as shown on bl. That changes with every security or version update. Slap on a different stock ROM and you get that ROM's bl release environment and number. Easy. Except when you lock it again... :) So I ginned out a bunch of guides, but I have no solution to Joshua's problem or unbricking a lost bl. it's a shame to have had the evolution of this phone be so costly to so many simply because of a few incorrect recommendations early on - like locking and flashing TWRP or any custom Recovery (though I never see CM any more - we used to use that all the time... - ah well - ancient history and it wouldn't have helped either.

Thanks for the links. I'll read them some more, but. yeah, we really don't know what it's keying on! :)
[Moto Z Play Questions & Answers] joshua764:
very interesting is information, thank you very much for your time, I will continue reading what you have exposed, of course I will ask for another unlocking code, tomorrow I do it. What really catches my attention is watching my motorcycle model play change, I think that has to do with re-unlocking the bootloander. al.final of the model I get SS, that I have not seen in any forum or captura

Enviado desde mi XT1635-02 mediante Tapatalk

[
[Moto Z Play Questions & Answers] KrisM22:
Joshua

fastboot getvar all

what is your cid?
[Moto Z Play Questions & Answers] joshua764:
C: \ Archivos de programa (x86) \ ADB Mínimo y Fastboot> fastboot getvar all*

(gestor de arranque) slot-count: no encontrado*

(bootloader) slot-sufijos: no encontrado*

(bootloader) slot-suffixes: no encontrado*

(cargador de arranque) versión: 0.5*

(bootloader) version-bootloader: moto-msm8953-C1.82*

(gestor de arranque) product: addison*

(gestor de arranque) board: addison*

(gestor de arranque) secure: yes*

(gestor de arranque) hwrev: P7*

(bootloader) radio: 2*

(gestor de arranque) storage-type : Emmc*

(gestor de arranque) emmc: 32 GB SAMSUNG RX1BMB RV = 08 PV = 07 FV = 0000000000000007*

(gestor de arranque) ram: 3 GB SAMSUNG LP3 DIE = 6Gb M5 = 01 M6 = 05 M7 = 00 M8 = 7B*

(gestor de arranque) CPU: MSM8953*

(gestor de arranque) ) serialno: ZY223LCGC3*

(bootloader) cid: 0x0000

(gestor de arranque) channelid: 0x23*

(gestor de arranque) uid: 9C2DFF1200000000000000000000*

(gestor de arranque) securestate: oem_locked*

(gestor de arranque) iswarrantyvoid: yes*

(gestor de arranque) max-download-size: 534773760*

(gestor de arranque) reason: UTAG "bootmode" configurado como fastboot*

(gestor de arranque) imei :*

(gestor de arranque) meid:*

(gestor de arranque) fecha: 08-29-2017*

(gestor de arranque) sku: XT1635-02-SS*

(gestor de arranque) battid: SNN5975A*

(gestor de arranque) iccid:*

(gestor de arranque) cust_md5:*

(gestor de arranque) max-sparse-size : 268435456*

(cargador de arranque) tiempo actual: "lun 5 de enero 2:39: 1 UTC 1970"*

(gestor de arranque) ro.build.fingerprint [0]: motorola / addison / addison: 8.0.0 / OPN

(gestor de arranque) ro.build.fingerprint [1]: 27.76-12-22 / 24: usuario / release-keys*

(gestor de arranque) poweroffalarm: 0*

(gestor de arranque) ro.build.version.full [0]: Blur_Version.27.21.24 .addison.ret*

(gestor de arranque) ro.build.version.full [1]: ail.en.US*

(gestor de arranque) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0*

(gestor de arranque) version-baseband: M8953_10238.63.04.83R ADDISON_ROW_CUST*

(cargador de arranque) kernel.version [0]: versión de Linux 3.18.71-perf-g174984b (hud*

(cargador de arranque) kernel.version [1]: soncm @ ilclbld67) (gcc versión 4.9. x 2015*

(gestor de arranque) kernel.version [2]: 0123 (prelanzamiento) (GCC)) # 1 SMP PREEMPT*

(gestor de arranque) kernel.version [3]: lun mar 26 08:27:14 CDT 2018*

(gestor de arranque) sbl1.git : git = MBM-NG-VC1.82-0-g3523998

(gestor de arranque) rpm.git: git = bd19194*

(gestor de arranque) tz.git: git = fbd9875-dirty*

(gestor de arranque) devcfg.git: git = fbd9875-dirty*

(gestor de arranque) keymaster.git: git = fbd9875-dirty*

(cargador de arranque) cmnlib .git: git = fbd9875-dirty*

(gestor de arranque) cmnlib64.git: git = fbd9875-dirty*

(gestor de arranque) prov.git: git = fbd9875-dirty*

(cargador de arranque) aboot.git: git = MBM-NG-VC1.82-0 -g345bd7e*

(gestor de arranque) frp-state: protected (77)*

(gestor de arranque) ro.carrier: attmx*

all: listed above*

finished.*tiempo total: 0.517s

I understand by the 0000007 it is unlockable

Cid 0x0000

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play Questions & Answers] joshua764:
C:\Program Files (x86)\Minimal ADB and Fastboot>

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock LX7EB4UIGLZKFE2AMCQV

< waiting for any device >

...

FAILED (command write failed (No error))

finished. total time: 0.134s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock LX7EB4UIGLZKFE2AMCQV

< waiting for any device >

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

...

(bootloader) Bootloader is unlocked! Rebooting phone

OKAY [ 1.976s]

finished. total time: 2.094s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot

rebooting...

finished. total time: 0.116s

I just opened the bootloander hehehe very happy

very grateful to all of you for the encouragement to move forward with this
[Moto Z Play Questions & Answers] KrisM22:
I totally missed your last comment - great!
[Moto Z Play Questions & Answers] KrisM22:
removed
[Moto Z Play Questions & Answers] echo92:
Well, it looks like the bootloader got unlocked after another attempt - it wouldn't surprise me if there was a communications error between the device and the computer (could be the USB port or the cable?)

The idea you posted above about downgrading or flashing earlier stock ROMs is not possible with a locked/re-locked bootloader - the bootloader would enforce and block downgrades of firmware that is older than the bootloader. You would only be able to flash firmware that is the same build or newer than the bootloader on a device, else that would defeat the purpose and security of a locked bootloader.

Which stock ROM are you referring to that you don't like? I'm not sure what stock ROM joshua flashed in the first place before getting a working stock ROM, but it looks like his device was from AT&T Mexico, hence the attmx carrier flag. The carrier flag would be vzw if you bought a Verizon carrier locked device, or retus if it was a retail US device (as an aside, Verizon is one of those carriers that if you buy a device from them, like the Z Droid, you cannot usually unlock the bootloader. Motorola won't issue an unlock key at all, presumably through a carrier agreement).

I'm not sure that flashing a stock ROM can influence the carrier flag or change your software channel. However, flashing a retail stock ROM onto a carrier branded device could cause issues, possibly including loss of IMEI if the radios are substantially different. I've seen this with Latin American G4 Plus devices flashing the retail G4 Plus stock ROMs and there've been reports of lost signal. Your experience may vary.
[Moto Z Play Questions & Answers] KrisM22:
sorry didn't read that - great! problem solved!!!
[Moto Z Play Questions & Answers] echo92:
2)Even so, you wouldn't be able to flash an earlier stock ROM on a locked bootloader - the bootloader would block any flash of firmware older than the bootloader version. Unlocked bootloaders may be less strict in this regard, a locked bootloader would block and report a 'preflash validation error' if you tried to flash an older firmware.

3)Hmm, that firmware version that's reported is the OPN27.76-12-22 stock Oreo April 2018 firmware. I'm not sure what other firmware is available besides the June 2018 Oreo OTA update, unless I'm misunderstanding your query?

4)That's true if the firmware's unified - and it looks like the Z Play Oreo firmware is unified across regions. If there were different variants of the firmware, you'd have to be careful (as those different variants would likely be modified for specific regions), which can cause some issues between the radio hardware and the firmware. Again, it looks like Motorola has wisely merged different regional firmwares into one update, and I don't know if AT&T Mexico has different firmware or uses the same as stock firmware, just that some carriers do have different firmware variants pushed to devices bought from them (Verizon's certainly one that does that, and Amazon Prime subsidised devices are subject to having different firmwares too).
[Moto Z Play Questions & Answers] KrisM22:
Just ignore all that - I deleted it. I am being plagued by 304 Forbidden 's on xda tons(Chrome, win10) - got distracted. sorry. great news that it worked!!!

---------- Post added at 06:04 PM ---------- Previous post was at 05:29 PM ----------

I keep getting bounced to 403 Forbidden

2. certainly you could and he did - he had to have as he twice flashed that phone, one failure you caught, and the one that worked but remained lock bl for a bit until he just managed to bl unlock it. I don't know "why". I simply notice he did. As to "similarity" it doesn't really know that until it flashes just about all of it.

3. my bad 76 12 22 is Oreo April. There would in fact be nothing before that. My booboo. I kept thinking 7...

4. It seems that some (Moto Z Play) region specific software works in other regions - this is something I heard about when I was around here in Jan, but been gone since then. And as I recall this related to something about eu folks not being able to get ota's, but I could well be remembering it wrong.

- It was bad enough that Vz made life so hard for it's phone owners, but a shame that Amazon is doing it too. But I haven't really researched any of that and I have no interest in them (perhaps because of that?). My choices here (Boston)(besides Vz) are simply ATT and TMo(besides a plethora of virtual/pretend ones that too often clamp speeds), and coverage for me for the sites I need works out best for ATT. But these Moto phones seem to be becoming more and more radio capable - that is can be taken to other parts of the world. Though some travel advice I have heard is to avoid having your phone stolen, just get a cheap paid phone there when you arrive, and that is probably what I would do. No worries about carrier compatibility. Take pics with a camera.

In general when I think about a new-to-me phone, I think about modifiabil-ity Can I unlock bl and root it. In practice, I buy phones that have been out for a year or so, so folks can have had lots of time to break it and make it usable. Course here I am running 8 stock - LOL. But who knows what I'll be running tomorrow. Pez is on the horizon and fast approaching. i did just boot to TWRP and do a backup, so I guess I'm thinking about moving... I do like how the fingerprint thing works on this - never would have thought to try it but someone had a prob so turned it on...

Course we don't really NEED any of this stuff! Toys!!!
[Moto Z Play Questions & Answers] echo92:
2)Hmm, I've not seen that Joshua flashed another stock ROM besides the Oreo stock ROM - from what I understand from this thread, he locked using the tutorial by Supahcookie (or the very similar tutorial by talktosam), then tried to flash the stock Oreo fastboot ROM. Afterwards, he experienced errors booting until another stock ROM was flashed and then the device booted, then after a few tries the unlock works. Is there something I missed or are we missing some information?

4)Having different firmware for various regions is an issue for other Moto devices (just look at the G4 Plus or G5/G5S Plus forums), and you are correct in that having the wrong firmware for your region made you ineligible for OTA updates whatsoever (mismatch between the expected build and the actual build on your device). Motorola has been unifying firmware updates but it's still an issue, perhaps less so for the Z Play - I guess this is their 'you unlocked the bootloader, it's your responsibility now' stance.

You're lucky in that you've dodged the Verizon/Amazon lockdown - other users haven't been so lucky... As for bootloader unlocking, seems that some OEMs are not keen anymore - Huawei/Honor and Lenovo come to mind, and Samsung Snapdragon devices in the US are not officially unlockable. I hope Motorola stays on unlockable bootloaders. As for root, it seems trickier to get root, for now magisk can handle it, it'll be interesting to see what the future holds as Safetynet may become more strict or Google puts in more restrictions in future Android builds.