Database Develop

Tried to flash T-Mobile 4.4.3 firmware onto locked XT1058

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.

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] Moto X stuck in bootloader screen after ota update

Hey guys!
After updating my rooted phone through OTA, it stucked in bootloader screen and every fastboot command I execute results in: FAILED (remote failure)
I tried everything I found and nothing solves the problem.
Please, someone help me!
C:\Fastboot+ADB>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.281s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.172s
Phone status:
Device is LOCKED (It was unlocked early)
Screen message:
downgrade security version
update gpt_main version failed
preflash validation failed for GPT

Did you downgrade your android system any time after 4.2.2?

It sounds like you've downgraded and now took an ota. It's written all over this section of xda that doing that on a Moto X is a guaranteed brick.
If this is the case, you'll want to look for the Resurrect your moto X thread in the general section.
Good luck!

victormagno said:
Hey guys!
After updating my rooted phone through OTA, it stucked in bootloader screen and every fastboot command I execute results in: FAILED (remote failure)
I tried everything I found and nothing solves the problem.
Please, someone help me!
C:\Fastboot+ADB>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.281s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.172s
Phone status:
Device is LOCKED (It was unlocked early)
Screen message:
downgrade security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
What Model X, what version does your bootloader say (2nd line of the FastbootAP/Bootloader screen), and what ROM are you trying to flash?
As suggested, please also be sure you are using Moto's fastboot, rather than stock fastboot from the Android SDK.

How did your bootloader get relocked? The OTA didn't do it so I'm guessing you relocked it for some reason.

Hi, thank you all for your attention, but I solved the problem... I found a Verison Rom with the files I needed \o/.
I'm at work right now, but in home I'll post the solution to help who needs to.
Sorry, my english is awful.
Again, thank you!

nhizzat said:
How did your bootloader get relocked? The OTA didn't do it so I'm guessing you relocked it for some reason.
Click to expand...
Click to collapse
I've seen that happen a few times when some have tried to downgrade.

My phone bricked when I tried to do an OTA update, after downgraded to 4.2.2. When the phone rebooted to compete the upgrade, it stuck on bootloader screen.
I downloaded this Verizon rom in link: h t t p : // sbf.droid - developers . org / download . php ? device = 0&file =9 40 (remove spaces)
and flashed its bootloader. After that, the phone was receiving commands. I restarted and it booted normally.
To solve the problem download this rom and execute: fastboot flash partition gpt.bin
I hope it help someone!

victormagno said:
My phone bricked when I tried to do an OTA update, after downgraded to 4.2.2. When the phone rebooted to compete the upgrade, it stuck on bootloader screen.
I downloaded this Verizon rom in link: h t t p : // sbf.droid - developers . org / download . php ? device = 0&file =9 40 (remove spaces)
and flashed its bootloader. After that, the phone was receiving commands. I restarted and it booted normally.
To solve the problem download this rom and execute: fastboot flash partition gpt.bin
I hope it help someone!
Click to expand...
Click to collapse
I would suggest something slightly different.
I would say.. check the bootloader on your phone, and download the corresponding ROM for your model phone.
Bootloader version = rom version
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Just some model examples...
XT1060 = Verizon Wireless USA
XT1058 = ATT in the USA, Rogers Canada
XT1056 = Sprint in the USA
XT1053 = GSM Dev Edition, as well as the "Unlocked ships with xxx Sim" from Moto's web site (like T-Mobile, Net10, and others).
XT1052 = European, and some Asia.
So if your bootloader is 30.B4 and you have a GSM Unlocked (with T-Mobile SIM), then download and flash the 4.4.2 XT1053 rom. If the bootloader is 30.B7, and you have a Sprint X, download/flash the 4.4.4 Sprint XT1056 rom
And I would flash the entire SBF, not just parts because when GPT.Bin and Motoboot.img are mismatched from the rom on the phone, you can/will brick taking an OTA.
You can get the roms from -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
In other words, suggesting to flash the Verizon 4.4.4 rom like you are, might not work if you have a LOCKED bootloader and don't have a Verizon XT1060. Flashing the Verizon XT1060 GPT.BIN onto a European XT1052 with unlocked bootloader could cause other issues too.
Finally, flashing the GPT.BIN from a 4.4.4 ROM onto a phone that has the bootloader from 4.4.2 for example, will also cause issues.

