Database Develop

[Q] Security Settings Force Closing in 4.4 (VZW Dev); can it be fixed?

Is anyone else having a problem with Security Settings constantly force closing anytime you try and view that area of settings? I'm on a bootloader unlocked, VZW Developer Edition following this 4.4 for VZW installation procedure: http://forum.xda-developers.com/showthread.php?t=2537398
I wasn't able to just OTA unfortunately. I currently am not rooted and no TWRP/CWM recovery installed, just straight installed from that link above. Everything works BUT the security settings which I need so I can enable installing apps not from the app store (e.g. Falcon Pro).
Thanks guys, I'm really at a loss on this one.

Was hoping this may have berm a common issue for other vzw dev edition owners. Was going to try returning to stock again and going through the ota updates. Hopefully they'll take this time.
Sent from my XT1060 using Tapatalk

+1. I just spent 3 hours trying to isolate the issue. With completely stock dev edition from Moto, it still fc's. I'm unhappily on an N5 until this can get resolved.

Using the one from Moto instead of the one from forums worked perfectly, and had the modem bin to boot. This is the one you want, you just need to hop through their little hoops and wait for the email:
1a202ae1579643c02c03f76a1a6e09f8 MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml.zip

The instructions from the link in the OP does not update the modem (NON-HLOS.bin). This is likely your problem...

I'm having a similar issue with a different 4.4 rom coming from stock 4.2.2. Do I just need to update the modem? and how would i do that?

elijahah said:
I'm having a similar issue with a different 4.4 rom coming from stock 4.2.2. Do I just need to update the modem? and how would i do that?
Click to expand...
Click to collapse
You always need to update the modem, just flash this two files. Please use the following commands and you are good to go.
fastboot flash modem NON-HLOS.bin
fastboot erease modemst1
fastboot erease modemst2
fastboot flash fsg fsg.bin

beelzebu said:
You always need to update the modem, just flash this two files. Please use the following commands and you are good to go.
fastboot flash modem NON-HLOS.bin
fastboot erease modemst1
fastboot erease modemst2
fastboot flash fsg fsg.bin
Click to expand...
Click to collapse
did you mean fsg.mbn?

[q] xt1052 4.4.4 ota update => no imei

