Database Develop

[Q] Downgrade Bootloader/gpt.bin on unlocked bootloader

I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...

mohlsen8 said:
I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...
Click to expand...
Click to collapse
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.

mohlsen8 said:
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.
Click to expand...
Click to collapse
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.

jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
This is absolutely correct!

jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
there's a couple places i've seen this. and my bootloader is unlocked, and i can't downgrade, for instance, to the bootloader from the original t-mobile software (4.2.2 pre-camera) - this file, just to clarify (from sbf droid developers): TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC.xml.zip. i take the motoboot.img out and use "fastboot flash motoboot motoboot.img". i get:
(bootloader) Preflash validation failed
phone display says:
Failed to hab check for tz: 0x4e
?
while we're discussing, motorola says these can be relocked. in all of my screwing around this morning i was trying this too. i followed all directions and still cannot lock the phone. i use "fastboot oem lock" and it tells me:
(bootloader) FAIL: Please run fastboot oem lock begin first!
ok, so i use "fastboot oem lock begin". now it gives me:
(bootloader) Ready to flash signed images
ok, try "fastboot oem lock" again and then it gives me:
(bootloader) Re-Lock Failure. See Display
display says "No valid PIV block in SP for system piv validation failed (system) Re-lock failure".
i've tried many times to flash all stock files back to the phone using fastboot, as well as RDS Lite, and it's been successful each time, but it won't re-lock. i've also tried "fastboot oem lock begin" then flashing all the stock files, then "fastboot oem lock". still, no dice. what's up with this?

The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.

Steve-x said:
The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.
Click to expand...
Click to collapse
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?

mohlsen8 said:
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?
Click to expand...
Click to collapse
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.

Steve-x said:
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.
Click to expand...
Click to collapse
really? i had no idea that sequence mattered. why would that matter if i have an unlocked bootloader and want to flash an older one onto the device?
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.

mohlsen8 said:
really? i had no idea that sequence mattered.
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.
Click to expand...
Click to collapse
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?

beelzebu said:
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?
Click to expand...
Click to collapse
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.

mohlsen8 said:
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.
Click to expand...
Click to collapse
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X

flashallthetime said:
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X
Click to expand...
Click to collapse
Are you saying you were able to flash the pre-camera sbf? edit: sorry - didn't read you right at first. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.

mohlsen8 said:
Are you saying you were able to flash the pre-camera sbf? edit: sorry - see you said you didn't try this. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.
Click to expand...
Click to collapse
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X

flashallthetime said:
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X
Click to expand...
Click to collapse
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.

mohlsen8 said:
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.
Click to expand...
Click to collapse
now that's interesting. figured i'd try it anyway, so in the pre-camera SBF file i replaced gpt.bin with the post-camera gpt.bin and it flashes fine through rsd lite, motoboot and all. what the hell.

I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.

Steve-x said:
I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.
Click to expand...
Click to collapse
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.

mohlsen8 said:
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.
Click to expand...
Click to collapse
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.

jayboyyyy said:
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.
Click to expand...
Click to collapse
is that a dig? you don't have to be a jerk. i'm not some idiot pressing buttons over here. just asking if anyone knows why this is.
this is for t-mobile. but i have a gsm dev edition, same model as t-mobile etc. even the official firmware files for the GSM Developer Edition, that i downloaded directly from Motorola themselves, are labeled "T-MOBILE RETAIL..". i don't think the dev edition ever had the pre-camera version (it shipped with the update applied). so maybe you're right about that. i dunno. i'm not the only one who's reporting this. i was just really curious to know why this is.

Downgrade from 4.4.2 to 4.4

So I used the 4.4 root tutorial without any problems and then flashed the 4.4.2 update via sdcard.
The deal is that my supersu seems to be damaged, thought I still have root, the xposed framework can´t seem to receive supersu permission.
So I want to downgrade to the 4.4.
How should I do this?

alemonte said:
So I used the 4.4 root tutorial without any problems and then flashed the 4.4.2 update via sdcard.
The deal is that my supersu seems to be damaged, thought I still have root, the xposed framework can´t seem to receive supersu permission.
So I want to downgrade to the 4.4.
How should I do this?
Click to expand...
Click to collapse
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896

