[X 2014 Q&A, Help & Troubleshooting] ostheer:
Bricked Moto X 2014? Fastboot flashing, ADB sideloading, nothing seems to work :(

Hello,

I have this Moto X 2nd gen (XT1092), and I wanted to install an Android Marshmallow OS last weekend.

I did it according to this article on XDA: http://xdaforums.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858 , where an install image plus small install description is posted.

This is the first ‘non-standard’ thing I tried with this phone. It is not rooted, nor did I make any changes in the settings for developers, apart from enabling USB debugging. The device was running an stock version of Android 5.1, which I received the normal way(just an automatic system update).

Using some 'fastboot flash....' commands via the PC, the image should be installed. However, upon trying the first command: 'fastboot flash partition gpt.bin', the terminal responded with:

-------------------------

target reported max download size of 536870912 bytes

sending 'partition' (32 KB)...

OKAY [ 0.003s]

writing 'partition'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.102s

-------------------------

Afterwards, my phone didnt boot to android anymore. The only thing it does is put me in "AP Fastboot Flash Mode (S)"

I have tried installing different stock Motorola images/zips for my phone, in order to try to get it back to how it was, but for every fastboot flash I want to do (except for the boot logo), I get the preflash validation error.

I also tried sideloading images via ADB via the recovery mode, bit this doesn’t work either:

When I try "adb sideload <IMAGE>.zip", it starts to send the file to the phone, and the phone receives it. Very quickly after completing the transfer, though, the phone can say two things (depending on what .zip file I try):

1.

Finding update package...

Opening update package...

Verifying update package...

Installing update...

Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re

Installation aborted.

2.

Finding update package...

Opening update package...

Verifying update package...

Installation aborted.

One thing to note is that when I try 'adb devices', it gives me:

-------------------------

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices

List of devices attached

TA99300SXJ sideload

-------------------------

It says that the device is in ADB sideload mode, which blocks me from using other ADB functions, like shell. Is there a way to get 'full' ADB acces?

I also tried using the official Motorola “RDS Lite” software, as some people say this can be used to correctly flash an image to the phone, but this program just does not see my phone.

I did install all drivers, and Windows recognizes the device correctly, in both fastboot and ADB (recovery) mode.

Another thing I wanted to do to solve this, is to unlock the bootloader, as some people on forums said that this would help. However, when I try “fastboot oem unlock UNIQUEKEY” with the key I got from the Motorola website, the bootloader responds with the message stating that I have to enable unlocking the bootloader via developer settings. And obviously, I cannot go to settings to enable this.

-------------------------

I’m very stuck here, and I would be the intensely happy if there would be someone around who can help me get my phone back to life!

I do have experience with flashing Android ROMs/Images/Zips, but not on Motorola devices.

I reckon that this:

“Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re”

could possibly be caused by an incorrect zip file. If that is the case, is there any way to obtain the proper file?

I did read about some special micro USB cables connecting the normally unused pin 4. Could this be helpful?

Any help would be IMMENSELY appreciated. I'm not ready to give up the fight!

Kind regards,

Ostheer