Need help, phone is mostly bricked.

[Ranys]

On the Moto X subreddit you might have seen my post on how it came to this. Cant post it here though, because I'm a new user.
So here is the stuff copy pasted:

I'll start from the beginning to list what I did to the phone: Also, yes I'm new to this, so I did some dumdums along the way.

-Did the Moto unlock stuff(worked fine)(thanks tutorial, you didn't tell me this would wipe all my data till the end, I was already done by then)
-Installed TWRP 2.7something (the latest that the TWRP site recommended for this phone, worked fine)
-Used TWRP to install SuperSU/Root the phone(worked fine)
-tried installing cyanogenmod (failed, doesn't boot normally)
-reflashed everything to stock(worked fine, boot android 4.2.2)
-android loads updates, installs, fails to boot (bricked)

Here I am this is what my bootloader looks like:

AP Fastboot Flash Mode (S)
30.BE(*) (sha- blahblah
eMMC: 16gGB blah blah
...
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
here comes the menue stuff
...

log looks like this:

downgraded security version
update gpt_main version failed
Failed to hab check for gtp_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot reason Invalid CID
USB connected

my fastboot recognizes the device I'm using the mfastboot v2 The Moto X is bought in EU (should be Moto X 1052)

I tried flashing it the same way I did for the reset, the way I did it before, but that doesn't work. I'm not exactly at the setup I actually used to do that with, I'll be able to try it that way again in 3 hours or so, but my setup should be about the same, cept that I'm using a USB3 connection right now instead of a USB2 (I read that ADB is having some problems there, but not that this is the case with fastboot) I've googled for a lot of solutions, non of them worked for me. I don't know what to do anymore.

Some things that might be of interest

mfastboot oem get_unlock_data

results in:

(bootloader) could not get unlock data! [Okay] finished...

Trying:

mfastboot flash partition gpt.bin

results in:

(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.269s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.174s

bootloader:

downgraded security version
update gpt_mail version failed
preflash validation failed for GPT

I usually get things done with trying around and normally(on other phones) I have no problem making a TWRP backup finding it! and pulling it from the phone so I can reset it within something like 15 mins, but I wasn't able to find where TWRP stored it's backups in this case, and I didn't care very much, not much on the phone to loose.
Anyone know what I could try?

E: Okay, just noticed that the codes in barcodes are different now:
IMEI/MEID: 0000000000000000
SKU: 000000000000
Serial Number: 13a869f1 (that's not the one it should be!!! My serial number should start with TA.... and not contain any lower case letters)
DATE: 01-01-1970

One more thing I did(because I found it in this forum) was mfastboot getvar all and got this back:

version-bootloader: 30BE(*)
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Samsung S4 SDRAM DIE=4Gb
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x3
secure: yes
mid: 026b
serialno: 13a869f1
qe:
unlocked: Not supported
iswarrantyvoid: Not supported
max-download-size: 805306368
uid: 2EED8B050C000100000000000000
imei: 000000000000000
meid:
sku: 000000000000000
cid: 0xdead
iccid:
date: 01-01-1970
cust_md5:
reason: Invalid CID
ro.build.date:
ro.build.id:
ro.build.tags:
ro.build.type:
ro.build.user:
ro.build.version.codename:
ro.build.version.incremental:
ro.build.version.release:
ro.mot.build.customerid:
ro.product.name:
ro.build.fingerprint:
ro.build.version.full:
kernel.version:

E: And no, I don't have a problem with the serial number showing here, in the getvar all, because as said in the text quoted from reddit, the stuff there is wrong anyway.

 

[substanceneil]

I am seeing the same error. Looking forward to any help to OP and me.