one fraction out
KidJoe said:
I would suggest something slightly different.
I would say.. check the bootloader on your phone, and download the corresponding ROM for your model phone.
Bootloader version = rom version
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Just some model examples...
XT1060 = Verizon Wireless USA
XT1058 = ATT in the USA, Rogers Canada
XT1056 = Sprint in the USA
XT1053 = GSM Dev Edition, as well as the "Unlocked ships with xxx Sim" from Moto's web site (like T-Mobile, Net10, and others).
XT1052 = European, and some Asia.
So if your bootloader is 30.B4 and you have a GSM Unlocked (with T-Mobile SIM), then download and flash the 4.4.2 XT1053 rom. If the bootloader is 30.B7, and you have a Sprint X, download/flash the 4.4.4 Sprint XT1056 rom
And I would flash the entire SBF, not just parts because when GPT.Bin and Motoboot.img are mismatched from the rom on the phone, you can/will brick taking an OTA.
You can get the roms from -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
In other words, suggesting to flash the Verizon 4.4.4 rom like you are, might not work if you have a LOCKED bootloader and don't have a Verizon XT1060. Flashing the Verizon XT1060 GPT.BIN onto a European XT1052 with unlocked bootloader could cause other issues too.
Finally, flashing the GPT.BIN from a 4.4.4 ROM onto a phone that has the bootloader from 4.4.2 for example, will also cause issues.
Click to expand...
Click to collapse
:9
30.B4 = 4.4.2
30.B5 = 4.4.3
30.B6 = 4.4.4
30.B7 = 5.0
this was misleading my unbricking development (even has set me at a good path at first) xD i saw this at a chinese site, which i did not understand at all, but the following " 4.4.4 = 30.B6" so i could guess the next version has to be lollipop and i had to get GPT.bin from there so the partitions in my phone could restore, which they did, so my hard brick phone, now is unbricked, until the next time i flash something without think about consequences :3

slash1432422 said:
:9
30.B4 = 4.4.2
30.B5 = 4.4.3
30.B6 = 4.4.4
30.B7 = 5.0
this was misleading my unbricking development (even has set me at a good path at first) xD i saw this at a chinese site, which i did not understand at all, but the following " 4.4.4 = 30.B6" so i could guess the next version has to be lollipop and i had to get GPT.bin from there so the partitions in my phone could restore, which they did, so my hard brick phone, now is unbricked, until the next time i flash something without think about consequences :3
Click to expand...
Click to collapse
Not sure where that list came from, but for every variant of the 2013 X I've seen, 30.B7 is the bootloader when 4.4.4. is the newest rom that was flashed on the phone.
After applying the 5.02 leaks for Brazil XT1058, and "Retail" XT1053 the bootloader was 30.BC.
Now, if you are saying that when attempting to unbrick its better to flash one version higher than the bootloader on your phone, that good as well. You have to flash equal or newer than what was on your phone when attempting to unbrick.

yeah probably
i'm probably wrong and i don't want to mislead anybody, so i'll say, that was my personal experience, you guys can google the c*ap out of it like i did (15 tabs+/- per browser)

Please help
I bought a unlocked pure edition moto x directly from Motorola. Powered on this past Tuesday. Didn't install sim card yet. Notified me Wednesday there was a update. I clicked OK. Went to work
come home and the phone was stuck on the M screen. Got it to the boot loader clicked recovery. Had the android guy laying down with the exclamation point. Wiped cache. That didn't work. Done a factory reset that didn't work. On the boot loader screen where the options are available it says device is locked. And software version it says modified. I never modified it. So now I have to return for a refund. But how would this of happened? And,what does it mean by modified? Called Motorola and I done everything they said to. do. I never down graded the os either.

Moto g2 stuck on boot loader screen while rebooting
hey guys.
so recently i installed an app called "kingroot" which helps enhance performance by rooting. Today my device ran out of battery and when i connected it to a charger, bootloader screen automatically appears and shows: 'boot-up failed'. I have not installed any custom ROM and the device was running stock ROM (6.0).
To be honest, I am not a developer and have no clue about this. all options shown in bootloader lead to a dead end. The battery won't charge and connecting it to my pc wasn't helpful either. All I want to do is run my stock rom, which doesn't seem to be happening.
Device: Moto G 2014 (dual sim)(India)
Need help Urgently.
thanks

[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] [q] please help me!!!

