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] Return to stock

Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
It seems that is pretty easy to brick this phone while changing versions. I would like to return it to stock, so that i can accept all OTAs. I don't care losing any data or root permissions. I've found this method to return to stock here in XDA:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
(cant post urls)
Android SDK
(cant post urls)
MFastboot(Used for manually downgrading to 4.2.2)
(cant post urls)
For firmware Download pick what firmware you want from the link below
(cant post urls)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
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
after your phone is done rebooting you will be completely stock firmware of your choice
I would like to know if there's any risk in doing this, or which would be the better way to get to android 4.4.
Thanks!

You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?

KJ said:
You can flash the same or higher versions . It's downgrading that bricks. On 4.4.2 and higher. ?
Click to expand...
Click to collapse
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks

vagh_nagas said:
So does that mean if my carrier give me an update from 4.4.2 to 4.4.4 i can take it and not worry. Also, with an unlocked boot loader will it re lock it?
Thanks
Click to expand...
Click to collapse
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.

KJ said:
No, it won't relock it. But, you can't take an ota if you have a custom recovery or have made many system changes....like Xposed. It needs to be uninstalled, properly.
Click to expand...
Click to collapse
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.

vagh_nagas said:
Okay, so that means that as long as I leave the recovery alone, and uninstall xposed before i take the update I can keep the boot loader. that is good. but does that mean that I can easily re root it? also thanks for the help, I have never rooted a phone that still gets updates and that is activated.
Click to expand...
Click to collapse
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?

OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.

KJ said:
If you have the stock recovery, yes....that's good. As long as Xposed is the only system changes you've done....You should be good.
Root is the same as any version with an unlocked bootloader.
But how did you root without a custom recovery?
Click to expand...
Click to collapse
When I first tried to use xposed, I Soft bricked my phone. That was just using towel pie's method of root. So I decided that it was not a good idea to do any modifications to my phone that I did not feel I had much control over. That is why I used the 4.4.2 boot loader unlocker (I forgot who made it already, sorry) . After that I re-installed a newer version of towel pie, and super SU (I have better luck keeping root with this app), and towel pie asked if I was going to install xposed and i said yes. then I attempted the xposed and reboot. at first it had said that it did not install correctly. then after the third time of me attempting it it and after soft rebooting the phone after using towel pie's software it let me keep xposed. I believe it was the soft restart that did it but I am not quite sure.
I have pics if you want to see my recovery.
Just to let people know i am using a Republic Wireless Moto X, That is why I must leave the recovery alone. Yes all features still work as if I had done nothing to it, Just in case some people were wondering that have this service.
---------- Post added at 11:49 PM ---------- Previous post was at 11:10 PM ----------
Another question I have for somebody that has republic wireless. if I unlocked my boot loader can I go back to jelly bean or is that just an impossibility?

mauri6870 said:
OP, you can just use RSDlite to update directly to 4.4.4. Just download RSDlite, as well as the 4.4.4 firmware for your phone. Boot to fastboot while keeping your phone plugged in to your PC with USB debugging on, and RSDlite will detect your phone on fastboot mode. Select the firmware zip and flash it.
Click to expand...
Click to collapse
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?

jisola said:
so in my case i can flash my careers firmware (4.4.4) while on 4.2.2? there's no risk bricking it that way? or if i get the same firmware (4.2.2 post cam) right?
Click to expand...
Click to collapse
Right.
Tho, let it be said....everything we do on XDA, everything , comes with risk.
Anything can go wrong, anytime.
Just wanted to remind of that. No one will, or at least should, guarentee anything on XDA. We all take the responsibility ourselves if something goes very wrong.
?
So in theory , yes, you should be absolutely fine. But again....stuff happens. Proceed at your own risk.

jisola said:
Hi,
I have a Moto X xt1058, with 4.2.2 post camera update, locked bootloader but rooted. I've been postponing the OTA to 4.4 for a while now. I now i can't just install it, because of the modifications i've been doing while rooted, and i'm pretty sure i can't restore everything i've done.
Click to expand...
Click to collapse
Before you upgrade, do you want to root after you've upgraded?
If so, you need to be aware of what can/can't be done BEFORE you update.

