Post Reply

Bricked Moto X after OTA upgrade. Please help me!!

OP motox1983

6th June 2014, 03:21 AM   |  #1  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Jun 2014
Hi everyone!!

I was wondering if you could help me. I am a bit of a noob in this flashing phones, so here it goes:

I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked . I am getting very similar errors like this similar thread and it now appears to be Device LOCKED: http://forum.xda-developers.com/moto...t2634982/page8

I saw they did something like flashing separate partitions to get it at some point that you could unlock it again or something.

Could you please help me? I am very desperate

Thanks!
6th June 2014, 03:52 AM   |  #2  
omias's Avatar
Senior Member
Thanks Meter: 42
 
165 posts
Join Date:Joined: Jan 2012
I think your phone is full bricked.
I'm from Mexico too

Enviado desde mi XT1053 mediante Tapatalk
6th June 2014, 06:00 AM   |  #3  
samwathegreat's Avatar
Senior Member
Thanks Meter: 1,727
 
1,987 posts
Join Date:Joined: Apr 2010
Donate to Me
Quote:
Originally Posted by motox1983

Hi everyone!!

I was wondering if you could help me. I am a bit of a noob in this flashing phones, so here it goes:

I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked . I am getting very similar errors like this similar thread and it now appears to be Device LOCKED: http://forum.xda-developers.com/moto...t2634982/page8

I saw they did something like flashing separate partitions to get it at some point that you could unlock it again or something.

Could you please help me? I am very desperate

Thanks!

Assuming you can get to the bootloader screen, you can TRY using RSD Lite or manual method to flash the 4.4.2 SBF:

http://forum.xda-developers.com/moto...using-t2446515

Just make sure you use the 4.4.2 SBF File for your carrier from here: sbf.droid-developers.org/phone.php?device=0

Good Luck

EDIT: Reading through the thread you linked, it looks like the key was to FIRST, JUST flash the gpt & motoboot.

So using manual method,

fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img

NEXT, Reboot BEFORE continuing (mfastboot reboot-bootloader)

THEN, you can use the RSD Lite method, or the manual method in the thread I linked.

Let us know if this helps.
Last edited by samwathegreat; 6th June 2014 at 07:37 PM.
The Following 2 Users Say Thank You to samwathegreat For This Useful Post: [ View ]
6th June 2014, 12:14 PM   |  #4  
KidJoe's Avatar
Senior Member
Flag Thorndale/Romansville, PA
Thanks Meter: 845
 
2,080 posts
Join Date:Joined: Aug 2008
More
Quote:
Originally Posted by motox1983

I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked .

So you had 4.4.2, downgraded to 4.4, and taking the OTA caused you to brick?

That is why there are warnings to NOT downgrade (to 4.4 or below) once you have 4.4.2 on your phone...

What @samwathegreat suggested (using mfastboot to flash gpt.bin and motoboot.img first, then RSDLite to flash full 4.4.2 SBF for your carrier) should hopefully work.

Try and charge your phone to above 80% if at all possible before you start.
The Following User Says Thank You to KidJoe For This Useful Post: [ View ]
6th June 2014, 04:33 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Jun 2014
Thumbs up It lives now!!!
Quote:
Originally Posted by samwathegreat

Assuming you can get to the bootloader screen, you can TRY using RSD Lite or manual method to flash the 4.4.2 SBF:

http://forum.xda-developers.com/moto...using-t2446515

Just make sure you use the 4.4.2 SBF File for your carrier from here: sbf.droid-developers.org/phone.php?device=0

Good Luck

EDIT: Reading through the thread you linked, it looks like the key was to FIRST, JUST flash the gpt & motoboot.

So using manual method,

fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img

NEXT, Reboot BEFORE continuing (adb reboot bootloader)

THEN, you can use the RSD Lite method, or the manual method in the thread I linked.

Let us know if this helps.

Thanks a lot samwathegreat. It helped me change the DEVICE Status to UNLOCKED again, but now I am in a bootloop. It boots every couple of minutes or so. I am going to try a full 4.4.2 flash with RSD Lite to see if it solves. What other reason would you think it would be?
6th June 2014, 04:39 PM   |  #6  
Senior Member
Flag Philadelphia, PA
Thanks Meter: 865
 
1,334 posts
Join Date:Joined: Jan 2008
More
The key is the reboot to boot loader after flashing the gpt.bin and Moto boot.img. That will allow the new boot loader to continue flashing the rest of the images.

You have a mismatched aboot image and it is incompatible with the new images and reports as locked and cannot flash any images until the proper aboot is flashed and the device reboots into the new boot loader.

Edit: I see you have gotten past the boot loader issue already.

