Database Develop

[Q] Downgrade Bootloader/gpt.bin on unlocked bootloader

I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...

mohlsen8 said:
I noticed on an unlocked bootloader, I can't downgrade the bootloader or gpt.bin (these are the only ones i checked once i read in another post about this). Can anyone explain why or how to do this? What is gpt.bin???
Kind of related - if the AT&T and Verizon locked BL 4.4 versions can downgrade, why can't I with an unlocked BL? It makes me feel cheated.. unless I'm not understanding something correctly...
Click to expand...
Click to collapse
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.

mohlsen8 said:
actually, after playing with it for a while now, i was able to downgrade from 4.4 to 4.2 (camera update) using RSD Lite and the leaked firmware. using fastboot commands themselves doesn't work. it's weird.
i'd still love to know why we can't downgrade the bootloader and some other files on unlocked dev editions.
Click to expand...
Click to collapse
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.

jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
This is absolutely correct!

jayboyyyy said:
you can. end of story. don't know what you read or what you are personally doing wrong that isn't allowing you to downgrade your device. but you most definitely can do this. there is nothing that you can't do with an unlocked bootloader.
Click to expand...
Click to collapse
there's a couple places i've seen this. and my bootloader is unlocked, and i can't downgrade, for instance, to the bootloader from the original t-mobile software (4.2.2 pre-camera) - this file, just to clarify (from sbf droid developers): TMO_XT1053_4.2.2-13.9.0Q2.X-116-X-17-6_CFC.xml.zip. i take the motoboot.img out and use "fastboot flash motoboot motoboot.img". i get:
(bootloader) Preflash validation failed
phone display says:
Failed to hab check for tz: 0x4e
?
while we're discussing, motorola says these can be relocked. in all of my screwing around this morning i was trying this too. i followed all directions and still cannot lock the phone. i use "fastboot oem lock" and it tells me:
(bootloader) FAIL: Please run fastboot oem lock begin first!
ok, so i use "fastboot oem lock begin". now it gives me:
(bootloader) Ready to flash signed images
ok, try "fastboot oem lock" again and then it gives me:
(bootloader) Re-Lock Failure. See Display
display says "No valid PIV block in SP for system piv validation failed (system) Re-lock failure".
i've tried many times to flash all stock files back to the phone using fastboot, as well as RDS Lite, and it's been successful each time, but it won't re-lock. i've also tried "fastboot oem lock begin" then flashing all the stock files, then "fastboot oem lock". still, no dice. what's up with this?

The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.

Steve-x said:
The updated bootloader isn't let you flash older files. If you flash a full package it will downgrade the bootloader first and then you can flash the other older files. If you use a program such as rsdlite it will handle it all for you.
Click to expand...
Click to collapse
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?

mohlsen8 said:
so if i flashed the entire 4.2.2 pre-camera file through RSD Lite, it would downgrade the bootloader as part of that? why am i not allowed to do this in fastboot manually?
Click to expand...
Click to collapse
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.

Steve-x said:
Yes, it would downgrade the bootloader.
You can do it with fastboot manually but you need to do it in the proper sequence is all.
Click to expand...
Click to collapse
really? i had no idea that sequence mattered. why would that matter if i have an unlocked bootloader and want to flash an older one onto the device?
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.

mohlsen8 said:
really? i had no idea that sequence mattered.
i just tried running the 4.2.2 pre-camera file through rsd lite (after removing the getvar line as usual) and it fails on 2/16 (flashing gpt.bin). screen says "downgraded security version. update gpt_main version failed. preflash validation failed for GPT".
i don't understand why it won't work for me and i really would love to understand all of this.
Click to expand...
Click to collapse
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?

beelzebu said:
to me happens the same, shouls we first downgrade bootloader and recovery before using GPT, maybe our version of RSD lite is not the same?
Click to expand...
Click to collapse
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.

mohlsen8 said:
i have 6.14. going to install 6.15 now and try.
edit: 6.15 does the same thing. won't flash 4.2.2 pre-camera through RSD Lite because of the downgraded security error on GPT.bin.
Click to expand...
Click to collapse
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X

