[Moto G Q&A, Help & Troubleshooting] Izaak99:
Need someone with unlocked code

Can someone who unlocked and was willing to give out their code also dump their persist, UTAGS, CID and PDS partitions and upload it here?

The CID partition is where the unlock_data command is getting those hashes (the entire hex strings are taken directly out of there). The PDS and UTAGS partitions are also partitions where the data is specific to the phone (both contain the serial #) and I'm curious if I can find any correlation to someone's unlock code stored somewhere in there. If nothing pans out then it looks like a very painful process to crack.. if the exact algorithm/which keys they are using to hash with the unlock code were known and if its even using that hash in the CID to match, then its very possible to use hashcat to find your key. I just have a feeling (more like hoping) its easier than brute-forcing it out there and its written as a backup somewhere.

FYI, there are some interesting strings just by dumping that fastboot partition:

0123456789abcdef0123456789ABCDEF<null>

token "%s" is found. Replace it with "%s".

dbval_read_partition

Malloc for DBVC: db_len %x failed!

No CID partition found!

failed to read CID 1st part of block for partition %s

Dlmot_sst_oem_lock_handler

mot_sst_validate_hash_password

%02X%02X%02X%02X%02X%02X%02X%02X#%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X#%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X#%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X

%s: temp buffer malloc failure!

%s: hash_ptr malloc failure!

%s: hash calculation faliure!

%s: hash calculation failure!

hash at offset i: %02d : %02x does not match

Error while unlocking device

mot_sst_validate_token: Token header incorrect

mot_sst_validate_token: Format version incorrect

mot_sst_validate_token: Length incorrect

mot_sst_validate_token: Binding information incorrect

mot_sst_validate_token: Unable to validate token integrity

mot_sst_validate_token: Token integrity invalid

unlock failed in sst oem unlock handler %02x

unlock data invalid!

Cannot provide unlock data

Cannot provide unlock data!

general failure in sst oem unlock handler %02x

General system failure! %02x

Unlock completed! Wait to reboot

General Unlock failure!

unlock failed in sst oem unlock handler

Done Setup my special MOT SST values

mot_sst_create_token: Unable to retrieve PUID

mot_sst_create_token: Unable to retrieve FUID

mot_sst_create_token: Getting PSV

mot_sst_create_token: Unable to retrieve PSV

mot_sst_create_token: Generate token code

mot_sst_create_token: token code generated!

mot_sst_create_token: Writing token

mot_sst_create_token: Unable to generate token code

create_token status: %d

mot_sst_create_token: Creating token

mot_sst_create_token: Getting flash uid

mot_sst_oem_lock_handler: invalid state

mot_sst_oem_lock_handler: load and validate failed

%s failure to delete or create token

mot_sst_pal_gen_aes_cmac: START

Success generating cmac

FAIL generating cmac

%s: failed to freeze utags: %d

ERROR: Cannot write device info

ERROR: out of memory

ERROR: Cannot read device info

ERROR: Device info corrupted

failed to thaw utags from partition "%s", error: %d

failed to load utags from secondary storage

generating empty utags in memory

dbval_validate_generic_datablock - Check Cert Chain

dbval_validate_generic_datablock - Check DB Signature

dbval_db_validate_gen_hdr - Check Type

dbval_db_validate_gen_hdr - Read Processor UID

dbval_db_validate_gen_hdr - Read Flash UID

dbval_db_validate_gen_hdr - PAL UID

dbval_db_validate_gen_hdr - DB UID

dbval_db_validate_gen_hdr - Success

dbval_db_validate_gen_hdr - Flash UID Length returned INVALID, must be 16 bytes

dbval_db_validate_gen_hdr - Processor UID Length returned INVALID, must be 16 bytes