well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!

jisola said:
well, like things usually happen, if there's risk it will go wrong.
i flashed my careers 4.4.2 and kind of brick it. when it powers up the motorola logo shows up and instantly enters ap fastboot mode with the security downgrade failure.
i'll try flashing a 4.2.2 firmware (same career) to see if that fixes it, if not, i dont know what else could i try.
thanks everyone for your comments!
Click to expand...
Click to collapse
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.

Wansanta said:
If your bootloader is unlocked and you can get to a functioning bootloader mode you are not bricked.
Click to expand...
Click to collapse
i have a locked bootloader...
i've tried flashing 4.2.2 and there were a lot of errors during installation that werent there when i tried to go to 4.4, after flashing was complete i got the same boot error, is there anything else to try?

jisola said:
great to hear that, i have a locked bootloader
Click to expand...
Click to collapse
Locked is above my paygrade.
But by functioning bootloader I mean you can use fastboot commands to flash.

lanemst curr
Wansanta said:
Locked or unlocked?
Click to expand...
Click to collapse
i edited... i misread when u said unlocked...

jisola said:
i edited... i misread when u said unlocked...
Click to expand...
Click to collapse
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?

Wansanta said:
Have you tried sunshine to see if you can unlock? I don't know if it would work in the state your phone is in but it is worth the $25 if it would work.
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Also, this site has resources on it for the XT1058 but make sure you read them thoroughly and understand what you are doing b/f you proceed with any of these methods.
http://www.theandroidsoul.com/?s=xt1058
Of the utmost importance is that you know what version of the bootloader your device is on. You MUST know this b/f you do anything. What version is it?
Click to expand...
Click to collapse
thanks for all this help.
never heard of sunshine before, i assume is way to unlock your bootloader right?
im kind of new with bootloaders phones, how could i check my bootloader version, doesn't seem to appear in the fastboot menu

jisola said:
how could i check my bootloader version, doesn't seem to appear in the fastboot menu
Click to expand...
Click to collapse
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.

Wansanta said:
It is the second line. Mine is 30:B7 b/c I am on 4.4.4.
Click to expand...
Click to collapse
thanks again
mine is: 30.B4

[Q] [XT1053] How to get 5.1 back. Already updated once to 5.1

Hello,
Please help me get any OS back to my XT1053 for now. Here's what happened:
1) I unlocked the bootloader, rooted my XT1053, stock recovery. Then last week I tried updating it to 5.1 official version via OTA. It failed due to files mismatch (maybe due to using apps that need root like Adaway). So I downloaded 4.4.4 STOCK version from Moto website, flashed boot.img, system.img and followed all the steps given here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Once the phone booted properly into 4.4.4, I tried 5.1 OTA and it worked fine. Then I flashed TWRP and SU to get root (I lost root when I flashed STOCK 4.4.4).
2) Everything was fine except that whenever I rebooted, my phone would Optimize ALL the apps. I Googled a lot and apparently this happened to many folks and there was no solution.
3) Today, I thought I will try and fix it by sideloading the 5.1 OTA zip (I thought the regular OTA style installation that I did of 5.1 over mfastboot style installation of 4.4.4 had something to do with it. I know, this was stupid of me!)
4) So, today I went to TWRP and tried to flash 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip'. I am 100% certain that this was the file that I copied from /cache after OTA had downloaded the file last week and I had saved it locally on PC and in SD on phone. However, this flashing gave me an error saying that it expected either 4.4.4 KXA or 5.1 but that my system was 4.4?? So the flashing failed and my OS is gone. How can I get ANY OS back? Here are the things that I tried so far:
1) Installed RSD Lite and I am downloading XT1053_TMO_RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip file from http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 as I type this out now. HOWEVER, I think I shouldn't use it as I read KidJoe saying not to downgrade. (KidJoe's comments are here http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347)
2) THEREFORE, I was wondering if I could simply flash a higher or equivalent version of ROM. Since we don't have an official 5.1 flashable zip right now, can I use 5.1.1 by CM? It's present here: http://primehowto.com/install-andro...le-moto-x-xt1053-2013-via-cm12-1-nightly-rom/
3) If yes to point# 2 above, I have a small problem. My phone is not detected by 'adb devices; in TWRP recovery mode. My battery is 11%. Could that be the issue?
I KNOW THIS WAS A LONG POST. I JUST WANTED TO GIVE ALL THE INFO. PLEASE HELP ME GET ANY OS ONTO THE PHONE AND THEN I WILL WAIT FOR THE 5.1 SBF TO BE AVAILABLE. THANKS A LOT IN ADVANCE....