flashallthetime said:
Had the same issue with downgrading from the camera ota to the pre camera sbf file, rsdlite wouldn't flash got.bin failed, I think it possibly the ota that prevents downgrading, but if you flash from one sbf file and downgrade you're OK, I haven't tried it, just a thought
Sent on my Moto X
Click to expand...
Click to collapse
Are you saying you were able to flash the pre-camera sbf? edit: sorry - didn't read you right at first. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.

mohlsen8 said:
Are you saying you were able to flash the pre-camera sbf? edit: sorry - see you said you didn't try this. i have tried it through rsd lite and no go.
I don't actually want to go back to that.. just want to know what the deal is with my "unlocked" bootloader. what i think is that the bootloader cannot be downgraded (and then gpt.bin and stuff subsequently cannot be). Someone pulled an oopsie with the 4.4 update because even the AT&T/Verizon versions can downgrade, so we can downgrade that but not to the pre-camera one.
I'm just used to nexuses where i can fastboot flash whatever i want whenever i want. i would just love clarification just to know what the deal is.
Click to expand...
Click to collapse
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X

flashallthetime said:
No I couldn't flash the pre camera sbf firmware after accepting the camera fix through ota, I believe flashing the ota flashes something that's prevents you from downgrading. You could try inserting the camera fix gpt.bin file into the pre camera sbf file and see if it flashes ?don't know if it will work
Sent on my Moto X
Click to expand...
Click to collapse
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.

mohlsen8 said:
at that point i could easily just flash everything other than gpt.bin and motoboot. i was hopping around on some of them today just to check it out. it's those two that are the issue.
Click to expand...
Click to collapse
now that's interesting. figured i'd try it anyway, so in the pre-camera SBF file i replaced gpt.bin with the post-camera gpt.bin and it flashes fine through rsd lite, motoboot and all. what the hell.

I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.

Steve-x said:
I think you can downgrade to any version. Check out the xml file for the order of operations. You will see some of them flash a few parts, then reboot the phone, and then continue with the flashing process. Others flash everything one partition after the other. I believe that reboot is vital for certain downgrades.
Click to expand...
Click to collapse
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.

mohlsen8 said:
i thought that as well and compared the two 4.2.2 xml's and did not find any real differences like that. not to mention gpt.bin is the first thing flashed and it fails when it tries to flash it. i'd like to know if anyone is or was able to directly flash 4.2.2 pre-camera without replacing the gpt.bin or motoboot.
Click to expand...
Click to collapse
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.

