Tried to flash T-Mobile 4.4.3 firmware onto locked XT1058 - Moto X Q&A

New to the Moto X and Android in general.
Have a SIM unlocked XT1058 but without realizing that I had locked bootloader, I attempted to flash using RSD Lite the T-Mobile (my carrier) 4.4.3 stock firmware and think I've bricked my phone..
Tried to revert back to the AT&T 4.4.2 stock firmware but at each turn I get the "security version downgraded" error; first when trying to gpt.bin (took that out the .xml) then boot.img (took that line out the .xml) and then finally at system.img turn..
At this point I'm thinking I'm screwed unless I can get an ATT firmware to load that is on the same "security version" as the botched 4.4.3 attempt..
Am I right or do I have any other options to get a working Moto X?
Thanks in advance, spent the better part of the evening trying to [email protected]#$ myself but I'm tired and need a hand from the pros..

blackout420 said:
New to the Moto X and Android in general.
Have a SIM unlocked XT1058 but without realizing that I had locked bootloader, I attempted to flash using RSD Lite the T-Mobile (my carrier) 4.4.3 stock firmware and think I've bricked my phone..
Tried to revert back to the AT&T 4.4.2 stock firmware but at each turn I get the "security version downgraded" error; first when trying to gpt.bin (took that out the .xml) then boot.img (took that line out the .xml) and then finally at system.img turn..
At this point I'm thinking I'm screwed unless I can get an ATT firmware to load that is on the same "security version" as the botched 4.4.3 attempt..
Am I right or do I have any other options to get a working Moto X?
Thanks in advance, spent the better part of the evening trying to [email protected]#$ myself but I'm tired and need a hand from the pros..
Click to expand...
Click to collapse
hi,
at first you cant flash another firmware than the xt1058 firmware. DONT FLASH ANOTHER FIRMWARE.
Now to your problem.
open the xml and delete the following lines:
<step operation="getvar" var="max-download-size" />
...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxx" />
then save it and use rsd lite to flash the "xt1058 firmware"!!!!!!! not tmobile OK?

nexuspur said:
hi,
at first you cant flash another firmware than the xt1058 firmware. DONT FLASH ANOTHER FIRMWARE.
Now to your problem.
open the xml and delete the following lines:
<step operation="getvar" var="max-download-size" />
...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxxxxxxxxxxxxxxxxxxxxx" />
then save it and use rsd lite to flash the "xt1058 firmware"!!!!!!! not tmobile OK?
Click to expand...
Click to collapse
Thanks for the response!
When I try the above, in RSD Lite I get: "Failed flashing process. 3/15 flash boot "boot.img" -> Phone returned FAIL
And on the phone itself I get: Partition (boot) Security Version Downgraded preflash validation failed for boot

blackout420 said:
Thanks for the response!
When I try the above, in RSD Lite I get: "Failed flashing process. 3/15 flash boot "boot.img" -> Phone returned FAIL
And on the phone itself I get: Partition (boot) Security Version Downgraded preflash validation failed for boot
Click to expand...
Click to collapse
And to clarify, what got me into this mess was trying to flash on my AT&T branded XT1058 the firmware from the Moto site called:
<phone_model model="PRO_CFC_TMO" />
<software_version version="ghost_retail-user 4.4.3 KXA21.12-L1.21 23 release-keysMSM8960PRO_BP_2323.038.123.00R" />
It failed for giving some message that when looked up tells me it's because I have locked bootloader.
I then try to re-flash the original AT&T 4.4.2 firmware from the Moto site but it looks like the failed upgrade to Tmob fw did some partial update to e security version which is now preventing me from getting out of this loop when trying:
<phone_model model="PRO_CFC_ATT" />
<software_version version="ghost_att-user 4.4.2 KXA20.16-1.31.1 1 bldacfg,release-keysMSM8960PRO_BP_2323.031.111.00R" />