I have a moto x xt1053 , factory unlocked version bought from moto maker.
previously i had unlocked bootloader, rooted my phone and done all sorts of **** with it like flashing cm12, but since i heard lollipop was officially coming, i decided to revert to stock. i returned to 4.2.2 by manually flashing it via mfastboot.
All though a few things had a remote failure while flashing, it worked well. now i had a stock moto x with unlocked bootloader. when i repeatedly received notifications from moto to update to kitkat, i accepted. it downloaded and when it went to that android logo with exclamation, i by mistake held the volume up and power button for a few seconds which made it reboot during the update. now, the phone doesn't work. it only opens to fastboot and it says my device is locked
although i had an unlocked bootloader.
now the device only says a few things like -
downgraded security version
update gpt_main version failed
failed to hab check
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
i have tried everything to save it. nothing works. i cant flash images because on rsd lite it always fails, and manually it says bootloader permission denied since the bootloader has got locked. even TWRP won't flash.what do i do?
When i try to click on anything such as recovery or factory or barcode or bp tools, it says boot up failed and load kernel ((boot) failed in red.
PLEASE HELP ME FIX MY PHONE XDA!! i need you all!! i don't mind losing data or anything. i dont even mind running cm forever, but please get it to work!!
thanks a lot in advance.

You missed all the warnings to NOT DOWNGRADE and went back to 4.2.2.
See -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Determine the bootloader version on your phone. What is it?
If it is 30.B7 or lower, grab the 4.4.4 image/sbf file for your phone, and flash it by following the Requirements and Option 5 from Post #2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
If your bootloader is 30.BC or higher, or you had 5.1 on your phone, you best bet is to wait for a 5.1 SBF for your phone to be leaked or posted. There are some possibilities but they depend on finding the correct leaked Lollipop OTA zip file for your phone.

KidJoe said:
You missed all the warnings to NOT DOWNGRADE and went back to 4.2.2.
See -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Determine the bootloader version on your phone. What is it?
If it is 30.B7 or lower, grab the 4.4.4 image/sbf file for your phone, and flash it by following the Requirements and Option 5 from Post #2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
If your bootloader is 30.BC or higher, or you had 5.1 on your phone, you best bet is to wait for a 5.1 SBF for your phone to be leaked or posted. There are some possibilities but they depend on finding the correct leaked Lollipop OTA zip file for your phone.
Click to expand...
Click to collapse
i have tried doing what you asked me to do. when i try to flash it manually from mfastboot, the first few things don't get flashed at all and later on during the flashing of system and stuff, it fails because bootloader access is denied.
please help me! im in deep trouble..:crying:
my bootloader version is 30.B7(*)
thanks a lot mark venture! youre the best!
i tried flashing lots of things like all kitkats factory images but it wont flash

suryanshsanghvi said:
i have tried doing what you asked me to do. when i try to flash it manually from mfastboot, the first few things don't get flashed at all and later on during the flashing of system and stuff, it fails because bootloader access is denied.
please help me! im in deep trouble..:crying:
my bootloader version is 30.B7(*)
thanks a lot mark venture! youre the best!
i tried flashing lots of things like all kitkats factory images but it wont flash
Click to expand...
Click to collapse
First... STOP FLASHING "all kitkats factory images"... that is how you got your self in this situation.
There are warnings about downgrading (flashing older SBFs) because its often either difficult and in many cases not possible to recover when you've bricked because of it.
Next... What Model X do you have, and who is the carrier?

KidJoe said:
First... STOP FLASHING "all kitkats factory images"... that is how you got your self in this situation.
There are warnings about downgrading (flashing older SBFs) because its often either difficult and in many cases not possible to recover when you've bricked because of it.
Next... What Model X do you have, and who is the carrier?
Click to expand...
Click to collapse
I have a moto x gen1 bought from moto maker. It's is factory unlocked gsm an:cyclops: came with TMO SIM card. Please, help me.

suryanshsanghvi said:
I have a moto x gen1 bought from moto maker. It's is factory unlocked gsm an:cyclops: came with TMO SIM card. Please, help me.
Click to expand...
Click to collapse
Have you ever tried any of the Lollipop leaks? either 5.02 or 5.1? Did your phone get prompted to update to Lollipop and fail?
IF your bootloader is still 30.B7, and you have NOT tried flashing anything but XT1053 "retail" roms, and have NOT flashed the leaked 5.02 or now 5.1 or the offical 5.1, then... hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
Next hit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and view post #2... Use the requirements and Option #5 with this downloaded file, EXACTLY as written! Do NOT skip any steps.
If it errors, copy/paste exactly what it says on the PC, or take a picture of the phone's screen and post it.
Further, if this fails each time it tries to flash GPT.BIN, then you may be stuck until a 5.1 SBF leaks and you can flash with that as any option risks bricking your phone even worse.

KidJoe said:
Have you ever tried any of the Lollipop leaks? either 5.02 or 5.1? Did your phone get prompted to update to Lollipop and fail?
IF your bootloader is still 30.B7, and you have NOT tried flashing anything but XT1053 "retail" roms, and have NOT flashed the leaked 5.02 or now 5.1 or the offical 5.1, then... hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
Next hit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and view post #2... Use the requirements and Option #5 with this downloaded file, EXACTLY as written! Do NOT skip any steps.
If it errors, copy/paste exactly what it says on the PC, or take a picture of the phone's screen and post it.
Further, if this fails each time it tries to flash GPT.BIN, then you may be stuck until a 5.1 SBF leaks and you can flash with that as any option risks bricking your phone even worse.
Click to expand...
Click to collapse
What do I do if I've tried flashing 5.0.2 leaked rom of xt1058 before? It did work at that time though. So now do I have to wait till moto updates their website and puts up 5.1 for my phone on the site? I went to the service centre today and they told me to shell out 300$ for repairs. I could buy a new phone with that cash. Really need all you dev's help.

suryanshsanghvi said:
What do I do if I've tried flashing 5.0.2 leaked rom of xt1058 before? It did work at that time though. So now do I have to wait till moto updates their website and puts up 5.1 for my phone on the site? I went to the service centre today and they told me to shell out 300$ for repairs. I could buy a new phone with that cash. Really need all you dev's help.
Click to expand...
Click to collapse
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.

KidJoe said:
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
Click to expand...
Click to collapse
I'm pretty sure the BSF will be put up by 2 weeks so I'll just wait till then. But when I get it, how will I flash it? RSD lite right? Cause if I do it manually through mfastboot, stuff doesn't get flashed cause boot loader is locked. If it wasn't locked, I'd flash twrp days back.

KidJoe said:
As i said before, DOWNGRADING is what got you into this situation. You can't do that. There are many warnings. Even a link to a thread discussing it (which also has links to many who have attempted to downgrade and have bricked).
If you had 5.x on there, and try to flash 4.x on there then you are downgrading.. NOW, the one caveat being IF you restored one of the TWRP backups of 5.x onto your phone, as that usually only restored /system and NOTHING ELSE which is better.. Its the OTHER PARTS that get in the way and cause issues when trying to downgrade.
IF however you flashed the XT1058 ROM (using RSDLite or fastboot), then took one of the LEAKED 5.x OTA updates at some point, its a different matter.
Again, *IF* your bootloader is 30.B7, then you should be able to do what I said a few posts ago. There is a 70% chance it will fix you. If not, then yes we must wait for a 5.1 SBF file for your carrier/model. Since you have the XT1053, Moto will eventually post it on their web site where they put Developer Edition recovery images, and you don't have to rely on a 5.1 SBF to LEAK (since leaks are not official, you cant count on them appearing)
IF your bootloader is 30.BC, 30.BD, or 30.BE, there are posts of people extracting the GPT.BIN and Bootloader from the leaked OTA zip files and flashing them to get their phone working, HOWEVER see this one -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-bricked-device-t3076918 where after doing that, getting it working, he took an OTA and it bricked him even worse.. That is why I say the SAFEST way would be to wait until the 5.1 SBF comes.. IF you want to attempt this, I won't advise you as to how, and will say that if you figure it out, DO NOT take an OTA!! Instead wait until the 5.1 SBF is posted, then fully flash that.
Click to expand...
Click to collapse
@KidJoe - props for helping this guy out man!
Sent from my XT1053 using Tapatalk

suryanshsanghvi said:
I'm pretty sure the BSF will be put up by 2 weeks so I'll just wait till then. But when I get it, how will I flash it? RSD lite right? Cause if I do it manually through mfastboot, stuff doesn't get flashed cause boot loader is locked. If it wasn't locked, I'd flash twrp days back.
Click to expand...
Click to collapse
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.

KidJoe said:
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
Click to expand...
Click to collapse
Bro you're the best.thanks a lot man!

Official ROM image from MOTO
KidJoe said:
hit Moto's web site -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and request access then download "MOTO X, GSM Dev Edition:
KK-4.4.4-KXA21.12-L1.29.1-2 (Retail) MR4"
Or download this copy from file factory which is the same rom version -> http://www.filefactory.com/file/2yh...4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip
.
Click to expand...
Click to collapse
Filefactory is dead-slow. Moto took a long time to give me access to the factory roms. I am linking 4.4.4 here for the community's convenience.
https://drive.google.com/open?id=0B1KTBUtop5_HZkxNS2NZdkdQZW8&authuser=0
XT1053_4.4.4_213.44.1 (KXA21.12-L1.29.1_2_cid9_CFC_1FF)
md5 = 22773e5981cb04f6286a12e9488d0db5
sha1 = f8e0d2c0e04c2414f16a44c21ddb0ca18b2122e4

KidJoe said:
There is no time table for when Moto will post the SBF file to their web site. We can hope they will do it sooner, rather than later. But at least with the XT1053, you know Moto WILL post it, unlike those who rely on leaks.
No. Do not RSDLite. RSDLite will likely fail due to the GPT errors. Again, use Option 5 of that post and mfastboot EXACTLY as written.
As long as you are flashing the Stock, and digitally signed by Moto rom for that phone carrier/model, you can flash with a locked bootloader. Its when you try to flash the rom for another model/carrier that locked bootloader comes into play.
Click to expand...
Click to collapse
I can't wait longer. Please tell me an alternate way to fix my phone? Or a leaked file for USA unlocked phone xt1053 of 5.1
As soon as it works, I'll switch to cyanogenmod and never switch back again.
Can you please tell me which moto boot gpt and recovery to flash from which sbf files so it boots up and I'll install twrp. I'll take the risk cause my phone's already ****ed up. If it's dead, it's dead. It'll be last attempt. You need not worry. Please tell me.

suryanshsanghvi said:
I can't wait longer. Please tell me an alternate way to fix my phone? Or a leaked file for USA unlocked phone xt1053 of 5.1
As soon as it works, I'll switch to cyanogenmod and never switch back again.
Can you please tell me which moto boot gpt and recovery to flash from which sbf files so it boots up and I'll install twrp. I'll take the risk cause my phone's already ****ed up. If it's dead, it's dead. It'll be last attempt. You need not worry. Please tell me.
Click to expand...
Click to collapse
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.

new error
KidJoe said:
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
Click to expand...
Click to collapse
till now it just said-
downgraded security version
update gpt_main version failed
failed to hab check
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
but now it says-
downgraded security version
update gpt_main version failed
failed to hab check for gpt _backup:0x35
CID read failure
invalid cid status 0*69
customer id error contact dealer ; 0xdead
No SP partition found
fastboot reason; invalid cid
:crying:

i tried flashing official sbf using the method you told me to use. this is the result
KidJoe said:
You said your bootloader was 30.B7, but you have NOT yet said if you tried what I put in Post #6....
Did you try that? what happened? I had asked you to copy/paste any errors and I didn't see them.
Click to expand...
Click to collapse
on command prompt, the followin takes place-
C:\Users\user\Desktop\moto x\platform-tools>mfastboot getvar max-download-size
max-download-size: 805306368
finished. total time: 0.149s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.301s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.223s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash motoboot motoboot.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.421s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.703s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.004s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.212s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash motoboot motoboot.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.426s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.383s]
writing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.485s
C:\Users\user\Desktop\moto x\platform-tools>
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash boot boot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'boot' (10240 KB)...
OKAY [ 0.986s]
writing 'boot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.088s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash recovery recovery.im
g
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 1.004s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 1.106s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 896527596 bytes
error: cannot load 'system.img': Not enough space
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.767s]
writing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 3.889s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Invalid partition name modemst1
FAILED (remote failure)
finished. total time: 0.102s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Invalid partition name modemst2
FAILED (remote failure)
finished. total time: 0.099s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (1223 KB)...
OKAY [ 0.426s]
writing 'fsg'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.529s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.104s
C:\Users\user\Desktop\moto x\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.002s
PLEASEE HELPPP

At this point, you need to wait on the 5.1 SBF to be safe. Anything else could risk bricking you even worse than you are, so I don't want to suggest it.
Keep an eye on -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 and see if it pops up there before Moto posts it..
Or maybe @s5610 has an idea?

KidJoe said:
At this point, you need to wait on the 5.1 SBF to be safe. Anything else could risk bricking you even worse than you are, so I don't want to suggest it.
Keep an eye on -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 and see if it pops up there before Moto posts it..
Or maybe @s5610 has an idea?
Click to expand...
Click to collapse
Can you give me link for a proper mfastboot. Mine says could not allocate and stuff while writing system

suryanshsanghvi said:
Can you give me link for a proper mfastboot. Mine says could not allocate and stuff while writing system
Click to expand...
Click to collapse
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip its the same mfastboot packaged in the 4.4.2 and 4.4.4 roms on moto's web site.