Just flash the full XML.zip with RSD Lite and you will be fine.
The Following User Says Thank You to cellzealot For This Useful Post: [ View ]
6th June 2014, 05:55 PM   |  #7  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Jun 2014
Bad news :(
Quote:
Originally Posted by cellzealot

The key is the reboot to boot loader after flashing the gpt.bin and Moto boot.img. That will allow the new boot loader to continue flashing the rest of the images.

You have a mismatched aboot image and it is incompatible with the new images and reports as locked and cannot flash any images until the proper aboot is flashed and the device reboots into the new boot loader.

Edit: I see you have gotten past the boot loader issue already.

Just flash the full XML.zip with RSD Lite and you will be fine.

Hey guys, bad news. I flashed what it supposed to be the full XML.zip from the sbf droid-developers web page (I am not allowed to post URL links yet) and it all seemed well, but when I turned it off and then back on, it got again into a bootloop, rebooting every couple of minutes . What do you think it would be the reason? I am from Mexico, so I used the Telcel Mexico 4.4.2 firmware, so I don't use any firmware below 4.4 (the other two options are 4.2.2). I noticed that the Telcel 4.2.2 has more files than the Telcel 4.4.2. Any suggestions? Should I try to flash other firmwares?
6th June 2014, 06:48 PM   |  #8  
KidJoe's Avatar
Senior Member
Flag Thorndale/Romansville, PA
Thanks Meter: 845
 
2,080 posts
Join Date:Joined: Aug 2008
More
Quote:
Originally Posted by motox1983

Hey guys, bad news. I flashed what it supposed to be the full XML.zip from the sbf droid-developers web page (I am not allowed to post URL links yet) and it all seemed well, but when I turned it off and then back on, it got again into a bootloop, rebooting every couple of minutes . What do you think it would be the reason? I am from Mexico, so I used the Telcel Mexico 4.4.2 firmware, so I don't use any firmware below 4.4 (the other two options are 4.2.2). I noticed that the Telcel 4.2.2 has more files than the Telcel 4.4.2. Any suggestions? Should I try to flash other firmwares?

Is the Telcel Mexico 4.4.2 what you were running when you first got the phone and it was on 4.4.2?

Based on what cellzealot said.. try this...

First, make sure you are using the latest mFastboot.EXE -> download mFastboot, and unzip it. It has folders containing the Windows, Linux and Mac versions of Moto's fastboot.exe. After unzipping, find the windows version of the moto fastboot.exe, rename it to mfastboot.exe (so you don't mix it up with the one that comes with the Android SDK) and move it in your Android SDK Platform Tools folder.. usually C:\Android-Sdk\platform-tools.

Open a command prompt and change to the folder where you unziped the SBF to, and run the following...


mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader


EDIT the XML from the SBF. and look for the following lines...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxx" />


and right after it, add...

<step operation="reboot">

save it.

Then use RSDLite to flash the entire XML.
The Following User Says Thank You to KidJoe For This Useful Post: [ View ]
6th June 2014, 07:13 PM   |  #9  
OP Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Jun 2014
Quote:
Originally Posted by KidJoe

Is the Telcel Mexico 4.4.2 what you were running when you first got the phone and it was on 4.4.2?

Based on what cellzealot said.. try this...

First, make sure you are using the latest mFastboot.EXE -> download ..., and unzip it. It has folders containing the Windows, Linux and Mac versions of Moto's fastboot.exe. After unzipping, find the windows version of the moto fastboot.exe, rename it to mfastboot.exe (so you don't mix it up with the one that comes with the Android SDK) and move it in your Android SDK Platform Tools folder.. usually C:\Android-Sdk\platform-tools.

Open a command prompt and change to the folder where you unziped the SBF to, and run the following...


mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader


EDIT the XML from the SBF. and look for the following lines...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxx" />


and right after it, add...

<step operation="reboot">

save it.

Then use RSDLite to flash the entire XML.

I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).

Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?

I flashed separately. First edited the XML to flash only gpt and motoboot and rebooted to fastboot. Then modified again XML so it would flash the rest of the SBF. I will see how it works.
Last edited by motox1983; 6th June 2014 at 07:24 PM. Reason: Added comment
6th June 2014, 07:23 PM   |  #10  
KidJoe's Avatar
Senior Member
Flag Thorndale/Romansville, PA
Thanks Meter: 845
 
2,080 posts
Join Date:Joined: Aug 2008
More
Quote:
Originally Posted by motox1983

I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).

Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?

I ask about the version because, to play it safer, we want to make sure you are flashing the SBF of what was on your phone... No matter what way the phone got to 4.4.2, the SBF you are using should be of the same 4.4.2 that was on your phone. i.e. don't flash a T-Mobile 4.4.2 if you started out with a Telcel 4.4.2 rom on your phone. And don't flash a Telcel 4.4.2 if you had a Movistar 4.4.2 rom on there.

Post the contents of the XML, its easier to see what might be wrong with it. Or post the original, un-edited XML, and I will make the edits for you.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools
Display Modes


Top Threads in Moto X Q&A by ThreadRank