@blackout420
I'm surprised that with a locked bootloader, the XT1053 firmware even flashed to your XT1058. Usually with a locked bootloader, it fails to flash any rom not for your model.
In any case... now, you are experiencing one of the main causes of bricking... Attempting to downgrade (i.e. you had 4.4.3 on your phone, and you are trying to flash 4.4.2).
Long story short... GPT.BIN is the partition table of the phone, Motoboot.img contains the bootloader and other parts. You are running into problems flashing a lower version because security restrictions on the phones don't let you downgrade them.
Ideally, we'd say grab the SBF/FXZ of the latest version you had on your phone (in this case 4.4.3) for your carrier and model. Unfortunately, there is no ATT 4.4.3, and an ATT 4.4.4 SBF/FXZ hasn't leaked yet.
In this case, you can attempt what @nexuspur is suggesting. Take the ATT 4.4.2 SBF, edit its XML to skip flashing GPT.BIN and MOTOBOOT.IMG, and flash using RSDLite (because its easier)... or you can do the same to manually flash using moto's fasboot (aka mfastboot).
Be aware... this is NOT fool proof, nor is it 100% safe. And you do NOT want to take an OTA in this state. We've seen enough bricking and other issues due to mismatched GPT.BIN and MotoBoot.IMG compared to the rest of the rom/files on the phone that I really don't like suggesting it, unless it is a last resort. For more, see -> http://forum.xda-developers.com/mot...rrecting-bricked-moto-x-t2629057/post55004649
BUT this is the only option until the 4.4.4 SBF for your phone model and carrier leaks and gets posted to -> http://sbf.droid-developers.org/phone.php?device=0 Once it does, I suggest using it to flash back to stock (follow option 5 on -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you do want to run the XT1053 ROM on your XT1058 (again, something I don't suggest because I've seen too many problems come up), check out the China Middleman thread in the general section and see if you can get your bootloader unlock code.

blackout420 said:
Thanks for the response!
When I try the above, in RSD Lite I get: "Failed flashing process. 3/15 flash boot "boot.img" -> Phone returned FAIL
And on the phone itself I get: Partition (boot) Security Version Downgraded preflash validation failed for boot
Click to expand...
Click to collapse
have you got the untouched xml or have you edited the xml before?
if you have edited the xml before grap an untouched xml and re-do the steps.

nexuspur said:
have you got the untouched xml or have you edited the xml before?
if you have edited the xml before grap an untouched xml and re-do the steps.
Click to expand...
Click to collapse
@nexuspur I've been using both, keeping the untouched one where I extracted the full zip and then moving over the contents to the \platform-tools\ folder, updating the .xml as suggested and then picking it when running RSD Lite... to no avail.
100% appreciate everyone's input, would like to try other things if anyone else has any ideas.. but it's looking like what @KidJoe suggests is what I'll need to wait for - an official ATT firmware to flash that has the security stuff at or higher than my 4.4.3.

blackout420 said:
@nexuspur I've been using both, keeping the untouched one where I extracted the full zip and then moving over the contents to the \platform-tools\ folder, updating the .xml as suggested and then picking it when running RSD Lite... to no avail.
100% appreciate everyone's input, would like to try other things if anyone else has any ideas.. but it's looking like what @KidJoe suggests is what I'll need to wait for - an official ATT firmware to flash that has the security stuff at or higher than my 4.4.3.
Click to expand...
Click to collapse
for me it has worked.
And I have got an unlocked bootloader btw.

Related

How to unlock&root my Puerto Rico Moto X(XT1058)?