okaban said:
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896
Click to expand...
Click to collapse
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT

alemonte said:
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT
Click to expand...
Click to collapse
you can't go back to the complete 4.4 package and honestly im not even going to tell you how to get 4.4 running because i wont be responsible for you hardbricking your phone.
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry

dray_jr said:
you can't go back to the complete 4.4 package and honestly im not even going to tell you how to get 4.4 running because i wont be responsible for you hardbricking your phone.
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry
Click to expand...
Click to collapse
OK! I know I messed up updating to 4.4.2 rooted. Should've stayed on 4.4 but my X was having issues after disconnecting from Wifi to connect to LTE. Anyways..I´ll be returning the phone and getting a new one today! Tnks a lot for the help!

alemonte said:
Ok, so I have a locked bootloader. My guess is that I have the last version since I made the update to 4.4.2.
By having a locked bootloader I think I can´t downgrade to 4.2.2, right?
So I wanted to go back to 4.4 by following the commands below:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
But right on the first fastboot, I get this error:
downgraded security version
Update gpt_main version failed
preflash validation for GPT
Click to expand...
Click to collapse
Most likely you tried to downgrade to the very first 4.2.2 (.31 in case of XT1058). It's not possible. You need the one after, with camera update (.54 for XT1058, for example, http://sbf.droid-developers.org/phone.php?device=0)

okaban said:
Most likely you tried to downgrade to the very first 4.2.2 (.31 in case of XT1058). It's not possible. You need the one after, with camera update (.54 for XT1058, for example, http://sbf.droid-developers.org/phone.php?device=0)
Click to expand...
Click to collapse
please dont downgrade to 4.2.2 camera update downgrade to 4.4 you just have to not flash the gpt file but flash everything else.
if you flash 4.2.2 Camera update and then take the OTA for 4.4 you will brick your phone.

dray_jr said:
please dont downgrade to 4.2.2 camera update downgrade to 4.4 you just have to not flash the gpt file but flash everything else.
if you flash 4.2.2 Camera update and then take the OTA for 4.4 you will brick your phone.
Click to expand...
Click to collapse
So, is it possible to go from 4.4.2 to 4.4 without bricking or not? Just asking for clarification because of
4.4.2 has a new bootloader and 4.4 has a diffrent bootloader you cant downgrade the 4.4.2 bootloader at all. it is a one way street sorry
Click to expand...
Click to collapse

okaban said:
Term "Downgrade" refers to "lowering" you version, in this case from 4.4 to 4.2.2. Now you just need to go back to 4.4
I am not sure whether your bootloader unlocked or not and what you version is, but I think this one will help http://forum.xda-developers.com/showthread.php?t=2603358 or this one http://forum.xda-developers.com/showthread.php?t=2538896
Click to expand...
Click to collapse
Please do not advise any users to downgrade!
It is well documented that if you downgrade to ANY version, once on 4.4.2, you will brick your phone! It is literally all over the Moto X forums.
Wouldn't you feel awful if the OP followed your advice and bricked their phone???
---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------
EchoHelix said:
So, is it possible to go from 4.4.2 to 4.4 without bricking or not? Just asking for clarification because of
Click to expand...
Click to collapse
NO! I have no idea why anyone would advise you to do that.....
Whatever exploit you had used to root on 4.4 does not work on 4.4.2
The only way to root (and achieve write-protect-disable), now that you are on 4.4.2 is to unlock the bootloader. Even with unlocked bootloader, you still can't downgrade without bricking.

I'll just add my two cents as well....as perfectly said already above....I'll just add....
NO. Do not ever try to downgrade to any version if you are on 4.4.2 or higher already. Unless you don't care at all if you brick and have the cash for a new phone or an old phone you'd be happy using again.
No. Some will debate this, and they should keep it to themselves.....unless they are offering to replace your phone if their advice bricks you. ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
@okaban , please do not advice people to downgrade, or lead them to believe its safe.
If you want to try it, go ahead....but keep it to yourself. Too many aren't confident with this stuff and will end up with a paperweight because you led them to believe they could do it.
So please, do not suggest downgrading. Its irresponsible and hazardous advice.
Thanks! ?