here [Official] XT1058_GHOST_RETBR_5.1 FXZ/SBF (Full Rom)uploaded by our fellow user GARUXA
https://doc-10-ak-docs.googleuserco...359/*/0BwcadIv25aK8Tng3SUk2b1k5aVE?e=download
http://forum.xda-developers.com/mot...t1058ghostretbr5-1-fxz-sbf-rom-t3144161/page2

hbenz2008 said:
here [Official] XT1058_GHOST_RETBR_5.1 FXZ/SBF (Full Rom)uploaded by our fellow user GARUXA
https://doc-10-ak-docs.googleuserco...359/*/0BwcadIv25aK8Tng3SUk2b1k5aVE?e=download
http://forum.xda-developers.com/mot...t1058ghostretbr5-1-fxz-sbf-rom-t3144161/page2
Click to expand...
Click to collapse
Thanks for quick response. But I have XT1053.. Can I still use the one that you gave?

Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?

hbenz2008 said:
Not recommended, hold on a bit. Did try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
No, I didn't try mfastboot of 'gpt' from 5.1 update file 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip'. I don't see an 'mboot' or 'boot' file in it though. I do see 'gpt'. Also, in fastboot mode it says "Charger connected" instead of "USB connected". I think that's due to the low battery too?

hbenz2008 said:
Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
Would you know if 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip' file is the OTA 5.1 file? I think that's how the naming convention goes i.e. the name is set to the system version on which it is going to be updated NOT the system version that it will be updated to. I don't know why this flash failed though. I can give you the exact error that I get when I try flashing this if that helps? Thanks!

Shoot the error. If it's security downgrade, again flash gpt and mboot from Ota 5.1.
I will have to verify the name of Ota as its critical info.

hbenz2008 said:
Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
When I tried flashing "Blur_Version.213.44.1.ghost_row.Retail.en.US.zip" file (which I still think is the OTA 5.1 zip), I get this error:
Package expects build fingerprint of mototola/ghost_retail/ghost:4.4.4/KXA21.12-L1.29.1/2:user/release-keys or motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys; this device has motorola/ghost_retail/ghost:4.4/13.11.1Q2.X-69-3/51:user/release-keys
This is where I got burned today. The above error wiped out my OS. I was on 5.1, I don't know why it says I have 4.4....

Prolly system mismatch, try only gpt and mboot. What error do u get?
---------- Post added at 09:27 PM ---------- Previous post was at 09:17 PM ----------
BTW your post provided good info. So Ota think u on 4.4.
You flashed only syst and boot to get on 4.4 ,could be where the prob is.
Need to know where img/rom info reside.
Double check the 4.4 files you flashed.
Just thinking out loud..

hbenz2008 said:
Prolly system mismatch, try only gpt and mboot. What error do u get?
---------- Post added at 09:27 PM ---------- Previous post was at 09:17 PM ----------
BTW your post provided good info. So Ota think u on 4.4.
You flashed only syst and boot to get on 4.4 ,could be where the prob is.
Need to know where img/rom info reside.
Double check the 4.4 files you flashed.
Just thinking out loud..
Click to expand...
Click to collapse
What's 'mboot'. There's no such file in the extracted folder of 'blur.....' file that I mentioned earlier. there is 'gpt'. My phone is detected via fastboot now so I can flash but don't know where the 'mboot' is

