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.

[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] 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.

Expert opinion needed in going back to Stock

Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.

Usama Ahmed said:
Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.
Click to expand...
Click to collapse
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.

samwathegreat said:
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.
Click to expand...
Click to collapse
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?

Usama Ahmed said:
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?
Click to expand...
Click to collapse
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347

samwathegreat said:
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Click to expand...
Click to collapse
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.

Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.

samwathegreat said:
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.
Click to expand...
Click to collapse
Thanks alot for your help. If you think there is even a slight chance of hard brick than i will stay with the current rom i have.
One last question, I you were in my position, would you go for flashing 4.4.4 SBF or would you just leave it as it is?

Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.

KidJoe said:
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.
Click to expand...
Click to collapse
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.

Usama Ahmed said:
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
Click to expand...
Click to collapse
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Usama Ahmed said:
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.
Click to expand...
Click to collapse
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.

KidJoe said:
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.
Click to expand...
Click to collapse
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
Click to expand...
Click to collapse
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.

Usama Ahmed said:
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.
Click to expand...
Click to collapse
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.

KidJoe said:
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.
Click to expand...
Click to collapse
Ok then i will be trying it right now and see what happens.

Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.

Usama Ahmed said:
Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.
Click to expand...
Click to collapse
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!

Excellent support here! @samwathegreat and @KidJoe are GREAT!

KidJoe said:
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!
Click to expand...
Click to collapse
Sorry i didn't realize that. Yes everything part was flashed without error otherwise i wouldn't go further.

But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.

Usama Ahmed said:
But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.
Click to expand...
Click to collapse
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155

KidJoe said:
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155
Click to expand...
Click to collapse
Yes i am not using sprint as my carrier. Thanks alot for the help again. I will try this now and post the result.

[Q] Moto X AT&T is STUCK on Bootloader! [HELP]

Hi guys, yesterday i tried to install ROM "XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml" to my moto X 1058 At&T (android 4.4.4) with RSD litle.
It failed and now i only can turn on the phone and it goes to bootloader menu and i cant do anything. I can connect it to my PC and RSD detect it but i cant put any kind of ROM ((
I know that my moto x is not dead yet i have hope u.u :crying:
Please someone can help me? :crying:
PS: SORRY MY ENGLISH
PS2: I ADD A SCREENSHOT WITH SOME DETAILS ABOUT MY MOTO X after DO what i explain.

First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.

KidJoe said:
First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.
Click to expand...
Click to collapse
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time

NEW INFO
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?

zloopa said:
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time
Click to expand...
Click to collapse
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
zloopa said:
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?
Click to expand...
Click to collapse
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.

KidJoe said:
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.
Click to expand...
Click to collapse
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.

zloopa said:
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.
Click to expand...
Click to collapse
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.

KidJoe said:
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.
Click to expand...
Click to collapse
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone

zloopa said:
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone
Click to expand...
Click to collapse
As I said earlier... flash using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 ) just use that 5.1 SBF... and I would consider including the mfastboot erase userdata command, or doing a factory reset after you flash... Yes it will erase your data, apps, SDCard, etc...

GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it

aamszia said:
GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it
Click to expand...
Click to collapse
Hi in same situation. Did u fixed it?