samwathegreat said:
Please do not advise any users to downgrade!
It is well documented that if you downgrade to ANY version, once on 4.4.2, you will brick your phone! It is literally all over the Moto X forums.
[cut]
The only way to root (and achieve write-protect-disable), now that you are on 4.4.2 is to unlock the bootloader. Even with unlocked bootloader, you still can't downgrade without bricking.
Click to expand...
Click to collapse
KJ said:
I'll just add my two cents as well....as perfectly said already above....I'll just add....
NO. Do not ever try to downgrade to any version if you are on 4.4.2 or higher already. Unless you don't care at all if you brick and have the cash for a new phone or an old phone you'd be happy using again.
No. Some will debate this, and they should keep it to themselves.....unless they are offering to replace your phone if their advice bricks you. ?
Click to expand...
Click to collapse
Sorry, quoted because I wanted to try and emphasize this advice... and add...
The GPT.BIN in 4.4.3 has been updated as well.. so Once you have either 4.4.2 or 4.4.3 on your phone, DO NOT ATTEMPT TO DOWNGRADE!!!
If you try and downgrade only "parts" things wont work properly... example: Those who had 4.4.2 and downgraded only system.img and boot.img found issues going settings -> security... (it kicked them out). And other flakey things happened. When they attempted to update, things got worse.
4.4.4 will likely see updates to motoboot.img(bootloader) and GPT.BIN(partition table)... So the same warnings will apply.
It does NOT matter if your bootloader is unlocked or not. These same warnings and caveats apply!!

KidJoe said:
Sorry, quoted because I wanted to try and emphasize this advice... and add...
The GPT.BIN in 4.4.3 has been updated as well.. so Once you have either 4.4.2 or 4.4.3 on your phone, DO NOT ATTEMPT TO DOWNGRADE!!!
If you try and downgrade only "parts" things wont work properly... example: Those who had 4.4.2 and downgraded only system.img and boot.img found issues going settings -> security... (it kicked them out). And other flakey things happened. When they attempted to update, things got worse.
4.4.4 will likely see updates to motoboot.img(bootloader) and GPT.BIN(partition table)... So the same warnings will apply.
It does NOT matter if your bootloader is unlocked or not. These same warnings and caveats apply!!
Click to expand...
Click to collapse
Good point at the end. After 4.4.2....some thought their unlocked phone was immune to these warnings.....or their dev edition....which every one should know now is no different than any other unlocked phone. Aside from intact warranty.
Great addition KidJoe! Doesn't matter the phone, locked, unlocked or dev edition......none can safely downgrade.
The moto x is nothing like a Nexus in this regard.

[SOLVED]Bootloader bricked, recovered, but fail when running firmware

Hello,
It had the original rom 4.4 on my XT1058 with root and unlocked bootloader, but was not getting running with 4.4.2 update for the original recovery. So I was going to be able to update and run fasthall.bat back to 4.2.2, but I opened the file and rebooted the machine to backup and forgot that it was open. Result: ****ed me.
I believe I have lost my bootloader, but following the tutorial of Gundabolu SC, unable to enter fastboot again, however, I can not run the sbf or RSD by flashall.bat.
I noticed that my phone with this LOCKED status, though I unlocked it.
To start the fastboot I run the code the tutorial I mentioned above, then it displays the following screen
Code:
[COLOR="Red"]Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found[/COLOR]
[COLOR="DarkOrange"]Fastboot Reason: Invalid CID[/COLOR]
For both methods to recovery, it becomes part of gpt.bin and when arrives at motoboot, of the following error message:
Code:
[COLOR="DarkOrange"]getvar max-download-size
downloading 32768 bytes
done
getvar max-download-size
downloading 1643008 bytes[/COLOR]
[COLOR="Red"]downgraded security version
update aboot version failed[/COLOR]
Can anyone help me?
------------
Problem solved thanks to XDA's amazing users!

