Related
Update: The ATT 4.4 firmware seems to have worked. Everything seems to function just as it should. Will someone release the rogers ota 4.4 update that I can flash in the future? If that's the case would I follow normal flashing behavior to return to my proper firmware?
shartwell said:
The first problem I had was that this 4.4 image had some bugs(Tmobile here: http://sbf.droid-developers.org/phone.php?device=0). The home button didn't bring me to the homescreen, the push notification area didnt work(clicking the little profile thing for wifi bluetooth etc,) and some other minor bugs.
What did I do? I tried flashing a backup of my clean 4.2.2 -- Doesn't work. Tried flashing another 4.4(dhacker i believe,) boot loop.
I'm tryign to use rsdlite to restore stock 4.2.2 image and worked through soem areas(editing the xml,) but now I get "failed to hab check for tz:0x4e" Google searches didn't return any relevant solutions for my situation.
I had got the OTA update to 4.4 while running TWRP and forgot(and was unable) to revert to stock recovery to accept the OTA update. This is how it all started. Does anyone have a solution to this error code? I just can't seem to find one(it fails during motoboot.img btw).
Ps: I heard it could be my BL being upgraded to 4.4, which peope claim can be downgraded, but I've yet to see how.
Click to expand...
Click to collapse
The only 4.2.2 sbf firmware file that will flash correctly is the post camera sbf firmware, so make sure you are using the correct firmware, have you attempted to reflash the T-Mobile sbf firmware again? Sounds like a full wipe was not done after you flashed the T-Mobile firmware.
Sent on my Gummy running Lenoto X
flashallthetime said:
The only 4.2.2 sbf firmware file that will flash correctly is the post camera sbf firmware, so make sure you are using the correct firmware, have you attempted to reflash the T-Mobile sbf firmware again? Sounds like a full wipe was not done after you flashed the T-Mobile firmware.
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Thanks for the quick reply. I have to love you guys here at XDA
I've managed to get the ATT firmware to work perfectly. Will the 4.4 firmware be added to sbf in a little while(seems the ota is slow. I randomly got it.) for me to reflash like I did ATT?
shartwell said:
Thanks for the quick reply. I have to love you guys here at XDA
I've managed to get the ATT firmware to work perfectly. Will the 4.4 firmware be added to sbf in a little while(seems the ota is slow. I randomly got it.) for me to reflash like I did ATT?
Click to expand...
Click to collapse
You can flash the rogers 4.4.2 sbf firmware when its available, the only thing, which needs to be confirmed is you may not be able to downgrade. Do not flash the other 4.4.2 firmware other than rogers just to be safe , people are flashing crap and messing with modems,panicking that their data is screwed and flashing back and bam dead phone. The resurrection thread works for some but not for everyone. Wish people would flash kangakat, eclipse, cm11 or gummy rom , its safer and you have stock based ROMs with all motos goodies and custom
Sent on my Gummy running Lenoto X
Where can I find installation for CM(my favorite mod) for my device? I haven't seemed to find any. Might be that none has been developed.
Otherwise can you suggest another similar mod that would work for my device.
My data seems to be non-functional for ATT firmware, which is fine for the moment, I'll leave everything as is(unless I install a mod) and flash the 4.4.2 rogers when it becomes avaliable(Do you think it would be within the next couple of days since the OTA is out?)
Ps: The other option I have is downgrading to 4.2.2 than using the OTA update(which is what I should have done in the first place...I forgot how to flash stock recovery for OTA,) but it seems the bootloader has now been upgraded. I don't suppose there is a way around that to restore 4.2.2 stock?
shartwell said:
Where can I find installation for CM(my favorite mod) for my device? I haven't seemed to find any. Might be that none has been developed.
Otherwise can you suggest another similar mod that would work for my device.
My data seems to be non-functional for ATT firmware, which is fine for the moment, I'll leave everything as is(unless I install a mod) and flash the 4.4.2 rogers when it becomes avaliable(Do you think it would be within the next couple of days since the OTA is out?)
Ps: The other option I have is downgrading to 4.2.2 than using the OTA update(which is what I should have done in the first place...I forgot how to flash stock recovery for OTA,) but it seems the bootloader has now been upgraded. I don't suppose there is a way around that to restore 4.2.2 stock?
Click to expand...
Click to collapse
Make sure your apns are correct anyways here's cm11 http://forum.xda-developers.com/showthread.php?t=2546412
Sent on my Gummy running Lenoto X
flashallthetime said:
Make sure your apns are correct anyways here's cm11 http://forum.xda-developers.com/showthread.php?t=2546412
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I don't have root to flash TWRP or other recovery to install CM from 4.4. RSD doesn't seem to work with the cm11 zip.
shartwell said:
I don't have root to flash TWRP or other recovery to install CM from 4.4. RSD doesn't seem to work with the cm11 zip.
Click to expand...
Click to collapse
You need to flash cm11 with custom recovery like twrp, it won't flash with rsdlite
Sent on my Gummy running Lenoto X
flashallthetime said:
You need to flash cm11 with custom recovery like twrp, it won't flash with rsdlite
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Makes sense. Figured that was it. How can I get a custom recovery onto my phone, though, as it's unrooted on 4.4(which I've heard has no current root.)
Thank you for all the help, hope I can get cm working soon and forget about OTA in the future.
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
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Save my custom wallpaper using these instructions:
How to Pull Custom Wallpaper
2) Root using Slap My Moto method
- here it the 4.4 OTA if 4.4.2 has already come out by the time I do this
Verizon 4.4 OTA
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the 4.4.2 OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Then after I root, I can selectively flash the 4.4.2 update:
Slap My Moto Page 150
Important Warning Before Flashing 4.4.2 Page 15
System.img, boot.img, non-hlos.bin and fsg.mbn
Cozume said:
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Flash TWRP and boot into it to make a pre-root nandroid b/u
- I know the custom recovery won't stick when I reboot, just doing it to make a pre-root b/u
- is this necessary as long as the sbf firmware is available?
2) Root using Slap My Moto method
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Also, I can't hit the thanks button anymore today but if you help me I will come back tomorrow and hit it, I promise!
Click to expand...
Click to collapse
Flashing twrp while having a locked boot loader? Idk
Sent on my Gummy running Lenoto X
flashallthetime said:
Flashing twrp while having a locked boot loader? Idk
Click to expand...
Click to collapse
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
well good! you're on the right track. 3 best pieces of advice here:
1. Search first
2. Read alot (yes even some long threads with several pages)
3. Then Q & A is here for you.
Glad you're being safe with your exepnsive device, some noobs usually shoot first ask questions later.
Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
Flashing a custom recovery always requires a unlocked boot loader, On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Sent on my Gummy running Lenoto X
flashallthetime said:
On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Click to expand...
Click to collapse
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Cozume said:
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Click to expand...
Click to collapse
No, wait and see what happens, it makes sense flash 4.4.2 now, it won't make any difference now or later, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware. Read please. I have 6 months of moto x experience behind me, been here from day 1
Sent on my Gummy running Lenoto X
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
Click to expand...
Click to collapse
yeah, but it will cause me great sadness to sell my beautiful wood backed baby!!!
flashallthetime said:
it won't make any difference now or later
Click to expand...
Click to collapse
well, yes it would because if I take the OTA then I won't be rooted unless someone finds an exploit for 4.4.2 and I will never be rooted if someone doesn't.
flashallthetime said:
i
, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware.
Click to expand...
Click to collapse
I am getting confused now. If I stay on 4.4 rooted and something happens to my device, can I or can't I flash the sbf for Verizon 4.4 with a locked bootloader to restore my device?
Maybe I wasn't clear but my plan is to root on 4.4 and stay there by freezing MotorolaOTA, which is the app that installs the updates and sends the annoying message. I was going to stay on 4.4 rooted and not upgrade to 4.4.2 unless someone can come up with a way to root it with a locked bootloader.
Cozume said:
yeah, that is my plan. But it will cause me great sadness to sell my beautiful wood backed baby!!!
Click to expand...
Click to collapse
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Sent on my Gummy running Lenoto X
flashallthetime said:
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Click to expand...
Click to collapse
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Cozume said:
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Click to expand...
Click to collapse
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Sent on my Gummy running Lenoto X
flashallthetime said:
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Click to expand...
Click to collapse
I am not planning on taking the 4.4.2 OTA. The whole point of freezing MotorolaOTA is to block the OTA.
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?
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
bushako said:
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
Click to expand...
Click to collapse
I don't want to go back to complete stock, I want to keep bootloader unlocked and root. Is there a stock rooted rom out there I can flash w/ TWRP without having to do OTA or flashing the recovery back to stock?
Yes there is its in the development section. You'll read the thread something like xt1053 stock flash-able. It contains only the kernel and system files so you should be good.
Here http://forum.xda-developers.com/showthread.php?t=3155843
Sent from my Moto X
-RanZ- said:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
Click to expand...
Click to collapse
First off, there is no Verizon 5.1 yet. So any 5.1 you try will be for a different model, and if you flash a full rom, it will have different radios (which don't work for CDMA that Verizon still uses for voice/3g data. If you keep your stock VZW radio files, keep in mind they will be on a different version than the rest of the rom which could cause some inconsistencies and issues. IF you do flash a FULL SBF, you will be stuck with no SAFE way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature), and you'll have to wait for the Verizon 5.1 SBF to get back to Verizon's rom.
Next, to install an OTA update, when it becomes available, you need STOCK RECOVERY on your phone. The OTA also does a pre-flash check/validation of your phone before it flashes, so if anything it looks for is not what it expects, the OTA will fail. Because of that you need to be 100% stock, or very near to it.
Finally, NO, an OTA will not relock your bootloader, nor will flashing an SBF.
For more on taking an OTA, see the link in my signature on OTA Updates..
That being said, if you TRY a 5.1 rom that is out there for another model you best bet is to find one that is a TWRP back up of 5.1 installed on someone's phone, since it only updates system.img and boot.img. It may not work 100% (because part of your phone will still have the 4.4.4 files), but it will give you a taste and you could later revert back to the stock 4.4.4 which you currently have on your phone. IF you flash a FULL SBF, you might be stuck with no way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature)
Hi Bushako, I've Moto X Verizon XT1060 and it's struck in 4.2.2 android. When I try to update using setting, about phone and system update it show there is no update available but the android version on it is 4.2.2
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
-RanZ- said:
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Click to expand...
Click to collapse
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
KidJoe said:
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Click to expand...
Click to collapse
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
-RanZ- said:
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
Click to expand...
Click to collapse
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
KidJoe said:
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
Click to expand...
Click to collapse
I will give this a try if I can locate the correct SBF files, your information has helped greatly, Thanks!
nevermind, google fixed me.