[Q] Corrupted Partition Files - Mega Hard Bricked - [Please Guys] - Moto X Q&A

Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
s code showed up in the picture.
Thanks for all,
Bruno Sastre.

BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.

samwathegreat said:
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.
Click to expand...
Click to collapse
Since he's international, couldn't he unlock the bootloader and reflash the software image?

sivarticus85 said:
Since he's international, couldn't he unlock the bootloader and reflash the software image?
Click to expand...
Click to collapse
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.

samwathegreat said:
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.
Click to expand...
Click to collapse
I know he was trying to downgrade, but I didn't realize what had happened until I re-read his post. I get it now. I think what you suggested should do the trick.

Still working [I hope]
BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.

BrunoX10 said:
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.
Click to expand...
Click to collapse
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.

Bad Feelings...
samwathegreat said:
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.
Click to expand...
Click to collapse
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.

BrunoX10 said:
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.
Click to expand...
Click to collapse
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img

Good News - We made it!!!
samwathegreat said:
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img
Click to expand...
Click to collapse
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.

BrunoX10 said:
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.
Click to expand...
Click to collapse
F-A-N-T-A-S-T-I-C !!!
I'm very glad you had success :highfive: (High-Five)
EDIT: @BrunoX10 can you read this post: http://forum.xda-developers.com/moto-x/moto-x-qa/request-twrp-backup-brazil-retail-t2817522
This user needs your help! He is also using Brazil Retail 4.4.3 and accidently erased /system
Can you help him by making a backup of /system and sharing?

Related

Moto X TMO Dev Edition Freezing

Hi,
I just got my Moto X Dev Edition GSM TMO last week, but I got it very unstable, while I had try to wipe cache and factory reset few times.
Some problem that I have
Numeric Keypad is not shown while using google keyboard. The problem that my email is using 2FA from google to entry my 6-digit PIN
Chrome freeze while open quite complex pages
Gmail freezing while open communication more than 3 email on the messaging mode
Path also unstable while need to scroll down and request to reload more data.
Whatsapp stuck when there's few message has beeen received
Thinking to downgrade the os to 4.4, but when I read in some thread inform better not to downgrade that might cause device brick.
Is there any other solution so I can use my Moto X for daily, while waiting for T-Mobile latest 4.4.2 rom.
Please share
Thank you
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Click to expand...
Click to collapse
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
tyapeter said:
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
Click to expand...
Click to collapse
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Let me make it easier. Just flash the system and kernel files leave everything else alone. However the ability to go back depends on how you got to 4.4.2 to begin with, OP said he took the OTA, not sure about you.
My advice assuming you're stock is to call Motorola, tell them you took the ota and these are the issues you're having. Get them to send you a new phone. I'd rather see you do that than brick your phone trying to do it yourself.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Are you sure this is correct? I was told in this thread: http://forum.xda-developers.com/showthread.php?p=50330230#post50330230 (see post #12):
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
Click to expand...
Click to collapse
So the way I understand it one cannot downgrade from 4.4.2 to any other version because bootloader in 4.4.2 was changed and is not compatible with any previous release.
tyapeter said:
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Click to expand...
Click to collapse
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
eksasol said:
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
Click to expand...
Click to collapse
Thanks a lot, it works

[Q] Moto X probabbly hard bricked

