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.

[Q] Moto XT1058 help going back to stock

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!!

[Q] Moto X AT&T is STUCK on Bootloader! [HELP]

Hi guys, yesterday i tried to install ROM "XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml" to my moto X 1058 At&T (android 4.4.4) with RSD litle.
It failed and now i only can turn on the phone and it goes to bootloader menu and i cant do anything. I can connect it to my PC and RSD detect it but i cant put any kind of ROM ((
I know that my moto x is not dead yet i have hope u.u :crying:
Please someone can help me? :crying:
PS: SORRY MY ENGLISH
PS2: I ADD A SCREENSHOT WITH SOME DETAILS ABOUT MY MOTO X after DO what i explain.

First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.

KidJoe said:
First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.
Click to expand...
Click to collapse
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time

NEW INFO
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?

zloopa said:
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time
Click to expand...
Click to collapse
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
zloopa said:
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?
Click to expand...
Click to collapse
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.

KidJoe said:
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.
Click to expand...
Click to collapse
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.

zloopa said:
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.
Click to expand...
Click to collapse
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.

KidJoe said:
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.
Click to expand...
Click to collapse
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone

zloopa said:
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone
Click to expand...
Click to collapse
As I said earlier... flash using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 ) just use that 5.1 SBF... and I would consider including the mfastboot erase userdata command, or doing a factory reset after you flash... Yes it will erase your data, apps, SDCard, etc...

GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it

aamszia said:
GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it
Click to expand...
Click to collapse
Hi in same situation. Did u fixed it?

moto x 1st gen 4.2.2 Upgrade to 5.1

Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?

No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X

bushako said:
No the new updates do not relock the bootloader. I suggest you first try out the Lollipop by flashing it through latest version of TWRP. If you think you can live with it than just flash complete stock through rsdlite or manually by fastboot. Reason I say that is because once you take the OTA it will update both bootloader version and the partition tables which means you won't be able to revert back to a lower Android version without the risk of bricking your device.
Sent from my Moto X
Click to expand...
Click to collapse
I don't want to go back to complete stock, I want to keep bootloader unlocked and root. Is there a stock rooted rom out there I can flash w/ TWRP without having to do OTA or flashing the recovery back to stock?

Yes there is its in the development section. You'll read the thread something like xt1053 stock flash-able. It contains only the kernel and system files so you should be good.
Here http://forum.xda-developers.com/showthread.php?t=3155843
Sent from my Moto X

-RanZ- said:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Question:
To upgrade to 5.1 do I just need to revert back to stock boot loader and do an OTA update?
Will the OTA re-lock my boot loader?
After the upgrade to 5.1 do I just reload TWRP recovery and flash SU for root access again?
Click to expand...
Click to collapse
First off, there is no Verizon 5.1 yet. So any 5.1 you try will be for a different model, and if you flash a full rom, it will have different radios (which don't work for CDMA that Verizon still uses for voice/3g data. If you keep your stock VZW radio files, keep in mind they will be on a different version than the rest of the rom which could cause some inconsistencies and issues. IF you do flash a FULL SBF, you will be stuck with no SAFE way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature), and you'll have to wait for the Verizon 5.1 SBF to get back to Verizon's rom.
Next, to install an OTA update, when it becomes available, you need STOCK RECOVERY on your phone. The OTA also does a pre-flash check/validation of your phone before it flashes, so if anything it looks for is not what it expects, the OTA will fail. Because of that you need to be 100% stock, or very near to it.
Finally, NO, an OTA will not relock your bootloader, nor will flashing an SBF.
For more on taking an OTA, see the link in my signature on OTA Updates..
That being said, if you TRY a 5.1 rom that is out there for another model you best bet is to find one that is a TWRP back up of 5.1 installed on someone's phone, since it only updates system.img and boot.img. It may not work 100% (because part of your phone will still have the 4.4.4 files), but it will give you a taste and you could later revert back to the stock 4.4.4 which you currently have on your phone. IF you flash a FULL SBF, you might be stuck with no way to revert to 4.4.4 due to GPT.BIN/Motoboot.img (for more on this, see the link in my signature)

Hi Bushako, I've Moto X Verizon XT1060 and it's struck in 4.2.2 android. When I try to update using setting, about phone and system update it show there is no update available but the android version on it is 4.2.2

5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery

-RanZ- said:
5.1 is available for Verizon Moto X 1st gen now isn't it? I am googling for a detailed process on how to update from 4.2.2 to 5.1 and keeping root but not having any luck finding anything. Is it easy to update from 4.2.2 stock rooted to 5.1? The specs of my phone are the same as the original post:
Verizon
Moto X 1st Gen
Android 4.2.2 - Stock rooted
Unlocked Boot loader - not DEV edition though
TWRP 2.7.1.1 recovery
Click to expand...
Click to collapse
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.

KidJoe said:
Aug 1, when I last posted in this thread, Verizon 5.1 wasn't available. It is now.
As for updating and keeping root, there are a few ways to do it. Since you say your Bootloader is unlocked, the best way is flash 5.1 SBF, and use the process of flashing TWRP and SuperSU to root and have Write protection Disabled (see -> http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 ). If you're bootloader isn't unlocked yet, and if you are on 4.4.2 or lower and have NEVER upgraded to 4.4.4 or 5.1, use Sunshine to unlock the bootloader FIRST
If you're bootloader isn't unlocked, there is only one way to root 5.1, but it doesn't disable write protection, and its risky because it intentionally soft bricks the phone back to the Qualcomm HS-USB QDLoader mode.
Click to expand...
Click to collapse
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.

-RanZ- said:
Bootloader is unlocked, I get the warning every time I restart the phone.
Where can I find the SBF files? Every post I find from a search the links do not work.
Are the SBF files stock or from someone else's phone?
Do I flash the files with my currently installed TWRP?
When I flash the SBF does it remove TWRP so I have to re flash it?
Are there any radio upgrades/do they get done w/ the SBF?
Sorry if these are basic questions, I have not done much phone rooting since my old HTC Incredible.
Click to expand...
Click to collapse
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/

KidJoe said:
There is a link in my signature to a thread containing the known places that were hosting the SBF/FXZ files. That is the only place I can suggest you look.
SBF/FXZ files I'm taking about are stock, and digitally signed by Motorola. They can be flashed on phones with locked or unlocked bootloaders. NOTE: make sure you get the SBF for your device model and carrier!!
You flash these via Mfastboot or RSDLite. When using these tools you are flashing back to stock. After you get the SBF file, see -> http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 and read the REQUIREMENTS section, and pick either Option 3, 4 or 5 to actually flash (only use one option. which ever you find the easiest. Do NOT use Option 1 or 2 as they would not apply to your situation). I usually recommend option 5.
Yes, the process of flashing the entire SBF will overwrite TWRP with stock recovery. You'll need to flash it later as part of the rooting process.
Yes there are radio updates in the newer SBF files.
So basically, you flash to stock 5.1 by using the SBF files (following the requirements and ONE of the options in http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2 again,I usually recommend option 5), then root by following http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
One other tip... Make a back up of your phone BEFORE YOU FLASH. copy all data from the /sdcard area to your PC, make a list of all your apps, etc. And seriously consider erasing your UserData while flashing (wipes the phone clear), or doing a factory reset before you flash.
I only say this because 5.1 seems more stable (and less buggy) if a factory reset is done before/during the upgrade process.
EDIT: The 5.1 SBF file you want for a Verizon XT1060 is GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip and is available from -> http://motofirmware.center/files/category/11-moto-x-1st-generation/
Click to expand...
Click to collapse
I will give this a try if I can locate the correct SBF files, your information has helped greatly, Thanks!

nevermind, google fixed me.

XT1096 Verizon latest firmware version?

Hello,
I'd like to know what the latest firmware of the XT1096 is so I can make sure the phone is running the most recent Verizon firmware and radios.
Here is the info for the device I have which is running crdroid 6.0.1.
bootloader version 6011
baseband MSM8974BP_4235210.110.09.13R
I think it had LP5.0 before sunshining, but I don't remember.
In any case, does anybody know what the latest firmware is (5.1 222.21.39, I think) and the best way to update it (hopefully fastboot)?
Also, would flashing the latest firmware lock the bootloader?
I searched this forum, but didn't find was I was looking for.
Thanks!

xdadevnube said:
Hello,
I'd like to know what the latest firmware of the XT1096 is so I can make sure the phone is running the most recent Verizon firmware and radios.
Here is the info for the device I have which is running crdroid 6.0.1.
bootloader version 6011
baseband MSM8974BP_4235210.110.09.13R
I think it had LP5.0 before sunshining, but I don't remember.
In any case, does anybody know what the latest firmware is (5.1 222.21.39, I think) and the best way to update it (hopefully fastboot)?
Also, would flashing the latest firmware lock the bootloader?
I searched this forum, but didn't find was I was looking for.
Thanks!
Click to expand...
Click to collapse
I believe that the mikeoswego's ROM in the link below is based on the latest VZW 5.1 ROM:
http://forum.xda-developers.com/moto-x-2014/development/img-xt1096-victara-mofo-image-root-t3100145
You will not relock your bootloader by flashing any ROM.

xdadevnube said:
Hello,
I'd like to know what the latest firmware of the XT1096 is so I can make sure the phone is running the most recent Verizon firmware and radios.
Here is the info for the device I have which is running crdroid 6.0.1.
bootloader version 6011
baseband MSM8974BP_4235210.110.09.13R
I think it had LP5.0 before sunshining, but I don't remember.
In any case, does anybody know what the latest firmware is (5.1 222.21.39, I think) and the best way to update it (hopefully fastboot)?
Also, would flashing the latest firmware lock the bootloader?
I searched this forum, but didn't find was I was looking for.
Thanks!
Click to expand...
Click to collapse
The latest is probably this one here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
5.1 LPE23.32-25-5
The flashing commands for the full firmware are contained in the included flashfile.xml file. You need an unlocked bootloader to flash it with fastboot. Flashing a firmware does not relock the bootloader.
(I was a few seconds too late)

Gus Ghanem said:
The latest is probably this one here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
5.1 LPE23.32-25-5
The flashing commands for the full firmware are contained in the included flashfile.xml file. You need an unlocked bootloader to flash it with fastboot. Flashing a firmware does not relock the bootloader.
(I was a few seconds too late)
Click to expand...
Click to collapse
I flashed that file with success easily with RSD Lite. It updated the bootloader from 60.11 to 60.16. I think its the latest, I'll have to dig around the net to make sure. Thanks a lot. Bootloader still unlocked. woot!

xdadevnube said:
I flashed that file with success easily with RSD Lite. It updated the bootloader from 60.11 to 60.16. I think its the latest, I'll have to dig around the net to make sure. Thanks a lot. Bootloader still unlocked. woot!
Click to expand...
Click to collapse
Excellent! Now just make sure you never flash an earlier version of the bootloader or partition table, so you don't risk bricking the phone. Since you flashed stock factory firmware, you can check for official system updates from the phone. It's not likely Motorola will release any more updates for the Moto X 2014.