4.4.2 KitKat 161.44.25 update bricked my GSM Unlocked "T-Mobile" Moto X

[chrisjohnson22]

So I installed the latest update and it seems to have disabled my phone. I guess it's not a hard brick as I'm able to get to the bootloader menu. I did a factory reset and wiped the cache. The phone restarts and displays the boot animation but after a few seconds it goes dark and shuts off.

I thought I could just boot into recovery and flash the stock rom but when I connect the phone to my PC, my computer doesn't recognize it (I have the drivers installed by the way).

Any suggestions? Or am I completely hosed?

 

[Ry]

Re: latest update bricked my moto x

So I installed the latest update and it seems to have disabled my phone. I guess it's not a hard brick as I'm able to get to the bootloader menu. I did a factory reset and wiped the cache. The phone restarts and displays the boot animation but after a few seconds it goes dark and shuts off.

I thought I could just boot into recovery and flash the stock rom but when I connect the phone to my PC, my computer doesn't recognize it (I have the drivers installed by the way).

Any suggestions? Or am I completely hosed?

What model do you have? I'm guessing the GSM Unlocked "T-Mobile" version.

Is this the 4.4 update or the 4.4.2 update?

 

[chrisjohnson22]

Re: latest update bricked my moto x

What model do you have? I'm guessing the GSM Unlocked "T-Mobile" version.

Is this the 4.4 update or the 4.4.2 update?

Yep, it's the GSM Unlocked Tmo version and the 4.4.2 update.

 

[mpegripper]

Re: latest update bricked my moto x

were you rooted before the update?

 

[vtpmt81]

Re: latest update bricked my moto x

How did you install the last update? Was it OTA?

When you did the factory reset, were you running a custom non stock rom? A factory reset on a non stock rom can mess up your phone.

 

[chrisjohnson22]

Re: latest update bricked my moto x

How did you install the last update? Was it OTA?

When you did the factory reset, were you running a custom non stock rom? A factory reset on a non stock rom can mess up your phone.

the phone was not rooted before the update and I was running the factory stock rom. i did the install via OTA.

very surprised this happened. i thought these incidents were somewhat rare.

 

[DCSholtis]

Activated my GSM unlocked phone today and it immediately downloaded 4.2.2 without a problem

Posted via Android Central App

 

[someguy01234]

Well you have two choices:
If you want to keep your warranty:
Try sideloading this ota update while in stock recovery. If you need drivers for the computer to recognize: drivers
If that don't work, call up Motorola and requested an RMA.

If you want to lose your warranty:
Drivers
Unlock Motorola bootloader
Toolkit to restore phone to stock

 

[chrisjohnson22]

I was trying this route but as of now my PC doesn't recognize my phone when I connect it with a usb cable.

I thought I had to enable USB Debugging (?) on the phone, but can't since I can only get to the recovery menu.

Well you have two choices:
If you want to keep your warranty: Call up Motorola and requested an RMA.

If you want to lose your warranty:
Drivers
Unlock Motorola bootloader
Toolkit to restore phone to stock

 

[someguy01234]

Are you using the stock Motorola cable and are you using Windows 8?

Try the Motorola_6.3.0_64bit driver I uploaded, try it on Windows 7 using the stock cable. Boot into Bootloader menu and use "fastboot devices" command to confirm the computer seeing it.