jayboyyyy said:
i would assume that your issue is coming from flashing OTAs that are not specific for dev phones (don't even know if dev phone OTAs are available). Im not certain of all of this, but when you flash the same OTA that a non-dev phone uses, it will still impliment the security checks to not let you downgrade even though your bootlader is unlocked. Perhaps you may need to unlock the bootloader again (even though it says it is unlocked). Again, i don't actually know this to be true, but I would assume that there is an error somewhere in some code that is relocking (or something like that) a dev phone that flashes the OTAs that are coming out. A nexus wouldn't ahve this problem because none of their OTAs are ever locked anyway (i believe). So the problem is probably with Verizon not releasing a different OTA for unlocked dev phones as opposed to consumer editions.
Im just speculating. Im sure you can find the answer on google if you read up about what unlocking the bootloader actually means.
Click to expand...
Click to collapse
is that a dig? you don't have to be a jerk. i'm not some idiot pressing buttons over here. just asking if anyone knows why this is.
this is for t-mobile. but i have a gsm dev edition, same model as t-mobile etc. even the official firmware files for the GSM Developer Edition, that i downloaded directly from Motorola themselves, are labeled "T-MOBILE RETAIL..". i don't think the dev edition ever had the pre-camera version (it shipped with the update applied). so maybe you're right about that. i dunno. i'm not the only one who's reporting this. i was just really curious to know why this is.

4.4.2 unlocked downgrade

Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks

ericizzy1 said:
Hi, tried searching my answer, but still not clear as to the answer for my situation, im about to purchase the unlock code for my non DE verizon moto x , code is from someone from china. If i upgrade to 4.4.2 while unlocked bootloader, any way back to 4.2.2 post camera update. Thanks
Click to expand...
Click to collapse
Yes and No
No you can not flash the complete 4.2.2 PCU package it will fail because you can't downgrade the bootloader
Yes because you can flash everything but the bootloader and it will take but if you accidentally take a OTA. you will brick your device.
but if you are able to unlock your bootloader then why would you want to downgrade. with a unlocked bootloader you will be able to root 4.4.2 with no issues

because when I was on 4.4, I had some battery consumption and heating issues also bluetooth was not perfect, I just wanted to make sure I have a way back To 4.2.2
also, not being able to downgrade the bootloader, in which way does this affect me going back to four point 4.2.2?

Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app

dray_jr said:
Your phone will work fine but like i said if you ever take a ota it will brick your phone
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?

Yup that is correct
Sent from my XT1056 using XDA Premium 4 mobile app

ericizzy1 said:
ota will brick, will be able to rsd to 4.4 or 4.4.2 if wanted?
Click to expand...
Click to collapse
No. Once you start mixing bootloader versions with system file versions (i.e. 4.4.2 bootloader with 4.2.2 system files), RSD Lite won't work. You will have to use a command line and mfastboot.exe to manually flash each partition.
And I actually tried to run 4.2.2 (post camera update) system files with a 4.4.2 bootloader and it would not boot; however, 4.4 system files do work with a 4.4.2 bootloader.
This has actually been discussed at great length and detail in this forum and A LOT of people were bricking their phones playing around with bootloader versions, just like you are talking about doing. At one point there was a sticky dedicated to it, but its since disappeared from the board for some reason.
To put it simply, please don't start mixing bootloader versions with system files. If you like 4.2.2, don't upgrade to 4.4.2. If you are on 4.4, then you can still downgrade to 4.2.2 (post camera update version). Do that and stay there. But if you upgrade to 4.4.2, don't fool around with it and start trying to downgrade. There is no point, and you will likely end up bricking your phone.
It's your phone, so do what you want, but you have been warned (by someone with personal experience by the way). If you do brick it, please don't start another "OMG! HELP ME!! I BRICKED MY PHONE!!" thread. There's plenty of those already floating around here. :good:

[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] Go from 4.2.2 to 4.4.2 Unlocked, rooted, twrp

I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks

dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
If all you want to do is update, you could install Custom ROM although you will lose Motorola's Active Display, Always Listening etc...
If you want complete stock and have to reflash TWRP and root your phone, you will need to flash the stock firmware using fastboot or a utility.

Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.

Alecegonce101 said:
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
Click to expand...
Click to collapse
Um, all VZW Moto Xs are SIM-unlocked.

dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
I hope it wasn't the pre-camera 4.2.2....or you might be in a tough spot now.... Risking a brick. ?
---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------
Unless the first firmware was also pre camera... Then you're OK.

dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
Taking OTA's is incremental, so if you are the initial shipping 4.2.2 you need to take the first 4.2.2 w/camera OTA, then the 4.4 OTA, then the 4.4.2 OTA... a real time waster and pain in the rear.
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
Since you have a Dev Edition, why not just go to 4.4.4? it has a few bug fixes, and is stable. For me and many others its no worse than 4.4.2 as far as performance and battery.
Once you arrive on the ROM you want, you can flash TWRP and root.

KidJoe said:
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
t.
Click to expand...
Click to collapse
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??

dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
Yup! ?
As long as it's not a lower version.

dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
OTA = Incremental. Only patches the changed/updated parts.
SBF/FXZ = "all inclusive" or "image files".. and overwrites entire partitions/parts.
So yes. You can just flash the newer SBF file. (As @Darth said... as long as the SBF you are flashing is NEWER than the version on your phone... i.e. NEVER DOWNGRADE)

[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?