bootloader lock failure standard unlocking commands not working thinking its hash failure or sst key corrupted -

i not know why when y friend gets inebriated hook phone pc , play it. has basic knowledge of adb , fastboot commmand , verified thrown. when went re-lock bootloader did not thisi did. downloaded google minimal sdk tools updated adb , fastboot went way , got mfastboot motorola insure parsing flashing. of these fastboot packages tested on mac , linux ubuntu, on windows 8.1 pro n update 1 , windows 7 professional n sp2 (all x64). resulted in same errors. super thorough , taught here how manually erase , flash no scripts or tool kits.

fastboot oem lock

and returned.

(bootloader) fail: please run fastboot oem lock begin first!

(bootloader) sst lock failure!

failed (remote failure)

finished. total time: 0.014s

then tried again, again, , yep again. @ this point either read log , followed it. though think based on point starts playing phones more started panic because needs bootloader locked work , started attempting flash.

fastboot oem lock begin

and returned.

m:\shamu\factory image\shamu-lmy47z>fastboot oem lock begin ...

(bootloader) ready flash signed images

okay [ 0.121s] finished. total time: 0.123s

factory image\shamu-lmy47z>fastboot flash boot boot.img

target reported max download size of 536870912 bytes

sending 'boot' (7731 kb)... okay [ 0.252s] writing 'boot'...

(bootloader) preflash validation failed failed (remote failure) finished. total time: 0.271s

then bootloader log stated

cmd: oem lock

hab check failed boot

failed validate boot image

upon flashing boot.img bootloader logs lists "mismatched partition size (boot)". intresting returns

fastboot oem lock begin ... (bootloader) ready flash signed images

okay [ 0.121s]

finished. total time: 0.123s

fastboot flash boot boot.img

target reported max download size of 536870912 bytes

sending 'boot' (7731 kb)...

okay [ 0.252s]

writing 'boot'...

(bootloader) preflash validation failed

failed (remote failure)

finished. total time: 0.271s

i logged partitions see if zeroed out indicating bad emmc not.

cat /proc/partitions

cat /proc/partitions major minor #blocks name

179 0 61079552 mmcblk0

179 1 114688 mmcblk0p1

179 2 16384 mmcblk0p2

179 3 384 mmcblk0p3

179 4 56 mmcblk0p4

179 5 16 mmcblk0p5

179 6 32 mmcblk0p6

179 7 1024 mmcblk0p7

179 8 256 mmcblk0p8

179 9 512 mmcblk0p9

179 10 500 mmcblk0p10

179 11 4156 mmcblk0p11

179 12 384 mmcblk0p12

179 13 1024 mmcblk0p13

179 14 256 mmcblk0p14

179 15 512 mmcblk0p15

179 16 500 mmcblk0p16

179 17 4 mmcblk0p17

179 18 512 mmcblk0p18

179 19 1024 mmcblk0p19

179 20 1024 mmcblk0p20

179 21 1024 mmcblk0p21

179 22 1024 mmcblk0p22

179 23 16384 mmcblk0p23

179 24 16384 mmcblk0p24

179 25 2048 mmcblk0p25

179 26 32768 mmcblk0p26

179 27 256 mmcblk0p27

179 28 32 mmcblk0p28

179 29 128 mmcblk0p29

179 30 8192 mmcblk0p30

179 31 1024 mmcblk0p31

259 0 2528 mmcblk0p32

259 1 1 mmcblk0p33

259 2 8 mmcblk0p34

259 3 16400 mmcblk0p35

259 4 9088 mmcblk0p36

259 5 16384 mmcblk0p37

259 6 262144 mmcblk0p38

259 7 65536 mmcblk0p39

259 8 1024 mmcblk0p40

259 9 2097152 mmcblk0p41

259 10 58351488 mmcblk0p42

179 32 4096 mmcblk0rpmb

254 0 58351488 dm-0

ive asked log or total process see full warning, error, , failure message super far on business. have , literature have started crack. starting believe research , learnng android boot proccess. maybe there missing or corrupted key in sst table beleieved called bigtable google. or hash password failure when locking bootloader security down or way off please let me know. not know how investigate or disprove issue move on. able confirmation through stack trace missing or corrupted coding. can puzzle thats solved. though has become puzzle begs solved not emergency thanks.

you should try "fastboot flashing lock" command instead.