feelknOck said:
Hello,
It had the original rom 4.4 on my XT1058 with root and unlocked bootloader, but was not getting running with 4.4.2 update for the original recovery. So I was going to be able to update and run fasthall.bat back to 4.2.2, but I opened the file and rebooted the machine to backup and forgot that it was open. Result: ****ed me.
I believe I have lost my bootloader, but following the tutorial of Gundabolu SC, unable to enter fastboot again, however, I can not run the sbf or RSD by flashall.bat.
For both methods, it becomes part of gpt.bin and when arrives at motoboot, of the following error message:
Code:
downgraded security version
aboot version update failed
Can anyone help me?
Click to expand...
Click to collapse
You can try go to this link Hope it helps
http://forums.androidcentral.com/mo...7371-unroot-unbrick-your-phone-using-sbf.html
---------- Post added at 04:31 PM ---------- Previous post was at 04:18 PM ----------
Did it worked??S i am too not quite sure about this??

manav113 said:
You can try go to this link Hope it helps
http://forums.androidcentral.com/mo...7371-unroot-unbrick-your-phone-using-sbf.html
Click to expand...
Click to collapse
I tried to recover via RSD several times, both with 4.4, as 4.2.2, but both have the same error.
In the RSD panel the following error message:
Code:
Failed flash process. 2/13 flash mootboot "motoboot.img" -> Phone returned FAIL.

quite a different error.NEVER heard of it>Wait let me ask my friends about it..

manav113 said:
quite a different error.NEVER heard of it>Wait let me ask my friends about it..
Click to expand...
Click to collapse
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.

dray_jr said:
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
Click to expand...
Click to collapse
I'm downloading and post the result. 202 KB/s
Thank you!
-

dray_jr said:
the issue is the bootloader you are trying to install dose not match the one installed so it will fail everytime we have to find the right one to get everything installed correct
so we need to grab the 100% correct firmware package for your phone.
the model you gave me is for the AT&T version
here is the 4.4 AT&T firmware try installing this one
http://sbf.droid-developers.org/download.php?device=0&file=4
let me know the outcome.
Click to expand...
Click to collapse
Sorry for double post there.
I remember that my device is the XT1058, but Brazil.
I downloaded the sbf, removed the max-download-size and run the RSD, but he brought me the same errors.

Sounds like you need to wait for the full 4.4.2 Brazil image to be posted for download to recover the phone.

Steve-x said:
Sounds like you need to wait for the full 4.4.2 Brazil image to be posted for download to recover the phone.
Click to expand...
Click to collapse
Excuse me, but why do you think?
I did not get to install 4.4.2, I started to run the script flashall.bat 4.2.2 and thinking it would give time, it ended up damaging the bootloader.
Tried the firm indicated that dray_jr and 2 BR's, but it did not work.
I am very worried.

Did you try this, sounds like your trying to flash 4.2.2 firmware over 4.4.2 which won't work http://forum.xda-developers.com/showthread.php?t=2628940
Sent on my Gummy running Lenoto X

Do you get the "downgraded security version" error when trying to flash 4.2.2 and 4.4 ?