It is the information I get below:
Baseband version:
MSM8960PRO_BP_2323.011.75.00R
Kernel Version:
3.4.4.2-xline-gfd1a699-00157-gfb2f8fc [email protected] #1 Thu Jul 18 22:37:58 CDT 2013
System Version:
139.7.26.ghost_row.AmericaMovil.en.PR
Build number:
13.9.0q2.x-116-LCX-26
Is it actually the same as the AT&T one? But I try to install motoroot and it can't be installed.
Please help!
Unlock here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Flash recovery, upon rebooting from recovery it will ask if you want to root.
mentose457 said:
Unlock here:
Flash recovery, upon rebooting from recovery it will ask if you want to root.
Click to expand...
Click to collapse
Is it possible to use PWNmymoto or Motoroot to do the root stuff?
And is it possible to flash t-mobile version on it?
I would do a search in the pwnmymoto root thread about routing it that way.
Sent from my Moto X.
There is no need in using pwnmymoto, especially because there is no pwnmymoto for PR phones - definitely the unlock bootloader thing from motorola is more stable. After it's unlocked, flashing the recovery is very easy. Having a PR phone myself, I can confirm CWM Recovery working and SuperSU root as well after the official bootloader unlock.
rchik said:
There is no need in using pwnmymoto, especially because there is no pwnmymoto for PR phones - definitely the unlock bootloader thing from motorola is more stable. After it's unlocked, flashing the recovery is very easy. Having a PR phone myself, I can confirm CWM Recovery working and SuperSU root as well after the official bootloader unlock.
Click to expand...
Click to collapse
Thank you very much. Have you tried to flash AT&T's rom on it? It seems like the same.
What if I want to do the update/flash stock image after unlocked? Is there any source for PR phone?
chrisjenho said:
Thank you very much. Have you tried to flash AT&T's rom on it? It seems like the same.
What if I want to do the update/flash stock image after unlocked? Is there any source for PR phone?
Click to expand...
Click to collapse
You should be able to flash the AT&T ROM without any problems, I have flashed mine with the T-Mobile ROM.
If you want to go back to the AmericaMovil.PR stock ROM, u can find it here:
http://sbf.droid-developers.org/ghost_rcica/list.php
mschumacher69 said:
You should be able to flash the AT&T ROM without any problems, I have flashed mine with the T-Mobile ROM.
If you want to go back to the AmericaMovil.PR stock ROM, u can find it here:
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
PR rom is pre-camera OTA. You can not flash back to that if you flashed any post-camera OTA roms as the bootloader can not be downgraded.
yghrv said:
PR rom is pre-camera OTA. You can not flash back to that if you flashed any post-camera OTA roms as the bootloader can not be downgraded.
Click to expand...
Click to collapse
Afaik, if u've unlocked ur bootloader, you can flash whatever u want including downgrading...
People have also managed to downgrade from 4.4 to 4.2.2 on locked bootloader phones...
mschumacher69 said:
Afaik, if u've unlocked ur bootloader, you can flash whatever u want including downgrading...
People have also managed to downgrade from 4.4 to 4.2.2 on locked bootloader phones...
Click to expand...
Click to collapse
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
yghrv said:
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
Click to expand...
Click to collapse
Again, this is if your bootloader is locked.
If you have an unlocked bootloader, you should be able to flash any ROM including downgrading to pre-camera OTA ROM.
mschumacher69 said:
Again, this is if your bootloader is locked.
If you have an unlocked bootloader, you should be able to flash any ROM including downgrading to pre-camera OTA ROM.
Click to expand...
Click to collapse
yes I'm talking about unlocked bootloader. not continue to the debate, u can try it out but I it's my opinion that u might brick the phone.
yghrv said:
yes I'm talking about unlocked bootloader. not continue to the debate, u can try it out but I it's my opinion that u might brick the phone.
Click to expand...
Click to collapse
I don't think so. What's the point in unlocking your bootloader if u can't downgrade??
mschumacher69 said:
I don't think so. What's the point in unlocking your bootloader if u can't downgrade??
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/showthread.php?t=2548867
I've seen several guys bricked the phone as they tried to downgrade to pre camera OTA 4.2.2 from 4.4.
of coz with unlocked bootloader.
yghrv said:
check this out
http://forum.xda-developers.com/showthread.php?t=2548867
I've seen several guys bricked the phone as they tried to downgrade to pre camera OTA 4.2.2 from 4.4.
of coz with unlocked bootloader.
Click to expand...
Click to collapse
This guy didn't brick because he downgraded back to pre camera OTA, he successfully downgraded back to pre-camera OTA but he bricked after installing the OTA.
Why? Because he did all sorts of things to his phone before installing the OTA including installing custom recovery, rooting, installing a custom logo and all sorts of other things and he didn't even flash the full stock ROM before taking the OTA.
We all know that you shouldn't take an OTA unless you go back to 100% stock first
mschumacher69 said:
This guy didn't brick because he downgraded back to pre camera OTA, he successfully downgraded back to pre-camera OTA but he bricked after installing the OTA.
Why? Because he did all sorts of things to his phone before installing the OTA including installing custom recovery, rooting, installing a custom logo and all sorts of other things and he didn't even flash the full stock ROM before taking the OTA.
We all know that you shouldn't take an OTA unless you go back to 100% stock first
Click to expand...
Click to collapse
You can see from the thread. The old bootloader can not be flashed and he skipped that step. I think this is actually why get bricked after trying to OTA.
Erased from XML files the following lines BECAUSE RSD LITE SHOWED ERROR ACCORDING TO THIS LINES:
“step operation=”getvar” var=”max-download-size”
<step operation="flash" partition="partition" filename="gpt.bin" MD5="A_LOT_OF_NUMBERS_HERE" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="A_LOT_OF_NUMBERS_HERE" />
yghrv said:
You can see from the thread. The old bootloader can not be flashed and he skipped that step. I think this is actually why get bricked after trying to OTA.
Erased from XML files the following lines BECAUSE RSD LITE SHOWED ERROR ACCORDING TO THIS LINES:
“step operation=”getvar” var=”max-download-size”
<step operation="flash" partition="partition" filename="gpt.bin" MD5="A_LOT_OF_NUMBERS_HERE" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="A_LOT_OF_NUMBERS_HERE" />
Click to expand...
Click to collapse
Probably, as I said, you should never take an OTA if u're not 100% stock.
yghrv said:
You should be noted that they downgrade from 4.4 to 4.2.2 post-camera OTA roms as they have the same bootloader. Try downgrade to pre-camera OTA rom may cause the phone bricked. Have seen several threads talking about this.
Click to expand...
Click to collapse
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Yes. That's what I'm talking about. Bootloader downgrade not supported for this model, even unlocked bootloader. @mschumacher69
I think for latin America XT1058s, can be flashed to stock with ATT or Rogers post camera OTA 4.2.2 sbf from 4.4 instead using the original one which are most pre camera OTA.
flashallthetime said:
Yes you are correct, you can not downgrade to the per camera firmware, regardless if you are running a unlocked boot loader, gpt.bin failure , I tried and failed and under no circumstance remove the gpt. bin line in the XML file as you will hard brick your device 100% guaranteed
Click to expand...
Click to collapse
So that's why he bricked, because he didn't flash gpt.bin not because he attempted to downgrade to pre-ota 4.2.2. Attempting to flash the pre-ota 4.2.2 might fail, but it will not brick, correct?

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