Dear ALL,
i searched for this kind of problem, but no right answers
Today i received the OTA UPDATE and since there were pleny of annoinyng popup warnings, i just installed the stock recovery back:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
(as described in Mark Venture's website)
Since installing the OTA i had a constant error (not describing the error...just generic one), i then EVEN typed:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
Updating "correctly", then....
...then after the update, my MOTO X rebooted itself and all it was OK, BUT mobile signal radio: NO IMEI
How can i resolve?
What could have gone wrong, updating via OTA?
Could be that once (i bought it second hand) my XT1052 4.4.2 en.EU was an american MOTO X (infact it is a 32gb version?)
But it was NEVER be downgraded...just upgraded

Kinto said:
Dear ALL,
i searched for this kind of problem, but no right answers
Today i received the OTA UPDATE and since there were pleny of annoinyng popup warnings, i just installed the stock recovery back:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
(as described in Mark Venture's website)
Since installing the OTA i had a constant error (not describing the error...just generic one), i then EVEN typed:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
Updating "correctly", then....
...then after the update, my MOTO X rebooted itself and all it was OK, BUT mobile signal radio: NO IMEI
How can i resolve?
What could have gone wrong, updating via OTA?
Could be that once (i bought it second hand) my XT1052 4.4.2 en.EU was an american MOTO X (infact it is a 32gb version?)
But it was NEVER be downgraded...just upgraded
Click to expand...
Click to collapse
You can TRY:
fastboot erase modemst1
fastboot erase modemst2
(That erases baseband cache)
If that doesn't solve your issue, I'm sorry but I don't have any further suggestions. Post back and let us know if it works or not...

Sorry I forgot to say that I even tryed that.... But with "mfastboot" instead of "fastboot".... (just right after the non-hlos input)
Should I try with your commands? And the appropriate fastboot?
Thanks in advance!

Kinto said:
Sorry I forgot to say that I even tryed that.... But with "mfastboot" instead of "fastboot".... (just right after the non-hlos input)
Should I try with your commands? And the appropriate fastboot?
Thanks in advance!
Click to expand...
Click to collapse
Nope. If you tried already (fastboot OR mfastboot), it isn't going to work.
I'm a little confused by your OP though...you say that you flashed "fsg.mbn & NON-HLOS.bin"
Well....the 4.4.2 SBF contains the NON-HOLS.bin (and it wasn't updated in the 4.4.4 OTA).
But....the 4.4.4 OTA DOES contain a NEW fsg.mbn.
So probably what you need to do is extract the fsg.mbn from the OTA zip file, and flash it back with fastboot/mfastboot. Make SURE you get it from the correct OTA Zip for YOUR version (the EU version).
Probably what has happened is that you flashed the fsg.mbn from 4.4.2 to your phone on 4.4.4 (which again, is supposed to have a NEW fsg.mbn).
After you do that, erase the modemst1 and modemst2 partitions again afterwards.
Let me know if it works.

I had 2 atrix hd's have that issue after flashing custom roms, the imei was erased and the radio wouldn't turn on if you get it fixed let me know how you did it cause I'd love to give my atrix hd to my girl.
Sent from my XT1058 using Tapatalk

Kinto said:
Dear ALL,
i searched for this kind of problem, but no right answers
Today i received the OTA UPDATE and since there were pleny of annoinyng popup warnings, i just installed the stock recovery back:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
(as described in Mark Venture's website)
Since installing the OTA i had a constant error (not describing the error...just generic one), i then EVEN typed:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
Updating "correctly", then....
...then after the update, my MOTO X rebooted itself and all it was OK, BUT mobile signal radio: NO IMEI
How can i resolve?
What could have gone wrong, updating via OTA?
Could be that once (i bought it second hand) my XT1052 4.4.2 en.EU was an american MOTO X (infact it is a 32gb version?)
But it was NEVER be downgraded...just upgraded
Click to expand...
Click to collapse
Let me ask you this...
1. BEfore you started, do you know what ROM was on your phone?
2. Did you download that exact SBF and use the files from inside that to return to stock?
3, Exactly what model X and for what carrier is it? (since you say XT1052, but later say it was an american moto x... XT1052 isn't american, so I'm guessing you had the ROM from the wrong carrier/model on there to begin with?)
If you took the 4.4.4 update, then flashed NON-HLOS.bin and fsg.mbn from the original SBF, that is likely why you have no IMEI now.
The only 4.4.4 SBF available is the Verizon XT1060 one. so you can't get the 4.4.4 versions for your phone from it (different modem files). I don't know the commands to have someone back those up from someone who has 4.4.4 on their same model X from your same carrier. So you may be stuck waiting on the 4.4.4 SBF for your model and carrier to leak in order to repair your phone.
AND BTW... The info about the 410 error and flashing NON-HLOS.bin and fsg.mbn was IF you got that error when following that process of flashing back to stock, NOT AFTER TAKING AN UPGRADE. In fact, that page is only about returning to stock!!

KidJoe said:
Let me ask you this...
1. BEfore you started, do you know what ROM was on your phone?
2. Did you download that exact SBF and use the files from inside that to return to stock?
3, Exactly what model X and for what carrier is it? (since you say XT1052, but later say it was an american moto x... XT1052 isn't american, so I'm guessing you had the ROM from the wrong carrier/model on there to begin with?)
If you took the 4.4.4 update, then flashed NON-HLOS.bin and fsg.mbn from the original SBF, that is likely why you have no IMEI now.
The only 4.4.4 SBF available is the Verizon XT1060 one. so you can't get the 4.4.4 versions for your phone from it (different modem files). I don't know the commands to have someone back those up from someone who has 4.4.4 on their same model X from your same carrier. So you may be stuck waiting on the 4.4.4 SBF for your model and carrier to leak in order to repair your phone.
AND BTW... The info about the 410 error and flashing NON-HLOS.bin and fsg.mbn was IF you got that error when following that process of flashing back to stock, NOT AFTER TAKING AN UPGRADE. In fact, that page is only about returning to stock!!
Click to expand...
Click to collapse
Well he stated in his OP that it was an american model (probably XT1053) and was flashed to the XT1052 firmware before he bought it.
Also, there is an actual replacement fsg.mbn file -inside- the 4.4.4 OTA zips. The NON-HLOS.bin did not change from 4.4.2 > 4.4.4
I suggested him to find the OTA zip (for the version he is on now) and extract it, and flash the fsg.mbn file from it.
Given that, it would seem unnecessary to have someone back them up for him.....although I DO know how to do that (using Linux shell, and BusyBox 'dd'), if absolutely necessary...
Any flaws in my logic?

samwathegreat said:
Well he stated in his OP that it was an american model (probably XT1053) and was flashed to the XT1052 firmware before he bought it.
Also, there is an actual replacement fsg.mbn file -inside- the 4.4.4 OTA zips. The NON-HLOS.bin did not change from 4.4.2 > 4.4.4
I suggested him to find the OTA zip (for the version he is on now) and extract it, and flash the fsg.mbn file from it.
Given that, it would seem unnecessary to have someone back them up for him.....although I DO know how to do that (using Linux shell, and BusyBox 'dd'), if absolutely necessary...
Any flaws in my logic?
Click to expand...
Click to collapse
As long as the fsg.mbn can be correctly extracted from the OTA.zip, that should work.

Thanks for ALL your replies!
I do not know which version it was my MOTO X in the beginning.
It is now an XT1052 EU(rope) version
How could i find the en.EU OTA 4.4.4 version now? I already flashed, so it is not anymore in my phone....
And here in XDA i just saw a brasilian version
p.s. i flashed fsg.bin and non-hlos.bin BEFORE taking the OTA...it was just to returno to stock
But i did that, even AFTER the update, because i got this radio signal problem (hoping to fix it)

Kinto said:
Thanks for ALL your replies!
I do not know which version it was my MOTO X in the beginning.
It is now an XT1052 EU(rope) version
How could i find the en.EU OTA 4.4.4 version now? I already flashed, so it is not anymore in my phone....
And here in XDA i just saw a brasilian version
p.s. i flashed fsg.bin and non-hlos.bin BEFORE taking the OTA...it was just to returno to stock
But i did that, even AFTER the update, because i got this radio signal problem (hoping to fix it)
Click to expand...
Click to collapse
Understood. Flashing -before- was no issue. Flashing afterwards is likely what has caused you to lose your IMEI.
While I know that the EU ota is out (must be -- you updated using it), I haven't found it posted yet. Look in settings > about phone and note the system version. You might try searching based on that.....OR just ask someone to upload it for you here: http://forum.xda-developers.com/moto-x/general/moto-x-g-e-4-4-4-kitkat-rollout-t2805645
Keep us updated. I hope this fixed your IMEI problem, at least. Not sure if it will solve your "signal issues" - but you really haven't gone into detail about that.
Good Luck :good:

Sorry, perhaps my english is not anymore good
I got the IMEI problem WITH the OTA upgrade!
From 4.4.2 eu to 4.4.4 (done after i restocked the default recovery with the commands i initially posted)
I had no problem returning to stock recovery.
JUST the OTA upgrade gave me the problem

Kinto said:
Sorry, perhaps my english is not anymore good
I got the IMEI problem WITH the OTA upgrade!
From 4.4.2 eu to 4.4.4 (done after i restocked the default recovery with the commands i initially posted)
I had no problem returning to stock recovery.
JUST the OTA upgrade gave me the problem
Click to expand...
Click to collapse
OK, yes I was quite confused:
Kinto said:
Since installing the OTA i had a constant error (not describing the error...just generic one), i then EVEN typed:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
Updating "correctly", then....
...then after the update, my MOTO X rebooted itself and all it was OK, BUT mobile signal radio: NO IMEI
Click to expand...
Click to collapse
So you suggested that you got a "constant error - generic one" after installing the OTA, and afterwards you flashed the NON-HLOS.bin and fsg.mbn
I appreciate you clarifying the situation. Your OP appeared to suggest that it happened only after flashing those files.
Now I'm really confused. Try flashing the correct fsg.mbn anyways, since you definitely have mismatched versions.
If that doesn't fix it, I'm kind of at a loss. Hopefully the full FXZ is released soon and you can fix using that if nothing else...

This worked for me:
Flashing French 4.4.2 & then OTA to french 4.4.4 & replacing with Modem from my Rogers 4.4.2:
http://forum.xda-developers.com/showpost.php?p=54716988&postcount=7

Just an info because i tryed almost all, except downgrading.
If i try to fastboot the FBS Verizon version 4.4.4 to my XT1052 en.EU, is there a problem?
I know it is not raccomended (i noticed that my original moto x was a xt1053 version and it was sold to me with the 4.4.2 european XT1052 version....the seller told me it was an american ones before selling it to me...for me it was good because i do not use LTE), but THIS is NOT a downgrade.
I still have the 4.4.4 OTA en.EU
What could gone bad? NO radios? i still have a telephone who can't calls...sounds odd, isn't it?
edit: i now have a custom rom based on a universal build 4.4.4...i tryed even that (it is called DIRTY UNICORN)

No1 knows?
i am ready to install (this time i will try the rdslite method) the SBF 4.4.4 verizon over my "damaged" 4.4.4 en.EU version....
I am just waiting for your last reply

Just to inform you all:
I RESOLVED my problem!
I installed with RDSlite the SBF 4.4.4 Verizon version and i have no problem with radio signal in Italy! NO MORE IMEI=0
I will install the 4.4.4 Europe SBF version when it will be released, because the Verizon one has some useless apps for me.

Kinto said:
Just to inform you all:
I RESOLVED my problem!
I installed with RDSlite the SBF 4.4.4 Verizon version and i have no problem with radio signal in Italy! NO MORE IMEI=0
I will install the 4.4.4 Europe SBF version when it will be released, because the Verizon one has some useless apps for me.
Click to expand...
Click to collapse
So it restored you imei number? If that's the case it gives me hope I can get my old atrix up and running
Sent from my XT1058 using Tapatalk

Yes, It restored my IMEI number!
I was luckily enough to restore it the night before I had to be hospitalized! So I could use my Moto X to chat on whatsapp and surfing the Internet..... And Not the old Samsung Gio
Appiccicato con Moto X

General Reply
Kinto said:
Yes, It restored my IMEI number!
I was luckily enough to restore it the night before I had to be hospitalized! So I could use my Moto X to chat on whatsapp and surfing the Internet..... And Not the old Samsung Gio
Appiccicato con Moto X
Click to expand...
Click to collapse
Every Times when have troubles with IMEI and/or Signal, u Just need flash fsg and NON-Hlos.bin
adb devices
adb reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
Click to expand...
Click to collapse
with your original model, if that don't works then ur original operator
Like if u have a XT1056 and u flash a firmware of XT1052 all works, maybe imei but can fail, so u can use firmware of XT1052, u search a XT1056 firmware extract, search, and flash the modem files, and all works fine.

hi
i know this is old thread ..
i have around 100 units same issue IMEI : 0000000000
moto x XT1060 verison
tryed all the firmware 4.4.4. , 5.1.
even try cross flash to xt1053, xt1058 but no success

[Q] xt1056 says out of service ,flashed the wrong baseband

Hi, I'm using the kikat 4.4.2 verison rom before,baseband version, I don't know.
Since I flashed the wrong baseband could not find the the moblie network, on the status says : out of service.and trying to switch into Global mode. and I can no problem with th IMEI.
I'm now using kikat4.4.2 ,baseband version: MSM8960PRO_BP_2323.038.123.00R\
I have tried verison 4.4.4 and 4.4.2 baseband but not working, really make me confused.
I have do all the search I can and can not fix it, maybe is the network lock problem? but I have unlock it.
If someone could help me that would be very thankful!!
Thanks in advance.

myarms said:
Hi, I'm using the kikat 4.4.2 verison rom before,baseband version, I don't know.
Since I flashed the wrong baseband could not find the the moblie network, on the status says : out of service.and trying to switch into Global mode.
I'm now using kikat4.4.2 ,baseband version: MSM8960PRO_BP_2323.038.123.00R\
I have tried verison 4.4.4 and 4.4.2 baseband but not working, really make me confused.
I have do all the search I can and can not fix it, maybe is the network lock problem? but I have unlock it.
If someone could help me that would be very thankful!!
Thanks in advance.
Click to expand...
Click to collapse
Flash a compatible SPRINT baseband:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
then erase modemst partitions
fastboot erase modemst1
fastboot erase modemst1
then reboot
fastboot reboot
Do you have service now? If now, you will most likely need to flash the ENTIRE stock Sprint SBF. Remember to NOT*** attempt to downgrade. Only flash the same, or higher version than what is installed on the device...
Also note that once you erase modemst partitions, you must repeat my entire sim-unlock procedure....

samwathegreat said:
Flash a compatible SPRINT baseband:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
then erase modemst partitions
fastboot erase modemst1
fastboot erase modemst1
then reboot
fastboot reboot
..
Click to expand...
Click to collapse
Thank you for your answer!
when I flash the NON-HLOS.bin and fsg.mbn , it said :'(bootloader) Variable not supported!' but then says"OKAY...finish..."
..It's this a problem?
and the first time I flash the 4.4.4 kikat , accidentally flash the baseband, then I reflash the baseband version between 4.4.2 and 4.4.4 system.
Will I brick the phone? I can still see IMEI NO. I just try the the 4.4 baseband still not work.

myarms said:
Thank you for your answer!
when I flash the NON-HLOS.bin and fsg.mbn , it said :'(bootloader) Variable not supported!' but then says"OKAY...finish..."
..It's this a problem?
and the first time I flash the 4.4.4 kikat , accidentally flash the baseband, then I reflash the baseband version between 4.4.2 and 4.4.4 system.
Will I brick the phone? I can still see IMEI NO. I just try the the 4.4 baseband still not work.
Click to expand...
Click to collapse
"Variable not supported" is totally normal.
Why are you flashing a 4.4 baseband? Flash at least the 4.4.2 baseband and try again...
You aren't at risk of bricking unless you attempt to downgrade motoboot.img or gpt.bin (Don't do that...).

samwathegreat said:
"Variable not supported" is totally normal.
Why are you flashing a 4.4 baseband? Flash at least the 4.4.2 baseband and try again...
You aren't at risk of bricking unless you attempt to downgrade motoboot.img or gpt.bin (Don't do that...).
Click to expand...
Click to collapse
the reason why I try the 4.4 baseband , is others are not working.
I only flash the baseband part, did not try the motoboot.img and gpt.bin.
so whats the solution now?
I have zero experience with the motoboot.img or gpt.bin.
can I flash it with the fastboot?

myarms said:
the reason why I try the 4.4 baseband , is others are not working.
I only flash the baseband part, did not try the motoboot.img and gpt.bin.
so whats the solution now?
I have zero experience with the motoboot.img or gpt.bin.
can I flash it with the fastboot?
Click to expand...
Click to collapse
You have obviously misunderstood me....
I said that you should NOT*** flash motoboot or gpt (as downgrading these will result in brick).
Why not just try using RSD Lite or full manual method to do a complete return to stock? Find the thread in "General" titled "Return to 100% stock".

samwathegreat said:
You have obviously misunderstood me....
I said that you should NOT*** flash motoboot or gpt (as downgrading these will result in brick).
Why not just try using RSD Lite or full manual method to do a complete return to stock? Find the thread in "General" titled "Return to 100% stock".
Click to expand...
Click to collapse
thank you! report you later , sir!

myarms said:
thank you! report you later , sir!
Click to expand...
Click to collapse
Remember: Do NOT attempt to downgrade (can result in brick). Only flash the SAME or HIGHER version of what is currently on the phone. If you are on 4.4.2, only flash 4.4.2.
Good Luck!

Complete return to stock means the xt1056 stock rom? or I can use the xt1060 rom?
beacause I can't use the xt1056 stock rom in here.

samwathegreat said:
Remember: Do NOT attempt to downgrade (can result in brick). Only flash the SAME or HIGHER version of what is currently on the phone. If you are on 4.4.2, only flash 4.4.2.
Good Luck!
Click to expand...
Click to collapse
Complete return to stock means the xt1056 stock rom? or I can use the xt1060 rom?
beacause I can't use the xt1056 stock rom in here.

samwathegreat said:
Remember: Do NOT attempt to downgrade (can result in brick). Only flash the SAME or HIGHER version of what is currently on the phone. If you are on 4.4.2, only flash 4.4.2.
Good Luck!
Click to expand...
Click to collapse
it's weird that i usre RSD flash the xt1060 rom ,it could find the globle network ,but still says ' NO GSM UMTS networks were found'.
really dont know why?

Hi , I finally found what the problem is.
The sim card brokes!
Before I flash the rom ,it still works fine.
Really don't know why .
I try another sim on my phone works well.
so I solve my phone's problem.
thank you Sam.

Flashed US firmware and lost signal

Hi I hope somebody can help me, today I unlocked my bootloader my Moto g is XT1064 its from the carrier Nextel Mexico and no problem here, then I flashed US firmware to my phone because I wanted to install Lollipop, it was the only way to have it I saw a user here saying that it worked for him but he had one from another carrier from USA I think here was my mistake.
I flashed it and everything okay, but when it rebooted I didn't had signal my imei is correct but no bar signals, later I flashed lollipop with recovery thinking it could change something and still same, I think its because the modem.
I searched my original firmware but no luck, is there something I can do to restore my signal?, Any modem from another one could work?
Thanks, hope somebody can help me.

DCloud9 said:
Hi I hope somebody can help me, today I unlocked my bootloader my Moto g is XT1064 its from the carrier Nextel Mexico and no problem here, then I flashed US firmware to my phone because I wanted to install Lollipop, it was the only way to have it I saw a user here saying that it worked for him but he had one from another carrier from USA I think here was my mistake.
I flashed it and everything okay, but when it rebooted I didn't had signal my imei is correct but no bar signals, later I flashed lollipop with recovery thinking it could change something and still same, I think its because the modem.
I searched my original firmware but no luck, is there something I can do to restore my signal?, Any modem from another one could work?
Thanks, hope somebody can help me.
Click to expand...
Click to collapse
Yes, you can use the modem of this "RETLA_XT1063_4.4.4_KXB21.85-24_cid12_CFC_SVC.xml.zip" Firmware even if you are on Lollipop.
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
Click to expand...
Click to collapse
If you need a link for the Firmware, send me a PM, I can't post it here because I have not reached 10 posts yet.
Next time, try rooting and doing a backup before attempting this kind of stuff.

Expert opinion needed in going back to Stock

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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