flashallthetime said:
Did you try this, sounds like your trying to flash 4.2.2 firmware over 4.4.2 which won't work http://forum.xda-developers.com/showthread.php?t=2628940
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I was going to try and probably would work (I've done this several times and has no secret), but it was not to start. I opened flashall.bat script but forgot to close it, because it was going back up yet, but the script detected the fastboot and started the process.
With seconds I removed the cable, barely gave it to start the first stage (before I left without turning back) and corrupted my bootloader.
I had the Original ROM 4.4 installed with root and unlocked bootloader, but even trying the 4.4 firmware I get the errors I described above.
Would have something to do with the tutorial I follow to start the fastboot?
I am Brazilian and even translating and reading what little I understand, I can not identify a problem as well. I'm scouring all here and trying something, but like I said, I am a layman and do not understand how the bootloader and related work.
Steve-x said:
Do you get the "downgraded security version" error when trying to flash 4.2.2 and 4.4 ?
Click to expand...
Click to collapse
With 2 firmwares I get the same error.

everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.

dray_jr said:
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
Click to expand...
Click to collapse
He removed the cable as it was flashing, can you get to the fastboot screen?
Sent on my Gummy running Lenoto X

dray_jr said:
everytime i post here i reread the first thread and i am still not sure what you did.
so im going to ask some questions and see if we can't get some more info on this issue
1. Your device was 4.4 unlocked bootloader and rooted
2. did you try and install the 4.4.2 firmware
3. your device is the AT&T model but from Brazil
because if you are getting the gpt error on both 4.2.2 and 4.4 and it would lead me to think that the 4.4.2 bootloader is installed on your device.
Click to expand...
Click to collapse
1. Yes, I was running 4.4 with unlocked bootloader and rooted
2. I installed the original recovery to try the OTA update for version 4.4.2, but he returned me error halfway through the update, because my ROM was modified. That's when I thought of going back to 4.2.2 without changes and run the 4.4.2.
3. My device is the XT1058 Retail Brazil.
flashallthetime said:
He removed the cable as it was flashing, can you get to the fastboot screen?
Click to expand...
Click to collapse
Yes, I can start the fastboot via script "qflash.exe with (PORT NUMBER)-ramload MPRG8960.hex-mbn 33 MSM8960_bootloader_singleimage.bin-v-o" with a blank bootloader.

feelknOck said:
1. Yes, I was running 4.4 and unlocked bootloader routed.
2. I installed the original recovery to try the OTA update for version 4.4.2, but he returned me error halfway through the update, because my ROM was modified. That's when I thought of going back to 4.2.2 without changes and run the 4.4.2.
3. My device is the XT1058 Retail Brazil.
Yes, I can start the fastboot via script "qflash.exe with (PORT NUMBER)-ramload MPRG8960.hex-mbn 33 MSM8960_bootloader_singleimage.bin-v-o" with a blank bootloader.
Click to expand...
Click to collapse
ok if i remember well first flash recovery from 4.4 firmware
mfastboot flash recovery recovery.img
after then u ll be able to flash entire image of 4.4.2

could it be that even thou the 4.4.2 update failed that it still installed the new bootloader and that is why nothing else will install.
but either way he could flash the 4.4 firmware without the gpt file and then take the OTA and everything should be fine.

danger2u said:
ok if i remember well first flash recovery from 4.4 firmware
mfastboot flash recovery recovery.img
after then u ll be able to flash entire image of 4.4.2
Click to expand...
Click to collapse
Before having this problem I tried all that.
I installed the original recovery and tried to upgrade to 4.4.2 but it gave error in the middle of the update and restarted the phone saying that the software update was not completed.

dray_jr said:
could it be that even thou the 4.4.2 update failed that it still installed the new bootloader and that is why nothing else will install.
but either way he could flash the 4.4 firmware without the gpt file and then take the OTA and everything should be fine.
Click to expand...
Click to collapse
I will remove the line from gpt and try again.
Earlier I was testing at work and now I'm home. The 4.4 firmware download this lingering: (

you really can't cause anymore problems so this is what i would try because from what i have read if you try to install 4.2.2 or 4.4 you the a gpt.bin verification error. which means that neither 4.2.2 or 4.4 are the right bootloader.
That leaves us with some how the 4.4.2 bootloader got installed because it is the only bootloader that can't go to 4.4 so with that being said.
I would download the correct 4.4 firmware for your phone.
extract it
and use the below adb commands to install it but leave out the gpt.bin flash command
Code:
*leave this one out*fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i think everything should install fine and your phone should boot up and from what i have read you should still be able to take the 4.4.2 OTA without bricking your phone

[Q] Please help in unbricking Atrix HD MB886

Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?

capricorn85 said:
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
Click to expand...
Click to collapse
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.

skeevydude said:
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
Click to expand...
Click to collapse
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......

capricorn85 said:
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
Click to expand...
Click to collapse
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).

skeevydude said:
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
Click to expand...
Click to collapse
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...

capricorn85 said:
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
Click to expand...
Click to collapse
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.

skeevydude said:
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
Click to expand...
Click to collapse
Came here after trying all that
Tried manually flashing but the phone returns FAIL on EVERY command, same with myth tools it executes but nothing really happen in the phone, dont know what went so wrong with the OTA
i am just confused if i should let it be or keep trying until i find a solution
COuld battery charge level be the problem, when it all started it was more than 70 percent and i didnt keep it on for long. it says battery ok but dont know whats the exact battery level as fastboot oem battery-status or voltage level are also restricted

Well, it seems that skeevydude told you all I want to say