Hitdroid said:
What's 'mboot'. There's no such file in the extracted folder of 'blur.....' file that I mentioned earlier. there is 'gpt'. My phone is detected via fastboot now so I can flash but don't know where the 'mboot' is
Click to expand...
Click to collapse
Okay, so I fixed it. At least got an OS for now .. This is what I did.. I took a chance and went ahead with these steps:
1) Extracted files from Stock TMO 4.4.4 file 'TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz' got from Moto website.
2) Modified 'flash.bat' file to have below commands:
SET mfastboot=mfastboot.exe
%mfastboot% getvar max-download-size
%mfastboot% oem fb_mode_set
%mfastboot% flash partition gpt.bin
%mfastboot% flash motoboot motoboot.img
%mfastboot% reboot-bootloader
%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
3) It failed with 'partition', 'motoboot', 'logo'. Everything else was successful.
4) My phone booted into 4.4.4 now.
It's funny but I think I have successfully downgraded from 5.1 to 4.4.4... That means, my main system file was never upgraded to 5.1?? It's late and I want a phone for tomorrow so I won't try 5.1 tonight. But it would be great if experts could pitch in. How did I downgrade from 5.1 to 4.4.4?
Anyway, thanks for your help. Your comment about 'gpt' made me think "maybe my phone won't hard brick if I install 4.4.4 again".. and it didn't!
CHEERS!

You can downgrade Fri 5.1 to 4.4 without flashing gpt and mboot. Wait for full 5.1.
Excellent man. Check your bootloader version, it's probably lollipop. So don't take update yet.

I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app

to check bootloader BL, restart phone in fastboot read menu.
KidJoe got this better covered here
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Hitdroid said:
I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse

Hitdroid said:
I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Many try to skip GPT.BIN and MOTOBOOT.IMG... but when you have a version missmatch (gpt/motoboot from one rom, and rest from another), you increase your chance of bricking should you apply an OTA update zip in the future. And you'll likely end up with features not working or extra "bugs" that wouldn't otherwise appear.
For those who say "its safe to downgrade"... I'll point you to -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 and ask you to view the 7 links near the end of the first post as just a few examples.

Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app

Hitdroid said:
Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Hitdroid, do you mind sharing your 5.1 OTA file for xt1053.
I'm in the same situation as you. Got 5.1 OTA a few weeks ago, rooted it and installed TWRP. Then I accidentally installed my 4.4.4 backup which erased my 5.1 install.
I just installed CM 5.1 as a stopgap but i'd like to return to near stock so i'm following this thread.

as I thought, you have a 5.1 BL.
Gotta flash manually when sbf/ROM is available

Hitdroid said:
Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Because of your bootloader, the safest way is wait for the 5.1 SBF to be posted (since you have an XT1053, it will be posted on Moto's web site, and you don't have to rely on leaks)... But I have no idea how long that will take.
Now, you could try to take the OTA, but I've seen enough bricks to say.. If it was my phone... I'd wait.

I'm at work so will share the file once I go home. But I think we should wait for 5.1 SBF as @KidJoe and @hbenz2008 have stated.
Sent from my XT1053 using XDA Free mobile app

[HELP] Moto X XT1058 AT&T fully bricked! I can't do anything!

So, as the title says, I had a Moto X XT1058 from AT&T.
I updated a long time ago to Lollipop and the phone worked perfectly fine until yesterday, when suddenly shutted down and when I restarted, got stuck on M logo.
I restarted to bootloader(?) pressing power off and vol down buttons.
The version that shows me is 30.BE
The device wasn't unlocked or rooted, because I was happy with the stock ROM, so it says Device is LOCKED ans Status Code 0.
I tried every option on this menu and everyone says (in red):
"No valid PIV block in SP for system
piv validation failed (system)
Boot up failed"
I tryed with abd, fastboot, mfastboot and RSDLite to flash gpt.bin and motoboot.img and every time I do it I get a error, and the operation fails.
For what I've read in tooooooo many posts, it's probably death, but I resist to this idea, so I came here to ask for advice.
THE PHONE IS NOT IN WARRANTY ANY MORE.
Thanks in advance and sorry for my english (not my native language).