Hello anyone! I'm looking for some help.
My phone was running android 4.4.2, then i modified the buil.prop for increasing the display density & my phone got off, then i tried and tried and tried turn it on, then i did it & i fash my stock rom (for XT1058 america movil MX) the OTA told me about the update & i accept it... Well my phone now is in fastboot & he says this (yep ''he'' LOL):
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
Well, i wish someone could help me, i don't want to have a beautiful $400 paperweight, thanks a lot XDA
TUESONER said:
Hello anyone! I'm looking for some help.
My phone was running android 4.4.2, then i modified the buil.prop for increasing the display density & my phone got off, then i tried and tried and tried turn it on, then i did it & i fash my stock rom (for XT1058 america movil MX) the OTA told me about the update & i accept it... Well my phone now is in fastboot & he says this (yep ''he'' LOL):
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
Well, i wish someone could help me, i don't want to have a beautiful $400 paperweight, thanks a lot XDA
Click to expand...
Click to collapse
try to flash with mfastboot the recovery from 4.4.2 the FIRMWARE U HAVE IT FIRST
MUST BE THE SAME VERSION THAT U HAVE FIRST THAT UR PHONE BRICKED
after u flash the recovery,reboot bootloader and try to flash all firmware
TUESONER said:
Hello anyone! I'm looking for some help.
My phone was running android 4.4.2, then i modified the buil.prop for increasing the display density & my phone got off, then i tried and tried and tried turn it on, then i did it & i fash my stock rom (for XT1058 america movil MX) the OTA told me about the update & i accept it... Well my phone now is in fastboot & he says this (yep ''he'' LOL):
downgraded security version
update gpt_maim¡n version failed
Failed to check for gpt_backup: 0x35
CID Read failure
Invalid CID status 0x69
Customer ID eroor. Contact dealer: 0xdead
No SP partition found
Fastboot reason: Invalid CID
Well, i wish someone could help me, i don't want to have a beautiful $400 paperweight, thanks a lot XDA
Click to expand...
Click to collapse
You had 4.4.2 on your phone, I'm betting the "stock rom" you had then tried flashing was 4.4 or lower.
As danger2u said, the first thing you'll want to try is to flash the ROM for your phone. Since you had 4.4.2 on there, you'll need to find the 4.4.2 SBF for your carrier (I don't see american movil mx listed on -> http://sbf.droid-developers.org/phone.php?device=0 ), and flash it.
If that doesn't work, you'll want to see this thread -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 It too requires you have the correct ROM for your device
If you manage to get it working.. DO NOT DOWNGRADE YOUR ROM!!!!! (i.e. once on 4.4.2 do NOT flash 4.4 or below!!!!)
KidJoe said:
You had 4.4.2 on your phone, I'm betting the "stock rom" you had then tried flashing was 4.4 or lower.
As TUESONER said, the first thing you'll want to try is to flash the ROM for your phone. Since you had 4.4.2 on there, you'll need to find the 4.4.2 SBF for your carrier (I don't see american movil mx listed on -> TUESONER ), and flash it.
If that doesn't work, you'll want to see this thread -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 It too requires you have the correct ROM for your device
If you manage to get it working.. DO NOT DOWNGRADE YOUR ROM!!!!! (i.e. once on 4.4.2 do NOT flash 4.4 or below!!!!)
Click to expand...
Click to collapse
I got my phone with 4.2.2 out of the box, then i recivied the 4.4.2 via OTA, at&t us have the XT1058, would i install the rom on 4.4 fot at&t then flash the modem?
TUESONER said:
I got my phone with 4.2.2 out of the box, then i recivied the 4.4.2 via OTA, at&t us have the XT1058, would i install the rom on 4.4 fot at&t then flash the modem?
Click to expand...
Click to collapse
No. If you received 4.4.2 OTA... you need to flash 4.4.2. do NOT flash 4.4.
Due to changes in 4.4.2, you either will brick, or set yourself up to brick if you try to downgrade your rom version... i.e. 4.4.2 -> 4.4 will brick or set you up for it.
Were you running an ATT ROM on your phone? or something else?
KidJoe said:
No. If you received 4.4.2 OTA... you need to flash 4.4.2. do NOT flash 4.4.
Due to changes in 4.4.2, you either will brick, or set yourself up to brick if you try to downgrade your rom version... i.e. 4.4.2 -> 4.4 will brick or set you up for it.
Were you running an ATT ROM on your phone? or something else?
Click to expand...
Click to collapse
I'm wrong, i wanted to write 4.4.2. I was running my stock rom, america movil 4.2.2, recivied the OTA for 4.4.2, in the page of firmwares i can´t find the firmware for america movil 4.4.2, probabbly it doesn´t exist, so, can i flash the rom for the at&t XT1058, then i got the modem for my carrier flashed?
TUESONER said:
I'm wrong, i wanted to write 4.4.2. I was running my stock rom, america movil 4.2.2, recivied the OTA for 4.4.2, in the page of firmwares i can´t find the firmware for america movil 4.4.2, probabbly it doesn´t exist, so, can i flash the rom for the at&t XT1058, then i got the modem for my carrier flashed?
Click to expand...
Click to collapse
I don't know the differences in the ATT Rom vs America Movil... I know the ATT rom has a lot of bloat.
I don't think the ATT 4.4.2 SBF was leaked yet (it wasn't when i looked earlier)...
TUESONER said:
I'm wrong, i wanted to write 4.4.2. I was running my stock rom, america movil 4.2.2, recivied the OTA for 4.4.2, in the page of firmwares i can´t find the firmware for america movil 4.4.2, probabbly it doesn´t exist, so, can i flash the rom for the at&t XT1058, then i got the modem for my carrier flashed?
Click to expand...
Click to collapse
the only Movil 4.4.2 is this
http://sbf.droid-developers.org/download.php?device=0&file=835
so i think u have this version of firmware on 4.2.2
download it
extract firmware
flash only the recovery
reboot bootloader
then flash entire rom
let us know
KidJoe said:
You had 4.4.2 on your phone, I'm betting the "stock rom" you had then tried flashing was 4.4 or lower.
As danger2u said, the first thing you'll want to try is to flash the ROM for your phone. Since you had 4.4.2 on there, you'll need to find the 4.4.2 SBF for your carrier (I don't see american movil mx listed on -> TUESONER ), and flash it.
If that doesn't work, you'll want to see this thread -> http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057 It too requires you have the correct ROM for your device
If you manage to get it working.. DO NOT DOWNGRADE YOUR ROM!!!!! (i.e. once on 4.4.2 do NOT flash 4.4 or below!!!!)
Click to expand...
Click to collapse
This ^^
If you downgraded and then took an ota, that usually leads to a brick. Read the thread kid Joe posted and hopefully you can recover.
Good luck!
Oh, and as said....the best moto x advice there is, is once on 4.4.2.....stay on 4.4.2. Unfortunately.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Thanks anyone for the suport, tomorrow imma try with that rom, i'm reall tired today, was a lng day at my work, i will post the results, again, thanks everyone, wait for my post tomorow.
TUESONER said:
Thanks anyone for the suport, tomorrow imma try with that rom, i'm reall tired today, was a lng day at my work, i will post the results, again, thanks everyone, wait for my post tomorow.
Click to expand...
Click to collapse
kj2112 said:
This ^^
If you downgraded and then took an ota, that usually leads to a brick. Read the thread kid Joe posted and hopefully you can recover.
Good luck!
Oh, and as said....the best moto x advice there is, is once on 4.4.2.....stay on 4.4.2. Unfortunately.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
danger2u said:
the only Movil 4.4.2 is this
xxx
so i think u have this version of firmware on 4.2.2
download it
extract firmware
flash only the recovery
reboot bootloader
then flash entire rom
let us know
Click to expand...
Click to collapse
It did't work at all, i flashed the recovery then the entire rom, now thce cellphone turn on, then i see the message of the unlocked bootloader, then the screen goes black & for something like half second i see the image of andy (the android caracter) & the legend ''updating'' then another image for half second or less that says ''error''
The rom has flashed correctly, i can enter in fastboot mode too
TUESONER said:
It did't work at all, i flashed the recovery then the entire rom, now thce cellphone turn on, then i see the message of the unlocked bootloader, then the screen goes black & for something like half second i see the image of andy (the android caracter) & the legend ''updating'' then another image for half second or less that says ''error''
The rom has flashed correctly, i can enter in fastboot mode too
Click to expand...
Click to collapse
flash it manually
try another firmware that is 4.4.2 and compatible with ur country and operator
now if turns on is no more bricked. u are on the good way
danger2u said:
flash it manually
try another firmware that is 4.4.2 and compatible with ur country and operator
now if turns on is no more bricked. u are on the good way
Click to expand...
Click to collapse
flash manually? that's with fastboot or mfastboot? what comands do i need to use?
TUESONER said:
flash manually? that's with fastboot or mfastboot? what comands do i need to use?
Click to expand...
Click to collapse
mfastboot
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
danger2u said:
mfastboot
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
Careful.. That is an example for Verizon. It might not match the XML that is in whatever rom TUESONER is trying to flash on an XT1058.
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
TUESONER said:
flash manually? that's with fastboot or mfastboot? what comands do i need to use?
Click to expand...
Click to collapse
First off, which SBF are you trying to flash? is it 4.4.2 or 4.4?
Past or attach the XML which is inside the SBF you are using. We'll help you convert it to the correct series of mFastboot commands.
KidJoe said:
Careful.. That is an example for Verizon. It might not match the XML that is in whatever rom TUESONER is trying to flash on an XT1058.
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
First off, which SBF are you trying to flash? is it 4.4.2 or 4.4?
Past or attach the XML which is inside the SBF you are using. We'll help you convert it to the correct series of mFastboot commands.
Click to expand...
Click to collapse
he can pass the comand
mfastboot oem config carrier vzw
it works without this too
KidJoe said:
Careful.. That is an example for Verizon. It might not match the XML that is in whatever rom TUESONER is trying to flash on an XT1058.
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
First off, which SBF are you trying to flash? is it 4.4.2 or 4.4?
Past or attach the XML which is inside the SBF you are using. We'll help you convert it to the correct series of mFastboot commands.
Click to expand...
Click to collapse
i will use this one, i erased the line of ''max download size''
TUESONER said:
i will use this one, i erased the line of ''max download size''
Click to expand...
Click to collapse
Is that the exact 4.4.2 ROM that was on your phone originally? If not, there is a chance this still might not fix you...
Its extremely similar to what @danger2u has already posted.
(based on Moto's web site and the XML you posted) after unzipping the "CLARO-BR_GHOST..." SBF, you'd want to try the following commands from the folder where you unzipped the SFB after booting the phone to fastboot/bootloader mode....
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot reboot
NOTE: by Mfastboot, I mean the Moto modified version of fastboot, not the one that comes with the standard Android SDK/Platform Tools. The moto modified Fastboot.exe can sometimes be found in a windows folder inside an SBF, or you can download from -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
KidJoe said:
Is that the exact 4.4.2 ROM that was on your phone originally? If not, there is a chance this still might not fix you...
Its extremely similar to what @danger2u has already posted.
(based on Moto's web site and the XML you posted) after unzipping the "CLARO-BR_GHOST..." SBF, you'd want to try the following commands from the folder where you unzipped the SFB after booting the phone to fastboot/bootloader mode....
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot reboot
NOTE: by Mfastboot, I mean the Moto modified version of fastboot, not the one that comes with the standard Android SDK/Platform Tools. The moto modified Fastboot.exe can sometimes be found in a windows folder inside an SBF, or you can download from -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
Click to expand...
Click to collapse
The ROM isn't the original that was running my phone, i got 4.2.2 out of the box, now i will indtsll thst ROM because is 4.4.2 & i will not brick or have problems, the fastboot that you attached doesn't work with the comands ''mfastboot'' i use just ''fastboot''?
i did it!
GUYS! THANK YOU A LOT! i did it, mi moto X is alive, thanks @KidJoe, @danger2u & @kj2112, you helped me without even knowing me.
I used the comands that @KidJoe gave me, but using just ''fastboot'' everything is working fine, even the 4G connection.
Thanks, really, really thanks... Now i feel i'm a real XDA member & i wish my post help people.

[Q] version downgraded for primary_gpt

Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819
im glad to know that "As long as you have a bootloader then your phone is never bric
skulldreamz said:
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819
Click to expand...
Click to collapse
Thank you for your help, but i dont have anymore twrp, and my phone is xt 1097, im glad to know that "As long as you have a bootloader then your phone is never bricked." i have it still!!
Now RSD Lite recognizes my phone, but when i start to flash android 5.0 it says: version downgraded for primary_gpt
I flash this same rom (5.0) before using RSD Lite and it worked perfectly, but now gives this error. How can i fix it?
Have you got your factory image for your phone and mfastboot?
yes, i have it
orangestrawberry said:
Have you got your factory image for your phone and mfastboot?
Click to expand...
Click to collapse
I heard many people reporting this error, say they have posts here on xda that solves the problem but I could not find them . I have seen in a blog that the problem is in doing downgrading from 5.0 to 5.1. and they say that to solve it is necessary to change two lines of a file , but I do not know which file is this , and not how it's done
jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?
I have bootloader (fastboot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JulesJam said:
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?
Click to expand...
Click to collapse
these are the information appearing:
So I try to install the rom 5.0 with RSD Lite this error occurs :
And that's what the RSD Lite says :
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "
jrmaiafs said:
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "
Click to expand...
Click to collapse
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Thank you
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007
jrmaiafs said:
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007
Click to expand...
Click to collapse
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?
JulesJam said:
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?
Click to expand...
Click to collapse
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ah, got it.
So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse
KB Smoka said:
So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
Click to expand...
Click to collapse
Is your bootloader unlocked? Last I read you could get the Verizon Moto X 2014 bootloader unlocked.
You can get into bootloader mode and use fastboot commands, correct?
3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.
Dangerous-Beans! said:
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.
Click to expand...
Click to collapse
No worries, Chrome did the translating fine. )

My XT1072 stuck on fastboot flash screen - Help needed

Hi,
I have an XT1072 which was rooted and running CM. Since I wanted to install stock ROM, I used the Windows Tool from this forum to restore stock Android. By doing so, I was stuck with Bootloader locked screen.
Since then I am stuck on Fastboot Flash Mode screen (see pic attached).
When I try to connect my device to the same PC or any other PC and try mfastboot or fastboot or any command, it just says Waiting for device. I have all the required drivers installed in all the PCs I tested.
Using the volume buttoms, I am able to select any option, but it wont open any option (such as Normal Powerup or Recovery)
Can someone help?
Thanks
anyone?
ram11 said:
anyone?
Click to expand...
Click to collapse
Your system image is signed using incorrect key. Reflash system partition with factory image.
LuK1337 said:
Your system image is signed using incorrect key. Reflash system partition with factory image.
Click to expand...
Click to collapse
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
ram11 said:
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
Click to expand...
Click to collapse
You need to get fastboot drivers...
LuK1337 said:
You need to get fastboot drivers...
Click to expand...
Click to collapse
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
ram11 said:
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
Click to expand...
Click to collapse
Join #titandev at freenode in 20 mins, I'll try to help you out.
Sent from my Moto G 2014 LTE using Tapatalk
Any luck?
Hi Guys,
I know this is a long shot as this is an old thread but did you get anywhere with a resolution to this?
I'm in the exact same position.
Tried flashing with different factory roms and "fastboot boot" to try force it to boot a twrp image
I'm also stuck here, anyone has had any luck?
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
This will flash the fw, factory reset and reboot the phone.
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it
dr.nic said:
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
This will flash the fw, factory reset and reboot the phone.
Click to expand...
Click to collapse
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot reboot
Click to expand...
Click to collapse
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
Bootloader should check if boot and system images are correct otherwise it should send user back to bootloader.
dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
I gave this a shot as suggested and I'm getting this error:
C:\Users\Nick\Downloads\New folder>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259279 KB)...
OKAY [ 9.742s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.131s
Also getting the error:
version downgraded for system
Invalid PIV signed system image
Out of tricks stock flash + factory reset always worked for me sorry.
I noted my phone model/region before doing anything (xt1072-thea-reteu) got the right fw and it worked fine, maybe was another problem giving the same error "failed to validate system image" unable to boot and stuck in bootloader, weird.... :\
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
nickkk93 said:
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
Click to expand...
Click to collapse
My phone is in a drawer I'd love to be able to fix it because I really miss Android now but it there doesn't seem to be a solution... I am no giving up hope entirely though!
I tink that I have similar problem with my X1072.
After unroot with Kingroot and install AdAway and TWRP from Google Play I even noticed that I hadn't unlock bootolader.
Now I can't reboot my phone without entering in Bootloader and reseting to factory defaults. After some reboots no data has been deleted.
I have tried to reflash the entire phone but In bootloader mode the phone is not detected by the computer, so I can't flash. I'm stucked. by now
josepmanel said:
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Click to expand...
Click to collapse
Have you had any luck at all? My phone has been in a drawer for a couple of months now...
Guys try flashing the latest MM stock i discovered an error too in my old update script /sniff.
Run the *.bat as admin .
Stock zip for XT1072:
MEGA Mirror 1
MEGA Mirror 2
Fastboot+mfastbootv2
BAT File
MM Flash BAT said:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Also remember if you are on another model and not XT1072 you should dl the correct image for your phone from HERE Look if Android 6 is available for your country, if you have gb-de-fr-es you can use the EU stock image.
Unpack everything in the same folder and launch the *.BAT as admin

Soft bricked XT1052

Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?
I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...
OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed
varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?
Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.

Categories

Resources