[Q] Moto XT1058 help going back to stock - Moto X Q&A

I installed TWRP and Cyanogenmod 12.1 on my XT1058, and would like to know if I can flash the stock ROM. I already have the link, but would like to know if there is a problem with going from 5.1 to 4.4.4, and what the difference is between a retail rom or the one of a provider, and how to know if my phone is retail or not. Thanks

there's a way!!
Mauro Mascioni said:
I installed TWRP and Cyanogenmod 12.1 on my XT1058, and would like to know if I can flash the stock ROM. I already have the link, but would like to know if there is a problem with going from 5.1 to 4.4.4, and what the difference is between a retail rom or the one of a provider, and how to know if my phone is retail or not. Thanks
Click to expand...
Click to collapse
I believe there are threads in General Section for getting back to Stock and receiving the OTA.
Also if your phone came without any contract from any carrier, it should be a Retail one. (You should have checked the firmware name before flashing CM for confirmation)

nijom said:
I believe there are threads in General Section for getting back to Stock and receiving the OTA.
Also if your phone came without any contract from any carrier, it should be a Retail one. (You should have checked the firmware name before flashing CM for confirmation)
Click to expand...
Click to collapse
But how can i know? Does it have to have branding or something that makes it diferentes? And what happens if i install a carrier one in a retail one? And viceversa? Also would there be any problems if i go to a previous android version? Because ive read that there can be problems if you downgrade the bootloader or something

Mauro Mascioni said:
But how can i know? Does it have to have branding or something that makes it diferentes? And what happens if i install a carrier one in a retail one? And viceversa? Also would there be any problems if i go to a previous android version? Because ive read that there can be problems if you downgrade the bootloader or something
Click to expand...
Click to collapse
I would stick with the stock rom for your phone's model and if its carrier branded, the rom for that carrier/model.
I would suggest you read -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 It FULLY explains why I recommend that.

KidJoe said:
I would stick with the stock rom for your phone's model and if its carrier branded, the rom for that carrier/model.
I would suggest you read -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 It FULLY explains why I recommend that.
Click to expand...
Click to collapse
So if i delete the gpt.bin and the motoboot.img i shouldnt brick the phone? Or i missunderstood?

Mauro Mascioni said:
So if i delete the gpt.bin and the motoboot.img i shouldnt brick the phone? Or i missunderstood?
Click to expand...
Click to collapse
If you have installed custom rom than you can easily go back to stock. but if you taken the ota than don't try to downgrade. most probably your device will get bricked. Check your bootloader version. if its 30.B7 than only flash the stock 4.4.4 otherwise don't.

miju12 said:
If you have installed custom rom than you can easily go back to stock. but if you taken the ota than don't try to downgrade. most probably your device will get bricked. Check your bootloader version. if its 30.B7 than only flash the stock 4.4.4 otherwise don't.
Click to expand...
Click to collapse
I am in cyanogenmod 12.1, how can i find out my bootloader versión?

Mauro Mascioni said:
I am in cyanogenmod 12.1, how can i find out my bootloader versión?
Click to expand...
Click to collapse
power off your phone. press vol down+power for 5sec an release. you will be in bootloader mode. see the second line

miju12 said:
power off your phone. press vol down+power for 5sec an release. you will be in bootloader mode. see the second line
Click to expand...
Click to collapse
Yes i have 30.B7, so if i flash the factory imagen i should be fine? Do i still need to delete the motoboot.img and gpt.bin? Alshow can i find out if i have a retail or carrier phone?
And if i want to flash the brazil 5.1 image, can i do it with no problems? Will i brick?
Thanks

Mauro Mascioni said:
Yes i have 30.B7, so if i flash the factory imagen i should be fine? Do i still need to delete the motoboot.img and gpt.bin? Alshow can i find out if i have a retail or carrier phone?
And if i want to flash the brazil 5.1 image, can i do it with no problems? Will i brick?
Thanks
Click to expand...
Click to collapse
you will be fine flashing factory image. you don't need to delete motoboot.img or anything. about retail or carrier i don't know because here we have retail versions only. if you flash 5.1 you can't downgrade back to 4.4.4. otherwise it fine.