How to get MSL/SPC?

I have contacted Sprint they just gave me a big headache since it's not activated wit them. It's on Android 4.4.4. Thanks in advance.
Precarious27 said:
I have contacted Sprint they just gave me a big headache since it's not activated wit them. It's on Android 4.4.4. Thanks in advance.
Click to expand...
Click to collapse
There is a spc.apk around.
aviwdoowks said:
There is a spc.apk around.
Click to expand...
Click to collapse
It doesn't work on 4.4.4...
samwathegreat said:
It doesn't work on 4.4.4...
Click to expand...
Click to collapse
So there is no known way?
Precarious27 said:
So there is no known way?
Click to expand...
Click to collapse
Maybe flash a 4.4.2 ROM with twrp. I wouldn't dare do that until the entire 4.4.4 sbf is released. Otherwise that isn't safe.
Don't dare downgrade to the 4.4.2 sbf or you will very likely brick.
Hopefully the sbf is released soon, and you can safely flash a twrp 4.4.2 ROM. ONLY FROM TWRP. Otherwise not safe.
Again, please wait until the full 4.4.4 sprint sbf is released, otherwise you might not be able to return to stock.
samwathegreat said:
Maybe flash a 4.4.2 ROM with twrp. I wouldn't dare do that until the entire 4.4.4 sbf is released. Otherwise that isn't safe.
Don't dare downgrade to the 4.4.2 sbf or you will very likely brick.
Hopefully the sbf is released soon, and you can safely flash a twrp 4.4.2 ROM. ONLY FROM TWRP. Otherwise not safe.
Again, please wait until the full 4.4.4 sprint sbf is released, otherwise you might not be able to return to stock.
Click to expand...
Click to collapse
What if a Sprint Moto X out the box came with 4.2.2, was bootloader unlocked via Motorola, TWRP'ed, rooted and then a nandroid was made of the stock 4.2.2. Then 4.4.4 was flashed via TWRP, and now the Moto X is on 4.4.4. I keep seeing calamitous warnings about not downgrading to 4.4.2 specifically else you brick your device. Would the same warning apply to attempting to restore back to the 4.2.2 backup, just out of curiosity?
LordLugard said:
What if a Sprint Moto X out the box came with 4.2.2, was bootloader unlocked via Motorola, TWRP'ed, rooted and then a nandroid was made of the stock 4.2.2. Then 4.4.4 was flashed via TWRP, and now the Moto X is on 4.4.4. I keep seeing calamitous warnings about not downgrading to 4.4.2 specifically else you brick your device. Would the same warning apply to attempting to restore back to the 4.2.2 backup, just out of curiosity?
Click to expand...
Click to collapse
The problem is with gpt.bin (the partition table) and motoboot.img (the bootloader). Neither of those are downwardly. So if you ever took an ota, you updated both of them. This causes problems both ways: if your android version doesn't match the BL or partition table you are at extreme risk of a brick. Sometimes it happens immediately and sometimes it happens after one or two otas.
Always best to use caution.
Twrp flashing is safe because it doesn't touch either! Twrp backups only flash system and boot.
The warnings apply to ANY version unless twrp is used.
samwathegreat said:
The problem is with gpt.bin (the partition table) and motoboot.img (the bootloader). Neither of those are downwardly. So if you ever took an ota, you updated both of them. This causes problems both ways: if your android version doesn't match the BL or partition table you are at extreme risk of a brick. Sometimes it happens immediately and sometimes it happens after one or two otas.
Always best to use caution.
Click to expand...
Click to collapse
Good stuff, as always.
Thing is i never took an OTA. Went straight from 4.2.2 to 4.4.4 by just flashing the entire KitKat 4.4.4 stock ROM System Version: 212.44.28 found here... http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594
LordLugard said:
Good stuff, as always.
Thing is i never took an OTA. Went straight from 4.2.2 to 4.4.4 by just flashing the entire KitKat 4.4.4 stock ROM System Version: 212.44.28 found here... http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594
Click to expand...
Click to collapse
Did you flash the ROM or the firmware? If you flashed the ROM from twrp, you are totally safe to flash down to 4.4.2, read the msl and then flash back to 4.4.4.
If you flashed the FIRMWARE you updated the BL and partition table and you risk bricking.
samwathegreat said:
Did you flash the ROM or the firmware? If you flashed the ROM from twrp, you are totally safe to flash down to 4.4.2, read the msl and then flash back to 4.4.4.
If you flashed the FIRMWARE you updated the BL and partition table and you risk bricking.
Click to expand...
Click to collapse
Don't think there was a separate firmware, just the ROM only. (I did have to fastboot NON-HLOS.bin and fsg.mbn manually though).
Anyway, not trying to push my luck here so i'll just stay put, but i was just curious.
LordLugard said:
Don't think there was a separate firmware, just the ROM only. (I did have to fastboot NON-HLOS.bin and fsg.mbn manually though).
Anyway, not trying to push my luck here so i'll just stay put, but i was just curious.
Click to expand...
Click to collapse
You are correct, the firmware for 4.4.4 isn't available yet. The NON-HLOS and fsg are the modem. You should be completely safe. Use caution none the less.
Good luck
Is there any updated spc.apk kind of thing for 4.4.4 ?
gc33 said:
Is there any updated spc.apk kind of thing for 4.4.4 ?
Click to expand...
Click to collapse
No.
samwathegreat said:
No.
Click to expand...
Click to collapse
When there is, where would we find it?
I have verizon moto g xt1028 so downgrade is not successful ... Any idea how to get spc as its has 4.4.4 ?
gc33 said:
I have verizon moto g xt1028 so downgrade is not successful ... Any idea how to get spc as its has 4.4.4 ?
Click to expand...
Click to collapse
There is no known way. There might never be a way. (to get SPC once on 4.4.4, that is....)
samwathegreat said:
Did you flash the ROM or the firmware? If you flashed the ROM from twrp, you are totally safe to flash down to 4.4.2, read the msl and then flash back to 4.4.4.
If you flashed the FIRMWARE you updated the BL and partition table and you risk bricking.
Click to expand...
Click to collapse
Hi, i flash 4.4.2 and 4.4 via TWRP and still cant read MSL =( look for screenshots
YEEEEEEHHHAAA i got it, pushed to my 4.4.4 radio from 4.4.2 via RSD lite
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="PRO_CFC_SPRINT" />
<software_version version="ghost_sprint-user 4.4.2 KXA20.16-1.32 37 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<sparsing enabled="false" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="48BFA7086A66EFC79CA609F29CD89291" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="63225D160B529B1C4AB52972E885DE67" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="config carrier sprint" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
add an update guide:
http://forum.xda-developers.com/moto-x/general/guide-how-to-read-moto-x-msl-spc-code-t2681816

[Q] [HELP]Probably bricked my XT1058 CA Rogers

Problem SOLVED! Android 5.1 stock ROM revived it! Thank you, Motorola and XDA!
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!
Try and flash tz and gpt from 4.4.4
mk1129 said:
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!
Click to expand...
Click to collapse
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
I tried several 4.4.4 stock ROMs, but no luck at the very beginning on gpt. What's tz, BTW?
Thank you anyway.
KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!
hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
It's weird that my reply to your PM cannot be found in my Sent items box and hope you may get my response.
KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy
yeah i wouldnt phuk with her like that, prob is gpt
mk1129 said:
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!
Click to expand...
Click to collapse
mk1129 said:
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy
Click to expand...
Click to collapse
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.
KidJoe said:
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.
Click to expand...
Click to collapse
Agree. I'd wait for the Lollipop SBF, then. Thanks!
I suddenly realized that I encrypted the phone when it's on 4.4.2 before playing with various SBFs, and that may be the reason why I cannot write anything any more....
I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.
thehanutedtubby said:
I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.
Click to expand...
Click to collapse
Thanks for the tips! You''re lucky! BTW, Where did you get the 5.02 GPT? from Brazil XT1058 soak test leak?
And yes, I'm really expecting the full lollipop stock rom to have a final try to save mine. I only heard Brazil XT1058 has the soak test for 5.02 and am wondering if I can leverage that...
Problem SOLVED! Android 5.1 stock ROM (XT1058_GHOST_RCICA_5.1_LPA23.12-15_cid14_CFC_xml) revived it!
Thank you, Motorola and XDA!

[Q] Invalid CID MOTO X XT1058

After attempting to upgrade rom stock KIT KAT 4.4.4 to 5.0.2 Lollipop over the air, I can not start the cell.
It is only on this screen "Fastboot Reason: Invalid CID".
It is not possible to go into bootloader, Flash attempts unsuccessfully by RSD Lite 6.1.5 and mfasboot.
In this case how to proceed.
View attachment 3306441
Looks more like you tried to downgrade which you cannot do
renatomuniz2015 said:
After attempting to upgrade rom stock KIT KAT 4.4.4 to 5.0.2 Lollipop over the air, I can not start the cell.
It is only on this screen "Fastboot Reason: Invalid CID".
It is not possible to go into bootloader, Flash attempts unsuccessfully by RSD Lite 6.1.5 and mfasboot.
In this case how to proceed.
View attachment 3306441
Click to expand...
Click to collapse
@WillisD is 100% correct...
Notice the message in the first shot?
Code:
downgraded security version
update gpt_main version failed
preflash vaildation failed for GPT
And the shot showing the top of the AP Fastboot screen shows 30.BC which is the bootloader version for the leaked test/soak 5.02...
You attempted to downgrade, and the phone doesn't like it.
Please see -> http://forum.xda-developers.com/mot..., and the impacts of GPT.BIN and MOTOBOOT.IMG
At this point, if your phone is saying Invalid CID and stops when it tries to boot, you are likely stuck until a 5.1 SBF for your phone/carrier leaks, and you can mfastboot fash it. It is the only SAFE way.
There might be other ways (look in the threads discussing the leaked 5.02), but I wont suggest them as they wont take you back to 100% stock, and also introduce version mismatches on your phone which could cause problems/issues.
You need flash moto boot and bootloader from 5.0.2 ota files and later can flash stock 4.4.4 me too brick my phone ..... And solved
flashed boot and bootloader from 5.0.2 and worked well, thanks makysssdroid
eldar4uk said:
flashed boot and bootloader from 5.0.2 and worked well, thanks makysssdroid
Click to expand...
Click to collapse
Just do NOT take any future OTA's if you're now running a gpt.bin and motoboot.img from a different rom than you are now running on your phone. If history is any indication, you are very likely to brick in this situation.
makysssdroid said:
You need flash moto boot and bootloader from 5.0.2 ota files and later can flash stock 4.4.4 me too brick my phone ..... And solved
Click to expand...
Click to collapse
Bro,
Can you help me?
My phone is XT1056, and i am having the same error as you were,
Can you suggest me what to do?
I was on android 4.4.4, and by mistake i installed the Security Update,
after that my phone was i this state.
KidJoe said:
@WillisD is 100% correct...
Notice the message in the first shot?
Code:
downgraded security version
update gpt_main version failed
preflash vaildation failed for GPT
And the shot showing the top of the AP Fastboot screen shows 30.BC which is the bootloader version for the leaked test/soak 5.02...
You attempted to downgrade, and the phone doesn't like it.
Please see -> http://forum.xda-developers.com/mot..., and the impacts of GPT.BIN and MOTOBOOT.IMG
At this point, if your phone is saying Invalid CID and stops when it tries to boot, you are likely stuck until a 5.1 SBF for your phone/carrier leaks, and you can mfastboot fash it. It is the only SAFE way.
There might be other ways (look in the threads discussing the leaked 5.02), but I wont suggest them as they wont take you back to 100% stock, and also introduce version mismatches on your phone which could cause problems/issues.
Click to expand...
Click to collapse
Hi, please, where can i get the latest gpt.bin and boot for a generic xt1058? cause mine is bricked and gpt.bin from every firmware (i tried LATAM, BR, and AR 21.12-15 and the one that last with .7 and it seems like the gpt.bin in those firms its not the last, i had no problem cause i skipped that part everytime, but atm my phone is bricked and i need to reflash bootloader and i cant cause older gpt.bin in the firmwares :S

Categories

Resources