Related
Hi,
I own a Moto X Developer Edition, so a XT1053 device.
After some issue, I decided to return to full stock, 4.4.2, and possibly changing the locale to get a full French support.
I followed the instructions from this thread to return to stock. And instead of choosing the original firmware, I took the French one from this list.
Everything run smoothly without any issue, except one annoying problem for a phone, the radio doesn't work, so no GSM connectivity. The phone says the radio is unactivated.
I think there is a way to "mix" some img files from the original Dev Edition and the FR one to get things working, but I don't know exactly. Any help would be greatly appreciated.
Thanks.
Hi,
Really need some help on this one because as I didn't get any answer, I decided to reflash the official 4.4 firmware to get my radio back. But as the Moto X has been flashed with the French 4.4.2 rom, it refuses to be downgraded to 4.4.
Any idea? Thanks.
Please please please please read up on these things before you end up flashing!
I'm glad I could answer before you ended up hard bricking your phone, your current bootloader is based on the 4.4.2 rom, so it is impossible to downgrade to previous images. If you were stubborn and skipped this information, you would have tried to manually flash the 4.4 image with mfastboot commands and just purposely left out the bootloader, if you did this, then as soon as you got the 4.4.2 OTA to update and accepted it, you would have hard bricked your phone.
Now with all that said, it may be possible to take the NON-HLOS.bin and fsg.mbn from the 4.4 SBF T-Mobile/Dev Edition image and try to flash that radio/modem to your phone. I would make a backup before doing this though. just follow the fastboot commands for the modem and you should be okay. Remember to follow them exactly.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I am not entirely sure that you can use the 4.4 modem with a 4.4.2 rom. There may have been some firmware changes that prevent this from working, but you are welcome to try, I would personally wait until a T-Mobile/Dev Ed SBF 4.4.2 image appears and try the same procedure with that instead, but you are welcome to "chance" it
Thanks for the help.
In the meantime, I've read this thread and this one. So, I tried to flash the Rogers Canada 4.4.2 image. Everything runs fine, but still no radio.
But, I currently run the instructions from here to return to stock, and so I didn't know I had to flash NON-HLOS.bin file. I'm going to try this right now.
Thanks again.
Just tried to flash the NON-HLOS.bin file by following your instructions. Tried with both Rogers Canada sbf and with the Official 4.4 image. Same, no radio.
Wait for the official Developer Edition 4.4.2 or I'll contact Motorola. Does somebody know if an there is some ETA from this official image?
Thanks.
romut said:
Thanks for the help.
In the meantime, I've read this thread and this one. So, I tried to flash the Rogers Canada 4.4.2 image. Everything runs fine, but still no radio.
But, I currently run the instructions from here to return to stock, and so I didn't know I had to flash NON-HLOS.bin file. I'm going to try this right now.
Thanks again.
Click to expand...
Click to collapse
Just to give you a heads up, the NON-HLOS.bin file is where most of the modem actually is (all 50-60MB of it), I'll send a PM to the topic creator, because it's not giving the community the right information, they are missing that critical piece.
Be careful with your bootloader, the FR version may be the same as the UK bootloader (30.B3), the Rodgers version is (30.B4) meaning you would no longer be able to flash the whole SBF for the FR version because it would have a lower bootloader. However, you would be safe by just flashing the system image, but I would recommend not taking any OTA updates if you flash it.
Also remember that radios require a reset/power down, because it needs to get the information from the SIM card to use the particular radio frequencies. Also make sure the APN is correctly configured, this may also cause an issue.
There may be another Developer Edition 4.4 image directly from Moto that you could try, I think it takes 24 hours for them to get back with you giving you the link to their google drive though, however, it may be the same as the T-Mobile one on SBF.
You could also attempt getting the patched files from a 4.4.2 OTA image and merging it with a 4.4 radio (basically over-writing some of the files in the 4.4 version), I am unsure if this would work, but in theory it should, since that's what is happening during the update. However, I don't know if there are checks or anything, don't brick your phone because of me
Thanks for your message.
I've tried to flash the modem part only, then switch off/on the phone. No way, no radio. As I flashed the Rogers firmware, yes, my bootloader has been upgraded to 30B4.
Only way now is to wait for the official Developer Edition 4.4.2 zip, or to contact Motorola.
romut said:
Thanks for your message.
I've tried to flash the modem part only, then switch off/on the phone. No way, no radio. As I flashed the Rogers firmware, yes, my bootloader has been upgraded to 30B4.
Only way now is to wait for the official Developer Edition 4.4.2 zip, or to contact Motorola.
Click to expand...
Click to collapse
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
flashallthetime said:
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
He wouldn't have been able to flash a 4.4 image anyways because he used the 4.4.2 FR image. The only reason to upgrade via OTA/SBF is if you are certain that your phone matches the SBF. Otherwise there are too many possible complications to list here. His best bet is the NON-HLOS and fsg from that 4.4.2 version since it has the 4.4 modem and the fixes/modifications of the 4.4.2 as well. Or he could try to "manually" update the T-mobile 4.4 SBF modem, by copying the T-mobile 4.4.2 OTA modem patches and overwriting the select few files in the SBF, then flashing the new image.
However, in reality, it's probably best to wait for the "official" SBF anyways.
mastarifla said:
He wouldn't have been able to flash a 4.4 image anyways because he used the 4.4.2 FR image. The only reason to upgrade via OTA/SBF is if you are certain that your phone matches the SBF. Otherwise there are too many possible complications to list here. His best bet is the NON-HLOS and fsg from that 4.4.2 version since it has the 4.4 modem and the fixes/modifications of the 4.4.2 as well. Or he could try to "manually" update the T-mobile 4.4 SBF modem, by copying the T-mobile 4.4.2 OTA modem patches and overwriting the select few files in the SBF, then flashing the new image.
However, in reality, it's probably best to wait for the "official" SBF anyways.
Click to expand...
Click to collapse
No just wait for the sbf firmware
Sent on my Gummy running Lenoto X
flashallthetime said:
Stuck between a rick and a hard place , been trying to warn folks not to flash the new 4.4.2 sbf firmware, the list gets bigger and bigger by the day if people who either hard brick or have no radio signal. I actually tried to just have a warning sticky for this reason and was denied by the moderators. All.I can suggest is flash the modem for south american variants as there 4.4.2 sbf firmware is available, also flash the fsg.mbn file too
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I know you're doing a dawn good job at warning people :good: I should have read some threads before flashing, my stupidity ! :laugh:
I'll try to contact Motorola and see what can be done. Problem is this is a DE bought in USA, and I'm in France. Not the best case.
romut said:
I know you're doing a dawn good job at warning people :good: I should have read some threads before flashing, my stupidity ! :laugh:
I'll try to contact Motorola and see what can be done. Problem is this is a DE bought in USA, and I'm in France. Not the best case.
Click to expand...
Click to collapse
Your screwed, the European boot loader is 30.b3 and America is 30.b4, the modem aren't compatible, you can't run European modems with american boot loader and visa versa , call moto
Sorry for your situation. Have you tried flashing the French firmware?
Sent on my Gummy running Lenoto X
flashallthetime said:
Your screwed, the European boot loader is 30.b3 and America is 30.b4, the modem aren't compatible, you can't run European modems with american boot loader and visa versa , call moto
Sorry for your situation. Have you tried flashing the French firmware?
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yes that's what I wrote, I've seen the bootloader has been upgraded. As the official ROM for the Moto X DE already includes the french, it's not a big deal for me to get stuck with the ghost.en.US ROM. But as I've already flashed a 4.4.2 (the french one), I need the official 4.4.2 which is not yet available.
I've read in another thread, Motorola has accepted to exchange some phones in that case, I cross my fingers.
Hi,
I had a chat yesterday with the Motorola Service. This issue can be covered by the warranty only for Developer Edition. Now my problem is the cost to send the Moto from France to the US, but I think this may be interesting for people with the same issue.
Or we have to wait for the official release of the T-Mobile 4.4.2 ROM, but I couldn't get an ETA.
stock 4.4.2 boot.img
i flashed faux123 custom kernel and was not aware it was for 4.4 the updater app allowed me to install it
now my phone is screwed up
does anyone know where I can find the stock kernel image for 4.4.2 on unlocked xt1053 dev edition
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
Hey, i got the verizon dev edition with unlocked boktloader and root device i flash xt1052 rom to get the ota to 5.1
And aftet i flashed the baseband of 4.4.4 xt1060 to get my network work.
But now i want to get back to 4.4.4 of the verizon dev edition and i download tgz fille from the motorola site
And i wanted to flash it on rsd lite but i didnt have the xml fille there? So i dont know what to do now?
Ty for help
harel013 said:
Hey, i got the verizon dev edition with unlocked boktloader and root device i flash xt1052 rom to get the ota to 5.1
And aftet i flashed the baseband of 4.4.4 xt1060 to get my network work.
But now i want to get back to 4.4.4 of the verizon dev edition and i download tgz fille from the motorola site
And i wanted to flash it on rsd lite but i didnt have the xml fille there? So i dont know what to do now?
Ty for help
Click to expand...
Click to collapse
there is a high risk of bricking your device while downgrading http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
It's highly risky to downgrade but if you persist just make sure your bootloader and partition table is not the one that got upgtaded with the latest 5.1 rom. If it is the latest then don't do it.
Sent from my Moto X using Tapatalk
You can downgrade completely to 4.4.4.
But don't take OTA, your phone will brick.
The safest way in my opinion is (if you want to downgrade);
- Flash entire official firmware of XT1060 to your phone.
- DON'T TAKE OTA
- Wait for full firmware of XT1060(5.1)
- Flash full firmware of XT1060(5.1)
But if you want to play with 5.1, you can try this;
In my case, I have XT1056, and I wanted to play around with 5.1, so I converted from XT1056(4.4.4) to XT1053(4.4.4), then took OTA to XT1053 (5.1).
After that I tried AOSP but my bluetooth headset had a problem with phone function, then I decided to go back to official firmware again.
Since there is no Lollipop image for XT1053 or XT1056 now, I had to flash another variants like XT1052 and XT1058, but I got no signal.
I had to downgrade to XT1056(4.4.4) and using it for a day. After that I found out that file size of fsg.mbn differ by variants, then I downloaded XT1053(5.1 OTA) to get it.
I mixed up an entire XT1052(5.1 retail EN) with fsg.mbn from XT1053(5.1 OTA) and flashed them manually. Now my XT1056 works very well (with Xposed framework).
Keep in mind that YOU DO THIS ON YOUR OWN RISK.
ong14 said:
You can downgrade completely to 4.4.4.
But don't take OTA, your phone will brick.
The safest way in my opinion is (if you want to downgrade);
- Flash entire official firmware of XT1060 to your phone.
- DON'T TAKE OTA
- Wait for full firmware of XT1060(5.1)
- Flash full firmware of XT1060(5.1)
But if you want to play with 5.1, you can try this;
In my case, I have XT1056, and I wanted to play around with 5.1, so I converted from XT1056(4.4.4) to XT1053(4.4.4), then took OTA to XT1053 (5.1).
After that I tried AOSP but my bluetooth headset had a problem with phone function, then I decided to go back to official firmware again.
Since there is no Lollipop image for XT1053 or XT1056 now, I had to flash another variants like XT1052 and XT1058, but I got no signal.
I had to downgrade to XT1056(4.4.4) and using it for a day. After that I found out that file size of fsg.mbn differ by variants, then I downloaded XT1053(5.1 OTA) to get it.
I mixed up an entire XT1052(5.1 retail EN) with fsg.mbn from XT1053(5.1 OTA) and flashed them manually. Now my XT1056 works very well (with Xposed framework).
Keep in mind that YOU DO THIS ON YOUR OWN RISK.
Click to expand...
Click to collapse
My situation is same with you. My phone is xt1056 sprint. I converted to xt1053, and got ota to 5.1. But I don't like stock 5.1,there are some bug with graphic... I flashed and used customs Rom CM, PA,Carbon...some day. But now, I want to come back 4.4.4. Can you guide me more details?
I think if you flash complete 4.4.4 from 5.1, phone will bricked, because bootloader can not downgrade as someone said in high risk ...topic. Maybe you can flash 4.4.4 fw with edit xml to NOT flash motoboot and gpt....
Right ?
And last question, if there is a method to flash back 4.4.4, can I flash 4.4.4 xt1053 ? I don't want my phone have many bloatware sprint xt1056.
md07 said:
My situation is same with you. My phone is xt1056 sprint. I converted to xt1053, and got ota to 5.1. But I don't like stock 5.1,there are some bug with graphic... I flashed and used customs Rom CM, PA,Carbon...some day. But now, I want to come back 4.4.4. Can you guide me more details?
I think if you flash complete 4.4.4 from 5.1, phone will bricked, because bootloader can not downgrade as someone said in high risk ...topic. Maybe you can flash 4.4.4 fw with edit xml to NOT flash motoboot and gpt....
Right ?
And last question, if there is a method to flash back 4.4.4, can I flash 4.4.4 xt1053 ? I don't want my phone have many bloatware sprint xt1056.
Click to expand...
Click to collapse
You can flash back to 4.4.4 of XT1053 or XT1056 as you prefer, I think their radio are compatible.
But when 5.1 comes out, DON'T TAKE OTA. You have to wait for a full firmware to upgrade your phone.
I always use a manual flash method, so I don't have to edit an xml file.
When you downgrades, you will see a warning message, just ignore them.
ong14 said:
You can flash back to 4.4.4 of XT1053 or XT1056 as you prefer, I think their radio are compatible.
But when 5.1 comes out, DON'T TAKE OTA. You have to wait for a full firmware to upgrade your phone.
I always use a manual flash method, so I don't have to edit an xml file.
When you downgrades, you will see a warning message, just ignore them.
Click to expand...
Click to collapse
Do you use fastening to flash fw? And you flash all part inside fw? Include motorboat and got... ? After flash, do you make unlock network again ?
I used mfastboot to flash all CGs to my phone. But you may try to skip some CGs like KidJoe said.
Every time when you return to stock or do a hard reset, you have to do the SIM-unlock process again.
harel013 said:
Hey, i got the verizon dev edition with unlocked boktloader and root device i flash xt1052 rom to get the ota to 5.1
And aftet i flashed the baseband of 4.4.4 xt1060 to get my network work.
But now i want to get back to 4.4.4 of the verizon dev edition and i download tgz fille from the motorola site
And i wanted to flash it on rsd lite but i didnt have the xml fille there? So i dont know what to do now?
Ty for help
Click to expand...
Click to collapse
Moto is no longer including the XML to flash via RSDLite, but you could make your own if needed... instead they include a BATCH file which calls a copy of Moto's fastboot to flash it.
That being said... I WARN YOU!!! You will risk bricking your phone if you attempt to downgrade. While there is a slight chance the phone will not brick, we have enough who have bricked to say it is not safe!!
Some will say... "its ok, just skip motoboot.img and gpt.bin when flashing" that isn't safe either. If you later get prompted for and take an OTA update you'll again likely brick. Further when motoboot.img and GPT.BIN are missmatched from the rest of a STOCK Moto rom we've seen "bugs" or "issues" of things no working, like speaker phone, Settings -> Security menu, etc which are not a problem when all parts of your phone are consistent.
You're best bet... wait until a full 5.1 SBF for the Verizon XT1060 is either posted to Moto's web site of Dev Edition Images, or wait until a copy leaks... however, that too many also fail *IF* the GPT.BIN and components of motoboot.img are newer or different in the build you are running compared to what is made available as the XT1060 5.1 SBF.
KidJoe said:
Moto is no longer including the XML to flash via RSDLite, but you could make your own if needed... instead they include a BATCH file which calls a copy of Moto's fastboot to flash it.
That being said... I WARN YOU!!! You will risk bricking your phone if you attempt to downgrade. While there is a slight chance the phone will not brick, we have enough who have bricked to say it is not safe!!
Some will say... "its ok, just skip motoboot.img and gpt.bin when flashing" that isn't safe either. If you later get prompted for and take an OTA update you'll again likely brick. Further when motoboot.img and GPT.BIN are missmatched from the rest of a STOCK Moto rom we've seen "bugs" or "issues" of things no working, like speaker phone, Settings -> Security menu, etc which are not a problem when all parts of your phone are consistent.
You're best bet... wait until a full 5.1 SBF for the Verizon XT1060 is either posted to Moto's web site of Dev Edition Images, or wait until a copy leaks... however, that too many also fail *IF* the GPT.BIN and components of motoboot.img are newer or different in the build you are running compared to what is made available as the XT1060 5.1 SBF.
Click to expand...
Click to collapse
Yea i think i will wait for the full sbf 5.1 for verizon, i dont want to take the chance.
Thank you all for your help when the 5.1 update will come to the verizon you think?
Hello everyone, I got an xt1050 while ago and wanted to flash 5.1 without any risk of bricking the device, so basically I'm just asking for a little boost of confidence and reassurance in the steps I'm going to take.
So, got my device bootloader unlocked via the moto page and I want to flash this version of 5.1:
http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
The XT1060 has the same FCC ID and almost the same radios, I want to flash the modded version. I read that I can flash practically every moto x rom regardless the version that was designed for, as long as I flash my model radios after.
My questions are, will this version work ok even though I'm not going to update the bootloader? And will it work okay with 4.4.2 radios?
The steps:
Flash TWRP. Probably via fastboot method.
Make a Nandroid backup
Boot into the custom recovery and flash the ROM
Factory reset (is the same as wipe data, wipe cache, and devilk? should it be after or before flashing the rom, not sure about this one)
Flash the modem firmware. Didn't find a lot about flashing radios so I extracted this from a comment:
Extract the file [from XT1050 GHOST BRIGHTPOINT-LRA 4 4 2 KXA20 16-1 31 11 cid9 CFC - in my case], and find JUST the following files: fsg.mbn & NON-HLOS.bin
use fastboot to flash these files:
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
then erase your modemst partitions:
fastboot erase modemst1
fastboot erase modemst2
REBOOT!
English is not my first language, so have that in mind.
Looking forward for your help, every little bit is welcome
If you read the entire thread (yeah, I know, total pain), then you'll see that many (including me) had problems doing what you did with the speakerphone not working until we flashed the 5.1 radio & rebooted. This is somewhat a slippery slope. For me, even that wasn't enough and the final step that got the speakerphone to work again was flashing the newest bootloader. If you're someone that doesn't give a damn about the speakerphone (unlike me), then go for it because the phone works fine on your ear with the older radio.
Once you've gone that far, reverting to something bootable on 4.4.x is a crapshoot. Or: I should say it's a luck proposition if you're thinking your nandroid backup is going to be of much use. It won't be unless you first flash a full .xml/sbf version of 4.4.4 and then restore the nandroid backup if you've still got it.
Of course, there might be exceptions to this. I plan to try reverting to 4.4.4 using a slightly customized .xml/sbf. I'm not seeing anything in 5.1 that is worth "upgrading" for. Also there are some things like the "data bug" that are negatives, use a lot of battery, etc.
By the way: I was on an xt1060 DE which no doubt has a different radio than yours so maybe yours will be OK.
Good luck.
I had bought used Moto X XT1049 on e-bay
I use it in Georgia (Caucasus) so, outside US
Story in short:
Phone (XT1049) was working on 4.4.2, flashed it to stock XT1053 Lollipop 5.1 with RTWP, still worked without issues, but got StageFright fix OTA notification, since there was TRWP I couldn't install it with OTA, found guide, followed it, installed new Lollipop, everything was OK, just it was not detecting SIM card, I blame the code from the guide, I might have flashed someto XT1049 hardware incompatible software, tried flashing XT1049 and XT1056 radio/modem from kitkat roms, "No sim card" still persists.
I don't think it is hardware problem, as I hadn't physically touched the sim card in between when it was working and wasn't, it might be that hardware "fried" due to software incompatibility,but I doubt it too, because the SIM card clearly survived if there was any cooking going on , it works in my old phone without problems right now. Tried other sim cards too, none of them detected by this device.
Full Story:
I don't remember exactly what firmware was it running when I got it, because when I turned it on and connected to WiFi OTA popped up and I installed update right away. Update quickly installed 4.4.2, I put sim card of local network and it worked all fine. It was not rooted, not Bootloader unlocked.
Two days later I found out that XT1049 was not getting any further OTA update and I wanted lollipop on my phone, having very little experience, I started searching for ways to manually flash lollipop to my device. As I was unable to find XT1049 lollipop rom (I knew already it didn't exist) and read somewhere that it was possible to flash XT1053 rom on XT1056 and XT1049, decided to give it a try.
So I unlocked the bootloader from moto site, installed TWRP recovery, downloaded XT1053 5.1 Lollipop rom from this thread and flashed it, IRRC (I'm 90% sure) I just flashed it and rebooted, without any of these code:
Code:
......
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
....
So XT1053 Lollipop 5.1 (222.21.15) was installed, everything worked fine, system, calling, wifi etc. The only thing was that I got OTA for StageFright fix. I tried to let OTA install itself but it didn't work, as after update rebooting RTWP was booting, preventing OTA update.
Than I found this thread and fallowed the first guide, under name: "Official Update Procedure", I did everything as was written there, new lollipop update was installed, but when the phone booted it was not detecting sim card, displaying error in the notification bar: "No SIM card - Emergency calls only". After that I tried everything, reflashed XT1053 Lollipop 5.1 (222.21.15), flashed CM12 without luck.
Then I found out it might have been caused by flashing wrong modem (I was following the guide blindly and didn't even know about existence of modem/radio roms then) with this code from the guide:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
So I started searching and flashing modems from XT1049 and XT1056 roms of original 4.4.2 and 4.4.4 images, still without luck. Tried wiping, unrooted, tried 2nd(restore) method from stagefright guide (which if I had used instead of the first one with codes, I think I'd save myself all these troubles) nothing worked. Now I have installed XT1053 Lollipop 5.1 (222.21.15), am still getting Stagefright OTA notification and everything works fine except I can't use the device as the phone, it does not detect sim card at all.
My nearest guess is still around those codes from the Stagefright guide, it should be modem or bootloader or some other files that got flashed by those codes and might have been incompatible with XT1049 hardware.
So is there anyone with any ideas I might try out?
Suggest what can I try to revive the sim please.
At some point I decided to give a try and flash Kitkat images, in hope that they might have worked, but then read lots of warnings about downgrading, so decided not to hurry.
Right now my XT1049 has:
Bootloader - version30.BE
Baseband version - MSM8960PRO_BP_2323.031.111.00R
System Version (XT1053 Lollipop 5.1) - 222.21.15.ghost_row.Retail.en.US ntelos
Additional info:
XT1056 and XT1049 have the same FFC ID, XT1053 has different, but it's the nearest unlocked version with lollipop, that's why people flash XT1053 Lollipop to XT1056/49, as I have written above, I did the same and it worked without issues, until I installed StageFright update.
Thanks for your time and help in advance.