miju12 said:
you will be fine flashing factory image. you don't need to delete motoboot.img or anything. about retail or carrier i don't know because here we have retail versions only. if you flash 5.1 you can't downgrade back to 4.4.4. otherwise it fine.
Click to expand...
Click to collapse
So if i flash the brazil 5.1 image it will work? Will the sim card work, i will still be able to use mobile data and make calles, text messages etc? I can just flash it from TWRP?

Mauro Mascioni said:
So if i delete the gpt.bin and the motoboot.img i shouldnt brick the phone? Or i missunderstood?
Click to expand...
Click to collapse
You misunderstood. AND COMPLETELY MISSED... Item #13 at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
I've said it before.. and I'll say it again... Some will tell you... "its ok, just skip motoboot.img and gpt.bin when flashing" but sorry, 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.
That being said.. 3rd party or custom roms usually don't touch gpt.bin, motoboot.img, the modem files, etc.. they usually only touch system and boot.
As @miju12 has explained, since you still have a 30.B7 bootloader, you should be able to still flash a STOCK MOTO 4.4.4 or Higher ROM without bricking. But, you wont be able to downgrade later.
You asked about flashing the Brazil 5.1 image.. IF your phone is a Brazil XT1058 you can flash it. If your phone is an XT1058 from another carrier and you have unlocked the bootloader, you can flash it. The Radio files between XT1058 variants have been the same (at least those I've seen). However, once you flash that image, you might not be able to flash to anything else... Again, read -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 and see items 9 & 12

KidJoe said:
You misunderstood. AND COMPLETELY MISSED... Item #13 at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
I've said it before.. and I'll say it again... Some will tell you... "its ok, just skip motoboot.img and gpt.bin when flashing" but sorry, 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.
Click to expand...
Click to collapse
But will this still happen if i have the same bootloader version as the one in 4.4.4? Because as far as i know, the bootloader version i have is 30.B7, and that is the same version of KitKat 4.4.4

Mauro Mascioni said:
But will this still happen if i have the same bootloader version as the one in 4.4.4? Because as far as i know, the bootloader version i have is 30.B7, and that is the same version of KitKat 4.4.4
Click to expand...
Click to collapse
Dude.. Item 22 -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202

KidJoe said:
Dude.. Item 22 -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Click to expand...
Click to collapse
Sorry its a rather long post and i read it a few days ago, i dont remember everything it says.
How can i know the build number of the cm 12.1 build that im using? So that i can compare it to the one of my countrys carrier?

Mauro Mascioni said:
Sorry its a rather long post and i read it a few days ago, i dont remember everything it says.
How can i know the build number of the cm 12.1 build that im using? So that i can compare it to the one of my countrys carrier?
Click to expand...
Click to collapse
custom rom doesn't have radio etc included in it. it is generally boot and system files. custom roms are all same for every model. it doesn't depend on carriers.

Mauro Mascioni said:
Sorry its a rather long post and i read it a few days ago, i dont remember everything it says.
How can i know the build number of the cm 12.1 build that im using? So that i can compare it to the one of my countrys carrier?
Click to expand...
Click to collapse
You can't equate the build numbers of custom roms to STOCK Moto Roms. Sorry. They are not the same.
As I typed a few posts ago...
KidJoe said:
That being said.. 3rd party or custom roms usually don't touch gpt.bin, motoboot.img, the modem files, etc.. they usually only touch system and boot.
As @miju12 has explained, since you still have a 30.B7 bootloader, you should be able to still flash a STOCK MOTO 4.4.4 or Higher ROM without bricking. But, you wont be able to downgrade later.
Click to expand...
Click to collapse

Wait so i should jst be able to flash the factory image and be find? Will i be able to update via ota to 5.1 when i get it then without bricking?
Edit: btw sorry i ddnt quote you, for some reason the quote button does not appear next to the other 3

Mauro Mascioni said:
Wait so i should jst be able to flash the factory image and be find? Will i be able to update via ota to 5.1 when i get it then without bricking?
Edit: btw sorry i ddnt quote you, for some reason the quote button does not appear next to the other 3
Click to expand...
Click to collapse
Going Stock 4.4.4 -> CM11/CM12 -> Stock 4.4.4 is fine because custom roms do not usually touch anything but system and boot...
I would just suggest trying to go back to the SAME Stock 4.4.4 you had on before you flashed a custom rom. there are less chances of issues that way. (which is pretty much what I said earlier in this thread )

Great thanks!!

Related

[Q] DOWNGRADE 4.4.4 FOR 4.4.3 or 4.4.2. Is it possivel?

I updated my Motorbike X XT1058 for 4.4.4 (KXA21.12 VZW_XT1060_4.4.4-KXA21.12-L1.26_1FF) and it wanted to do the DOWNGRADE for 4.4.3 or 4.4.2. Some way for that?
The GPT.BIN in 4.4.4 is different from 4.4.3, which is different from 4.4.2, which is different from 4.4.0's.
Motoboot.img is different between 4.4.3 and 4.4.2. 4.4.2's is different from 4.4.0.
These will prevent a complete, successful and safe downgrade of the rom version.
If you've seen all the "don't downgrade or you'll brick" warnings, this is what its talking about.
This ^^^
But a better question is WHY would you want to downgrade?
I did not like because of the modification Verizon
Christian Correia said:
I did not like because of the modification Verizon
Click to expand...
Click to collapse
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Darth said:
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Click to expand...
Click to collapse
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
DROID_4_UsEr said:
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
Click to expand...
Click to collapse
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
KidJoe said:
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
Click to expand...
Click to collapse
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
DROID_4_UsEr said:
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
Click to expand...
Click to collapse
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
I did try but no succes
KidJoe said:
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
Click to expand...
Click to collapse
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
DejanPet said:
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
DROID_4_UsEr said:
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
Click to expand...
Click to collapse
But you should know Sunshine developers charge a fee of 25 bucks to unlock and it works but you need to have a pay pal account and enough money for it
DejanPet said:
The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
its documented in the sunshine thread that once 4.4.4 is on your phone its too late. even if you manage to downgrade it without bricking, the parts sunshine relies on will already have been patched and cant be downgraded. so downgrading wont help you to get sunshine to work

[Q] Need Sprint 4.4.4 Stock Image

Please help! Need .sbf or system img & recovery img of Sprint 4.4.4!
Thank you!
Please post questions in the Q&A section
Thread moved
Sprint 4.4.4 sbf hasn't been released yet I'm afraid.
KJ said:
Sprint 4.4.4 sbf hasn't been released yet I'm afraid.
Click to expand...
Click to collapse
When do you think we can expect the sbf to be out? The update was out a long time back. Is the sbf uploded by developers or by Motorola itself?
abhishekpujar said:
When do you think we can expect the sbf to be out? The update was out a long time back. Is the sbf uploded by developers or by Motorola itself?
Click to expand...
Click to collapse
While the SBF's for the Developer Editions are released by Moto, the other SBF's are not. Instead, they are "leaked" to the internet. Therefore we really don't know. Its whenever the person leaking the file gets their hands on it, and it makes its way to the net.
Many don't realize that http://sbf.droid-developers.org/ is neither owned, nor operated, nor sponsored by Moto.
If you have an unlocked bootloader, you can go here http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594 and flash the 4.4.2 ROM link, which is a flashable zip for twrp. Once you wipe and flash that you can accept the 4.4.4 ota, which should fix your problem. If you're locked, you just need to wait to get the sbf.
mxc42 said:
If you have an unlocked bootloader, you can go here http://forum.xda-developers.com/moto-x/development/roms-stock-roms-t2499594 and flash the 4.4.2 ROM link, which is a flashable zip for twrp. Once you wipe and flash that you can accept the 4.4.4 ota, which should fix your problem. If you're locked, you just need to wait to get the sbf.
Click to expand...
Click to collapse
I hope you realize if he was already on a 4.4.4 firmware from any carrier and does what you've told him to do.... Boom... Instant brick.
Please be careful about what advice you give, especially with the easily brickable moto x. I'm sure you don't want to cause anyone to brick. That would be a real drag. ?
KJ said:
I hope you realize if he was already on a 4.4.4 firmware from any carrier and does what you've told him to do.... Boom... Instant brick.
Please be careful about what advice you give, especially with the easily brickable moto x. I'm sure you don't want to cause anyone to brick. That would be a real drag. ?
Click to expand...
Click to collapse
If you read through the linked post you would find out that the 4.4.2 zip I told him to flash to doesn't include the bootloader and can be safely flashed from 4.4.2. I've done it successfully and it saved me from waiting for the sbf.
@MystaWright please don't flash 4.4.2 if you were on a higher version already. If you do, you will likely destroy your device, or at least have some serious issues. ?
mxc42 said:
If you read through the linked post you would find out that the 4.4.2 zip I told him to flash to doesn't include the bootloader and can be safely flashed from 4.4.2. I've done it successfully and it saved me from waiting for the sbf.
Click to expand...
Click to collapse
I actually flashed the twrp recovery and downloaded the 4.4.4 sprint Rom in the development section and flashed that and I'm up and running now. Thanks for the concern and advice.
Already softbricked. Would flash the 4.4.4 rom (zip) from the link if I had a way to get the file on the device.
mxc42 said:
If you read through the linked post you would find out that the 4.4.2 zip I told him to flash to doesn't include the bootloader and can be safely flashed from 4.4.2. I've done it successfully and it saved me from waiting for the sbf.
Click to expand...
Click to collapse
Right, but the bootloader and gpt.bin would then be mismatched and when in that state, taking OTA has bricked the phone more often than not.
So its VERY RISKY suggesting that.

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.

[Q] Q: How to flash to stock firmware?

i have moto x (xt1058) without at&t logo (ghost_rcica) and i have some problems with wifi and downloading apps from play store.
so, i want to flash stock rom again in my moto x (if that will fix my problems).
i have locked bootloader. pleas help me.
sheikh.sami17 said:
i have moto x (xt1058) without at&t logo (ghost_rcica) and i have some problems with wifi and downloading apps from play store.
so, i want to flash stock rom again in my moto x (if that will fix my problems).
i have locked bootloader. pleas help me.
Click to expand...
Click to collapse
Visit the link in my signature for Stock SBF files...
The view/read/follow -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
but i have locked bootloader. can i flash stock firmware with locked bootloader?
KidJoe said:
Visit the link in my signature for Stock SBF files...
The view/read/follow -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
Click to expand...
Click to collapse
but i have locked bootloader. can i flash stock firmware with locked bootloader?
help!
sheikh.sami17 said:
but i have locked bootloader. can i flash stock firmware with locked bootloader?
Click to expand...
Click to collapse
i have downloaded the stock firmware. and will flash through manual method. the question is this that can i flash with locked bootloader?
sheikh.sami17 said:
but i have locked bootloader. can i flash stock firmware with locked bootloader?
Click to expand...
Click to collapse
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
help me.
i'm currently on 4.4.4 stock and i'm flash stock 4.4.4 again with locked bootloader. i'm not downgrading.
my phone's model is xt1058 i've downloaded brasilian 4.4.4 stock firmware for xt1058. i again ask is that ok to flash with locked bootloader?
thankyou so much for helping.
help me!
KidJoe said:
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
Click to expand...
Click to collapse
I'm currently on stock 4.4.4. and i will flash stock 4.4.4 again.
my phone's model is xt 1058. I've downloaded stock Brasilian 4.4.4 firmware
for xt 1058. i had Chat with a motorola agent he said that first i have to
unlock bootloader. i want to confirm again that if i flash without unlocking
the bootloader my will not get Bricked or something like that?
thank you for helping me.
sheikh.sami17 said:
i'm currently on 4.4.4 stock and i'm flash stock 4.4.4 again with locked bootloader. i'm not downgrading.
my phone's model is xt1058 i've downloaded brasilian 4.4.4 stock firmware for xt1058. i again ask is that ok to flash with locked bootloader?
thankyou so much for helping.
Click to expand...
Click to collapse
I don't know exactly what ROM is on a Brasilian XT1058.
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
That is what to look for when you are searching for the Stock SBF for your phone. The file name will usually contain parts or all of that info, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc)
This is important because if you have a locked bootloader, you can't for example flash an XT1058 from AT&T USA (locked bootloader), with the SBF for an XT1058 from Rogers Canada.
KidJoe said:
I don't know exactly what ROM is on a Brasilian XT1058.
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number.
That is what to look for when you are searching for the Stock SBF for your phone. The file name will usually contain parts or all of that info, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc)
This is important because if you have a locked bootloader, you can't for example flash an XT1058 from AT&T USA (locked bootloader), with the SBF for an XT1058 from Rogers Canada.
Click to expand...
Click to collapse
i don't have a at&t phone.
my phone's android version is 4.4.4
system version is 212.44.26. ghost_row. RCI. en. ca
build nunber is KXA21.12-L1.26
that would be really great if u can find correct stock firmware for my phone.
help would be really appreciated.
sheikh.sami17 said:
i don't have a at&t phone.
my phone's android version is 4.4.4
system version is 212.44.26. ghost_row. RCI. en. ca
build nunber is KXA21.12-L1.26
that would be really great if u can find correct stock firmware for my phone.
help would be really appreciated.
Click to expand...
Click to collapse
Right, you have an XT1058 from Rogers Canada... Notice the RCI in the system version (which I also mentioned in my post as a possible acronym)
No offense, but your posts come across as if you are not willing to do anything but ask "tell me how to do this".
I would have a different attitude if you showed me that you took the time to read and try to understand what has been posted.
For example, I KNOW the correct XT1058 RCI CA 4.4.4 SBF is out there on the file factory link, and it has XT1058, RCI CA, 4.4.4 and that system number in its name! but YOU have to take the time to look, IT IS YOUR PHONE.
But no, its been "do it for me."
I have a life. Helping people on these forums is a HOBBY, not a job. I don't have the time to spoon feed each individual. That is why there are guides written (which I gave you links to).
If you can't figure this out, maybe you should play it safe and skip trying to flash your phone. And if you haven't factory reset your phone yet, try that as a first step.
sorry!
KidJoe said:
Right, you have an XT1058 from Rogers Canada... Notice the RCI in the system version (which I also mentioned in my post as a possible acronym)
No offense, but your posts come across as if you are not willing to do anything but ask "tell me how to do this".
I would have a different attitude if you showed me that you took the time to read and try to understand what has been posted.
For example, I KNOW the correct XT1058 RCI CA 4.4.4 SBF is out there on the file factory link, and it has XT1058, RCI CA, 4.4.4 and that system number in its name! but YOU have to take the time to look, IT IS YOUR PHONE.
But no, its been "do it for me."
I have a life. Helping people on these forums is a HOBBY, not a job. I don't have the time to spoon feed each individual. That is why there are guides written (which I gave you links to).
If you can't figure this out, maybe you should play it safe and skip trying to flash your phone. And if you haven't factory reset your phone yet, try that as a first step.
Click to expand...
Click to collapse
sorry but u took me wrong. i have spent too much time in finding the correct firmware but i haven't found. i found at&t firmware which i dont want, and yeah i saw that link and have choose to flash through manual method.
KidJoe said:
Right, you have an XT1058 from Rogers Canada... Notice the RCI in the system version (which I also mentioned in my post as a possible acronym)
No offense, but your posts come across as if you are not willing to do anything but ask "tell me how to do this".
I would have a different attitude if you showed me that you took the time to read and try to understand what has been posted.
For example, I KNOW the correct XT1058 RCI CA 4.4.4 SBF is out there on the file factory link, and it has XT1058, RCI CA, 4.4.4 and that system number in its name! but YOU have to take the time to look, IT IS YOUR PHONE.
But no, its been "do it for me."
I have a life. Helping people on these forums is a HOBBY, not a job. I don't have the time to spoon feed each individual. That is why there are guides written (which I gave you links to).
If you can't figure this out, maybe you should play it safe and skip trying to flash your phone. And if you haven't factory reset your phone yet, try that as a first step.
Click to expand...
Click to collapse
and i have reset my phone many times but no fixes. and the link to sbf files is dead.
sheikh.sami17 said:
sorry but u took me wrong. i have spent too much time in finding the correct firmware but i haven't found. i found at&t firmware which i dont want, and yeah i saw that link and have choose to flash through manual method.
Click to expand...
Click to collapse
Yes, ATT is not right.
sheikh.sami17 said:
and i have reset my phone many times but no fixes. and the link to sbf files is dead.
Click to expand...
Click to collapse
It took me all of 15 seconds to use the link in my signature to the thread with SBF ROM sites, then click the FileFactory site, and find a listing for XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
which most certainly DOES work as I am downloading it as I type.
So again, you are looking for "Do it for me" rather than trying your self. Sorry, but I'm done. Good luck.
thanx!
KidJoe said:
Yes, ATT is not right.
It took me all of 15 seconds to use the link in my signature to the thread with SBF ROM sites, then click the FileFactory site, and find a listing for XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
which most certainly DOES work as I am downloading it as I type.
So again, you are looking for "Do it for me" rather than trying your self. Sorry, but I'm done. Good luck.
Click to expand...
Click to collapse
can u help me a little bit more? in the commands i saw this "fastboot oem config carrier vzw"
but i dont have a vzw phone. so which command should i use?
sheikh.sami17 said:
can u help me a little bit more? in the commands i saw this "fastboot oem config carrier vzw"
but i dont have a vzw phone. so which command should i use?
Click to expand...
Click to collapse
You should be fine not running that command I believe. Flash everything else.
Need Help
Hey Every One! I Need a little Help I Have Bought a moto X At&t but unfortunately i Wipe my custom Rom.. and now its stuck in Bootloader.
Ps.
Bootloader is unlocked
Phone is Rooted
Can You Tell me What can i Do? or any one have Stock Rom for Moto X Xt1058 (At&t). Cuz i have seen lots of links and there are broken..
Regards
Faisal Siddiqui
faisal siddiqui said:
Hey Every One! I Need a little Help I Have Bought a moto X At&t but unfortunately i Wipe my custom Rom.. and now its stuck in Bootloader.
Ps.
Bootloader is unlocked
Phone is Rooted
Can You Tell me What can i Do? or any one have Stock Rom for Moto X Xt1058 (At&t). Cuz i have seen lots of links and there are broken..
Regards
Faisal Siddiqui
Click to expand...
Click to collapse
Download the correct firmware from here: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Here you have the XT1058 AT&T 4.4.4 version for example: http://www.filefactory.com/file/48ofsvh148j7/ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip
Here is a good how-to: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Make sure you only flash a version that has the same or newer bootloader version! Downgrading can/will brick your device.
Just look up your bootloader version:
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Meaning if you have 30.B7 for example, flashing 4.4.2 is a big no-no
You can find more about it here: http://mark.cdmaforums.com/MotoX-Downgrade.htm
All credits to original posters

[Q] Help downgrade to offical verizon dev from lollipop

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?

Categories

Resources