[X 2014 Q&A, Help & Troubleshooting] gardndj:
Been a long time away from xda (stock android's come a long way). Back with a messed up Moto X. Here's the rundown.

Moto X 2014 dev edition XT1095

Purchased May 2015

Bootloader unlocked upon arrival

Rooted and TWRP for a while, no custom roms, eventually flashed back to stock with firmware image from Motorola

Have received multiple OTA updates since - running latest version

Have encrypted since

Ever since the marshmallow and subsequent updates my phone has been acting strangely - weird periods of rapid battery drain, misreported battery life, etc. Thought it might be a good time for a wipe, so after backing up the few pieces of data I wanted I rebooted to recovery.

Wipe cache appeared to execute properly.

Wipe userdata did not. It failed with an error that I remember including "blkdiscard on partition failed", or something along those lines, and messages about not being able to access recovery logs. Subsequent tries produced the same error. Reboot resulted in a boot loop on the initial warning bootloader unlocked boot animation, would sometimes progress past for a few seconds and freeze on the moto globe animation, and twice got a few seconds past that to a screen that explained my encrypted data was corrupted and I would need to reset my phone, with a big reset button that, when pressed, told me it would reset and restart my phone but simply turned it off.

At this point I figured I had some corrupted partitions, and what better way to repair that than start over and reflash clean? Problem is I naively assumed moto would have the latest and greatest on their firmware page, didn't pay attention to version numbers and just downloaded the highest version on there for the XT1095 - later found it was 5.1, which is obviously a downgrade and not what I wanted. Flashing that image with mfastboot produced an error during each part, starting with gpt.bin. Couple examples.

C:\Users\Dan\Desktop\motox>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.011s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.092s

C:\Users\Dan\Desktop\motox>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.545s

A little troubleshooting led to the realization that I was flashing an old android version, so I found the latest - VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip - at the firmware.center website. This produced the same errors.

Here's where I stand.

I've tried fastboot, mfastboot, rsdlite and windroid, nothing works

I can no longer access recovery - attempting to do so produces a red message - "Invalid boot image header!"

Whenever I try to flash an img my phone displays a pink message - "version downgraded for primary gpt", or primary recovery, etc

Attempting to format or erase partitions through fastboot produces a remote failure as well

Motorola Device Manager reports no updates for my device, current version is 24.201.3.victara_tmo.tmo.en.us

Currently my phone is in a fastboot bootloop, but fastboot appears functional - I can reboot-bootloader

The result of getvar all is:

C:\Users\Dan\Desktop\motox>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6018
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA44909E26
(bootloader) cid: 0x0000
(bootloader) channelid: 0x85
(bootloader) uid: 7A05AE100B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: prefer not to share, but matches
(bootloader) meid:
(bootloader) date: 05-06-2015
(bootloader) sku: XT1095
(bootloader) iccid: prefer not to share, but matches
(bootloader) cust_md5: 48718E6D7332FB353113EE5EA0335438
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Aug 30 5:20:21 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_tmo/victara:6.0/M
(bootloader) ro.build.fingerprint[1]: PES24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.victara_tmo
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_T
(bootloader) version-baseband[1]: MO_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g7820355 (hudsoncm@
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 20 02:41:33 CDT 2016

I'm thinking either my emmc was corrupted to begin with and there was no coming back, or there was a chance at recovering but I bricked after accidentally attempting to downgrade the bootloader, even though it seemed like nothing actually flashed. If anyone has any thoughts I would be grateful, I've been down the rabbit hole today and don't have any answers. If not I suppose it's time for a new phone - or a moto claim, if possible?