Solved: Using Nextel (Mex Retail)
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue

capricorn85 said:
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
Click to expand...
Click to collapse
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?

palmbeach05 said:
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
Click to expand...
Click to collapse
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion

capricorn85 said:
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
Click to expand...
Click to collapse
I told ya Mex Retail would work....

skeevydude said:
I told ya Mex Retail would work....
Click to expand...
Click to collapse
It is worth a shot for me too!
I have RSDLite and attempted to flash. It gives me error about unknown <getvar>. Deleted those line(s) according to another post I found.
Then everything passes but I am stuck on the Fastboot Flash Mode?
God I will be happy when uncle same gets through with my son so he can help is ole man, lol.
---------- Post added at 06:14 PM ---------- Previous post was at 05:55 PM ----------
PROGRESS! I recalled skeevydude saying to stay alway from front USB ports and moved to back one and I now also have the Mex Retail version working. What a relief.
Now the bearing question is should I move on to another version like carbon or holoblur?
If ok to stay with this version, meaning will NOT get busted out by AT&T by using hotspot?
What do you recommend skeevydude?
Thank you so so so much.
Woody

Mexico Retail link
can someone provide me any link of Mexico Retail stock rom? Please.

ErickST18 said:
can someone provide me any link of Mexico Retail stock rom? Please.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=7

quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Thanks man

Pleas hlep me for alive my set thanks advance
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English

shamshadhashmi said:
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
Click to expand...
Click to collapse
Please stop whining and being pathetic and actually search for moto sbf files. A new site popped up and comes up very easily. No need to make us die of laughter at someone begging for an sbf like a guy begging to get with a girl b/c he's thirsty. Smh lol
Sent from my ATRIX HD using XDA Free mobile app

need working link of file
i search everywhere but no file found i need file if anybody have so please share with me or upload thanks

quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Need 4.1.1..where can I find it? Tyvm

[Q] Locked/Unrooted Phone Decided to Brick Itself

I'm not entirely sure how to troubleshoot this problem, but here goes...
I was charging my phone and it just attempted to reboot itself. I saw it in the corner of my eye and figured "oh well, let it finish". It never finished, and it seems it won't get past the boot screen.
I entered Fastboot mode. Device is still locked. It also states that the charger is connected, regardless of whether it is or isn't. Additionally, I cannot access Recovery or Factory, instead receiving the following error:
No valid PIV block in SP for system
piv validation failed (system)
Boot up failed
Click to expand...
Click to collapse
Anyone know what's going on here? Did my phone really just brick itself?
Edit: I apologize if my first post goes against any of the rules here. I've searched for a similar thread, but mostly found cases in which people failed to root and are receiving this message. I have some minor experience with rooting a Motorola Droid, Verizon Droid Incredible 2 and a Nexus 10. I was hoping to do the same with this phone, but it came with 4.4.2 already installed.

Don't take my word for it, but if you Google no valid piv moto x....it doesn't look good.
Then again if you read through some of the stuff you find, even other phones with issue....perhaps you'll stumble on a fix.
Last moto x thread I read with that error was solved by a replacement unfortunately.
Hope you find a fix, or can send it in. Your warranty should be in tact if its locked and unrooted.

As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition

SymbioticGenius said:
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
Click to expand...
Click to collapse
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!

samwathegreat said:
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
Click to expand...
Click to collapse
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?

ed0421 said:
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
Click to expand...
Click to collapse
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.

samwathegreat said:
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
Click to expand...
Click to collapse
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!

I didn't have the same issue but I did just RMA my X for another reason and got a brand new 2014 X, was expecting a refurbished phone and was surprised to get a new one. They shipped it next day air that same day which also surprised me.

ed0421 said:
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
Click to expand...
Click to collapse
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat

samwathegreat said:
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
Click to expand...
Click to collapse
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated

ed0421 said:
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
Click to expand...
Click to collapse
Really dumb question but when flashing... Are you using the command fastboot or mfastboot?
I had all kinds of errors and thought I was bricked too until I used mfastboot. Then everything went perfect. Moto uses their own version of fastboot.exe that's included in the sbf/fxz or whatever they are called now. Even the XML file states fastboot as the command but never worked for me. Just a thought.