why dont you try twrp recovery ?
just flash it

fadyrox said:
why dont you try twrp recovery ?
just flash it
Click to expand...
Click to collapse
Can I do it if my phone isn't rooted? The bootloader it's locked!

Flash full stock att 5.1 rom, it will be fine.

Salik Iqbal said:
Flash full stock att 5.1 rom, it will be fine.
Click to expand...
Click to collapse
Flashing via fastboot mode will be okay !
do search here you will get details !

fadyrox said:
Flashing via fastboot mode will be okay !
do search here you will get details !
Click to expand...
Click to collapse
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058

MatiCepe said:
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
Click to expand...
Click to collapse
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !

fadyrox said:
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
Click to expand...
Click to collapse
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.

MatiCepe said:
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
Click to expand...
Click to collapse
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.

Salik Iqbal said:
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Click to expand...
Click to collapse
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.

MatiCepe said:
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
Click to expand...
Click to collapse
Is your phone is charge enough? Search 5.1.1 att xml zip

can anybody give a solution for this problem because i am also with a xt1058 at&t, The device wasn't unlocked or rooted and the version that shows me is 30.BE too
sorry my english

What's up with your device any screen shot?

Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!

Thank you
H3c4rtr1 said:
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Click to expand...
Click to collapse
You can help how you got the code, give details.
Thank you

Bootloader locked - cannot flash stock verification error

I flashed the wrong firmware and now my bootloader locked g6 is stuck in bootloader mode. Cannot flash stock due to validation errors. Any ideas to help me fix this?

hydroman202 said:
I flashed the wrong firmware and now my bootloader locked g6 is stuck in bootloader mode. Cannot flash stock due to validation errors. Any ideas to help me fix this?
Click to expand...
Click to collapse
Try to unlock bootloader and the reflash stock (don't go back to older version but go forward to next version):
https://mirrors.lolinet.com/firmware/moto/ali/official/

HueyT said:
Try to unlock bootloader and the reflash stock (don't go back to older version but go forward to next version):
https://mirrors.lolinet.com/firmware/moto/ali/official/
Click to expand...
Click to collapse
I really appreciate your response. My bootloader is ineligible to be unlocked. I can flash the bootloader partition. The ones I can't flash are boot, oem, system, gpt, and a few other critical ones. The other issue I run into is the validation error when I do flash a new firmware. The stock won't flash due to security downgrade issues. If there is a way to get around it I would appreciate any and all help!

hydroman202 said:
I really appreciate your response. My bootloader is ineligible to be unlocked. I can flash the bootloader partition. The ones I can't flash are boot, oem, system, gpt, and a few other critical ones. The other issue I run into is the validation error when I do flash a new firmware. The stock won't flash due to security downgrade issues. If there is a way to get around it I would appreciate any and all help!
Click to expand...
Click to collapse
What is your exact model? You may have to wait for Pie official or next monthly update to flash

HueyT said:
What is your exact model? You may have to wait for Pie official or next monthly update to flash
Click to expand...
Click to collapse
The model is xt1925dl

I
hydroman202 said:
I flashed the wrong firmware and now my bootloader locked g6 is stuck in bootloader mode. Cannot flash stock due to validation errors. Any ideas to help me fix this?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmwar...bsidy-TRAC_ONE_regulatory-DEFAULT_CFC.xml.zip is the Nov. Firmware. If this does not flash, then you have to wait for newer firmware

HueyT said:
https://mirrors.lolinet.com/firmwar...bsidy-TRAC_ONE_regulatory-DEFAULT_CFC.xml.zip is the Nov. Firmware. If this does not flash, then you have to wait for newer firmware
Click to expand...
Click to collapse
It would not flash however I found blankflash file for g6 ali variant. Is there a way I can use that without being in qualcomm mode?

hydroman202 said:
It would not flash however I found blankflash file for g6 ali variant. Is there a way I can use that without being in qualcomm mode?
Click to expand...
Click to collapse
Unfortunately, you're screwed until newer firmware that's later than 11/18 is released for your Trackfone/Straight Talk G6 or return for exchange for a new phone ?